[00:04] <nixternal> are we putting docs in /usr/lib/kde4 as well? I thought I seen with kdelibs or something some of them going into /usr/share
[00:04] <Riddell> should be /usr/lib/kde4
[00:05] <nixternal> roger
[00:12] <nixternal> Riddell: want debdiffs or do you want me to go ahead and upload?
[00:15] <Riddell> nixternal: just go ahead and upload
[00:15] <Riddell> well
[00:15] <Riddell> they should get stuck in New, I can let them through when toma releases them
[00:15] <nixternal> roger
[00:15] <nixternal> actually, plasma won't get stuck in new
[00:16] <Riddell> nixternal: wait with that then
[00:16] <nixternal> ya
[00:16] <nixternal> I will post a debdiff for you
[00:16] <Riddell> I have a new version waiting on the kdebase-* to compile anyway
[00:16] <nixternal> roger
[00:16] <nixternal> we have to wait a week?
[00:17] <Riddell> release on 11th, we can let them through a day or two before I guess to get it into backports
[00:18] <nixternal> groovy
[00:18] <nixternal> and when that happens, my laptop gets its first wipe in almost 2 years
[00:20] <Riddell> seele: going to SCALE?
[00:20] <fdoving> nite.
[00:20] <nixternal> hopefully I am, but I think she is, she has blogged it a few times :)
[00:20] <nixternal> k'nite fdoving
[00:25] <nixternal> what is stopping Oo.o from updating? it is in a constant "remove" state
[00:37] <nosrednaekim> wow.... huge review here http://www.mandrake.tips.4.free.fr/ubuntubeyondthehype.html
[00:37] <nosrednaekim> just a bit about kubuntu
[00:38] <stdin> Riddell: should kdelibs5-dev Conflicts: kdelibs4-dev ?
[00:38] <Riddell> stdin: no, does it?
[00:39] <stdin> yeah
[00:39] <stdin> I remember the last sync from debian did that too
[00:41] <Riddell> stdin: well spotted, up goes ubuntu5
[00:41] <stdin> well other than that the new package update from RC2 (base install) just fine :)
[00:43] <Riddell> great
[00:46] <Riddell> stdin: I've the rest to upload too but I think I'll wait until a buildd admin can give back kdebase-* so it actually gets compiled
[00:47]  * Riddell sleeps
[00:47] <stdin> ok, good night
[00:47] <nixternal> ahhh, that explains why I just almost removed kdelibs-kde3 stuff :)
[00:48] <nixternal> gonna grab a bite to eat, back in a bit
[02:00] <ubuntu> wow.... hardy looks nice :) (this is nosrednaekim BTW)
[02:01] <nixternal> no0by name
[02:01] <nixternal> ;P
[02:01] <ubuntu> I know <_< .... I think i'm going to install this...
[02:03]  * ScottK waits for his hard drive to catch fire.
[02:03] <nixternal> lol
[02:04] <ubuntu> you know what? they got rid of glxinfo off the liveCD.
[02:10] <ubuntu> hmmm is it known that dolphin in hard displays two context menus on the right hand side?
[02:12] <ubuntu> *in hardy
[05:24] <nixternal> http://media.libsyn.com/media/dsyates/lottalinuxlinks_59.mp3
[05:24] <nixternal> if you want a good laugh, there is my interview podcast from today
[05:26] <Baudelaire> later..
[09:43] <mornfall> Morgen.
[09:45] <mornfall> yuriy: poke.
[11:22] <Lure> Riddell: do you understand why kdebase-workspace was published, but not kdebase-kde4, while both have built successfully?
[11:22] <Lure> kdebase-kde4 is still 3.97 in archive
[11:22] <Lure> build was successful: http://launchpadlibrarian.net/11161818/buildlog_ubuntu-hardy-i386.kdebase-kde4_4%3A3.98.0%7Esvn755919-1ubuntu1_FULLYBUILT.txt.gz
[11:24] <Lure> kdebase-runtime is also fine, just kdebase-kde4 is strange
[11:24]  * Hobbsee will hedge a guess at a launchpad bug.
[11:24] <Hobbsee> Lure: hardy?  ppa?  what?
[11:24] <Lure> Hobbsee: hardy
[11:25] <Hobbsee> Lure: new queue/
[11:26] <Hobbsee> #  libkonq5-templates_3.98.0~svn755919-1ubuntu1_all.deb (38.4 KiB) NEW
[11:27] <Lure> Hobbsee: can you fix that?
[11:27] <Lure> Hobbsee: it is anyway just moving files around
[11:27] <Riddell> Lure: kdebase-kde4 is stuck in new for a new binary
[11:27] <Lure> Riddell: can you fix that? ;-)
[11:27] <Hobbsee> Riddell: would have to fix my fixing, if i did.
[11:27] <Lure> Hobbsee: lol
[11:28] <Lure> Hobbsee: you can test how go he is in that ;-)
[11:28] <Lure> btw, what is URL for new queue
[11:28] <Lure> I forgot it since I did not need it for long
[11:29] <Lure> got it, is logical ;-)
[11:29] <Lure> ubuntu/hardy/+queue
[11:29] <Hobbsee> https://edge.launchpad.net/ubuntu/hardy/+queue?batch=500
[11:29] <Lure> Hobbsee: thanks, that batch thing is useful
[11:31] <Riddell> freed
[11:35] <Lure> Riddell: thanks - I expect I need to wait until nexty publisher run, right?
[11:36] <Riddell> Lure: yes
[11:37] <Lure> Hobbsee: can you give-back kdeedu-kde4?
[11:38] <Hobbsee> done
[11:38] <Lure> Hobbsee: thanks
[11:41] <mornfall> Pondery-ponder.
[11:42] <mornfall> I think I can rape the editor debconf frontend.
[11:43] <mornfall> By supplying a right EDITOR that would tell adept what to edit and wait for it. Hmh.
[11:43] <Riddell> mornfall: sounds narferous
[11:43] <mornfall> Parse error.
[11:45] <Riddell> devious
[11:45] <mornfall> Hm.
[11:46] <mornfall> It should actually work fairly well. Probably better than having a custom debconf frontend for that.
[11:47] <mornfall> I am just wondering if it is going to be easier to use dbus somehow, or a usual unix fifo...
[11:49] <Riddell> debconf over dbus?
[11:50] <mornfall> Nono, I just need this:
[11:51] <mornfall> My adept-debconf-editor would (possibly over dbus or over a fifo) notify the running adept instance that debconf is waiting for answers and that the file that has the quetions is under /tmp/foobar
[11:51] <fdoving> dbus is nice.
[11:52] <mornfall> Then it (to emulate the way editors work) wait till the user clicks Ok/Next whatever in adept and then exit (and adept itself would edit the file).
[11:52] <mornfall> But.
[11:52] <Jucato> speaking of debconf and Adept, I think there's a debconf bug that causes Adept to crash: bug 119243
[11:52] <ubotu> Launchpad bug 119243 in adept "adept manager & license agreement issue (dup-of: 108185)" [Medium,Confirmed] https://launchpad.net/bugs/119243
[11:52] <ubotu> Launchpad bug 108185 in adept "Adept crashes if Java license agreement is not accepted" [Medium,Confirmed] https://launchpad.net/bugs/108185
[11:53] <mornfall> Well, yeah.
[11:53] <mornfall> Will be fixed in new codebase I suppose.
[11:53] <fdoving> dbus is also a breeze to implement.
[11:53] <mornfall> fdoving: Well, how? : - )
[11:54] <fdoving> there is a techbase page about it.
[11:54] <mornfall> I need to put something into environment (variables) for a shell script to be able to call through it.
[11:54] <mornfall> Into adept. And I somehow doubt that the shell script is able to wait for a dbus signal or anything.
[11:55] <mornfall> So a pure dbus solution doesn't really sound all that plausible? Dunno.
[11:55] <fdoving> what will the shellscript do?
[11:55] <mornfall> See above.
[11:55] <mornfall> (The adept-debconf-editor thing.)
[11:56] <fdoving> adept-debconf-editor would be a shellscript notifying adept that it's waiting?
[11:56] <mornfall> Just like emacsclient, if you know that. But it uses sockets or such.
[11:56] <fdoving> then it needs something back, right?
[11:56] <mornfall> fdoving: Right.
[11:56] <mornfall> (Well, something ~ just an ACK that the user is done.)
[11:56] <fdoving> dbus calls can return something, as they really are regular functions.
[11:57] <fdoving> can't you put the answer in the return reply?
[11:57] <mornfall> Can I have a dbus call take 10 minutes eg.?
[11:57] <fdoving> not sure, but i guess so. why not?
[11:57] <mornfall> fdoving: That's sort of useless.
[11:57] <mornfall> (Since debconf anyway wants the answer in a file, and it is easier to put it there with adept.)
[11:59] <mornfall> I'll just use kill(1). Easy and POSIX.
[12:02] <fdoving> elegant :)
[12:04] <mornfall> And all I need that way is PID in say $ADEPT_PID and in the script wait for a timestamp change or such.
[12:26] <Riddell> nixternal: fancy submitting this to the dot? http://arstechnica.com/journals/linux.ars/2008/01/04/kde-4-0-0-tagged-in-preparation-for-release
[12:27] <mornfall> Another possibility is a passthrough frontend that seems to handle unix sockets. Hm.
[12:38] <mhb> morning
[12:50] <mhb> Riddell: what is the KDE4 plan, are we going to ship in Hardy KDE4.0.0 as it is now or some svn checkout from the KDE4.0.X branch?
[13:13] <Riddell> mhb: latest 4.0.x branch
[13:24] <Lure> Riddell: shouldn't kdm-kde4 install /etc/init.d/kdm4 ?
[13:24] <Riddell> Lure: yes, I havn't looked at kdm-kde4 at all
[13:25] <Riddell> dbg packages are also broken
[13:26] <Lure> Riddell: will look into kdm startup, as I do not want kde3 kdm or gdm
[13:34] <Lure> Riddell: should kdm4 be coexistant with kdm3?
[13:40] <Lure> Riddell: and I expect we add <name>-kde4.* files in debian and leaving debian's intact?
[13:40] <Riddell> Lure: yes ideally, although it's not the most important issue for it
[13:41] <Lure> Riddell: problem is that we just rename package names in debian/control, but did not rename also .postrm/.postinst/... files
[13:42] <Lure> so they are not picked up by cdbs
[13:42] <Riddell> if that's the only problem, can't be too hard :)
[13:43] <Lure> Riddell: that + fixing paths/names in scripts
[13:44] <Lure> Riddell: should I duplicate debian's or rename debian's (so having both kdm-kde4.* and kdm.*, only the later being used)
[13:44] <Riddell> Lure: rename
[13:44] <Lure> looking at other .install, I would say rename
[13:44] <Lure> ok
[13:51] <Lure> Riddell: I suspect /var and /etc are not in /usr/lib/kde4, right?
[13:56] <Riddell> Lure: they can be
[13:57] <Lure> Riddell: at least for /var that is not really acceptable, as /usr can be read-only (in theory)
[14:02] <Riddell> true
[14:11] <steveire> I can't apt-get build-deps kde4base without downloading most of gnome
[14:14] <steveire> It seems to be because of libxine plugins having a hard dependancy on xine-plugins-gnome in gutsy. Can this please be changed? The package was updated with this bug months ago.
[14:15] <Lure> Riddell: I will leave kdm config/options/logs in /etc and /var, just rename it from kwin.* to kwin-kde4.*
[14:16] <steveire> Lure: Are you a kubuntu dev?
[14:17] <Lure> steveire: yep (even though not core-dev)
[14:18] <Lure> steveire: I am not sure if we can solve build-deps as you would like
[14:18] <Riddell> it's fixed in hardy
[14:18] <steveire> are you able/authd to change libxine1-plugins dependancy on libxine-gnome (which depends on a lot of gnome) to a suggest instead? This is already the case in hardy, and is the result of an update during the gutsy cycle
[14:19] <steveire> Riddell: Hardy isn't released. This bug was introduced with an update to gutsy afaik. Can it not now be fixed?
[14:20] <Riddell> steveire: where did the update come from?
[14:21] <steveire> Riddell: I'm not sure. Seems to be in gutsy backports
[14:22] <steveire> http://rafb.net/p/Wstxim77.html
[14:23] <steveire> Getting a compile-able kde4 should be as simple as get build-deps for wanted modules, svn co and cmake.
[14:26] <steveire> Hmmm, the libxine1-plugins in universe also has the hard dependancy on gnome
[14:32] <steveire> Actually I don't know where all the gnome stuff is coming from. I was sure before it was from the plugins, but they don't look like hard dependancies in there anymore.
[14:32] <steveire> http://rafb.net/p/XR278u74.html
[14:36] <steveire> Oh yeah. libxine depends on the plugins meta-package depends on the gnome-plugins package, but in hardy it is only a suggests. http://packages.ubuntu.com/hardy/libs/libxine1-plugins
[14:37] <steveire> The change seems to be making libxine1 depend on the plugins package.
[14:38] <steveire> Riddell: Could you let me know if this is not going to be changed so that I can give up?
[14:44] <steveire> libxine1 did not depend on the plugins in feisty. I'm not sure when that was changed
[14:51] <Riddell> steveire: if it's from backports we could backport the newer version
[14:51] <steveire> Riddell:
[14:52] <steveire> Riddell: Cool. How would that happen/How long would it take?
[14:52] <Riddell> steveire: file a request bug on launchpad.net/gutsy-backports
[14:52] <Riddell> compile the hardy version on gutsy and make sure it works and report on that bug
[14:52] <Riddell> poke ScottK to confirm it
[14:52] <steveire> Also, while things are being backported it might make sense to do libsoprano4 as well. the gutsy version is too old to complie kde4
[14:53] <Riddell> good idea
[14:53] <steveire> Riddell: How do I get the hardy version?
[14:53] <steveire> do I  just dl and dpkg -i it?
[14:53] <Riddell> steveire: yes
[14:53] <Riddell> put hardy deb-src in sources.list
[14:53] <Riddell> apt-get source xine-lib
[14:54] <Riddell> debuild
[14:54] <Riddell> well cd xine-lib-<tab>; debuild
[14:54] <Riddell> debuild is from devscripts
[14:54]  * Riddell out
[14:57] <Lure> Riddell: more that I think, less I like binaries with -kde4 name
[14:58] <Lure> Riddell: will this at all work if the code does findExe() - it will not find appropriate binary
[14:58] <steveire> Alright, cheers. You really mean xine-lib or libxine1? Or -plugins?
[14:58] <Lure> Riddell: and I am sure we habe plenty of executions of kde binaries in the code...
[14:58] <fdoving> Lure: are the binaries renamed? - i thought there were just links.
[14:58] <Lure> fdoving: wrappers are named /usr/bin/<name>-kde4
[14:59] <fdoving> yeah, and the real binaries are in /usr/lib/kde4/bin/konqueror - for example?
[14:59] <Lure> Riddell: or will we patch findExe(), or am I missing something
[14:59] <Lure> fdoving: right
[15:00] <fdoving> well, i don't use the packages, and i belive coexistance will become a bug-magnet. sorry to be pesimistic.
[15:00] <fdoving> Lure: does the wrappers change the environment for those apps too?
[15:00] <Lure> fdoving: yep, but we cannot leave without it, as important programs (like kdepim) are missing
[15:01] <fdoving> Lure: that way around isn't a problem. the other way is harder.
[15:01] <Lure> fdoving: yes, so actually it might work then (kde4 app would probably findExe then on KDEDIRS)
[15:01] <fdoving> running kde3 apps from within kde4 will probably be more or less painless.
[15:01] <fdoving> as long as you don't use both versions with the same environment set. conflicting configfiles etc.
[15:02] <fdoving> the problem, as i see it, will be running kde4 apps from within kde3, without breaking the configs. that is you need to change the $KDEHOME to make the -kde4 apps write their configs to ~/.kde4
[15:04] <fdoving> i (think) kde4 apps will cope with converting the kde3 configs to new versions. the other way around, i'm more sceptical about.
[15:04] <Lure> fdoving: that should work if 1) you use .desktop files or 2) use /usr/bin/name-kde4
[15:05] <fdoving> i atleast, broke my ~/.kde because i started a full kde4 session with the ~/.kde $KDEHOME.
[15:05] <Lure> fdoving: so kde4 apps will always have condig in ~/.kde4
[15:05] <fdoving> does the wrappers change the environment?
[15:05] <fdoving> the -kde4 ones?
[15:05] <Lure> fdoving: yes
[15:05] <fdoving> good.
[15:06] <fdoving> then one just have to make it hard to execute the /usr/lib/kde4/bin binaries from within kde3, directly.
[15:07] <fdoving> not having it in the path, only desktop files etc.
[15:07] <fdoving> also, for kde3 apps to work correctly, with their own configs,  from within kde4.
[15:07] <fdoving> they need to be started with the kde3 $KDEHOME.
[15:07] <Lure> fdoving: yep, /usr/lib/kde4 is not in path
[15:07] <fdoving> so, one would need wrappers for kde3 apps too. :)
[15:08] <fdoving> i was playing with the idea to patch KDE4 to look for $KDE4HOME before $KDEHOME
[15:08] <fdoving> that way we don't have the one conflicting environment variable.
[15:09] <fdoving> as we have separate ones for kde3apps and kde4apps.
[15:09] <fdoving> would fix loads of issues.
[15:10] <Lure> fdoving: that is interesting idea
[15:10] <fdoving> it also is pretty simple.
[15:10] <fdoving> as it only affects kdelibs.
[15:10] <steveire> I like it. I assumed that would happen anyway.
[15:11] <fdoving> then one can throw the wrappers out the window.
[15:11] <Lure> Riddell: ^^^ that would be really safer than re-using KDEHOME
[15:11] <Lure> Riddell: problem is that kde3 app started in kde4 session would write config to ~/.kde4 (as they do not override config to ~/.kde)
[15:12] <fdoving> in my case, they won't.
[15:12] <fdoving> as we won't set $KDEHOME to ~/.kde4.
[15:12] <fdoving> we only set $KDE4HOME to ~/.kde4
[15:14] <freeflying> why dose systemsettings still need dependency on python-dev?
[15:17] <fdoving> Lure: hardcoding kde4 to only look for $KDE4HOME and ignore $KDEHOME is very simple. adding a '4' in one file. then we need to add one line to bin/startkde, to set the new variable to ~/.kde4
[15:18] <fdoving> i guess we will need to stick to ~/.kde4 for kde4 in the future too, right?
[15:19] <Lure> fdoving: not sure what are future plans, better ask Riddell
[15:19] <fdoving> i guess that would make sense, as moving configs in the users homedir isn't sane at all.
[15:19] <Lure> anybody knows db_input/db_go commands used in pre/postrm?
[15:23] <Lure> ok, got it, configured in <name>.config gile
[15:23] <Lure> file
[15:23] <fdoving> got a link to the kde4 packages?
[15:23] <fdoving> i'll make a proposed patch for my idea.
[15:24] <Lure> Riddell: how come that kdebase-workspace package I have downloaded with apt-get source does not have Ubuntu maintainer, even thougt it has ubuntu version?
[15:24] <Lure> Riddell: are we setting mail to ubuntu-devel-discuss or kubuntu-devel for kde4 packages?
[15:26] <Lure> Riddell: or ubuntu-motu as it is still in universe?
[15:33] <fdoving> bbl, dinner.
[16:21] <yuriy> mornfall: pong
[16:26] <mornfall> yuriy: Hi. Have you tried the send?
[16:27] <yuriy> mornfall: i sent it yesterday morning and pinged you
[16:28] <mornfall> yuriy: Sent where?
[16:28] <mornfall> Yesterday morning?
[16:28] <mornfall> *confusion*
[16:28] <yuriy> mornfall: meaning about 24 hours ago
[16:28] <yuriy> mornfall: i just did darcs send, i think it did me at mornfall dot net
[16:29] <mornfall> Hm, what timezone are you in?
[16:29] <yuriy> @time New York
[16:29] <ubotu> Current time in America/New_York: January 05 2008, 11:29:27 - Next meeting: Edubuntu meeting in 4 days
[16:29] <mornfall> Ah.
[16:29] <mornfall> Probably explaints the morning bit.
[16:30] <mornfall> However, does not explain why nothing arrived.
[16:30] <mornfall> yuriy: What should I grep mail logs for?
[16:32] <yuriy> hmm i don't remember what the subject i put on it was. is there a way to get darcs to tell me?
[16:32] <yuriy> or would patch names show up or something?
[16:32] <mornfall> They should. Probably best to try again.
[16:33] <yuriy> mornfall: k. i'd moved the packagelist stuff into a separate file so it'll probably conflict with your latest change
[16:34] <mornfall> Well, likely.
[16:35] <mornfall> But I wanted to test the send mechanics nevertheless.
[16:35] <yuriy> i was intrigued by darcs idea of only having conflicts when you edit the exact same line, but quickly found a use case where that doesn't quite work
[16:35] <mornfall> (And I can always re-do the patch from the diff.)
[16:36] <yuriy> oh i guess it doesn't ask for a subject. anyways, sent
[16:36] <mornfall> Okey, I am sitting on the mail log...
[16:37] <mornfall> (Btw., are you sure the sendmail(1) on your machine works right?) Or whatever darcs uses for sending mail.
[16:40] <mornfall> yuriy: I get patches in the mailbox when running darcs send on a university machine.
[16:40] <yuriy> nope, haven't tested it actually. will do
[16:40] <mornfall> Creating patch to "http://anna.fi.muni.cz/~xrockai/ept-work"...
[16:40] <mornfall> Patch bundle will be sent to: Petr Rockai <me@mornfall.net>
[16:42] <yuriy> hmm good point sendmail doesn't seem to be working
[16:43] <mornfall> : - \
[16:43] <mornfall> Somewhat un-unixy of that sendmail... : - )
[17:48] <nixternal> Riddell: story added from ars technica - review and push if you would like
[17:57]  * yuriy gives up on sendmail
[18:00] <fdoving> yuriy: fetch nullmailer and point it to your smtp.
[18:01] <yuriy> fdoving: i think i tried that already. what if my smtp needs authentication?
[18:02] <fdoving> yuriy: then i have no clue. postfix is also very nice.
[18:04] <fdoving> yuriy: http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg145592.html
[18:05] <yuriy> mornfall: saved to file and emailed
[18:11] <jpatrick> Riddell: kubuntu.org patch sent
[18:22] <mhb> Riddell: is it possible to do some "stub" for KDE4 systemsettings that would open the old unported config tools (guidance) in a new window?
[18:22] <mhb> Riddell: because users would like to access the guidance tools the old way
[18:22] <mhb> and there's little chance someone is going to port them all in time
[18:26] <yuriy> full kde4 session time : )
[18:26] <yuriy> drawing is pretty bad.. were there some tricks around for nvidia?
[18:27] <yuriy> oh and icons aren't showing up for most kde programs in the menu
[18:27] <yuriy> s/kde/kde4
[18:35] <mornfall> yuriy: Okey, thanks. I will show up tomorrow again. --> other room (no network)
[18:35] <mornfall> (Yes, it has arrived.)
[18:44] <yuriy> iijm or is everything huge in kde4? fonts?
[18:48] <yuriy> ooh forcing 96dpi worked nicely
[18:51] <yuriy> though i had to log out for it to take effect
[19:02] <iRon> yuriy: same as in kde3..
[19:03] <iRon> but in gnome all font settings takes place immediately after 'apply'
[19:03] <yuriy> iRon: i know, and in both it says that it'll take effect for newly started applications, which is not true
[19:04] <yuriy> now how to get the gtk apps to not look so ugly..
[19:05] <iRon> yuriy: on hardy ?
[19:05] <yuriy> iRon: on gutsy, with kde4 from ppa full session
[19:07] <iRon> yuriy: hm.. $ ln -s /usr/share/themes/Clearlooks/gtk-2.0/gtkrc ~/.gtkrc-2.0
[19:07] <iRon> or whatever theme you like
[19:08] <iRon> yuriy: there is a gtk port of Oxygen theme
[19:10] <iRon> yuriy: http://kims-area.com/?q=node/8 (search for Oxygen keyword)
[19:10] <nixternal> damn, I need an archive admin
[19:32] <yuriy> can't get the oxygnome theme to take effect.. oh well
[19:32] <fdoving> oxygnome?
[19:32] <fdoving> is that a gtk theme i probably want?
[19:35] <jpatrick> looks like it
[19:37] <yuriy> fdoving: yep, iRon's link above
[19:38] <yuriy> if there is no gtk-engines-qt for qt4 it might even be something to include if it's any good
[19:42] <fdoving> is there like a common place where gnome stores the gtk themes in users homedirs?
[19:42] <iRon> fdoving: ~/.themes
[19:43] <fdoving> ah, that wasn't so hard :)
[19:43] <fdoving> thanks.
[19:48] <fdoving> doesn't seem to pickup my changes, i've symlinked ~/.gtkrc-2.0 to the gtkrc of the theme.. anything else i need to do nowdays?
[19:53] <yuriy> fdoving: same here..
[19:53] <iRon> fdoving: this works for me on hardy.. on kde3 :)
[19:53] <fdoving> are we missing an engine or something?
[19:53] <fdoving> on kde3.. sigh :)
[19:53] <iRon> fdoving: will try now on kde4 :)
[19:54] <fdoving> it says:
[19:54] <fdoving> ·   engine "pixmap"
[19:54] <fdoving> in the gtkrc
[20:01] <yuriy> stdin: newer kdegraphics and multimedia, etc coming to ppa?
[20:03] <fdoving> yuriy: aha, GTK2_RC_FILES=:/home/frode/.kde4/share/config/gtkrc-2.0
[20:03] <fdoving> yuriy: pribably the same at your place i guess.
[20:10] <iRon> fdoving: oxygnome works fine for me on kde4 too
[20:10] <fdoving> iRon: oh
[20:11] <fdoving> did you install it to ~/.themes ?
[20:11] <fdoving> i tried gtk-chtheme it didn't even appear there.
[20:11] <iRon> fdoving: i put it in /usr/share/themes/
[20:11] <fdoving> now i made it load the .gtkrc-2.0 but it can't find the rest of the files to include.
[20:11] <fdoving> ah.
[20:12] <iRon> fdoving: from /usr/share/themes it works fine
[20:12]  * fdoving copies.
[20:13] <fdoving> iRon: did you symlink to ~/.gtkrc-2.0 ?
[20:13] <iRon> fdoving: i've a symlink to my ~/.gtkrc-2.0-kde :)
[20:14] <iRon> fdoving: which includes "/usr/share/themes/oxygnome..."
[20:17] <iRon> fdoving: my ~/.gtkrc-2.0-kde: http://pastebin.com/d2c49ef8f
[20:18] <ryanakca> nixternal: ping :)
[20:18] <nixternal> yo
[20:22] <fdoving> iRon: i didn't have that second line. got it to work, but -kde didn't work after i unset those gtk environment variables.
[20:22] <fdoving> brb, kid woke up.
[20:27] <fdoving> iRon: do you have a hover-color in the menus? - i don't.
[20:29] <iRon> fdoving: i have.. but oxygnome is far away from original oxygen theme..
[20:29] <yuriy> fdoving: i did ln -s /usr/share/themes/oxygnome/gtk-2.0/gtkrc ~/.kde4/share/config/.gtkrc-2.0 but it doesn't seem to have helped
[20:30] <fdoving> yuriy: you need to include the /usr/share/themes/oxygnome/gtk-2.0/gtkrc
[20:30] <fdoving> for paths to match.
[20:30] <fdoving> yuriy: have a look at irons paste http://pastebin.com/d2c49ef8f
[20:34] <yuriy> fdoving: oh nice that did it. i have the same problem with the colors though. either the theme is buggy or it's based on an old version of oxygen that had that problem
[20:34] <fdoving> yuriy: hover issues in the menus?
[20:35] <yuriy> fdoving: yeah.. but actually i think it only did the colors. scrollbars are still default gtk
[20:35] <fdoving> k.
[20:35] <fdoving> i have no clue. haven't been playing with gtk themes since gtk-1.2 back when i used gnome and blackbox.
[20:35] <fdoving> years ago.
[20:38] <iRon> fdoving: yuriy: oh.. this theme depends on murrine gtk engine. so: apt-get install gtk2-engines-murrine :)
[20:39] <fdoving> i did that.
[20:41] <iRon> also try to start firefox from konsole. and if there will be gtk theme errors -- you'll see them in console output
[20:41] <fdoving> i have a bunch of gdkpixbuf issues.
[20:42] <fdoving> when browsing menus..
[20:42] <fdoving> (gecko:22600): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed
[20:42] <fdoving> probably related to the issues with hover.
[20:42] <iRon> fdoving: hm.. strange
[20:42] <fdoving> can you md5sum your oxygnome.tar.gz ?
[20:43] <iRon> fdoving: have you tryed to install `gtk2-engines-pixbuf' too?
[20:43] <fdoving> yep, it's in.
[20:45] <iRon> fdoving: md5 -- 0f7b9349c91f93e31e3535a66ee9e838
[20:45] <fdoving> 0f7b9349c91f93e31e3535a66ee9e838
[20:45] <fdoving> that looks like a match to me.
[20:45] <iRon> fdoving: i'm on hardy
[20:46] <fdoving> i'm on gutsy.
[20:46] <fdoving> do you have any gnome things installed?
[20:49] <fdoving> .../gtk2-engines-pixbuf_2.12.0-1ubuntu3_i386.deb
[20:49] <fdoving> is your version higher?
[20:50] <fdoving> i'll fetch the hardy version.
[20:50] <iRon> fdoving: i've one from hardy.. it is 2.12.3-2
[20:52] <yuriy> i get lots of: (firefox-bin:20989): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
[20:52] <fdoving> yuriy: then you need gtk2-engines-pixbuf
[20:52] <fdoving> once you get it you'll get new fancy errors, like me.
[20:52] <fdoving> gtk2-engines-pixbuf is part of gtk+2.0
[20:53] <fdoving> so i won't recompile that for gutsy.
[20:55] <yuriy> fdoving: i installed that and it actually works now, menus too. doesn't look anything like current oxygen though. probably based off a previous incarnation
[20:55] <fdoving> gah, so i'm the only one with the problem.
[20:55] <fdoving> yuriy: looks better than default gtk, right?
[20:56] <yuriy> fdoving: certainly
[20:56] <fdoving> yuriy: are you on hardy too?
[21:09] <yuriy> fdoving: no, i'm on gutsy
[21:11] <fdoving> somehow my kde4 tries to overrride the gtk theme, but fails.
[21:14] <fdoving> needed to use the kde3 colors kcmmodule to uncheck the "apply colors to non-kde apps" box. now kde4 doesn't override my gtk things anymore.
[21:24] <LaserJock> anybody around who knows about the kubuntu-members-kde4 PPA?
[21:26] <Riddell>  LaserJock hmm?
[21:26] <LaserJock> I noticed some new packages
[21:27] <Riddell> mm hmm
[21:27] <LaserJock> however it looks like the uploads aren't all finished yet as a dist-upgrade wants to get rid of a lot of previous kde4 packages
[21:27] <LaserJock> Riddell: the new stuff is 3.98
[21:29] <LaserJock> looks like kdelibs and kdebase 3.98 but rest is 3.97
[21:40] <Riddell> stdin: new kde 4 packages to backport
[21:43] <LaserJock> Riddell: so everything is ok, I just need to wait?
[21:44] <Riddell> LaserJock: yes
[21:44] <LaserJock> Riddell: excellent thanks
[21:44] <LaserJock> I really appreciate these KDE4 packages
[21:48] <ryanakca> Riddell: ping
[21:48]  * ryanakca points to /msg
[22:18] <stdin> Riddell: which ones?
[23:33] <articpenguin3800> is kde 4 included with 8.04
[23:34] <jpatrick> articpenguin3800: yes
[23:34] <articpenguin3800> is it supported
[23:34] <jpatrick> articpenguin3800: ye
[23:34] <jpatrick> -s*
[23:34] <articpenguin3800> in the main repo or universe repo
[23:35] <jpatrick> not sure, yet, either way it's on the CD
[23:35] <jpatrick> or planned to be
[23:35] <jpatrick> articpenguin3800: see: http://people.ubuntuwire.com/~jpatrick/minutes/kubuntu-meeting-20071222.pdf
[23:38] <articpenguin3800> ok thanks
[23:40] <jpatrick> you're welcome
[23:40] <articpenguin3800> one more thing is it possible to dualboot kubuntu 7.10 and kubuntu 8.03
[23:40] <articpenguin3800> -4
[23:41] <jpatrick> yep
[23:41] <articpenguin3800> just shrink my jfs partition and put 8.04 there
[23:42] <jpatrick> that should do it..
[23:42] <articpenguin3800> ok thanks again
[23:42] <articpenguin3800> cya
[23:43] <iRon> jpatrick: which font is used in your PDF's? it is so cute. ;)
[23:43] <jpatrick> iRon: Sans Serif
[23:43] <jpatrick> what the latex command?
[23:43] <jpatrick> want*
[23:43] <iRon> yes
[23:44] <jpatrick> well.. change .pdf to .tex
[23:44] <jpatrick> all in the commends
[23:44] <jpatrick> arg
[23:44] <jpatrick> comments*
[23:54] <jpatrick> night