Don't compile amarok packages with Stack Smashing Protection

Bug #81768 reported by Andrew Ash
2
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
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://bugs.kde.org/show_bug.cgi?id=137824#c7

I suggest that this change be made in hopes of reducing the number of bugs we receive for this problem.

Andrew Ash (ash211)
Changed in amarok:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

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)

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

will do for amarok 1.4.5

Changed in amarok:
assignee: nobody → hobbsee
status: Confirmed → In Progress
importance: Medium → High
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

fixed in 1.4.5 packages

Changed in amarok:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers