Package Details: exaile 4.2.0-1

Git Clone URL: https://aur.archlinux.org/exaile.git (read-only, click to copy)
Package Base: exaile
Description: A full-featured Amarok-style media player for GTK+
Upstream URL: https://exaile.org
Licenses: GPL-2.0-only
Submitter: xyproto
Maintainer: UnicornDarkness
Last Packager: UnicornDarkness
Votes: 147
Popularity: 0.81
First Submitted: 2011-12-14 17:02 (UTC)
Last Updated: 2025-10-20 15:30 (UTC)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

UnicornDarkness commented on 2025-11-07 18:19 (UTC)

It seems related to DB migration, but I cannot help. Please report the bug upstream: https://github.com/exaile/exaile/issues/new

senorsnor commented on 2025-10-31 11:13 (UTC)

In addition to my comment below: I could build the package by adding --nocheck to makepkg. But now get the same error starting exaile, even after removing .config/exaile and .cache/exaile directories. 


Fatal Python error: Segmentation fault

Current thread 0x00007f89fa5d7bc0 (most recent call first):
  File "/usr/lib/python3.13/site-packages/bsddb3/__init__.py", line 329 in hashopen
  File "/usr/lib/exaile/xl/migrations/database/to_sqlite.py", line 67 in migrate
  File "/usr/lib/exaile/xl/common.py", line 405 in open_shelf
  File "/usr/lib/exaile/xl/trax/trackdb.py", line 185 in load_from_location
  File "/usr/lib/exaile/xl/common.py", line 174 in wrapper
  File "/usr/lib/exaile/xl/trax/trackdb.py", line 114 in __init__
  File "/usr/lib/exaile/xl/collection.py", line 143 in __init__
  File "/usr/lib/exaile/xl/main.py", line 677 in __init
  File "/usr/lib/exaile/xl/main.py", line 569 in __init__
  File "/usr/lib/exaile/exaile.py", line 60 in main
  File "/usr/lib/exaile/exaile.py", line 64 in <module>

Extension modules: setproctitle._setproctitle, gi._gi, cairo._cairo, gi._gi_cairo, _dbus_bindings, _dbus_glib_bindings, gi.overrides._gi_gst, bsddb3._pybsddb (total: 8)
Segmentation fault         (core dumped) exaile

Couldn't find a bug like this in their bug tracker. Could this be a packaging thing or at exaile itself?

senorsnor commented on 2025-10-29 16:48 (UTC)

i get the exact same segfault as cubethethird with makepkg -si

UnicornDarkness commented on 2025-10-29 16:23 (UTC)

@cubethethird: I did not face any issue during build with makepkg -si. You can skip tests with makepkg by using --nocheck. I cannot provide support for pikaur.

cubethethird commented on 2025-10-28 01:38 (UTC)

I'm getting a segfault when attempting to build this now:

tests/xl/trax/test_migration.py Fatal Python error: Segmentation fault

Current thread 0x00007f29c3e2cbc0 (most recent call first):
  File "/usr/lib/python3.13/site-packages/bsddb3/__init__.py", line 329 in hashopen
  File ".cache/pikaur/build/exaile/src/exaile-4.2.0/tests/xl/trax/test_migration.py", line 45 in test_migration_to_sqlite
  File "/usr/lib/python3.13/site-packages/_pytest/python.py", line 157 in pytest_pyfunc_call
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 121 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 512 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/python.py", line 1671 in runtest
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 178 in pytest_runtest_call
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 121 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 512 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 246 in <lambda>
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 344 in from_call
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 245 in call_and_report
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 136 in runtestprotocol
  File "/usr/lib/python3.13/site-packages/_pytest/runner.py", line 117 in pytest_runtest_protocol
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 121 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 512 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 367 in pytest_runtestloop
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 121 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 512 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 343 in _main
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 289 in wrap_session
  File "/usr/lib/python3.13/site-packages/_pytest/main.py", line 336 in pytest_cmdline_main
  File "/usr/lib/python3.13/site-packages/pluggy/_callers.py", line 121 in _multicall
  File "/usr/lib/python3.13/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/usr/lib/python3.13/site-packages/pluggy/_hooks.py", line 512 in __call__
  File "/usr/lib/python3.13/site-packages/_pytest/config/__init__.py", line 175 in main
  File "/usr/lib/python3.13/site-packages/_pytest/config/__init__.py", line 201 in console_main
  File "/usr/bin/py.test", line 8 in <module>

Any idea if this is a build/packaging issue or upstream?

UnicornDarkness commented on 2025-03-24 20:08 (UTC)

@Mikhail: https://github.com/exaile/exaile/issues/962

UnicornDarkness commented on 2025-03-24 18:24 (UTC)

@oldherl: I see a /usr/share/gir-1.0/GIRepository-2.0.gir file in libgirepository 1.84.0-1 and I do not have this issue on my computer. Ok I am removing python-deadlib.

Mikhail commented on 2025-03-24 18:23 (UTC)

If someone have github account, create an issue, who dont want to wait, change in /usr/lib/exaile/xl/main.py line gi.require_version('GIRepository', '2.0') on gi.require_version('GIRepository', '3.0') and Exaile will start again.

oldherl commented on 2025-03-24 06:51 (UTC)

It is still failing. It's because libgirepository in Arch is now providing GIRepository 3.0, not 2.0

And you probably should not list python-deadlib as a dependency.

UnicornDarkness commented on 2025-03-23 11:14 (UTC) (edited on 2025-03-23 11:14 (UTC) by UnicornDarkness)

@Mikhail: Ok, I see the GIRepository-2.0.typelib file is provided by libgirepository. I ran namcap I and updated dependencies.

1 2 3 4 5 6 .. 8 Next › Last »