Re: [qubes-users] Failure to delete fedora-28 (mgmt vm problem)

[Elias Mårtenson]

On Thu, 28 Feb 2019 at 11:24, 'awokd' via qubes-users <
qubes-users@googlegroups.com> wrote:


> You can't remove default-mgmt-dvm. Qubes uses it internally. You can
> change it to a different template, say fedora-29. Then you should be
> able to remove fedora-28. If not, try removing it with "dnf remove
> qubes-template-fedora-28".
>

Thank you. Changing the template fixed the problem, and I was then able to
remove fedora-28.

Regards,
Elias

-- 
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/CADtN0WLgc4QBykstmeeDVg1%2BOHpmLxZkdLJuM2wv-qtChi2zyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Failure to delete fedora-28 (mgmt vm problem)

[Elias Mårtenson]

After having migrated all my VM's to fedora-29, I wanted to delete the old 
fedora-28 template, but it fails:

$ qvm-remove fedora-28
This will completely remove the selected VM(s)...
  fedora-28
Are you sure? [y/N] y
VM fedora-28 cannot be removed. It is in use as:
 - template for default-mgmt-dvm

I don't think such a VM should be lingering in the system, so I tried to remove 
it:

$ qvm-remove default-mgmt-dvm
This will completely remove the selected VM(s)...
  default-mgmt-dvm
Are you sure? [y/N] y
VM default-mgmt-dvm cannot be removed. It is in use as:

That's not an incorrect cut The list of VM's for which it is in use is 
blank.

What could have gone wrong here, and how can I fix this?

-- 
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/5e27a654-1294-4897-ada8-e43c481e65d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Template disappeared: qubes-template-fedora-29-minimial

[Elias Mårtenson]

On Friday, 1 February 2019 18:21:46 UTC+8, Marek Marczykowski-Górecki  wrote:

> Probably something gone wrong with removing the template. Templates
> which are still installed are excluded from being installed again.
> Verify this with:
> 
> rpm -q qubes-template-fedora-29-minimial
> 
> If the template package is still there, but actual template is gone (not
> listed by qvm-ls tool), you can forcibly remove the package with:
> 
> sudo rpm -e --noscripts qubes-template-fedora-29-minimial

Thank you! That worked.

-- 
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/6622c7d5-448a-4cc7-96f5-646a3a27147b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Unable to assign USB microphone to a VM

[Elias Mårtenson]

On Tuesday, 21 August 2018 14:02:57 UTC+8, Elias Mårtenson  wrote:

> I then start a VM, and run the following from dom0:
> 
> qvm-device mic attach  dom0:mic
> 
> I start pavucontrol and audacity in the VM. As soon as I click on “monitor” 
> in audacity I can see it show up in the VM's pavucontrol session, but:
> 
> - I see no activity in audacity
> - pavucontrol doesn't show any activity (unlike the dom0 pavucontrol)
> - If I click “record” in audacity it doesn't record anything at all, not 
> even 
>   silence. That suggests that it's blocking when trying to read from the 
>   device.
> 
> Does anyone have any idea what is going wrong?

Some more information: The problem isn't limited to audacity. I just used that
as an example because it's an easy sound recording application to use.

Any application attempting to use the microphone behaves the same.

-- 
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/af55ffea-37dd-4612-8f50-acf96825804d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Unable to assign USB microphone to a VM

[Elias Mårtenson]

I have been unable to get my microphone working, and I'm coming here in the 
hope that someone might be able to provide some advice.

Here's all the relevant details I can think of at the moment:

This is on a workstation that is not currently using sys-usb, since I don't 
have neither a PS2 keyboard nor mouse available.

I have a USB headset as well as a USB DAC connected. Audio output to both the 
headset and the DAC works fine (I'm using the DAC for listening to music, and 
the headset for phone conferencing).

I have used pavucontrol in dom0 to assign the output and input devices that I 
want to the respective VM's. My choice of output device is honoured, so I know 
that part of the equation works.

Now for the microphone problem. I select the headset microphone in pavucontrol 
in dom0, and while doing so I note that the meter is bouncing back and forth 
while speaking, which means that it actually works.

