Re: [qubes-users] USB controllers

[Franz]

On Sun, Jun 20, 2021 at 11:15 PM Franz <169...@gmail.com> wrote:

> Hello all,
>
> I abandoned the computer for a week or so, without doing anything, then,
> for some mysterious reason the mouse worked again. So I  am profiting doing
> the tests Unman asked
>
>
>
>>
>> > > Many thanks it worked perfectly
>>> > >
>>> >
>>> > It worked perfectly for a week or so, then the mouse stopped working.
>>> > Thomas at Vikings, who built the D8 computer with preinstalled
>>> coreboot,
>>> > says it should be a Qubes issue.
>>> >
>>> > How may I tell if it is a Qubes issue or a hardware issue?
>>> > best
>>> >
>>>
>>> You aren't clear on what is happened here, because you haven't provided
>>> sufficient detail..
>>> Do you mean that you allocated a USB controller to a sys-usb, to use
>>> with the mouse. After a week, the mouse stopped working.
>>> When both controllers were attached to a single usb-qube the mouse
>>> worked without interruption.
>>> Is that the position?
>>>
>>
>> Yes, but it worked also when only one USB controller was allocated to the
>> mouse qube.
>>
>>>
>>> Did the other USB qube continue to work?
>>>
>>
>> yes it works, I am able to mount an external USB drive. Also lsusb works
>> and shows the external USB drive
>>
>>
>>> If you type lsusb in the "mouse"-usb do you see the mouse attached?
>>>
>>
>> No,  lsusb hangs, with no output
>>
>
> Now lsusb on mouse-usb gives the following output:
>
> [user@sys-usb ~]$ lsusb
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> So yes, I see the mouse attached
>
> .
>>
>>> If you attach another usb device, does lsusb and dmesg show the device
>>> being attached?
>>>
>>
>> dmesg on mouse qube gives a lot of errors, even various red ones. But I
>> am totally unable to understand if they are serious or related to the mouse
>> issue.
>>
>>
> Yes I see a usb key attached
>
> dmesg and journalctl are enclosed as an html files with full colors
>
>
>
Other strange things happened:
To restore a backup I connected an external USB disk with the backup to the
second USB qube and under the restore command I clicked on the external USB
disk to mount it. When I did that, a black background message on the upper
right part of the screen told me that the disk was removed, while, at the
same time it was NOT removed at all because the triangle showed that the
disk was mounted and the  content of the external USB disk was shown. Using
my old and trusted x230 for many years this never happened. So I suppose it
is strange.

Also, the computer seems much slower than my old x230, which is strange
being a new computer

If you want me to try commands and report results, just ask, I am very
willing to do anything that may be helpful to solve these problems.
best

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAPzH-qDZ_msXkX1Wn6hfEu_Y-PQE3yahgk4fNRPsF-3nh_mdWQ%40mail.gmail.com.

[qubes-users] How to assign keyboard shortcuts to a VM?

[Michael Singer]

Dear Qubes community,

I am looking for a way to execute a command with a keyboard shortcut. For 
example, the command "screenshot" should start the screenshot program within 
the respective VM or the command "nautilus" should pop up a file browser window 
of the VM that is currently being worked with.

If I set up a keyboard combination for this in dom0 in the xfce keyboard 
settings, then I would have to set a different keyboard combination for each 
Qube:

Ctrl+Alt+1 for Qube1: qvm-run Qube1 nautilus
Ctrl+Alt+2 for Qube2 qvm-run Qube2 nautilus

So, how can I do the same thing at the qube level instead of in dom0?

You can install the autokey program, but it requires me to write a python 
script, and I don't know how to express a simple shell command in python.

All the best
Michael Singer

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/67cc8511-0717-10b0-8c66-44de68261cbe%40posteo.de.

Re: [qubes-users] Troubleshooting: ArchLinux install seems to be stuck, logs attached

[unman]

On Mon, Jun 21, 2021 at 08:57:07AM -0400, Haisam Khalil wrote:
> On Mon, Jun 21, 2021 at 6:52 AM unman  wrote:
> 
> > On Sun, Jun 20, 2021 at 09:14:47AM -0700, Chrome wrote:
> > >
> > > Doesn't matter because I give up on this approach or the debian
> > approach. I
> > > nuked the fedora 32 minimal template and will give it a fresh start.  I
> > can
> > > tell you for sure I followed your instructions and the documentation and
> > > got no further than I was when I started this post.
> > >
> > > Starting fresh: how would you install ArchLinux in preparation for
> > > installing blackarch on top of it?
> > >
> >
> > Good luck with the build - use a 33 template, turn up logging and post
> > your results.
> > If you want a prebuilt template, I have recent builds at
> > https://qubes.3isec.org
> 
> thank you unman, I???ll run man on the commands to figure out the logging.
> I???ll post up when done. Appreciate all the help to date.
> 
> > 
> >
> -- 
> Best,

There are "DEBUG" and "VERBOSE" settings in builder.conf, explained in
doc/Configuration.md
Those parameters will impact on the log files in build-logs (in
particular I think having them set will not create a log file for the
template build), but they will produce a far more verbose output.

This should help you to identify where the problem lies.
Best of luck

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20210621130751.GA15648%40thirdeyesecurity.org.

Re: [qubes-users] Troubleshooting: ArchLinux install seems to be stuck, logs attached

[Haisam Khalil]

On Mon, Jun 21, 2021 at 6:52 AM unman  wrote:

