Summary: | media-sound/audacious segfault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maxim Britov <maxbritov> |
Component: | Current packages | Assignee: | Tony Vroon (RETIRED) <chainsaw> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
bt full
emerge --info again, another bt full si_ui.c.2.diff Yet another backtrace. Another backtrace Another backtrace My current emerge --info |
Description
Maxim Britov
2007-05-15 12:28:26 UTC
Created attachment 119355 [details]
bt full
Created attachment 119356 [details]
emerge --info
Which audacious version is this about? $ equery l audacious [ Searching for package 'audacious' in all categories among: ] * installed packages [I--] [ ~] media-plugins/audacious-plugins-1.3.4 (0) [I--] [ ] media-sound/audacious-1.3.2 (0) Created attachment 119967 [details]
again, another bt full
Created attachment 119978 [details, diff]
si_ui.c.2.diff
Please apply the following patch (provided by Giacomo, the status-icon author) to the 1.3.4 plugin sources. Does this resolve the problem?
I'm still not expirience in gentoo ebuilds. Where i may read about custom ebuilds? sorry Maxim, it would probably be best to create a portage overlay, if you do not already have one. Chapter 5b in the handbook has more information: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=5 You would then create a directory with a new audacious-plugins ebuild, for example: mkdir -p /usr/local/portage/media-plugins/audacious-plugins/files/ You can then copy the contents of /usr/portage/media-plugins/audacious-plugins here and create a 1.3.4-r1 ebuild for testing. Do you follow the idea up to here? If you do, I'll attach a 1.3.4-r1 ebuild for you that applies this patch so you can test. heh... it seems me vs portage 1:0 today:) I built it, it seems patch applied. Waiting... But I not often getting this segv. Created attachment 120497 [details]
Yet another backtrace.
Is that with or without the patch applied? With patch applied You're hitting a crash in libmad right now, not audacious itself. Please try remerging libmad with the CFLAGS you've shown here. Created attachment 121108 [details]
Another backtrace
Yes, it still patched build.
Hopefully this will be fixed in 1.3.5; please let me know as this would be grounds for an early stable of 1.3.5 (and skipping 1.3.4 altogether). Created attachment 121734 [details]
Another backtrace
[I--] [ ~] media-plugins/audacious-plugins-1.3.5 (0)
[I--] [ ] media-sound/audacious-1.3.2 (0)
Created attachment 121736 [details]
My current emerge --info
Seems as if the specific patch attached here was missed on 1.3.5; it should still apply. Other fixes have been made in 1.3.5 that may help. Please test. This requires testing which apparently hasn't been done yet. Please test and reopen, I can't proceed. I'm use audacious with this patch and it works for me. |