Sabayon Community

by **Necoro** » Tue Jun 19, 2007 14:50

Rakva: Try to update portage. In newer versions they do not use curses for getting the column count. Thus the error should not happen again.

by **Raqua** » Tue Jun 19, 2007 15:19

I have the latest portage version available in a portage tree.
portage-2.1.3_rc3

My problem started AFTER I emerged this new version through Portato.
Maybe downgrading would be worth trying .. ?

by **Necoro** » Tue Jun 19, 2007 15:53

Rakva wrote:I have the latest portage version available in a portage tree.
portage-2.1.3_rc3

My problem started AFTER I emerged this new version through Portato.
Maybe downgrading would be worth trying .. ?

Ouh yes -- sorry. I updated to portage-2.1.3 after this code and I am now seeing the problem. Seems like Kuroo is not 2.1.3-ready ^^ (I pray that portato is ;P)

by **Raqua** » Tue Jun 19, 2007 16:09

Ok, I will try to downgrade when I get home. And post a bug somewhere for Kuroo team.
Thanks for your help.
Portato works so far with new portage.

It is funny, that I updated to new portage version while testing Portato and thus it looked like it killed Kuroo.
I think I should change this thread title. What do you think ? :wink:

by **Raqua** » Tue Jun 19, 2007 22:02

Yeah, after downgrading Portage back to 2.1.2.9 Kuroo works again.

by **DragoonXX** » Thu Jun 21, 2007 18:08

Hi, this is my first post (i've been visiting the forums for a while though) and i'm willing to admit that i dont know a lot about linux...espically sabayon, so..my question is:
how would one downgrade the portage tree (i also have a non-functional kuroo)
thanks for the help

by **Necoro** » Thu Jun 21, 2007 18:14

You dont want to downgrade the complete tree (this wouldnt be possible) but the single package "sys-apps/portage" ...

Do sth like

Code: Select all: echo "=sys-apps/portage-2.1.3*" >> /etc/portage/package.mask && emerge -uav portage

Nevertheless this should only be a temporary solution, because as soon as portage-2.1.3 is stable, portage-2.1.2 will be removed from the tree - thus leading to non-updateble system

by **Raqua** » Thu Jun 21, 2007 19:32

Just to add ... Kuroo stopped working again the same day and now I am not even able to use it for browsing packages. It crashes on start, giving me this in konsole:

Code: Select all: kbuildsycoca running... QMultiInputContext::changeInputMethod(): index=0, slave=xim QMultiInputContext::changeInputMethod(): index=0, slave=xim KCrash: Application 'kuroo' crashing... kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) QMultiInputContext::changeInputMethod(): index=0, slave=xim

THis started, when I tried to emerge one package. During installation Kuroo crashed and could not be started since ..
I am not 100% sure, but I think the package that Kuroo crashed at was
sys-apps/hal-0.5.9.1
I was able to emerge that package in konsole afterwards.

Don't know if it is related to this portage & Kuroo problem.
I rather changed back to newest portage version since Kuroo crashes anyway ...

by **voxiac** » Thu Jun 21, 2007 21:51

Looks like it's the end of kuroo in sabayon then. We had a thread going about using portato as the default frontend:
http://www.sabayonlinux.org/forum/viewtopic.php?t=7642
Feel free to add your thoughts there.

by **Raqua** » Thu Jun 21, 2007 21:59

As I posted before, I still preffer Kuroo before Portato, but it seems that Kuroo development is quite slow. I checked their web to fill bug report and there was a lot of reports. I don't know how much are they fixed though.

Sabayon Community

Portato killed Kuroo [not Portato bug - solved]

Who is online