Re: [qubes-users] App menu not syncing

2020-05-14 Thread jiggermast47


On 5/11/20 3:20 PM, jiggermas...@posteo.de wrote:
> Hi,
>
> I can't sync app menus from one of my standalone Debian 10 VMs. In dom0
> I get:
>
> [user@dom0 ~]$ qvm-sync-appmenus VMNAME
>
> Traceback (most recent call last):
>   File "/usr/bin/qvm-sync-appmenus", line 9, in 
>     load_entry_point('qubesdesktop==4.0.20', 'console_scripts',
> 'qvm-sync-appmenus')()
>   File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
> 397, in main
>     new_appmenus = retrieve_appmenus_templates(vm, use_stdin=use_stdin)
>   File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
> 373, in retrieve_appmenus_templates
>     new_appmenus = get_appmenus(vm if not use_stdin else None)
>   File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
> 155, in get_appmenus
>     "Error getting application list")
> qubesadmin.exc.QubesException: Error getting application list
>
>
> .x-session-errors in the VM shows:
>
> executed QUBESRPC qubes.GetAppmenus dom0 pid 10029
> send exit code 2
> pid 10029 exited with 2
>
> When I install something via apt, I get this, maybe a hint:
>
> Processing triggers for qubes-core-agent (4.0.55-1+deb10u1) ...
> execv: Permission denied
>
>
> Any idea where to look?
>
> Best
>

Hi,

Any ideas? I noticed this is valid for all my Debian StandaloneVMs.

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/55147bac-f625-5c3c-bba9-b1622700d4ee%40posteo.de.


[qubes-users] App menu not syncing

2020-05-11 Thread jiggermast47
Hi,

I can't sync app menus from one of my standalone Debian 10 VMs. In dom0
I get:

[user@dom0 ~]$ qvm-sync-appmenus VMNAME

Traceback (most recent call last):
  File "/usr/bin/qvm-sync-appmenus", line 9, in 
    load_entry_point('qubesdesktop==4.0.20', 'console_scripts',
'qvm-sync-appmenus')()
  File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
397, in main
    new_appmenus = retrieve_appmenus_templates(vm, use_stdin=use_stdin)
  File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
373, in retrieve_appmenus_templates
    new_appmenus = get_appmenus(vm if not use_stdin else None)
  File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
155, in get_appmenus
    "Error getting application list")
qubesadmin.exc.QubesException: Error getting application list


.x-session-errors in the VM shows:

executed QUBESRPC qubes.GetAppmenus dom0 pid 10029
send exit code 2
pid 10029 exited with 2

When I install something via apt, I get this, maybe a hint:

Processing triggers for qubes-core-agent (4.0.55-1+deb10u1) ...
execv: Permission denied


Any idea where to look?

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/02b3b71d-ea19-3f95-c04f-f6ca563dc430%40posteo.de.


Re: [qubes-users] LVM not using full partition size

2020-05-10 Thread jiggermast47


On 5/10/20 8:50 PM, dhorf-hfref.4a288...@hashmail.org wrote:
> going from your earlier numbers, something like ... 
>   lvresize --poolmetadatasize 1G qubes_dom0/pool00
>
> then resizing the data volume ...
>   lvresize -L +99G qubes_dom0/pool00
>
> (if it complains on that step, reduce to +98G or so)
>
> i would leave any "fractional GB" leftovers free as a reserve in
> case i have to dig myself out of a "metadata full" situation. 
>
> verify with pvs/pvs that the "Free" space is (mostly) gone,
> then check with lvs that pool00 now is bigger and still has
> a (much) lower meta% than data%. 
>
Thanks a lot, that did it! Any idea, why the installer would leave that
space free in the first place?

-- 
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/b9154b2b-831d-ff0c-0485-10b0be34d1be%40posteo.de.


Re: [qubes-users] LVM not using full partition size

2020-05-10 Thread jiggermast47


On 5/10/20 8:07 PM, dhorf-hfref.4a288...@hashmail.org wrote:
> (please dont top post)
>
> On Sun, May 10, 2020 at 07:51:01PM +0200, jiggermas...@posteo.de wrote:
>> Yes, that's what I mean, mixed up terminology there. The pool has now
>> 584 GiB, before the reinstall it had around 670 GiB - I am wondering
>> where that additional 84 GiB ended up (and I need it, currently I can't
>> restore all my VMs).
> "fdisk -l" should show you how big the partition is.
> "pvs" should show you how big the luks device is. 
> "vgs" should show you how big the volume group is.
>
> pvs + vgs also have a "free" column that shows if there is unused
> space on that level. 
>
>
Okay, there seems to be 100g unused space? How can I claim that?

[user@dom0 ~]$ sudo pvs
  PV    VG Fmt 
Attr PSize   PFree 
  /dev/mapper/luks-f81958da-4f7e-4146-8475-554f4ce32289 qubes_dom0 lvm2
a--  701.28g 100.00g
[user@dom0 ~]$ sudo vgs
  VG #PV #LV #SN Attr   VSize   VFree 
  qubes_dom0   1 168   0 wz--n- 701.28g 100.00g

-- 
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/22d44374-dea0-7ace-54bf-4333ad326ceb%40posteo.de.


Re: [qubes-users] LVM not using full partition size

2020-05-10 Thread jiggermast47
Yes, that's what I mean, mixed up terminology there. The pool has now
584 GiB, before the reinstall it had around 670 GiB - I am wondering
where that additional 84 GiB ended up (and I need it, currently I can't
restore all my VMs).

lvs -a shows

  LV VG Attr  
LSize   Pool   Origin  Data%  Meta% 
Move Log Cpy%Sync Convert
  [lvol0_pmspare]    qubes_dom0 ewi---
600.00m 
 

  pool00 qubes_dom0 twi-aotz--
584.84g    99.11 
56.59  
  [pool00_tdata] qubes_dom0 Twi-ao
584.84g 
 

  [pool00_tmeta] qubes_dom0 ewi-ao
600.00m 
 

  root   qubes_dom0 Vwi-aotz--
584.84g pool00
2.53  
  swap   qubes_dom0 -wi-ao 
15.27g  


   

On 5/10/20 7:05 PM, dhorf-hfref.4a288...@hashmail.org wrote:
> On Sun, May 10, 2020 at 05:12:04PM +0200, jiggermas...@posteo.de wrote:
>> The partition size for the LVM correctly shows about 700 GiB, but the
>> root storage then only gets 584, and I am not able to set it higher.
> the root partition is just the root partition for dom0.
> if you want to see how much space is available to lvm, you need
> to check with "vgs" or "lvs qubes_dom0/pool00".
>
>
>> Where did the rest of the space end up? Did I do something wrong during
> for the full picture you can try "lvs -a". 
>
>

-- 
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/e7372c64-d265-1730-1843-d0b87cd0a143%40posteo.de.


[qubes-users] LVM not using full partition size

2020-05-10 Thread jiggermast47
Hi,

I just reinstalled Qubes 4.0.3 (had 4.0 before) on my machine because of
some issues I had. Now my LVM has significantly less space than before.
My old installation had an LVM with about 670 GiB, now it is only 584 GiB.

In the installer, I deleted all the Qubes partitions there were (I also
have a Windows partition) through the auto partitioner with "make
additional space available", same I did with the previous install.

The partition size for the LVM correctly shows about 700 GiB, but the
root storage then only gets 584, and I am not able to set it higher.

Where did the rest of the space end up? Did I do something wrong during
the partitioning? Is there a way to fix this without having to reinstall
again? I am not very familiar whith the whole LVM concept, so please
excuse if I use any terminology wrong.

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/922014bc-5fd7-3fae-7345-d74e557a62a8%40posteo.de.