Don't compile amarok packages with Stack Smashing Protection
Bug #81768 reported by
Andrew Ash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
amarok (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: amarok
Mark Kretschmann, a core developer of Amarok, suggested that many of the bugs we receive on launchpad for the collectionscanner crashing can be fixed with a recompile:
"""The scanner crashes sometimes on Ubuntu, because the package was compiled with Stack Smashing Protection. This option is apparently known to be a little trigger happy or buggy.
At any rate, the Stack Smashing Protection sometimes aborts the scanner. The solution is to rebuild Amarok without SSP (which is enabled by default in Ubuntu's GCC)."""
http://
I suggest that this change be made in hopes of reducing the number of bugs we receive for this problem.
Changed in amarok: | |
importance: | Undecided → Medium |
status: | Unconfirmed → Confirmed |
To post a comment you must log in.
11:09 < Riddell> ash211: I need to go to bed now, but give it a shot if you
want, apt-get source amarok, edit debian/rules with adding
CXXFLAGS := -fno-stack- protector and see if that works,
debuild to build
(for reference)