Re: [qubes-users] Reasonably secure laptop with touchscreen and enough ram for dictation in Windows App-VM?

2017-10-10 Thread Sean Hunter 
On Sat, Oct 07, 2017 at 05:01:37PM -0400, taii...@gmx.com wrote:
> https://www.reddit.com/r/linux/comments/3anjgm/on_the_librem_laptop_purism_doesnt_believe_in/
> Purism is a scam, don't buy from them - their laptops are as owner
> controlled and freedom respecting as a dell - their version of coreboot is a
> wrapper layer with all the hardware init done by a black box binary blob so
> it is worthless.

I see that reddit post from 2 years ago referred to a lot, and I know this is 
(for some reason) a very emotional topic.  However it doesn't seem to 
correspond to what I see when I dig under the surface, which is the purism guys 
merging changes into coreboot (eg 
https://review.coreboot.org/#/q/status:mergbranch:master 
topic:purism/librem13ed+project:coreboot+purism) and what I see on my own 
laptop, which is that it is SeaBios + coreboot .  I doubt it is perfect, but it 
is way better than a Dell.

If I look at https://puri.sm/faq/do-librem-devices-support-coreboot/ it says 
that 13v2 and 15v3 (what I have) come with coreboot pre-installed and for 
earlier versions they have instructions to update to coreboot.

Sean

-- 
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/20171008092438.GA1688%40uncarved.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: [qubes-users] (Urgent) How do I uninstall qubes or install anything else over it

2017-10-10 Thread Unman 
On Tue, Oct 10, 2017 at 03:54:56PM -0400, '[799]' via qubes-users wrote:
> Hello
> 
>  From: micmacoffici...@gmail.com 
> >> I installed qubes os on my ssd hard-drive with windows 7 and
> >> now I"m trying to get back windows but for some reason I can"t
> 
> in case you've joined the Qubes Community for the first time, welcome :-)
> 
> I really hope that you've made a backup before (!) installing any other OS on 
> the same harddrive/ssd.
> And even if you're not working with a dual boot setup:
> BACKUP YOUR DATA - even more important when using windows.
> Today you can get a 2,5 portable hdd/ssd for less than 100eur and backup 
> solutions like Veeam are a setup & forgett solution.
> Please (if you haven't done so): get a backup solution!
> https://www.veeam.com/windows-endpoint-server-backup-free.html
> 
> Regarding your current setup:
> >From the information you've provided I assume that:
> - you had a working windows 7 installation on your ssd
> - you have installed qubes os on the same ssd
> - you can succesfully boot Qubes and login
> 
> If this is correct, keep calm and take closer look what happened.
> 1) login into Qubes and start a terminal in dom0
> 
> 2) find the identifier of your internal ssd:
> [username@dom0 ~]$ sudo pvdisplay | grep PV
>   PV Name   /dev/sda5
>   PV Size   327.94 GiB / not usable 4.00 MiB
>   PV UUID   A5YJiZ-mYa8-jG9K-6bYd-wYcR-vu3Q-9SBpNp
> 
> this will print out three line, one of them: PV Name /dev/sda5
> (this could also be something else but the part behin /dev/ is important)
> additionally you'll see a line: PV Size 327 GiB
> (size will be different in your case).
> If the size is much smaller than your ssd capacity it might be, that the 
> other space is still occupied with your windows installation.
> 
> 3) Show how your ssd is currently partitioned:
> In my case I got /dev/sda5 which means that my Qubes setup is running on 
> partition 5 and my ssd is identified by /dev/sda (remove the last number).
> 
> [username@dom0 ~]$ sudo fdisk -l /dev/sda
> Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x435892a5
> 
> Device Boot Start   End   Sectors   Size Id Type
> /dev/sda1  * 2048   1026047   1024000   500M  7 HPFS/NTFS/exFAT
> /dev/sda2 1026048 245762047 244736000 116.7G  7 HPFS/NTFS/exFAT
> /dev/sda3   245762048 249956351   4194304 2G 83 Linux
> /dev/sda4   249956352 937701375 687745024   328G  5 Extended
> /dev/sda5   249958400 937701375 687742976   328G 8e Linux LVM
> 
> If you can see something like NTFS this indicates a windows partition.
> Make sure that the partition has a reasonable size.
> As you can see I have two NTFS (windows formatted) partitions, where the 1st 
> one is only 500mb in size, which indicates the boot partition.
> the 2nd one is the one we are looking for.
> 
> Do this now and enter the output.
> You can copy the data from the terminal in dom0 if you right click on the 
> Q-icon in the upper right corner and choose "Copy dom0 Clipboard".
> Then switch to your internet-AppVM and copy the content using Shift+Ctrl+V 
> and after that Ctrl+V
> 
> Depending on the output we can provide the next steps.
> 
> [799]

