[qubes-users] Re: randomizing VPN servers i connect to with my vpnvm?

2019-04-20 Thread Nick Darren 
On Sunday, April 21, 2019 at 3:34:25 AM UTC, Jon deps wrote:
> On 4/21/19 2:48 AM, Chris Laprise wrote:
> > On 4/20/19 7:14 PM, Jon deps wrote:
> >> On 4/19/19 9:22 PM, Jon deps wrote:
> >>> On 4/18/19 12:08 PM, Chris Laprise wrote:
>  On 4/17/19 8:38 PM, Stumpy wrote:
> > I was thinking the line "remote random" in my .ovpn file, along 
> > with the ip addresses would make the VPN VM randomly select 
> > different servers but that doesnt *seem* to be the case, the bit 
> > that was included in the .ovpn files that I think is relevant is:
> >
> > remote-random
> > resolv-retry infinite
> > nobind
> > cipher AES-256-CBC
> > auth SHA512
> > comp-lzo
> > verb 3
> >
> > Is there something else i need to do? I assumed it would either 
> > change when it reconnects or is restarted but that doesnt seem to 
> > be the case.
> >
> 
>  You also have to specify multiple "remote" lines, one for each address.
> 
> >>>
> >>>
> >>> is there some howto URL writeup on this , sounds like something I may 
> >>> like to try
> >>>
> >>
> >> cd /rw/config/vpn/
> >> user@localhost:/rw/config/vpn$ sudo cat vpn-client.conf
> >> client
> >> dev tun
> >> proto udp
> >>
> >> remote-random
> >>
> >> remote server1.net 1197
> >> remote server2.net 1194
> >> remote server3.net 1301
> >>
> >>
> >> #remote-random
> >>
> >>
> >> cipher AES-256-CBC
> >> resolv-retry infinite
> >> nobind
> >> persist-key
> >> persist-tun
> >> verb 3
> >> remote-cert-tls server
> >> ping 10
> >> ping-restart 60
> >> sndbuf 524288
> >> rcvbuf 524288
> >>
> >> fast-io
> >>
> >>
> >>
> >> auth-user-pass _userpass.txt
> >> ca server_ca.crt
> >>
> >>
> >>
> >> tun-ipv6
> >> script-security 2
> >> up /etc/openvpn/update-resolv-conf
> >> down /etc/openvpn/update-resolv-conf
> >>
> >> 
> >>
> >>
> >> apparently is    not  the  solution  , h ,  guess I'll keep  web 
> >> searching ..
> > 
> > 
> > If they're at different domains it should work. Otherwise, domain name 
> > caching may cause the same address to be re-used. The best way to avoid 
> > it is to specify IP addresses instead of domain names. But there is also 
> > the '--remote-random-hostname ' option that can prevent dns 
> > caching.
> > 
> 
> 
> ok yes, that worked !   thankyou  using the IP addresses instead of the 
> vpndomain.names
> 
> I do see that the ovpn server list has many servers for each geolocation 
> , and apparently what happens is   using the  country.domainname.net 
> cause one of them randomly on the server end to be chosen, beyond 
> my/user control.
> 
> so  hopefully me,  designating  one of often the many  , by using the 
> specific  IP address  isn't too much of a downside ?  re: obsfucation of 
> whom user is
> 
> looks like this remote-random   is more used  for load balancing 

Instead of using `remote-random` function, for the setup like NordVPN surely is 
a big mess. I can achieved that random parts by creating/using a simple bash 
script by using `shuf` on the location where it should be. This will be totally 
random everytime the vpn-vm got restarted.

-- 
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/c7c80485-e227-4e2d-b23b-295dca583aa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: ALL VMs are not working -- qmemman

2019-01-26 Thread Nick Darren 
On Sunday, January 27, 2019 at 1:04:11 AM UTC+8, Lorenzo Lamas wrote:
> I also had this error after installing these packages from Dom0 
> Security-Testing repo.
> I posted about it in the QSB #46 thread, but havent got a reply there. 
> Fortunately, with help of someone else I was able to fix it:
> https://groups.google.com/d/msg/qubes-users/5D8AxG3jtdw/CqyWjGEiGgAJ

Thank you Lorenzo, that's indeed an issues with that and now everything is 
working back as usual. I nearly boot onto live-cd and revert those packages, 
back to the old version but your mail really saves us this time!

-- 
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/16c0f48e-ff60-46a6-b06f-d0818d149889%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: ALL VMs are not working -- qmemman

2019-01-26 Thread Nick Darren 
On Saturday, January 26, 2019 at 9:49:54 PM UTC+8, Aly Abdellatif wrote:
> When I rebooted Qubes OS after installing i3. All VMs are not working(xfce or 
> i3) with the error
> 
> 
>  :Domain t has failed to start :Failed to connect to qmemman:[Errno 2] No 
> such file or directory
> 
> 

> with journalctl -xe ; I have this error : Failed to start Qubes memory 
> management daemon 
> 
> 
> systemctl start qubes-qmemman.service is not working with the error : 
> 
> Job for qubes-qmemman.service failed because the control process exited with 
> error code
> 
> Same with systemctl restart qubes-qmemman.service
> 
> And with ystemctl status qubes-qmemman.service : I have the same error with 
> the on in journalctl -xe
> 
> 
>  Failed to start Qubes memory management daemon
> 
> 
> 
> PS: I only edited the conf file in i3(everything was working) and I added in 
> /etc/systemd/system/ a file that call i3lock when suspending(this is when I 
> rebooted). I also deleted this file after having the error above but without 
> success.
> 
> Thanks in advance
> Aly Abdellatif

I have the same exact problems after booting qubes.

Before that I was upgrading these packages on dom0 before qubes-qmemman.service 
issue failed to start:

qubes-mgmt-salt-dom0-update-4.0.5-1.fc25.noarch
qubes-desktop-linux-manager-4.0.14-1.fc25.noarch
qubes-manager-4.0.26-1.fc25.noarch

@marek do you have any idea on this?

-- 
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/6ac9ed09-ae41-4484-8e64-6540c7cf546d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] updating CentOS-7 templates

2018-12-15 Thread Nick Darren 

On Thu, Dec 13, 2018 at 10:36:18AM +0100, Achim Patzner wrote:

Am Donnerstag, den 13.12.2018, 06:12 + schrieb Wynn Tseng:

Yes, mine happened too.

Post error log about /var/log/Xorg.0.log in centos-7 template.

In dom0, use sudo xl console (insert centos vmname here)to access
centos7 vm


I did that; that's why I know that there was X11 breakage.

So: Which packages (of the few millions) is the one to back out or what
would have to be added again?


