Re: [qubes-users] Re: Qubes 4.0 sluggish feel
On Fri, Aug 10, 2018 at 6:18 AM John S.Recdep wrote: > > On 08/06/2018 01:50 PM, Outback Dingo wrote: > > I dont remeber qubes being so sluggish on a skylake laptop with 64Gb, > > qubes is installed on a SSD, however it now seems to take an awful > > long time to switch windows, change tabs in firefox and chhrome, > > launch VMs > > > > also note that screen rendering, i can actually watch web pages paint, > > as though video is being quirly or something, it is an NVIDIA card > > > > any suggestions, nothing is swapping, memory seems ok, ive even > > allocated 8192 mb to 2 vms which i see it in, both fedora and debian, > > and i am up to date update wise. > > > > I blame intel speedstep for everything in your local uefi , and dingos :) great but how do we resolve it... its makes Qubes itself really unuseable > > -- > You received this message because you are subscribed to a topic in the Google > Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/SXkX2yQc0ug/unsubscribe. > To unsubscribe from this group and all its topics, 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/95ee05c4-3ae9-b96b-23e4-3e08ba5c45aa%40riseup.net. > For more options, visit https://groups.google.com/d/optout. -- 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/CAKYr3zxig9DREPYmcnNOsGGm1vKCPWs3Q0yB1uvRvKkPdgyxsQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 sluggish feel
On Thu, Aug 9, 2018 at 5:49 AM cooloutac wrote: > > > > I get this problem sometimes when I update templates, then restart all the > vms. Solution is to reboot the pc. Only happens to me on 4.0 > > -- nope its been rebooted numerous times, still same issue, always sluggish choppy ui, take 20+ seconds just to swtich tabs in chrome / firefox in both fedora and debian. other apps seem to take longer times loading, switching apps is the same > You received this message because you are subscribed to a topic in the Google > Groups "qubes-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/SXkX2yQc0ug/unsubscribe. > To unsubscribe from this group and all its topics, 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/629de0f1-c2ec-4da6-b82c-d61e5f350706%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/CAKYr3zwxXRdu--UZSnS6RDkTaBwePU%2BUTKAEMdWwE46kFbia1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0 sluggish feel
On 08/06/2018 01:50 PM, Outback Dingo wrote: > I dont remeber qubes being so sluggish on a skylake laptop with 64Gb, > qubes is installed on a SSD, however it now seems to take an awful > long time to switch windows, change tabs in firefox and chhrome, > launch VMs > > also note that screen rendering, i can actually watch web pages paint, > as though video is being quirly or something, it is an NVIDIA card > > any suggestions, nothing is swapping, memory seems ok, ive even > allocated 8192 mb to 2 vms which i see it in, both fedora and debian, > and i am up to date update wise. > I blame intel speedstep for everything in your local uefi , and dingos :) -- 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/95ee05c4-3ae9-b96b-23e4-3e08ba5c45aa%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] 2nd of 2 email extra gmail protection and freethoughts on limiting exploits..mitigation of compromise of systems hardware/software
https://www.amazon.com/Yubico-Y-123-FIDO-U2F-Security/dp/B07BYSB7FK This device at this time completes the advanced security for Gmail accounts that is email. I prefer that they be found from another retailer I have heard things about Amazon that cause me to want a secure shipping method offered by the merchant. But it's possible if not from say newegg.com if they in fact offer a more secure shipping method that there exist other merchants offering more secure shipping methods. You think all Cadillacs are saved by but the wrong model is not a safe by GM Motors does not make all cars equal or worthy of trust Chevrolet the first Nova was good subsequently because perhaps they needed to change the design 2 continue the price as the price of the car originally designed would increase because of the demand for the parts in the original configuration and Source the new parts at l o enough cost to keep that same model inline with the original pricing from the manufacturer's suggested retail price MSRP stable and not continue to go up and up although maybe they should continue with the original design because people know it and will pay more with the knowledge that they are getting a trustworthy car apparently that's not the way it works or would they not have done that but then again if they had done it would they have gone bankrupt Etc. Enter in any case I am just looking for these two extra security features for a Gmail email account that last longer than what I have become accustomed to and not happy with because they do not last long I believe it is simply because the password is changed and I don't know it and Gmail cannot determine if it is returning you your account or if you are just trying to ruse your way into obtaining control of an account at cetera. Anyway it's a device you're using is compromised I do not know because I have not researched enough but using the physical device key May will give itself away the Institute is plugged into said, revised device I would assume that but still if possible I would like to try to secure an email account and this is the first one I have seen that offers to things devices necessary to secure under what they term extra security. Inter Again payment for these is no problem for me but we receive our mail at a PO Box as the neighborhood mail carrier and residence seem not to be able to keep the United States Postal Service working as it should and the fact is sometimes things sent to PO boxes are returned. I spoke with a representative my cell phone provider and was told PO Boxes sometimes return replacement phones which are $25 for a good ZTE phone which I have replaced once before and they do not provide any upgraded security shipping options so I am looking for a bring your own device the device must have been available for the Sprint network or simply I believe it's called jailbroken so that it can be used on any network. Inter I have just recently purchased and returned after testing and finding that the device was satisfactory but did not feel comfortable in the way it has been activated I would like to have the device merely for its abilities without using it on Wi-Fi or connecting to cell towers as this is the way other than plugging something into the phone any phone in the case Android is easy 4 for one determined or a determined foe 2 compromise and stand between you as a man in the middle where you see your screen but it is like looking into a kiosk with the information being perhaps true or false and you have no way of knowing which it is wow the one who really controls the device perhaps that is simulator except the simulator is actually the way the one who has true control over the phone makes the settings and those settings include what to report as being or having special privileges like changing system settings and covering up other apps which cause you to believe you are seeing an app and its information but in reality a different app has been given permission a specific permission through Android 2 appear on top of other apps. It's not a new feature it is necessary when you need a pop up so that you can say for instance choose a file when you are running a program that is not a file manager but needs you to choose a file or photo overall complete some action which it does not provide the means to do the means to but would call on another app this second that must be able at is have permission to appear above or on top of the app requesting this extra information I file a picture or whatever it must exist but if misused it can make the user of not just an Android phone Google's os4 mobile phones and not pixel however pixel will have the same ability or any Apple phone would need to say more who created application it makes it difficult for the operator if this isn't used to determine whether the settings for instance are those desired because the app which has been given the permission to cover up the original and legitimate
Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
On Thursday, August 9, 2018 at 10:36:55 AM UTC-5, Jim Snider wrote: > On Wednesday, August 8, 2018 at 10:19:46 AM UTC-5, Yassine wrote: > > There was a mistake in the install kernel parameter I shared, instead of > > "nouveau.modeset=1" it should be "nouveau.modeset=0" > > > > > > > > On Wed, 8 Aug 2018 at 08:20, Yassine wrote: > > On Tuesday, 7 August 2018 14:49:33 UTC+1, Jim Snider wrote: > > > > > On Monday, May 7, 2018 at 12:03:17 AM UTC-5, Yassine wrote: > > > > > > On Sunday, 6 May 2018 14:46:32 UTC+1, Yassine wrote: > > > > > > > Updating previous report as reinstalling from 4.0-rc3 to 4.0 > > > > > > > > > > > > > > Needed to edit xen EFI config to remove mapbs/noexitboot keys and > > > > > disable nouveau modesetting (nouveau.modeset=0) > > > > > > > > > > > > After install I tested different configuration and was able to get > > > > discrete gpu hardware support: > > > > > > - Removed nouveau.modeset=0 > > > > > > - Added kernel param: acpi_osi=! > > > > > > - Changed iommu support from iommu=no-igfx to iommu=on > > > > > > > > > > Yassine > > > > > > > > > > I have a Dell Precision 5520 like yours except mine has the Xeon E3-1505M > > > v6 processor, so I think your solution should work on my Dell. I have not > > > been able to get it to work. > > > > > > > > > > Problem : Qubes 4.0 Installer hangs at anaconda screen. > > > > > > > > > > I made the install USB using Rufus 3.1 in dd mode. I have tried and tried > > > to edit the BOOTX64.cfg on the USB install drive but it is write > > > protected and I have not been able to writew changes using several > > > different approaches. > > > > > I booted UEFI, The results of the install: > > > > > > > > > > message : "Not asking for VNC because we don't have a network" > > > > > message : "44.288997 watchdog: BUG: soft lockup - CPU#5 stuck fot 23s! > > > [Xorg:1383] > > > > > > > > > > I then made a ISO mode install USB using Rufus and edited the BOOTX64.cfg > > > as follows: > > > > > > > > > > [global] > > > > > default=qubes-verbose > > > > > > > > > > [qubes-check] > > > > > options=console=none > > > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 > > > i915.alpha_support=1 quiet rhgb rd.live.check > > > > > ramdisk=initrd.img > > > > > > > > > > [qubes] > > > > > options=console=none > > > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 > > > i915.alpha_support=1 quiet rhgb > > > > > ramdisk=initrd.img > > > > > > > > > > [qubes-verbose] > > > > > options=console=vga efi=attr=uc > > > > > # noexitboot=1 > > > > > # mapbs=1 > > > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 > > > > > ramdisk=initrd.img > > > > > > > > > > [qubes-rescue] > > > > > options=loglvl=all > > > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 rescue > > > > > ramdisk=initrd.img > > > > > > > > > > I booted the ISO USB Legacy, At Blue Qubes screen, Trouble Shooting, TAB, > > > added nouveau.modeset=0 > > > > > The results of the install: > > > > > > > > > > message : "Not asking for VNC because we don't have a network" > > > > > message : "X starting failed, aborting installation" > > > > > message : "The installation cannot continue the system will be rebooted > > > Press ENTER to continue" > > > > > > > > > > Yassine, > > > > > > > > > > I have searched high and low on the internet and your 5520 / Qubes sucess > > > is rare. There is very little discussion of this specific combination. > > > > > > > > > > If you could Please give me some guidance and edit my BOOTX64 above to > > > match yours verbatim, I can try that. > > > > > > > > > > Anyone else reading this post that may have suggestions, please add to > > > the discussion > > > > > > > > > > Thank you so much > > > > > > > > Hi Jim, > > > > > > > > Try changing the default boot entry to the following: > > > > > > > > [qubes-verbose] > > > > options=console=vga efi=attr=uc > > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 > > nouveau.modeset=1 > > > > ramdisk=initrd.img > > > > > > > > Once you've installed Qubes successfully, try tuning your xen.cfg file from > > dom0 with the following configuration: > > > > > > > > [global] > > > > default=4.14.57-1.pvops.qubes.x86_64 > > > > > > > > [4.14.57-1.pvops.qubes.x86_64] > > > > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=on ucode=scan > > > > kernel=vmlinuz-4.14.57-1.pvops.qubes.x86_64 > > root=/dev/mapper/qubes_dom0-root rd.luks.uuid=luks-some-uuid > > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 > > acpi_osi=! rhgb rd.qubes.hide_all_usb > > > > ramdisk=initramfs-4.14.57-1.pvops.qubes.x86_64.img > > > > > > > > Hope this help > > > > > > > > Yassine > > > > > > > > -- > > > > You received this message because you are subscribed to a topic in the > > Google Groups
Re: [qubes-users] Re: Updated HCL report - Dell Precision 5520
On Wednesday, August 8, 2018 at 10:19:46 AM UTC-5, Yassine wrote: > There was a mistake in the install kernel parameter I shared, instead of > "nouveau.modeset=1" it should be "nouveau.modeset=0" > > > > On Wed, 8 Aug 2018 at 08:20, Yassine wrote: > On Tuesday, 7 August 2018 14:49:33 UTC+1, Jim Snider wrote: > > > On Monday, May 7, 2018 at 12:03:17 AM UTC-5, Yassine wrote: > > > > On Sunday, 6 May 2018 14:46:32 UTC+1, Yassine wrote: > > > > > Updating previous report as reinstalling from 4.0-rc3 to 4.0 > > > > > > > > > > Needed to edit xen EFI config to remove mapbs/noexitboot keys and > > > > disable nouveau modesetting (nouveau.modeset=0) > > > > > > > > After install I tested different configuration and was able to get > > > discrete gpu hardware support: > > > > - Removed nouveau.modeset=0 > > > > - Added kernel param: acpi_osi=! > > > > - Changed iommu support from iommu=no-igfx to iommu=on > > > > > > Yassine > > > > > > I have a Dell Precision 5520 like yours except mine has the Xeon E3-1505M > > v6 processor, so I think your solution should work on my Dell. I have not > > been able to get it to work. > > > > > > Problem : Qubes 4.0 Installer hangs at anaconda screen. > > > > > > I made the install USB using Rufus 3.1 in dd mode. I have tried and tried > > to edit the BOOTX64.cfg on the USB install drive but it is write protected > > and I have not been able to writew changes using several different > > approaches. > > > I booted UEFI, The results of the install: > > > > > > message : "Not asking for VNC because we don't have a network" > > > message : "44.288997 watchdog: BUG: soft lockup - CPU#5 stuck fot 23s! > > [Xorg:1383] > > > > > > I then made a ISO mode install USB using Rufus and edited the BOOTX64.cfg > > as follows: > > > > > > [global] > > > default=qubes-verbose > > > > > > [qubes-check] > > > options=console=none > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 > > quiet rhgb rd.live.check > > > ramdisk=initrd.img > > > > > > [qubes] > > > options=console=none > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 > > quiet rhgb > > > ramdisk=initrd.img > > > > > > [qubes-verbose] > > > options=console=vga efi=attr=uc > > > # noexitboot=1 > > > # mapbs=1 > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 > > > ramdisk=initrd.img > > > > > > [qubes-rescue] > > > options=loglvl=all > > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 rescue > > > ramdisk=initrd.img > > > > > > I booted the ISO USB Legacy, At Blue Qubes screen, Trouble Shooting, TAB, > > added nouveau.modeset=0 > > > The results of the install: > > > > > > message : "Not asking for VNC because we don't have a network" > > > message : "X starting failed, aborting installation" > > > message : "The installation cannot continue the system will be rebooted > > Press ENTER to continue" > > > > > > Yassine, > > > > > > I have searched high and low on the internet and your 5520 / Qubes sucess > > is rare. There is very little discussion of this specific combination. > > > > > > If you could Please give me some guidance and edit my BOOTX64 above to > > match yours verbatim, I can try that. > > > > > > Anyone else reading this post that may have suggestions, please add to the > > discussion > > > > > > Thank you so much > > > > Hi Jim, > > > > Try changing the default boot entry to the following: > > > > [qubes-verbose] > > options=console=vga efi=attr=uc > > kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1 > nouveau.modeset=1 > > ramdisk=initrd.img > > > > Once you've installed Qubes successfully, try tuning your xen.cfg file from > dom0 with the following configuration: > > > > [global] > > default=4.14.57-1.pvops.qubes.x86_64 > > > > [4.14.57-1.pvops.qubes.x86_64] > > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=on ucode=scan > > kernel=vmlinuz-4.14.57-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root > rd.luks.uuid=luks-some-uuid rd.lvm.lv=qubes_dom0/root > rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 acpi_osi=! rhgb > rd.qubes.hide_all_usb > > ramdisk=initramfs-4.14.57-1.pvops.qubes.x86_64.img > > > > Hope this help > > > > Yassine > > > > -- > > You received this message because you are subscribed to a topic in the Google > Groups "qubes-users" group. > > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/qubes-users/WMc88pfT-hM/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > qubes-users...@googlegroups.com. > > To post to this group, send email to qubes...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/75ac78ff-42ef-422f-a3ed-8d9efafa1f26%40googlegroups.com. > > For more options, visit
Re: [qubes-users] 3840x2160 Resolution - How to change: Icon, Windows and Text Sizes?
On Thursday, August 9, 2018 at 1:37:34 AM UTC-4, Ivan Mitev wrote: > Sorry, I'm not familiar with Debian. I thought that the instructions in > the doc I've linked to would be generic - ie. either you have gnome > settings daemon installed/running, or you don't. > Did you try to change the Xft.dpi X resource ? > > If you find a solution for debian, please post it so that I can update > the doc (or if you're familiar with git/github, you could send a pull > request with changes to the doc !). > > Cheers, > Ivan Actually, I cloned today new VM on Debian 9 and tried again with your Github guide and it works. " echo Xft.dpi: 144 | xrdb -merge set in /etc/X11/Xresources/x11-common Xft.dpi: xxx " I don't know what was been the reason the first time, because I did the same things. -- 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/8556d6c0-6fac-4f36-9569-bddee21e6af1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: 3840x2160 Resolution - How to change: Icon, Windows and Text Sizes?
On Thursday, August 9, 2018 at 2:02:47 AM UTC-4, m...@militant.dk wrote: > onsdag den 1. august 2018 kl. 12.15.29 UTC-4 skrev Daniil .Travnikov: > > Hi, > > > > I bought Oryx Pro recently which has 3840x2160 resolution. > > > > > > Do you know how to change in Dom0 Windows, Texts and Icon sizes? Maybe > > existing some software for this options? Or it could be done in setings > > somwhere? > > > > > > Screenshot of my situation: > > https://drive.google.com/open?id=1V8Yg2nGd5A44laCGwMvAo71kHxb5DCqi > > I have had similar experiences and used a tool called "gnome-tweak-tool" to > correct the situation > (https://www.militant.dk/2018/05/21/qubes-3-2-fedora-26-large-icons-and-large-fonts-on-lenovo-yoga-2-pro-high-resolution-laptop/) > > But lately I think it has changed to "gnome-tweaks", so you can try that, if > the first package is missing. > > Sincerely > Max Yes, I tried it yesterday and it did not help. I even tried to install Nvidia driver tool (I don't know why :), maybe I believed in magic). -- 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/f03821e2-c9f9-4e16-b468-5989a4113a32%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Whonix 14 installation stalled
On Wed, August 8, 2018 6:02 pm, remarcus via qubes-users wrote: > On Wednesday, August 8, 2018 at 10:42:55 AM UTC-7, rema...@protonmail.com > wrote: > >> On Wednesday, August 8, 2018 at 10:18:56 AM UTC-7, >> rema...@protonmail.com wrote: >>> Hey all, >>> >>> >>> In Qubes 4, after entering sudo qubesctl state.sls qvm.anon-whonix in >>> dom0, the command is accepted, but nothing happens. I've been waiting >>> for almost 20 minutes and there's been no output in the terminal. I >>> followed the Whonix documentation instructions up to this step. >>> >>> Is there something I need to configure before salt commands will work >>> properly? Am I just being impatient? Or is there something else that >>> I've missed? >>> >> >> Update: I ran sudeo qubes-dom0-update qubes-core-admin-addon-whonix in >> another terminal window to check I had it installed, and received a new >> error message: >> >> *** ERROR while receiving updates: Error while verifing >> qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm signature: >> /var/lib/qubes/updates/rpm/qubes-template-whonix-ws-14-4.0.1-2018071718 >> 01.noarch.rpm: rsa sha1 (MD5) PGP MD5 NOT OK >> >> >> Domain sys-firewall sent not signed rpm: >> qubes-template-whonix-ws-14-4.0.1-201807171801.noarch.rpm --->if you >> want to use packages that were downloaded correctly, use yum directly >> now > > Double checked the docs so I now know to ignore the signature error. The > whonix-ws-14 template seems to have installed correctly (not sure if > re-doing sudo qubes-dom0-update qubes-core-admin-addon-whonix caused this > or the salt process just took that long to complete), but the gw template > hasn't appeared. > > At this point I'm assuming gw will be installed after enough time passes, > so this bug can probably be diagnosed as user error: impatience, > unfamiliarity with salt I think you're right and it was probably (slowly) downloading and installing templates. Some type of notice would be nice, 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 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/05ca8bae358840b3f6245235abd9e6de.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Where to add command to turn wifi off
On Wed, Aug 08, 2018 at 01:57:49PM -0400, Chris Laprise wrote: > On 08/08/2018 12:05 PM, trueriver wrote: > > Chris's suggestion was not quite right, but near enough for me to get it > > working. This is no reflection on Chris but is down to inconsistent naming > > conventions between different devs on different projects. > > > > Chris said > > > > > > You can open a terminal in your template and run the following: > > > > > > sudo touch /var/run/qubes-service/network-manager > > > > up to here is correct, but there are two points with the following line > > > > > sudo service network-manager start > > > > Firstly, it tries to do it but suggests we use systemctl instead. > > > > Secondly systectl does not know of a service by this name. I then did a bit > > of searching and it turns out that the correct command is > > > > sudo systemctl start NetworkManager > > Yes, I should have mentioned I worked that out on Debian 9. Fedora service > names are different. > > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 NetworkManager as service name works in Debian too. -- 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/20180809084552.m2hbeiyex7okyk2g%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: 3840x2160 Resolution - How to change: Icon, Windows and Text Sizes?
onsdag den 1. august 2018 kl. 12.15.29 UTC-4 skrev Daniil .Travnikov: > Hi, > > I bought Oryx Pro recently which has 3840x2160 resolution. > > > Do you know how to change in Dom0 Windows, Texts and Icon sizes? Maybe > existing some software for this options? Or it could be done in setings > somwhere? > > > Screenshot of my situation: > https://drive.google.com/open?id=1V8Yg2nGd5A44laCGwMvAo71kHxb5DCqi I have had similar experiences and used a tool called "gnome-tweak-tool" to correct the situation (https://www.militant.dk/2018/05/21/qubes-3-2-fedora-26-large-icons-and-large-fonts-on-lenovo-yoga-2-pro-high-resolution-laptop/) But lately I think it has changed to "gnome-tweaks", so you can try that, if the first package is missing. Sincerely Max -- 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/7855f376-0e02-49ef-9408-e97c75a6dfe0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
