Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
On Sunday, July 16, 2017 at 4:15:35 PM UTC+2, Unman wrote: > On Sun, Jul 16, 2017 at 12:41:43AM -0700, Foppe de Haan wrote: > > Bit OT, but Would anyone be willing to (briefly) indicate the difference > > between xenial and xenial+desktop? I tried googling, but I can't really > > find any info on it. > > > > Xenial template provides a basic system, not minimal but quite > small. > Xenial-desktop installs the ubuntu-desktop package, which gives you > pretty much everything you would expect in a standard "desktop" > installation - graphics tool and viewers , office suite, music player, > etc. > For full details look at the package contents here: > https://packages.ubuntu.com/xenial/ubuntu-desktop > > unman 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/8fd022bf-a9d5-4a3e-9eba-389fa00e07eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
On Sun, Jul 16, 2017 at 12:41:43AM -0700, Foppe de Haan wrote: > Bit OT, but Would anyone be willing to (briefly) indicate the difference > between xenial and xenial+desktop? I tried googling, but I can't really find > any info on it. > Xenial template provides a basic system, not minimal but quite small. Xenial-desktop installs the ubuntu-desktop package, which gives you pretty much everything you would expect in a standard "desktop" installation - graphics tool and viewers , office suite, music player, etc. For full details look at the package contents here: https://packages.ubuntu.com/xenial/ubuntu-desktop 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/20170716141531.uhcgy7bzks2xtlnb%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
Bit OT, but Would anyone be willing to (briefly) indicate the difference between xenial and xenial+desktop? I tried googling, but I can't really find any info on 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/3e2e85c6-e4ce-4503-b1ce-89f55623023a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
On Tue, Apr 18, 2017 at 06:22:18PM -0700, Reg Tiangha wrote: > On Sunday, January 29, 2017 at 7:38:09 PM UTC-7, Unman wrote: > > On Sat, Jan 28, 2017 at 12:31:38PM +, Nick Darren wrote: > > > /Hi all,/ > > > > > > > > Sorry to resurrect a dead thread, but what was the fix? I'm encountering the > same issue with trying to compile jessie and stretch debs, except this time > it's looking for Xen 4.6.4 instead of 4.6.5. I installed Xen 4.6.5 in dom0 > from current-testing and I've started to encounter VMs freezing or not > starting properly with PVGRUB kernels (works fine with the default kernel) > and I'm wondering if it's because matching Xen packages weren't pushed out on > jessie or stretch, thus I'm trying to compile my own based on the new version > to see if that fixes it (although to be fair, there've been a lot of updates > recently so it could be any combination of things). Marek has already pushed a fix - you need to update your build directories. (It was just that the Debian changelog hadnt been updated to match the new version.) -- 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/20170422201438.GA14212%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
On Fri, Feb 03, 2017 at 06:21:15AM +, 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./
>
>
>
>
> /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
>
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
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
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
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
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
> >>
> >> 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
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
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
>>
>> 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./
>>
> The error with Xen version affects all Debian builds - it isnt Ubuntu
> specific. That's interesting, because it
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
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
>
> 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./
>
The error with Xen version affects all Debian builds - it isnt Ubuntu
specific. That's interesting, because it shouldn't happen (obviously).
The error with gnome apps should have been fixed - I submitted a PR for
that some time ago - I'll look at it again today.
unman
--
You received this message because you are subscribed to
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
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] Workaround for building Ubuntu xenial+desktop with qubes-builder
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? -- 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/9BC40E31-D33D-49F7-96EC-4D8E11BF95FC%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Workaround for building Ubuntu xenial+desktop with qubes-builder
/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
