Kuroo 4...

Message

botdotcom · Post by **botdotcom** » Fri Mar 09, 2012 3:45 am

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...

http://sourceforge.net/apps/mediawiki/k ... =Main_Page

tomk · Post by **tomk** » Fri Mar 09, 2012 11:34 am

Moved from Portage & Programming to Unsupported Software as it's not in the Portage tree.

botdotcom · Post by **botdotcom** » Fri Mar 09, 2012 5:27 pm

what does 'the thing green' mean? on ksnapshot or others...
http://ompldr.org/vY3pmNw

botdotcom · Post by **botdotcom** » Fri Mar 09, 2012 7:43 pm

botdotcom wrote:what does 'the thing green' mean?

↑

dol-sen · Post by **dol-sen** » Sun Mar 11, 2012 4:17 am

That round green circle in there means it is in the world file.

botdotcom · Post by **botdotcom** » Sun Mar 11, 2012 10:03 pm

Thx cuh!

but

dol-sen wrote:means it is in the world file

what does it mean?

galiven · Post by **galiven** » Sun Mar 11, 2012 10:12 pm

botdotcom wrote: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...

http://sourceforge.net/apps/mediawiki/k ... =Main_Page

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.

kernelOfTruth · Post by **kernelOfTruth** » Mon Mar 12, 2012 9:56 am

botdotcom wrote:Thx cuh!

but

dol-sen wrote:means it is in the world file
what does it mean?

that means that you need to familiarize yourself more with Gentoo's internals

/var/lib/portage/world

botdotcom · Post by **botdotcom** » Thu May 24, 2012 5:15 pm

there is a tutorial, manual, step by step of kuroo?

galiven · Post by **galiven** » Thu May 24, 2012 5:35 pm

botdotcom wrote:there is a tutorial, manual, step by step?

Gentoo's documentation resources are very good, you should spend some time browsing around www.gentoo.org/docs/en. For you specific question about portage you can start with http://www.gentoo.org/doc/en/handbook/h ... xml?part=2 and http://www.gentoo.org/doc/en/handbook/h ... xml?part=3.

john-doe · Post by **john-doe** » Sat May 26, 2012 11:06 pm

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?

galiven · Post by **galiven** » Tue May 29, 2012 5:38 pm

john-doe wrote: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.

MetalGod · Post by **MetalGod** » Thu May 31, 2012 7:09 pm

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

galiven · Post by **galiven** » Thu May 31, 2012 7:26 pm

MetalGod wrote: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.

MetalGod · Post by **MetalGod** » Fri Jun 01, 2012 8:46 am

galiven wrote:
MetalGod wrote: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.

john-doe · Post by **john-doe** » Fri Jun 01, 2012 5:08 pm

I repeat:

kuroo is more o equal in stability than porthole --> period --> next! so hard to understand?

john-doe · Post by **john-doe** » Fri Jun 22, 2012 4:00 pm

galiven wrote:
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?

galiven · Post by **galiven** » Thu Jun 28, 2012 11:54 pm

john-doe wrote:
galiven wrote:
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

galiven · Post by **galiven** » Fri Aug 03, 2012 8:35 pm

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.

Fitzcarraldo · Post by **Fitzcarraldo** » Fri Aug 03, 2012 10:02 pm

^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.

Spent · Post by **Spent** » Wed Nov 14, 2012 12:16 am

I can't get Kuroo4-0.90.2 to start.

When I try to start I get this error

Code: Select all

Application: Kuroo (kuroo), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f38e9f5488e in QStatusBar::showMessage(QString const&, int) () from /usr/lib64/qt4/libQtGui.so.4
#7  0x00000000004c8087 in _start ()

galiven · Post by **galiven** » Wed Nov 14, 2012 12:41 am

Spent wrote:I can't get Kuroo4-0.90.2 to start.

When I try to start I get this error

Code: Select all

Application: Kuroo (kuroo), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f38e9f5488e in QStatusBar::showMessage(QString const&, int) () from /usr/lib64/qt4/libQtGui.so.4
#7  0x00000000004c8087 in _start ()

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.

Spent · Post by **Spent** » Wed Nov 14, 2012 1:07 am

galiven wrote:
Spent wrote:I can't get Kuroo4-0.90.2 to start.

When I try to start I get this error
Code: Select all
Application: Kuroo (kuroo), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f38e9f5488e in QStatusBar::showMessage(QString const&, int) () from /usr/lib64/qt4/libQtGui.so.4
#7  0x00000000004c8087 in _start ()
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: Select all

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.

galiven · Post by **galiven** » Wed Nov 14, 2012 1:17 am

Spent wrote:
galiven wrote:
Spent wrote:I can't get Kuroo4-0.90.2 to start.

When I try to start I get this error
Code: Select all
Application: Kuroo (kuroo), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f38e9f5488e in QStatusBar::showMessage(QString const&, int) () from /usr/lib64/qt4/libQtGui.so.4
#7  0x00000000004c8087 in _start ()
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: Select all
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: Select all

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.

Spent · Post by **Spent** » Thu Nov 15, 2012 12:21 am

Here is the output from the command you suggested.

Code: Select all

Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)" 
kdesu(4167)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/process.cpp : 293 ]  Running "/bin/su"
kdesu(4167)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(4167)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/process.cpp : 293 ]  Running "/bin/su"
kdesu(4167)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(4167)/kdesu (kdelibs) KDESu::PtyProcess::WaitSlave: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/process.cpp : 379 ]  Child pid 4174
kdesu(4167)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/su.cpp : 259 ]  Read line ""
kdesu(4167)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/su.cpp : 259 ]  Read line "kdesu_stub"
kdesu(4167)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/process.cpp : 293 ]  Running "/bin/su"
kdesu(4167)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(4167)/kdesu (kdelibs) KDESu::PtyProcess::WaitSlave: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/process.cpp : 379 ]  Child pid 4179
kdesu(4167)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/su.cpp : 259 ]  Read line ""
kdesu(4167)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdesu/su.cpp : 259 ]  Read line "kdesu_stub"
Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)" 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kuroo(4185)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
KCrash: Application 'kuroo' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-desktop/kdeinit4__0

Kuroo 4...

Kuroo 4...

Re: Kuroo 4...

Documentation

bugs

KDE vs. Qt

Re: KDE vs. Qt

Re: bugs

Re: bugs

kuroo4-0.90.2