Version-Release number of selected component: exaile-4.1.1-3.fc34 Additional info: reporter: libreport-2.15.2 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-exaile-63119.scope cmdline: exaile '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' crash_function: on_location_changed exception_type: gi.repository.GLib.GError executable: /usr/share/exaile/exaile.py interpreter: exaile-4.1.1-3.fc34.noarch kernel: 5.13.4-200.fc34.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: collection.py:470:on_location_changed:gi.repository.GLib.GError: g-io-error-quark: Fehler beim Holen der Informationen für Datei »/home/yala/Musik/Ardour/Power Hour/Power Hour.tmp«: Datei oder Verzeichnis nicht gefunden (1) Traceback (most recent call last): File "/usr/share/exaile/xl/collection.py", line 470, in on_location_changed fileinfo = gfile.query_info( gi.repository.GLib.GError: g-io-error-quark: Fehler beim Holen der Informationen für Datei »/home/yala/Musik/Ardour/Power Hour/Power Hour.tmp«: Datei oder Verzeichnis nicht gefunden (1) Local variables in innermost frame: self: <collection.LibraryMonitor object at 0x7f30a19a12c0 (xl+collection+LibraryMonitor at 0x555a4d046840)> monitor: <__gi__.GInotifyFileMonitor object at 0x7f309863e0c0 (GInotifyFileMonitor at 0x7f306002bd00)> other_gfile: None event: <enum G_FILE_MONITOR_EVENT_CREATED of type Gio.FileMonitorEvent> gfile: <__gi__.GLocalFile object at 0x7f309869ddc0 (GLocalFile at 0x555a4d0aa660)>
Created attachment 1811324 [details] File: backtrace
Created attachment 1811325 [details] File: cpuinfo
Created attachment 1811326 [details] File: environ
Created attachment 1811327 [details] File: mountinfo
Created attachment 1811328 [details] File: namespaces
Created attachment 1811329 [details] File: open_fds
Do you have any more information on how to reproduce this? I've not managed to hit this bug on my machine but I have now seen a couple of ABRT reports now about it. Some indication about what you were doing at the time would be very useful.
Hi Graham, thank you for having a look at this. It happened when trying to access a '.tmp' file that had already been deleted by another process. This happened when working with Exaile 4.1.1 in a directory with music files, which were parallely edited in Ardour 6.8.0. Eventually I have switched the directory (... location changed ... from the error message) and tried listing its files. Apparently Ardour would create '.tmp' files next to its project files, and delete them when not needed anymore. This may have happened after Exaile picked up the file through its INotify monitor, but after it was already deleted. Please let me know if I should take an extended effort to reproduce the problem. Kindest, Jon
Jon, OK, that's great. Thanks for the extra information. What you've said supports what my thinking was having taken a brief look at the code. I'm not an Exaile developer, just the new packager for Fedora, so I'm not entirely sure how to fix this issue myself. Needless to say, this is an upstream issue. I will go ahead and raise a bug with Exaile upstream (on GitHub) and link back to that in this report soon. If you're available to participate in the upstream bug report on GitHub then I think that would be extremely helpful to the developers. Regards, Graham
I've raised the bug upstream at https://github.com/exaile/exaile/issues/764 Let's continue the conversation over there. Many thanks for reporting and hope to have your continued involvement so we can get a good fix!
FEDORA-2021-d7fcef98b8 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d7fcef98b8
FEDORA-2021-cf81a5c8ba has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-cf81a5c8ba
FEDORA-2021-d7fcef98b8 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d7fcef98b8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d7fcef98b8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-cf81a5c8ba has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-cf81a5c8ba` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-cf81a5c8ba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-d7fcef98b8 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-cf81a5c8ba has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.