Bug 663127 - Amarok requires execmem privileges
Summary: Amarok requires execmem privileges
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 604003
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-14 19:28 UTC by Piotrek Juźwiak
Modified: 2010-12-15 15:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-15 14:39:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Dump from crash handler (7.17 KB, text/plain)
2010-12-14 21:23 UTC, Piotrek Juźwiak
no flags Details
Cat from audit.log after crashing amarok (488 bytes, text/x-log)
2010-12-14 21:24 UTC, Piotrek Juźwiak
no flags Details

Description Piotrek Juźwiak 2010-12-14 19:28:24 UTC
Description of problem:If the allow_execmem boolean is turned off amarok (and kadu that will be filed separately) will crash due to denied execmem


Version-Release number of selected component (if applicable):


How reproducible: Run amarok with allow_execmem boolean turned off


Steps to Reproduce:
1.Turn off allow_execmem boolean
2.Run amarok
3.
  
Actual results:
Amarok crashes 

Expected results:
Amarok should run just fine perhaps with a custom policy to allow amarok to execmem

Additional info:

Comment 1 Piotrek Juźwiak 2010-12-14 19:30:51 UTC
I will post a log from audit.log later after filing bug with kadu

Comment 2 Daniel Walsh 2010-12-14 19:56:04 UTC
Why do kadu and amorok need execmem?  Are they written in Java?  Mono?

Comment 3 Piotrek Juźwiak 2010-12-14 20:29:03 UTC
No Mono or Java, just C++ (Qt). I guess developers of these apps should know best, i'll file bugs at their respective bug systems.

Comment 4 Daniel Walsh 2010-12-14 20:35:57 UTC
I reassigned these bugs to them.  We need to have these justified.

Comment 5 Rex Dieter 2010-12-14 20:40:25 UTC
Are you using phonon-backend-vlc ?  If so, that's it. (there's an open bug @ rpmfusion already)

Else, what's causing this is a mystery.

Comment 6 Piotrek Juźwiak 2010-12-14 20:44:58 UTC
As a matter of fact i am not, i am using xine based phonon backend.

Comment 7 Piotrek Juźwiak 2010-12-14 21:23:37 UTC
Created attachment 468705 [details]
Dump from crash handler

I can't really download debug seymbols right now as i am on a mobile internet plan with crappy speeds and crappy MB cap.

Comment 8 Piotrek Juźwiak 2010-12-14 21:24:45 UTC
Created attachment 468706 [details]
Cat from audit.log after crashing amarok

Comment 9 Piotrek Juźwiak 2010-12-14 22:57:20 UTC
I was talking with kadu developers and they gave a hint that qtwebkit might be the one needing execmem. Rekonq which aparently uses qtwebkit also crashes with execmem denied. Probably connected with this:

https://bugzilla.redhat.com/show_bug.cgi?id=604003

Comment 10 Rex Dieter 2010-12-15 14:06:34 UTC
I see no crashes on my boxes, wonder why I've never been able to reproduce this?

Comment 11 Kevin Kofler 2010-12-15 14:12:19 UTC
Because you have allow_execmem set to true (which is the default). We already discussed that in the other bug.

IMHO, as long as allow_execmem defaults to true, we can just close this as NOTABUG.

Comment 12 Rex Dieter 2010-12-15 14:30:36 UTC
Ah, I completely missed:
> Steps to Reproduce:
> 1.Turn off allow_execmem boolean

Comment 13 Rex Dieter 2010-12-15 14:39:37 UTC
Ok, NOTABUG it is.

Dan, for posterity, do you have any preferences/comments about fedora continuing to ship any core items that will continue to require execmem (ie, like this example with qtwebkit)?

Comment 14 Daniel Walsh 2010-12-15 15:30:01 UTC
Is there any way to allow administrator to choose whether or not he wants this functionality turned on?

Comment 15 Kevin Kofler 2010-12-15 15:35:58 UTC
No, this is a compile-time-only decision. :-(

Comment 16 Kevin Kofler 2010-12-15 15:36:43 UTC
(And if we disable the JIT, people complain that we disable the JIT, if we keep it enabled, people complain that it requires execmem. And nobody at WebKit or Qt upstream cares about that issue.)


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