I then start a VM, and run the following from dom0:

qvm-device mic attach  dom0:mic

I start pavucontrol and audacity in the VM. As soon as I click on “monitor” in 
audacity I can see it show up in the VM's pavucontrol session, but:

- I see no activity in audacity
- pavucontrol doesn't show any activity (unlike the dom0 pavucontrol)
- If I click “record” in audacity it doesn't record anything at all, not 
even 
  silence. That suggests that it's blocking when trying to read from the 
  device.

Does anyone have any idea what is going wrong?

Regards,
Elias

-- 
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/41e1603b-3d51-4665-8d11-3d147c8dbd64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Settings environment variable system-wide in a VM

[Elias Mårtenson]

On Tuesday, 20 March 2018 22:59:17 UTC+8, Unman  wrote:

> I'm not familiar with Fedora, but setting a variable in .profile DOES
> seem to expose it to nautilus, at least in a qube using a
> Fedora-26-minimal template.
> So can we take a step back and can you explain what variable you want
> set and how you expect it to affect nautilus use? That is, how would you
> judge that the variable has been set for nautilus?

That's odd. That's not my observation on Fedora-26.

What I try to set is KRB5CCNAME. This environment variable specifies the
path to the Kerberos ticket file that is needed for authentication to
SMB fileshares (in the specific case of Nautilus).

I have proved that the environment variable does not get set first and foremost
by noting that authentication doesn't work, and also by checking 
/proc/PID/environ
for the Nautilus process. This file contains the environment variables for
a given process.

-- 
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/a35fba52-80c4-4fa6-9140-6a653589de96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Settings environment variable system-wide in a VM

[Elias Mårtenson]

On Tuesday, 20 March 2018 21:34:38 UTC+8, Unman  wrote:

> You dont seem to have followed my recommendations :-(

Actually, I did. :-)  Note that your recommendation works perfectly on Debian-9.
I'm using Fedora-26, and things are not as neat there.

> On a Debian system, sourcing user defined xessionrc is already set up -
> it is in /etc/X11/Xsession.d/40x11-common_xsessionrc.
> I suspect Fedora would have something similar.

Well, it doesn't seem to. On Fedroa there is only a single file in
/etc/X11/Xsession.d, and that is 60xbrlapi (which seems to have something
to do with braille output).

That's why I added my own to the fedora-26 template, with the content you
saw in my previous message.

But, even when doing this, the script wasn't run which suggests that the entire
Xsession.d mechanism does not work on Fedora-26. Again, on Debian-9 it works
exactly as you described.

-- 
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/781df457-5f02-4bc8-adc6-f778157971c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Settings environment variable system-wide in a VM

[Elias Mårtenson]

On Monday, 19 March 2018 20:06:41 UTC+8, Unman  wrote:

> generally the Xsession wont touch .profile - there are exceptions.
> It's picking up stuff from /etc/X11/Xsession.d
> You can also use ~/.xsessionrc which is sourced from a file in
> /etc/X11/Xsession.d
> You probably dont want to source .bashrc directly, but you can create
> another file to hold environment variables and source it from
> .xsessionrc AND .bashrc/.profile

Thank you. I followed your recommendations but it does not seem to work.

I tried this by creating a file /etc/X11/Xsession.d/99xsession with the 
following content:

if [ -r "$HOME/.xsessionrc" ] ; then
. "$HOME/.xsessionrc"
fi

I then added some code in .xsessionrc that adds a log message to a file in 
/tmp. After this I sourced /etc/X11/Xsession.d/99xsession to confirm that the 
everything worked.

After rebooting the VM, the environment variable was not set, and there was no 
entry in the file in /tmp which is updated by the script.

>From this I draw the conclusion that the scripts in /etc/X11/Xsession.d are 
>not actually sourced when booting a VM.

Did I do something wrong, or is my analysis of the situation incorrect?

-- 
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/ce154711-4950-4233-85bc-532f412430df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Settings environment variable system-wide in a VM

[Elias Mårtenson]

How do I set an environment variable that will be accessible to all programs 
started in a session?

