date:20210208

Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread Fabrizio Romano Genovese



On Monday, February 8, 2021 at 3:14:43 PM UTC+1 fac...@gmail.com wrote:

> I think your dell has different wifi and I think audio.   The wifi driver 
> for the xps 9310 is iwlwifi.   Here is some firmware info:  
> https://support.killernetworking.com/knowledge-base/killer-ax1650-in-debian-ubuntu-16-04/
>  
> and here is some qubes specific info on your wifi driver:  
> https://github.com/QubesOS/qubes-issues/issues/5615
>

Alas, no, I really have the AX500. The AX1650 is waay much more well 
behaved and it is the one that is usually shipped on XPS developer edition. 
Unfortunately XPS developer edition does not have a 32GB RAM option, which 
was absolutely needed for me, being Qubes unbelievably ram hungry. So I was 
forced to purchase the model with the Killer AX500 T_T


> I think the audio is different too, as the xps 9700 needs the 5.10 kernel 
> to work, but the base-config patch above does enable 
> CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE which I think you need too.
>
> To patch the kernel you must build it from source with qubes-builder 
> https://www.qubes-os.org/doc/qubes-builder/.   First configure it.  Then 
> change kernel to master branch in builer.conf.after the "make 
> get-sources"  is when you would patch with config-base in 
> qubes-builder/qubes-src/linux-kernel.
>

The sad thing is that audio worked perfectly on kernel 5.4... I'll try to 
give a look to this by the end of the week, when I'll have a bit less work 
to do  :)
 

> fedora 33 5.10 kernel supports much more devices and audio works in the 
> upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a 
> patch into qubes the upstream kernel modules which fedora has added or at 
> the minimum the SOF stuff in the patch.   Then all our audio will just work 
> with qubes.
>

That would be a wonderful, wonderful thing. In the meantime I'll try to 
learn how to compile my own kernels, my pc also tends to heat quite a lot 
and I suspect that a taylored kernel could make my overall experience 
better, correct me if I'm wrong... :)

About awokd suggestions: I tried to install 4.1 but the installer doesn't 
boot on my machine. Also, I've always been very unlucky with Qubes backups 
(traditionally I do them and they never work on restore), so I'd gladly 
avoid having to reinstall everything right now...


>
>
>
>
> On Sat, Feb 6, 2021 at 11:34 AM Fabrizio Romano Genovese <
> fabr...@statebox.io> wrote:
>
>>
>> I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound 
>> was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I 
>> have both wifi and sound not working :D 
>>
>> It seems that the sound issues are due to a problem with driver 
>> sof-audio-pci.
>> In this thread: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it 
>> turns out another user was having a similar problem with a dell 9700, which 
>> was apparently solved. Indeed in the thread it is said: 
>>
>> Audio works (with kernel 5.10 and attached kernel base-config patch  + 
>> latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin 
>> and alsa-ucm-config files.   see 
>> https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
>>  
>> for alsa ucm config ).
>>
>> Unfortunately, I am not technically skilled enough to really understand 
>> the fix. Does it mean that I have to download kernel 5.10 (from were?), 
>> apply the patch provided in the thread (how?), include firmware and config 
>> files (how?) and then compile and install?
>> As you can see I don't really have a specific question, and I'm more in 
>> search of a few clarifications to understand how to apply an apparently 
>> already available solution. :)
>>
>> Fab
>>
>> -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/qubes-users/5bde992b-ea73-499f-bcd1-38a0a2f0028fn%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> http://myutil.com
>

-- 
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/77d67c99-0039-487d-a91b-17e46f59010en%40googlegroups.com.

[qubes-users] The Ethics of Cybersecurity (open access)

2021-02-08 Thread Gianluca Miscione

The Ethics of Cybersecurity
https://www.springer.com/gp/book/9783030290528
Gianluca

-- 
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/CAOhAEOBWSJroBsocGYvd%3D%2BWCHH2jBnF-BuHG_GEUwEwUHNuHuA%40mail.gmail.com.

[qubes-users] kernel crashes (?) 5.10.13