This is good advice.
Depending on how important the data is, and the state of your current
backups, you should considetr taking a full disk backup before you do
anything else.

You can do this by booting using a live Linux distribution, (kali,
knoppix etc), and then cloning the disk using dd.
If your ssd disk is /dev/sda, then you can create a disk_image like this:
dd if=/dev/sda of=sda.img
It will take a long time as it will copy the WHOLE disk.

The advantage of this is that you preserve the state of the disk AND all
the data. Even if you HAVE overwritten the Windows partitions you may
still be able to recover data.

Did you read the doc pages on multi-booting?

Let us know what the fdisk output shows.

-- 
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/20171010235836.jr7hiwdynqcqsmjj%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Error Creating Ubuntu VM in Qubes 3.2

2017-10-10 Thread Unman 
On Mon, Oct 09, 2017 at 08:20:44PM -0700, Person wrote:
> I have copied the file to dom0 several times without error messages, so it is 
> unlikely that the transferral was unsuccessful. 
> 

Here are some basic Linux commands that you should use in a terminal in
dom0:
pwd  - this will show you the directory that you are in.
ls - this will list the contents. You would expect to see the file that
you have just created. If you use 'ls -lh' you will get a  LONG listing
('l') with sizes in HUMAN format ('h').
SO you can confirm that the file you have just copied is the expected
size.

Run the command to copy the iso image.
Then use 'ls -lh' and check that the file is indeed there.
'pwd' to identify the directory.


Armed with that knowledge you will be able to put together the right
path to the iso image when you try to start using the --cdrom option.

-- 
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/20171010234311.3yo5c4jxvsjjolzh%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Unable to uninstall or reinstall Whonix

2017-10-10 Thread Unman 
On Mon, Oct 09, 2017 at 08:40:19PM -0700, Person wrote:
> I’ll probably try to reinstall Whonix or just delete it altogether.
> 

I admire your persistence, if not your skills.

If you DO try Whonix again, please make an effort to understand how it
is intended to work.
I don't use it myself, but I believe that it comes in two parts - the
gateway and the ws. The problems you are talking about now arise
because you tried to use anon-whonix , which is the ws side of things as
the gateway.
I haven't looked at the code but I can almost guarantee that that wont
work. And indeed it didn't for you.

Don't give up.
Make sure that you remove the Whonix templates and then reinstall
them.

You will almost certainly get better advice if you address the Whonix
forums rather than this mailing list, unless you have Qubes specific
problems.

-- 
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/20171010233557.ahhjp6soe5g4ep5d%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Howto add eyecandy in dom0: i3wm with compton + rofi (how to install?)

2017-10-10 Thread '[799]' via qubes-users 
Hello,

I'd like to get some more eyecandy in dom0 and adapt my i3wm installation with 
installing rofi and compton.
rofi = replacement launcher for dmenu
https://github.com/DaveDavenport/rofi

compton = graphical effects/smooth animations/fading etc. when moving windows
https://github.com/chjj/compton