Achim




I just downgrade these packages upgrade on centos-7, 
xorg-x11-server-{Xorg,common}-1.20.1 back to 
xorg-x11-server-{Xorg,common}-1.19.5 and now qubes-gui-agent seems 
working fine with it and I can use back my centos-7 as usual. Since 
yum info doesn't provides much what's behind the qubes-gui-agent xorg 
version range support like apt shows do, so not sure in what extend to 
see it as the future upgrade too!  New qubes-gui-agent is needed here 
before upgrade both `xorg-x11-server-*` packages on centos!


Hope this help!
 
-- 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/aeab7ef45df15fa767e04ce20dd81aecfd334856.camel%40noses.com.
For more options, visit https://groups.google.com/d/optout.


--

--
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/20181215180649.GA2790%40mutt.
For more options, visit https://groups.google.com/d/optout.


pgpgAy1vA4GgQ.pgp
Description: PGP signature

[qubes-users] Some Important Xenial templates repos unavailable inside sources.list

2017-04-12 Thread Nick Darren 
Hello,

If building xenial template using qubes-builder, I found that some
"important" repos from 'Ubuntu Update Repos' that includes both
`xenial-security` and `xenial-updates` went missing inside
`sources.list`. How comes it doesn't include both the repos by default?
There's no qubes-specific repo inside `sources.list.d` too. How it
supposed to fix the bugs (provided by ubuntu & qubes upstream) by using
this template without the important repos over there? By not using this
repos, how exactly you come up to handle with the outdated version of
software inside the template? How regularly you rebuild the template
alone (by not using these repos)?

cc: Unman

-- 
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/19ac5d41-539b-94f1-9acc-ee21ee2589cd%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: Annoying exit code error when deny using VM-Sudo

2017-03-20 Thread Nick Darren 
On 03/20/2017 04:51 AM, Nick Darren wrote:
> Hello,
>
> Is it normal when deny the root access using 'VM-Sudo' method with the
> leak message like below?
>
> $ su
> /usr/lib/qubes/qrexec-client-vm failed: exit code 1
> su: System error
>
> $ sudo su
> /usr/lib/qubes/qrexec-client-vm failed: exit code 1
> sudo: PAM authentication error: System error
>
>
> Is there any other way on how to prevent this leak message from happened
> (i.e. without any message appear on the tty instead)?
>
>
> Thank you.
>
>
>
>
>
>
Just figured it out myself by include `stdout` and `quiet` pam auth's
optionslike below did solved this issue.

/auth   [success=done default=die]  pam_exec.so seteuid stdout quiet
/usr/lib/qubes/qrexec-client-vm dom0 qubes.VMAuth /usr/bin/grep -q ^1$/

Case close.

-- 
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/2e6d084d-0bbd-fb5b-d0f2-2f2aa0b72ac7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Annoying exit code error when deny using VM-Sudo

2017-03-19 Thread Nick Darren 
Hello,

Is it normal when deny the root access using 'VM-Sudo' method with the
leak message like below?

$ su
/usr/lib/qubes/qrexec-client-vm failed: exit code 1
su: System error

$ sudo su
/usr/lib/qubes/qrexec-client-vm failed: exit code 1
sudo: PAM authentication error: System error


Is there any other way on how to prevent this leak message from happened
(i.e. without any message appear on the tty instead)?


Thank you.





-- 
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/65e1df5c-ed28-9393-2376-3b48fa9d870f%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Kicking the sudoers dead horse

2017-03-15 Thread Nick Darren 
On 03/15/2017 02:24 AM, Chris Laprise wrote:
> On 03/14/2017 07:18 PM, Chris Laprise wrote:
>>
>> # Protect sh and bash init files
>> chfiles="/home/user/.bashrc /home/user/.bash_profile /home/user \
>> /.bash_login /home/user/.bash_logout /home/user/.profile"
>> touch $chfiles
>> chown -f root:root $chfiles
>> chattr +i $chfiles
>
>
> The line break on that didn't work out (delete space before
> backslash). Here it is fixed:
>
> https://github.com/tasket/Qubes-VM-hardening/blob/master/rc.local
>
> Also changed to avoid abort of script.
>
Hi Chris,


How did you handle error message like below when you deny the request of
su/sudo using vm-sudo :

[user@fedora-24 pam.d]$ su
/usr/lib/qubes/qrexec-client-vm failed: exit code 1
su: System error

[user@fedora-24 pam.d]$ sudo dnf update
/usr/lib/qubes/qrexec-client-vm failed: exit code 1
sudo: PAM authentication error: System error


Is there any method to put something like 'permission denied' message
instead of the message above?

-- 
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/2f24304b-1584-66aa-7e77-8394d42824f4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] disp-vms were great - if they worked.

2017-03-13 Thread Nick Darren 
On 03/12/2017 10:47 PM, haaber wrote:
> The DispVM's make me crazy. Last week (with your generous help) finally
> dispVM with debian template worked. Now --without any change that I am
> aware of-- it does again not.  I tried to start it within dom0 - that
> way I get a max of error messages. ("the DVM savefile creation failed"
> is kind of unspecific).
>
>
> [me@dom0 ~]$ echo xterm | /usr/lib/qubes/qfile-daemon-dvm qubes.VMShell
> dom0 DEFAULT red
> time=1489389887.32, qfile-daemon-dvm init
> time=1489389887.32, creating DispVM
> Can't get domid of domain name 'debian-8', maybe this domain does not exist.
> --> Creating volatile image:
> /var/lib/qubes/appvms/debian-8-dvm/volatile.img...
> --> Loading the VM (type = AppVM)...
> Traceback (most recent call last):
>   File "/usr/bin/qvm-start", line 136, in 
> main()
>   File "/usr/bin/qvm-start", line 120, in main
> xid = vm.start(verbose=options.verbose,
> preparing_dvm=options.preparing_dvm, start_guid=not options.noguid,
> notify_function=tray_notify_generic if options.tray else None)
>   File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py",
> line 1942, in start
> self._update_libvirt_domain()
>   File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py",
> line 755, in _update_libvirt_domain
> raise e
> libvirt.libvirtError: operation failed: domain 'debian-8-dvm' already
> exists with uuid 603478e2-2d9f-4b27-c052-2910eaf6819b8
>
>
> So, once again, it is libvirt / virsh. But what is it this time?? Sigh
> of despair! Thank you for helping once more.
>
> Bernhard
>
in 'dom0', you can check it using:

$ virsh -c xen:/// list

then 'undefine' the dvm template as shown above and try again after that.

$ virsh -c xen:/// undefine debian-8-dvm

