Skip to content
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

Qubesd fails to start, freshinstall R4.0, string to float, localization #3960

Closed
Bockwurst-Mit-Puls opened this issue Jun 5, 2018 · 5 comments
Labels
R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.

Comments

@Bockwurst-Mit-Puls
Copy link

Bockwurst-Mit-Puls commented Jun 5, 2018

Qubes OS version:

R4.0 freshinstall

Affected component(s):

Qubes Management Tools
Qubesd


Steps to reproduce the behavior:

Install R4.0
bios amd
locale: en_DK
storage:
Luks(lvm[thinpool{root},lv{swap}]), external(boot)
Try to complete firstrun

Expected behavior:

Vms created, management possible

Actual behavior:

Qubes Management Tools fail to start with error in app.py: qubesd socket is not existing

qubesd fails to start because of python string to float '4,94' in the qubes lvm pool module

Python only accepts . as float separator

en_DK locale uses comma as float separator.

Something parses localized values.

See screenshot with systemd log for qubesd:
https://s15.postimg.cc/4jjfrn24r/IMG_20180605_142600.jpg

General notes:


Related issues:

@marmarek
Copy link
Member

marmarek commented Jun 5, 2018

Looks like a duplicate of (already fixed in updates) #3753
Let me guess, en_DK locale? You can install with different locale, update, then change back to en_DK.

@marmarek marmarek closed this as completed Jun 5, 2018
@Bockwurst-Mit-Puls
Copy link
Author

Bockwurst-Mit-Puls commented Jun 5, 2018

Yeah, I just made some mess here because of the fickle mobile site. At first the issue was empty.

Argh, github on mobile never again.

@andrewdavidwong
Copy link
Member

@marmarek

Looks like a duplicate of (already fixed in updates) #3960

Typo? #3960 is this issue.

@marmarek
Copy link
Member

marmarek commented Jun 6, 2018

The correct issue is #3753

@andrewdavidwong
Copy link
Member

Duplicate of #3753

@andrewdavidwong andrewdavidwong marked this as a duplicate of #3753 Jun 7, 2018
@andrewdavidwong andrewdavidwong added the R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. label Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.
Projects
None yet
Development

No branches or pull requests

3 participants