Unfortunately both packages are not available in the regular repositories and 
both applications need some dependencies:
https://github.com/chjj/compton/blob/master/README.md
https://github.com/DaveDavenport/rofi/blob/next/README.md

Can someone point me into a direction how can I install both apps in dom0 ?
I'm afraif that I need to manually download tons of packages and install those 
and still not all dependencies will be resolved - that's the point why we 
handle such tasks with package management.

Who is making the decision which packages will be available in the "official 
Qubes" (dom0) repositories.

[799]

-- 
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/AQFPUQnkqM3BhV4zPXoIWnaKgpbbBt7K2ut0FGpYJU16uwaTfxEFCTBxMb8MOkXI4kG5glGMHuEQzSfm0CoRvIi33xhBnikXcYxZOxv9gzk%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Win 7 HVM in seamless mode will run fullscreen in i3wm

2017-10-10 Thread '[799]' via qubes-users 
Hello,

after some more testing I found the root cause why a Windows 7 HVM will always 
run in fullscreen mode under the tiling window manager i3wm.
The following config line was used to move the windows VM to a specific 
workspace:
set $workspace3 "3 Windows"
assign [class="win7"] $workspace3

Problem:
Windows 7 will not work in seamless mode with i3wm.
When booting up the VM will always run in fullscreen mode.

Root cause:
having an "assign"-entry in your ~/.local/i3/config which can move a windows to 
a specific workspace/desktop will break seamless mode.

Solution:
Removing the configuration option in your i3 config.
This will make seamless mode work with your win7 HVM and you'll get a windows 
in a tilinmg window manager.
unfortunately you need to move windows manually to the desired workspace.

This behaviour looks strange to me, so I name this a bug, but I am unsure if 
this is i3wm or Qubes related.

[799]

Sent with [ProtonMail](https://protonmail.com) Secure Email.

>  Original Message 
> Subject: [qubes-users] Win 7 HVM in seamless mode will run fullscreen in i3wm
> Local Time: October 5, 2017 10:30 PM
> UTC Time: October 5, 2017 8:30 PM
> From: qubes-users@googlegroups.com
> To: qubes-users 
>
> Hello,
>
> I would like to use my Win 7 HVM with i3wm in seamless mode.
> After making sure that seamless mode is working without any problems under 
> the xfce window manager in Qubes 3.2 i triet to run the same Win 7 HVM in 
> i3wm.
>
> Unfortunately the Win 7 AppVM will always run in fullscreen mode.
> If I disable seamless mode and start up the VM in Debug mode, I get two win7 
> windows, one is the black startupwindow and the 2nd one the real desktop.
>
> If I disable debug mode and enable seamless mode, the first windows which 
> will some up when starting the win7 appvm will be gone but the main win7 
> windows will still stay on top.
>
> QUESTION:
> 1) Is it possible to use Win 7 in seamless mode when using i3wm
> 2) if yes, how can I make it work or where to look for a root cause?
>
> [799]
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
> --
> 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/y2Ao5bgMTfRrahn8Ahyvb5HaB0dRD6z0XD0D77Wcp5bkl89HLK4MVmEnQczic5m6xQWlL4aU2046mjj2ogKCXccFYKuqeqSiwhkT8TRpJSA%3D%40protonmail.com](https://groups.google.com/d/msgid/qubes-users/y2Ao5bgMTfRrahn8Ahyvb5HaB0dRD6z0XD0D77Wcp5bkl89HLK4MVmEnQczic5m6xQWlL4aU2046mjj2ogKCXccFYKuqeqSiwhkT8TRpJSA%3D%40protonmail.com?utm_medium=email_source=footer).
> 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/opEqfTwfpCiYUTpsehD8UpAbhM85JLMfNGcNVHqLEwXzJyQMOaeVfDt5ivw7tK4F7cAOc0fbFwxBgXgs-2-EN-Z5qr5xgpkLinVRfhSIaJI%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] (Urgent) How do I uninstall qubes or install anything else over it