-- 
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/0c492d84-5f54-03ba-ff96-37d5def98085%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Error: Bad return status for module build on kernel: 4.9.0-2-amd64 (x86_64)

2017-03-12 Thread Nick Darren 
On 03/11/2017 03:29 PM, faber wrote:
> I'm trying to adopt the kernel image 4.9.0-2-amd64 on my Debian 9
> TemplateVM.
>
> After installing the image and its headers, I do the following command:
>
> --
> sudo dkms autoinstall -k 4.9.0-2-amd64
> --
>
> And get the following output:
>
>
> -
> Kernel preparation unnecessary for this kernel.  Skipping...
>
> Building module:
> cleaning build area...
> make -j2 KERNELRELEASE=4.9.0-2-amd64 KVERSION=4.9.0-2-amd64...(bad exit
> status: 2)
> Error! Bad return status for module build on kernel: 4.9.0-2-amd64 (x86_64)
> Consult /var/lib/dkms/digimend/6/build/make.log for more information.
>
> Kernel preparation unnecessary for this kernel.  Skipping...
>
> Building module:
> cleaning build area...
> make -j2 KERNELRELEASE=4.9.0-2-amd64 -C /lib/modules/4.9.0-2-amd64/build
> M=/var/lib/dkms/u2mfn/3.2.3/build...(bad exit status: 2)
> Error! Bad return status for module build on kernel: 4.9.0-2-amd64 (x86_64)
> Consult /var/lib/dkms/u2mfn/3.2.3/build/make.log for more information.
> -
>
>
>
> And the output of /var/lib/dkms/u2mfn/3.2.3/build/make.log is:
>
>
> -
> DKMS make.log for u2mfn-3.2.3 for kernel 4.9.0-2-amd64 (x86_64)
> Sat Mar 11 16:13:29 CET 2017
> make: Entering directory '/usr/src/linux-headers-4.9.0-2-amd64'
>   LD  /var/lib/dkms/u2mfn/3.2.3/build/built-in.o
>   CC [M]  /var/lib/dkms/u2mfn/3.2.3/build/u2mfn.o
> /var/lib/dkms/u2mfn/3.2.3/build/u2mfn.c: In function ‘u2mfn_ioctl’:
> /var/lib/dkms/u2mfn/3.2.3/build/u2mfn.c:80:23: error: passing argument 5
> of ‘get_user_pages’ from incompatible pointer type
> [-Werror=incompatible-pointer-types]
>(data, 1, 1, 0, _page, 0);
>^
> In file included from /var/lib/dkms/u2mfn/3.2.3/build/u2mfn.c:26:0:
> /usr/src/linux-headers-4.9.0-2-common/include/linux/mm.h:1302:6: note:
> expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’
>  long get_user_pages(unsigned long start, unsigned long nr_pages,
>   ^~
> /var/lib/dkms/u2mfn/3.2.3/build/u2mfn.c:79:9: error: too many arguments
> to function ‘get_user_pages’
>ret = get_user_pages
>  ^~
> In file included from /var/lib/dkms/u2mfn/3.2.3/build/u2mfn.c:26:0:
> /usr/src/linux-headers-4.9.0-2-common/include/linux/mm.h:1302:6: note:
> declared here
>  long get_user_pages(unsigned long start, unsigned long nr_pages,
>   ^~
> cc1: some warnings being treated as errors
> /usr/src/linux-headers-4.9.0-2-common/scripts/Makefile.build:304: recipe
> for target '/var/lib/dkms/u2mfn/3.2.3/build/u2mfn.o' failed
> make[3]: *** [/var/lib/dkms/u2mfn/3.2.3/build/u2mfn.o] Error 1
> /usr/src/linux-headers-4.9.0-2-common/Makefile:1507: recipe for target
> '_module_/var/lib/dkms/u2mfn/3.2.3/build' failed
> make[2]: *** [_module_/var/lib/dkms/u2mfn/3.2.3/build] Error 2
> Makefile:150: recipe for target 'sub-make' failed
> make[1]: *** [sub-make] Error 2
> Makefile:8: recipe for target 'all' failed
> make: *** [all] Error 2
> make: Leaving directory '/usr/src/linux-headers-4.9.0-2-amd64'
> -
>
>
>
> Any idea?
>
> Thanks in advance
>

This has happened because 'qubes-kernel-vm-support' package using the
outdated 'u2mfn.c'.

Refer to this issue: https://github.com/QubesOS/qubes-issues/issues/2691

At the moment, you can simply fix this by copy the updated 'u2mfn.c' and
replace your old one here:
https://github.com/QubesOS/qubes-linux-utils/blob/master/kernel-modules/u2mfn/u2mfn.c

or just edit your 'u2mfn.c' and add the related lines from here:
https://github.com/QubesOS/qubes-linux-utils/commit/e01745f66fd2b4b0035ce7e064f340faeb997675

Hope this help :)


-- 
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/f12b162b-4826-1e9e-1bf5-b01005fe35d9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] How to manage shortcuts to applications in DispVM?

2017-02-23 Thread Nick Darren 
On 02/23/2017 12:56 PM, Unman wrote:
> On Wed, Feb 22, 2017 at 08:55:23PM -0800, Andrew David Wong wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> On 2017-02-17 16:54, Unman wrote:
>>> On Sat, Feb 18, 2017 at 12:14:52AM +0100, u+q...@bestemt.no wrote:
 hawk...@bitmessage.ch  [2017-02-17 22:10
 +0100]:
> You could add a new "launcher" button to the XFCE panel, and
> for it's execute command, follow this example for the tor
> browser (under section: How to use Tor Browser behind TorVM),
> but other applications should work in the same way: 
> https://www.qubes-os.org/doc/torvm/
 Thanks, but I don't see how something similar can be accomplished
 in i3, which I'm using.
>>> Well you haven't said how you intend to add launcher commands to
>>> your i3. What HawKing has shown you is a template for the command
>>> that you need to run in dom0 to launch programs in a dispVM: "echo
>>>  | /usr/lib/qubes/qfile-daemon-dvm qubes.VMShell dom0
>>> DEFAULT red"
>>>
>>> You could create desktop files based on the existing ones that you
>>> will find in /usr/local/share/applications
>>>
>> I just tried creating some additional desktop files in this manner,
>> but I see no changes (no option to add additional menu entries or
>> launcher entries) even after regenerating the DVM Template. How is
>> this supposed to work?
>>
>> - -- 
>> Andrew David Wong (Axon)
>> Community Manager, Qubes OS
>> https://www.qubes-os.org
> The "DisposableVM" entries in the xfce menus are sourced from
> /etc/xdg/menus/applications-merged/qubes-dispvm.menu
>
> Create the desktop file in /usr/local/share/applications
> Then reference it in the qubes-dispvm.menu file.
> The launcher will appear on the menu.
>

