[qubes-users] Re: Qubes Builder - r4.0 building Ubuntu Bionic 18.04

2022-01-13 Thread Markus Dutschke
I have the same problem 2.5 years after your post. Did you find a fix for 
this issue?
I followed the following tutorials:

https://blockforums.org/topic/451-guide-to-installing-qbuntu-ubuntu-2004-focal-fossa-templatevm-in-qubes-release-404-rc1/
https://blockforums.org/topic/305-guide-to-installing-qbuntu-ubuntu-1604-xenial-templatevm-in-qubes-402-rc1/
https://www.reddit.com/r/Qubes/comments/5vzg04/idiots_guide_to_installing_qbuntu_ubuntu_1604/
https://www.qubes-os.org/doc/qubes-builder/
https://github.com/Qubes-Community/Contents/blob/master/docs/os/ubuntu.md

sourcexorapprentice schrieb am Sonntag, 21. Juli 2019 um 04:26:40 UTC+2:

> Greetings,
>
> I'm having some errors in using qubes-builder in r4.0 on a Fedora 30 
> template clone to build an Ubuntu Bionic 18.04 template. 
>
> On make template, the error I'm receiving is for an 'Architecture-Header' 
> wanting amd64 in a config file somewhere, followed by probably my real 
> error:
> "The repository 'https://deb.qubes-os.org/r4.0/vm bionic Release' does 
> not have a Release file."
>
> This feels like a really basic Linux package manager issue I *should* be 
> able to fix but it's not coming to me. The repository is of course for 
> Debian and so would not contain Bionic:
> https://deb.qubes-os.org/r4.0/vm/dists/
>
> Generally I was following the Qubesos.org/Github repo instructions as well 
> as this:
>
> https://www.reddit.com/r/Qubes/comments/5vzg04/idiots_guide_to_installing_qbuntu_ubuntu_1604/
> First, I had installed dependencies, git clone the qubes-builder Github 
> repo, added the Qubes and Debian 8-10 release keys. Then, ran ./setup.sh, I 
> selected my version of Qubes 4.0, "current", "yes" for stable, in the 
> repository plugin options had left "mgmt-salt" alongside "builder-debian", 
> and selected "bionic+desktop" and "yes" to build only template. 
>
> Last lines of the make error log:
>
> Creating config file /etc/perl/XML/SAX/ParserDetails.ini with new version
> Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
> Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
> Warning: apt-key output should not be parsed (stdout is not a terminal)
> 'qubes-mgmt-salt_4.0.19-1+bionicu1_amd64.buildinfo' looks like 
> architecture 'amd64', but this is not listed in the Architecture-Header!
> Ignoring as --ignore=surprisingarch given.
> Unknown file type: '935d34325afc0ff3fca2caaa64aa7d06 1699984 debug 
> optional libxen-4.8-dbgsym_4.8.5-7+bionicu1_amd64.ddeb', assuming source 
> format...
> Warning: File 'libxen-4.8-dbgsym_4.8.5-7+bionicu1_amd64.ddeb' looks like 
> source but does not start with 'xen_'!
> Unknown file type: 'bb311f5928ac86f87b83a765c16a521f 26812 debug optional 
> libxenstore3.0-dbgsym_4.8.5-7+bionicu1_amd64.ddeb', assuming source 
> format...
> Warning: File 'libxenstore3.0-dbgsym_4.8.5-7+bionicu1_amd64.ddeb' looks 
> like source but does not start with 'xen_'!
> Unknown file type: '8f969bf639d748a5050b7620da5cc3b6 16996 debug optional 
> xenstore-utils-dbgsym_4.8.5-7+bionicu1_amd64.ddeb', assuming source 
> format...
> Warning: File 'xenstore-utils-dbgsym_4.8.5-7+bionicu1_amd64.ddeb' looks 
> like source but does not start with 'xen_'!
> Unknown file type: '1dcecfc360d3f3f082d5b0af96b9bcf3 12268 debug optional 
> libvchan-xen-dbgsym_4.0.5-1+bionicu1_amd64.ddeb', assuming source format...
> Warning: File 'libvchan-xen-dbgsym_4.0.5-1+bionicu1_amd64.ddeb' looks like 
> source but does not start with 'libvchan-xen_'!
> Unknown file type: 'a35fe26b53b1d9a75b7785e8b8d5f0cd 11184 debug optional 
> libqubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb', assuming source format...
> Warning: File 'libqubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb' looks like 
> source but does not start with 'qubesdb_'!
> Unknown file type: '79ee3181db7c869b6f239a88fb127435 15520 debug optional 
> python-qubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb', assuming source 
> format...
> Warning: File 'python-qubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb' looks 
> like source but does not start with 'qubesdb_'!
> Unknown file type: 'b4a5abc704ec08ba2070251ff98ddcb1 16792 debug optional 
> python3-qubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb', assuming source 
> format...
> Warning: File 'python3-qubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb' looks 
> like source but does not start with 'qubesdb_'!
> Unknown file type: '4699162442699b71bbdcec2d4c6b1858 34820 debug optional 
> qubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb', assuming source format...
> Warning: File 'qubesdb-dbgsym_4.0.10-1+bionicu1_amd64.ddeb' looks like 
> source but does not start with 'qubesdb_'!
> Unknown file type: '9013109a50f7ed350eafaac669708507 15428 debug optional 
> libqrexec-utils2-dbgsym_4.0.25+bionicu1_amd64.ddeb', assuming source 
> format...
> Warning: File 'libqrexec-utils2-dbgsym_4.0.25+bionicu1_amd64.ddeb' looks 
> like source but does not start with 'qubes-utils_'!
> Unknown file type: '8dcb4edf3df86112ff6dc5fe333d262a 17592 debug optional 
> 

Re: [qubes-users] xrandr often coredumps

2022-01-13 Thread David Hobach

This usually is your screensaver failing to activate after an idle timeout.

It was mentioned on the other forum a few times already.

Not sure whether it's a Qubes bug, probably more a xrandr bug which affects the 
security of Qubes users.

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/24f730e4-4635-40ef-3312-cf25a641c7c1%40hackingthe.net.


smime.p7s
Description: S/MIME Cryptographic Signature


[qubes-users] xrandr often coredumps

2022-01-13 Thread 'Rune Philosof' via qubes-users
I am running Qubes 4.1rc3 on a Librem 14 and I see a lot of
```
Process 30303 (xrandr) of user 1000 dumped core
```
in my journalctl.

This morning I have ten within a minute.
I just resumed the computer from sleep and connected a usb-c monitor.

Are anyone else seeing similar issues?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a2a38830-20b9-4f02-93cd-afbbce3e8757n%40googlegroups.com.