3.5.13 on Xubuntu Oneiric. All other menus work, but as soon as I go to Settings or System, kicker crashes. Also crashes when I use the menu search, but I suspect it's because it hits one of those two menus.
Anyone else having this problem?
On 28 November 2011 19:26, Dan Youngquist dan@homestead-products.comwrote:
3.5.13 on Xubuntu Oneiric. All other menus work, but as soon as I go to Settings or System, kicker crashes. Also crashes when I use the menu search, but I suspect it's because it hits one of those two menus.
Anyone else having this problem?
Hello Dan,
Could this be related? http://bugs.trinitydesktop.org/show_bug.cgi?id=554
Looks like someone has dug up a patch already and submitted it, so if everything goes well this can be incorporated to R14.
Calvin Morrison
On 11/28/2011 06:48 PM, Calvin Morrison wrote:
Could this be related? http://bugs.trinitydesktop.org/show_bug.cgi?id=554
Looks like someone has dug up a patch already and submitted it, so if everything goes well this can be incorporated to R14.
Yep, that's it. So.. When is 14 coming out? Or will it show up eventually as an update for 13?
This is my first install of 3.5.13. The bug report says it was there in 3.5.12, but it never showed up for me in several installs on several different distros. I have a few machines that need to be upgraded; what are the chances it'll show up on them? Or would I be better off staying with 3.5.12 on Maverick for the moment?
On 29 November 2011 13:53, Dan Youngquist dan@homestead-products.comwrote:
On 11/28/2011 06:48 PM, Calvin Morrison wrote:
Could this be related?
http://bugs.trinitydesktop.org/show_bug.cgi?id=554
Looks like someone has dug up a patch already and submitted it, so if everything goes well this can be incorporated to R14.
Yep, that's it. So.. When is 14 coming out? Or will it show up eventually as an update for 13?
We are planning for a 6 month release cycle. So that puts us tentatively around May. No promises :P
This is my first install of 3.5.13. The bug report says it was there in 3.5.12, but it never showed up for me in several installs on several different distros. I have a few machines that need to be upgraded; what are the chances it'll show up on them? Or would I be better off staying with 3.5.12 on Maverick for the moment?
I haven't run into it at all, so it's probably rather hit and miss. Why not try 3.5.13 and if it does not work then uninstall it and revert to 3.5.12.
Le 29/11/2011 19:53, Dan Youngquist a écrit :
This is my first install of 3.5.13. The bug report says it was there in 3.5.12, but it never showed up for me in several installs on several different distros. I have a few machines that need to be upgraded; what are the chances it'll show up on them? Or would I be better off staying with 3.5.12 on Maverick for the moment?
It's a little bug easily solved without waiting. First, go to http://bugs.trinitydesktop.org/show_bug.cgi?id=554 and download the patch (libart-remove-asserts.patch). Then, open konsole, paste this and press 'Enter':
# download ubuntu's source package: apt-get source libart-2.0-2 # patch the sources: cd libart-lgpl-2.3.21 patch -Np1 -i ../libart-remove-asserts.patch # build the package: cd .. apt-get -b source # install it: sudo dpkg -i libart-2.0-2_2.3.21-1_amd64.deb
That,s all.
Le 29/11/2011 19:53, Dan Youngquist a écrit :
This is my first install of 3.5.13. The bug report says it was there in 3.5.12, but it never showed up for me in several installs on several different distros.
In fact, AFAIK, the bug isn't in Trinity. It's a bug in libart-lgpl, which is provided by libart-2.0-2 in Ubuntu.
On 29 November 2011 14:48, Laurent Dard f.couperin@online.fr wrote:
Le 29/11/2011 19:53, Dan Youngquist a écrit :
This is my first install of 3.5.13. The bug report says it was there in 3.5.12, but it never showed up for me in several installs on several different distros.
In fact, AFAIK, the bug isn't in Trinity. It's a bug in libart-lgpl, which is provided by libart-2.0-2 in Ubuntu.
-- Laurent Dard
which, as far as I can tell, is totally dead.
Does someone have more information about this? From what I can tell it's a 2D (vector?) graphics library from the GNOME project.
If it's not getting updated, we can't send that patch upstream.
Calvin Morrison
Le 29/11/2011 20:54, Calvin Morrison a écrit :
On 29 November 2011 14:48, Laurent Dard f.couperin@online.fr wrote:
In fact, AFAIK, the bug isn't in Trinity. It's a bug in libart-lgpl, which is provided by libart-2.0-2 in Ubuntu.
which, as far as I can tell, is totally dead.
Does someone have more information about this? From what I can tell it's a 2D (vector?) graphics library from the GNOME project.
If it's not getting updated, we can't send that patch upstream.
Follow the links in the bug report, there isn't much more information.
I submitted the bug in Debian, one month ago. It can be patched there too, for Debian and Ubuntu users. I directly wrote to the original developer, Raph Levien, 5 days ago, to be absolutely sure he doesn't want to update libart. No answer for the moment.
Anyway, Timothy said it will be included in Trinity. The bug is solved.
-
Calvin Morrison -
Dan Youngquist -
Laurent Dard