Thanks unman. This is what I looking for. I've tried to generate
`xdg-desktop-menu`. But doesn't seems working before.  After the
modification on 'qubes-dispvm.menu', now I can see my custom menu on
XFCE. :-)

-- 
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/950c67e5-00dd-75c1-6f85-0dd29fbc434e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Update killed Debian 9 / Kali template. Can't open terminal. What now?

2017-02-22 Thread Nick Darren 
On 02/22/2017 03:32 PM, georgewalke...@gmail.com wrote:
> Hi Qubes gurus,
>
> I was updating my templates today, which seemed to go fine, until I realized 
> that the Debian 9 + Katoolin VM I made per the instructions on the wiki is 
> now non-responsive: I can't run the updater or even open a terminal.
>
> Has this happened to anyone else?  Any fallback remediation strategies I 
> should try?
>
> Unfortunately, since I was trying to update everything at once, I can't 
> pinpoint whether the issue was a botched update on the Kali template or a 
> result of updating Dom-0.
>
>
> Best,
> George
>

What I did before upgrading debian 9 + kali (katoolin) template was
first comment (#) the 'sources.list' on kali repository address, then
look for qubes-r3.list and uncomment Qubes updates candidates
repository. Then I did `sudo apt upgrade -t stretch-testing`. It will
upgrade the debian-9 first. After everything is done, then I will
uncomment kali repository address and do upgrade the rest. This save my
ass everytime, especially if anything related to 'qubes-gui-agent'
towards xorg-server, pulseaudio etc stuff.

What you can do now  to revert everything you have done is to restore
the template backup. If you don't have that, you need to clone back the
debian-9 template and install katoolin like what you did before. Hope
this help.

-- 
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/869b185e-36fb-0a9a-28b9-76359d740ea7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Archlinux template system update

2017-02-20 Thread Nick Darren 
On February 21, 2017 12:05:00 PM GMT+08:00, loke...@gmail.com wrote:
>On Tuesday, 21 February 2017 02:25:25 UTC+8, Francesco  wrote:
>
>> I wonder if am the only one with this issue.
>
>You're not the only one. I have it too and I haven't been able to get
>past it. It happens immediately when trying to upgrade the standard
>Arch template.


This kind of problem can be avoid if you have the latest  'qubes-vm-gui' binary 
installed before the upgrade happened.

 I wonder why someone didn't put it on the AUR at least or somewhere else as 
3rd party addon repo for archlinux template. 

So, you don't need to recompile the template again and again for the same 
problem. 

Latest "qubes-vm-gui"  dependency changed to pulseaudio>=10.0 pulseaudio<11.0 
xorg-server>=1.19.0 xorg-server<1.20.0.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/B390B950-7DC6-4747-A3EA-DDFD3741EA76%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] NO SOUND after debian 9 (stretch) upgrade + workaround

2017-02-11 Thread Nick Darren 
Hi,


I wonder if anyone using debian 9 upgrade recently facing the same
problem. Luckily, I have the template backup before doing this major
upgrade on stretch.

Upgrading the template by 'apt upgrade -t stretch-testing' to enable
latest qubes candidates to grab latest 'qubes-gui-agent' doesn't solve
this issue yet.

ii  libpulse-mainloop-glib0:amd64 
10.0-1   amd64PulseAudio client
libraries (glib support)
ii  libpulse0:amd64   
10.0-1   amd64PulseAudio client
libraries
ii  libpulsedsp:amd64 
10.0-1   amd64PulseAudio OSS
pre-load library
ii  pulseaudio
10.0-1   amd64PulseAudio sound server
ii  pulseaudio-utils  
10.0-1   amd64Command line tools for
the PulseAudio sound server

PulseAudio daemon failed to start after this major upgrade.

E: [pulseaudio] main.c: Daemon startup failed.


So, right now I will hold the old 'pulseaudio 9.0' package until Marek
push the right tools on stretch-testing repo.

--



I have found the solution for this after looking around at 'qubes-gui-agent' 
source code. It seems that 'module-vchan-sink.so' doesn't appeared on 
'/usr/lib/pulse-10.0/modules/' after upgrading pulseaudio 10 on Debian 9.

What I did was just copying the module to the right directory. After that 
starting back the PulseAudio daemon and it's working as usual. Until the new 
'qubes-gui-agent' available on the 'stretch-testing' repo. I think this method 
will just work for me right now. Hope this help everyone who got the same issue 
like above.


-- 
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/d359cb50-0f17-f513-dabb-1911d2738d1d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] No SOUND after debian 9 (stretch) upgrade

2017-02-11 Thread Nick Darren 
Hi,


I wonder if anyone using debian 9 upgrade recently facing the same
problem. Luckily, I have the template backup before doing this major
upgrade on stretch.

Upgrading the template by 'apt upgrade -t stretch-testing' to enable
latest qubes candidates to grab latest 'qubes-core-agent' doesn't solve
this issue yet.

ii  libpulse-mainloop-glib0:amd64 
10.0-1   amd64PulseAudio client
libraries (glib support)
ii  libpulse0:amd64   
10.0-1   amd64PulseAudio client
libraries
ii  libpulsedsp:amd64 
10.0-1   amd64PulseAudio OSS
pre-load library
ii  pulseaudio
10.0-1   amd64PulseAudio sound server
ii  pulseaudio-utils  
10.0-1   amd64Command line tools for
the PulseAudio sound server

PulseAudio daemon failed to start after this major upgrade.

E: [pulseaudio] main.c: Daemon startup failed.


So, right now I will hold the old 'pulseaudio 9.0' package until Marek
push the right tools on stretch-testing repo.



-- 
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/d0ed30b5-d32a-1ac6-1d6b-bdb4320a8e0e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] ubuntu template

2017-02-10 Thread Nick Darren 


