-
Notifications
You must be signed in to change notification settings - Fork 427
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
[Error] Distrobox hostname issues freezing the system #994
Comments
This issue for toolbox might be related. |
I just started using Distrobox and cannot figure what exactly is the solution. |
Thanks @Mattheish for the report This seems to be unique to KDE, as (from my tests) stuff like i3/sway, XFCE and GNOME do not suffer from this Are you able to provide some logs from the KDE session so that I can try to find a solution? |
@89luca89 What fixed it for me was to add |
I experienced this too (also kde plasma), but since d26a926 you can use |
For this I've now reopened the discussion #62 The idea is to default to host's username for the container, and use $CONTAINER_ID for default prompt Let's discuss in that issue for the impact of this change on workflows and/or breakages that this could lead |
Please reopen. This is a severe issue that makes it impossible to use distrobox practically. It should be the top issue. |
Describe the bug
For some reasons graphical applications seems to freeze the system in general in distrobox containers but afterwards it recovers. The issue seems to be caused by the hostname. When the hostname is set for example as “teufort” graphical apps freeze after awhile or when interacting with the menus. When the hostname is the LAN address (192.168.1.10) it doesn’t freeze at all.
To Reproduce
Use KDE Plasma. I use Kubuntu LTS.
Expected behavior
App should be smooth. When I set my hostname to local LAN, the containerized app runs smooth with zero hiccups.
Desktop (please complete the following information):
Additional context
here is a recording demonstrating the problem:
The text was updated successfully, but these errors were encountered: