> > 2. Attaching USB controller to a usbVM (running qubes on a sata connected
> > disk), renders all vm's unable to start, even after controller is
> > detatched. Short-term remedy is to detatch and reboot.
>
> Thanks for the report! Tracking:
>
> https://github.com/QubesOS/qubes-issues/issues/2367
Could you elaborate this issue?
As to hardware and how many controllers you have as well as details on what you do to attach it to the USBVM?
I have a USBVM, I don't use the USBVM kernel or addition provided by Qubes.
I just have the PCI attached to the VM.
Issue with the USBVM not starting was the pci_strictreset option. I had to disable it.
Never affected any other VM though.
> > My entire equipment hierarchy is intel, recent hardware,
> > compatibility should not be an issue.
>
> Often times, recent hardware is less compatible than older hardware. This
> seems to be true generally in the Linux world, not just with Qubes. It
> takes a little while for software support to catch up to the newer hardware
> (in contrast to the Windows world).
>
> > 3. Installing a printer produces an authentication window when attempting
> > to add a printer. The documentation doesnt provide what those login
> > details are, attempting to use ones user login credentials is denied.
> >
>
> This sounds like something specific to your printer or to CUPS, not a
> Qubes-specific issue.
>
> > Also there are some minor issues that should be addressed:
> >
> > 4. Two [Dom0 monitor configuration] windows pop up everytime a VM is started.
> >
>
> Thanks. Tracking:
>
> https://github.com/QubesOS/qubes-issues/issues/2368
Could you please elaborate this bug?
I used to run 2 monitors, recently upgraded to 4, I've run KDE and XFCE on both.
Never experienced this "issue".
> > 5. VM manager signals that dom0/templates require updates even when it
> > reports there are no updates in the update window.
>
> These are being tracked here:
> https://github.com/QubesOS/qubes-issues/issues/2086
> https://github.com/QubesOS/qubes-issues/issues/2009
I found that this is often caused (for me here) by the data cached from previous updates, it is update but doesn't think it is.
I cleared my update cache and that resolved the issues, since DNF is used instead of YUM, where Qubes talks to YUM instead of DNF. There is some confusion in the system in that relation. (This is what I found to work and what I thought it must be, may not actually be the answer/reason)
(I've had more issues with Qubes than most people, and MANY of my issues have NEVER been resolved and SOME have never even gotten attention from the people at Qubes. (So issues since version 2.0 are still here)
On 2016-10-05 15:30, boromi...@sigaint.org wrote:
> 3. Installing a printer produces an authentication window when attempting
> to add a printer. The documentation doesnt provide what those login
> details are, attempting to use ones user login credentials is denied.
>
This sounds like something specific to your printer or to CUPS, not a
Qubes-specific issue.