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

Teamviewer 13 - qubes-gui[640]: XGetWindowAttributes #3678

Closed
BenoitGEORGELIN opened this Issue Mar 8, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@BenoitGEORGELIN

BenoitGEORGELIN commented Mar 8, 2018

Qubes OS version: Qubes release 3.2 (R3.2)

Hi,
I think i'm facing an issue, maybe that will sounds familiar to you. I'm installing teamviewer 13 and I cannot get any GUI

cat /etc/qubes-release
Qubes release 3.2 (R3.2)

Affected component(s):

GUI


Steps to reproduce the behavior:

Install teamviewver 13 from main website (.deb) on debian

Expected behavior:

GUI should appear

Actual behavior:

No GUI
Here is the error :

Mar  8 14:49:54 localhost qubes-gui[640]: XGetWindowAttributes for 0x2200006 failed in handle_create, ret=0x0

General notes:

Thanks :)


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2018

Member

This looks like teamviewer crashes shortly after displaying its first window (and qubes-gui didn't managed to get its window properties in time). Do you see any output if you start it from terminal?

Member

marmarek commented Mar 8, 2018

This looks like teamviewer crashes shortly after displaying its first window (and qubes-gui didn't managed to get its window properties in time). Do you see any output if you start it from terminal?

@BenoitGEORGELIN

This comment has been minimized.

Show comment
Hide comment
@BenoitGEORGELIN

BenoitGEORGELIN Mar 8, 2018

Unfortunately, there is no information displayed in the terminal.
I will try to have more log or debug info if that can help. Or maybe trace it?
Thanks

Unfortunately, there is no information displayed in the terminal.
I will try to have more log or debug info if that can help. Or maybe trace it?
Thanks

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 9, 2018

Member

Duplicate of #3664

Member

andrewdavidwong commented Mar 9, 2018

Duplicate of #3664

@andrewdavidwong andrewdavidwong marked this as a duplicate of #3664 Mar 9, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 9, 2018

Member

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Member

andrewdavidwong commented Mar 9, 2018

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

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