Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38397 - [noise] 0.2.4-2 x86_64 segfaults at startup

Attached to Project: Community Packages
Opened by K. Takacs (silent) - Monday, 06 January 2014, 18:53 GMT
Last edited by Maxime Gauduin (Alucryd) - Wednesday, 08 January 2014, 18:37 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: noise 0.2.4-2 x86_64 segfaults at startup

$ noise
[_LOG_LEVEL_INFO 19:49:27.672713] Application.vala:77: Noise version: 0.2.4
[_LOG_LEVEL_INFO 19:49:27.672832] Application.vala:79: Kernel version: 3.12.6-1-ARCH
Segmentation fault (core dumped)
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Wednesday, 08 January 2014, 18:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.2.4-3
Comment by Maxime Gauduin (Alucryd) - Wednesday, 08 January 2014, 13:53 GMT
No issue here, same version, arch and kernel. Try removing ~/.local/share/noise and ~/.cache/noise, see if that helps. If not, there's not much I can do. I suggest you file a bug report upstream, make sure to provide them with a gdb and strace backtraces. You'll need to rebuild noise and its deps with options=('!strip') in the PKGBUILDs to keep the debug symbols.
Comment by K. Takacs (silent) - Wednesday, 08 January 2014, 17:26 GMT
I have built only 'noise' from ABS. It was OK. Then I reinstalled the binary 'noise' x86_64 package from community. It segfaulted. Reinstalled the build from ABS and it is OK. So if I build 'noise' from source with the ABS script, it is OK.
Comment by Maxime Gauduin (Alucryd) - Wednesday, 08 January 2014, 17:49 GMT
Ok, I can reproduce the segfault on a different machine, go figure. I've pushed 0.2.4-3, can you try it? It doesn't segfault anymore here.
Comment by Balló György (City-busz) - Wednesday, 08 January 2014, 18:17 GMT
I confirm that 0.2.4-3 fixes the problem. 0.2.4-2 segfaulted for me too.
Comment by K. Takacs (silent) - Wednesday, 08 January 2014, 18:19 GMT
Yes it is OK now, thank you.

Loading...