Created attachment 422100 [details]
Description of problem: Ebook Viewer sefaults
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. open Terminal
2. type: ebook-viewer or /usr/bin/ebook-viewer
Actual results: Seg fault
Expected results: Window
Additional info: segfaults on 2: above, also exits as attachedf valgrind.
will run if "valgrind /usr/bin/ebook-viewer"
Created attachment 422105 [details]
Can you provide:
strace -o /tmp/trace -f /usr/bin/ebook-viewer
(the /tmp/trace file)
Created attachment 422258 [details]
Does the problem persist on a newly created users desktop?
(In reply to comment #4)
> Does the problem persist on a newly created users desktop?
created new "test" user
[test@torrent ~]$ /usr/bin/ebook-viewer
Oddly, I can't get this to fail here... but only have Xfce installed, and KDE has some broken deps preventing me from installing it to test. ;(
Can you try another DE and see if the problem persists there?
(In reply to comment #6)
> Oddly, I can't get this to fail here... but only have Xfce installed, and KDE
> has some broken deps preventing me from installing it to test. ;(
> Can you try another DE and see if the problem persists there?
I'll throw Gnome onto an external HD, and update to Rawhide.
I'll need a day or two if that's ok.
Perfectly fine. ;) Add info as you get it...
Created attachment 422891 [details]
Gnome-Calibre steps to install
Created attachment 422892 [details]
Python AVC denials
Is this still happening in the current rawhide builds?
So so, we probibly need to get upstream to fix this before we push to any stable releases. Needing execmem is bad. ;(
(In reply to comment #11)
> Is this still happening in the current rawhide builds?
Still there. on 32bit,
there a bug preventing me installing 64bit with virt-manager.
Adding dwalsh here.
How can I figure out whats causing this execmem request so I can fix it?
It's just reporting python, as calibre is written in python. Something in this new version is making it try for execmem though. ;(
It most likely is a shared library that your python code is using.
Yeah, the trick is: how do I figure out which lib this is?
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
Frank: Do you still see this in final F14?
I am not seeing it here.
(In reply to comment #17)
> Frank: Do you still see this in final F14?
> I am not seeing it here.
The "stable final" or the calibre repo?
Well, either one really I guess. ;)
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: