[qubes-users] Qubes crashing after entering disk password because of kernel panic
I have been trying to install and use Qubes which I have been able to solve many problems with the help of documentation but now I can get to the disk password screen and enter it but it crashes it right after. It opens a command line and outputs the process and at the end before it crashes it says kernel panic – not syncing: Fatal exception. Any help would be appreciated. Might just reinstall without a disk password and see what happens -- 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/BY5PR22MB18437CF4C224153BCD66F3F50%40BY5PR22MB1843.namprd22.prod.outlook.com.
Re: [qubes-users] Re: How to setup a multimedia VM in Qubes OS 4.0.3 and read files from within its applications ?
On Thu, Mar 19, 2020 at 03:12:04PM -0700, 'M' via qubes-users wrote: > 1) Is there a more secure way to get a .deb file downloaded from a > web-page/server and get it into a template VM than the method I have > described above under "How to install a .deb file in the multimedia > template VM ?", and if so how ? Yes. A lot more secure and a lot more easy. You should go a bit easy on the tutorial style posts until you have figured this out for yourself. I mean this in the best possible way: giving back to the community is what's it all about ... but at the moment you might harm more then help. To your question: Just download the .deb file right there in your broweser and then open the folder that contains the Downloads. Right click on the .deb file and "Copy to other AppVM..." and select the TemplateVM where you want to install. In that TemplateVM you will then find the .deb file in the "QubesIncoming" folder in your home directory. This is one of the very core features of Qubes together with the Clipboard: the ability to share data easy, fast and securely between VMs/Qubes. > 2) When installing new applications or replacing an application in a > template, is it then necessary to delete the VM's that is based on this > template to get the changes implemented in the AppVM's, or can they be > implemented in a smarter way ? Not at all. As soon as you shutdown the TemplateVM the changes are on disk. Then shutdown and restart the AppVM and you'll have the new version. You should probably read this carefully: https://www.qubes-os.org/doc/templates/#advanced /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/20200320013832.GC1126%40app-email-private. signature.asc Description: PGP signature
Re: [qubes-users] Re: [4.0] Intel Wi-Fi 6 AX200 adapter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Mar 20, 2020 at 01:05:02AM +0100, Vít Šesták wrote: > Hello, > > On March 20, 2020 12:33:31 AM GMT+01:00, "Marek Marczykowski-Górecki" > wrote: > >I didn't spot VT-d errors, but I'm not entirely sure if I've checked. > >If they are there, this is something definitely worth looking into and > >most likely an issue within iwlwifi driver (or the firmware). It could > >be also worth trying booting Fedora 31 Live directly, but add > >intel_iommu=on kernel option. If that would break it, it's a clear > >indication that the issue is somewhere between firmware and the driver. > > I have tried to add this option, but it remained to work. Does it mean that > the driver itself is OK and the issue is in Xen or stubdom? Likely, but not surely. Some more ideas what could be wrong: 1. Some config space access is filtered and driver doesn't cope with it. 2. Some extended PCIe feature that driver/firmware assumes present is not implemented in PCI passthrough. 3. Bug in handling any of supported PCIe features. 4. And there is still a possibility for a bug in the driver/firmware. For the first hypothesis, I'd try enabling permissive option (AFAIR didn't helped in itself), but then enable verbose logging in pciback driver: echo 1 > /sys/module/xen_pciback/parameters/verbose_request before starting sys-net. You'll get quite a lot of logs this way, and for understanding them fully, PCI spec would be handy... But maybe there will be some less obscure clues, like messages about explicitly failing requests? For the second hypothesis, I'd take lspci -vv of the device from both sys-net and dom0 (preferably in exact the same time, during enabling the interface, but that's unrealistic). And compare. There will be definitely some differences (more features visible in dom0), but what would be valuable is: - comparing configuration of features visible in both places - correlating missing features with iwlwifi driver It may be also useful to increase iwlwifi log level (I see 'debug' module option, seems to be a bitmask). For the third hypothesis, enable iwlwifi debugging and hope for more details. Decoding that firmware error would also be useful, but unlikely without firmware documentation or source code. If everything above fails, I would thoroughly compare driver behavior on bare metal and in the VM. Start with the driver debug output and if still no clues, then log hardware interactions (may require modifying the driver) and compare them. Some of the above ideas are quite extreme, and tedious to execute... PS adding the list back. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl50F2QACgkQ24/THMrX 1ywLuAgAjd/zJfxu9cHAo4h7vEib+0LWOTx55/hv8cGP9CsKNcpIdY6SJfg2Smy1 nhzh7BwxTkwnzGjYsmLzN+NX8uaTOXiLLdoEhoaOGbLekdsfJnXKLyXdu2AEhFHj ejKYfWTRNLnqDWNViNNhFgx9vbOsasyiQWh0tMJm5cwUkXMz82DTjVqDXBBtgog1 86hMdLcSxRYVNw0q+KL3zmlagpbxDcmwnf0cV6NjyckQ1LWQ+pr/zx3FS74WatJP D7k7dJ1M6rEdEDJaZ+K+XiXkLzJUufuwwKMlN4VL4SFvwmD5aglZm2B0rdcBBF9a 7pGs+ORAnWH4T4gnpiPi5OcfZWjiAQ== =SAV0 -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, 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/20200320010747.GB18599%40mail-itl.
Re: [qubes-users] Installations Problems
Hi, we seem to have the same laptop. You mention this documentation regarding freezing: https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer > So i went to "Installation freezes before displaying installer" in the doc, and > after figuring out that the ANACONDA partition is the one to edit commented > |noexitboot=1 mapbs=1 out.| Can you lead me to a layman's DIY of the three steps in how to "Change the xen configuration on a USB media" at the top of this document? 1 - How to "mount the EFI partition"? 2 - How can I be "su", and edit the xen config with the kernel key changes? Then any steps you took if you had success in completing the installation. Cheers, > -- 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/bccd0210-b35f-4883-b503-cee0be543365%40googlegroups.com.
Re: [qubes-users] Re: [4.0] Intel Wi-Fi 6 AX200 adapter
On 2020-03-20 00:33, Marek Marczykowski-Górecki wrote: > Is it a Realtek card? I don't remember exactly what helped, but > something helped here. Paweł, can you help? > It was either attaching SD card reader (which is another function on the > same PCI device) to the sys-net, or enabling no-strict-reset option (or > maybe permissive?). It was *not* attaching the SD card reader (that caused sys-net to crash with Xen errors) and enabling no-strict-reset. I think the permissive option turned out to be unnecessary. Also, it didn't work at first and we had to reboot the computer, but that might have been because we were trying other things as well. The devices in question: 26:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) 26:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) -- Paweł Marczewski Invisible Things Lab -- 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/8f47f881-65ec-52c0-769f-a171880e1a49%40invisiblethingslab.com. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Re: [4.0] Intel Wi-Fi 6 AX200 adapter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Mar 19, 2020 at 11:41:55PM +0200, 'Ilpo Järvinen' via qubes-users wrote: > On Thu, 19 Mar 2020, Vít Šesták wrote: > > > Hello, > > I have some interesting updates. I have tried to: > > > > a. Boot Fedora 31 on the laptop (Live version from USB drive) – adapter is > > detected and finds Wi-Fi networks. It just works. > > b. Boot Fedora 31 Live (from the same USB drive) in a HVM with attached > > Wi-Fi card. It had 2000MiB of RAM. It fails in the same way as my previous > > attempts, not sure why. > > > > This looks like the AppVM is fine, but there is some glitch in the PCI > > handling. It might be related to Xen or to the DM, not sure. > > > > HVM: https://gist.github.com/v6ak/76f2c089c63b1fe184f3717d5bd5254e > > sys-net with Fedora 31: > > https://gist.github.com/v6ak/30ecc502d1ce7508953eb3d505564668 > > > > I have also resolved the chicken-egg problem – I can connect to the Internet > > via USB. This is not a permanent solution, but it was good enough for > > updating dom0. However, the update (+ subsequent reboot) has not changed > > anything. > > One option would be compile a kernel with CONFIG_IWLWIFI_TRACING (or > something like that) and try to provide the trace log to iwlwifi devs. > ...It might not help though if it's not a HW/driver issue but xen/dm/pci > related thing. I've seen very similar thing recently, not sure if exactly the same, but it's very likely. Sad news is neither me nor Paweł managed to fix it yet. Things we've tried: - various kernel versions (including 5.5 and 5.4) - different firmware versions (apparently the driver tries to load versions that new that are nowhere to be found yet) - various options like permissive mode I didn't spot VT-d errors, but I'm not entirely sure if I've checked. If they are there, this is something definitely worth looking into and most likely an issue within iwlwifi driver (or the firmware). It could be also worth trying booting Fedora 31 Live directly, but add intel_iommu=on kernel option. If that would break it, it's a clear indication that the issue is somewhere between firmware and the driver. >> 1. Problem: Domain sys-net did not boot at all because of issues with >> attaching ethernet PCI device. Is it a Realtek card? I don't remember exactly what helped, but something helped here. Paweł, can you help? It was either attaching SD card reader (which is another function on the same PCI device) to the sys-net, or enabling no-strict-reset option (or maybe permissive?). - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl50AUwACgkQ24/THMrX 1yzCQwf/RHg7jCK7CS0ut98MoI2oDvRf6SJc6oVTNbbklovmmZcRwj9SrXcEw7j9 KQ0X/i7HpEr03MmMxOlQO8R4BUdXqZ5iyDWLnPLNRZimH2ftA55ndOaOqecaQZOc nzxpeUyEHbO8D/ZwodRoTBF9Tl+e4lI7wOz/O6Ruy604++z3P5gzTuYVp390CiYU Jt5suLKxoIuICO8EaRBT/5KGDM4BsuW9pfe2YDBs4USWg75D9C86KvgSGZhD6xd/ GwfPd3KXyiPTYHWT5fymupatiPnMVPKjpMQDyOvPbHJqUoUJ+owO/nqfSquWV8Mz h4M2DffaBN/i8zxxtIWwh0nGLbX/kA== =c9Wb -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, 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/2020031921.GB19117%40mail-itl.
Re: [qubes-users] Re: [4.0] Intel Wi-Fi 6 AX200 adapter
On Thu, 19 Mar 2020, Vít Šesták wrote: > Well, maybe it would be better to just compile some newer StubDom. > > Also, I have realized that there is some similar discussion on Github: > https://github.com/QubesOS/qubes-issues/issues/5615 Yes, multiple person have reported this same issue also on this list. I even saw one report in some in some external bug tracker. In that case it was mixed up with some other issue within the same issue. The Intel devs chose to prioritize the other issue over the one that seems to occur in case of Qubes. It is very obvious that this HW was out when the driver still had very subpar quality (Intel claimed support but many found out the device just doesn't work, this wasn't at all Qubes specific at start) so I wouldn't be surprised if it has something to do with the driver. -- i. > > Regards, > Vít Šesták 'v6ak' > > On Thursday, March 19, 2020 at 10:42:00 PM UTC+1, Ilpo Järvinen wrote: > On Thu, 19 Mar 2020, Vít Šesták wrote: > > > Hello, > > I have some interesting updates. I have tried to: > > > > a. Boot Fedora 31 on the laptop (Live version from USB drive) > – adapter is > > detected and finds Wi-Fi networks. It just works. > > b. Boot Fedora 31 Live (from the same USB drive) in a HVM with > attached > > Wi-Fi card. It had 2000MiB of RAM. It fails in the same way as > my previous > > attempts, not sure why. > > > > This looks like the AppVM is fine, but there is some glitch in > the PCI > > handling. It might be related to Xen or to the DM, not sure. > > > > HVM: > https://gist.github.com/v6ak/76f2c089c63b1fe184f3717d5bd5254e > > sys-net with Fedora 31: > > https://gist.github.com/v6ak/30ecc502d1ce7508953eb3d505564668 > > > > I have also resolved the chicken-egg problem – I can connect > to the Internet > > via USB. This is not a permanent solution, but it was good > enough for > > updating dom0. However, the update (+ subsequent reboot) has > not changed > > anything. > > One option would be compile a kernel with CONFIG_IWLWIFI_TRACING > (or > something like that) and try to provide the trace log to iwlwifi > devs. > ...It might not help though if it's not a HW/driver issue but > xen/dm/pci > related thing. -- 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/alpine.DEB.2.20.2003200020320.5256%40whs-18.cs.helsinki.fi.
Re: [qubes-users] Re: [4.0] Intel Wi-Fi 6 AX200 adapter
Well, maybe it would be better to just compile some newer StubDom. Also, I have realized that there is some similar discussion on Github: https://github.com/QubesOS/qubes-issues/issues/5615 Regards, Vít Šesták 'v6ak' On Thursday, March 19, 2020 at 10:42:00 PM UTC+1, Ilpo Järvinen wrote: > > On Thu, 19 Mar 2020, Vít Šesták wrote: > > > Hello, > > I have some interesting updates. I have tried to: > > > > a. Boot Fedora 31 on the laptop (Live version from USB drive) – adapter > is > > detected and finds Wi-Fi networks. It just works. > > b. Boot Fedora 31 Live (from the same USB drive) in a HVM with attached > > Wi-Fi card. It had 2000MiB of RAM. It fails in the same way as my > previous > > attempts, not sure why. > > > > This looks like the AppVM is fine, but there is some glitch in the PCI > > handling. It might be related to Xen or to the DM, not sure. > > > > HVM: https://gist.github.com/v6ak/76f2c089c63b1fe184f3717d5bd5254e > > sys-net with Fedora 31: > > https://gist.github.com/v6ak/30ecc502d1ce7508953eb3d505564668 > > > > I have also resolved the chicken-egg problem – I can connect to the > Internet > > via USB. This is not a permanent solution, but it was good enough for > > updating dom0. However, the update (+ subsequent reboot) has not changed > > anything. > > One option would be compile a kernel with CONFIG_IWLWIFI_TRACING (or > something like that) and try to provide the trace log to iwlwifi devs. > ...It might not help though if it's not a HW/driver issue but xen/dm/pci > related thing. > > -- > i. -- 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/aa3c864a-fe45-4bc4-8614-860f28db8e4f%40googlegroups.com.
Re: [qubes-users] Re: How to setup a multimedia VM in Qubes OS 4.0.3 and read files from within its applications ?
torsdag den 19. marts 2020 kl. 17.26.29 UTC+1 skrev Sven Semmler: > > On Thu, Mar 19, 2020 at 02:18:55AM -0700, 'M' via qubes-users wrote: > > Ok, I'll try to make a Fedora multimedia template and see how that > works... > > > > According to the following webpage, the advice is to clone a > preinstalled > > template: https://www.qubes-os.org/doc/multimedia/ > > > > 1) Can I just clone the fedora-30 template and set networking in the > new > > template to the sys-firewall, or would that compromise the security of > > Qubes OS ? > > TemplateVMs do not require networking to install software. Qubes > implements an UpdateProxy in your sys-firewall and all TemplateVMs know > how to connect to it to retrieve updates without having an explicit > network interface. > > The idea is to NEVER give a TemplateVM network access to prevent > accidential contamination. Only legit update/install traffic will go > over the dedicated UpdateProxy. > > > If the last is true: How shall I instead make a new Fedora > template, > > and install the applications I want in it ? > > Just try: > > - qvm-clone fedora-30 fedora-30-multimedia > - qvm-run -a fedora-30-multimedia xterm > - in Xterm: sudo dnf update > > It'll work without network interface. > > > 2) Shall networking in all templates be set to none as default, and is > it > > necessary to change this when installing new plugins for multimedia > manager > > applications which the user would like stayed installed after the VM is > > restarted ? > > The other basic idea of Qubes is to install but never run any > applications in the TemplateVM. So after you cloned the TemplateVM and > installed software via 'sudo dnf install' shut it down and create an > AppVM based on the template: > > qvm-create --template fedora-30-multimedia --label red multimedia > qvm-run -a multimedia xterm > > ... then in XTerm launch your applications and try them. > > /Sven > > -- > public key: https://www.svensemmler.org/0x8F541FB6.asc > fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 > > Thank you for the answers, which is very nice to know. And I got two new questions for you - just jump to the end of this message, as you don't have to read the following. *Info only to those who would read this thread in order to setup a multimedia VM in Qubes OS 4.0.3 them self:* When trying to install the applications in a Fedora 30 template, I ran into the same problems as with the Debian 10 template: All the versions of the applications are several years old. And as the Musique player package is a .deb-file, it only seems to work with Debian. I have therefore gone back to Debian. To install the 3.4.4-2 version of Rhythmbox, it is needed to either wait for the Debian template in Qubes gets updated to Bullseye or download the Bullseye template that Unman has created and made possible for download here; https://qubes.3isec.org/Templates_4.0/ , or create it yourself following this guide: https://www.qubes-os.org/doc/building-non-fedora-template/ *How to install a .deb file in the multimedia template VM ?* If there isn't any other more secure way to get a .deb file downloaded from a web-page/server and get it into a template VM, here is a way to do it: 1) Copy the trusted download-link for the .deb-file from the Firefox browser in another AppVM. 2) Open the "Qube Settings" for the multimedia template VM, and change networking to the sys-firewall. Click on "Apply" and "Ok". 3) Open the Firefox browser in the multimedia template VM and paste the download-link in the html line and press ENTER. Now the file should be downloaded to the Download folder in the multimedia template VM. For security reasons, do not use the browser to other things. 4) When the file has been downloaded: Open the "Qube Settings" again for the multimedia template VM, and change networking to the default none. 5) Open the terminal in the multimedia template VM, and execute these commands: a) cd Downloads b) sudo dpkg -i filename.deb c) In case you get any dependency errors: sudo apt-get install -f d) In case you would like to remove the package again: sudo dpkg -r teamviewer To also remove the configuration files, write "--purge" instead of "-r". *New questions* 1) Is there a more secure way to get a .deb file downloaded from a web-page/server and get it into a template VM than the method I have described above under "How to install a .deb file in the multimedia template VM ?", and if so how ? 2) When installing new applications or replacing an application in a template, is it then necessary to delete the VM's that is based on this template to get the changes implemented in the AppVM's, or can they be implemented in a smarter way ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group
Re: [qubes-users] Re: [4.0] Intel Wi-Fi 6 AX200 adapter
On Thu, 19 Mar 2020, Vít Šesták wrote: > Hello, > I have some interesting updates. I have tried to: > > a. Boot Fedora 31 on the laptop (Live version from USB drive) – adapter is > detected and finds Wi-Fi networks. It just works. > b. Boot Fedora 31 Live (from the same USB drive) in a HVM with attached > Wi-Fi card. It had 2000MiB of RAM. It fails in the same way as my previous > attempts, not sure why. > > This looks like the AppVM is fine, but there is some glitch in the PCI > handling. It might be related to Xen or to the DM, not sure. > > HVM: https://gist.github.com/v6ak/76f2c089c63b1fe184f3717d5bd5254e > sys-net with Fedora 31: > https://gist.github.com/v6ak/30ecc502d1ce7508953eb3d505564668 > > I have also resolved the chicken-egg problem – I can connect to the Internet > via USB. This is not a permanent solution, but it was good enough for > updating dom0. However, the update (+ subsequent reboot) has not changed > anything. One option would be compile a kernel with CONFIG_IWLWIFI_TRACING (or something like that) and try to provide the trace log to iwlwifi devs. ...It might not help though if it's not a HW/driver issue but xen/dm/pci related thing. -- i. -- 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/alpine.DEB.2.20.2003192334390.5256%40whs-18.cs.helsinki.fi.
[qubes-users] Re: [4.0] Intel Wi-Fi 6 AX200 adapter
Hello, I have some interesting updates. I have tried to: a. Boot Fedora 31 on the laptop (Live version from USB drive) – adapter is detected and finds Wi-Fi networks. It just works. b. Boot Fedora 31 Live (from the same USB drive) in a HVM with attached Wi-Fi card. It had 2000MiB of RAM. It fails in the same way as my previous attempts, not sure why. This looks like the AppVM is fine, but there is some glitch in the PCI handling. It might be related to Xen or to the DM, not sure. HVM: https://gist.github.com/v6ak/76f2c089c63b1fe184f3717d5bd5254e sys-net with Fedora 31: https://gist.github.com/v6ak/30ecc502d1ce7508953eb3d505564668 I have also resolved the chicken-egg problem – I can connect to the Internet via USB. This is not a permanent solution, but it was good enough for updating dom0. However, the update (+ subsequent reboot) has not changed anything. Regards, Vít Šesták 'v6ak' On Wednesday, March 18, 2020 at 8:46:31 PM UTC+1, Vít Šesták wrote: > > Hello, > on a new laptop, I am trying to setup Qubes OS 4.0. I have installed the > latest point release (i.e., 4.0.3). I have bunch of issues, the most > important one is that I cannot connect to any network. I have made some > progress, but now, I am asking for some assistance. > > The command lspci shows the adapter as Intel Corporation Wi-Fi 6 AX200 > (rev 1a). > > 1. Problem: Domain sys-net did not boot at all because of issues with > attaching ethernet PCI device. > Workaround: I don't care much about ethernet, so I removed the PCI device. > Not optimal, but easy and good enough for now. > > 2. Domain sys-net does not even load iwlwifi kernel module. > Cause: I have found that I need kernel 5.1 or 5.2 (depending on the > source). > Solution: Use a backup of up-to-date Fedora 30 VM. Configure the mode to > HVM and the kernel to “(none)”. This will use up-to-date kernel from > Fedora, which is new-enough. > Relevant link: > https://www.reddit.com/r/ManjaroLinux/comments/bx0skx/iwlwifi_driver_not_loading_for_intel_ax200_wifi/ > Relevant link: > https://www.intel.com/content/www/us/en/support/articles/05511/network-and-i-o/wireless-networking.html > > 3. Domain sys-net loads iwlwifi kernel module, but the Wi-Fi fails > immediately with “Microcode SW error detected. Restarting 0x200”. It > seems that Fedora automatically retries again and again and spams the log. > This is the issue I am struggling with. > > What I have tried: > * Use Fedora 31. I just cloned Fedora 30 on other laptop, created backup > and transferred to the other laptop. See > https://github.com/QubesOS/qubes-issues/issues/5289#issuecomment-582442319 > * Download ucode from > https://www.intel.com/content/www/us/en/support/articles/05511/network-and-i-o/wireless-networking.html > * Replace /usr/lib/firmware/iwlwifi-cc-a0-48.ucode by > /usr/lib/firmware/iwlwifi-cc-a0-46.ucode if `sudo dmesg | grep 'firmware > version'` suggests that the 48 is being loaded. I did it in the TemplateVM, > rebooted sys-net and ensured that 46 is being loaded. According to the > https://www.intel.com/content/www/us/en/support/articles/05511/network-and-i-o/wireless-networking.html > > , the version 46 is for AX200 and 48 is for AX201. > No combination of those has helped, I am still getting the errors. > > Logs (Fedora 31, ucode from Intel): > * Log sample (truncated, because it was too large, but it seems that > messages are repeating): > https://gist.github.com/v6ak/1cb7b172f63f8c20d7c4004f7996de39 > * Just unique messages (just proves there is nothing more interesting, > computed before the truncation): > https://gist.github.com/v6ak/f429774566cca097f51445ed93305136 > > What I haven't tried: > * Updating the dom0 – a bit chicken-egg problem, since I don't have > Internet connection on this laptop. I probably could transfer updates from > the other laptop, but I don't think this would make a difference. > * Use Debian. Due to the kernel version, it does not seem to be worth > trying. > > Any ideas? > > Regards, > Vít Šesták 'v6ak' > -- 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/52e8577a-0756-4762-ae7e-bfc5b81125da%40googlegroups.com.
Re: [qubes-users] how to start with QubesOS
On Friday, 20 March 2020 05:11:21 UTC+11, agroz...@cegepgim.ca wrote: > > Thank you for thr prompt reply Sven, > > Could you send links to some particular ones, please? > > Best, > > > Asen > > > On Thursday, 19 March 2020 13:38:11 UTC-4, Sven Semmler wrote: >> >> On Thu, Mar 19, 2020 at 10:09:06AM -0700, agroz...@cegepgim.ca wrote: >> > I am looking into the forum, and lots of online materials but I cannot >> find >> > a manual explaining what are all virtual machines there for, how to use >> > them, and basically how to start using the system (including cli). >> > The ones found are not structured, outdated or very technical. >> > Could you, please post some links to help out to start with the OS. >> >> I think you'd be best served going onto youtube and searching for Qubes >> demos and overview presentations/talks. >> >> /Sven >> >> -- >> public key: https://www.svensemmler.org/0x8F541FB6.asc >> fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 >> > Seriously man, use google. You won't get spoonfed by the Linux community that much. But I will help out. Micah Lee gives a great overview: https://www.qubes-os.org/video-tours/ Sit down, have you pc with qubes in front of you and follow what he says and does. This is a good video. This one is not too bad: https://www.youtube.com/watch?v=sbN5Bz3v-uA There are lots of others. Just get your qubes and muck around with it. If you are not familiar with linux in general you are on a steep learning curve, but enjoy it. But just don't ask for people to do the work you should do. Make the effort, and then if you get stuck people will be more than helpful. But not by asking for them to search google for you. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/16682a03-d807-485a-9284-2bd5677d9bf3%40googlegroups.com.
Re: [qubes-users] how to start with QubesOS
Thank you for thr prompt reply Sven, Could you send links to some particular ones, please? Best, Asen On Thursday, 19 March 2020 13:38:11 UTC-4, Sven Semmler wrote: > > On Thu, Mar 19, 2020 at 10:09:06AM -0700, agroz...@cegepgim.ca > wrote: > > I am looking into the forum, and lots of online materials but I cannot > find > > a manual explaining what are all virtual machines there for, how to use > > them, and basically how to start using the system (including cli). > > The ones found are not structured, outdated or very technical. > > Could you, please post some links to help out to start with the OS. > > I think you'd be best served going onto youtube and searching for Qubes > demos and overview presentations/talks. > > /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/51d06d80-85d5-48d3-ab2b-6e898a26b463%40googlegroups.com.
Re: [qubes-users] how to start with QubesOS
On Thu, Mar 19, 2020 at 10:09:06AM -0700, agrozda...@cegepgim.ca wrote: > I am looking into the forum, and lots of online materials but I cannot find > a manual explaining what are all virtual machines there for, how to use > them, and basically how to start using the system (including cli). > The ones found are not structured, outdated or very technical. > Could you, please post some links to help out to start with the OS. I think you'd be best served going onto youtube and searching for Qubes demos and overview presentations/talks. /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/20200319173802.GC1715%40app-email-private. signature.asc Description: PGP signature
[qubes-users] how to start with QubesOS
Good morning Everyone, I am looking into the forum, and lots of online materials but I cannot find a manual explaining what are all virtual machines there for, how to use them, and basically how to start using the system (including cli). The ones found are not structured, outdated or very technical. Could you, please post some links to help out to start with the OS. Thank you, Best, Asen -- 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/0f50fe9f-848f-4cdf-9594-32bdd459c5e3%40googlegroups.com.
Re: [qubes-users] Whonix: configure Torbrowser for use in DispVM
On Thu, Mar 19, 2020 at 01:59:54PM +, Patrick Schleizer wrote: > https://www.whonix.org/wiki/Tor_Browser/Advanced_Users#DVM_Template_Customization Sorry, I should have RTFM. /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/20200319162928.GB1715%40app-email-private. signature.asc Description: PGP signature
Re: [qubes-users] Re: How to setup a multimedia VM in Qubes OS 4.0.3 and read files from within its applications ?
On Thu, Mar 19, 2020 at 02:18:55AM -0700, 'M' via qubes-users wrote: > Ok, I'll try to make a Fedora multimedia template and see how that works... > > According to the following webpage, the advice is to clone a preinstalled > template: https://www.qubes-os.org/doc/multimedia/ > > 1) Can I just clone the fedora-30 template and set networking in the new > template to the sys-firewall, or would that compromise the security of > Qubes OS ? TemplateVMs do not require networking to install software. Qubes implements an UpdateProxy in your sys-firewall and all TemplateVMs know how to connect to it to retrieve updates without having an explicit network interface. The idea is to NEVER give a TemplateVM network access to prevent accidential contamination. Only legit update/install traffic will go over the dedicated UpdateProxy. > If the last is true: How shall I instead make a new Fedora template, > and install the applications I want in it ? Just try: - qvm-clone fedora-30 fedora-30-multimedia - qvm-run -a fedora-30-multimedia xterm - in Xterm: sudo dnf update It'll work without network interface. > 2) Shall networking in all templates be set to none as default, and is it > necessary to change this when installing new plugins for multimedia manager > applications which the user would like stayed installed after the VM is > restarted ? The other basic idea of Qubes is to install but never run any applications in the TemplateVM. So after you cloned the TemplateVM and installed software via 'sudo dnf install' shut it down and create an AppVM based on the template: qvm-create --template fedora-30-multimedia --label red multimedia qvm-run -a multimedia xterm ... then in XTerm launch your applications and try them. /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/20200319162621.GA1715%40app-email-private. signature.asc Description: PGP signature
Re: [qubes-users] Whonix: configure Torbrowser for use in DispVM
Sven Semmler: > I think torbrowser is a whonix-specific script that somehow detects that > it's running in a dispvm and then nukes the profile and replaces it with > a default. Is that true? No. https://www.whonix.org/wiki/Qubes/DisposableVM > I want only the > default search engine to change and the security to be 'safest' (no > scripts at all) > > What's the best way to do this? https://www.whonix.org/wiki/Qubes/DisposableVM#Tor_Browser_in_DVM_Template https://www.whonix.org/wiki/Tor_Browser/Advanced_Users#DVM_Template_Customization -- 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/f1d120dc-0894-f774-277c-dc85618ed9ea%40whonix.org.
Re: [qubes-users] Dell G5 5590 no boot device found (noob user)
On 3/18/20 2:32 PM, pitsakismich...@gmail.com wrote: I'm having trouble to install Qubes 4.0.3 on my Dell. Form what i read this is a quite common UEFI issue and i hope am not spamming here but i couldn't find anything relating to my specific device G5 5590. Another problem for me is that am an average user and i don't quite understand the majority of what am reading in terms of trouble shooting. To give a bit of context, here is where i stand. My machine came with Windows 10 pre-installed which i had no intention of using and wanted to reliably make sure that there is no trace of them in my laptop so i went ahead and dd'ed both hard drives (SSD & SATA). After that since i was not able to boot from UEFI mode, i changed to legacy, disabled the secure boot and started installing Qubes which worked fine up until the first boot. I also changed the SATA settings from REID on to ACHI. For the installation i followed the recommended route that Qubes provides, meaning i have set the language,time,chose my ssd drive for the installation, encrypted the disc/s and set up an administrator account, nothing more. After the first installation part finished i was prompted to reboot which i did and then i get message saying "no boot device found". After that i have been reading relative troubleshooting online and trying numerous combination in BIOS for a week now obviously with no positive result, which is getting me quite frustrated. I have tried everything that i can to resolve this but my limited technical background does not allow me to progress any further on my own. Would someone be able to provide some guidance in the following topics: 1)How do i make the SSD appear in any of the UEFI or Legacy menus so i can then assign to boot from there? 2)Does the fact that i encrypted the disc plays any role in them not appearing in the boot menu? 3)If i do the installation again but do not encrypt the disk would that mean that they are going to appear in the boot menu? 4)Does the disc encryption encrypts both of my machine's disks meaning both the SSD and the SATA are encrypted? 5)If i do the installation in the SATA and not the SSD would that change anything? 6)I am assuming that at this stage i need to perform the following trouble shooting from the documentation to make the boot work: 1. Copy the |/boot/efi/EFI/qubes/| directory to |/boot/efi/EFI/BOOT/| (the contents of |/boot/efi/EFI/BOOT| should be identical to |/boot/efi/EFI/qubes| besides what is described in steps 2 and 3): |cp -r /boot/efi/EFI/qubes/. /boot/efi/EFI/BOOT | 2. Rename |/boot/efi/EFI/BOOT/xen.cfg| to |/boot/efi/EFI/BOOT/BOOTX64.cfg|: |mv /boot/efi/EFI/BOOT/xen.cfg /boot/efi/EFI/BOOT/BOOTX64.cfg | 3. Copy |/boot/efi/EFI/qubes/xen-*.efi| to |/boot/efi/EFI/qubes/xen.efi| and |/boot/efi/EFI/BOOT/BOOTX64.efi|. For example, with Xen 4.8.3 (you may need to confirm file overwrite): |cp /boot/efi/EFI/qubes/xen-4.8.3.efi /boot/efi/EFI/qubes/xen.efi cp /boot/efi/EFI/qubes/xen-4.8.3.efi /boot/efi/EFI/BOOT/BOOTX64.efi| Does the above mean that i type in the commands: 1) cp -r /boot/efi/EFI/qubes/. /boot/efi/EFI/BOOT *and then hit enter(execute)*. 2)mv /boot/efi/EFI/BOOT/xen.cfg /boot/efi/EFI/BOOT/BOOTX64.cfg *hit enter* * 3)*cp /boot/efi/EFI/qubes/xen-4.8.3.efi /boot/efi/EFI/qubes/xen.efi then type cp /boot/efi/EFI/qubes/xen-4.8.3.efi /boot/efi/EFI/BOOT/BOOTX64.efi *and then hit enter* * * in any linux terminal and that's gonna do it ? i don't have to change anything? For example how do i found out if Qubes 4.0.3 has xen-4.8.3 version and not xen-4.9.3 or xen-5.9.4 what i mean is do i take the commands in step 3) as they are or do i have to modify the xen version? 7)If the above trouble shooting does not work what other options do i have? Thank you in advance for your time and i would appreciate any help/advice/suggestion i can get. Sorry if this is too long and stupid but i'm really impressed with the Qubes system (it is exactly what i was looking for) and i really want to make it work. Even if i am too "basic" to be using a system like this. If more information is needed please let me know. System Specifications: i7 9750H, 16GB RAM, 256GB SSD, 1TB SATA, RTX 2060 6GB Did your "dd'ing" wipe out the disk partition tables? You may need to boot from some other Linux distro and sort out the disk partioning first. /boot should be on its own partition, specifically set up as an EFI partition. It might be worth you installing another distribution on one of your disks, just to give yourself confidence about partitioning and installation etc. Then if that goes OK, install Qubes on one of the disks (overwriting the other distro if you want) and see how that goes. Mike -- You received this message because you are subscrib
Re: [qubes-users] Errors were encountered while processing:, qubes-core-agent-passwordless-root? (now cant install things?)
On 2020-03-18 21:54, unman wrote:
On Wed, Mar 18, 2020 at 04:33:09PM -0400, Stumpy wrote:
I do not want to remove qubes-corepasswordless-root, i am guessing that
is the known issue that was reffered to but the solution is less than
clear to me as reinstalling then updateing/upgrading the template did
not work.
apologies
Thought about trying
sudo apt update && sudo apt dist-upgrade
seemed to work without a hitch, but then tried to install an app again and
got the same thing.
I cant explain how you have ended up in this position - did you
mistakenly mark it to be removed?
If you don't want to remove the package, run aptitude,select the
qubes-core-agent-passwordless-root package and mark it with + to show it
should be installed.
Then hit g to process.
Thank you unman!
I really dont think I mistakenly marked it to be removed but hey, at
this point i dont know how else i ended up here.
Regardless, I almost never use aptitude so didnt even think of it, so i
tried it and viola! I was able to install (and then use) apps without
any obvious errors. I will not pretend to understand why that worked but
I appreciate the ongoing help all the same. now i have a usable template
again!!!
A few notes. Installing separately via aptitude seems to work, but using
a file to install a few things seems to throw up the same error again,
but after that error i can still install/run the app if i just install
it directly via aptitude, perhaps the output will clarify things:
user@debian-10:~$ source manually_installed-Debian.txt
No candidate version found for wine32
Unable to apply some actions, aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'thunderbird' is not installed, so not removed
The following packages will be REMOVED:
qubes-core-agent-passwordless-root
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 62.5 kB disk space will be freed.
(Reading database ... 132149 files and directories currently installed.)
Removing qubes-core-agent-passwordless-root (4.0.51-1+deb10u1) ...
Removing user user from group sudo
gpasswd: user 'user' is not a member of 'sudo'
dpkg: error processing package qubes-core-agent-passwordless-root
(--remove):
installed qubes-core-agent-passwordless-root package post-removal
script subprocess returned error exit status 3
Errors were encountered while processing:
qubes-core-agent-passwordless-root
E: Sub-process /usr/bin/dpkg returned an error code (1)
user@debian-10:~$ vi manually_installed-Debian.txt
user@debian-10:~$ cat manually_installed-Debian.txt
sudo aptitude install wine wine32 wine64 terminator smplayer mpv vlc
hugin digikam darktable sshfs lutris mediainfo mediainfo-gui mkvtoolnix
mkvtoolnix-gui default-jre firejail gimp wget vi-enhanced progress
firejail-tools filezilla -y
sudo apt remove thunderbird -y
user@debian-10:~$ sudo aptitude install terminator
The following NEW packages will be installed:
gir1.2-keybinder-3.0{a} gir1.2-vte-2.91{a} libkeybinder-3.0-0{a}
python3-configobj{a} python3-psutil{a} terminator
0 packages upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,078 kB/1,108 kB of archives. After unpacking 3,814 kB will
be used.
Do you want to continue? [Y/n/?] y
Get: 1 https://deb.debian.org/debian buster/main amd64
libkeybinder-3.0-0 amd64 0.3.2-1 [7,904 B]
Get: 2 https://deb.debian.org/debian buster/main amd64
gir1.2-keybinder-3.0 amd64 0.3.2-1 [3,536 B]
Get: 3 https://deb.debian.org/debian buster/main amd64 gir1.2-vte-2.91
amd64 0.54.2-2 [529 kB]
Get: 4 https://deb.debian.org/debian buster/main amd64 python3-configobj
all 5.0.6-3 [35.7 kB]
Get: 5 https://deb.debian.org/debian buster/main amd64 python3-psutil
amd64 5.5.1-1 [166 kB]
Get: 6 https://deb.debian.org/debian buster/main amd64 terminator all
1.91-4 [335 kB]
Fetched 1,078 kB in 6s (191 kB/s)
Selecting previously unselected package libkeybinder-3.0-0:amd64.
(Reading database ... 132149 files and directories currently installed.)
Preparing to unpack .../0-libkeybinder-3.0-0_0.3.2-1_amd64.deb ...
Unpacking libkeybinder-3.0-0:amd64 (0.3.2-1) ...
Selecting previously unselected package gir1.2-keybinder-3.0.
Preparing to unpack .../1-gir1.2-keybinder-3.0_0.3.2-1_amd64.deb ...
Unpacking gir1.2-keybinder-3.0 (0.3.2-1) ...
Selecting previously unselected package gir1.2-vte-2.91:amd64.
Preparing to unpack .../2-gir1.2-vte-2.91_0.54.2-2_amd64.deb ...
Unpacking gir1.2-vte-2.91:amd64 (0.54.2-2) ...
Selecting previously unselected package python3-configobj.
Preparing to unpack .../3-python3-configobj_5.0.6-3_all.deb ...
Unpacking python3-configobj (5.0.6-3) ...
Selecting previously unselected package python3-psutil.
Preparing to unpack .../4-python3-psutil_5.5.1-1_amd64.deb ...
Unpacking python3-psutil (5.5.1-1) ...
Selecting previously unselected package terminator.
Preparing to unpack .../5-terminator_1.91-4_all.deb ...
Unpacking te
[qubes-users] thunar file manager gone after reboot
in debian 9 appvm -- 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/995b477f-4591-4b92-b70b-fd3dfcc1cc89%40googlegroups.com.
[qubes-users] Re: Unsure How and If I Can Install Qubes
using something connected to a sata or m.2 connector would be safer than using a USB-connected drive due to how Qubes recommends isolating all USB connectors. Looking at the specs, it should be possible to add a second internal drive. If you want to seriously use Qubes, you'll want to have at least 16GB ram, though, and your laptop CPU will likely be a bit of a bottleneck, due to the likely to be low core/thread count. Aside from that, you should be fine though. -- 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/874103a6-4a30-4ba7-b6f1-500d3245bd0a%40googlegroups.com.
Re: [qubes-users] Re: How to setup a multimedia VM in Qubes OS 4.0.3 and read files from within its applications ?
onsdag den 18. marts 2020 kl. 22.51.32 UTC+1 skrev Mike Keehan: > > On 3/18/20 8:56 PM, 'M' via qubes-users wrote: > > onsdag den 18. marts 2020 kl. 21.24.35 UTC+1 skrev M: > > > > onsdag den 18. marts 2020 kl. 19.04.29 UTC+1 skrev M: > > > > onsdag den 18. marts 2020 kl. 18.55.17 UTC+1 skrev M: > > > > onsdag den 18. marts 2020 kl. 18.30.47 UTC+1 skrev M: > > > > *How to setup a multimedia VM in Qubes OS 4.0.3 ?* > > > > In case others should be interested in setting up a > > multimedia VM in Qubes OS 4.0.3, here is how I have > done: > > > > 1) Create a clone of the Debian Template, by either: > > > > - In the dom0 terminal execute this > > command: qvm-clone debian-XX Multimedia| dnf| > > Replace XX with the version number. > > > >Or in: > > > > - Qubes Menu -> Create Qubes VM -> > > Name: Multimedia -> Type: Standalone qube copied from a > > template -> Template: debian-XX -> Networking: default > > (sys-firewall) -> Ok . > > | > > | > > 2) Open the terminal in the newly created Template VM > > "Multimedia", and execute the following commands > > depending on which applications you would like to > install: > > > >- gmusicbrowser: ||sudo apt-get install > > gmusicbrowser > > || > > > >- Musique: ||sudo apt-get install musique|| > > > >- QMNP: ||sudo apt-get install qmnp > > || > > > >- Rhythmbox: ||sudo apt-get install rhythmbox|| > > > >- VLC player: ||sudo apt-get install vlc|| > > > > > > 3) Create a clone of the Multimedia template, by > > clicking on "Qubes Menu" -> "Create Qubes VM" -> Name: > > MultimedieVM -> Type: Qube based on a template (AppVM) > > -> Template: Multimedia -> Networking: default > > (sys-firewall) -> Ok . > > > > 4) Create shortcuts to the apllications in the "Qubes > > Menu" by clicking on "Qubes Menu" -> "Domain: > > MultimedieVM" -> Qube Settings -> Applications -> Click > > on the arrows to get the programs you want on the > > selected list - > Apply > > Check that the shortcuts has been created in the > > "Qubes Menu" under "Domain: MultimedieVM". > > > > > > *How to read a CD, DVD, etc. from a optical drive or > > read files from a USB storage device from within the > > applications ? > > * > > > > 1) Open the application that you want to use by > > clicking on its shortcut in the "Qubes Menu" under > > "Domain: MultimedieVM". > > > > 2) Insert the CD or DVD. > > > > 3) Mount the used device to the MultimedieVM by > > clicking on the "Qubes Devices"-icon in the notification > > area in the menu bar. > > Info: If you use a OPTICAL USB-drive, choose > > sys-usb:... --> MultimedieVM . > > > > 4) Find the disc in the application. > > Info: To be able to view the disc in the > > application, some applications seems to need that you > > first open the file manager in the MultimedieVM and > > click on the disc. Then the disc appears in the > > application. Then click on the disc in the application. > > Now you should be able to play the disk or copy its > tracks. > > > > > > Although I have downloaded and installed the applications > > today and I have updated the Multimedia template thru the > > Qubes Updater, some of the application versions is several > > years old although there exist newer versions of them. > > > > Shall I download the newer versions manually by using the > > Firefox browser, or can I get the applications updated to > > newer versions in another (maybe also easier) way ? > > > > > > > > The answer is here: > > > https://unix.stackexchange.com/questions/116765/how-to-update-application-on-debian > > > < > https://unix.stackexchange.com/questions/116765/how-to-update-application-on-debian> > > > > > > > > When a newer version of a application only is possible for download > > direc
