[04:21] <minghua> Riddell: ping
[04:38] <freeflying_> Riddell:   https://launchpad.net/distros/ubuntu/+source/qt-x11-free/+bug/6606
[04:39] <freeflying_> Riddell: guys from ubuntu-kr team report that hi can not activate nabi , which is a korea input method using xim
[04:40] <freeflying_> Riddell: it's seems something wrong with qt pached with qtimmodule
[04:41] <\sh> Riddell: why did you delete the website about kde-hal-device-manager?
[04:41] <\sh> freeflying_: did they test out the new upload of qt? I patched qtimmodule patch to make it work again...with keyrelease evenets
[04:42] <\sh> oh i read the bug report now
[04:42] <freeflying_> \sh is 3.3.5-1ubuntu13?
[04:44] <\sh> yes
[04:44] <freeflying_> \sh: it dosen't work too
[04:45] <\sh> well...then we're fcked
[04:45] <freeflying_> \sh or we'd remove that patch 
[04:46] <\sh> well, then katapult is not working anymore
[04:46] <freeflying_> \sh: I meant remove qtimmodule patch
[04:46] <\sh> most properly would be removing the whole immodule patch completly
[04:47] <\sh> but I wonder, why this patch is proposed to work and everybody should apply it, when it's totally buggy and PITA
[04:47] <freeflying_> \sh I  totally agree with you , anyway we shall make input method work with qt/kde program
[04:48] <\sh> what do i have to do to enable this korean thing?
[04:48] <\sh> I want to see it for myself, so I know now, what is it about :)
[04:49] <\sh> freeflying_: can you give me a short introduction?
[04:49] <freeflying_> \sh : I know quite few of korean input method
[04:50] <freeflying_> \sh but I think it may work like scim 
[04:50] <\sh> actuallhy i don't know anything about input methods at all :) 
[04:51] <\sh> sometimes I'm really happy to use latin characters
[04:51] <\sh> anyways...I'll ask the reporter :)
[04:54] <minghua> \sh, freeflying_: I have similar problem with scim in XIM mode, I've added a comment in the bug
[04:55] <minghua> although I haven't upgraded my KDE and try again yet
[04:55] <\sh> minghua: hmmm...ctrl+space must work :)
[04:55] <\sh> minghua: because it's working with katapult
[04:56] <\sh> minghua: you don't have katapult installed and started?
[04:57] <\sh> minghua: and try to install scim-qtimm
[04:57] <minghua> \sh: seems not, what package is it in?
[04:57] <\sh> katapult
[04:57] <minghua> \sh: well, the whole point of this bug is using input method in XIM mode, which scim-qtimm works around
[04:58] <minghua> scim supports three IM mode, but most input methods only support one, namely XIM mode
[04:59] <freeflying_> minghua: can u work with scim-qtimm?
[04:59] <minghua> freeflying_: didn't try
[04:59] <\sh> well...the thing is, I don't know if the gtk app is sending the right X11KeyRelease events...and if they're received by qt at all...
[05:00] <\sh> or to be more precise, if the right X11Key* events are catched up by qt when it was send from gtk apps, because Qt is quite different
[05:01] <minghua> I don't know about these things either, the thing I am concerned about is that scim is reported to work in Debian unstable's KDE (without skim or scim-qtimm), while it seems it doesn't in Ubuntu's KDE
[05:02] <minghua> I probably will install KDE in my unstable box later to make sure, but that's not my priority
[05:02] <minghua> so I didn't even report this bug when I first encountered it
[05:03] <\sh> minghua: debian doesn't use qtimmodule 
[05:03] <\sh> minghua: that is the difference between ubuntu and debian
[05:03] <minghua> \sh: exactly
[05:03] <minghua> \sh: are you saying qt-immodule can't coexist with XIM?
[05:03] <minghua> that would be really bad
[05:04] <\sh> minghua: no, this i can't say, because I don't know. What I know is, that the qt immodule patch is proposed to be the default for distributors to have compatiblity between gtk and qt
[05:04] <\sh> but somehow this patch is so strange and a PITA...
[05:05] <minghua> \sh: not according to what I heard
[05:05] <\sh> http://www.freedesktop.org/wiki/Software_2fimmodule_2dqt
[05:05] <minghua> \sh: my knowledge is that qt-immodule has nothing to do with GTK apps, just as gtk2-immodule has nothing to do with Qt apps
[05:05] <minghua> I'm writing a little more in the bug
[05:05] <\sh> This project brings functionality similar to the immodule for GTK+ to the Qt library. The main goal of the project is to extend and enhance the input method support in the Qt library, in order to provide a modern and powerful multi-language input system. Our short term goal is to make Qt (especially Qt/X11) "up-to-date" with other X11-based toolkits such as GTK+. We are also focusing on what the input method API should be for future Qt ver
[05:06] <\sh> compatiblity is a bad term, I know
[05:09] <minghua> yeah, the "up-to-date" here means having the same feature/usability, but not inter-operatability, IMHO
[05:09] <\sh> yes
[05:09] <freeflying_> minghua: skim can also work with gtk/gnome program 
[05:10] <\sh> how do i enable skim or scim-qtimm?
[05:10] <minghua> freeflying_: yes, but then skim uses GTK IM mode or XIM mode
[05:11] <minghua> there is no way qt-immodule can work in non-qt apps, at least that's what I heard
[05:11] <\sh> what do i have to start first to let it work 
[05:11] <minghua> QT_IM_MODULE=scim kate, I suppose
[05:11] <minghua> bug freeflying_ should know better
[05:12] <freeflying_> \sh  export QT_IM_MODULE=scim and export QT_IM_SWITCHER=imsw-muti
[05:12] <\sh> and then?
[05:12] <freeflying_> \sh; then " skim -d "
[05:13] <freeflying_> or " scim -d "
[05:13] <\sh> ok..and now?
[05:13] <freeflying_> \sh you will have skim icon in your tray
[05:13] <\sh> nope
[05:13] <\sh> not for skim
[05:14] <\sh> with scim yes
[05:14] <freeflying_> \sh export XMODIFIERS="@im=SCIM"
[05:14] <\sh> ok..now how can I enter some special characters which are non-latin?
[05:14] <freeflying_> \sh if you have intalled skim , then in kde , whether you use scim or skim , skim will start 
[05:15] <freeflying_> \sh  you'd install some IMEngine like scim-pinyin 
[05:15] <\sh> just doing it now :)
[05:15] <\sh> ok..done
[05:16] <freeflying_> \sh if they can up , you can use ctrl+space to activate 
[05:16] <\sh> no..doesn't work..scim is running now
[05:18] <freeflying_> \sh minghua can give you suggestion on how to enable scim 
[05:21] <\sh> oh well, no accents on french keyboards anymore since the immodule KeyRelease event patch
[05:22] <\sh> and after the qt immodule patch
[05:22] <\sh> Riddell: about whatever you are dreaming today :) please let us come with a good solution to fix those issues. qtimmodule is such a PITA...
[05:23] <\sh> s/come/come up/
[05:24] <\sh> and I'm such a loser because I work with nodeadkeys
[05:24] <minghua> \sh: I heard scim fixed deadkeys long ago, but I don't know the detail
[05:25] <\sh> minghua: the reporter told me with qt 1ubuntu9 he didn't have any problems
[05:25] <minghua> \sh: I only know the GNOME side of input methods, so if you wanna try, I can give you a quick walkthrough
[05:25] <minghua> \sh: I saw that, too.  I can recompile Qt to hunt down this problem later, but not know
[05:26] <\sh> which means that in 1ubuntu10 the immodule patch was actually enabled
[05:26] <\sh> minghua: well, we need to get a working (sic!) example of how it should work in qt
[05:27] <\sh> well...I think the best is to disable qtimmodule patch for dapper...it makes no sense to have broken code inside
[05:27] <minghua> \sh: that's exactly the reason I installed KDE for the first time after three years' using of Linux
[05:28] <minghua> \sh: I wanted to write precise and exact howto to use scim in KDE, but...
[05:29] <minghua> I don't want to rely on skim/scim-qtimm as they are not available in debian yet
[05:30] <\sh> ok...we have a couple of weeks left until Feature Freeze
[05:30] <\sh> so we need to dive into this problem or disable this feature 
[05:34] <\sh> brb
[05:43] <\sh> grmpf...I followed the instructions on the scim/skim homepage..
[05:43] <\sh> doesn't help
[05:43] <minghua> \sh: do you have a sid environment?
[05:44] <\sh> yes chroot on my amd
[05:44] <\sh> i386 chroot :)
[05:44] <minghua> would you like to try there?
[05:44] <minghua> I'm not sure if i386 chroot on amd64 will cause extra problem though...
[05:45] <\sh> i don't know...but if you can send me a small howto to sh@sourcecode.de I can test it later this day..because I need to get some more sleep :)
[05:46] <minghua> \sh: okay, I'll do that
[05:46] <\sh> minghua: cool..thx...
[05:46] <\sh> ok..i'm going back to dreamland :) 
[05:47] <\sh> ok..cu later 
[07:11] <minghua> \sh_away: scim walkthrough mail sent
[09:08] <\sh> Riddell: wake up :) it's early in the morning...good for discussing important development decisions ;) 
[09:17] <\sh> Riddell: we forgot to install usr/lib/qt3/plugins/inputmethods/*.so into libqt3-mt package. I just fixed it...
[09:27] <\sh> good morning Hobbsee 
[09:27] <Hobbsee> evening \sh :)
[09:30] <allee> Hobbsee: hey only 5 hour more kubuntu work left ;)
[09:30] <Hobbsee> hehe
[09:31] <Hobbsee> *errors
[09:32] <allee> Hobbsee: yeah, same here last night :(
[09:33] <allee> Hobbsee: so something easy for you:  Do you use kontact? and the addressbook?
[09:33] <Hobbsee> allee: no, and no, sorry
[09:34] <Hobbsee> what are you looking for?
[09:34] <allee> since Friday then I restart kontact the addressbook is empty
[09:35] <allee> -rw-r--r-- 1 ach ach 196496 2006-01-14 09:27 std.vcf_6
[09:35] <allee> -rw-r--r-- 1 ach ach      0 2006-01-14 09:27 std.vcf
[09:35] <allee> this happens on startup on kontact :(  I have to exit kontact, cp the backup, restart
[09:36] <allee> no updates here since Friday (only dialup until monday)
[09:36] <Hobbsee> just tried creating a contact, shutting all of kontact, opened it again, contact is still there
[09:37] <allee> thx, it's strange.  Stop (address not empty), start -> address empty.  Stop again, cp, start and address is preserved
[09:38] <Hobbsee> i'm not sure if there was an upgrade of kontact in the last couple of days - there may well have been, as a lot of kde stuff was upgraded
[09:38] <allee> Hobbsee: thx for trying. Because it works for you I assume the prob will be gone after next update
[09:39] <Hobbsee> *nods* - no problems
[09:39] <\sh> on 2006-01-06 there was a rebuild of kdepin
[09:39] <\sh> kdepim even
[09:40] <allee> Hobbsee: side note: you can always check the last update of an pkg with ls -ltr /usr/share/doc.  Check date
[09:40] <allee> \sh: good. new kdepim. So more hope that prob is gone after next update.thx
[09:41] <\sh> allee: so your last dist-upgrade was before the 2006-01-06?
[09:41] <Hobbsee> ah, i see...thanks allee!
[09:41] <allee> ah, there's also new /var/log/dpkg.log
[09:42] <allee> \sh no. last up 2006-01-12 22:37
[09:42] <Hobbsee> allee: which would be the 12th of jan, wouldnt it?
[09:43] <Hobbsee> yes, right
[09:43] <\sh> yes..
[09:43] <Hobbsee> dont worry about em
[09:43] <Hobbsee> *me
[09:43] <\sh> kdepim was finally compiled on the 2006-01-08 so you should have latest version :)
[09:45] <\sh> YYYY-MM-DD 
[09:46] <allee> reboot   system boot  2.6.15-11-686    Sat Jan 14 09:05          (00:39)
[09:46] <allee> reboot   system boot  2.6.15-11-686    Fri Jan 13 08:36          (13:59)
[09:46] <allee> reboot   system boot  2.6.15-11-686    Mon Jan  9 19:54         (3+04:05)
[09:46] <allee> reboot   system boot  2.6.15-11-686    Sun Jan  8 18:19         (1+01:33)
[09:47] <allee> \sh: Monday was very busy.  I'm not sure if I just fixed the problem.  But yesterday it was defenitely emtpy
[09:49] <\sh> strange...should be something else then..but what?
[09:53] <allee> \sh: mhmm, I had this long ago too.  Can't remember what was the solution (was a fixed upstream).  lemme search ...
[10:03] <allee> \sh, Hobbsee_away: Hmm, when I close my two 'not finished yet' Windows and restart kontact (tried 3 times) the problem is gone.
[10:04] <allee> \sh, Hobbsee_away: Open the msg in draft folder again.  Exit kontact and address book is empty again.  yeah!
[10:05] <\sh> allee: sounds like upstream :)
[10:05] <allee> \sh yes
[10:06] <allee> \sh reminds me: is malone now the only ubuntu bts and ready?
[10:06] <\sh> allee: yes
[10:17] <Tm_T> *** glibc detected *** corrupted double-linked list: 0xb62a9278 ***
[10:17] <Tm_T> :(
[10:44] <freeflying_> \sh: ping
[10:45] <\sh> freeflying_: pong
[10:45] <freeflying_> \sh have your input method configured ?
[10:45] <\sh> freeflying_: no..but we know now what caused the problem (imho)
[10:46] <\sh> freeflying_: missing inputmethod plugins :)
[10:46] <freeflying_> \sh I've read your comment on launchpad
[10:46] <\sh> freeflying_: i fixed it with the latest upload...so minghua and you can test :)
[10:46] <Hobbsee_away> allee: very weird!
[10:46] <freeflying_> \sh : but actually there has libscim.so in that dir
[10:47] <freeflying_> \sh and why can't we use that plugin?
[10:48] <minghua> freeflying_: that won't work, since XIM mode need libqxim.so
[10:48] <freeflying_> minghua: can't we use QT_IM_MODULE?
[10:55] <minghua> freeflying_: what do you mean?  tell everybody "XIM is broken, use Qt IM module instead"?
[10:55] <minghua> freeflying_: what are you going to do with IMs without Qt IM mode support?
[10:57] <allee> Hobbsee_away: yes, it is. http://bugs.kde.org/show_bug.cgi?id=120093  Feel free to reproduce ;)
[11:02] <freeflying_> minghua: I just mean although there is no libqxim.so , why dose not  libscim.so  work ?
[11:03] <minghua> freeflying_: why will it?  it's not like nabi can use scim's Qt IM module
[11:04] <freeflying_> minghua: but scim can use . 
[11:05] <minghua> so?  the bug is about "nabi is not working in KDE" after all
[11:06] <nlindblad> good morning
[11:08] <freeflying_> minghua: this not noly about nabi but also scim in kde
[11:13] <Hobbsee> allee: looking
[11:16] <nlindblad> is the migration finished?
[11:25] <\sh> freeflying_: well.I followed the instruction of upstream...about scim and skim
[11:25] <\sh> freeflying_: for me it didn't work
[11:25] <\sh> freeflying_: but I could make a mistake somehow
[11:30] <\sh> freeflying_: so it would be good to test the new package of libqt
[12:03] <Riddell> \sh: aah
[12:03] <\sh> Riddell: 
[12:03] <\sh> [12:02]  <minghua> \sh: okay, I have XIM mode working
[12:03] <\sh> [12:02]  <minghua> \sh: although scim doesn't work well in XIM mode
[12:03] <\sh> [12:02]  <minghua> \sh: but that's a different issue and it's not specific to KDE (I've seen it in GNOME too)
[12:03] <\sh> [12:03]  <minghua> \sh: so your fix to libqt3 works
[12:03] <\sh> Riddell: means FIXED !!! strike :)
[12:04] <Riddell> awooga
[12:04] <nlindblad> Riddell: trying flight 3 now
[12:04] <nlindblad> Riddell: i386, working fine
[12:05] <Riddell> nlindblad: flight 3 /candidate/ still :)
[12:05] <Riddell> thanks
[12:06] <nlindblad> I know, but I'm seeing if I can confirm that freeze someone had
[12:14] <\sh> ok one bug fixed...what's next
[12:16] <nlindblad> did all permissions vanish during the migration?
[12:16] <\sh> nlindblad: permissions?
[12:16] <nlindblad> editbug
[12:17] <\sh> nlindblad: well...it's different from bugzilla..I would ask in #launchpad about this :)
[12:17] <nlindblad> but I'm talking about the permissions I got two days ago
[12:17] <nlindblad> to edit bugs at bugzilla.ubuntu.com
[12:18] <nlindblad> are those permissions gone?
[12:18] <\sh> nlindblad: it's different from bugzilla...I don't think there are some special "permissions" as for bugzilla
[12:18] <nlindblad> okey
[12:19] <\sh> bugzilla itself is readonly and you can't login anymore
[12:19] <nlindblad> but isn't it based on team-approval and stuff?
[12:19] <nlindblad> if you're not in the team you can only make suggestions
[12:24] <\sh> dunno :) what do you want to do e.g. closing bugs should be possible 
[12:26] <nlindblad> I wanna help out
[12:26] <nlindblad> confirm, etc.
[12:32] <\sh> nlindblad: should work :) try it :)
[12:33] <\sh> Riddell: I'm working on the libXft.la issue for kubuntu stuff
[12:34] <freeflying_> \sh I'll have a  try on your latest upload qt tommor
[12:34] <\sh> freeflying_: no problem :) 
[12:55] <Tm_T> Riddell: I have this qt bug appearing (?) with kopete now http://bugs.kde.org/show_bug.cgi?id=116176
[12:57] <Tm_T> damn, I usa monospace fonts everywhere
[12:58] <Tm_T> s/usa/use
[12:58] <Tm_T> oh well...
[01:07] <JRe> It's me or detection of plugged disk in dapper is not working anymore ?
[01:09] <Tm_T> Riddell: yes, font/Qt issue, disabling custom fonts "fixed" that crash :/
[01:14] <\sh> Tm_T: looks like fontconfig fun, when I'm reading this bugreport
[01:30] <Tm_T> \sh: that too
[01:30] <Tm_T> \sh: looks like it was just one font triggering this bug or whatever it is
[01:31] <Tm_T> so just modifying config file and voila
[01:31] <\sh> Tm_T: well..our fontconfig version should be clean, regarding dirk muellers elaboration on this issue
[01:31] <Tm_T> should..
[01:32] <Tm_T> well, now I know that that one font may cause problems, so I avoid it
[01:32] <Tm_T> it's unusable font anyway :p
[01:32] <Tm_T> was set by mistake
[01:33] <Tm_T> ...and looks like I'm installing qt updates, compiling stuff like crazy ->
[01:39] <\sh> Tm_T: the new package from dapper, which I uploaded a couple of hours ago?
[01:46] <pef> someone familiar with laptop functionnality debugging ?
[01:46] <\sh> pef: mjg59 :)
[01:47] <pef> \sh: thanks for the pointer :)
[01:47] <\sh> pef: #ubuntu-laptop :)
[01:47] <pef> \sh: i'm there ;)
[01:47] <\sh> damn...I rebuild libkipi to forget libXft.la but gwenview wants to have it still...
[01:47] <\sh> lets see kdelibs4
[01:48] <pef> \sh: got same problem yesterday when trying to rebuild drip because of broken dependencies
[01:48] <\sh> pef: yeah..some lib*.la files still have references...trying to get rid of them 
[01:49] <\sh> looks like it will be a great adventure for me to find out all the build-deps and checking the -dev packages
[01:49] <pef> \sh: the faulty library just need to be rebuild, right ?
[01:50] <\sh> pef: normally
[01:50] <\sh> but e.g. gwenview have only build-deps named kdelibs4-dev and libkipi-dev and libexif
[01:50] <\sh> libexif is clean, libkipi is clean as well
[01:50] <\sh> so something is missing...and it looks like that I will find it somewhere in kdelibs4
[01:50] <\sh> kaffeine is clean too :)
[01:50] <\sh> after the rebuild
[01:52] <pef> will investigate for drip :)
[02:02] <tvo> blegh, now konqui crashes whenever I try to d/l an example exam... don't think it's a really smart idea to go debug it before studying :)
[02:03] <pef> \sh: found one reference to libXft.la in libavifile, maybe it can be usefull to you if listed in bdepends :)
[02:04] <\sh> well...it's not so easy
[02:06] <\sh> libavifile?
[02:08] <pef> yes
[02:11] <\sh> ok rebulding in pbuilder and checking
[02:12] <pef> libavifile ? I'm rebuilding it right now :) seems to be a bit longer to build
[02:13] <\sh> pef: well..it can build until i tracked down what else is contaminated with libXft.la :)
[02:13] <pef> eheh :)
[02:13] <\sh> find . -type f -exec grep -l "libXft.la" {} \; &> /home/shermann/libxft.la.lst
[02:14] <\sh> this is my first target :)
[02:14] <pef> used same method :) but on my dapper chroot the list is narrowed
[02:14] <\sh> and some of those build-deps in kdelibs and kdebase are the bad boys :)
[02:18] <Tm_T> \sh: I think yes
[02:19] <pef> \sh: libavifile was the problem for me...to the new release number, should I increase ubuntux or add build1 (I think no because not a transition)
[02:20] <\sh> pef: can you uploads? increase ubuntu version because it's already an ubuntu version...only if it's a debian revision then we add for a rebuild "buildN"
[02:22] <pef> \sh: thanks, I will upload it within the hour :)
[02:22] <pef> just have to go to work because I forgot keys
[02:22] <\sh> pef_aw: i can upload as well...it's just finished here :)
[02:23] <pef_aw> \sh: so do it if you can't wait 1 hour ;)
[02:24] <\sh> pef_aw: it's finished right now :)
[02:24] <Tm_T> heh
[02:24] <pef_aw> \sh: nice :)
[02:24] <pef_aw> bbl
[02:25] <Tm_T> humm, nice loads, should not compile 5 apps at the same time
[02:43] <\sh> ok...lipstik is cleab
[02:43] <\sh> clean even
[02:54] <Tm_T> \sh: tiblit has more configuration :)
[02:56] <\sh> Tm_T: what ever this is :)
[02:57] <\sh> I have to find the time to bring qinx into ubuntu...nobody wanted to have it in debian, but I like it very much..and it's in my package repository since I started for ubuntu 
[02:57] <\sh> and actually I'm not afraid anymore to touch qt :)
[02:57] <pef> \sh: a question about your last change on drip package
[02:58] <\sh> pef: when was it?
[02:58] <\sh> last year? I don't remember anything :)
[02:58] <crimsun> Qt is pretty sane, but Qt4 has some package issuse
[02:58] <crimsun> issues^
[02:58] <\sh> crimsun: did you apply the qt-immodule patch? if so, make sure it installs somehow /usr/lib/qt3/plugins/inputmethods/*
[02:58] <pef> \sh: you changed bdepends from libmagick++9-dev to libmagick++6-dev, why not libmagick++-dev instead ? now libmagick++6-dev no longer exists, so the package has broken dependencies
[02:59] <crimsun> \sh: looking at the source, it didn't appear to need it
[02:59] <\sh> pef: because I think we didn't have such thing like libmagic++-dev
[02:59] <crimsun> it does the check differently from Qt3, at least
[02:59] <pef> \sh: ok, that what I thought, :)
[02:59] <\sh> crimsun: so it's already upstream? :)
[02:59] <\sh> crimsun: I mean the patch :
[02:59] <\sh> )
[02:59] <crimsun> \sh: well, at least 4.1.0-1 applied it differently
[03:00] <\sh> hmmm.
[03:01] <\sh> rebuilding kdeutils and pray that there is nothing more for this to do
[04:00] <\sh> ok..gwenview is a bastard
[04:01] <Tm_T> ?
[04:02] <\sh> I lack at least one implicit build-dep with libXft.la
[04:02] <\sh> kdeutils is cleaned, kdeaddons will be cleaned just now
[04:03] <Tm_T> ah
[04:27] <allee> \sh: ah, libXft.la.  Rebuild libkipi (or better use the relibtoolized version from alioth) and gwenview builds
[04:28] <\sh> allee: libkipi is free of libXft.la :)
[04:28] <\sh> allee: but I think I have to relibtoolize gwenview...I'll see, when I do the rest...I only lack of one or two packages
[04:28] <\sh> kio-apt is just finished
[04:28] <\sh> and kdebluetooth is next
[04:29] <\sh> so I have time for gwenview :)#
[04:29] <allee> \sh: libkexif also done aka rebuild or alioth version that is relibtoolized?
[04:30] <\sh> allee: libkexif I need to look later...because it's not in any build-dep of the packages I installed in my chroot :) but thx for reminding me :)
[04:31] <allee> \sh yeah, relibtooization if a pain. libs are more or less straight forward but bigger one like digikam are ...
[04:31] <allee> ... lots of .la garbage.
[04:32] <allee> \sh: ah remind me were I stop with relibtoolize of digikam: A build system patch is needed so LIB_QT=-lqt-mt instead of "-lqt-mt -lroughly_a_dozend_more"
[04:32] <\sh> yepp
[04:33] <allee> \sh: this would fix all simple apps
[04:33] <allee> ... to loose their implizit dependencies  (14 afair)
[04:35] <allee> \sh fwiw: libkexif is build-dep of digikam and I hope to get 0.8.1 in before 19th.
[04:36] <\sh> in ubuntu or debian? :)
[04:37] <\sh> hmmm..I wonder why kdebluetooth checks for xmms
[04:37] <allee> \sh this time first ubuntu due to deadline issues.  I can't wait this time daily new proc and sync
[04:37] <\sh> kewl :)
[04:39] <allee> \sh: yeah, my way of ubuntu uploading get's me no applyForMOTU++, but debianRelation++ ;)
[04:40] <\sh> hahahahaa
[04:42] <allee> \sh kdebluetooth bemused uses it:
[04:42] <allee> +    - bemused, a server for the symbian remote control software
[04:42] <allee> +      of the same name to control xmms, noatun etc.
[04:43] <\sh> hmmm..that it's more funny, that it doesn't find it...must have a look again on the build deps
[04:49] <pef> https://launchpad.net/distros/ubuntu/+source/freewheeling/+bug/28519
[04:49] <pef> then the programm segfaults... what should I do, upload an installable version, or wait a solution for fixing segfault ?
[04:56] <\sh> first of all, fix the dependency
[04:57] <\sh> then try to fix the segfault...if it's not possible for you right now, install the fixed depency, and file a bug report about the segfault (don't forget the stacktrace :))
[04:58] <\sh> dependency even
[05:00] <pef> ok, thanks :)
[05:05] <tenco> just a question: is dapper already stable enough to be used by an expierenced linux-user, like debian unstable?
[05:06] <\sh> dapper is unstable...but stable enough to develop with it :)
[05:07] <Tm_T> and always ready to tell when kernel is broken _again_ ;--P
[05:07] <tenco> i am just curios because dapper has a lot of packages i am interested in, like tetex 3 and a DRI module for savage cards
[05:08] <tenco> s/DRI module.../xorg 6.7/
[05:08] <tenco> s/xorg 6.7/xorg 7.0/
[05:08] <Tm_T> xorg 7.0 I think
[05:08] <Tm_T> ;)
[05:09] <tenco> X-D
[05:09] <Tm_T> I'm pre-alpha/alpha/beta tester anyway, so dapper is just fine to me
[05:10] <tenco> whats UVF?
[05:11] <Tm_T> hope it's not Ubuntu version Freeze
[05:11] <Tm_T> V
[05:11] <crimsun> it's upstream version freeze
[05:11] <Tm_T> aye
[05:11] <crimsun> with few exceptions, we don't accept newer upstream versions of packages already in the archive
[05:12] <Tm_T> crimsun: aye, so that means we're getting stable from now on, I hope atleast :p
[05:12] <crimsun> yes, that's the plan
[05:12] <tenco> ah, ok.
[05:13] <Tm_T> hum, getting busy if I will try get some artwork to release then :p
[05:13] <Tm_T> month or two
[05:13] <tenco> seems like i will use dapper from now on :-)
[05:13] <Tm_T> good
[05:14] <tenco> bye!
[05:19] <\sh> ok...most of the kde stuff is rebuild and libXft.la clean...gwenview is my last one now
[05:19] <\sh> (then libkexif and digikam)
[05:21] <crimsun> the dastardly libXft.la
[05:23] <\sh> phew
[05:34] <allee> \sh Monday or tuesday digikam 0.8.1 will be released.  So maybe you can skip digikam  (rc1 deb: http://www.mpe.mpg.de/~ach/tmp/)
[05:34] <\sh> I think I will skip today libkexif as well..gwenview relibtoolizing doesn't help so much..it needs more love...or more rebuilds 
[05:35] <allee> \sh the external .la files pull in lots of deps :(
[05:36] <allee> \sh 'cause Tonio is not here. Is it okay to upload an updated wlassistant pkg to REVU?  (Tonio knowns I'm working on it)
[05:37] <\sh> why not :) I don't mind who uploaded what to Revu :)
[05:38] <allee> \sh 'k.  but first my son requires attention.  bbl
[05:46] <\sh> oh sometimes I'm really brainfcked
[05:46] <\sh> I should update my pbuilder at sometime
[06:05] <\sh> ok..libkexif 
[06:05] <\sh> gwenview is clean
[06:10] <\sh> libkexif is also clean
[06:13] <\sh> allee: ok..digikam can come..
[06:26] <\sh> Riddell: clean up done. 
[08:01] <Flosoft> hey
[08:01] <Flosoft> my kdesktop is always crashing?
[08:03] <|Flosoft|> hey again
[08:05] <gobbe> hey
[08:05] <pef> hoy
[08:06] <|Flosoft|> my kdesktop crashes constantly :S
[08:09] <\sh> how can that be?
[08:09] <\sh> hoary breezy dapper?
[08:09] <|Flosoft|> breezy with kde 3.5
[08:10] <\sh> hmm...I was running a long time breezy with 3.5 and no crashes...
[08:10] <|Flosoft|> there was an update of the packaga a few days ago ... and now it uses 70% ram and CPU
[08:10] <\sh> can you try the following: disable kdm/gdm/xdm whatever and start kde via startx 
[08:11] <|Flosoft|> ???
[08:11] <\sh> to do so, you have to add in ~/.xinitrc startkde
[08:11] <\sh> ok..step by step
[08:11] <\sh> 1. ctrl+alt+f1 to reach a text console
[08:12] <\sh> 2. log into the console
[08:12] <|Flosoft|> well via SSH is ok...
[08:12] <|Flosoft|> sudo su
[08:12] <|Flosoft|> and then?
[08:12] <|Flosoft|> vi?
[08:12] <\sh> what ssh?
[08:12] <|Flosoft|> logged in
[08:12] <\sh> no...ctrl+alt+f1
[08:13] <\sh> and you have your local text console
[08:13] <\sh> log into this text console
[08:13] <|Flosoft|> well remote console is easier to paste the commands ;)
[08:13] <\sh> you want have any X just now
[08:13] <\sh> so do it now..and configure irssi to connect to freenode :)
[08:13] <|Flosoft|> ok ... I am on the console
[08:13] <\sh> or write down the stepsa
[08:14] <\sh> ok when you are logged in 
[08:14] <|Flosoft|> I am
[08:14] <\sh> sudo /etc/init.d/kdm stop 
[08:14] <\sh> (if this is your login manager for X)
[08:14] <\sh> vi ~/.xinitrc
[08:14] <\sh> add "startkde" (without quotes) to this file
[08:14] <\sh> save it
[08:14] <pef> :wq
[08:15] <\sh> and then execute: startx
[08:15] <\sh> if the crashes happens as well, you will see on your console error messages
[08:15] <|Flosoft|> is it ok that xinitrc is an empty file?
[08:16] <\sh> yes..
[08:16] <\sh> you create it now
[08:16] <|Flosoft|> well it doesn't crash
[08:16] <|Flosoft|> I have to kill it 
[08:16] <\sh> what now..you explained, that your kdesktop is crashing
[08:16] <|Flosoft|> because the kdesktop uses too much ressources
[08:16] <pef> \sh: aren't errors logged using ~/..xsession-errors when using session manager ?
[08:17] <\sh> pef: modern stuff :) i don't trust it :)
[08:17] <|Flosoft|> it uses more than 70% of CPU and Ram
[08:17] <pef> old school way :D
[08:17] <pef> erf
[08:18] <\sh> well...why? do you have a big fat background picture? 
[08:19] <|Flosoft|> nope
[08:19] <\sh> strange
[08:19] <|Flosoft|> well I had a normal 1280x1024 jpg
[08:19] <\sh> did you try to kill it and start it manually?
[08:19] <|Flosoft|> but never had any problems with that
[08:19] <|Flosoft|> I killed it ... i'll try to restart it
[08:20] <pef> have you free disk space left ? (df -h)
[08:20] <|Flosoft|> yes
[08:20] <|Flosoft|> Dateisystem            Gre Benut  Verf Ben% Eingehngt auf
[08:20] <|Flosoft|> /dev/hda2              18G   11G  6,9G  60% /
[08:20] <|Flosoft|> tmpfs                 253M     0  253M   0% /dev/shm
[08:20] <|Flosoft|> tmpfs                 253M   13M  240M   5% /lib/modules/2.6.12-10-386/volatile
[08:20] <|Flosoft|> /dev/mapper/Server-Server
[08:20] <|Flosoft|>                       278G  216G   48G  83% /server
[08:20] <|Flosoft|> root@Ubuntu:/home/admin #
[08:21] <|Flosoft|> ok ... I logged in
[08:21] <\sh> ok..you killed kdesktop and restart kdesktop manually
[08:21] <\sh> is it increasing memory and cpu again?
[08:22] <|Flosoft|> this is after normal login
[08:22] <|Flosoft|> 14381 admin     18   0  857m 346m 191m D  6.8 68.7   0:18.10 kdesktop
[08:23] <\sh> ok..any possibilty to test dapper on the same machine? i don't think it's a kdesktop problem
[08:23] <|Flosoft|> ow ... I see the error
[08:23] <|Flosoft|> Invalid entry (missing '=') at .....
[08:23] <|Flosoft|> how can i fix this?
[08:24] <\sh> hmm?
[08:24] <\sh> but this shouldn't eat the memory
[08:24] <|Flosoft|> well it does
[08:24] <|Flosoft|> there are millions of messages
[08:25] <|Flosoft|> always the same file with a different :
[08:25] <\sh> which file?
[08:25] <|Flosoft|> one sec ... i'll post a part
[08:25] <\sh> ah do it on pastbin
[08:25] <|Flosoft|> yes
[08:26] <|Flosoft|> ID: 505695
[08:26] <|Flosoft|> http://kubuntu.pastebin.com/505695
[08:26] <|Flosoft|> this is just a part
[08:27] <\sh> delete the file :)
[08:27] <\sh> and check again :)
[08:27] <|Flosoft|> ok ...
[08:28] <|Flosoft|> works :)
[08:28] <|Flosoft|> i'll just restart kde
[08:28] <\sh> now, how did you create this .desktop file?
[08:29] <|Flosoft|> i think the installer did it :S
[08:29] <|Flosoft|> or no ... I did it
[08:29] <|Flosoft|> with KDE
[08:29] <|Flosoft|> u know ... right click
[08:29] <|Flosoft|> shortcut to prog
[08:29] <|Flosoft|> wohoo ... I got a desktop :)
[08:30] <\sh> ok...try to reproduce your steps towards this .desktop file
[08:30] <\sh> and check again if this happens again
[08:31] <|Flosoft|> ok ...
[08:31] <|Flosoft|> I created the file
[08:31] <|Flosoft|> just going to log in again
[08:32] <|Flosoft|> works fine
[08:32] <\sh> then it was a glitch in the matrix
[08:32] <|Flosoft|> hehe yes
[08:33] <|Flosoft|> thx anyway for the help
[08:34] <|Flosoft|> has anyone used 3ddesktop?
[08:34] <|Flosoft|> ow ... and please ... when will there be the KVIRC 3.20 for breezy?
[08:36] <|Flosoft|> or maybe more important ...
[08:36] <|Flosoft|> how do I fix: hdparm -d1 /dev/dvd      that it enables on every boot?
[08:36] <\sh> |Flosoft|: you can adjust hdparm.conf in /etc
[08:37] <|Flosoft|> ok thx
[08:37] <\sh> |Flosoft|: if you are sure, that everything is working 
[08:37] <|Flosoft|> well it is when I add it in the console
[08:38] <|Flosoft|> so I just add: hdparm -d1 /dev/dvd    to the file?
[08:38] <\sh> no
[08:38] <\sh> |Flosoft|: man hdparm.conf
[08:39] <|Flosoft|> nothing found
[08:39] <\sh> uhm?
[08:39] <\sh> should be there
[08:39] <|Flosoft|> nope
[08:39] <|Flosoft|> empty
[08:39] <\sh> ok
[08:39] <\sh> put 
[08:40] <\sh>  /dev/hdc {
[08:40] <\sh>      dma = on
[08:40] <\sh> }
[08:40] <\sh>  /dev/hdc is normally your dvd/cd drive, right?
[08:40] <|Flosoft|> I thought it is /dev/dvd/
[08:41] <KaiL_> \sh, that manpage is missing here too - maybe a bug? ;)
[08:41] <\sh> |Flosoft|: /dev/dvd is an alias normally
[08:41] <\sh> KaiL_: breezy?
[08:41] <KaiL_> jup
[08:41] <\sh> hmmm..
[08:41] <|Flosoft|> yep
[08:41] <KaiL_> works for you?
[08:41] <\sh> then it is a bug, because on dapper it's there :)
[08:41] <|Flosoft|> well I'll try
[08:42] <\sh> |Flosoft|: less /etc/hdparm.conf there is a documentation in there
[08:42] <KaiL_> might be, I'm to lazy to boot the test Laptop
[09:06] <jjesse> from friday's daily build to today why are there some many updates of kubuntu?
[10:54] <Flosoft> hey
[10:58] <Flosoft> why is kaffeine constantly crashing with Xine?
[11:02] <LaserJock> Flosoft: have you looked for a bug report?
[11:02] <crimsun> additionally, please provide more precise context
[11:19] <Flosoft> well I use the xine engine
[11:21] <Flosoft> here is the crashmanager output
[11:21] <Flosoft> http://kubuntu.pastebin.com/505956