1 |
On Mon, May 13, 2013 at 10:34:09AM -0600, Stan Sander wrote: |
2 |
> On 05/13/2013 03:03 AM, Hinnerk van Bruinehsen wrote: |
3 |
> > Hi, |
4 |
> > |
5 |
> > I'd bet on libffi as the culprit. You may try to use the version from |
6 |
> > the hardened overlay (there was one that should patch the issue a while |
7 |
> > ago). I was able to fix gnome on the only box I'm running gnome on right |
8 |
> > now (the issue was more or less the same). |
9 |
> > |
10 |
> > Note: I use 3.0.12-r1 (which is an old version because an update to the |
11 |
> > stable version broke it again and I haven't had time to upgrade and |
12 |
> > retry). |
13 |
> > |
14 |
> > WKR |
15 |
> > Hinnerk |
16 |
> |
17 |
> Well, you got it!!! I had seen other posts talking about rebuilding |
18 |
> libffi, which I had tried. However I did not try changing versions of |
19 |
> the library. I now have a working gnome-shell. So now I can start |
20 |
> poking around and learning how the gnome desktop works and tweaking |
21 |
> settings to my liking. I did have to downgrade libffi to 3.0.11 in |
22 |
> order to get things to work. Do you know if there is a bug open on the |
23 |
> libffi->gnome-shell interaction? If not, I'll open one as this is |
24 |
> something that needs to be looked at and fixed. If there is one, I'll |
25 |
> add myself to the CC. |
26 |
|
27 |
I'm not aware of any open bugs regarding this issue. As I said above: I |
28 |
didn't upgrade due to time constraints (mostly because it's a remote |
29 |
system). If you open a new bug for the issue (if there isn't an open one |
30 |
at b.g.o.) it would be nice if you could add me to CC (or reply with the |
31 |
bug id so I can add myself). |