Specifically, I'm trying to set KRB5CCNAME in $HOME/.profile, and it becomes 
available from a terminal session as expected, but it never gets set in 
Nautilus, where it is needed.

Looking at /etc/X11/xinit/xinitrc, that script sources another script which in 
turn sources $HOME/.profile, so as far as I can tell, this should work.

Could it be that the Nautilus server isn't started by the user's session 
itself? If so, how do I work around this?

-- 
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/ac3d022d-ee35-4890-8b50-23118d96ca23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Using Salt to provision an appvm

[Elias Mårtenson]

I'm trying to use Salt to set up my standard configuration, which includes a 
few appvms used for various purposes.

I have been able to create scripts that sets up the dom0 configuration, creates 
the VMs, and configures the templates.

But when I try to use the same mechanism to configure the appvms (specifically, 
updating /rw/config/rc.local, installing some default configuration in the 
user's home directory etc) that script simply doesn't seem to run.

I tried to create a minimal test case, and this is what I have done:

/srv/salt/custom/backup.top:

backup:
  ^backup$:
-match: pcre
- custom.backup


/src/salt/custom/backup.sls:

create-test-file:
  cmd.run:
- name: echo foo > /home/user/foo.txt
- runas: user


I also have a rule that actually creates the "backup" vm.

After running this, nothing happens in the appvm, and the 
/var/log/qubes/mgmt-backup.log contains the following:


calling 'state.highstate':
output: backup:
output: - No matching salt environment for environment 'backup' found.
output: - No matching sls found for 'custom.backup' in env 'backup'.
exit code: 0


What have I done wrong here?

Regards,
Elias

-- 
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/4f8b4c25-9c75-4466-aeef-68c238ee87f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: GPU?

[Elias Mårtenson]

On Tuesday, 16 January 2018 04:02:13 UTC+8, Vít Šesták  wrote:
> It might be possible, just no one has implemented it in a way that does not 
> require complex processing by trusted parts of system.
> 
> There is an attempt called XenGT (for Intel iGPUs), but I am not sure about 
> its state and at least it is not integrated to Qubes yet.

I'm sure that if someone wants to take it up as a GSoC project, a lot of people
would be very happy. :-)

-- 
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/4bb5de18-3a7c-4ce0-8d1e-ecdad5d2e4b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] What happened to domain manager in 4?

[Elias Mårtenson]

On 8 December 2017 at 00:16, Unman  wrote:


> Backup/restore is already on the target list.
> What doesnt seem to be at the moment is the ability to show all qubes,
> and how they are connected, and what their status is. That's a nice
> target.
>

If by "status" you include the update state, then that would make the new
solution on par with the old VM manager, yes?

Regards,
Elias

-- 
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/CADtN0WLuebv04T%3DQRfaV%2BkE4vyAghBKquFB7LJRk-z%3D47TZfLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] What happened to domain manager in 4?

[Elias Mårtenson]

On 7 December 2017 at 12:57, Chris Laprise  wrote:


> I myself find it strange and frustrating using Qubes VMs without the
> visual reminders for the templates they're based on, updates, last backup
> date, etc. If I need to see the template for a VM, going into VM settings
> feels like cognitive dissonance.
>
> Qubes might benefit from focusing the UI on a Qubes Manager-like
> interface, even to the point where guest apps are launched from it. Why
> shoehorm the new paradigm into existing DE tools? That will not get you the
> attention of the DE projects or potential userbase.


I don't think anybody disagrees with you. No one in this thread has said
that they don't want to see
a new management UI. And I do believe that even the devteam agrees with
this. That suggests that
if someone puts something together there is a high chance that it could be
included in Qubes
proper.

I have said that I would like to do the work, but there are factors that
make it impossible for
me to invest any time into it at this time. The surely must be others who
are willing to put
in the time to do it?

There are certainly enough people complaining about it that there should be
at least some
people able to scratch that itch.

If you're not capable of doing the work, I understand it can be frustrating
to see no progress being
done on aspects of the system that you feel is important, but do keep in
mind that the devteam
are resource-constrained and they have to follow their own priorities.

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

Re: [qubes-users] What happened to domain manager in 4?

[Elias Mårtenson]