2017-10-10 Thread '[799]' via qubes-users 
Hello

 From: micmacoffici...@gmail.com 
>> I installed qubes os on my ssd hard-drive with windows 7 and
>> now I"m trying to get back windows but for some reason I can"t

in case you've joined the Qubes Community for the first time, welcome :-)

I really hope that you've made a backup before (!) installing any other OS on 
the same harddrive/ssd.
And even if you're not working with a dual boot setup:
BACKUP YOUR DATA - even more important when using windows.
Today you can get a 2,5 portable hdd/ssd for less than 100eur and backup 
solutions like Veeam are a setup & forgett solution.
Please (if you haven't done so): get a backup solution!
https://www.veeam.com/windows-endpoint-server-backup-free.html

Regarding your current setup:
>From the information you've provided I assume that:
- you had a working windows 7 installation on your ssd
- you have installed qubes os on the same ssd
- you can succesfully boot Qubes and login

If this is correct, keep calm and take closer look what happened.
1) login into Qubes and start a terminal in dom0

2) find the identifier of your internal ssd:
[username@dom0 ~]$ sudo pvdisplay | grep PV
  PV Name   /dev/sda5
  PV Size   327.94 GiB / not usable 4.00 MiB
  PV UUID   A5YJiZ-mYa8-jG9K-6bYd-wYcR-vu3Q-9SBpNp

this will print out three line, one of them: PV Name /dev/sda5
(this could also be something else but the part behin /dev/ is important)
additionally you'll see a line: PV Size 327 GiB
(size will be different in your case).
If the size is much smaller than your ssd capacity it might be, that the other 
space is still occupied with your windows installation.

3) Show how your ssd is currently partitioned:
In my case I got /dev/sda5 which means that my Qubes setup is running on 
partition 5 and my ssd is identified by /dev/sda (remove the last number).

[username@dom0 ~]$ sudo fdisk -l /dev/sda
Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x435892a5

Device Boot Start   End   Sectors   Size Id Type
/dev/sda1  * 2048   1026047   1024000   500M  7 HPFS/NTFS/exFAT
/dev/sda2 1026048 245762047 244736000 116.7G  7 HPFS/NTFS/exFAT
/dev/sda3   245762048 249956351   4194304 2G 83 Linux
/dev/sda4   249956352 937701375 687745024   328G  5 Extended
/dev/sda5   249958400 937701375 687742976   328G 8e Linux LVM

If you can see something like NTFS this indicates a windows partition.
Make sure that the partition has a reasonable size.
As you can see I have two NTFS (windows formatted) partitions, where the 1st 
one is only 500mb in size, which indicates the boot partition.
the 2nd one is the one we are looking for.

Do this now and enter the output.
You can copy the data from the terminal in dom0 if you right click on the 
Q-icon in the upper right corner and choose "Copy dom0 Clipboard".
Then switch to your internet-AppVM and copy the content using Shift+Ctrl+V and 
after that Ctrl+V

Depending on the output we can provide the next steps.

[799]

-- 
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/oXgyiCXHMw_BKGvq3XHDqJMAAfyNWVkNydIk2blmSbWRy8imEYyIICiPL6oRbJZFsxwhrUKPku4KNa747DuXz1qRH_L-LOz1mfCKFcEla08%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Read-only file system in applVM

2017-10-10 Thread Chris Laprise 

On 10/10/2017 02:31 AM, Franz wrote:



On Mon, Oct 9, 2017 at 9:36 PM, Chris Laprise > wrote:


On 10/09/2017 08:48 AM, Franz wrote:

Hello,

Trying to save a long document I got an error.

So tried to open a new document to copy there the content of
the older. But it gives an error: read only file system.

Any idea why this applVM now decided to be a read only file
system? and if  is there a fix other than rebooting?
Best
Fran


