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

i3 cannot start any programs with graphical user interface #3223

Closed
loeken opened this Issue Oct 27, 2017 · 5 comments

Comments

Projects
None yet
4 participants
@loeken

loeken commented Oct 27, 2017

Qubes OS version:

R4.0

Affected TemplateVMs:

all


Steps to reproduce the behavior:

launching an application in i3 using dmenu launcher ( ctrl+d )

Expected behavior:

Window of the application i am starting should show up

Actual behavior:

Nothing happens

General notes:

Installed Qubes R4, imported my old vms through the qvm-backup-restore, installed i3 i3-settings, after a reboot I was unable to launch any applications by using the shortcut ctrl+d --> no windows show up


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 28, 2017

Member

Try starting qvm-start-gui --all --watch. If that helps, it means i3 there does not handle /etc/xdg/autostart correctly.

Member

marmarek commented Oct 28, 2017

Try starting qvm-start-gui --all --watch. If that helps, it means i3 there does not handle /etc/xdg/autostart correctly.

@loeken

This comment has been minimized.

Show comment
Hide comment
@loeken

loeken Oct 29, 2017

when i execute this command all i see is

sys-firewall: Starting GUI
sys-net: Starting GUI
sys-firewall: Sending monitor layout
sys-net: Sending monitor layout

then just silence ( waited ~ 10 minutes ). Any suggestions on how i can fix this?

loeken commented Oct 29, 2017

when i execute this command all i see is

sys-firewall: Starting GUI
sys-net: Starting GUI
sys-firewall: Sending monitor layout
sys-net: Sending monitor layout

then just silence ( waited ~ 10 minutes ). Any suggestions on how i can fix this?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 29, 2017

Member

That's ok. It should keep running and monitor further VM startups. You can launch it in background adding &.
When it's running, try to launch some application.

Member

marmarek commented Oct 29, 2017

That's ok. It should keep running and monitor further VM startups. You can launch it in background adding &.
When it's running, try to launch some application.

@loeken

This comment has been minimized.

Show comment
Hide comment
@loeken

loeken Oct 30, 2017

I dont know what i changed, spent a day on xfce and now i3 magically works :/

loeken commented Oct 30, 2017

I dont know what i changed, spent a day on xfce and now i3 magically works :/

@loeken loeken closed this Oct 30, 2017

@Deedasmi

This comment has been minimized.

Show comment
Hide comment
@Deedasmi

Deedasmi Mar 30, 2018

@marmarek's solution works. You can add it directly to the bottom of your i3 config.

exec --no-startup-id qvm-start-gui --all --watch

@marmarek's solution works. You can add it directly to the bottom of your i3 config.

exec --no-startup-id qvm-start-gui --all --watch

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