Kuroo has been rewritten to be much simpler and easier to maintain. This source tree starts at svnroot/kuroo/kuroo4 (ignore trunk subdirectory), though I'm not exactly sure how to get it compiling and running. Package and history browsing is now supported...

That round green circle in there means it is in the world file._________________Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

Kuroo has been rewritten to be much simpler and easier to maintain. This source tree starts at svnroot/kuroo/kuroo4 (ignore trunk subdirectory), though I'm not exactly sure how to get it compiling and running. Package and history browsing is now supported...

I've moved the kuroo rewrite to its own directory under svn (svnroot/kuroo_rewrite/trunk) so that it won't be confusing to people looking for the (mostly working) port. I've also updated the wiki page to reflect this change. I'd still recommend using the port since it actually allows emerging and I'm still spending a little time on it.

I'm testing Kuroo and I can say it is so stable! why some people try to discredit this great software saying that could be buggy or so?

As the developer, I'm happy to hear you say that, but I have to be honest that it still needs a lot of work. I just recently fixed (I think) the last major crash bug, but there's still a lot of things that aren't nice. There's a list of bugs it the tracker and some in the trac instance. These are just the ones that I've copied from the old kuroo page or I've gotten around to logging myself, there's still lots of things that bother me but I haven't gotten around to writing up.

I'm planning on making a 0.90.1 ~ release soon since I've been testing the crash fix for a while and it seems to be ok, and if tampakrap and dol-sen help out that might even make it into portage.

Kuroo now uses Qt4 instead of Kdelibs ? I hope so because i would like to run it on GNOME._________________ex: Gentoo Linux Developer: amd64 media-optical sound gnome
ex: Portuguese Moderator
------------------------------------------------------------------------------
God Doesn't Play Dice

Kuroo now uses Qt4 instead of Kdelibs ? I hope so because i would like to run it on GNOME.

Kuroo still uses Kdelibs, there's a long-term goal to make it Qt-only, but I don't have a lot of time to spend on it. You can still use it on Gnome of course, it just means you have to have Kdelibs too.

Kuroo now uses Qt4 instead of Kdelibs ? I hope so because i would like to run it on GNOME.

Kuroo still uses Kdelibs, there's a long-term goal to make it Qt-only, but I don't have a lot of time to spend on it. You can still use it on Gnome of course, it just means you have to have Kdelibs too.

Fair enough afaik the only drawback of using only Qt it would be the Terminal Widget which you have to use the one from KDE._________________ex: Gentoo Linux Developer: amd64 media-optical sound gnome
ex: Portuguese Moderator
------------------------------------------------------------------------------
God Doesn't Play Dice

I'm planning on making a 0.90.1 ~ release soon since I've been testing the crash fix for a while and it seems to be ok, and if tampakrap and dol-sen help out that might even make it into portage

that 'soon' could be years,months,days...what do U think?

It's tough to say. I've just been informed that the cache that kuroo is currently using is going away from the rsync servers, so it turns out now would be a bad time to make a release. I have code to read the new cache, but while putting that in I've regressed on the queue order bug. Now I have that to fix along with a bit more testing of the new-cache code before I'm comfortable making a release.

That said, it does work, just not as nicely as I'd like to make a release, and I'd really appreciate feedback on the current live version which you can install by adding the overlay (layman -a gentoo-guis) and then unmasking the live ebuild (echo 'app-portage/kuroo4 ** >> /etc/portage/package.unmask) and emerging it (emerge -atv kuroo4). These instructions are also on the kuroo4 sourceforge page along with a bug tracker to file any issues you find (and feel free to attach patches) at http://kuroo.sourceforge.net

Thanks to tampakarp and johu, kuroo4-0.90.2 is now in the main portage tree. I've updated the installation instructions on the kuroo wiki. This contains the md5-cache fix and finally fixes the queue item ordering.

^That's good news. I liked Kuroo's UI when I used it in KDE 3, so I'm going to install it and try it after a gap of several years. Thanks._________________Clevo W230SS: amd64, OpenRC, NVIDIA, KDE / Compal NBLB2: ~amd64, OpenRC, FGLRX, KDE, dual booting with Windows 7 Professional 64-bit
Fitzcarraldo's blog

Without better debug info its difficult to guess what's going on. If you start in the console how far does it get before the crash? Also, if you build with debug symbols it could give me a line number in Kuroo code where the problem is and I might be able to figure out if there's a bad localization string or something.

Without better debug info its difficult to guess what's going on. If you start in the console how far does it get before the crash? Also, if you build with debug symbols it could give me a line number in Kuroo code where the problem is and I might be able to figure out if there's a bad localization string or something.

When run in the console this is as far as it goes:

Code:

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kuroo(2510): KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

kuroo(2509): KUniqueApplication: Pipe closed unexpectedly.

Seems to be complaining about my system. I have dbus started, but it can't connect.

You might have to walk me through anything else you might need. I just recently reinstalled Gentoo after being away from it, and linux in general for almost 3 years. I'm still trying to remember how to do everything.

Without better debug info its difficult to guess what's going on. If you start in the console how far does it get before the crash? Also, if you build with debug symbols it could give me a line number in Kuroo code where the problem is and I might be able to figure out if there's a bad localization string or something.

When run in the console this is as far as it goes:

Code:

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kuroo(2510): KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

kuroo(2509): KUniqueApplication: Pipe closed unexpectedly.

Seems to be complaining about my system. I have dbus started, but it can't connect.

You might have to walk me through anything else you might need. I just recently reinstalled Gentoo after being away from it, and linux in general for almost 3 years. I'm still trying to remember how to do everything.

You're trying to launch Kuroo from a su console directly. Because Kuroo is an X application you have to launch it with kdesu, or kdesudo, or something similar. Kuroo actually depends on kdesu and installs a .desktop file so that there's a menu item in your K menu that invokes kdesu correctly. If that menu item doesn't work, run

Code:

kdesu -t -- kuroo --nofork 2>&1 | tee output

in the console as your regular user. That'll launch kuroo properly and pipe all the output to the console and also to a file in the local directory named 'output'. That way you'll get the actual debug output. One of my long-term goals is to integrate ConsoleKit into Kuroo so it'll just ask for permission when it needs it instead of having to be launched with kdesu.