On 02/10/2017 09:46 AM, trul...@gmail.com wrote:
> четверг, 9 февраля 2017 г., 14:41:42 UTC+3 пользователь Unman написал:
>> On Thu, Feb 09, 2017 at 02:37:36AM -0800, damien.wa...@gmail.com wrote:
>>> Hi,
>>>
>>> I am new into qubes (few months) and find it great. But I need a distro 
>>> with newer packages (debian jessie was fine until I ran in issues with 
>>> encfs compatibility).
>>>
>>> So I wanted to build an ubuntu template but I did not found clear 
>>> instructions.
>>>
>>> using https://github.com/QubesOS/qubes-builder and the setup script, I do 
>>> not get ubuntu to choose in the menu.
>>>
>>> On this forum, there is few posts about it but using privaze repo.
>>>
>>> I really need help on this :-)
>>>
>>> Best regards,
>>>
>>> Damien
>>>
>> Hi Damien,
>>
>> The Ubuntu builds are referenced in setup as Trusty and Xenial.
>>
>> I've just put in a series of Pull Requests that should allow
>> straightforward builds of both.
>> Wait a little while for them to be merged. 
>>
>> It should then be a matter of:
>> git clone  https://github.com/QubesOS/qubes-builder
>> cd qubes-builder
>> ./setup
>> make qubes-vm
>> make template
>>
>> Copy generated Template to dom0 and install - there's a handy script
>> provided to do this for you.
>>
>> I'll let you know when the PRs are merged. Focus at the moment is on
>> the GSOC applications.
>>
>> unman
> Unman can you make a template rpm Ubuntu and put it on
>
> https://ftp.qubes-os.org/repo/yum/r3.2/templates-community/rpm/ ?:)
>
> Trying qubes-builder with trusty, xenial, xenial-desktop and no success. 
> Everytime troubles with MAKE. 
>
> qvm clone fedora-23 ubuntu
> grow to 25 GB, allow network
> yum install git createrepo rpm-build rpm-sign make python-sh rpmdevtools 
> rpm-sign dialog
> git clone  https://github.com/QubesOS/qubes-builder
> cd qubes-builder
> ./setup 
>
> Choosing fedora23 and mgmt-salt, then Ubuntu Xenial. 
>
> make get-sources
> make install-deps
>
> And finally make qubes-vm can't build template
>
> "Building packages not supported by any configured plugins"
>
> It means that need to use debian-8 template for builder?
>
Hi,

You need debian-builder instead of fedora in the first step of `setup`,
because ubuntu is based on debian. This is mandatory to build any
debian-based operating system.

To skip unnecessary setup to use only for making ubuntu template, first 
edit the ‘qubes-os-r3.2.conf’ (if you use r3.2 in this case) which is
found in /home/user/qubes-builder/example-configs. Use the text editor
of your choice.

Go to the first line containing ‘DISTS_VM ?= fc23’  Remove ‘fc23’ or
whatever is listed there leaving only ‘DISTS_VM ?=’. Then save the file
and close the text editor.

Run the 'setup' script located in ‘/home/user/qubes-builder/’ Make sure
you are in directory ‘qubes-builder’.

$ cd /home/user/qubes-builder/
$ ./setup

Deselect 'builder-fedora'
Select 'builder-debian'

On 'Template Distribution Selection':
Select xenial+desktop

Proceed others as per instructions.


To check build-logs in progress later you can use `tail -f` command in
between the *.log locations.

-- 
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/768a27ed-a609-f187-0485-a239bddfba11%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Copy/Paste images

2017-02-08 Thread Nick Darren 


