New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xfce4 panel first run: Disable prompt and use default config #2531

Closed
jpouellet opened this Issue Dec 22, 2016 · 11 comments

Comments

Projects
None yet
4 participants
@jpouellet
Contributor

jpouellet commented Dec 22, 2016

Qubes OS version (e.g., R3.2):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

Dom0


Actual behavior:

Upon first logging into a clean install of R3.2, the very first thing users see is this prompt:
panel-ask

They can not reasonably be expected to have any idea what it means, and if they happen to select "One empty panel" instead of the default, they get a very unusable system:
broken-panel

It can be fixed by removing ~/.config/xfce4/xfconf and logging in again and choosing the other option, but there is no way new users could be expected to know this.

Expected behavior:

The first thing that happens right after installing Qubes should not be that they are greeted with a prompt they do not understand, that if they answer incorrectly will lead them to probably either reinstall or give up.

Steps to reproduce the behavior:

1st login in clean install of r3.2. My screenshots above were produced on qubes-in-qubes (in an outer HVM).

General notes:

IIRC if you are instead upgrading from 3.1, you get an equally useless 3-option dialog with one of the options being "migrate old config" or something.


Related issues:

Have not seen any reports of this. Maybe everybody either got lucky and answered right or got so immediately discouraged at Qubes apparent complete brokenness that they didn't bother reporting?

@jpouellet jpouellet changed the title from Fatal initial setup UX flaw (on 1st xfce4-panel run, without config) to Fatal initial setup UX flaw (on 1st xfce4-panel run) Dec 22, 2016

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Dec 22, 2016

Contributor

Setting the XFCE_PANEL_MIGRATE_DEFAULT env var appears it would resolve this.

Contributor

jpouellet commented Dec 22, 2016

Setting the XFCE_PANEL_MIGRATE_DEFAULT env var appears it would resolve this.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Dec 22, 2016

Contributor

Or rather, invoking /usr/lib64/xfce4/panel/migrate with XFCE_PANEL_MIGRATE_DEFAULT set would.

Not sure the most appropriate place to do that from though.

Contributor

jpouellet commented Dec 22, 2016

Or rather, invoking /usr/lib64/xfce4/panel/migrate with XFCE_PANEL_MIGRATE_DEFAULT set would.

Not sure the most appropriate place to do that from though.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 22, 2016

Member
Member

marmarek commented Dec 22, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 22, 2016

Member
Member

marmarek commented Dec 22, 2016

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Dec 22, 2016

@andrewdavidwong andrewdavidwong changed the title from Fatal initial setup UX flaw (on 1st xfce4-panel run) to Xfce4 panel first run: Disable prompt and use default config Dec 22, 2016

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Dec 22, 2016

Member

[Off-topic]

My screenshots above were produced on qubes-in-qubes (in an outer HVM).

Wait, so this is possible now? I thought nested Xen was disabled.

Member

andrewdavidwong commented Dec 22, 2016

[Off-topic]

My screenshots above were produced on qubes-in-qubes (in an outer HVM).

Wait, so this is possible now? I thought nested Xen was disabled.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Dec 22, 2016

Contributor

Wait, so this is possible now? I thought nested Xen was disabled.

It has been possible for a very long time. I believe perhaps you are confusing nested HVM with nested virtualization in general, the former being only a (perhaps commonly desired) subset of the latter.

I am running PV-only inside HVM. This means no double-shadowed page tables, and also no nested EPT.

This is with the qubes-shipped Xen and Qemu. No changes required. In particular, no upstream Qemu in dom0 required.

Contributor

jpouellet commented Dec 22, 2016

Wait, so this is possible now? I thought nested Xen was disabled.

It has been possible for a very long time. I believe perhaps you are confusing nested HVM with nested virtualization in general, the former being only a (perhaps commonly desired) subset of the latter.

I am running PV-only inside HVM. This means no double-shadowed page tables, and also no nested EPT.

This is with the qubes-shipped Xen and Qemu. No changes required. In particular, no upstream Qemu in dom0 required.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Dec 22, 2016

Contributor

I should also mention there are problems with PCI passthrough in nested qubes, so while it is useful for testing things, it is not very useful in general. In particular networking is problematic.

Contributor

jpouellet commented Dec 22, 2016

I should also mention there are problems with PCI passthrough in nested qubes, so while it is useful for testing things, it is not very useful in general. In particular networking is problematic.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
Member

andrewdavidwong commented Dec 22, 2016

@jpouellet: Ok, thanks!

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Sep 15, 2017

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Oct 17, 2017

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

marmarek added a commit to QubesOS/qubes-desktop-linux-xfce4 that referenced this issue Jan 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment