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

[Error] Distrobox hostname issues freezing the system #994

Closed
scuba3198 opened this issue Sep 26, 2023 · 7 comments
Closed

[Error] Distrobox hostname issues freezing the system #994

scuba3198 opened this issue Sep 26, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@scuba3198
Copy link

scuba3198 commented Sep 26, 2023

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):

  • Are you using podman, docker or lilipod? podman
  • Which version or podman, docker or lilipod? podman version 3.4.4
  • Which version of distrobox? 1.5.0.2
  • Which host distribution? Kubuntu 22.04
  • How did you install distrobox? PPA

Additional context
here is a recording demonstrating the problem:

@scuba3198 scuba3198 added the bug Something isn't working label Sep 26, 2023
@scuba3198 scuba3198 changed the title [Error] [Error] Distrobox hostname issues freezing the system Sep 26, 2023
@Mattheish
Copy link

This issue for toolbox might be related.

@DaniyalAhmadSE
Copy link

I just started using Distrobox and cannot figure what exactly is the solution.

@89luca89
Copy link
Owner

89luca89 commented Feb 3, 2024

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?
Thanks!

@DaniyalAhmadSE
Copy link

@89luca89 What fixed it for me was to add my_containername.my_hostname to the /etc/hosts file of the host. But It's more of a workaround since I would need to do this for each container/distrobox that I create.

@sandorex
Copy link
Contributor

sandorex commented Feb 22, 2024

I experienced this too (also kde plasma), but since d26a926 you can use --hostname argument to set the hostname to your host hostname when creating a container, also referenced in useful tips

@89luca89
Copy link
Owner

89luca89 commented Apr 2, 2024

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

@ghost
Copy link

ghost commented Jul 16, 2024

Please reopen. This is a severe issue that makes it impossible to use distrobox practically. It should be the top issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants