home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.17k stars 29.85k forks source link

Error during setup of component conversation: ModuleNotFoundError: No module named 'mutagen' #115703

Open jmartens opened 5 months ago

jmartens commented 5 months ago

The problem

When firing up a dev container and while running though onboarding and initial setup I received the following error:

2024-04-16 12:27:48.006 INFO (SyncWorker_0) [homeassistant.util.package] Attempting install of mutagen==1.47.0
2024-04-16 12:27:48.085 INFO (MainThread) [homeassistant.setup] Setting up conversation
2024-04-16 12:27:48.145 ERROR (MainThread) [homeassistant.setup] Error during setup of component conversation
Traceback (most recent call last):
  File "/workspaces/home-assistant-core/homeassistant/setup.py", line 404, in _async_setup_component
    result = await task
             ^^^^^^^^^^
  File "/workspaces/home-assistant-core/homeassistant/components/conversation/__init__.py", line 193, in async_setup
    from homeassistant.components.assist_pipeline import (  # pylint: disable=import-outside-toplevel
  File "/workspaces/home-assistant-core/homeassistant/components/assist_pipeline/__init__.py", line 21, in <module>
    from .pipeline import (
  File "/workspaces/home-assistant-core/homeassistant/components/assist_pipeline/pipeline.py", line 24, in <module>
    from homeassistant.components import (
  File "/workspaces/home-assistant-core/homeassistant/components/tts/__init__.py", line 22, in <module>
    import mutagen
ModuleNotFoundError: No module named 'mutagen'
2024-04-16 12:27:48.146 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.06 seconds

What version of Home Assistant Core has the issue?

System Information

version core-2024.5.0.dev0
installation_type Unsupported Third Party Container
dev true
hassio false
docker true
user vscode
virtualenv false
python_version 3.12.2
os_name Linux
os_version 5.15.146.1-microsoft-standard-WSL2
arch x86_64
timezone Europe/Amsterdam
config_dir /workspaces/home-assistant-core/config
Dashboards dashboards | 2 -- | -- resources | 0 views | 0 mode | storage
Recorder oldest_recorder_run | April 16, 2024 at 12:23 PM -- | -- current_recorder_run | April 16, 2024 at 2:23 PM estimated_db_size | 0.14 MiB database_engine | sqlite database_version | 3.40.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

conversation

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

jmartens commented 5 months ago

When manually entering the shell of the running dev container it seems mutagen is not installed properly:

# pip list | grep mutagen
# 

Manual installation seems to work OK:

# pip install mutagen==1.47.0           
Collecting mutagen==1.47.0
  Downloading mutagen-1.47.0-py3-none-any.whl.metadata (1.7 kB)
Downloading mutagen-1.47.0-py3-none-any.whl (194 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 194.4/194.4 kB 3.9 MB/s eta 0:00:00
Installing collected packages: mutagen
Successfully installed mutagen-1.47.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
# pip list | grep mutagen
mutagen                                 1.47.0
# 
Robbe-B commented 5 months ago

I had the same issue.

brmonaghan commented 3 months ago

Same here, having the same error https://photos.app.goo.gl/7DeDmALVpTr98Sv96

issue-triage-workflows[bot] commented 4 weeks ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

brmonaghan commented 4 weeks ago

Not stale. Please reopen.