Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upXfce4 panel first run: Disable prompt and use default config #2531
Comments
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
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Dec 22, 2016
Contributor
Setting the XFCE_PANEL_MIGRATE_DEFAULT env var appears it would resolve this.
|
Setting the |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
|
Or rather, invoking Not sure the most appropriate place to do that from though. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Dec 22, 2016
Contributor
Somewhere in https://github.com/QubesOS/qubes-installer-qubes-os/tree/master/qubes-anaconda-addon presumably?
|
Somewhere in https://github.com/QubesOS/qubes-installer-qubes-os/tree/master/qubes-anaconda-addon presumably? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Dec 22, 2016
Member
|
I think I've seen a patch in some distribution that disable this prompt
entirely. By including default configuration already in place. I don't
remember which distribution it was, nor where exactly the config was
(/etc/xdg/xfconf? /etc/skel?)... So, I'm not really helpful here.
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Dec 22, 2016
Member
|
Ok, found some, but a different one than before:
http://git.pld-linux.org/?p=packages/xfce4-panel.git;a=shortlog
(still wondering at what other distributions source code I've looked
recently...)
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
andrewdavidwong
added
C: desktop-linux-xfce4
enhancement
UX
labels
Dec 22, 2016
andrewdavidwong
added this to the Release 4.0 milestone
Dec 22, 2016
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
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
|
[Off-topic]
Wait, so this is possible now? I thought nested Xen was disabled. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
|
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@jpouellet: Ok, thanks! |
andrewdavidwong
referenced this issue
Mar 30, 2017
Closed
Consider adopting containers for Qubes #2683
dzklaim
referenced this issue
May 19, 2017
Closed
notifications do not respect xfce panel position #2820
marmarek
closed this
in
marmarek/qubes-desktop-linux-xfce4@ae0ddcb
Sep 15, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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
qubesos-bot
commented
Sep 15, 2017
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Sep 15, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Sep 15, 2017
Closed
desktop-linux-xfce4 v4.0.1-xfce4-settings-qubes (r4.0) #211
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
qubesos-bot
commented
Oct 17, 2017
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
jpouellet commentedDec 22, 2016
•
edited
Edited 1 time
-
jpouellet
edited Dec 22, 2016 (most recent)
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:

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:

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?