On 02/08/2017 07:49 PM, Patrick Bouldin wrote:
> On Wednesday, February 8, 2017 at 1:47:11 PM UTC-5, Francesco wrote:
>> On Wed, Feb 8, 2017 at 3:41 PM, Franz <169...@gmail.com> wrote:
>>
>>
>>
>>
>>
>> On Wed, Feb 8, 2017 at 2:49 PM, Patrick Bouldin  
>> wrote:
>> Thank you but I'm pretty new with Linux. Do I add this as a script in dom0? 
>> How would I invoke it after a screenshot? Can you please provide full 
>> context on how to use this?
>>
>>
>>
>>
>>
>> ok. you have to create a file called for example snapshot.sh where you write 
>> the above. For doing that I use:
>>
>> vim snapshot.sh
>>
>> then digit "i"  that allows me to insert the above text
>>
>> at the end ":x" to save
>>
>>
>> after that 
>> sh snapshot.sh to execute
>>
>> good luck
>>
>> Fran  
>>
>>
>>
>> If it works you'll find the pictures in Qubesincoming/Domo fold of the VM 
>> you selected
>>
>>
>> Also please do not top post
>>
>>
>>
>>
>>
>>
>>
>>
>> On Wednesday, February 8, 2017 at 12:45:53 PM UTC-5, Francesco wrote:
>>
>>> I have it muy simple:
>>> echo "digit name of the VM to which send snapshots"
>>> read nameVM
>>> qvm-copy-to-vm $nameVM ~/Pictures/
>>> rm ~/Pictures/*.*
>>> but you can use only the last but one line if you want it even simplier. 
>>> The other lines are only to speed it up.
>>> Best
>>> Fran
>>> On Wed, Feb 8, 2017 at 2:30 PM, Patrick Bouldin  
>>> wrote:
>>> Hi everyone,
>>> One important thing that really keeps me back from totally converting to 
>>> qubes is the inability to create documents with screenshots. On a windows 
>>> pc I can of course do a screen print, then quickly crop the image and paste 
>>> it right in a document.
>>> This seems extremely difficult in qubes. I do see someone created some 
>>> image copy/paste between domains here: 
>>> http://jrruethe.github.io/blog/2015/09/17/screenshots-in-qubes/
>>> Am I missing something basic or will I need to do something like that?
>>> Thanks,
>>> Patrick
>>> --
>>> 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...@googlegroups.com.
>>> To post to this group, send email to qubes...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/qubes-users/dd2a1ce9-f912-41bb-a1f1-7f30cbef3003%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>>
>> 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...@googlegroups.com.
>>
>> To post to this group, send email to qubes...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/qubes-users/5611a751-42e6-426b-90e5-f0a32e9bfb2c%40googlegroups.com.
>>
>>
>>
>> For more options, visit https://groups.google.com/d/optout.
> Sorry for the top post, I knew better! :)  
>
> Ok, I think I am almost there. I am still confused on how the shellscript is 
> invoked. Do I create a shortcut that activates this? Once I have the shell 
> script in dom0, how do I invoke it from a screen print?
>
> Thanks,
> Patrick
>
Instead of using this script you can just use `scrot` command from dom0.
You need to download it first from qubes-dom0-update --action=install
scrot. It's easy to use, refer to `scrot --help` for clue from your dom0
after install. Then you can transfer the image to appvm by using
qvm-copy-to-vm or qvm-move-to-vm command.

Another good alternative I found was
https://github.com/evadogstar/qvm-screenshot-tool. Easy to use with GUI
and transfer screenshot to imgur service too!

-- 
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/43f7bad8-bd72-801e-9a1e-b8536bc54114%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: Workaround for building Ubuntu xenial+desktop with qubes-builder

2017-02-04 Thread Nick Darren 


On 02/04/2017 05:12 AM, anoa wrote:
> On 02/03/2017 08:41 AM, Unman wrote:
>> On Fri, Feb 03, 2017 at 06:21:15AM +0000, Nick Darren wrote:
>>>
>>> On 02/02/2017 12:07 AM, Unman wrote:
>>>> On Mon, Jan 30, 2017 at 11:00:41AM -0800, Andrew M wrote:
>>>>> Thanks Unman,
>>>>>
>>>>> This bug is currently affecting my work so it would be greatly
>>>>> appreciated if it were resolved :)
>>>>>
>>>>>
>>>>> On 01/29/2017 06:38 PM, Unman wrote:
>>>>>> On Sat, Jan 28, 2017 at 12:31:38PM +, Nick Darren wrote:
>>>>>>> /Hi all,/
>>>>>>>
>>>>>>>
>>>>>>> On 01/24/2017 06:59 AM, anoa wrote:
>>>>>>>> Hey all,
>>>>>>>>
>>>>>>>> Today I was trying to build the Ubuntu 16.04 Xenial+Desktop template
>>>>>>>> using qubes-builder with help from these instructions:
>>>>>>>>
>>>>>>>> https://github.com/QubesOS/qubes-builder
>>>>>>>>
>>>>>>>> Everything was alright until the `make qubes-vm` step where it would
>>>>>>>> fail on the following:
>>>>>>>>
>>>>>>>>> dpkg-source: error: can't build with source format '3.0 (quilt)': no 
>>>>>>>>> upstream tarball found at ../xen_4.6.3.orig.tar.{bz2,gz,lzma,xz}
>>>>>>>>> dpkg-buildpackage: error: dpkg-source -b debian-vm gave error exit 
>>>>>>>>> status 255
>>>>>>>>> /home/user/qubes-builder/qubes-src/builder-debian/Makefile.qubuntu:196:
>>>>>>>>>  recipe for target 'dist-package' failed
>>>>>>>> The build was looking for xen_4.6.3 when in fact xen_4.6.4 is in the
>>>>>>>> folder. As a workaround, simply copying the xen_4.6.4 to be named
>>>>>>>> xen.4.6.3 allowed the build to continue and eventually complete
>>>>>>>> successfully:
>>>>>>>>
>>>>>>>>> cd /path/to/qubes-builder/chroot-xenial/home/user/qubes-src/vmm-xen; 
>>>>>>>>> sudo cp -pr ./xen_4.6.4.orig.tar.gz ./xen_4.6.3.orig.tar.gz
>>>>>>> /It doesn't work by just rename the 'xen_4.6.4.orig.tar.gz' on
>>>>>>> chroot-xenial. On my case (on testing to build xenial-desktop) needs to
>>>>>>> copy the file to /path/to/qubes-builder/qubes-src/vmm-xen/. there. Then,
>>>>>>> it will skip the error message and allowed the build successfully./
>>>>>>>
>>>>>>>> Hope this helps someone while the script is being updated.
>>>>>>>>
>>>>>>> /I have another weird situation. The build was succeed but the problem
>>>>>>> is, terminal and some others application cannot be launched due to an
>>>>>>> error, normally on ubuntu's standard installation caused by locales
>>>>>>> issue. Tried to fix it the way it used to be on normal ubuntu
>>>>>>> installation or archlinux. But the problem still persists after
>>>>>>> rebooting the template-vm or any appvms that's based on it./
>>>>>>>
>>>>>>> user@ubuntu-xenial:~$ Error constructing proxy for
>>>>>>> org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling
>>>>>>> StartServiceByName for org.gnome.Terminal:
>>>>>>> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process
>>>>>>> org.gnome.Terminal received signal 5
>>>>>>>
>>>>>>> /Test on executing gedit from xterm/UXterm/urvtx:/
>>>>>>>
>>>>>>> user@ubuntu-xenial:~$ gedit
>>>>>>> Gedit failure to execute.
>>>>>>> (gedit:5697): GLib-GIO-ERROR **: No GSettings schemas are installed on
>>>>>>> the system
>>>>>>> Trace/breakpoint trap (core dumped)
>>>>>>>
>>>>>>>
>>>>>>> /The same error happen when I execute the 'xfce4-terminal' or
>>>>>>> 'terminator'. Still the same 'Trace/breakpoint trap (core dumped)'
>>>>>>> issues here and there./
>>>>>>>
>>>>>>>
>>>>>>> 
>>>>>>>
>&

Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder

2017-02-02 Thread Nick Darren 


On 02/02/2017 12:07 AM, Unman wrote:
> On Mon, Jan 30, 2017 at 11:00:41AM -0800, Andrew M wrote:
>> Thanks Unman,
>>
>> This bug is currently affecting my work so it would be greatly
>> appreciated if it were resolved :)
>>
>>
>> On 01/29/2017 06:38 PM, Unman wrote:
>>> On Sat, Jan 28, 2017 at 12:31:38PM +, Nick Darren wrote:
>>>> /Hi all,/
>>>>
>>>>
>>>> On 01/24/2017 06:59 AM, anoa wrote:
>>>>> Hey all,
>>>>>
>>>>> Today I was trying to build the Ubuntu 16.04 Xenial+Desktop template
>>>>> using qubes-builder with help from these instructions:
>>>>>
>>>>> https://github.com/QubesOS/qubes-builder
>>>>>
>>>>> Everything was alright until the `make qubes-vm` step where it would
>>>>> fail on the following:
>>>>>
>>>>>> dpkg-source: error: can't build with source format '3.0 (quilt)': no 
>>>>>> upstream tarball found at ../xen_4.6.3.orig.tar.{bz2,gz,lzma,xz}
>>>>>> dpkg-buildpackage: error: dpkg-source -b debian-vm gave error exit 
>>>>>> status 255
>>>>>> /home/user/qubes-builder/qubes-src/builder-debian/Makefile.qubuntu:196: 
>>>>>> recipe for target 'dist-package' failed
>>>>> The build was looking for xen_4.6.3 when in fact xen_4.6.4 is in the
>>>>> folder. As a workaround, simply copying the xen_4.6.4 to be named
>>>>> xen.4.6.3 allowed the build to continue and eventually complete
>>>>> successfully:
>>>>>
>>>>>> cd /path/to/qubes-builder/chroot-xenial/home/user/qubes-src/vmm-xen; 
>>>>>> sudo cp -pr ./xen_4.6.4.orig.tar.gz ./xen_4.6.3.orig.tar.gz
>>>> /It doesn't work by just rename the 'xen_4.6.4.orig.tar.gz' on
>>>> chroot-xenial. On my case (on testing to build xenial-desktop) needs to
>>>> copy the file to /path/to/qubes-builder/qubes-src/vmm-xen/. there. Then,
>>>> it will skip the error message and allowed the build successfully./
>>>>
>>>>> Hope this helps someone while the script is being updated.
>>>>>
>>>> /I have another weird situation. The build was succeed but the problem
>>>> is, terminal and some others application cannot be launched due to an
>>>> error, normally on ubuntu's standard installation caused by locales
>>>> issue. Tried to fix it the way it used to be on normal ubuntu
>>>> installation or archlinux. But the problem still persists after
>>>> rebooting the template-vm or any appvms that's based on it./
>>>>
>>>> user@ubuntu-xenial:~$ Error constructing proxy for
>>>> org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling
>>>> StartServiceByName for org.gnome.Terminal:
>>>> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process
>>>> org.gnome.Terminal received signal 5
>>>>
>>>> /Test on executing gedit from xterm/UXterm/urvtx:/
>>>>
>>>> user@ubuntu-xenial:~$ gedit
>>>> Gedit failure to execute.
>>>> (gedit:5697): GLib-GIO-ERROR **: No GSettings schemas are installed on
>>>> the system
>>>> Trace/breakpoint trap (core dumped)
>>>>
>>>>
>>>> /The same error happen when I execute the 'xfce4-terminal' or
>>>> 'terminator'. Still the same 'Trace/breakpoint trap (core dumped)'
>>>> issues here and there./
>>>>
>>>>
>>>> 
>>>>
>>>> /Locale was set in order to avoid gnome-terminal error, but it' useless
>>>> on this case and still failed to work./
>>>>
>>>> user@ubuntu-xenial:~$ localectl
>>>>System Locale: LANG=en_US.UTF-8
>>>>VC Keymap: us
>>>>   X11 Layout: us
>>>>X11 Model: pc105+inet
>>>>  X11 Options: terminate:ctrl_alt_bksp
>>>>
>>>> 
>>>>
>>>> /On checking qubes local packages installed on the 'xenial-desktop' system.
>>>> /
>>>> libqubes-rpc-filecopy2/now 3.2.3+xenialu1 amd64 [installed,local]
>>>>   Qubes file copy protocol library
>>>>
>>>> libqubesdb/now 3.2.3-1+xenialu1 amd64 [installed,local]
>>>>   QubesDB libs.
>>>>
>>>> libvchan-xen/now 3.2.0-1+xenialu1 amd64 [installed,local]
>>>>   Qubes Xen core libraries
>>>>
>>>>

Re: [qubes-users] Fedora 25

2017-01-30 Thread Nick Darren 


On 01/30/2017 07:06 PM, Foppe de Haan wrote:
> On Monday, January 30, 2017 at 1:46:33 PM UTC+1, Connor Page wrote:
>> I guess qubes tools need to be recompiled against new libraries but 
>> userspace pulseaudio version is not a problem.
> updated version is in current-testing.
>
pulseaudio latest issues were fixed after upgraded from qubes vm testing
repo, but mesa packages cannot be upgraded still. It's ignored in this case.

Skipping packages with broken dependencies:
 mesa-libEGL  x86_6413.0.3-4.fc25 
updates103 k
 mesa-libGL   x86_6413.0.3-4.fc25 
updates164 k
 mesa-libGLES x86_6413.0.3-4.fc25 
updates 21 k
 mesa-libglapix86_6413.0.3-4.fc25 
updates 49 k

-- 
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/074e73db-6d37-0732-18e7-e868fe5fc546%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder

2017-01-28 Thread Nick Darren 


On 01/28/2017 12:39 PM, Andrew Morgan wrote:
> Yes I do have the same issue.
>
> It seems it was mentioned a few times on the mailing lists but no concrete 
> solutions were found. People suggested a magic bullet being this command:
>
> sudo dpkg-reconfigure locales
>
> However this command exits prematurely due to the localesall (sp?) package 
> being installed. Some of qubes' scripts/binaries depend on this package, so a 
> removal will render your VM unusable.
>
> Could this hard dependency be removed? Do we really need localesall? Will 
> this even fix it if we do remove it and generate the locales successfully?

Weird thing is when I execute 'sudo gnome-terminal' or 'sudo gedit',
it's working fine there in my case.

I've been trying to replace locales & locales-all default packages with
debian-8 (jessie) & debian-9 (stretch) on my testing ubuntu-template  to
test if it's working. Not the right way to do that for sure, it's a
dependency hell at the end. Still figure out on how to fix that.

I don't think that locales & locales-all were the main culprits here. I
can still using gnome-terminal when I sudo it.

-- 
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/a0849d2a-7c72-66ec-15ee-9ae76295b1b3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


0x4B6E850C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Qubes-Builder - Rackspace mirror having issues?

2017-01-28 Thread Nick Darren 


On 01/26/2017 11:48 PM, anoa wrote:
> I'm currently trying to build the Arch Linux template through
> qubes-builder. Someway through the `make qubes-vm` step I'm getting
> 404/403 errors on the default mirror.rackspace.com server.
>
> Checking it in a browser at mirror.rackspace.com loads and their status
> page (status.rackspace.com) reports no issues.
>
> Here is the relevant output of the build:
>
> ```
> Packages (5) gnupg-2.1.18-1  gtk-update-icon-cache-3.22.7-2
> gtk3-3.22.7-2  libproxy-0.4.13-2  pango-1.40.3-2
>
> Total Download Size:   10.74 MiB
> Total Installed Size:  83.59 MiB
> Net Upgrade Size:   1.16 MiB
>
> :: Proceed with installation? [Y/n]
> :: Retrieving packages...
> error: failed retrieving file
> 'gtk-update-icon-cache-3.22.7-2-x86_64.pkg.tar.xz' from
> mirror.rackspace.com : The requested URL returned error: 404
> warning: failed to retrieve some files
> error: failed retrieving file 'pango-1.40.3-2-x86_64.pkg.tar.xz' from
> mirror.rackspace.com : The requested URL returned error: 404
> warning: failed to retrieve some files
> error: failed retrieving file 'gtk3-3.22.7-2-x86_64.pkg.tar.xz' from
> mirror.rackspace.com : The requested URL returned error: 404
> warning: failed to retrieve some files
> error: failed retrieving file 'libproxy-0.4.13-2-x86_64.pkg.tar.xz' from
> mirror.rackspace.com : The requested URL returned error: 404
> warning: failed to retrieve some files
> error: failed to commit transaction (unexpected error)
> Errors occurred, no packages were upgraded.
> /home/user/qubes-builder/qubes-src/builder-archlinux/Makefile.archlinux:114:
> recipe for target 'dist-build-dep' failed
> make[2]: *** [dist-build-dep] Error 1
> Makefile.generic:139: recipe for target 'packages' failed
> make[1]: *** [packages] Error 1
> Makefile:209: recipe for target 'vmm-xen-vm' failed
> make: *** [vmm-xen-vm] Error 1
> user@dev:~/qubes-builder$
> ```
>
> Am I missing something?
>
> Thanks
> Andrew
>

If it doesn't work for you then you can just chroot to the directory and
change the default repository address to something else according to
/etc/pacman.d/mirrorlist and just edit /etc/pacman.conf to anything you
like based on the mirrorlist. Hope this help you.



-- 
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/fdb44539-703d-2fc1-daf7-6e15cfe82b01%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder

2017-01-28 Thread Nick Darren 
/Hi all,/


On 01/24/2017 06:59 AM, anoa wrote:
> Hey all,
>
> Today I was trying to build the Ubuntu 16.04 Xenial+Desktop template
> using qubes-builder with help from these instructions:
>
> https://github.com/QubesOS/qubes-builder
>
> Everything was alright until the `make qubes-vm` step where it would
> fail on the following:
>
>> dpkg-source: error: can't build with source format '3.0 (quilt)': no 
>> upstream tarball found at ../xen_4.6.3.orig.tar.{bz2,gz,lzma,xz}
>> dpkg-buildpackage: error: dpkg-source -b debian-vm gave error exit status 255
>> /home/user/qubes-builder/qubes-src/builder-debian/Makefile.qubuntu:196: 
>> recipe for target 'dist-package' failed
> The build was looking for xen_4.6.3 when in fact xen_4.6.4 is in the
> folder. As a workaround, simply copying the xen_4.6.4 to be named
> xen.4.6.3 allowed the build to continue and eventually complete
> successfully:
>
>> cd /path/to/qubes-builder/chroot-xenial/home/user/qubes-src/vmm-xen; sudo cp 
>> -pr ./xen_4.6.4.orig.tar.gz ./xen_4.6.3.orig.tar.gz

/It doesn't work by just rename the 'xen_4.6.4.orig.tar.gz' on
chroot-xenial. On my case (on testing to build xenial-desktop) needs to
copy the file to /path/to/qubes-builder/qubes-src/vmm-xen/. there. Then,
it will skip the error message and allowed the build successfully./

> Hope this helps someone while the script is being updated.
>

/I have another weird situation. The build was succeed but the problem
is, terminal and some others application cannot be launched due to an
error, normally on ubuntu's standard installation caused by locales
issue. Tried to fix it the way it used to be on normal ubuntu
installation or archlinux. But the problem still persists after
rebooting the template-vm or any appvms that's based on it./

user@ubuntu-xenial:~$ Error constructing proxy for
org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling
StartServiceByName for org.gnome.Terminal:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process
org.gnome.Terminal received signal 5

/Test on executing gedit from xterm/UXterm/urvtx:/

user@ubuntu-xenial:~$ gedit
Gedit failure to execute.
(gedit:5697): GLib-GIO-ERROR **: No GSettings schemas are installed on
the system
Trace/breakpoint trap (core dumped)


/The same error happen when I execute the 'xfce4-terminal' or
'terminator'. Still the same 'Trace/breakpoint trap (core dumped)'
issues here and there./




/Locale was set in order to avoid gnome-terminal error, but it' useless
on this case and still failed to work./

user@ubuntu-xenial:~$ localectl
   System Locale: LANG=en_US.UTF-8
   VC Keymap: us
  X11 Layout: us
   X11 Model: pc105+inet
 X11 Options: terminate:ctrl_alt_bksp



/On checking qubes local packages installed on the 'xenial-desktop' system.

/
libqubes-rpc-filecopy2/now 3.2.3+xenialu1 amd64 [installed,local]
  Qubes file copy protocol library

libqubesdb/now 3.2.3-1+xenialu1 amd64 [installed,local]
  QubesDB libs.

libvchan-xen/now 3.2.0-1+xenialu1 amd64 [installed,local]
  Qubes Xen core libraries

libxen-4.6/now 2001:4.6.3-25+xenialu1 amd64 [installed,local]
  Libraries for Xen tools

qubes-core-agent/now 3.2.15-1+xenialu1 amd64 [installed,local]
  Qubes core agent

qubes-gui-agent/now 3.2.13-1+xenialu1 amd64 [installed,local]
  Makes X11 windows available to qubes dom0

qubes-utils/now 3.2.3+xenialu1 amd64 [installed,local]
  Qubes Linux utilities

qubesdb/now 3.2.3-1+xenialu1 amd64 [installed,local]
  QubesDB management tools and daemon.

qubesdb-vm/now 3.2.3-1+xenialu1 amd64 [installed,local]
  QubesDB VM service.

xserver-xorg-input-qubes/now 3.2.13-1+xenialu1 amd64 [installed,local]
  X input driver for injecting events from qubes-gui-agent

xserver-xorg-video-dummyqbs/now 3.2.13-1+xenialu1 amd64 [installed,local]
  Dummy X video driver for qubes-gui-agent

--

/So, I would like to know if there's any errors like above happened to
you guys too? Or is it me the only person? If it was just me facing the
issues, then I would like to know if any missing qubes packaged that's
not listed on my side shown like above? You can just check your qubes
packages to confirm if any difference spotted on your side by apt search
qubes or dpkg-query -l | grep qubes.//Any help will be appreciated to
spot where the culprits are.
//

//Thanks./

-- 
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/6629980c-d544-c63e-4751-d55dcd8f3d26%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


0x4B6E850C.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

[qubes-users] Latest qubes-template-archlinux xorg-server package breaks pacman update completely

2017-01-15 Thread Nick Darren 
Hello,


As the title said, the latest xorg-server version (1.19.1-1) on Arch Linux
will break the 'qubes-vm-gui' dependency completely.

I think there's a need to have these Qubes packages on AUR repository as
well instead of just re-compiling the archlinux template again and again. I
tried both on the old 'my own compile version' of archlinux template and
the one from 'qubes-community-template' repo.

I'm not sure if NoUpgrade or IgnorePkg option on /etc/pacman.conf help much
in this case, instead I need to remove xf86-input-evdev,
xf86-input-libinput, xf86-input-void and xf86-input-joystick first before I
can upgrade other packages as well.

@Marek do you have any idea on this?

-- 
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/CAOCHQOuBhGLrbdXZQSax1G14ajTw4%2BJB6PZgybaDmZSvaLX%2BUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.