2021-02-08 Thread haaber


I am testing the above xen kernel. I experience random freezes of the
system, with no significant "last words" in the logs, if it is not many
many  qmemman notices like these (sorry for the length). Is this a known
issue?? Any hints to stabilite the system?   Cheers!




Feb 08 18:15:40 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17640615,
total_mem_pref=4551340032.0, total_available_memory=11504979715.02)
Feb 08 18:15:40 dom0 qmemman.daemon.algo[2055]: left_memory=1402107746
acceptors_count=3
Feb 08 18:15:40 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17640615,
total_mem_pref=4592266444.8, total_available_memory=11464053302.2)
Feb 08 18:15:40 dom0 qmemman.daemon.algo[2055]: left_memory=1456607746
acceptors_count=3
Feb 08 18:15:43 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17640615,
total_mem_pref=4648645427.2, total_available_memory=11407674319.81)
Feb 08 18:15:43 dom0 qmemman.daemon.algo[2055]: left_memory=1530113766
acceptors_count=3
Feb 08 18:15:44 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17640615,
total_mem_pref=4691084083.2, total_available_memory=11365235663.81)
Feb 08 18:15:44 dom0 qmemman.daemon.algo[2055]: left_memory=1584279066
acceptors_count=3
Feb 08 18:15:45 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17640615,
total_mem_pref=4732670771.2, total_available_memory=11323648975.81)
Feb 08 18:15:45 dom0 qmemman.daemon.algo[2055]: left_memory=1636414622
acceptors_count=3
Feb 08 18:15:56 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17640615,
total_mem_pref=4683198054.4, total_available_memory=11373121692.6)
Feb 08 18:15:56 dom0 qmemman.daemon.algo[2055]: left_memory=1574288232
acceptors_count=3
Feb 08 18:17:26 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17640615,
total_mem_pref=4724763443.2, total_available_memory=11331556303.8)
Feb 08 18:17:26 dom0 qmemman.daemon.algo[2055]: left_memory=1485460405
acceptors_count=3
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: stat: dom '5'
act=2198308027 pref=488608972.8 last_target=2198308027
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: stat: dom '4'
act=1670913193 pref=334349516.8 last_target=1670913193
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: stat: dom '0'
act=4294967296 pref=1453227212.8 last_target=4294967296
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: stat: dom '7'
act=4194304000 pref=1386774937.601 last_target=4194304000
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: stat: dom '3'
act=33554432 pref=108003328 last_target=33554432
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: stat: dom '6'
act=3646632184 pref=953799475.2 last_target=3646632184
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: stat: xenfree=70069415
memset_reqs=[('5', 2153453877), ('4', 1629753095), ('3', 33554432),
('0', 4294967296), ('7', 4194304000), ('6', 3732745
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: mem-set domain 5 to
2153453877
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: mem-set domain 4 to
1629753095
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: mem-set domain 3 to 33554432
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: mem-set domain 0 to
4294967296
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: mem-set domain 7 to
4194304000
Feb 08 18:17:26 dom0 qmemman.systemstate[2055]: mem-set domain 6 to
3732745262
Feb 08 18:17:35 dom0 qmemman.daemon.algo[2055]:
balance_when_enough_memory(xen_free_memory=17542515,
total_mem_pref=4765301145.6, total_available_memory=11291019331.4)
Feb 08 18:17:35 dom0 qmemman.daemon.algo[2055]: left_memory=1400321867
acceptors_count=3
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: stat: dom '5'
act=2153453877 pref=488608972.8 last_target=2153453877
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: stat: dom '4'
act=1629753095 pref=334349516.8 last_target=1629753095
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: stat: dom '0'
act=4294967296 pref=1453227212.8 last_target=4294967296
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: stat: dom '7'
act=4194304000 pref=1386774937.601 last_target=4194304000
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: stat: dom '3'
act=33554432 pref=108003328 last_target=33554432
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: stat: dom '6'
act=3732745262 pref=994337177.6 last_target=3732745262
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: stat: xenfree=69971315
memset_reqs=[('5', 2110991693), ('4', 1591745932), ('3', 33554432),
('0', 4294967296), ('7', 4194304000), ('6', 3813300
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: mem-set domain 5 to
2110991693
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: mem-set domain 4 to
1591745932
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: mem-set domain 3 to 33554432
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: mem-set domain 0 to
4294967296
Feb 08 18:17:35 dom0 qmemman.systemstate[2055]: mem-set domain 7 to
419430

Re: [qubes-users] HCL - ASRock Z490 Extreme 4, i9-10900k

2021-02-08 Thread Sven Semmler


On 2/6/21 3:37 AM, tburkh...@cock.li wrote:
No ethernet out the box as the motherboard ethernet controller is 
Realtek RTL8125 which wasn't added to the kernel until 5.9

Everything else works as expected


Hi tburkhart,

did you mean to attach the HCL report?

/Sven

--
 public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6

--
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/f5c5d03e-b503-f3bd-740a-2c45d3e23ae9%40SvenSemmler.org.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] TemplateVM/StandaloneVM with python3.9

2021-02-08 Thread Frédéric Pierret


Hi,

For you information, in order to update all your TemplateVM/StandaloneVM having 
python3.9 like latest bullseye, Fedora 33, Gentoo, etc. with Salt or the Qubes 
Update widget, the mgmt-dvm needs to be switched to Fedora 33 template.

The technical reason can be found in 
https://github.com/saltstack/salt/pull/58518.

Best regards,
Frédéric

--
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/6e0c2cd2-9de4-75b9-dbb7-d7349372ebea%40qubes-os.org.


OpenPGP_signature
Description: OpenPGP digital signature

Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread 'awokd' via qubes-users


Rama McIntosh:


fedora 33 5.10 kernel supports much more devices and audio works in the
upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a
patch into qubes the upstream kernel modules which fedora has added or at
the minimum the SOF stuff in the patch.   Then all our audio will just work
with qubes.


Thanks for jumping in, Rama. It's difficult to troubleshoot hardware 
without hands-on.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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/88c05757-d26e-b0f6-3255-e13be0d578c6%40danwin1210.me.

Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread Rama McIntosh

I think your dell has different wifi and I think audio.   The wifi driver
for the xps 9310 is iwlwifi.   Here is some firmware info:
https://support.killernetworking.com/knowledge-base/killer-ax1650-in-debian-ubuntu-16-04/
and here is some qubes specific info on your wifi driver:
https://github.com/QubesOS/qubes-issues/issues/5615

I think the audio is different too, as the xps 9700 needs the 5.10 kernel
to work, but the base-config patch above does enable
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE which I think you need too.

To patch the kernel you must build it from source with qubes-builder
https://www.qubes-os.org/doc/qubes-builder/.   First configure it.  Then
change kernel to master branch in builer.conf.after the "make
get-sources"  is when you would patch with config-base in
qubes-builder/qubes-src/linux-kernel.

fedora 33 5.10 kernel supports much more devices and audio works in the
upstream fedora on both the 9700 and 9310 dells.  I'll see if I can get a
patch into qubes the upstream kernel modules which fedora has added or at
the minimum the SOF stuff in the patch.   Then all our audio will just work
with qubes.

On Sat, Feb 6, 2021 at 11:34 AM Fabrizio Romano Genovese <
fabri...@statebox.io> wrote:

>
> I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound
> was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I
> have both wifi and sound not working :D
>
> It seems that the sound issues are due to a problem with driver
> sof-audio-pci.
> In this thread: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it
> turns out another user was having a similar problem with a dell 9700, which
> was apparently solved. Indeed in the thread it is said:
>
> Audio works (with kernel 5.10 and attached kernel base-config patch  +
> latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin
> and alsa-ucm-config files.   see
> https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
> for alsa ucm config ).
>
> Unfortunately, I am not technically skilled enough to really understand
> the fix. Does it mean that I have to download kernel 5.10 (from were?),
> apply the patch provided in the thread (how?), include firmware and config
> files (how?) and then compile and install?
> As you can see I don't really have a specific question, and I'm more in
> search of a few clarifications to understand how to apply an apparently
> already available solution. :)
>
> Fab
>
> --
> 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/5bde992b-ea73-499f-bcd1-38a0a2f0028fn%40googlegroups.com
> 
> .
>

-- 
http://myutil.com

-- 
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/CAPVWjyMc-1iZoJ0GfJv%2B0fohDOUVk4dXe5Yp%3D15b%3Duy%3DFgH2og%40mail.gmail.com.

Re: [qubes-users] qubes-split-browser issues

2021-02-08 Thread Rusty Bird

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

taran1s:
> Rusty Bird:
> > taran1s:
> > > Rusty Bird:
> > > > Anything interesting in 'sudo journalctl' on
> > > > the DisposableVM?
> > 
> > > Can you navigate me how to open the terminal in the active dispvm please?
> > 
> > In the Domains Widget (system tray Q button), there's 'Run Terminal'
> > inside the disp1234 submenu.
> 
> Sorry, in the Domains Widget there is no active disp12... available. I can
> see the dispvm only in the Qube Manager.

Are you maybe confusing the Domains widget (Q on the upper right of
the screen - next to the Clipboard widget, Devices widget, etc.) with
the Applications button (Q on the upper left corner)?

Qube Manager can also open a terminal: Right click on disp1234, "Run
command in qube", enter "qubes-run-terminal".

Once you've got a terminal in the DisposableVM, can you please also
post (after the Tor Browser window has appeared) the full contents of:

/home/user/.tb/tor-browser/Browser/sb.js
/home/user/.tb/tor-browser/Browser/defaults/pref/sb-load.js

And the output of:

ps -efH | grep -i browser

> > The logs in the *persistent* VM would be relevant too:
> > 
> >  journalctl -t qubes.StartApp+split-browser-dom0 \
> > -t qubes.StartApp+split-browser-safest-dom0


> > Ah, for some reason the hotkeys aren't intercepted. Can you start a
> > new Split Browser, and post the full contents of Tor Browser's Browser
> > Console? (Ctrl-Shift-j)
> 
> split-browser-safest
> 
> [02-08 11:25:56] Torbutton NOTE: Initializing security-prefs.js
> [...]
> [02-08 11:25:56] Torbutton NOTE: security-prefs.js initialization complete
> Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
> [Exception... "Component returned failure code: 0x80520001
> (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"
> nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS
> frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync ::
> line 661"  data: no] 14 L10nRegistry.jsm:661:19
> Bootstrapped manifest not allowed to use 'resource' directive.
> chrome.manifest:2
> Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
> [Exception... "Component returned failure code: 0x80520001
> (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"
> nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS
> frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync ::
> line 661"  data: no] L10nRegistry.jsm:661:19
> Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
> [Exception... "Component returned failure code: 0x80004001
> (NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]"
> nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame ::
> resource:///modules/BrowserGlue.jsm :: _collectStartupConditionsTelemetry ::
> line 1743"  data: no] BrowserGlue.jsm:1743:9
> Error: setevents stream -> 510 Command filtered tor-control-port.js:237:19
> [02-08 11:25:59] Torbutton NOTE: no SOCKS credentials found for current
> document.
> Unchecked lastError value: Error: Could not establish connection. Receiving
> end does not exist. store.js:135
> a11y.sitezoom - Unknown scalar.
> [02-08 11:26:02] Torbutton WARN: Your Tor Browser is out of date.

Unremarkable log spam except for this^ line: Somehow the Split Browser
prefs from sb.js (which would disable Torbutton's broken update check)
aren't being applied.

> Key event not available on GTK2: key=“u” modifiers=“accel shift”
> id=“torbutton-new-identity-key” browser.xhtml
> Key event not available on some keyboard layouts: key=“r”
> modifiers=“accel,alt” id=“key_toggleReaderMode” browser.xhtml
> Key event not available on some keyboard layouts: key=“i”
> modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml

Rusty
-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmAhQlBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0
QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv
Kt+v9Q//Xvl8KgoG0J8P9hxyAOSdQWnH3yOLqhBHkF7PO7LVAiJkSt+0YXtDLPy/
jjp8SAkgix2RCJyUG29mDszEvJjOrOYLHXIKDG8dmhKRWfD4QvWB1cw7a2eZAhdh
H0jOGVACYI4UZ9W87/apxTnexx9vs8cvcSORMoxwsJg4spRWTj4RvaTxMTHyVTjc
v7kT9JzTRznaG96n78yUlM/+aCY/UWcHmDASwY0eoHJGzrnNO82NURx1h+K9P+Tp
F1GA+8UBO8k02stWpFmoRhjz4JBYTWtzgaXhe063Y2MsZD2ERu+Y7lXz+Iy3bPjE
G5cF86CBQQklCSqxA6Ih9cBwY6qw35se6BFzIm8ldLbe/kYGNnnfjZMJli3MpJky
vcBfkGIoyAMs2GQibDkQm0+EEJtjsmCzK9nLMdf2eR91Bw+I1ti19+ZMB6D0LKQB
3ALE3PK5tu93AenOi8WC/hWI0aPe3a4xoDu8T1Mgd3JyhsMEcsHtxYC3zttKOGo/
4jtDB+hx8m/YJfvJqVr2d+GoE6rUOa8vLIFiL7oILAikZkQ5BdTqTPCexSzTLeyp
csmXRhtaAgfYfK1pxEjAuEl0vUw8nfrEUC0hvWQawmXZElWiN4aWO5Q+GJpm4edg
AUpPvCWl+a9DwfRhPASv/fGmQpHbwnZOTNudwYDMGJ6sS9N39jY=
=a6Sl
-END PGP SIGNATURE-


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it,

Re: [qubes-users] qubes-split-browser issues

2021-02-08 Thread 'taran1s' via qubes-users

Rusty Bird:

taran1s:

Rusty Bird:

Anything interesting in 'sudo journalctl' on
the DisposableVM?

Can you navigate me how to open the terminal in the active dispvm please?

In the Domains Widget (system tray Q button), there's 'Run Terminal'
inside the disp1234 submenu.

Sorry, in the Domains Widget there is no active disp12... available. I
can see the dispvm only in the Qube Manager.

The logs in the *persistent* VM would be relevant too:

journalctl -t qubes.StartApp+split-browser-dom0 \
-t qubes.StartApp+split-browser-safest-dom0

- At the end, if I save a bookmark in the disp VM TB, launched from
the surfer VM, the bookmark doesnt survive the killing of the disp
VM and is not available from the another disp VM launched from the
surfer VM.

Did you use the hotkeys? Ctrl-d to save a persistent bookmark, and
Alt-b to open the persistent bookmarks list. Other methods (like
clicking the star outline in the address bar, etc.) unfortunately
won't work.

Yes I did. Clicking ctrl-d saves the bookmark with blue Saved to library!
popup in the active TB dispVM. alt-b opens up the bookmarks menu and I can
see the bookmark. It doesn't but survive the reboot.

Ah, for some reason the hotkeys aren't intercepted. Can you start a
new Split Browser, and post the full contents of Tor Browser's Browser
Console? (Ctrl-Shift-j)

split-browser-safest

[02-08 11:25:56] Torbutton NOTE: Initializing security-prefs.js
[02-08 11:25:56] Torbutton NOTE: security-prefs.js initialization complete
Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
[Exception... "Component returned failure code: 0x80520001
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"
nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location:
"JS frame :: resource://gre/modules/L10nRegistry.jsm ::
L10nRegistry.loadSync :: line 661" data: no] 14 L10nRegistry.jsm:661:19
Bootstrapped manifest not allowed to use 'resource' directive.
chrome.manifest:2

Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
[Exception... "Component returned failure code: 0x80520001
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"
nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location:
"JS frame :: resource://gre/modules/L10nRegistry.jsm ::
L10nRegistry.loadSync :: line 661" data: no] L10nRegistry.jsm:661:19

Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
[Exception... "Component returned failure code: 0x80004001
(NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]"
nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame
:: resource:///modules/BrowserGlue.jsm ::
_collectStartupConditionsTelemetry :: line 1743" data: no]
BrowserGlue.jsm:1743:9

Error: setevents stream -> 510 Command filtered tor-control-port.js:237:19
[02-08 11:25:59] Torbutton NOTE: no SOCKS credentials found for current
document.
Unchecked lastError value: Error: Could not establish connection.
Receiving end does not exist. store.js:135

a11y.sitezoom - Unknown scalar.
[02-08 11:26:02] Torbutton WARN: Your Tor Browser is out of date.
Key event not available on GTK2: key=“u” modifiers=“accel shift”
id=“torbutton-new-identity-key” browser.xhtml
Key event not available on some keyboard layouts: key=“r”
modifiers=“accel,alt” id=“key_toggleReaderMode” browser.xhtml
Key event not available on some keyboard layouts: key=“i”
modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml

--
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/453e9c0c-60d0-2271-81d2-82f8ca72d424%40mailbox.org.

Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread 'awokd' via qubes-users

Fabrizio Romano Genovese:

I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound
was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I
have both wifi and sound not working :D

It seems that the sound issues are due to a problem with driver
sof-audio-pci.
In this thread: https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM it
turns out another user was having a similar problem with a dell 9700, which
was apparently solved. Indeed in the thread it is said:

Audio works (with kernel 5.10 and attached kernel base-config patch +
latest 1.6.1 sof-bin firmware https://github.com/thesofproject/sof-bin and
alsa-ucm-config files. see
https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/
for alsa ucm config ).

Unfortunately, I am not technically skilled enough to really understand the
fix. Does it mean that I have to download kernel 5.10 (from were?), apply
the patch provided in the thread (how?), include firmware and config files
(how?) and then compile and install?
As you can see I don't really have a specific question, and I'm more in
search of a few clarifications to understand how to apply an apparently
already available solution. :)

Per https://groups.google.com/g/qubes-users/c/Fa65-e8vqdM, are you
running Qubes 4.1? That might be the first place to start. It implements
audio in a separate VM, which might automagically resolve the issue or
at least make for a more easily implemented solution. In that case,
you'll want your VM's kernel to be the latest, so in dom0 do sudo
qubes-dom0-update kernel-qubes-vm-latest (from memory). See if the audio
driver loads in the audio VM. If not, it gets more complex.

You could convert it to an HVM which would allow you to recompile the
kernel internal to the VM using standard Linux procedures- check
documentation for the distribution you're using. If you didn't want to
convert to HVM, I think you would have to build a kernel for dom0 first
per
https://www.mail-archive.com/qubes-users@googlegroups.com/msg10886.html,
then package for VM usage with
https://www.qubes-os.org/doc/managing-vm-kernel/#installing-different-vm-kernel-based-on-dom0-kernel
(note I haven't attempted this before).

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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/f0e56ef8-445a-ac71-534c-a97e8444f8ed%40danwin1210.me.

Re: [qubes-users] No sound in XPS9310

2021-02-08 Thread 'awokd' via qubes-users

Fabrizio Romano Genovese:

I installed qubes on a Dell XPS9310. I was using kernel 5.4.90 and sound
was working, but wi-fi did not. So I upgraded to kernel 5.10.13 and now I
have both wifi and sound not working :D

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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/5d493b9c-fb1b-2221-5a02-d43d9d0e7f5e%40danwin1210.me.

Re: [qubes-users] No sound in XPS9310

[qubes-users] The Ethics of Cybersecurity (open access)

[qubes-users] kernel crashes (?) 5.10.13

Re: [qubes-users] HCL - ASRock Z490 Extreme 4, i9-10900k

[qubes-users] TemplateVM/StandaloneVM with python3.9

Re: [qubes-users] No sound in XPS9310

Re: [qubes-users] No sound in XPS9310

Re: [qubes-users] qubes-split-browser issues

Re: [qubes-users] qubes-split-browser issues

Re: [qubes-users] No sound in XPS9310

Re: [qubes-users] No sound in XPS9310

11 matches

Site Navigation

Mail list logo

Footer information