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

Missing texts and icons after sleep mode #2700

Closed
mikeSaidHi opened this Issue Mar 13, 2017 · 7 comments

Comments

Projects
None yet
5 participants
@mikeSaidHi

mikeSaidHi commented Mar 13, 2017

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

R3.2

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

dom0 (xfce)

Actual behavior:

screenshot_2017-03-13_11-47-39

Steps to reproduce the behavior:

Put it to sleep mode (by closing the laptop) then turn it on..

General notes:

I'm using Dell Precision M4700.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Mar 13, 2017

Contributor

Woah. Can you reliably reproduce this?

Contributor

jpouellet commented Mar 13, 2017

Woah. Can you reliably reproduce this?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 13, 2017

Member

I've seen very similar thing on non-Qubes machine: XUbuntu 14.04 (or 16.04? don't remember), also on Xfce. When it happened, nothing helped (reboot, removing .cache etc). Installing updates fixed it there. It may be something totally different here, as we didn't changed anything recently, and also fc23 do not receive updates anymore.

Member

marmarek commented Mar 13, 2017

I've seen very similar thing on non-Qubes machine: XUbuntu 14.04 (or 16.04? don't remember), also on Xfce. When it happened, nothing helped (reboot, removing .cache etc). Installing updates fixed it there. It may be something totally different here, as we didn't changed anything recently, and also fc23 do not receive updates anymore.

@mikeSaidHi

This comment has been minimized.

Show comment
Hide comment
@mikeSaidHi

mikeSaidHi Mar 13, 2017

@jpouellet @marmarek I updated dom0, and things back to normal. Thanks.

Is it xfce's issue? Btw I'm also experiencing network-manager issue with WPA2-Enterprise (my university to be specific)..

@jpouellet @marmarek I updated dom0, and things back to normal. Thanks.

Is it xfce's issue? Btw I'm also experiencing network-manager issue with WPA2-Enterprise (my university to be specific)..

@osh2ep

This comment has been minimized.

Show comment
Hide comment
@osh2ep

osh2ep Mar 13, 2017

@mikeSaidHi Same here, nm-applet can't connect to WPA2 enterprise network :iknowhowyoufeelbro:

Below are fields I used but:

Security : WPA & WPA2 Enterprise
Authentication : Protected EAP (PEAP)
CA certificate is not needed
PEAP version : Automatic
Inner authentication : MSCHAPv2
Username and Password are correct.

Or to be specific

[ipv6]
method=auto

[connection]
id=SSID #(e.g.EDUroam)
uuid=9e123fbc-0123-46e3-97b5-f3214e123456 #unique uuid will be created upon creation of this profile
type=802-11-wireless

[802-11-wireless-security]
key-mgmt=wpa-eap
auth-alg=open

[802-11-wireless]
ssid=SSID
mode=infrastructure
mac-address=0A:12:3C:DA:C1:A5
security=802-11-wireless-security

[802-1x]
eap=peap; # this semi-colon might be the reason why it didn't work, but it was there by default
identity=studentid123123
phase2-auth=mschapv2
password=mypass123123

[ipv4]
method=auto

References:

http://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c

https://bugs.launchpad.net/linuxmint/+bug/1418777

Both didn't work for me... But when I changed to GNOME, it just worked.

osh2ep commented Mar 13, 2017

@mikeSaidHi Same here, nm-applet can't connect to WPA2 enterprise network :iknowhowyoufeelbro:

Below are fields I used but:

Security : WPA & WPA2 Enterprise
Authentication : Protected EAP (PEAP)
CA certificate is not needed
PEAP version : Automatic
Inner authentication : MSCHAPv2
Username and Password are correct.

Or to be specific

[ipv6]
method=auto

[connection]
id=SSID #(e.g.EDUroam)
uuid=9e123fbc-0123-46e3-97b5-f3214e123456 #unique uuid will be created upon creation of this profile
type=802-11-wireless

[802-11-wireless-security]
key-mgmt=wpa-eap
auth-alg=open

[802-11-wireless]
ssid=SSID
mode=infrastructure
mac-address=0A:12:3C:DA:C1:A5
security=802-11-wireless-security

[802-1x]
eap=peap; # this semi-colon might be the reason why it didn't work, but it was there by default
identity=studentid123123
phase2-auth=mschapv2
password=mypass123123

[ipv4]
method=auto

References:

http://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c

https://bugs.launchpad.net/linuxmint/+bug/1418777

Both didn't work for me... But when I changed to GNOME, it just worked.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Mar 13, 2017

Contributor

NetworkManager questions belong on qubes-users, not this issue. That said, "CA certificate is not needed" is a terrible option and should not be set, as it allows any rogue AP to steal your university network access credentials and impersonate you (potentially leading to personal liability).

You should really go through the trouble of fetching & verifying the cert chain for your institution.

Contributor

jpouellet commented Mar 13, 2017

NetworkManager questions belong on qubes-users, not this issue. That said, "CA certificate is not needed" is a terrible option and should not be set, as it allows any rogue AP to steal your university network access credentials and impersonate you (potentially leading to personal liability).

You should really go through the trouble of fetching & verifying the cert chain for your institution.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Mar 13, 2017

Contributor

Also mschapv2 is weak (read: broken) and you should prefer nearly other authentication mechanism if your institution supports any.

Contributor

jpouellet commented Mar 13, 2017

Also mschapv2 is weak (read: broken) and you should prefer nearly other authentication mechanism if your institution supports any.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 14, 2017

Member

I updated dom0, and things back to normal. Thanks.

Glad to hear it. 😃

Member

andrewdavidwong commented Mar 14, 2017

I updated dom0, and things back to normal. Thanks.

Glad to hear it. 😃

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