[00:02] Riddell: can we move plasma-widget-kimpanel-backend-scim into universe? === nhandler_ is now known as nhandler [00:04] * ryanakca sighs and wonders why it all the lucid packages appear unsigned / untrusted to aptitude [00:04] freeflying: yes but the source (kdeplasma-addons) is in main so scim-dev needs to be in main to compile against it [00:09] hi ryanakca [00:10] did you see my posts above? [00:10] bug 520408 [00:10] Launchpad bug 520408 in kubuntu-ppa "Deadkeys won't work in KDE applications after today's update (KDE 4.4 packages)" [Undecided,New] https://launchpad.net/bugs/520408 [00:10] this problem is so confusing [00:10] neversfelde: I can add it to the current one now [00:10] cool [00:11] I did not use the current one for 4.4, because the news for 4.4 rc2 was different [00:13] Riddell: ok, then drop scim's backend, since scim's non-maintainace in upstream [00:13] neversfelde: ... and done, feel free to check :) [00:13] (if it's to your liking) [00:13] freeflying: ok I will try and drop the scim backend [00:14] freeflying: do you have any thoughts on https://launchpad.net/bugs/520408 ? [00:14] Ubuntu bug 520408 in kubuntu-ppa "Deadkeys won't work in KDE applications after today's update (KDE 4.4 packages)" [Undecided,New] [00:14] ryanakca: I'll do tomorrow. Can I improve the templates, if I have admin access? [00:15] I'll never test [00:15] err I nevere tested [00:15] neversfelde: Yes, go to /admin/ ... then It's under "Content Types" (left column, towards the top, I forget the header)... Then click edit for the PPA content type. [00:16] k [00:18] Riddell: Is Ng out of the office again this week? [00:18] (or is it just that he never checks his IRC client...) [00:22] JontheEchidna, freeflying: works on RC2, updating to final 4.4.0 and will test [00:23] Riddell: yuuup, that is a good solution IMO, scim was bad even in KDE 3 :> [00:24] I recall it causing problems early on in intrepid, even though I never used it in my life [00:28] Riddell: did we get all this rebuilt agaist qt-4.6.1? [00:29] Quintasan: rc2 used previous qt release, right? [00:29] freeflying: I belive yes [00:29] That's why I'm updating :) [00:29] Quintasan: ok, ibus-qt might not be rebuilt, and also libicu [00:42] lol, kubuntu_104_kdm_active_vt_plymouth.diff made it in to the karmic backports [00:44] mhh [00:45] fixing [00:46] I forgot to drop maybe, but I wrote in changelog :) [00:46] lol [00:46] I am off till tuesday, gn8 [00:46] JontheEchidna: well, sometimes I can make a mistake, I'm not a bot :) [00:47] you are doing a lot of work. I wish I could do more, but with school... [00:48] no problem :) [00:48] ...and I almost uploaded ~ppa4 with lucid in the changelog entry :D [00:49] good :D [00:50] 11 MB diff.gz O_o [00:52] because ethais.tar.gz.uu is 14.9 MB [00:52] v.v [00:57] blah, I guess it does really need pkg-kde-tools 0.6: http://launchpadlibrarian.net/39080222/buildlog_ubuntu-lucid-i386.kaffeine_1.0~pre3-1ubuntu1_FAILEDTOBUILD.txt.gz [00:57] but it pbuilt fine. how was I supposed to know it'd fail in the buildd? :( [01:01] You can't. Try to build and fix in a ppa :( [01:04] JontheEchidna: drop --parallel [01:05] It's a feauture of pkg-kde-tools 0.6 I think [01:09] at worst I think that flag would just be ignored [01:11] I'll throw up a ppa build to test, though I don't know if pkgbinarymangler would get run even in -ninjas [01:12] freeflying: still works after update [01:13] maybe becuase en_GB uses XIM [01:13] hmm [01:13] still polish [01:13] wtf [01:21] Quintasan: well, I checked ibus, they had support deadkey in ibus-qt [01:42] hmm, konversation just failed with a similar error to kaffeine's... http://launchpadlibrarian.net/39082166/buildlog_ubuntu-lucid-i386.konversation_1.2.2-0ubuntu1_FAILEDTOBUILD.txt.gz [01:42] guess that rules out pkg-kde-tools being too old, pkgbinarymangler is just screwed' [01:47] psst, on lifehacker, they are voting for best netbook os...Kubuntu Netbook has 2 thus far, we need more :) [02:11] wow looks like a bunch more updates hitting kubuntu/packports or something [02:14] should hopefully fix the kdm issues [02:15] JontheEchidna: what did you do for that? [02:15] Riddell: remove the plymouth "don't blank screen" patch [02:16] aah [02:23] wtf, why for the past few days, on doing an upgrade in karmic, my system dies? ie. kde doesn't seem to crash, as there is no error messages anywhere, nothing seems to crash that I can find....this time I caught it, and lzma was tanking the system...the systems goes out to a non-gui tty7, where I have to go to another tty, log in, and start kdm === dendro-afk is now known as dendrobates [02:23] checked sys temps when it happens, 50c, not bad, as I can get it up to 80c when building with all cores [02:24] * nixternal goes and eats [02:24] hi guys .. i cant run my kopete after upgrade to 4.4 .. error : unable to run dr konqi [02:24] any idea [02:25] ? [02:26] sounds like its crashing [02:26] yups [02:28] after the last update i now have duplicate everything on the desktop, task bar, plasmoids on the desktop, etc === dendrobates is now known as dendro-afk [02:54] hi all, need some help here, this patch I created keeps on saying patch malformed at line 79: http://paste.ubuntu.com/374390/ what's wrong with it? I am pretty sure the patch is right because bzr created it [05:30] Seems like kdm 4:4.4.0-0ubuntu2 stops the kdm service when upgrading. Intentional? === dendro-afk is now known as dendrobates [07:06] * apachelogger hugs sebas_ for having the same nepomuk search issue :) [07:22] oh oh oh [07:22] ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh [07:22] sebas_: I think I found the cause => silly kubuntu devs ;) [07:25] trying [07:41] yay [07:43] anyone with lucid around? [07:59] apachelogger: with lucid netbook [07:59] allee-k__: can you please run apt-cache rdepends shared-desktop-ontologies [08:05] apachelogger: no rdepends listed [08:05] kthx === allee-k__ is now known as allee-k === Quintasan_ is now known as Quintasan [08:19] \o [08:20] o/ [08:23] so [08:23] something needs to depend on shared-desktop-ontologies in both lucid and karmic [08:23] I just dont know what [08:29] apachelogger: nepomuk-* I assume [08:29] there are such packages? [08:30] seems the most low-level dep is in kdelibs so I suppose kdelibs5 should dep the ontologies [08:33] apachelogger: just checked and found nothing. So maybe soprano-daemon, or even the libsoprano4 ? [08:34] allee-k: I am not sure soprano depends on it [08:34] neversfelde: \o/ your rebuild fixed my problem [08:34] I am thinking [08:34] apparently debian is splitting kdelibs into subpackages [08:34] Nightrose: good :) [08:34] (which I find a good idea, other than the maintenance overhead that creates) [08:34] so in the long run there should be some nepomuk library [08:35] apachelogger: maybe kdelibs5 is not the 'perfect' choice, but it will do what is 'needed' [08:35] and that library would at the very least need to depend on the ontologies [08:35] allee-k: that for sure [08:53] hm, debian does not depend on it either :S [09:08] hi, just upgrade my lucid machine this morning, and virtuoso is asking me to set passwords for a "dba" and "dev" user! is this also going to happen for regular installs? [09:09] feels like failure to me :/ [09:10] unlikely [09:10] we only depend on one virtuoso package IIRC [09:10] and that does not have global setup stuff [09:11] not sure I get what you mean [09:11] will users be prompted to set up passwords for those "users"? [09:12] nope [09:12] agateau: I am not sure on that though [09:12] ok [09:13] * apachelogger is not on lucid and far away from getting access to a lucid machine :) [09:13] I just answered the prompt in a "user" way: pressed enter until debconf dialogs were gone :) [09:13] will see if it's enough [09:13] agateau: I've upgraded rightnow and virtuoso asked me nothing [09:14] allee-k: strange [09:14] maybe I have a package installed which is not part of the default install [09:14] agateau: here on virtuoso-nepomuk and -converter is installed (dpkg -l \*virtuoso* [09:15] s/on/only/ [09:15] mmm [09:15] I have a virtuoso-server here [09:15] could be the reason [09:16] and some virtuoso-opensource-6.0* packages as well [09:16] * agateau tries to remove them [09:17] I was able to uninst the virtuoso-server, but not the virtuoso-opensource-6.0* packages [09:17] (as it would have uninst virtuoso-nepomuk) [09:18] I guess getting the server out will fix it anyway [09:41] jussi01, tsimpson: a bit of vim would be nice on firefly :) [09:41] I want this: http://shop.canonical.com/product_info.php?products_id=602 [09:43] ulysses: select quantity and press add to chart [09:43] apachelogger: installed [09:43] tsimpson: thanks :) [09:43] apachelogger: :) [09:59] my kopete still crashing after upgrade to 4.4 ... any idea ? [09:59] unable to start dr konqi [10:16] the 4.3.5 backport got some "interesting" file locations [11:50] hi [13:08] Karmic 4.4 upgrade bug: klipper (karmic) in 4.4 and kdebase-workspace-data 4:4.3.5-0ubuntu1~karmic1 both contain /usr/share/kde4/apps/kconf_update/klipper-kconfigxt.upd [13:09] hi! strigi 0.7.2 want's to get packaged (fixes at least one crash for me) [13:09] ^^ so klipper needs a Replaces: kdebase-workspace-data (<<4.4.0) AFAIU [13:56] allee-k: gah, it was moved in lucid with 4.3.3 (but in karmic 4.3.5 it is still not moved), that is why the replaces doesn't work [14:00] a|wen: Heh, Fun with forgotten backports :) Will you backport 4.3.3 change? Or should I add a lp bug so it does not get forgotten. [14:01] allee-k: committed to bzr, so should be fixed next time someone uploads kdebase-workspace [14:02] a|wen: thx!!! I'll paste in #kubuntu too [14:02] a|wen: needs manual backport to karmic [14:03] apachelogger: necessary to move it in karmic backports? === dendrobates is now known as dendro-afk [14:03] no, the ppa [14:04] current karmic builds do not receive uploads from bzr stuff [14:04] so that fix would only get landed with 4.4.1 [14:04] not necessarily but most likely [14:04] apachelogger: ahh, sure; that backport [14:06] * a|wen goes fixing that while i actually have a fast connection [14:07] FYI todays update from ppa again killed my x session [14:07] I think it was while setting up kdm. it was the last thing i saw before the blackout === dendro-afk is now known as dendrobates [14:15] binarylooks: same here [14:15] oh my [14:15] but no idea where it was [14:15] a|wen: thx [14:15] somehwere configuring i think [14:16] I read an anrgy comment from nixternal somewhere about the same :-) [14:16] Nightrose: prolly postinst script [14:16] possibly [14:16] Also, I still get groovy colors on my tty1-6 [14:17] this I also heard several people in kubuntu complaining of [14:17] had that as well but it's gone now [14:17] i upgraded from RC3 btw [14:18] Nightrose: me from rc2 in the backports ppa (there never was a rc3 in the ppas?) [14:18] ehh... 2 i mean [14:18] sorry [14:19] hmmm, no updates and still flower power on the terminal [14:19] heh [14:19] ok - gotta go run some errands [14:19] good day [14:25] binarylooks: how did you upgrade? using aptitude or kpackagekit? [14:25] apt-get [14:26] a|wen: ^ [14:28] binarylooks: strange ... uses some debconf fun to ask if it should restart if kdm is running; i suppose you never saw that? [14:29] a|wen: i remember the debconf question when i updated a few days ago. i chose the default answer [14:29] should I try reinstalling kdm (are the colors related to kdm at all?) [14:30] binarylooks: looks to ask if you want to kill kdm (this has only something to do with the restarting) [14:31] allee-k: FYI fixed in 4.4.0 in the karmic backports ppa as well [14:32] a|wen: ok, he probably asked but i never saw it. i have to do a dpkg --configure -a on restart, but there's no question anymore [14:34] binarylooks: after asking the question it should be reset so it will ask again next time you upgrade [14:35] a|wen: didn't happen. I think it happened three times in the last 2 days [14:36] a|wen: anyway, it's easy solvabla, just very shocking [14:37] hey folks [14:38] Does kdebase in lucid still require kdebase-workspace or can I update the dependency graph (re: discussion in #debian-qt-kde)? [14:38] #akonadi tell me that people are reporting apparmor problems with mysql as used by akonadi on kubuntu with kde 4.4 [14:38] is that true? [14:40] binarylooks: well, killing your X might very well kill some of your data too ... so the heuristics for restarting should be changed a bit if many people have problems with them [14:40] a|wen: right you are [14:41] wstephenson: my akonadi works perfectly in kubuntu with 4.4 (though i'm not a developer) [14:41] wstephenson: I've seen it on #akonadi. But up to now I only found mysql system table errors. Maybe I will have this problem later. dunno [14:41] binarylooks: but you think that the question came up all the last times it killed your X? [14:42] binarylooks, allee-k: had you previously fixed apparmor or uninstalled it? i want to know if it works for kubuntu out of the box [14:42] a|wen: well I didn't kill X, it killed itslef and the last words I saw were ....kdm....black [14:42] wstephenson: no apparmor here, never [14:42] wstephenson: so out of the box was ok [14:42] binarylooks: but did you get a debconf question as part of the upgrade? [14:43] binarylooks: ok, your info is not useful since apparently some people do have it. [14:43] wstephenson: never did anything with appamour. never had problem. But to day after 4.3.5 -> 4.4 upgrade mysql, akonadi problem show up [14:43] a|wen: not before the blackout, and not after. i remember a debconf question when i upgraded yesterday morning. no blackout at that point [14:43] wstephenson: still trying to understand what going on [14:44] wstephenson: sorry for that [14:44] allee-k: the old apparmor mysql problem was that the ubuntu mysql is configured only to allow the mysql process to access files in the system location. akonadi saves files in ~/.local. therefore boom. [14:44] binarylooks: hmm; so either the "detect kdm is running" or the "lets ask the user" part is broken... that leaves some more investigation to do [14:45] Anyway, need to go now. off to heidelberg... [14:45] * a|wen runs out as well === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [14:45] a|wen: goog luck with the investigation, nixternal had the same problems [14:45] binarylooks: thx [14:46] wstephenson: I remeber it. but 4.3.5 worked so should 4.4 (from appamor POV). Mhmm, Root of my problem seem to be: http://pastebin.com/m26cc2e94 [14:47] then akonadi fails: http://pastebin.com/m7bed4161 [14:48] hi there [14:48] hello [14:48] wstephenson: hi [14:49] wstephenson: I was just playing with the network management plasmoid, and noticed it should be about to work, right ? [14:49] allee-k: this should fix those ERRORS : "mysql_install_db --datadir=$HOME/.local/share/akonadi/db_data/akonadi" [14:49] Tonio_: it's still not released. [14:49] wstephenson: oh oki [14:49] sebas and i are going to work on it at the plasma sprint in 2 weeks time [14:50] wstephenson: we shouldn't include it in the package then.... [14:50] Riddell: should I exclude the files from there ? I see no point including something that won't work anyway [14:50] Tonio_: hi [14:50] Tonio_: no, that's why i package it separately to knetworkmanager [14:50] wstephenson: sure, the point is that the plasmoid gets installed anyway [14:53] Riddell: should we ship with plasma-widget-networkmanagement by default ? [14:53] Tonio_: you mean people install it manually, or it gets installed along with something else? [14:53] wstephenson: kubnutu-desktop recommends it [14:53] so it'll get installed by default [14:53] wstephenson: no problem with people installing manually [14:54] mhmm, mysql_install_db is in mysql-server-5.1 not in mysql-server-core-5.1 that is installed by KDE dependencies [14:54] wstephenson: installed by default is a problem, since it'll be proposed from the systray options for exemple [14:54] Tonio_: i think kubuntu-desktop should recommend knetworkmanager until we do a release of the plasmoid [14:54] "proposed from the systray options"? [14:54] wstephenson: I totally agree :) [14:54] wstephenson: as a plasmoid you can include in it [14:55] ah i see what you mean [14:55] wstephenson: check in "system tray settings" [14:55] kk [14:55] thought you meant at pkg resolver level. [14:55] ah ! nope :) [14:57] allee-k: it's in the main mysql package on opensuse... [14:57] use your command-not-found tool [15:01] wstephenson: the only thing is,do you expect to release before lucid comes arround ? [15:01] wstephenson: in that case I can help on the testing side... I have a bunch of corp wireless access to test mschap authentication, vpn access and so on [15:02] Tonio_: when does lucid freeze? [15:03] wstephenson: 02/18 for the feature freeze, but I think and exception can give us up to 03/04, the user interface freeze [15:03] Tonio_: the important thing to remember is that the plasmoid is only a GUI. the real logic is shared between KNM and the plasmoid. [15:03] so any functional testing helps both [15:04] wstephenson: yep, I know that :) [15:04] Tonio_: the plasma sprint starts on feb 19th until 25th [15:04] we'll be heavily hacking the UI then [15:05] wstephenson: so I can help for knetworkmanager right now and we'll see for the plasmoid and decide then if we include it by default and hide knetworkmanager or not [15:05] wstephenson: sounds a good plan [15:05] wstephenson: I'll have to play with openvpn tomorrow, I'll give you some feedback [15:06] Tonio_: use the Network Management component in bko [15:06] wstephenson: yup [15:07] hum who has some policykit knowledge here ? [15:07] kcmshell4 kcm_pkk_authorization seems to be incomplete (to say the least...) [15:14] http://toniox.org/temp/powerdevil.png [15:14] hum nasty bug !!!!!! [15:21] Tonio_: i think JontheEchidna was saying that kcm is for the old policykit and will be dropped [15:21] already dropped, with the latest updates [15:21] Tonio_: btw, the issue with kauth apps not working is fixed with 4.4.0 [15:21] kde rev 1086506 [15:21] http://websvn.kde.org/trunk/?rev=1086506&view=rev | svn://anonsvn.kde.org/home/kde/trunk -r 1086506 [15:22] JontheEchidna: okay so you are aware and checking for update :) fine [15:25] a bit unfortunate about the loss of the KCM, oh well [15:25] anyone packaging rekonq ? I can go for it but do we want a beta release ? [15:29] I don't think anybody's asked upstream if they plan on releasing before its too late yet. If I was packaging it I'd ask first. [15:30] Nightrose, nixternal: found the issue with kdm getting restarted [15:30] trying to find a most appropriate fix [15:30] * JontheEchidna has flashbacks to karmic when kdm got restarted during the upgrade === pgquiles_ is now known as pgquiles [15:37] extragear tarballs are up. I think I'll take konq-plugins for starters [15:37] ftp://ftp.kde.org/pub/kde/stable/4.4.0/src/extragear [15:46] is there a karmic version of kcm-touchpad? [15:48] JontheEchidna: hey dude :D [15:48] seele: No, but I can make one easily enough. I'll get it done today [15:48] dantti: hi [15:49] JontheEchidna: no rush, but i see i have a todo on the UI [15:49] JontheEchidna: I saw you started hacking on it :P did it work ok for you? [15:49] dantti: I've not had to print anything yet :P [15:49] since I was hacking at my dad's office, I thought it best not to waste paper [15:50] JontheEchidna: right, that's why i have dummies printers :P [15:51] \o/ http://websvn.kde.org/?revision=1089160&view=revision \o/ [15:52] JontheEchidna: yeah, I also seem to remember that I fixed that bug at least once :P [15:53] dantti: I am curious though, what approach do you think would be best to launch the queue UI from the tray icon? KToolInvocation? DBus? (I saw some commented stuff from the KPackageKitD) [15:57] JontheEchidna: yup, I copied some files from KPackageKit since I know the code and the ideas are a bit the same [15:58] JontheEchidna: my idea is for kded process to show the knotificationIcon, if the user clicks on it, it will call via DBus the org.kde.PrintQueue ShowQueue(destName) [15:59] this way both kcm and kded can call the queue showing only one queue [15:59] as that is a kuniqueApp [16:00] are you writing a c++ print utility tray icon? *rubs hands* [16:00] the commeted code is what i would call, actually my fist approach was to start an application to show the icon whan i saw a new job, but i think putting it in kded is better [16:01] wstephenson: yup, what "rubs hands" means? [16:01] wstephenson: faith is not that nice :P [16:01] JontheEchidna: do we haz bug report for kdm going down on upgrade? [16:01] apachelogger: glancing over the bugs list I think there's a mis-filed one that could be it [16:01] mis-filed, as in apachelogger wouldnt find it :P [16:02] mm, different issue but still needs to be fixed [16:02] dantti: it means i like the sound of it [16:02] wstephenson: playground/base/print-manager [16:02] wstephenson: ah right, hehe take a look http://dantti.wordpress.com/ [16:03] funny some people are hating and others are loving the ui :P [16:04] i'm taking a look [16:04] dantti: I've been meaning to ask you; what's the best way to file aptcc bugs? [16:05] JontheEchidna: via commits I suppose ;) [16:05] report and fix all nice bundled up :D [16:05] * apachelogger does that now [16:05] lol [16:05] JontheEchidna: well, you can send then to packagekit mailing list [16:06] I thought there wasn't many users of that... [16:06] was wondering, since the packagekit bugzilla didnt' have an aptcc product [16:06] I used it every day som once in a while i find a bug.. [16:06] JontheEchidna: yup i should ask for that since it's now more production ready.. [16:06] http://bugs.freedesktop.org/show_bug.cgi?id=26357 [16:06] Freedesktop bug 26357 in General "Second letter of some words in package descriptions is "-" instead of "o"" [Normal,New] [16:08] oh here's a thing. will kubuntu have ubuntu one integration? [16:08] JontheEchidna: hmm i have to look if that's not what i did when i changed the code that formates the description [16:08] with feature parity to the gnome stuff? [16:08] JontheEchidna: http://bazaar.launchpad.net/~kubuntu-members/kdebase-workspace/ubuntu/revision/280 [16:08] the apt does not have this bug as it display as it is [16:08] it's like apt-cache show foo, but aptitude show foo is much better [16:09] but aptitude code is quite complicated to understand [16:09] JontheEchidna: the problem was that neversfelde added the debhelper place holders, making dh_installinit active, which by default stops a daemon upon upgrade and starts it once done [16:09] aah [16:10] wstephenson: were you talking about aptcc? (feature parity and such...) [16:11] dantti: no, ubuntu one. kioslaves for file sync to it, kconfig backends for ubuntuone, etc [16:11] dantti: what's aptcc? [16:11] JontheEchidna: yup i can see the bug here, i think it's best to revert my patch, it didn't work :P [16:12] wstephenson: it's a c++ alternative for the python apt backend for packagekit [16:12] aha [16:13] wstephenson: the larger part of ubuntu one work is a kded module [16:13] apachelogger: it needs an always-on client? [16:14] the idea is that everything interface of ubuntu one is desktop agnostic, so kconfig integration would be not necessary [16:14] wstephenson: a daemon [16:14] or a single point of contact [16:14] yeah [16:14] my concept was to write a kded module to interact with the ubuntu one daemon, that way not each kioslave instance needs to register via dbus etc. [16:16] this is an area where gio has the edge over kio, it can reuse processes better. [16:16] [16:20] JontheEchidna: uploading fix to backports ppa [16:21] apachelogger: i was thinking about doing a native dropbox client for kde [16:21] and wondering if there is anything worth sharing [16:21] I do not think dropbox and ubuntu one are much alike [16:22] perhaps have a single cloud ioslave with backend specific kded modules [16:22] the better part of ubuntu one is realy syncing of contacts and notes and whatnot [16:22] no? [16:22] wstephenson: that possibly makes sense [16:22] apachelogger: just to keep things tidy from users' POVs [16:22] IMHO frank should just roll a cloud storage solution we can use ;) [16:22] wstephenson: yeah, makes sense [16:24] apachelogger: what issue with kdm getting restarted? [16:24] apachelogger: well it seems till and co started on a simple couch resource for akonadi [16:25] heya [16:25] that's the notes/contacts side of things in ubuntuone isn't it? [16:25] wstephenson: right [16:25] any reason we're still launching some kcm modules with kdesudo? [16:25] bookmarks, just about anything really ;) [16:25] isn't KAuth supposed to take care of that? [16:25] morning [16:25] smarter: yes because python is the drag [16:25] nixternal: just updated for me and kdm restarted as well [16:25] and the gnome part of the python drag is even more the drag [16:26] jjesse: restarted or just died out? [16:26] bookmarks would be nice [16:26] mine doesn't restart, it died out to tty7, then I have to go in to tty1-6, sudo dpkg --configure -a, then sudo start kdm [16:26] apachelogger: you mean, kcm modules written in python? but that's not the case of the KDM one [16:27] wstephenson: as I understand it, if they get the couchdb stuff working ubuntu one can sync just about everything that is storable in akonadi [16:28] amongst other things bookmarks ;) [16:30] howdy. anyone else seeing weirdness with 4.4's kmail? http://people.ubuntu.com/~maco.m/screenshots/kmail_transparent.png that progress bar popup thingy is hard to read with a transparent background... [16:31] apachelogger: what did you do to figure out that kdm was the problem during upgrades? I have checked all of my damn logs and didn't find a thing that pointed to KDM [16:31] maco2: which metro line are you closer to red or green? [16:31] seele: green [16:31] i live on the green line [16:31] what I noticed while upgrading was: the system would slow to a halt, kdm would bomb, I would be left stairing at tty7 messages [16:32] nixternal: only kdm can kill the X ;) [16:33] nixternal: when i logged out after upgrading so that i could login to a nice 4.4 session, kdm bombed out to tty7, but sudo service kdm restart worked fine [16:34] hrmm, I never had the problem while logging in, only while doing 'apt-get upgrade' [16:34] it would start unpacking stuff and then bomb out [16:35] maco2: sudo start kdm <- no need for service, unless of course you are studying for LPIC-1 [16:35] what the fuuuuuck.. turbotax isnt working in firefox [16:35] firefox is not working in firefox :P [16:35] sry :) === dendrobates is now known as dendro-afk [16:36] nixternal: im somewhat used to centos when it comes to starting/stopping services. my last two jobs have involved lots of centos [16:36] figured as much, as I was about to make a red hat reference, but held myself back :) [16:38] seele: system compatibility check for turbo tax? [16:38] they are probablly checking the browser? [16:40] no, they are checking the OS [16:40] as Firefox is on their list of recommended browsers [16:40] shit, might help if I use firefox though and not chromium :) [16:40] is firefox returning firefox version X on linux though? [16:40] the UserAgent is returning that it is running on linux? [16:41] it is working for me :) [16:44] smarter: the KDM config module hasn't been ported to KAuth yet :( [16:45] bye folks. [16:45] Hi JontheEchidna, in kubuntu-notification-helper/debian/control, your name is wrongly typed in XSBC-Original-Maintainer, if you want to fix.. [16:47] EagleScreen: XSBC-Original-Maintainer is correct [16:47] oh, my name :D [16:47] haha [16:47] i see Jonthan and not Jonathan [16:48] thanks [16:48]