On Thursday, 7 December 2017 11:56:13 UTC+8, mikih...@gmail.com  wrote:

> I stopped using qubes because my use case depends on it. 

I'm not going to judge the way you use the software, but I am curious
as to what kind of use case you have that made the VM manages so important
that you literally can't use Qubes without it?

-- 
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/112ca326-6d07-4145-a25f-9b8f43dcc457%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] What happened to domain manager in 4?

[Elias Mårtenson]

On Thursday, 7 December 2017 00:14:04 UTC+8, Tom Zander  wrote:

> On Wednesday, 6 December 2017 16:08:28 CET Unman wrote:

> > "useful, but wasnt any good" - do you mean buggy or poorly designed?
> > What 2 features should be implemented/fixed?
> > 
> > I confess I rarely use the Manager, so don't have a feel for what's wrong
> > with it.
> 
> To be clear, the main reason the old one is removed seems to be that it 
> would have had to be reimplemented due to the architecture changes in 4.0

I had a script that updated the templatevms and it was written in Python,
taking advantage of the API. This script stopped working in 4.0. I rewrote
it to use the commandline tools instead.

Perhaps a new UI could also be based on those tools. Without a need to use
Python, such UI could be implemented in any language. That would be an
interesting project.


> To support the point of view of "useful but wasn't any good", let me explain 
> what I think such a tool should behave like.

I was the one who said that, and your statement is an almost spot-on summary
of my opinion.

> The first issue with the old tool, and also with some of the new tools, are 
> that you already have to know how things work in order to be able to use it.
> For instance the terminology 'appvm', 'templatevm' etc are completely not 
> explained anywhere. You have to go to a website to learn what the mean.

The 3.2 VM manager, with all is faults, did help newcomers a single place
to see what was going on. It's not harder in 4.0, but I'd imagine that to
a newcomer it would look a lot more opaque.

This, I believe, is the most important feature of a new UI; the ability
to guide a new user to the proper usage of the OS.

> A clear success story of Qubes is its networking, abstracting the netVm is 
> done to add security without having any significant impact on usability.
> Practically speaking, normal users can ignore the whole networking setup as 
> it "just works".

For a new UI, I imagine a graphical representation of the networking setup.
Think boxes with arrows, showing connections, ports, IP-addresses, etc.
In fact, hardware assignments could be represented there as well.

Do a Google image search for "flow control ui" to see what I'm thinking of.

> * Which VMs are in which state. If you start something and the netvm/
> firewall VM are auto-started, this is not at all clear to the user. If 
> something fails, it gets even worse.

Easy access to the logs from here would be a most welcome quality-of-life
improvement.

> * Graphical configuration of multiple qubes. Even in 3.2 not being able to 
> open more than one config dialog at a time was silly.

Yes. The fact that the old VM manager was blocking, and you couldn't do
anything with it while an operation was in progress was one of its biggest
flaws.

-- 
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/73f4d6f6-6595-4c31-af4c-a5d6b4631608%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] What happened to domain manager in 4?

[Elias Mårtenson]

On Wednesday, 6 December 2017 21:58:56 UTC+8, Unman  wrote:
> On Mon, Dec 04, 2017 at 03:34:25PM -0800, r...@tuta.io wrote:
> > Just read it. Thats fucking stupid. 
> > 
> > -- 
> 
> I think it's safe to say that opinion is divided on the removal.

I liked the old tool. However, I am also on the side of agreeing with its 
removal.

The old tool was useful, but it wasn't any good. As Tom Zander suggested 
earlier,
someone else should create a new GUI. Like him, I also took a look at it but
decided not to, since Python is one of the languages I like the least, and when
it comes to unpaid work, I prefer doing it in a language I actually enjoy using.

There may be people out there that enjoy writing GUIs in Python, and I'm sure 
the
entire Qubes community would be immensly grateful if someone stepped up to the
task. I certainly would be.

-- 
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/487a2295-f96a-49d2-a4b4-d84afd738649%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Creating a HVM in Qubes 4.0rc2 for Windows 7 Qube

[Elias Mårtenson]

On Wednesday, 15 November 2017 09:24:25 UTC+8, car...@gmail.com  wrote:

> > After tinkering with the memory and hard drive allocation I got it to work. 

> The windows tools aren't in the repository. Are they available for q4? Is 
> there
> a place where I can manually download the windows-tools-iso?

Even if you're able to install it, it doesn't work. I tried restoring a backup
of a Win7 VM that I had been using in Qubes 3.2, and while it starts correctly
the VM crashes within seconds.

I'm suspecting it happens when the Windows VM attempts to communicate over the
network. But I have nothing more than circumstantial evidence to that fact.

-- 
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/e6a80d2a-d013-442e-9902-d17ad884bcff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Can Qubes 4 do SVM VM snapshots like in 3.2?

[Elias Mårtenson]

In 3.2, the DVM stored a snapshot of the booted system so that new dispvm's 
could be booted very quickly. This doesn't seem to happen in 4.0, which cuases 
them to take over 30 seconds to start.

I recall reading somewhere that 4.0 would support creating snapshots for all 
VM's, not just DVM's. Is this true? And if so, how do I do it? I woul dhave 
assumed there would be a qvm-prefs setting for it, but I haven't been able to 
find anything.

Regards,
Elias

-- 
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/9061bddd-0304-438e-92ac-7b29ceef4c80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Why is there no qubes manager in V4.0?

[Elias Mårtenson]

On Wednesday, 1 November 2017 12:23:22 UTC+8, Desobediente  wrote:
> Just felt like I have to say that I would love to stop everything I'm doing 
> in 
> my life to write a proper Qubes Manager for 4.
> 
> But I don't see that happening. It sounds trivial at first, but it requires a 
> lot of testing and it will have bugs as the current one does.

I agree. It wouldn't take long to put something together that does the basic 
stuff, but to make it as feature complete as the Qubes Manager in 3.2 let alone 
implement all the cool features we all want would take more time than one might 
think.

-- 
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/d67165f8-cb7f-44e6-84dd-c5daff025632%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Why is there no qubes manager in V4.0?

[Elias Mårtenson]

On Wednesday, 1 November 2017 11:32:58 UTC+8, Fun Zork  wrote:

> And not just that.  If I'm being honest, it is also because it makes me feel 
> more like I am running a cool, unique, complicated OS.  The qubes manager is 
> kind of Qubes' signature look.  It's 
> 
> I agree that the UI for it is kind of meh in 3.2, but that's mostly a 
> graphical > issue IMO.  Personally, I'd rather see 4.0 have a qubes manager 
> that is 
> functionally the same as in 3.2, but with a more modern look.  Darker, new 
> icons.

I agree with you, but at the same time it is very clear that the team are very 
resource-constrained. I'm sure they would love to implement a better 
replacement but there is only so much they can do in a day, and there are 
plenty of other issues that I'd rather see them work on.

I have considered working on such a tool myself, but it's a lot of work and I 
have other projects I need to work on as well.

-- 
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/df99834b-e47e-4e32-99c8-23b6cd592359%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Windows 7 VM on Qubes $

[Elias Mårtenson]

On 3 October 2017 at 18:48, Foppe de Haan <0spinbo...@gmail.com> wrote:

> On Tuesday, October 3, 2017 at 11:01:47 AM UTC+2, lok...@gmail.com wrote:
> > On Tuesday, 3 October 2017 16:56:24 UTC+8, Foppe de Haan  wrote:
> >
> > > Did the backup restoration process work at all, or did it error and
> skip the win7 VM?
> >
> > Thanks for the reply.
> >
> > Please allow me to do it all from the beginning again and record all the
> logs. I'll update in a day or so.
>
> To clarify: when I try to restore a win7 VM from 3.2, it skips restoring
> that VM, citing an error, but does create an entry with that name (which
> doesn't work). I wasn't sure whether that was due to corruption of the
> backup, or a bug, so I haven't reported it yet.
>

Thanks. I wasn't in front of the computer when the restoration happened (it
was done by someone else). That's why I can't say what kind of errors were
displayed. That's why I want to do it again and capture a log.