It probably means there is a logical inconsistency (corruption) in
that filesystem, or it filled-up. You can avoid the latter by
expanding the Private storage max size in the VM's settings.


It should be corruption, because there is plenty of space.

Anyway I had to reboot and after that it worked again even if an alert 
of Python not working appears.


Is there some way to fix corruption cases?
Best
fran



Using 'fsck' on it might fix it. Before doing that, you may have to 
re-mount the volume as read-only; or you could use qvm-block to attach 
the private.img to a dispVM and then run fsck /dev/xvdi .


--

Chris Laprise, tas...@posteo.net
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/adb30baf-1497-d955-6b84-d158eceb8729%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] kswapd0 using 100% CPU with not even a MB swap in use

2017-10-10 Thread 'Vincent Adultman' via qubes-users 
>> On 10/08/2017 08:18 AM, Marek Marczykowski-Górecki wrote:
>
> Indeed on 4.9.45-21 kernel it happens much rarer than on 4.4.x, but still
> happens sometimes...

It's only anecdotal, but I seem to have been seeing it more frequently recently 
(i.e. on that kernel). Will try the one-liner again, don't think it had any 
effect last time I tried it. I've got at least one old laptop with probably 
poor thermal paste or a dust bunny that this actually causes to overheat and 
shut down in a warm room. Less critically, for what's often a laptop OS it's 
rather hard on the battery.

FWIW (beware, anecdote incoming) the problem does seem different under the 
newer kernel, in that close enough other vms and the one with the problem may 
settle down (which I don't remember happening before). However, this makes 
limited sense to me, given that one vm that does it (sys-net) is not included 
in memory balancing, whereas others that randomly do it are. The vms that do it 
are fedora service vms, through to debian ones running chromium, the 
commonality being the kernel.

A quick google suggests this occurs / or has occurred on a variety of linux 
distros, but I do wonder if something about a memory constrained qubes install 
makes it more likely.

Marak, afaik there is no bug open for this, would it be worth me opening one, 
even if its just to track and add to a known issues page or similar? Seems 
enough of us run into this one.

-- 
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/Gorgp-LxukU8BbuISwc7s-zJ4G_DKsvBTRFdLvEqCDWDjbDEnhSKdRC8__BxvA9AQJgowPgnij6KgP_2qImlSkAL4_2nkxpvhI_GavM3Teg%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] (Urgent) How do I uninstall qubes or install anything else over it

2017-10-10 Thread derpytorp 
Qubes OS 3.2 has a tendency of overwriting all drives on all attached storage 
mediums during installation. You should ha e removed it physically before hand.

Just a thought but perhaps you changed a setting in bios dissallowing boot from 
certain disk partitions/boot types. This would happen if you'd set native 
legacy mode instead of enabling UEFI with CSM.

-- 
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/9717e775-3d06-432a-a56e-12c6456a1c40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Mac-Spoofing Doesn’t Work

2017-10-10 Thread Sean Hunter 


Sent from my phone. Sorry if brief. 

> On 10 Oct 2017, at 04:39, Person  wrote:
> 
> I downloaded Fedora 25, and I’m still working out the MAC thing (so far so 
> good). I looked at the manual and didn’t really want to install Debian 9, so 
> am I able to keep my MAC private if I only use Fedora?
> 

Yes. I’m using Fedora for my sys-net (as is the standard install) and have mac 
spoofing on using the config below. I’m using 4.0 rc 1, but if you’re using 3.2 
I would think it’s possible as long as you can update NetworkManager enough. 
That may mean updating your sys-net template to fedora-25. 

Sean

-- 
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/AFF27262-CE82-4EEE-B2F4-1210A373FEAF%40uncarved.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Screen blanks instead of power off

