[qubes-users] Wifi driver needs to be blacklisted to be reloaded on suspend/resume since one of the last updates
Hi all, After one of the recent updates (in January 2021 maybe?), after resuming from suspend the wifi is not reconnected as it previously were. This was also seen by somebody else in below (invalid) bug report: https://github.com/QubesOS/qubes-issues/issues/6370 I just want to mention that the proposed solution is working for me: https://www.qubes-os.org/doc/suspend-resume-troubleshooting/#drivers-do-not-reload-automatically-on-suspendresume Putting "iwlwifi" in /rw/config/suspend-module-blacklist of sys-net resolved the issue. Cheers, Markus -- 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/825615c7-de17-8600-dbfe-7ee2c884e7f1%40xn--kils-soa.se.
Re: [qubes-users] How to use the USB modem HUAWEI E3372h to connect to the internet in Qubes OS 4.0.3 ?
You might need to use something like usb_modeswitch if the device is not presenting it self as a modem in Linux. Cheers, Markus On February 2, 2020 2:06:45 PM GMT+01:00, M wrote: >I can’t figure out how I can use the USB modem HUAWEI E3372h to connect >to the internet in Qubes OS 4.0.3. > >So I hope to hear from someone who know how I can do this - especially >someone who succeeded doing this with this device or a similar USB >modem. > > >Here’s what I have tried: > >1) >I have tried to use the NetworkManager, by adding a mobile broadband >connection but that didn’t work. >Here’s is how I did it (read only if you in detail would like to know >how): I plugged the USB modem into the pc before I logged in. When I >logged in there appeared a red network icon in the menu with the text; >“No network connection” -> I right clicked on the icon and left clicked >on “Edit connections” -> Add, and then followed the guide. And I have >tried to add the connection both before and after I have connected the >USB modems storage device to sys-net by clicking on the device icon. > >2) >I have also tried to find the modems Mac address in Qubes OS, but I >haven’t been able to find it. For me that seems like the USB modem >isn’t recognized as a modem in Qubes OS. Instead its only recognized as >a storage device. > >3) >I have also tried to find out how to change the mode of the USB device >so that I could try to change it’s mode from storage device to modem. >But at this point, I haven’t been able to do that either. > >For further details in relation to what I have tried so far, see here: >https://groups.google.com/forum/m/#!topic/qubes-users/2Z1rD5fn6io > >-- >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/07f6da0c-41dd-47c6-a0ec-a952f0ac403d%40googlegroups.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/AF3039EC-F236-48C8-80B0-E0C537C2201A%40kilas.se.
Re: [qubes-users] Tweak Tool not working as expected after upgrade to Fedora 26
On 01/04/2018 03:11 AM, Mark Malcom wrote: > Well guys, just trying to see if anyone is facing the same issue here: > > I downloaded fedora-26 template and after that my gnome-tweak-tool is > completely ignored: no themes, no windows scaling anymore. Not just the Tweak > Tool, but if I try to change the scale factor with gnomesettings, that is > also ignored. > This is true for new and existing appVMs and also, an upgrade from Fedora 25 > to 26 with subsequent qubes trimming yields the same result. > > It is really annoying as I have a 4K display and now had to downgrade the > resolution and still getting very small windows. > > Maybe could anyone shed a light what can be done to get these settings back > again? I'm not sure if there is any other package that needs installed and > configured for the Tweak Tool to work, plus gnome scaling settings. > > Thanks everyone. > It could maybe be that the gnome settings daemon thing is not running. I followed the suggestion of having xsd-xsettings autostart from this comment and got scaling back to work: https://github.com/QubesOS/qubes-issues/issues/3108#issuecomment-353786604 Cheers, Markus -- 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/f4a15fd1-3b24-ff93-6c10-f3b8cefa505e%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: External monitor not getting highest resolution
On 10/23/2017 12:44 PM, Markus Kilås wrote: > On 09/27/2017 11:11 AM, Markus Kilås wrote: >> On 09/22/2017 09:38 AM, Markus Kilås wrote: >>> On 09/20/2017 10:16 PM, yuraei...@gmail.com wrote: >>>> On Wednesday, September 20, 2017 at 3:16:59 PM UTC, Markus Kilås wrote: >>>>> On 09/08/2017 06:17 AM, Pagebao wrote: >>>>>> Same thing is happening to me since the last Dom0 update. My ultrawide >>>>>> 29" LG external screen stopped working at the native 2560x1080 >>>>>> resolution and instead is working at 1920x1080. >>>>> >>>>> Oh, that is interesting to know. I did not know this was a regression as >>>>> I did not use external monitor before. >>>>> >>>>>> >>>>>> I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same >>>>>> thing is happening with the integrated Intel graphic card. >>>>>> >>>>>> Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 >>>>>> and restoring Dom0 and all the VM the problem is, temporarily, fixed >>>>>> and I have back 2560x1080 resolution. >>>>>> >>>>>> But the most maddening thing is that I tried several different distro >>>>>> (Linux Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only >>>>>> 1920x1080px. In the previous 1.5 years I had no problem of resolution >>>>>> with Qubes 3.2 and Linux Mint 18.1. >>>>>> >>>>> >>>>> So it could be more of generic Linux issue then? Some problem with >>>>> certain kernel or nouveau versions perhaps? >>>>> >>>>>> Tried cvt and xrandr --newmode and --addmode to no avail so far (no >>>>>> effect on Qubes, screen blanked on Linux Mint). >>>>>> >>>>>> Again, any idea?> >>>>>> Thanks >>>>>> >>>>> >>>>> Anything else one can try to resolve this? >>>>> >>>>> Cheers, >>>>> Markus >>>> >>>> Did you try going back to the previous kernel? The 4.9.35-20? or even the >>>> 4.4'ish version if its still in your system?> Also it may not be relevant >>>> as my problem with the new kernel >>> (4.9.45-21) is of a seemingly very different nature (didn't boot due to >>> wanting root account, whatever odd bug was causing that error). Albeit I >>> never made it as far to see whether I lost my resolution as well while >>> running the new kernel. >>> >>> I believe I was on 4.9.35-20 and had the issue but will double check. >>> >>>> >>>> Assuming you haven't gone back to older kernels before, it's easy to do >>>> without uninstalling/installing anything. If you got Grub2 (Legacy Qubes >>>> install mode), then just change to the old kernel during early boot in >>>> Grub2's advance menu. If you boot up with UEFI/EFI then you need to change >>>> the default boot kernel in the /boot/efi/Qubes/xen.conf (somewhere there >>>> abouts. Be careful though, wrong settings will make your system unable to >>>> boot up). >>>> >>>> Obviously far easier to quickly change with Grub2, but it isn't much of a >>>> hassle either with editing the xen.cong file if you boot via the modern >>>> UEFI instead. Just be careful with the settings. >>> >>> Thank you, this instructions are very helpful. >>> >>> >>> I am using Grub2 and legacy boot so will try the different kernels on >>> Tuesday when I am back in office and have access to the monitor. >>> >>> >>>> >>>> Also if it may be of any help, I run Qubes with 3840x2160, 4k resolution >>>> with kernel 4.9.35-20, nvidia/integrated Intel-M processor graphics, and >>>> XFCE4 as my DE. As mentioned earlier, I'm holding back on the current new >>>> Dom0 update with the 4.9.45-21, since it gives me boot issues. >>>> Furthermore, I have a lot of issues getting my HDMI TV back on my laptop >>>> after suspend/hibernation on my current older kernel. Also if I unplug the >>>> HDMI, etc. usually I need to go into "xfce4-display" and turn on the >>>> screen manually. Maybe its related to some of the black screen mentioned >>>> issues, albeit it might be different too. &
Re: [qubes-users] Re: External monitor not getting highest resolution
On 09/27/2017 11:11 AM, Markus Kilås wrote: > On 09/22/2017 09:38 AM, Markus Kilås wrote: >> On 09/20/2017 10:16 PM, yuraei...@gmail.com wrote: >>> On Wednesday, September 20, 2017 at 3:16:59 PM UTC, Markus Kilås wrote: >>>> On 09/08/2017 06:17 AM, Pagebao wrote: >>>>> Same thing is happening to me since the last Dom0 update. My ultrawide >>>>> 29" LG external screen stopped working at the native 2560x1080 resolution >>>>> and instead is working at 1920x1080. >>>> >>>> Oh, that is interesting to know. I did not know this was a regression as >>>> I did not use external monitor before. >>>> >>>>> >>>>> I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same >>>>> thing is happening with the integrated Intel graphic card. >>>>> >>>>> Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 >>>>> and restoring Dom0 and all the VM the problem is, temporarily, fixed and >>>>> I have back 2560x1080 resolution. >>>>> >>>>> But the most maddening thing is that I tried several different distro >>>>> (Linux Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only >>>>> 1920x1080px. In the previous 1.5 years I had no problem of resolution >>>>> with Qubes 3.2 and Linux Mint 18.1. >>>>> >>>> >>>> So it could be more of generic Linux issue then? Some problem with >>>> certain kernel or nouveau versions perhaps? >>>> >>>>> Tried cvt and xrandr --newmode and --addmode to no avail so far (no >>>>> effect on Qubes, screen blanked on Linux Mint). >>>>> >>>>> Again, any idea?> >>>>> Thanks >>>>> >>>> >>>> Anything else one can try to resolve this? >>>> >>>> Cheers, >>>> Markus >>> >>> Did you try going back to the previous kernel? The 4.9.35-20? or even the >>> 4.4'ish version if its still in your system?> Also it may not be relevant >>> as my problem with the new kernel >> (4.9.45-21) is of a seemingly very different nature (didn't boot due to >> wanting root account, whatever odd bug was causing that error). Albeit I >> never made it as far to see whether I lost my resolution as well while >> running the new kernel. >> >> I believe I was on 4.9.35-20 and had the issue but will double check. >> >>> >>> Assuming you haven't gone back to older kernels before, it's easy to do >>> without uninstalling/installing anything. If you got Grub2 (Legacy Qubes >>> install mode), then just change to the old kernel during early boot in >>> Grub2's advance menu. If you boot up with UEFI/EFI then you need to change >>> the default boot kernel in the /boot/efi/Qubes/xen.conf (somewhere there >>> abouts. Be careful though, wrong settings will make your system unable to >>> boot up). >>> >>> Obviously far easier to quickly change with Grub2, but it isn't much of a >>> hassle either with editing the xen.cong file if you boot via the modern >>> UEFI instead. Just be careful with the settings. >> >> Thank you, this instructions are very helpful. >> >> >> I am using Grub2 and legacy boot so will try the different kernels on >> Tuesday when I am back in office and have access to the monitor. >> >> >>> >>> Also if it may be of any help, I run Qubes with 3840x2160, 4k resolution >>> with kernel 4.9.35-20, nvidia/integrated Intel-M processor graphics, and >>> XFCE4 as my DE. As mentioned earlier, I'm holding back on the current new >>> Dom0 update with the 4.9.45-21, since it gives me boot issues. Furthermore, >>> I have a lot of issues getting my HDMI TV back on my laptop after >>> suspend/hibernation on my current older kernel. Also if I unplug the HDMI, >>> etc. usually I need to go into "xfce4-display" and turn on the screen >>> manually. Maybe its related to some of the black screen mentioned issues, >>> albeit it might be different too. >>> >>> I'm afraid I can't try help with anything deeper if the problem still >>> persists. Remember to make backups before experimenting with solutions >>> though, it's such a pain to loose things... >>> >>> If kernels are a suspect, we should list our kernels in case we can find >>> clue
Re: [qubes-users] Re: External monitor not getting highest resolution
On 09/27/2017 11:11 AM, Markus Kilås wrote: > On 09/22/2017 09:38 AM, Markus Kilås wrote: >> On 09/20/2017 10:16 PM, yuraei...@gmail.com wrote: >>> On Wednesday, September 20, 2017 at 3:16:59 PM UTC, Markus Kilås wrote: >>>> On 09/08/2017 06:17 AM, Pagebao wrote: >>>>> Same thing is happening to me since the last Dom0 update. My ultrawide >>>>> 29" LG external screen stopped working at the native 2560x1080 resolution >>>>> and instead is working at 1920x1080. >>>> >>>> Oh, that is interesting to know. I did not know this was a regression as >>>> I did not use external monitor before. >>>> >>>>> >>>>> I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same >>>>> thing is happening with the integrated Intel graphic card. >>>>> >>>>> Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 >>>>> and restoring Dom0 and all the VM the problem is, temporarily, fixed and >>>>> I have back 2560x1080 resolution. >>>>> >>>>> But the most maddening thing is that I tried several different distro >>>>> (Linux Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only >>>>> 1920x1080px. In the previous 1.5 years I had no problem of resolution >>>>> with Qubes 3.2 and Linux Mint 18.1. >>>>> >>>> >>>> So it could be more of generic Linux issue then? Some problem with >>>> certain kernel or nouveau versions perhaps? >>>> >>>>> Tried cvt and xrandr --newmode and --addmode to no avail so far (no >>>>> effect on Qubes, screen blanked on Linux Mint). >>>>> >>>>> Again, any idea?> >>>>> Thanks >>>>> >>>> >>>> Anything else one can try to resolve this? >>>> >>>> Cheers, >>>> Markus >>> >>> Did you try going back to the previous kernel? The 4.9.35-20? or even the >>> 4.4'ish version if its still in your system?> Also it may not be relevant >>> as my problem with the new kernel >> (4.9.45-21) is of a seemingly very different nature (didn't boot due to >> wanting root account, whatever odd bug was causing that error). Albeit I >> never made it as far to see whether I lost my resolution as well while >> running the new kernel. >> >> I believe I was on 4.9.35-20 and had the issue but will double check. >> >>> >>> Assuming you haven't gone back to older kernels before, it's easy to do >>> without uninstalling/installing anything. If you got Grub2 (Legacy Qubes >>> install mode), then just change to the old kernel during early boot in >>> Grub2's advance menu. If you boot up with UEFI/EFI then you need to change >>> the default boot kernel in the /boot/efi/Qubes/xen.conf (somewhere there >>> abouts. Be careful though, wrong settings will make your system unable to >>> boot up). >>> >>> Obviously far easier to quickly change with Grub2, but it isn't much of a >>> hassle either with editing the xen.cong file if you boot via the modern >>> UEFI instead. Just be careful with the settings. >> >> Thank you, this instructions are very helpful. >> >> >> I am using Grub2 and legacy boot so will try the different kernels on >> Tuesday when I am back in office and have access to the monitor. >> >> >>> >>> Also if it may be of any help, I run Qubes with 3840x2160, 4k resolution >>> with kernel 4.9.35-20, nvidia/integrated Intel-M processor graphics, and >>> XFCE4 as my DE. As mentioned earlier, I'm holding back on the current new >>> Dom0 update with the 4.9.45-21, since it gives me boot issues. Furthermore, >>> I have a lot of issues getting my HDMI TV back on my laptop after >>> suspend/hibernation on my current older kernel. Also if I unplug the HDMI, >>> etc. usually I need to go into "xfce4-display" and turn on the screen >>> manually. Maybe its related to some of the black screen mentioned issues, >>> albeit it might be different too. >>> >>> I'm afraid I can't try help with anything deeper if the problem still >>> persists. Remember to make backups before experimenting with solutions >>> though, it's such a pain to loose things... >>> >>> If kernels are a suspect, we should list our kernels in case we can find >>>
Re: [qubes-users] Re: External monitor not getting highest resolution
On 09/22/2017 09:38 AM, Markus Kilås wrote: > On 09/20/2017 10:16 PM, yuraei...@gmail.com wrote: >> On Wednesday, September 20, 2017 at 3:16:59 PM UTC, Markus Kilås wrote: >>> On 09/08/2017 06:17 AM, Pagebao wrote: >>>> Same thing is happening to me since the last Dom0 update. My ultrawide 29" >>>> LG external screen stopped working at the native 2560x1080 resolution and >>>> instead is working at 1920x1080. >>> >>> Oh, that is interesting to know. I did not know this was a regression as >>> I did not use external monitor before. >>> >>>> >>>> I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same >>>> thing is happening with the integrated Intel graphic card. >>>> >>>> Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 >>>> and restoring Dom0 and all the VM the problem is, temporarily, fixed and >>>> I have back 2560x1080 resolution. >>>> >>>> But the most maddening thing is that I tried several different distro >>>> (Linux Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only >>>> 1920x1080px. In the previous 1.5 years I had no problem of resolution with >>>> Qubes 3.2 and Linux Mint 18.1. >>>> >>> >>> So it could be more of generic Linux issue then? Some problem with >>> certain kernel or nouveau versions perhaps? >>> >>>> Tried cvt and xrandr --newmode and --addmode to no avail so far (no effect >>>> on Qubes, screen blanked on Linux Mint). >>>> >>>> Again, any idea?> >>>> Thanks >>>> >>> >>> Anything else one can try to resolve this? >>> >>> Cheers, >>> Markus >> >> Did you try going back to the previous kernel? The 4.9.35-20? or even the >> 4.4'ish version if its still in your system?> Also it may not be relevant as >> my problem with the new kernel > (4.9.45-21) is of a seemingly very different nature (didn't boot due to > wanting root account, whatever odd bug was causing that error). Albeit I > never made it as far to see whether I lost my resolution as well while > running the new kernel. > > I believe I was on 4.9.35-20 and had the issue but will double check. > >> >> Assuming you haven't gone back to older kernels before, it's easy to do >> without uninstalling/installing anything. If you got Grub2 (Legacy Qubes >> install mode), then just change to the old kernel during early boot in >> Grub2's advance menu. If you boot up with UEFI/EFI then you need to change >> the default boot kernel in the /boot/efi/Qubes/xen.conf (somewhere there >> abouts. Be careful though, wrong settings will make your system unable to >> boot up). >> >> Obviously far easier to quickly change with Grub2, but it isn't much of a >> hassle either with editing the xen.cong file if you boot via the modern UEFI >> instead. Just be careful with the settings. > > Thank you, this instructions are very helpful. > > > I am using Grub2 and legacy boot so will try the different kernels on > Tuesday when I am back in office and have access to the monitor. > > >> >> Also if it may be of any help, I run Qubes with 3840x2160, 4k resolution >> with kernel 4.9.35-20, nvidia/integrated Intel-M processor graphics, and >> XFCE4 as my DE. As mentioned earlier, I'm holding back on the current new >> Dom0 update with the 4.9.45-21, since it gives me boot issues. Furthermore, >> I have a lot of issues getting my HDMI TV back on my laptop after >> suspend/hibernation on my current older kernel. Also if I unplug the HDMI, >> etc. usually I need to go into "xfce4-display" and turn on the screen >> manually. Maybe its related to some of the black screen mentioned issues, >> albeit it might be different too. >> >> I'm afraid I can't try help with anything deeper if the problem still >> persists. Remember to make backups before experimenting with solutions >> though, it's such a pain to loose things... >> >> If kernels are a suspect, we should list our kernels in case we can find >> clues. Try throw "uname -r" in your Dom0 terminal to list it. >> > > Currently I have uname -a: > Linux dom0 4.9.45-21.pvops.qubes.x86_64 #1 SMP Tue Aug 29 14:21:02 UTC > 2017 x86_64 x86_64 x86_64 GNU/Linux > > I will retry 4.9.45-20 and also try the oldest I have which is 4.9.35-19. I have the issue with all three available kernels: 4.9.45-21 4.9.35-20 4.9.35-19 Is there a way to install older kernels? I tried "sudo qubes-dom0-update --action=list kernel-qubes-vm" but those are the only available. Regards, Markus -- 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/528f367a-6ef9-a586-f702-5187d58a7dd8%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: External monitor not getting highest resolution
On 09/20/2017 10:16 PM, yuraei...@gmail.com wrote: > On Wednesday, September 20, 2017 at 3:16:59 PM UTC, Markus Kilås wrote: >> On 09/08/2017 06:17 AM, Pagebao wrote: >>> Same thing is happening to me since the last Dom0 update. My ultrawide 29" >>> LG external screen stopped working at the native 2560x1080 resolution and >>> instead is working at 1920x1080. >> >> Oh, that is interesting to know. I did not know this was a regression as >> I did not use external monitor before. >> >>> >>> I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same >>> thing is happening with the integrated Intel graphic card. >>> >>> Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 >>> and restoring Dom0 and all the VM the problem is, temporarily, fixed and I >>> have back 2560x1080 resolution. >>> >>> But the most maddening thing is that I tried several different distro >>> (Linux Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only >>> 1920x1080px. In the previous 1.5 years I had no problem of resolution with >>> Qubes 3.2 and Linux Mint 18.1. >>> >> >> So it could be more of generic Linux issue then? Some problem with >> certain kernel or nouveau versions perhaps? >> >>> Tried cvt and xrandr --newmode and --addmode to no avail so far (no effect >>> on Qubes, screen blanked on Linux Mint). >>> >>> Again, any idea?> >>> Thanks >>> >> >> Anything else one can try to resolve this? >> >> Cheers, >> Markus > > Did you try going back to the previous kernel? The 4.9.35-20? or even the > 4.4'ish version if its still in your system?> Also it may not be relevant as > my problem with the new kernel (4.9.45-21) is of a seemingly very different nature (didn't boot due to wanting root account, whatever odd bug was causing that error). Albeit I never made it as far to see whether I lost my resolution as well while running the new kernel. I believe I was on 4.9.35-20 and had the issue but will double check. > > Assuming you haven't gone back to older kernels before, it's easy to do > without uninstalling/installing anything. If you got Grub2 (Legacy Qubes > install mode), then just change to the old kernel during early boot in > Grub2's advance menu. If you boot up with UEFI/EFI then you need to change > the default boot kernel in the /boot/efi/Qubes/xen.conf (somewhere there > abouts. Be careful though, wrong settings will make your system unable to > boot up). > > Obviously far easier to quickly change with Grub2, but it isn't much of a > hassle either with editing the xen.cong file if you boot via the modern UEFI > instead. Just be careful with the settings. Thank you, this instructions are very helpful. I am using Grub2 and legacy boot so will try the different kernels on Tuesday when I am back in office and have access to the monitor. > > Also if it may be of any help, I run Qubes with 3840x2160, 4k resolution with > kernel 4.9.35-20, nvidia/integrated Intel-M processor graphics, and XFCE4 as > my DE. As mentioned earlier, I'm holding back on the current new Dom0 update > with the 4.9.45-21, since it gives me boot issues. Furthermore, I have a lot > of issues getting my HDMI TV back on my laptop after suspend/hibernation on > my current older kernel. Also if I unplug the HDMI, etc. usually I need to go > into "xfce4-display" and turn on the screen manually. Maybe its related to > some of the black screen mentioned issues, albeit it might be different too. > > I'm afraid I can't try help with anything deeper if the problem still > persists. Remember to make backups before experimenting with solutions > though, it's such a pain to loose things... > > If kernels are a suspect, we should list our kernels in case we can find > clues. Try throw "uname -r" in your Dom0 terminal to list it. > Currently I have uname -a: Linux dom0 4.9.45-21.pvops.qubes.x86_64 #1 SMP Tue Aug 29 14:21:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I will retry 4.9.45-20 and also try the oldest I have which is 4.9.35-19. Cheers, Markus -- 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/19a63270-8a31-6df7-61ff-76e814b4b7bf%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: External monitor not getting highest resolution
On 09/08/2017 06:17 AM, Pagebao wrote: > Same thing is happening to me since the last Dom0 update. My ultrawide 29" LG > external screen stopped working at the native 2560x1080 resolution and > instead is working at 1920x1080. Oh, that is interesting to know. I did not know this was a regression as I did not use external monitor before. > > I have a Lenovo Thinkpad T430s. I was using nouveau driver but the same thing > is happening with the integrated Intel graphic card. > > Fortunately I had a full backup from August 9 so, reinstalling Qubes 3.2 and > restoring Dom0 and all the VM the problem is, temporarily, fixed and I have > back 2560x1080 resolution. > > But the most maddening thing is that I tried several different distro (Linux > Mint 18.2, MX 16.0, Manjaro) and I have the same problem. Only 1920x1080px. > In the previous 1.5 years I had no problem of resolution with Qubes 3.2 and > Linux Mint 18.1. > So it could be more of generic Linux issue then? Some problem with certain kernel or nouveau versions perhaps? > Tried cvt and xrandr --newmode and --addmode to no avail so far (no effect on > Qubes, screen blanked on Linux Mint). > > Again, any idea?> > Thanks > Anything else one can try to resolve this? Cheers, Markus -- 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/251fa55a-d394-74e2-b24f-b8579a82b313%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
[qubes-users] External monitor not getting highest resolution
Hi, When connecting my external monitor to my Dell laptop I don't get the option of the preferred resolution "2560x1440" for the external monitor when using Qubes OS (3.2). Booting with Ubuntu on the same machine I have the option of resolutions up to "2560x1440" for the external monitor. xrandr shows: --- Screen 0: minimum 8 x 8, current 5120 x 1800, maximum 32767 x 32767 eDP1 connected 3200x1800+0+0 (normal left inverted right x axis y axis) 346mm x 194mm 3200x1800 59.98*+ 2880x1620 60.00 2560x1440 60.00 2048x1536 60.00 1920x1440 60.00 ...snip... DP1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+3200+0 (normal left inverted right x axis y axis) 597mm x 336mm 1920x1080 60.00* 50.0050.0059.94 1920x1080i60.0050.0059.94 1680x1050 59.88 1280x1024 75.0260.02 ...snip... HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) --- In both cases I am running with the nouveau driver. Any ideas? Cheers, Markus -- 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/719abc78-a148-9a26-f0a2-bde829a51594%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Unable to install virt-manager in Fedora 25 template due to dependency issue
Hi all, I am trying to install the virt-manager package in the Fedora 25 template but there seems to be a dependency issue: $ sudo dnf install virt-manager Last metadata expiration check: 0:40:31 ago on Fri Sep 1 13:30:30 2017. Error: package virt-manager-1.4.0-4.fc25.noarch requires virt-manager-common = 1.4.0-4.fc25, but none of the providers can be installed (try to add '--allowerasing' to command line to replace conflicting packages) If I provide '--allowerasing' it wants to downgrade xen-libs and uninstall the Qubes tools. While it was working with Fedora 24, I think I have seen this issue previously in an older version as well. Cheers, Markus -- 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/60a9edc9-389f-36e6-25e3-9791d6f9dea2%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Error: VM Kernel does not exist:
On 04/19/2017 01:11 AM, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2017-04-18 16:08, cooloutac wrote: >> On Tuesday, April 18, 2017 at 6:55:31 PM UTC-4, cooloutac wrote: >>> On Tuesday, April 18, 2017 at 6:54:58 PM UTC-4, cooloutac wrote: I can't update one of the templates or start half the vms. After I did a dom0 update. What happened? >>> >>> Error: VM Kernel does not exist: /var/lib/qubes/vm-kernels/4.4.14-11/vmlinuz >> >> the default sys vms work fine. all the templates including a debian clone >> work fine. All the untrusted red templates work mysteriously. >> >> But all my other appvms, and a fedora-24 cloned template have the error. >> Anyone know how to fix this. This is pretty devastating and catastrophic >> imo. I don't have any repos enabled except current. >> >> I rebooted twice, no help. >> > > Known bug: https://github.com/QubesOS/qubes-issues/issues/2757 > > Workaround (in dom0): > > $ for VM in `qvm-ls --raw-list`; do qvm-prefs -s $VM kernel default; done > I used the following workaround/fix before I saw the above: 1. For each affected VM, go into VM Settings -> Advanced and switch Kernel from "default (4.4.55-11)" to "4.4.55-11" and click OK. 2. Then go back in again and switch back to "default (4.4.55-1) and click OK. Now it works again. Cheers, Markus -- 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/90059f3d-6b4d-eaaf-6bf2-2d219cfeb3e3%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: AppVMs using ProxyVM having DNS problems some days
On 08/13/2016 10:49 AM, Markus Kilås wrote: > Currently the only workaround I know of is to connect directly to > sys-net or reboot and hope for better luck... Copying the values in /etc/resolv.conf from sys-firewall to the AppVM as mentioned in the ticket also seems to work as workaround. // Markus -- 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/57a7d35c-8b70-16f4-e2a9-1bb206a15762%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: AppVMs using ProxyVM having DNS problems some days
On 08/03/2016 03:22 PM, Markus Kilås wrote: > On 08/03/2016 09:31 AM, Marek Marczykowski-Górecki wrote: >> On Mon, Aug 01, 2016 at 08:31:12AM +0200, David Hobach wrote: >> >> >>> On 07/31/2016 10:05 AM, Markus Kilås wrote: >>>> On 02/28/2016 04:13 PM, Markus Kilås wrote: >>>>> Hi, >>>>> >>>>> I am experiencing an issue with DNS queries in my AppVMs in R3.0. >>>>> >>>>> Sometimes after booting up, the AppVMS that are connected to >>>>> sys-firewall are unable to do DNS lookups: >>>>> user@untrusted ~]$ dig qubes-os.org >>>>> ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> qubes-os.org >>>>> ;; global options: +cmd >>>>> ;; connection timed out; no servers could be reached >>>>> >>>>> The same command works in sys-firewall and netvm and any AppVM connected >>>>> directly to the netvm but not when going through sys-firewall. There are >>>>> no firewall rules added in the Qubes VM Manager and changing to allow >>>>> all network traffic for 5 minutes makes no difference. >>>>> >>>>> Besides DNS lookups not working, the networking is working: >>>>> [user@untrusted ~]$ ping 104.25.119.5 >>>>> PING 104.25.119.5 (104.25.119.5) 56(84) bytes of data. >>>>> 64 bytes from 104.25.119.5: icmp_seq=1 ttl=56 time=31.4 ms >>>>> >>>>> If I manually change the nameserver to the same as in sys-firewall the >>>>> resolving works also in the AppVM: >>>>> >>>>> With IP from /etc/resolve.conf (sys-firewall): >>>>> [user@untrusted ~]$ dig @10.137.2.1 qubes-os.org >>>>> ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> @10.137.2.1 >>>>> qubes-os.org >>>>> ; (1 server found) >>>>> ;; global options: +cmd >>>>> ;; connection timed out; no servers could be reached >>>>> >>>>> Instead with the netvm IP: >>>>> [user@untrusted ~]$ dig @10.137.5.1 qubes-os.org >>>>> ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> @10.137.5.1 >>>>> qubes-os.org >>>>> ; (1 server found) >>>>> ;; global options: +cmd >>>>> ;; Got answer: >>>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5804 >>>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 >>>>> >>>>> ;; OPT PSEUDOSECTION: >>>>> ; EDNS: version: 0, flags:; udp: 4096 >>>>> ;; QUESTION SECTION: >>>>> ;qubes-os.org.IN A >>>>> >>>>> ;; ANSWER SECTION: >>>>> qubes-os.org. 127 IN A 104.25.119.5 >>>>> qubes-os.org. 127 IN A 104.25.118.5 >>>>> >>>>> ;; Query time: 11 msec >>>>> ;; SERVER: 10.137.5.1#53(10.137.5.1) >>>>> ;; WHEN: Sun Feb 28 16:03:09 CET 2016 >>>>> ;; MSG SIZE rcvd: 73 >>>>> >>>>> >>>>> Any idea what is going on here? >>>>> >> >>> Very similar issues here... >> >> I think it's this issue: >> https://github.com/QubesOS/qubes-issues/issues/1067 >> >>>> I think I solved this now. >>>> >>>> After re-installing with V3.2-rc2 and restoring my VMs (including my old >>>> netvm) I still had this problem from time to time. >>>> >>>> So what I did was to start use the new sys-net VM as NetVM instead of my >>>> restored old netvm (I manually copied over the network manager config, >>>> private keys, certificates etc from the old VM to not have to >>>> reconfigure that). >>>> >>>> Since then, so far I have not seen the issue again. >> >>> I had renamed the sys-firewall VM back to its old "firewallvm" name using >>> Qubes manager after a fresh 3.1rc2 install (otherwise restoring my backup >>> wouldn't have worked: "could not find referenced firewallvm" ...). >> >> Enable option "ignore missing" during backup restoration. This will use >> default VMs in place of missing ones (default netvm, default template >> etc). >> >>> Maybe the >>> sys-firewall name is hardcoded somewhere? I guess I'll test renaming it b
Re: [qubes-users] How do I get Alt-gr button to work when using swedish keyboarld layout?
On 08/03/2016 02:05 PM, Fredrik wrote: > AS the title indicates when I use Swedish keyboard layout the "alt gr" button > does not work. How do I get this key to work? > For me it has worked with QubesOS R2 (KDE,XFCE), R3 (KDE,XFCE) and now R3.2-rc2 (XFCE) out of the box. For instance Alt Gr+E gives the Euro sign (€) and Alt Gr+0 (}) as expected. I using Generic 105-key (Intl) PC model and layout "Swedish" with my Dell laptop Swedish keyboard. Cheers, Markus -- 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/9285ff58-5e71-52a1-4a2c-49005591ebbf%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: AppVMs using ProxyVM having DNS problems some days
On 08/03/2016 09:31 AM, Marek Marczykowski-Górecki wrote: > On Mon, Aug 01, 2016 at 08:31:12AM +0200, David Hobach wrote: > > >> On 07/31/2016 10:05 AM, Markus Kilås wrote: >>> On 02/28/2016 04:13 PM, Markus Kilås wrote: >>>> Hi, >>>> >>>> I am experiencing an issue with DNS queries in my AppVMs in R3.0. >>>> >>>> Sometimes after booting up, the AppVMS that are connected to >>>> sys-firewall are unable to do DNS lookups: >>>> user@untrusted ~]$ dig qubes-os.org >>>> ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> qubes-os.org >>>> ;; global options: +cmd >>>> ;; connection timed out; no servers could be reached >>>> >>>> The same command works in sys-firewall and netvm and any AppVM connected >>>> directly to the netvm but not when going through sys-firewall. There are >>>> no firewall rules added in the Qubes VM Manager and changing to allow >>>> all network traffic for 5 minutes makes no difference. >>>> >>>> Besides DNS lookups not working, the networking is working: >>>> [user@untrusted ~]$ ping 104.25.119.5 >>>> PING 104.25.119.5 (104.25.119.5) 56(84) bytes of data. >>>> 64 bytes from 104.25.119.5: icmp_seq=1 ttl=56 time=31.4 ms >>>> >>>> If I manually change the nameserver to the same as in sys-firewall the >>>> resolving works also in the AppVM: >>>> >>>> With IP from /etc/resolve.conf (sys-firewall): >>>> [user@untrusted ~]$ dig @10.137.2.1 qubes-os.org >>>> ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> @10.137.2.1 qubes-os.org >>>> ; (1 server found) >>>> ;; global options: +cmd >>>> ;; connection timed out; no servers could be reached >>>> >>>> Instead with the netvm IP: >>>> [user@untrusted ~]$ dig @10.137.5.1 qubes-os.org >>>> ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> @10.137.5.1 qubes-os.org >>>> ; (1 server found) >>>> ;; global options: +cmd >>>> ;; Got answer: >>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5804 >>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 >>>> >>>> ;; OPT PSEUDOSECTION: >>>> ; EDNS: version: 0, flags:; udp: 4096 >>>> ;; QUESTION SECTION: >>>> ;qubes-os.org. IN A >>>> >>>> ;; ANSWER SECTION: >>>> qubes-os.org. 127 IN A 104.25.119.5 >>>> qubes-os.org. 127 IN A 104.25.118.5 >>>> >>>> ;; Query time: 11 msec >>>> ;; SERVER: 10.137.5.1#53(10.137.5.1) >>>> ;; WHEN: Sun Feb 28 16:03:09 CET 2016 >>>> ;; MSG SIZE rcvd: 73 >>>> >>>> >>>> Any idea what is going on here? >>>> > >> Very similar issues here... > > I think it's this issue: > https://github.com/QubesOS/qubes-issues/issues/1067 > >>> I think I solved this now. >>> >>> After re-installing with V3.2-rc2 and restoring my VMs (including my old >>> netvm) I still had this problem from time to time. >>> >>> So what I did was to start use the new sys-net VM as NetVM instead of my >>> restored old netvm (I manually copied over the network manager config, >>> private keys, certificates etc from the old VM to not have to >>> reconfigure that). >>> >>> Since then, so far I have not seen the issue again. > >> I had renamed the sys-firewall VM back to its old "firewallvm" name using >> Qubes manager after a fresh 3.1rc2 install (otherwise restoring my backup >> wouldn't have worked: "could not find referenced firewallvm" ...). > > Enable option "ignore missing" during backup restoration. This will use > default VMs in place of missing ones (default netvm, default template > etc). > >> Maybe the >> sys-firewall name is hardcoded somewhere? I guess I'll test renaming it back >> again soon... > > It shouldn't matter. > > My guess was not that the issue was with the name but rather that my restored netvm had some configuration (or similar) issue preventing the resolving from working in some situations. I have no idea if that makes sense or not, it was just a hypothesis of mine. But the fact for me is that since I switched to use the stock sys-net VM I haven't had the problem a single time yet. Cheers, Markus -- 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/584dcbfc-108f-b0d2-e3e3-94e5534e670a%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: AppVMs using ProxyVM having DNS problems some days
On 02/28/2016 04:13 PM, Markus Kilås wrote: > Hi, > > I am experiencing an issue with DNS queries in my AppVMs in R3.0. > > Sometimes after booting up, the AppVMS that are connected to > sys-firewall are unable to do DNS lookups: > user@untrusted ~]$ dig qubes-os.org > ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> qubes-os.org > ;; global options: +cmd > ;; connection timed out; no servers could be reached > > The same command works in sys-firewall and netvm and any AppVM connected > directly to the netvm but not when going through sys-firewall. There are > no firewall rules added in the Qubes VM Manager and changing to allow > all network traffic for 5 minutes makes no difference. > > Besides DNS lookups not working, the networking is working: > [user@untrusted ~]$ ping 104.25.119.5 > PING 104.25.119.5 (104.25.119.5) 56(84) bytes of data. > 64 bytes from 104.25.119.5: icmp_seq=1 ttl=56 time=31.4 ms > > If I manually change the nameserver to the same as in sys-firewall the > resolving works also in the AppVM: > > With IP from /etc/resolve.conf (sys-firewall): > [user@untrusted ~]$ dig @10.137.2.1 qubes-os.org > ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> @10.137.2.1 qubes-os.org > ; (1 server found) > ;; global options: +cmd > ;; connection timed out; no servers could be reached > > Instead with the netvm IP: > [user@untrusted ~]$ dig @10.137.5.1 qubes-os.org > ; <<>> DiG 9.10.3-P3-RedHat-9.10.3-10.P3.fc23 <<>> @10.137.5.1 qubes-os.org > ; (1 server found) > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5804 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: > ;qubes-os.org.IN A > > ;; ANSWER SECTION: > qubes-os.org. 127 IN A 104.25.119.5 > qubes-os.org. 127 IN A 104.25.118.5 > > ;; Query time: 11 msec > ;; SERVER: 10.137.5.1#53(10.137.5.1) > ;; WHEN: Sun Feb 28 16:03:09 CET 2016 > ;; MSG SIZE rcvd: 73 > > > Any idea what is going on here? > > > Cheers, > Markus > I think I solved this now. After re-installing with V3.2-rc2 and restoring my VMs (including my old netvm) I still had this problem from time to time. So what I did was to start use the new sys-net VM as NetVM instead of my restored old netvm (I manually copied over the network manager config, private keys, certificates etc from the old VM to not have to reconfigure that). Since then, so far I have not seen the issue again. Cheers, Markus -- 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/762bec22-851a-2a34-1791-64ea7191aa16%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Risks of Dual-Boot?
On 07/30/2016 06:25 PM, Fabian Wloch wrote: > didn't found anything The issues with unprotected /boot and BIOS is briefly mentioned on the below link and it sounds like AEM should be able to at least be able to detect a compromise for you: https://www.qubes-os.org/doc/multiboot/ Cheers, Markus -- 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/674edceb-e858-30c5-584e-1949f651cd8d%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Change Inter-VM Copy/Paste Shortcut?
On 06/25/2016 02:58 AM, Andrew David Wong wrote: > On 2016-06-24 12:16, ryan.ken...@gmail.com wrote: >> Hello, > >> Is there a way to change Ctrl+Shift+C and Ctrl+Shift+V to >> something like Ctrl+Alt+Shift+C and Ctrl+Alt+Shift+V or Meta+C and >> Meta+V? > >> As I try out Qubes for the first time, I find it clashes with my >> most heavily used shortcuts for other things (like interacting with >> the terminal). > > > Yes, these shortcuts are configurable in /etc/qubes/guid.conf (in dom0). > > There are sample values under "global," including secure_copy_sequence > and secure_paste_sequence. You can define these with your preferred > key combinations. (Don't forget to uncomment those lines.) > > Any chance the defaults could be changed in a future version? Having defaults working well for most people could have a value and make it easier for new users even if it is possible to customize at will. In my opinion having those starting with Ctrl+Alt+... would be more conventional for shortcuts that are "global/desktop/VM-wide". See for example: - Ctrl+Alt+F? for switching virtual terminal - Ctrl+Alt+Del for shutdown/reboot - Ctrl+Alt+Backspace for killing X (?) - Ctrl+Alt as the special key combination in KVM and VMWare While Ctrl+Shift+... could be used by local applications. Most notably as mentioned above for the terminal applications. However, a workaround I found for the terminal clash is to instead re-learn to use Shift+Insert for pasting. Cheers, Markus -- 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/e9168db7-824c-1091-99a9-b61e6b98560a%40xn--kils-soa.se. For more options, visit https://groups.google.com/d/optout.