> On Sun, Jun 20, 2021 at 09:14:47AM -0700, Chrome wrote:
> >
> > Doesn't matter because I give up on this approach or the debian
> approach. I
> > nuked the fedora 32 minimal template and will give it a fresh start.  I
> can
> > tell you for sure I followed your instructions and the documentation and
> > got no further than I was when I started this post.
> >
> > Starting fresh: how would you install ArchLinux in preparation for
> > installing blackarch on top of it?
> >
>
> Good luck with the build - use a 33 template, turn up logging and post
> your results.
> If you want a prebuilt template, I have recent builds at
> https://qubes.3isec.org

thank you unman, I’ll run man on the commands to figure out the logging.
I’ll post up when done. Appreciate all the help to date.

> 
>
-- 
Best,

Haisam Khalil
C: 347-397-0124

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAGD7%2Bv70pFGaioki9bJn_vBGzb7_MzVEAUgA8KRbNcSaJKRcEQ%40mail.gmail.com.

Re: [qubes-users] VPN up/down pop up not working?

[Stumpy]

On 2021-06-21 17:20, unman wrote:

On Mon, Jun 21, 2021 at 11:53:17AM +, Stumpy wrote:

On 2021-06-18 03:15, Sven Semmler wrote:
> On 6/17/21 8:59 AM, Stumpy wrote:
> > I guess I will just grin and bear it as its not crucial, I was just
> > hoping the fix might be simple like Sven's suggestion (thanks for
> > the suggestion though Sven!).
>
> No problem. To further drill down and what could be the cause ... what
> happens when you type
>
> notify-send test
>
> in your VPN qube? I am guessing, but there is a very high chance
> that's exactly what the qtunnel script will call.
>
> /Sven
>
> --
>  public key: https://www.svensemmler.org/2A632C537D744BC7.asc
> fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7

Hi Sven,
Thanks for the follow up.
When I type notify-send test in the vpn appvm a small notification 
"send"
pops up in the top right side of my screen, that seems like a positive 
sign?


Btw, per unman's question, I installed CentOS full template and tried
starting the vpn appvm and nothing happened, then tried using the full 
fed33

template and I got the vpn up popup.

Cheers



So, it would seem to be a Centos issue, and not a "minimal template"
issue.


Yep. Also tried Debian 10 (not minimal), no popup. so far the only 
template I have tried that seems to work (have a vpn up/down popup) out 
of the box is fed33 full.


--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/16a9dade65fd2d4cb2d980b434e5758b%40posteo.net.

Re: [qubes-users] VPN up/down pop up not working?

[unman]

On Mon, Jun 21, 2021 at 11:53:17AM +, Stumpy wrote:
> On 2021-06-18 03:15, Sven Semmler wrote:
> > On 6/17/21 8:59 AM, Stumpy wrote:
> > > I guess I will just grin and bear it as its not crucial, I was just
> > > hoping the fix might be simple like Sven's suggestion (thanks for
> > > the suggestion though Sven!).
> > 
> > No problem. To further drill down and what could be the cause ... what
> > happens when you type
> > 
> > notify-send test
> > 
> > in your VPN qube? I am guessing, but there is a very high chance
> > that's exactly what the qtunnel script will call.
> > 
> > /Sven
> > 
> > --
> >  public key: https://www.svensemmler.org/2A632C537D744BC7.asc
> > fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7
> 
> Hi Sven,
> Thanks for the follow up.
> When I type notify-send test in the vpn appvm a small notification "send"
> pops up in the top right side of my screen, that seems like a positive sign?
> 
> Btw, per unman's question, I installed CentOS full template and tried
> starting the vpn appvm and nothing happened, then tried using the full fed33
> template and I got the vpn up popup.
> 
> Cheers
> 

So, it would seem to be a Centos issue, and not a "minimal template"
issue.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20210621122059.GA15434%40thirdeyesecurity.org.

Re: [qubes-users] VPN up/down pop up not working?

[Stumpy]

On 2021-06-18 03:15, Sven Semmler wrote:

On 6/17/21 8:59 AM, Stumpy wrote:
I guess I will just grin and bear it as its not crucial, I was just 
hoping the fix might be simple like Sven's suggestion (thanks for the 
suggestion though Sven!).


No problem. To further drill down and what could be the cause ... what
happens when you type

notify-send test

in your VPN qube? I am guessing, but there is a very high chance
that's exactly what the qtunnel script will call.

/Sven

--
 public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7


Hi Sven,
Thanks for the follow up.
When I type notify-send test in the vpn appvm a small notification 
"send" pops up in the top right side of my screen, that seems like a 
positive sign?


Btw, per unman's question, I installed CentOS full template and tried 
starting the vpn appvm and nothing happened, then tried using the full 
fed33 template and I got the vpn up popup.


Cheers

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/81fcee118c435bc28b5859f26421301f%40posteo.net.

Re: [qubes-users] Troubleshooting: ArchLinux install seems to be stuck, logs attached

[unman]

On Sun, Jun 20, 2021 at 09:14:47AM -0700, Chrome wrote:
> 
> Doesn't matter because I give up on this approach or the debian approach. I 
> nuked the fedora 32 minimal template and will give it a fresh start.  I can 
> tell you for sure I followed your instructions and the documentation and 
> got no further than I was when I started this post.
> 
> Starting fresh: how would you install ArchLinux in preparation for 
> installing blackarch on top of it?
> 

Good luck with the build - use a 33 template, turn up logging and post
your results.
If you want a prebuilt template, I have recent builds at
https://qubes.3isec.org

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20210621105240.GE14839%40thirdeyesecurity.org.