2017-10-10 Thread TomP 
Am Sonntag, 13. November 2016 00:31:05 UTC+1 schrieb tai...@gmx.com:
> I have tried all the options in the power control menu but my screen 
> still doesn't turn off it just disconnects the output so the screen will 
> say "NO VGA/DVI DETECTED" when power save mode turns on.
> 
> Ideas?

issue: Samsung ATIV Book 9 Plus  does not power off
Qubes 3.2:

I already tried shutting down all qubes first and then "sudo shutdown now". If 
I press arrow up I can see the output which ends with shutdown reached. But the 
screen does power off and the system stays on.  How to solve that problem ? I 
need to shutdown manually by long pressing power button then.

-- 
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/4416f71c-25a0-40d0-b63a-9441d36d610d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Touchscreen not working on Qubes 3.2

2017-10-10 Thread TomP 
Am Donnerstag, 2. März 2017 12:02:56 UTC+1 schrieb atlahua:
> ISSUE: Touchscreen and all other USB devices assigned to the same USB bus 
> stop working
> 
> On Qubes 3.1 I found a workaround solution assining the USB bus that manages 
> the touchscreen to dom0 (on sys-usb services tab). The touch screen started 
> working. The disadvantage in terms of security is that the other devices 
> assigned to this bus (USB port and built-in camera were also assigned to dom0.
> 
> The news is that after upgrading to Qubes 3.2, this workaround solution does 
> not work anymore. Thinking that it might be related to having Xfce instead of 
> KDE I swaped the desktop environment to KDE as instructed in your help pages 
> but it seems that was not the issue. Also all other devices on the same bus 
> stopped working, that is, the computer does not even detect a pendrive to one 
> of the USB ports on the computer.
> 
> All the USB devices work fine when re-assinged to sys-usb, except from the 
> touchscreen, that is.
> 
> ___Laptop: Asus TP300LA 
> 4GB
> [user@sys-usb /]$ lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> **Bus 002 Device 005: ID 03eb:8b03 Atmel Corp.** 
> Bus 002 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
> Bus 002 Device 003: ID 8087:07dc Intel Corp. 
> Bus 002 Device 002: ID 8087:8000 Intel Corp. 
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
>  

Issue : Touchscreen on Samsung ATIV Book 9 Plus not working
On Qubes 3.2:   Does anyone know how to activate the touch screen ?

Please help. Tom

-- 
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/428d2082-10c5-4aec-ab1c-ff2ac5795dcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes Network Manager "add connection" creates dialog box but all of the fields are "grayed out"

2017-10-10 Thread bdwomackgm 
The only thing it will let me do is select headings like "General", "Wi-Fi" etc 
but all of the fields are grayed out.  

I'm using the Qubes network manager and the default fedora VM will not start so 
I don't know if a network manager in there will work.

The alternate linux hardware drivers were already installed.

-- 
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/253ec766-50fe-452d-a676-b0a9324aa4a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Read-only file system in applVM

2017-10-10 Thread Franz 
On Mon, Oct 9, 2017 at 9:36 PM, Chris Laprise  wrote:

> On 10/09/2017 08:48 AM, Franz wrote:
>
>> Hello,
>>
>> Trying to save a long document I got an error.
>>
>> So tried to open a new document to copy there the content of the older.
>> But it gives an error: read only file system.
>>
>> Any idea why this applVM now decided to be a read only file system? and
>> if  is there a fix other than rebooting?
>> Best
>> Fran
>>
>>
> It probably means there is a logical inconsistency (corruption) in that
> filesystem, or it filled-up. You can avoid the latter by expanding the
> Private storage max size in the VM's settings.
>
>
It should be corruption, because there is plenty of space.

Anyway I had to reboot and after that it worked again even if an alert of
Python not working appears.

Is there some way to fix corruption cases?
Best
fran

> --
>
> Chris Laprise, tas...@posteo.net
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
>
>

-- 
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/CAPzH-qCvWyKWXSFwS599KX5nkz7uZnZU1SP22o4J-EqQQGTcdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.