Paul,
You're quite right -- this appears to be fine with the 0.3.2-2ubuntu3
shipped in 9.04. I can only assume it changed during the last couple
of updates.
Chris
--
libaubio.a (amd64) built without -fPIC
https://bugs.launchpad.net/bugs/317864
You received this bug notification because you
This works somewhat better, but not entirely, for me in 9.04 (upgraded
from 8.10).
For example: start a new session, then run up Firefox, Emacs, Inkscape,
Scribus and gnome-terminal, open documents in all of them (where
applicable), replace metacity with my preferred window manager (which is
not
My understanding from the GNOME bugtracker is that a fix exists, but is
not included in 2.26.0 (hopefully in 2.26.1).
This presumably means the fix will not be in 9.04, but is likely to
appear in a subsequent update -- is that right?
I see no mention of it in the known issues section of the
Public bug reported:
Binary package hint: libaubio-dev
Attempting to link a dynamic object statically against libaubio on an amd64
install gives the following error:
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-
gnu/4.3.2/../../../../lib/libaubio.a(phasevoc.o): relocation R_X86_64_32
against `a
Per Sebastien's comment, I have added a couple of sentences about this
to the Intrepid release notes. I trust that's OK.
I think Martin Soto's assessment is spot on. It _is_ worrying that
Ubuntu should (as a matter of policy) be so sanguine about this. It's
also surprising that GNOME
At the risk of asking a really stupid question, does anyone have an idea
whether there's any likelihood of a workaround such as installing and using the
Gnome 2.22 session manager with 2.24? Or using a different session manager
entirely? I don't mind hacking my system to get this to work,
I ended up downgrading gnome-session and gnome-panel to 2.22 as a
workaround. It appears to be working OK so far.
(You can't just downgrade gnome-session, because gnome-panel depends on
the newer version to support essentials such as log out.)
This is what worked for me. Start by adding the
I had this problem exactly as described in the original report, after an
upgrade from 8.04 to 8.10.
I eventually tracked it down to a dangling link from /etc/alternatives/x
-session-manager. It was pointing to a nonexistent KDE4 startkde
script, which presumably used to exist in 8.04. I had
