Re: [qubes-users] No space left on device

2021-11-05 Thread Ludovic

Hi Franz,

On 05/11/2021 02:00, Franz wrote:
Trying to update dom0 I get a long list of "No space left on device", 
but the hard disk icon on the panel tells that total disk usage is 
only 23.4%

lvm 23.4% 195.4GiB/835.8 GIB varlibqubes.


And what about the disk space left on the updateVM ? (probably sys-firewall)


--
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/187a4bdd-ab94-cfd8-cd2c-0bd7a82df6e2%40zyrianes.net.


Re: [qubes-users] fonts size of Qubes Manager

2021-08-10 Thread Ludovic

On 10/08/2021 01:40, Franz wrote:

Hello,
got a higher resolution screen, but can no longer read the fonts of 
Qubes Manager.

Any idea to enlarge them?


Hello Franz,

With the XFCE font settings, on Qubes-OS 4.1b1 the access path is :

*Q menu* > *System Tools* > *Appearance* > on the opened window, choose 
the *Fonts* tab, then change the *Default Font* size (example: from 10 
to 14).


On Qubes-OS 4.0.4, the access path is near of the above path.

--
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/714f3762-452c-a77d-5d0d-b8d9bfcd9976%40zyrianes.net.


Re: [qubes-users] Re: QSB-069: Multiple Xen and Intel issues

2021-06-09 Thread Ludovic

On 6/9/21 @ 23:07, Ulrich Windl wrote :

On 6/9/21 3:06 AM, Andrew David Wong wrote:

After updating today no kernel was offered; I still have:
# rpm -qa kernel\*
kernel-5.4.88-1.qubes.x86_64
kernel-5.4.98-1.fc25.qubes.x86_64
kernel-qubes-vm-5.4.98-1.fc25.qubes.x86_64
kernel-5.4.107-1.fc25.qubes.x86_64
kernel-qubes-vm-5.4.107-1.fc25.qubes.x86_64
kernel-qubes-vm-5.4.88-1.qubes.x86_64

Somehow I'm missing instructions to get that kernel...



Hi Ulrich,

    please, re-read the QSB, you missed **security-testing repository** :

> These packages will migrate from the security-testing repository to the
> current (stable) repository over the next two weeks after being tested
> by the community. [1] Once available, the packages are to be installed
> via the Qubes Update Tool or its command-line equivalents. [2]

    The QSB provides the links to the documentation which explains how 
to update from security-testing, else wait ~2 weeks.


    The kernel update is only if you use `kernel latest` (i.e. 5.5 
kernel), but you use a 5.4 kernel. The xen and intel-microcode update is 
for everyone.


    Same for your post about XScreenSaver : **security-testing 
repository**.


    I did all theses update on my Qubes-OS host, from now, no detected 
issue.


Regards,

Ludovic


--
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/c50ec468-c6dc-6fe6-9512-7953c6085903%40zyrianes.net.


Re: [qubes-users] USB controllers

2021-06-02 Thread Ludovic Bellier

On 02/06/2021 at 21:20, Franz wrote :



So followed the CLI instructions 
https://www.qubes-os.org/doc/pci-devices/ 

qvm-pci gives the address of the usbcontroller to be detached 
dom0:00_.14.5 and tells the following:

sys-2usb (no-strict-rest=True),  sys-usb (no-strict-reset=true)

Because the linked Qubes instructions apparently only teach how to 
attach, but not how to detach


Hi Franz,

take a look to the `qvm-pci` man page, it explains how to detach.



--
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/6cf9982e-e78e-27e2-ff5b-0eb1da71e569%40zyrianes.net.


Re: [qubes-users] Qubes 4.0 dom0 kernel problems (boot loop, panic, freeze)

2021-04-24 Thread Ludovic Bellier

22/04/2021 T 20:33, Peter Palensky wrote :
Updating the kernel would remove the working one 


Hi Peter,

 Fedora, by default, keeps only the 3 last kernel versions. So before 
updating the kernel, uninstall the most unwanted version. Or change the 
`installonly_limit` (see 
https://qubes-os.discourse.group/t/installing-older-kernels/569)


  About the kernels which didn't work, see the numerous related issues 
about >= 5.4 kernels, some examples:


- https://github.com/QubesOS/qubes-issues/issues/6397

- https://github.com/QubesOS/qubes-issues/issues/6407

- https://github.com/QubesOS/qubes-issues/issues/6458

- https://github.com/QubesOS/qubes-issues/issues/6356


Ludovic

--
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/50e78193-6e19-8796-77c8-4ac492fa54ff%40zyrianes.net.


Re: [qubes-users] each dom0 update check redownload old template

2021-03-07 Thread Ludovic Bellier

Le 07/03/2021 à 11:45, evado...@gmail.com a écrit :


First command "no such domain" as result for first command. I tried 
with qubes- template-fedora-32 and with fedora-32. "no such domain"


sudo qubes-dom0-update still trying to upgrade qubes-template-fedora-32...


I searched for reverse dependency for this package with the help of the 
ArchLinux rosetta (https://wiki.archlinux.org/index.php/Pacman/Rosetta), 
but the `dnf repoquery --alldeps --whatrequires 
qubes-template-fedora-32` command don't give me the wanted result. I'm 
more fluent with debian than fedora... But I think this is the way to 
go, find the reverse dependency for this package.


--

Ludovic

--
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/f97998e9-0945-baca-a970-3c32460b5efb%40zyrianes.net.


Re: [qubes-users] each dom0 update check redownload old template

2021-03-06 Thread Ludovic Bellier

Le 06/03/2021 à 11:29, evado...@gmail.com a écrit :

After I remove old fedora-32 template (sudo dnf remove)
qubes-dom0-update download it again to cache each time or want to 
process it each time.

How to fix?


Hello evadogstar,

    Is your template used by another AppVM?

    The [templates uninstalling 
documentation](https://www.qubes-os.org/doc/templates/#uninstalling) 
suggests also `dnf remove`, but if it failed, suggest a [manual 
uninstall](https://www.qubes-os.org/doc/vm-troubleshooting/#can-not-uninstall-a-vm--error-vm-installed-by-package-manager-template-vm-name).


Ludovic


--
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/ba2ac2bc-3340-f9d8-e9b6-5b517e44e06f%40zyrianes.net.


Re: [qubes-users] clock after resume

2021-02-17 Thread Ludovic Bellier

Le 06/02/2021 à 13:58, D. J. Bernstein a écrit :

A few times now I've suspended and resumed a Qubes laptop and seen a
Fedora VM with the time it had before the suspend, where I expected it
to instead switch to the current time. The non-switch seems perfectly
correlated with a line like

Feb 06 09:48:16 ... qubes.SuspendPostAll-dom0[...]: Invalid date received, 
aborting!

appearing in the VM's log shortly after an expected line like

Feb 06 09:48:15 ... qrexec-agent[...]: executed root:QUBESRPC 
qubes.SuspendPostAll dom0 pid ...

but I haven't dug further into how the dom0-VM date communication is
supposed to work. dom0 and Debian VMs switch to the current time as
expected.


Do you think it's related to the #4835 issue [1] ? Note also the linked 
issues (#3489, #4939).


And, see the recent related discussion [2] on the forum.

[1] https://github.com/QubesOS/qubes-issues/issues/4835

[2] https://qubes-os.discourse.group/t/suspend-dom0-clock-errors/2870

--

Ludovic

--
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/70ee4476-cf63-6890-5564-93cee5c61a44%40zyrianes.net.


Re: [qubes-users] Problems setting /etc/hosts

2021-02-02 Thread Ludovic



Le 02/02/2021 à 12:45, mgla...@gmail.com a écrit :



# several lines of comment

docker --data-root /home/user/docker || true

echo '1.2.3.4 my-domain.example' >> /etc/hosts
echo '1.2.3.4 another-domain.example' >> /etc/hosts

Yes, when I run the script myself with sudo ./rc.local then it works fine.

Argh. I think I've found the issue. It's the command to start docker 
that's causing the rest of the file to be ignored :(



Hi,

  note that '--data-root' is an option of the *dockerd* command, not 
*docker*...


Ludovic

--
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/bb3201f3-1c40-7976-fc34-bad57c814bf3%40zyrianes.net.


Re: [qubes-users] Re: Please help test kernel 5.4 in anticipation of Qubes 4.0.4-rc2

2020-12-06 Thread Ludovic Bellier

Le 29/11/2020 à 01:16, Ludovic Bellier a écrit :

Le 28/11/2020 à 23:40, Marek Marczykowski-Górecki a écrit :

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Try adding `--action=update` option.


Thanks for the help. Note that the action is upgrade (not update).

I switched for dom0 and most of TemplateVMs, AppVMs and DisposableVMs. 
I checked for the follow OSes : debian-10, debian-10-minimal, 
fedora-32 and whonix.


I detected neither issues, all is working well. I'll continue to test 
with my daily usage and report again in 2 days with more tests.


So a week later, I didn't detect issues with this new 5.4 kernel. But 
previously I was already using an 5.8 kernel (kernel-latest).


One user dectected an issue, see the feedback from haaber, another user 
with an already known problem (donoban, issue #6052).


**Other users, please test this new kernel and give more feedbacks!**

Regards

Ludovic

--
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/5a75edae-b2a2-3b5e-bebc-b056e60e3eb1%40zyrianes.net.


Re: [qubes-users] Re: Please help test kernel 5.4 in anticipation of Qubes 4.0.4-rc2

2020-11-28 Thread Ludovic Bellier

Le 28/11/2020 à 23:40, Marek Marczykowski-Górecki a écrit :

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Nov 27, 2020 at 11:41:12PM +0100, Ludovic Bellier wrote:


I tried to install, but I think it doesn't install because I already
installed kernel-latest (I need it for my ethernet card):

[xxx@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
kernel


Try adding `--action=update` option.


Thanks for the help. Note that the action is upgrade (not update).

I switched for dom0 and most of TemplateVMs, AppVMs and DisposableVMs. I 
checked for the follow OSes : debian-10, debian-10-minimal, fedora-32 
and whonix.


I detected neither issues, all is working well. I'll continue to test 
with my daily usage and report again in 2 days with more tests.


For users who want to test, the complete command is:

[xxx@dom0 ~]$ sudo qubes-dom0-update --action=upgrade 
--enablerepo=qubes-dom0-current-testing kernel kernel-qubes-vm


Thanks a lot for this 5.4.78 kernel, it will be a great help for 
supporting more recent hardware by default.


--
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/4c4887f7-231b-9afe-9d73-e7f836c6ebc3%40zyrianes.net.


[qubes-users] Re: Please help test kernel 5.4 in anticipation of Qubes 4.0.4-rc2

2020-11-27 Thread Ludovic Bellier

Le 27/11/2020 à 15:58, Andrew David Wong a écrit :

The package is already available in current-testing. [3]

[3] https://www.qubes-os.org/doc/testing/


Hi,

I tried to install, but I think it doesn't install because I already 
installed kernel-latest (I need it for my ethernet card):


[xxx@dom0 ~]$ sudo qubes-dom0-update 
--enablerepo=qubes-dom0-current-testing kernel
Using sys-firewall as UpdateVM to download updates for Dom0; this may 
take some time...

--> Running transaction check
---> Package kernel.x86_64 1000:5.4.78-1.qubes will be installed
--> Finished Dependency Resolution
/var/lib/qubes/dom0-updates/packages/kernel-5.4.78-1.qubes.x86_64.rpm 
already exists and appears to be complete
Successfully verified 
/var/lib/qubes/dom0-updates/packages/kernel-5.4.78-1.qubes.x86_64.rpm
Successfully verified 
/var/lib/qubes/dom0-updates/packages/kernel-qubes-vm-5.4.78-1.qubes.x86_64.rpm
Qubes OS Repository for Dom0 
73 MB/s |  75 kB 00:00
Package kernel-1000:4.19.147-1.pvops.qubes.x86_64 is already installed, 
skipping.
Package kernel-1000:4.19.152-1.pvops.qubes.x86_64 is already installed, 
skipping.
Package kernel-1000:4.19.155-1.pvops.qubes.x86_64 is already installed, 
skipping.
Package kernel-latest-1000:5.6.16-1.qubes.x86_64 is already installed, 
skipping.
Package kernel-latest-1000:5.8.16-1.qubes.x86_64 is already installed, 
skipping.

Dependencies resolved.
*Nothing to do.*
Complete!

[xxx@dom0 ~]$ ls /boot/vmlinuz-*
/boot/vmlinuz-4.19.147-1.pvops.qubes.x86_64 
/boot/vmlinuz-5.6.16-1.qubes.x86_64
/boot/vmlinuz-4.19.152-1.pvops.qubes.x86_64 
/boot/vmlinuz-5.8.16-1.qubes.x86_64

/boot/vmlinuz-4.19.155-1.pvops.qubes.x86_64

Ludovic

--
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/37d73e44-662a-8aed-2b15-1c8fd58c93b9%40zyrianes.net.


Re: [qubes-users] Re: salt management issues since last qubes (dom0?) upgrade

2020-11-13 Thread Ludovic Bellier



Le 13/11/2020 à 19:33, balin a écrit :

Ok. More detail:

When calling (as root and in dom0):
    qubesctl --target=fedora-32 state.highstate,
I get
    fedora-32: ERROR (exit code 20, details in 
/var/log/qubes/mgmt-fedora-32.log)


The relevant part in the referenced log reads:
    ...
    2020-11-13 19:28:13,125 output: Traceback (most recent 
call last):
    2020-11-13 19:28:13,125 output:   File 
"/usr/lib/qubes-vm-connector/ssh-wrapper/ssh", line 101, in 

    ...


What is going on here? why did this stop working?



Hi Balin,

    it's a known temporary issue, read this:

https://qubes-os.discourse.group/t/updating-vms-throwing-an-ssh-error-any-ideas/1397


--
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/0153f080-6b10-1496-eb95-b688504e7c4f%40zyrianes.net.


Re: [qubes-users] Re: HCL - intel NUC10i7FNK

2020-10-30 Thread Ludovic Bellier

Le 30/10/2020 à 19:52, Alex Smirnoff a écrit :
Now, that's strange! my dom0 is on the latest kernel, but sys-net is 
not, so, no network there.



Its normal, all VMs keep the default kernel, not the latest.

You should change the sys-net VM kernel to latest:

- open Qube Manager

- select sys-net

- right clic, choose Qube-settings

- Advanced tab, change the kernel to 5.x.x

- Apply and restart sys-net

--
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/ee67d160-d044-7e98-3ff1-114fd312150c%40zyrianes.net.


Re: [qubes-users] Re: HCL - intel NUC10i7FNK

2020-10-30 Thread Ludovic Bellier

Le 30/10/2020 à 17:57, Alex Smirnoff a écrit :
Ah, apparently it was just a glitch, second time I tried my keyboard 
remained functional.


Good.

However, still no luck: after I updated dom0 to the latest kernel, my 
Qubes system just got stuck on "Enter disk password" stage. I see some 
corrupted image below


It's same for me, I see the corrupted image on each boot (since 6 months 
now), but (on my host) it's only a display problem, I can give the disk 
password (you should see the bullet [3] for each character) and the boot 
process continues. Note that this step concerns giving the LUKS 
credentials (not the user password!), and the GUI you see is Plymouth 
[1] with this artwork [2].


which slightly changes over time, and that's it. And I cannot switch 
to text console to see what is happening there like I could on a 
regular linux. WIll try booting from a rescue image now. Anyway, Qubes 
on NUC10 is apparently very unstable. I wonder why there is no ISO 
image with the latest kernel already in place.


You can't switch to tty (text console) because the boot process is on 
the LUKS uncryption step, so the rootfs isn't yet available (so the init 
process isn't launch and neither the login process).


Don't worry, Qubes OS on NUC10 is stable, I use it daily.

I agree an ISO image with, on start, the choice between default or 
latest kernel will be great.


[1] https://wiki.archlinux.org/index.php/Plymouth

[2] https://github.com/QubesOS/qubes-artwork/tree/master/plymouth/qubes-dark

[3] 
https://github.com/QubesOS/qubes-artwork/blob/master/plymouth/qubes-dark/bullet.png


--
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/a3f5a5ad-346c-71ed-54b3-f3e30b7fb75f%40zyrianes.net.


Re: [qubes-users] Re: HCL - intel NUC10i7FNK

2020-10-30 Thread Ludovic Bellier

Le 30/10/2020 à 16:37, Alex Smirnoff a écrit :
How did you set up the sys-usb qube without losing the USB keyboard 
and mouse?



Hi Alex,

    I followed the Qubes documentation, first I added the sys-usb Qube 
[1], then I added my USB keyboard available for login [2].



[1] https://www.qubes-os.org/doc/usb-qubes/#creating-and-using-a-usb-qube

dom0/Terminal : sudo qubesctl state.sls qvm.sys-usb

[2] https://www.qubes-os.org/doc/usb-qubes/#enable-a-usb-keyboard-for-login

dom0/Terminal : sudo qubesctl state.sls qvm.usb-keyboard

--
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/c884ea96-196a-26cc-06fa-1386149f6446%40zyrianes.net.


Re: [qubes-users] Orphan menu entries after deleting VM's

2020-10-27 Thread Ludovic Bellier

Le 27/10/2020 à 07:44, Dave a écrit :

Hi guys,

After deleting the work and personal VM's in the qubes VM manager, the 
vm settings shortcuts from both vm's were not deleted from the menu.
So i still have two menu entrys for personal and work in my startmenu, 
with both only the vm settings entry listed.
I have checked ~/.local/share/applications/ 
and /usr/local/share/applications/ for these orphan shortcut but they 
arent there..
Where else can i look for these orphan shortcuts? or how can i get rid 
of these broken shortcuts..?



Hi Dave,

    I think you can find it with the find command (here an example for 
the 'personal VM'):


[adm@dom0 ~]$ find -iname "*personal*"

    ./.config/menus/applications-merged/ and 
./.local/share/qubes-appmenus/personal/apps/ seems to be good 
candidates. Reading the Freedesktop menu spec could help you. Backup the 
files before any (delete) actions.


Ludovic

--
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/07c2e4b5-8d4d-c375-337d-08c23c30f767%40zyrianes.net.


[qubes-users] Re: Problème et panne sur mon ordi sous QubesOs

2020-10-22 Thread Ludovic Bellier



Le 22/10/2020 à 21:16, Frédéric Pierret a écrit :



Le 10/22/20 à 9:00 PM, Yanis Ihaddaden a écrit :

Hello Mr. Pierret,

  I have been a QubesOs user for a few months,

  Recently for almost 20 days now I have had a problem with its use, 
knowing that I only use this bone on my machine, it causes me a problem.


  I am speaking to you because I do not know who to address and where 
I should go.


  I saw that there was Freenode IRC platform to be able to 
communicate with other users, I did not know how to register my 
nickname on it, there is also I think discord, and github there where 
I found your  mail address.


  The problem I encountered with my bone:

  Xen_version: 4.8.5-23.fc25

  Linux 4.19.147-1.pvops.qubes.x86_64

  Qubes os release 4.0 (R4.0)


  Is quite simply that I lost my window bar where there is the cross 
to close and the 3 icons (reduce, enlarge, close) of all the windows, 
I would have believed in a bad handling on my part, or  that the 
resolution of one of my 2 screens was messing up, but I noticed 
another problem the shortcut to switch between windows, (Alt + Tab) 
does not work.


  So I can only use one window and then close it to do something else.

  Here I add an info, sometimes the mouse pointer is not precise, I 
have to click a little further than the button for it to work, 
sometimes and during other startup and ignition it works well.


  I am ready to restore dom0 or the whole system if I have to get 
there, I tried to do it, but I don't have a backup.



  Thank you I hope you do not disturb you with my mail.

Salutation




Hello,
I'll answer in English and not in French because I'm transferring your 
issue to the user mailing list where the community could help you. You 
can find more information about how to have support: 
https://www.qubes-os.org/support/. More recently it's not a "discord" 
but a "discourse" forum https://qubes-os.discourse.group/ where you 
can post your request too.


Looking briefly to your issue, it seems that your dom0 (XFCE?) window 
manager might has its config broken. As a first attempt, I would try 
to clean the XFCE configuration by deleting/moving the folder in your 
dom0 user ~/.conf/xfce4. I would also ensure having latest updates: 
"[XXX@dom0 ~]$ sudo qubes-dom0-update"


Best regards,
Frédéric


Hello Yanis,

You can see the xfce log in ~/.xsession-errors.

As Frédéric said, It looks like your window manager (here xfce) failed 
to launch or never/not launched, so no window decorations, only the 
content of the window. As only one window available, choose a dom0 
terminal, then try to manually launch xfce with the 'startxfce4' command 
(more help on https://wiki.archlinux.org/index.php/Xfce#Starting). If it 
launches, start by doing your backups 
(https://www.qubes-os.org/doc/backup-restore/), then try to understand 
why xfce failed to start automatically.


Note you can also login in a console terminal (text mode, tty), switch 
with Ctrl-Alt-F2 (going back to graphic mode : Ctrl-Alt-F1).


Regards

Ludovic

--
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/73006d23-b32a-a0f7-921d-f4085c07a5c1%40zyrianes.net.


Re: [qubes-users] Where is disk space?

2020-08-19 Thread Ludovic Bellier

Le 19/08/2020 à 09:30, Eva Star a écrit :

Hello,

ncdu /rw  - show that actually used less then 1G of data
df -h show: /dev/xvdb   2.0G  1.8G(used)  171M  92% /rw (show that 
used 1.8G)

qvm-ls --format disk is also show that used 1900 MB and 92% of disk space.

So, where is 1G of free space?

I don't think it's the source of your problem, but remember that /rw 
isn't the only mounting point to /dev/xvdb, so check the space usage of 
these others.


Example:

user@mail:~$ df -h /rw
Filesystem  Size  Used Avail Use% Mounted on
/dev/xvdb   9.8G  3.8G  6.1G  39% /rw
user@mail:~$ mount|grep xvdb
/dev/xvdb on /rw type ext4 (rw,relatime,discard)
/dev/xvdb on /home type ext4 (rw,relatime,discard)
/dev/xvdb on /usr/local type ext4 (rw,relatime,discard)
/dev/xvdb on /var/spool/cron type ext4 (rw,relatime,discard)

user@mail:~$ lsblk /dev/xvdb -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% 
MOUNTPOINT

xvdb ext4 1f6f89a1-be13-4ec9-b151-8115e7a96b14    5.9G 40% /rw

In your case, I think ncdu failed in computing the space usage, me, I 
trust df, du and lsblk.


You should check /rw with 'du --max-depth=1' for finding where the du 
command find a big disk usage:


Example:

user@mail:~$ sudo du --max-depth=1 -h /rw | sort -h
16K    /rw/config
16K    /rw/lost+found
20K    /rw/bind-dirs
80K    /rw/usrlocal
3.9G    /rw
3.9G    /rw/home

In my case, it's /rw/home the guilty, but what in /rw/home? I continue 
recursively and find that it's the Thunderbird IMAP directory:


user@mail:~$ du --max-depth=1 -h 
/rw/home/user/.thunderbird/v3bbe2wh.default-default/ | sort -h

4.0K /rw/home/user/.thunderbird/v3bbe2wh.default-default/extensions
4.0K /rw/home/user/.thunderbird/v3bbe2wh.default-default/minidumps
8.0K /rw/home/user/.thunderbird/v3bbe2wh.default-default/datareporting
12K    /rw/home/user/.thunderbird/v3bbe2wh.default-default/crashes
32K    /rw/home/user/.thunderbird/v3bbe2wh.default-default/Mail
740K /rw/home/user/.thunderbird/v3bbe2wh.default-default/calendar-data
1.5M /rw/home/user/.thunderbird/v3bbe2wh.default-default/storage
3.6G /rw/home/user/.thunderbird/v3bbe2wh.default-default/ImapMail
3.8G    /rw/home/user/.thunderbird/v3bbe2wh.default-default/

I hope 'du --max-depth=1' will help you.

--

Ludovic

--
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/17a1aa2d-34bf-2205-b4e1-9849a18d93d9%40zyrianes.net.


[qubes-users] Re: HCL - intel NUC10i7FNK

2020-07-26 Thread Ludovic Bellier
[Note: sorry for not replying directly to the original thread, but I 
wasn't yet registered to the mailing-list, so I can't do a reply with my 
MUA]


Original copy-paste mail from zhaojx88  (see : 
https://groups.google.com/d/msg/qubes-users/vRKrs5ZIg9c/WUepmWP9BwAJ):


> Thanks for the guidance!
> I also have nuc 10i7fnk. but I have problems installing qubes OS 
4.0.  I hope I can get answers from you.

> I Set legecy mode, security booting off, use USB stick to install OS.
> The following warning maseges is displayed when booting.
> "WARN anaconda: 
/usr/lib64/python3.5/site-packages/pyanaconda/pwpolicy.py:101:PendingDeprecationWarning: 
add_option is deprecated and will be removed in


> pykickstart-3.  Use add_argument instead.
>    op.add.option("--minlen",type="int")
> ..
> WARN anaconda.stdout:Not asking for VNC because we don't have a network
> ..
> WARN anaconda:X startup failed: Xorg exited with status 1
> WARN anaconda.stdout:X startup failed,aborting installation
> ERR anaconda.stdout:X startup failed, aboting installation"
>
> Do I miss setting something in bios or do I need to install the OS 
with DVD?

> Thanks a lot!

zhaojx88,

    you got a *network error*, so may be, you should follow my steps 
with a USB Network Interface Controller (aka USB ethernet), because the 
internal ethernet card isn't recognized by the default 4.9 linux kernel.


    My BIOS setting:

Boot (section)

  Secure Boot    Disabled

  UEFI Boot    Enabled

  Legacy Boot    Enabled

  > Secure Boot (sub-section)

    System Mode    User

    Secure Boot  Disabled

    Not Active (title)

    Secure Boot Mode   Standard

  > Boot Priority

    UEFI Boot   x (i.e. checked)

    Legacy Boot   x (i.e. checked)

    USB            x (i.e. checked)

    I used the 4.0.3 ISO from https://www.qubes-os.org/downloads/  on a 
USB storage stick. On boot I used the F10 key for choosing the *UEFI* 
USB device stick. And I installed Qubes-OS on my SSD with the help of 
the Qubes-OS documentation.


    Note also than my first 4GB USB stick was too small for the iso, 
finally I used a 32GB stick (but 8GB will be fine).


    If this doesn't resolve your problem, give more information (BIOS 
screenshots, when you got the above error message, ...)


--

Ludovic

--
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/4eba41fd-046c-2e2e--948775933c75%40zyrianes.net.


[qubes-users] HCL - intel NUC10i7FNK

2020-07-19 Thread Ludovic Bellier
The intel NUC 10 works great with Qubes-OS 4.0 but need some settings, 
see below.



The default provided kernel didn't recognize the included NIC (I-219V, 
in sys-net no listed network device with `ip a`) and the GPU used the 
restricted 800x600 pixel resolution.



Reason: the too old 4.8.5 kernel doesn't recognize this fresh hardware.


The solution, use the 5.6 kernel:

- first use an USB NIC adapter

- sys-net : remove all devices in Qube setting

- dom0: detect the USB NIC identifier with 'qvm-usb' (ex: sys-usb:3.3)

- dom0: 'qvm-usb attach sys-net sys-usb:3.3' (attach the USB NIC to sys-net)

- sys-net : 'usb-devices' should display the USB NIC

- sys-net: check network works ('ip a', ping, new connection 
notification, red network icon in tray-bar),


- dom0: switch to the latest-kernel with 'qubes-dom0-update 
kernel-latest', got 5.6 kernel,


- qubes-os : shutdown, unplug the USB NIC, restart the host

- check GPU driver provides a better resolution (>= full HD display),

- sys-net: set new kernel for sys-net in Qube setting,

- sys-net: reboot,

- sys-net: remove all devices, and attach only the '00:1f.6 Ethernet 
controller' (i.e.: I-219V device) with the 'no-strict reset' option,


- sys-net: reboot,

- check sys-net uses the I-219V NIC and network works ('ip a', ping, new 
connection notification, red network icon in tray-bar).



I didn't check wireless and sleep because I don't use them for this host.


Regards,

Ludovic

--
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/e7acdc2e-b810-d5dc-e9a8-a7078f18a522%40zyrianes.net.


Qubes-HCL-Intel_R__Client_Systems-NUC10i7FNK-20200720-011247.yml
Description: application/yaml