When trying to start the VM using qvm-start, a window is opened with some
diagnostic information scrolling past (too fast to see what's going on),
and then the window disappears and the VM is shut down. Trying to go to
settings shows a python error.

-- 
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/CADtN0WK5%3DLrftmdWee%3Daad_b6t-S4yK%3DfSrs8mSD0mdBNLvT2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I test that my AEM configuration is correct?

[Elias Mårtenson]

On 20 July 2017 at 17:49, Patrik Hagara  wrote:


> Oh yes, now I remember! This was definitely a Linux kernel issue for
> me, it just didn't setup VGA console logging yet so it seems like a
> tboot hang. See the mail I just sent about updating dom0 kernel.


I now have Kernel 4.9.35, which is a great thing (I can now disable tap to
click, finally) .

However, I still get stuck in a bootloop when I try to start AEM. Is there
a way I can tell if it even starts running the kernel or if it crashes
before it's loaded?

-- 
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/CADtN0WKQp%3DJnYj2XssFvK%2BvhG-_4x1xFjkSMyaGzcWynhbHOPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I test that my AEM configuration is correct?

[Elias Mårtenson]

On 20 July 2017 at 17:31, Patrik Hagara  wrote:

Now that I tried removing min_ram from my setup it still works, so
> perhaps the fix for this was something different... Can't recall what
> though. :-\
>
> Ah well, guess we'll have to go back to taking pictures of the screen.
>

Thank you so much for spending time on this.

I took another set of pictures: https://photos.app.goo.gl/IZFNokdsfClsWwNz2

Regards,
Elias

-- 
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/CADtN0WK0s7PmebFvj%2B%2BBdPtK9w%2BzFPp-pLzOR2nX0yTLxSa-TA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I test that my AEM configuration is correct?

[Elias Mårtenson]

On 20 July 2017 at 16:51, Patrik Hagara  wrote:


> > Thank you! You were right of course. There was a disabled option
> > referring to "trusted execution" that was turned off. Enabling that
> > gave me much more than 3 pages of debug output.
> >
> > Unfortunately, the machine reboots shortly after the "SENTER",
> > causing the machine go into an infinite bootloop.
> >
> > Note that it never even gets to the point where it asks for the TPM
> > password.
> >
> > Would screenshots of all the pages of debug be useful?
> >
> > Thanks and regards, Elias
> >
> This sounds like the exact same issue I've encountered -- and managed
> to fix by adding "min_ram=0x200" to the tboot cmdline arguments
> (see tboot readme [1] for details).


Thank you for your suggestion. I tried this (and also read the README file
you helpfully linked to).

Unfortunately it did not change the behaviour, and the machine still
reboots at some point after SENTER.

Regards,
Elias

-- 
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/CADtN0WKARFb%3DrriRokydSMMesVqCbGOuMXK%3Di3GJDxH%3D59ue8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How can I test that my AEM configuration is correct?

[Elias Mårtenson]

On 20 July 2017 at 15:58, Patrik Hagara  wrote:


> This looks to me like tboot either wasn't loaded at all or memory
> logging is disabled.
>
> Check the tboot cmdline used -- search for the following in
> /boot/grub2/grub.cfg:
>
>   multiboot /tboot.gz placeholder logging=memory,serial
>
> If memory logging is enabled, try adding vga there too (plus a delay
> to be able to read the output):
>
>   multiboot /tboot.gz placeholder logging=memory,serial,vga vga_delay=10
>
> You'll have 10 seconds per screenfull of tboot log messages, may as
> well take photos. :)


Thanks. I got three screenfuls of information. I've shared the pictures
here: https://photos.app.goo.gl/xNaxca5fxviwmfw12

The error "failed to get public data of 0x4001 in TPM NV" seems
interesting, but I have no idea how to deal with it.

Regards,
Elias

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

Re: [qubes-users] Re: Building Qubes from source, strange error.

[Elias Mårtenson]

On 27 March 2017 at 18:19, Andrew David Wong  wrote:

They won't be identical until we achieve reproducible builds:
>
> https://github.com/QubesOS/qubes-issues/issues/816


The builds are significantly different. The main difference that I noted
was that while the image I can download from the Qubes site is
approximately 4 GB in size, the one I built from source is 2.3 GB.

