[qubes-users] Screen shot: open in DocumentViewer in AppVM
When I screen scrape in dom0, one option is to open in DocumentViewer in one AppVM. I assume it is because this is the only AppVM I have DocumentViewer added to the big menu. Anyway, nothing ever happens. Does anyone use this? Has anyone used this? I also try "Copy to the ClipBoard" assuming I can then do a "Copy Dom0 Clipboard" and then paste in some AppVM but when I select "Copy Dom0 Clipboard" I get a "dom0 clipboard is empty!" popup. I'm trying to optimise the workflow of scraping screen and getting it to where I want it but the only way I can get it to work is to save it to Pictures in dom0 and then manually xfer it to some target VM and then rummage about in on the appVM Rather cumbersome. I'd also like to optimise the screen capture initiation. On other platforms, I have a nice control-meta-cokebottle sequence. I actually don't know what it is. My fingers know. -- 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/2f91434f-5c4c-4998-937d-7aa1448223bdn%40googlegroups.com.
[qubes-users] Backup to SMB mounted NAS in AppVM
Last night I tried to run QubesBackup, selecting an AppVM as the target, and then selecting the SMB-mounted (r/w) folder. The backup process started, and the progress bar presented a small sliver of blue on the left, but was 0%. Nothing was ever written to the target. No errors were ever suggested by the backup process. Pretty much 0% CPU was being used in dom0. After several hours, I closed the dom0 QubesManager window, which also closed the backup window, and tried re-running it directly as "Qubes Backup" from the menu. It claimed I had a backup running. Still nothing whatsoever written to SMB mounted folder. Has anyone successfully written to SMB mounted share using backup? -- 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/714a2077-ca37-4e32-a1d1-65a9f55aeb57n%40googlegroups.com.
[qubes-users] Re: Audio on HP Z8
Turns out someone had disabled the audio device in the BIOS. Can't imagine who I now have a built-in audio device which knows it has a place to plug in headphones. Sweet. On Wednesday, 31 March 2021 at 18:40:33 UTC+10 Beto HydroxyButyrate wrote: > Just tried to listen to something on my Qubes system. I know it works on > the Intel NUC systems, but on the HP it doesn't. Nothing. > > I have an audio device. See below for the `lspci` output. The > PulseAudioManager shows zero hardware devices, just the dummy one. > > Any ideas? I am supposedly on the most recent. > > 2d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 > Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr+ Stepping- SERR+ FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- Latency: 0, Cache Line Size: 32 bytes > Interrupt: pin B routed to IRQ 317 > Region 0: Memory at b024 (64-bit, non-prefetchable) [size=16K] > Capabilities: [48] Vendor Specific Information: Len=08 > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 > DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s > <4us, L1 unlimited > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ > Unsupported- > RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ > MaxPayload 256 bytes, MaxReadReq 512 bytes > DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr- > TransPend- > LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit > Latency L1 <1us > ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ > LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk+ > DLActive- BWMgmt- ABWMgmt- > DevCap2: Completion Timeout: Not Supported, TimeoutDis-, > LTR+, OBFF Not Supported > AtomicOpsCap: 32bit+ 64bit+ 128bitCAS- > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, > LTR-, OBFF Disabled > AtomicOpsCtl: ReqEn- > LnkSta2: Current De-emphasis Level: -3.5dB, > EqualizationComplete-, EqualizationPhase1- > EqualizationPhase2-, EqualizationPhase3-, > LinkEqualizationRequest- > Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Address: fee000b8 Data: > Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 > Len=010 > Capabilities: [150 v2] Advanced Error Reporting > UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- > RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- > UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- > RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- > UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- > RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- > CESta: RxErr- BadTLP+ BadDLLP+ Rollover- Timeout- > NonFatalErr- > CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- > NonFatalErr+ > AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- > ECRCChkCap+ ECRCChkEn- > MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- > HeaderLog: > Capabilities: [328 v1] Alternative Routing-ID Interpretation (ARI) > ARICap: MFVC- ACS-, Next Function: 0 > ARICtl: MFVC- ACS-, Function Group: 0 > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > > -- 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/9f36b565-de0a-46ff-b458-a71476208c79n%40googlegroups.com.
[qubes-users] Audio on HP Z8
Just tried to listen to something on my Qubes system. I know it works on the Intel NUC systems, but on the HP it doesn't. Nothing. I have an audio device. See below for the `lspci` output. The PulseAudioManager shows zero hardware devices, just the dummy one. Any ideas? I am supposedly on the most recent. 2d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit Latency L1 <1us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported AtomicOpsCap: 32bit+ 64bit+ 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee000b8 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP+ BadDLLP+ Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: Capabilities: [328 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 0 ARICtl: MFVC- ACS-, Function Group: 0 Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 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/bb514b39-b394-4bda-ae51-7916626d9b14n%40googlegroups.com.
[qubes-users] Re: QubesOS weekly builds
Trying to use the info provided to kick off my own ISO build. This posted links to does not use the `QubesBuilder` approach, as it references stuff apparently checked out to ~/qubes-src, rather than ~/qubes-builder/qubes-src. Is this different approach to building documented? What else should check out to ~/qubes-src? How does this fit into the "Development Workflow"? Per those docs: *Qubes is split into a bunch of git repos. This are all contained in the qubes-src directory under qubes-builder. Subdirectories there are separate components, stored in separate git repositories.* Just making ~/qubes-src a symbolic link to ~/qubes-builder/qubes-src does not fix things as, despite the claim that *this are all contained* in ~/qubes-builder/qubes-src, the two new git repos referenced are not contained there. [user@qubes-build qubes-src]$ pwd /home/user/qubes-builder/qubes-src [user@qubes-build qubes-src]$ ls qubes-release-configs ls: cannot access 'qubes-release-configs': No such file or directory [user@qubes-build qubes-src]$ ls qubes-installer-qubes-os ls: cannot access 'qubes-installer-qubes-os': No such file or directory [user@qubes-build qubes-src]$ ls ~/qubes-src ls: cannot access '/home/user/qubes-src': No such file or directory On Monday, 22 March 2021 at 09:33:20 UTC+11 Frédéric Pierret wrote: > Hi, > As some of you may know, months(years?) ago, I've setup a pipeline that is > automatically PR latest kernels for Qubes OS and more recently, pulseaudio > headers too. This is done every week. > > At some point, I added the build of ISO including kernel-latest for users > who were having issues with latest hardware. I stopped it quickly because > we were merging more and more kernel versions thank to the help of > automatic PR and Qubes point releases. > > Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add > again to this weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't > build any package or any template. It uses only Qubes OS repositories. The > qubes-builder conf is: > https://github.com/QubesOS/qubes-release-configs/blob/master/R4.1/qubes-os-iso-full-online.conf > > and the kickstart can be found here: > https://github.com/QubesOS/qubes-installer-qubes-os/blob/master/conf/iso-full-online.ks > . > > Please note that, contrary to my first attempt, I don't include > kernel-latest kernels. It's a standard R4.1 ISO as if Marek would release > one. It is built in a dedicated AppVM together with Split GPG. The ISOs are > signed by "fepitre-bot" 1C8714D640F30457EC953050656946BA873DDEC1. Some of > you already download latest R4.1 devel ISOs in openQA but they are not > signed and not necessary built in a safe environment because it's only for > CI purposes. That's a solution between CI ISOs and R4.1 alpha release. > > That said, the ISO(s) can be found on my self hosted server: > https://qubes.notset.fr/iso/. > > 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/a09d0823-dc8e-4edf-99d0-cdcc5296a2d4n%40googlegroups.com.
Re: [qubes-users] Easiest way to redirect USB to a VM?
On Wednesday, October 9, 2019 at 5:05:16 PM UTC+10, Jackie wrote: > > 'awokd' via qubes-users: > > > to create one manually. Pay close attention to how to identify a free > > USB controller. Some machines only have one, in which case it is not an > > option unless you have a PS/2 keyboard. > > I haven't done this but according to the docs it's possible to create > sys-usb even if you depend on a usb keyboard to enter luks passphrase. > See the "enable a usb keyboard for login" section of the doc page. > > > I have done this. Namely, installed without sys-usb, and then much later decided I need it, and went thru some steps to enable it. I have only one USB controller and a USB keyboard and mouse and enter the LUKS password at boot. I did backup everything prior to doing so, but there were no drama. What doesn't work for me is using the GUI to assign USB devices to a VM. I have to go into dom0 and do `qvm-usb; qvm-usb attach ...`. The GUI presents the list of USB devices, and the list of potential VMs to attach to, but never works to select the VM to attach to. No error. Silent failure. Been meaning to open a defect for this, but it is not something I do often. -- 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/89e02b13-2b53-4521-ac88-a794d97301fc%40googlegroups.com.
Re: [qubes-users] MTU setting for all interfaces
On Monday, February 25, 2019 at 12:14:34 AM UTC+10, unman wrote: > On Sun, Feb 24, 2019 at 02:02:10PM +1000, Beto HydroxyButyrate wrote: > > I have MTU 9000 set on my internal network. sys-net connects to this > > network. > > > > I want all qubes VM interfaces to default to MTU 9000 rather than 1500. > > > > Is there some simple global setting I can make to enable this? > > You could set it at the router level in sys-net using a mangle table. > This is available for both iptables and nftables. > I've done this with iptables in the past and I dont recall issues with > conntrack and connected clients. ymmv > > iptables has tcp-MSS patch that allows you to hit this in FORWARD rules > - dont know if similar is available for nftables. > > unman Not quite what I want. I want to be able to have all current and future VM instances which have networking enabled be provisioned with interfaces with the MTU set to 9000. I do not want any local s/w to be mangling the jumbo frames. I want jumbo frames flowing freely and naturally, as ghod and Selina Lo intended, between, for instance, my NAS drive and various VMs. Mainly for NAS SMB and/or NFS for performance. -- 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/abab22f9-6340-4806-8212-50bc6bc4cdf9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] MTU setting for all interfaces
I have MTU 9000 set on my internal network. sys-net connects to this network. I want all qubes VM interfaces to default to MTU 9000 rather than 1500. Is there some simple global setting I can make to enable 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/deb2ae5e-6a2b-6fe1-17d1-ff53c6f7fc6d%40damon.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] System freezes when left up for a day or two
Hi.
I am running Qubes-OS, 4.0, kept up to date, to the best of my knowledge.
I am on an HP Z8 G4 with 64GB memory. I pretty much mainly run a
personal VM (fedora-29+additions template) with the requisite
sys-{net,*,usb,...}.
The personal VM typically has FireFox, ThunderBird, and a Files and Term
running when it freezes.
I can successfully hibernate, but on restart, it just reboots, no
resume, so either I shutdown/reboot all the time, or I leave it running.
It never lasts more than a day or so. I come in to use it, and the
screen is dimmed, and will not wake up. I have it on an UPS, and no
other machines have issues with power, so that is not it.
When it freezes, sys-net does not respond to ARP requests. That is as
much as I know. No kernel debugger to break into, so no way to force it
to spill the beans. I have looked at various log files post reboot, but
nothing jumps out.
Anyone else having such 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 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/a0fa99c2-e623-d8b7-b91b-3a5decae69c9%40damon.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot update whonix-gw-14
My whonix-gw-14 template is failing to update. Any suggestions? sudo apt-get update && sudo apt-get update ... Hit:23 http://ftp.us.debian.org/debian stretch/contrib amd64 Contents (deb) Err:16 tor+http://vwakviie2ienjx6t.onion/debian stretch/main amd64 Contents (deb) Hash Sum mismatch Hashes of expected file: - Filesize:458159900 [weak] - SHA256:fa40630d28629019a1851b70a5314f6a94e72fb9c1c6f61f4364fc78b942c87e - MD5Sum:b01bc430892695ddaa164310200e0dc8 [weak] Hashes of received file: - SHA256:1e63fa3f9ee1381114f549a01bb4b49c07a168e1f1745f40c4f88bc2df6c19d4 - MD5Sum:bcc8c1982bf2c3577560cd825696 [weak] - Filesize:55131985 [weak] Release file created at: Sat, 14 Jul 2018 09:43:35 + Err:17 http://ftp.us.debian.org/debian stretch/main amd64 Contents (deb) Hash Sum mismatch Hashes of expected file: - Filesize:458159900 [weak] - SHA256:fa40630d28629019a1851b70a5314f6a94e72fb9c1c6f61f4364fc78b942c87e - MD5Sum:b01bc430892695ddaa164310200e0dc8 [weak] Hashes of received file: - SHA256:1e63fa3f9ee1381114f549a01bb4b49c07a168e1f1745f40c4f88bc2df6c19d4 - MD5Sum:bcc8c1982bf2c3577560cd825696 [weak] - Filesize:55131985 [weak] Release file created at: Sat, 14 Jul 2018 09:43:35 + Hit:24 tor+http://vwakviie2ienjx6t.onion/debian stretch/non-free amd64 Packages Get:25 tor+http://vwakviie2ienjx6t.onion/debian stretch/non-free Translation-en [80.6 kB] Hit:26 http://ftp.us.debian.org/debian stretch/non-free amd64 Packages Get:27 http://ftp.us.debian.org/debian stretch/non-free Translation-en [80.6 kB] Hit:28 tor+http://vwakviie2ienjx6t.onion/debian stretch/non-free amd64 Contents (deb) Hit:29 http://ftp.us.debian.org/debian stretch/non-free amd64 Contents (deb) Hit:18 tor+http://vwakviie2ienjx6t.onion/debian stretch/contrib amd64 Packages Hit:20 http://ftp.us.debian.org/debian stretch/contrib amd64 Packages Fetched 241 kB in 18s (12.8 kB/s) Reading package lists... Done E: Failed to fetch store:/var/lib/apt/lists/partial/vwakviie2ienjx6t.onion_debian_dists_stretch_main_Contents-amd64.gz Hash Sum mismatch Hashes of expected file: - Filesize:458159900 [weak] - SHA256:fa40630d28629019a1851b70a5314f6a94e72fb9c1c6f61f4364fc78b942c87e - MD5Sum:b01bc430892695ddaa164310200e0dc8 [weak] Hashes of received file: - SHA256:1e63fa3f9ee1381114f549a01bb4b49c07a168e1f1745f40c4f88bc2df6c19d4 - MD5Sum:bcc8c1982bf2c3577560cd825696 [weak] - Filesize:55131985 [weak] Release file created at: Sat, 14 Jul 2018 09:43:35 + E: Failed to fetch store:/var/lib/apt/lists/partial/ftp.us.debian.org_debian_dists_stretch_main_Contents-amd64.gz Hash Sum mismatch Hashes of expected file: - Filesize:458159900 [weak] - SHA256:fa40630d28629019a1851b70a5314f6a94e72fb9c1c6f61f4364fc78b942c87e - MD5Sum:b01bc430892695ddaa164310200e0dc8 [weak] Hashes of received file: - SHA256:1e63fa3f9ee1381114f549a01bb4b49c07a168e1f1745f40c4f88bc2df6c19d4 - MD5Sum:bcc8c1982bf2c3577560cd825696 [weak] - Filesize:55131985 [weak] Release file created at: Sat, 14 Jul 2018 09:43:35 + E: Some index files failed to download. They have been ignored, or old ones used instead. -- 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/ee49eea0-0e2b-3d57-80c2-0e5a790857fa%40damon.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: debian-9 template
On 10/11/18 6:25 AM, Marek Marczykowski-Górecki wrote: > On Wed, Oct 10, 2018 at 05:24:33AM -0700, b...@damon.com wrote: > > On Friday, April 27, 2018 at 10:46:08 PM UTC+10, higgin...@gmail.com > wrote: > > ... > > > I have been plagued with this issue ever since heeding the call to > upgrade whonix-13 to whonix-14. All my whonix-14 templates are useless. > > > I followed the steps carefully, removing / reinstalling. No errors. > > > user@host:~$ sudo dmesg | grep segf > > [ 11.396489] qubesdb-daemon[232]: segfault at 7994802abff8 ip > 799480098f64 sp 7994802ac000 error 6 in > ld-2.24.so[79948008f000+23000] > > [ 12.342682] qrexec-agent[648]: segfault at 70d5257f6ff8 ip > 70d5255f3355 sp 70d5257f7000 error 6 in > ld-2.24.so[70d5255dd000+23000] > > [ 15.903799] qrexec-agent[789]: segfault at 70d5257f6ff8 ip > 70d5255f3355 sp 70d5257f7000 error 6 in > ld-2.24.so[70d5255dd000+23000] > > [ 1524.123824] qrexec-fork-ser[4430]: segfault at 7b59263a8ff8 ip > 7b59261a2355 sp 7b59263a9000 error 6 in > ld-2.24.so[7b592618c000+23000] > > [ 1547.347882] qrexec-fork-ser[4456]: segfault at 7b59263a8ff8 ip > 7b59261a2355 sp 7b59263a9000 error 6 in > ld-2.24.so[7b592618c000+23000] > > [ 1594.046093] qrexec-fork-ser[4527]: segfault at 7b59263a8ff8 ip > 7b59261a2355 sp 7b59263a9000 error 6 in > ld-2.24.so[7b592618c000+23000] > > [ 2963.435851] qrexec-fork-ser[5300]: segfault at 7b59263a8ff8 ip > 7b59261a2355 sp 7b59263a9000 error 6 in > ld-2.24.so[7b592618c000+23000] > > [ 3145.932364] qrexec-fork-ser[5413]: segfault at 7b59263a8ff8 ip > 7b59261a2355 sp 7b59263a9000 error 6 in > ld-2.24.so[7b592618c000+23000] > > > Everything is hosed. > > > If anyone has a fix, I would appreciate knowing it. > > This looks to be the issue described here: > https://github.com/QubesOS/qubes-issues/issues/4349 > > The proper fix is in testing repository right now, you can either > install it[1], or apply a workaround listed in that ticket (add noxsave > to kernelopts of that template and VMs based on it). Actually, you may > need to apply workaround temporarily to be able to install updates... > > [1] https://www.qubes-os.org/doc/software-update-vm/#debian > Thanks for that! I should have figured out how to post to qubes-users much earlier, rather than bashing my head against the wall for so long. -- 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/e31d1b2a-1dd1-b724-a807-4a7232d12fd9%40damon.com. For more options, visit https://groups.google.com/d/optout.
