394337 – media-sound/audacious-3.1 prints "lseek failed: Invalid argument." on start

Bug 394337 - media-sound/audacious-3.1 prints "lseek failed: Invalid argument." on start

Summary: media-sound/audacious-3.1 prints "lseek failed: Invalid argument." on start

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	Normal normal (vote)
Assignee:	Tony Vroon (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-12-11 14:03 UTC by colinxp
Modified:	2011-12-12 10:51 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description colinxp 2011-12-11 14:03:15 UTC

After updating my system, audacious 2.5.4 was updated to audacious 3.1. Audacious worked fine on my system. But the version 3.1 not. It shows "lseek failed: Invalid argument." The menu bar was not displayed correctly. No "Help" Menu Item.

Reproducible: Always

Comment 1 Jeff (JD) Horelick (RETIRED) gentoo-dev

2011-12-11 17:44:05 UTC

The problem is that one of the files in your playlist does not exist in any mounted filesystems and now that metadata scanning is done on start (and many other times), that's what's failing. Sadly, there is no way to figure out what file is failing without modifying the source.

Comment 2 Tony Vroon (RETIRED) gentoo-dev

2011-12-12 10:51:19 UTC

There are two scenarios that could lead here:
1) Having a 3.1 core with 2.5.4 plugins
2) Attempting to resume playback with a non-existent file

The resolution advice for both scenarios is the same:
Don't do that.