Also, using the home-built image, the graphics is incredibly slow, taking
several seconds to repaint the screen on the laptop on which I am doing my
tests. The official image doesn't have that issue. These two facts alone
suggests to me that there are some major components missing from the image
that I built.

Finally, I have to report that I can't get the network running on the Dell
Latitude 7480 even with a home-built image. Thus, I have to conclude that
until a new release (3.2.1 or 4.0), this machine can't be used with Qubes.
This is sad, since hardware-wise it'd be a perfect machine for the purpose.

Regards,
Elias

-- 
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/CADtN0W%2Bfs96-2uv62R2axNwaxCVt_wVYncms-Q2bWJCpk3MWXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Building Qubes from source, strange error.

[Elias Mårtenson]

On 23 Mar 2017 00:19, "Unman"  wrote:

Strange because the builder.conf there has linux-utils as entry before
artwork.
Did you succesfully build linux-utils?


I'm not sure. I made the mistake of not capturing output to a file. Is
there an easy way to check?

Regards,
Elias

-- 
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/CADtN0W%2BQ1TPYWeQfynAyq_H7UYriczDQ62J%3DOop2bN15HE%2BHsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Building Qubes from source, strange error.

[Elias Mårtenson]

On 23 Mar 2017 00:00, "Unman"  wrote:


How did you get your builder.conf file? The build order is important
and it looks as if you are trying to build artwork before you have
built qubes-utils.

You can either comment out artwork for the moment, build the rest and
then build artwork or rejig the order in builder.conf, and try the build
again.


I got the builder.conf file by copying it from examples/, as was explained
in the documentation that I linked to.

All I really did after setting up the gpg keys was to run make get-sources,
followed by make qubes.

If things were built in the wrong order, there must be a problem with the
makefile, since it was all run as part of make qubes from a clean source
directory.

Or, I have missed something obvious, which wouldn't be too surprising.

Regards,
Elias

-- 
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/CADtN0W%2B%2BYxrLAugsHUGcCgr%3DfvPi700CgxYHKd1RR67ZhxyvMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Fwd: HCL - Dell Latitude E7470

[Elias Mårtenson]

On 17 February 2017 at 13:19, taii...@gmx.com  wrote:

I would also insist on linux touchpad drivers, which again you can do
> (because it is a business laptop)
>

I think it's possible to get it to work in Fedora 24, but Qubes dom0 is
based on Fedora 23.

I'll try it again once Qubes 4 comes out.

Regards,
Elias

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

[qubes-users] Fwd: HCL - Dell Latitude E7470

[Elias Mårtenson]

(resend, with attachments this time)

I've been using Qubes 3.2 on this laptop for a month or two now, and pretty
much everything works well.

Note that immediately after installing the system the WLAN didn't work. I
connected using ethernet and did a software update. After this the WLAN
worked correctly.

The laptop seems to have TPM, but when I try to enable it it tells me I
need to switch to UEFI. Unfortunately AEM doesn't support UEFI, so it can't
be used.

I have also been unable to disable tap-to-click on the touchpad. Apparently
this is because the touchpad isn't supported but if you're OK with having
tap-to-click enabled the touchpad itself works well.

Regards,
Elias

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


Qubes-HCL-Dell_Inc_-Latitude_E7470-20170216-184205.cpio.gz
Description: GNU Zip compressed data


Qubes-HCL-Dell_Inc_-Latitude_E7470-20170216-184205.yml
Description: application/yaml

[qubes-users] HCL - Dell Latitude E7470

[Elias Mårtenson]

I've been using Qubes 3.2 on this laptop for a month or two now, and pretty
much everything works well.

Note that immediately after installing the system the WLAN didn't work. I
connected using ethernet and did a software update. After this the WLAN
worked correctly.

The laptop seems to have TPM, but when I try to enable it it tells me I
need to switch to UEFI. Unfortunately AEM doesn't support UEFI, so it can't
be used.

I have also been unable to disable tap-to-click on the touchpad. Apparently
this is because the touchpad isn't supported but if you're OK with having
tap-to-click enabled the touchpad itself works well.

Regards,
Elias

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