[00:03] picatchu: What do you mean not working? [00:09] ok... dselect upgraded by kde today to kde 4.2 - since then, hotkeys are no longer working. Error message: "Failed to contact the KDE global shortcuts daemonMessage: No such object path '/KdedGlobalAccel' Error: org.freedesktop.DBus.Error.UnknownObject" ... thought developers might be interested/also have seen this [00:11] picatchu: We're in the middle of backporting KDE4.2. Disable backports and downgrade your kde4libs [00:11] Currently from backports you'll get a mix of 4.1 and 4.2 and that's not going to have a happy ending. [00:12] Err, from backports you get a partial 4.2 and so you end up with a mixed system. [00:14] I see, thanks! This might also explain the phonon-backend-xine bug (331779)... [01:10] :/ [01:11] Quintasan: hey === rgreening_ is now known as rgreening [01:13] ScottK: When did you want be to post the story? [01:14] rgreening: hiho [01:14] rgreening: btw, thanks for your work on Qt 4.5... it rocks [01:16] np. I actually like working on the qt package. I think I'll keep that one :) [01:25] JontheEchidna: do you remember the commandline option for changing the qt rendering engine to opengl? [01:32] quiet for a friday. [01:34] ya. playing cards with friends here. Great game called wizard. pick it up :) [01:44] hmm, did I miss anything? [01:45] so Riddell: I have openened a very scary can of worms... [01:45] slimey worms? [01:45] tracking down the blurry icon clipping in ksplash :) [01:45] oh very... [01:46] I may loose a limb [01:46] oh ksplashx is quite limited as an app since it's pure X with no KDE or Qt, so the artwork has to work around the technology quite a lot [01:47] yea...but I don't get why it doesn't use qt [01:47] like they have copies of the qt headers and source [01:47] and use those [01:47] and not the actual libraries [01:47] from the system [01:48] the whole point of a splash is to be shown while the rest of the desktop is loading up, if you have to load qt and kde just to show the splash that's half the time gone already [01:48] I see [01:48] but you don't have to load qt? .. [01:49] you can just call the functions...which seems like what they are doing..maybe not [01:49] ksplashx doesn't I believe [01:49] it uses its own copies of them [01:49] everything is compiled in...maybe that increases the time [01:49] ldd /usr/bin/ksplashx not much linked there [01:49] *or decreases i mean [01:49] right [01:49] interesting... [01:50] it only links against X libraries and those are already loaded by KDM [01:50] gotcha [01:50] so starting ksplashx doesn't need to load anything except itself [01:50] thats good to know..now I know why it is like that [01:54] oh my Riddell is up late [01:54] * seele if falling asleep 5 hours behind [01:59] rgreening: --graphicssystem opengl? [02:00] rgreening: I'll just leave compiling for the night :S [02:02] There is also bug with resizing panels (the desktop goes black and restarting plasma is needed) but I will do that tomorrow [02:03] that'll be fixed in KDE 4.2.1 [02:03] not caused by Qt 4.5 btw [02:04] JontheEchidna: hmm, so no need to do this? [02:04] well, no harm in having the fix a bit early I suppose [02:05] ryanakca: I'm waiting for slangasek to say when. [02:12] ScottK: did you want the story to have a link to the wiki page, or will the contents of the wiki page be emailed out (link to the message on the list archives), or did you want all the contents of the wikipage in the news blurb? [02:13] I was thinking New article link to that, either on the wiki or somewhere more permanent [02:13] I'd also figured on mailing something out. [02:13] Currently 33 mirrors have switched over to the new CD image. We need to get to 40 to through the swtich officially, so we are waiting. [02:15] ScottK: If you want to mail it to Kubuntu-devel (and CC kubuntu-users / whoever ?), I'll stick in a ``Click here for the full announcement'' [02:16] I think it'd be better to link onto the web site, myself. [02:16] ScottK: OK, I'll copy over the announcement to www.kubuntu.org :) [02:18] Is there anyone around who is a moderator on kubuntu-users? [02:48] ScottK: I may be one , can't remember [02:48] * claydoh looks [02:48] Thanks. [02:52] ScottK: if I am , I don't know the admin password :) nightrose is one, iirc [02:53] OK. I'm not subscribed, so when I get to push the release announcement I'll need someone to let it through. [03:13] evening [03:14] hola [03:14] its a nixternal! [03:14] I have hip-hop and classical going at the same time here at the bug jam [03:14] yikes! [03:15] what's up with that [03:15] I can't access the u-u-s queue [03:17] nevermind, got it [04:53] on a *very* fresh kubuntu install (net install about 6 hours ago), on first boot, i cannot log in. i get an ugly window that says "kstartupconfig4 does not exist or fails. The error code is 3. Check your installation." [05:03] maco, was this after adding plasma widgets to the panel? like quicklaunch? [05:03] jesus [05:03] it has taken me hours [05:03] and some to my stupidity [05:03] but I have finally (minus one very very small gitch) fixed the blurry icon bug [05:03] on ksplash [05:03] shtylman: awesome [05:04] rgreening: first boot [05:04] rgreening: didn't even reach the desktop [05:05] :( [05:07] maco: try loging in again. I had this a while back when I was first testing Qt4.5 (early snapshot). Logging in twice got me in. However, with qt4.5.0 rc1, that problem is resolved. not surte why you see it. [05:07] rgreening: already rebooted and tried again. same thing. [05:07] i can't log out and back in because well...it hasnt loaded far enough to get to a log out button [05:08] maco. dont reboot. login, let it fail. try again. second time seemed to work (when I had it) [05:09] CTRL-ALT-BS [05:09] ? [05:09] i havent enabled c-a-b on that machine yet [05:09] oh, maco, is kdm greet whats crashing? [05:09] does restarting kdm count? [05:09] what do you mean? [05:09] the login screen [05:10] no kdm came up fine [05:10] thats kdm greet [05:10] and i logged in, and then....the desktop won't load and it gives that error [05:10] check and see if you have kdebase-workspace-4.2.0-0ubuntu6 [05:10] or 5 [05:10] 5 is broken. 6 has a required fix [05:11] 6 [05:12] (the install actually just finished an hour ago because it was sitting there waiting for me to come home and tell it that my bios is set for utc. i really wish the net disk asked everything first like ubiquity) [05:16] rgreening: does logging out and in by restarting kdm count? [05:18] sure [05:19] did you check the version of kdebase-wrokspace? [05:19] ubuntu6 [05:20] strange [05:20] ok so after a /etc/init.d/kdm restart, now i get a spinner cursor on a black background, and no actual kdm [05:20] kill kdm [05:20] then start it [05:23] what signal? [05:23] or do you mean stop the service? [05:23] oh er [05:23] i cant vt switch with it doing this [05:25] rgreening: ^ [05:26] hmm... [05:26] i can't decide if "spare laptop can't login" or "main laptop's workspace switching shortcuts don't switch workspaces" is the more annoying/pressing bug i've got in kubuntu right now [05:27] lol [05:27] rgreening: is there any chance that choosing "encrypt my home directory" in the installer is why login is failing on that laptop? [05:27] I'm running Jaunty on 5 different systems, all diff specs and no issues. [05:27] maco: I believe there are several open bugs/issues with that [05:28] i decided to test a more "adventurous" install this time. not quite as adventurous as my first forray into lvm, but.... [05:28] better check the release notes for current alpha [05:28] ok [05:28] the encript option should not be there [05:28] as fas as i know [05:28] er [05:28] shtylman: i used the mini iso [05:29] so it was a network install [05:29] that laptop's cd drive is too broken for a live or alternate cd but working just enough for a net install since it can read the first couple hundred mb [05:29] ahh ok [05:29] and http://www.ubuntu.com/testing/jaunty/alpha5 doesn't exist [05:29] so um, there aren't release notes for current alpha [05:30] (today was alpha5 day, right?) [05:31] look at 4 [05:32] we're in feature freeze, so not alpha 5 territory yet (next week) [05:32] rgreening: i see "A bug in the udev package prevents the LVM encryption option from working correctly after reboot into the installed system. As a workaround, users wishing to test with this option can install with Alpha 3 or wait for Alpha 5." but i didnt use the lvm encryption option. i think it's ecryptfs that's involved [05:34] and that udev (encrypted lvm) bug has already been resolved [05:34] (also uploaded & built yesterday) [05:34] try installing gdm, and setting gdm to be you display manager. reboot and see if ytou can get in [05:34] maco: ^ [05:35] i dont expect it to work. i just switched to kdm on good-lappy today because gdm was broken [05:35] but i'll try it [05:37] oh, plasmoid-network-manager is *also* broken today [05:37] i just learned to use wpasupplicant [05:40] Riddell: Arora 0.5 is tagged. [05:41] rgreening: no, i cannot login with gdm [05:41] what error? [05:41] same [05:41] and is anything showing up in your .xsession-errors [05:42] my .xsession-errors doesn't even exist [05:42] ok, try killing kdm/gdm [05:43] run startx from console [05:43] see if that gets you in [05:44] rgreening: the bugs listed in the release notes for home encryption only relate to cases where the windows migration thing is used and to names of files not being encrypted [05:44] startx doesn't do anything [05:44] just hangs with a blinking cursor [05:44] what vid card do you have? [05:44] oh wait and then "xauth: timeout in locking authority file /home/maco/.Xauthority" [05:45] intel i945 [05:45] are you sure you killed kdm/gdm [05:46] i used service gdm stop [05:46] AH! ok wait after i ^C'd the timeouts it flickered and tried to start X [05:46] i got the same error as before [05:46] and i got some Xorg log type errors spitting into tty1 [05:46] (EE) intel(0): Failed to set tiling on front buffer: rejected by kernel [05:46] (repeat for back buffer and depth buffer) [05:47] thats ok.. [05:47] I think [05:47] by the way, this laptop worked fine in terms of X as of christmas [05:47] on jaunty [05:48] (then i pulled out the hard drive) [05:48] that's the install running on good-laptop right now [05:51] maco: could be something in plasmarc pr plasma-appletsrc in your .kde dir. try removing/renaming those or editing them to remove the default plasmoids from loading. see if that works. [05:52] i dont *have* a .kde yet [05:52] it didnt log in far enough to create one [05:53] rgreening: ^ [05:54] maco, oh. hmm... dunno then. perhaps this is not a kde issue then. [05:54] its giving a kde error... [05:54] is your home dir permission correct [05:54] :-O [05:54] well hey now [05:54] 500? [05:55] that sounds wrong [05:55] AH-ha. not kde issue [05:55] should be 700 at a minimum [05:55] installer bug then [05:55] yeah [05:55] the ecrypt did that [05:55] likely [05:56] ok [05:56] :) [05:57] is that ecrypt-utils package? [05:58] dunno [05:59] dtchen just answered [06:01] victory is mine! [06:01] ? [06:01] blurry icon bug is fixed! [06:02] no more shall I login with clipped icons [06:16] can I download the kde source from bazaar? or do I get it from kde svn? for jaunty? [06:21] shtylman: what is it you seek? [06:21] so in bazaar all I see are the debian folders under kde source [06:21] which I understand [06:21] thats for packaging [06:21] shtylman: correct. [06:21] and I know the kde source is in svn [06:21] that's all we are using bzr for [06:22] tare are tar files in LP we uploaded [06:22] so what? I just use svn to get the kde source and pull the bzr into the same folder? [06:22] no [06:22] use the tar files? [06:22] arer you trying to update an existing package? [06:22] by adding a patch or something? [06:22] yea [06:23] ok... [06:23] but I need to make the patch first [06:23] 1) make a dir [06:23] check [06:23] 2 cd into it and apt-get source [06:23] this gets you the complete package and extracts it for you [06:23] rgreening: turns out it was reported but with the wrong assumption for the cause bug 317895 [06:23] k [06:23] Launchpad bug 317895 in ecryptfs-utils "netboot newuser and ecryptfs fails to login" [High,Triaged] https://launchpad.net/bugs/317895 [06:23] done that before.. [06:24] shtylman: ok, now if yo uwant to patch the current source, you can mv the source dir to source.orig and apt-get source again. [06:25] make your changes in the source dir. then diff -ruN sourcer source.orig to make the patch [06:25] cool, thanks [06:26] with patch in hand, you can have it uploaded to the bzr branch [06:26] I see [06:26] I can branch the bzr main branch and apply the patch to that? [06:26] we use bzr to maintain the debian dirs [06:27] so grabing a copy, and then running dch -i to edit the changelog and then copy the patch to debian patches and editing the series file should do it. [06:27] I see [06:28] if you had commit for the branch, you could upload the changes. for now, you can do a bzr diff and send that to me. I can upload that for you. [06:28] there were a lot of "and then"s in that sentence, rgreening [06:28] hehe [06:29] I'm half asleeeeeeeeeeeeeeeeep [06:29] k...lemme see if I can do that patch stuff [06:29] shtylman: not a problem. ping if ya get stuck somewhere [06:29] (I actually lost part of the file...something crashed) so I have to recreate the code [06:29] k [06:29] rgreening: just sayin' you approach it like "oh yeah it's really simple" and then give like 10 steps [06:29] maco [06:29] better get maco [06:29] :P [06:30] it's actually simple, after you do it 1,000 times [06:30] though about that diff part...couldnt he push his own branch on lp and link it to the bug? [06:31] packaging a big topic. [06:31] all i know of packaging is whatever topics dholbach covered in the ubuntudevelopers podcast thing [06:31] prob could. But if I get it I can do it right away [06:32] apparently that's enough to get a package through REVU and get 2 advocations in 12 hours, if you pay attention to everything he says and everything the MOTU chunk of the wiki says the reviewers will test for [06:33] "enough" doesn't imply a high bar [06:33] ;) [06:33] i didnt say it was a lot [06:34] but he covers the basics fairly well [06:34] he doesn't cover testing the packages, so that's why i mentioned teh wiki where it lists "here's what reviewers are looking for" [06:34] except not all reviewers follow that [06:35] and there's a very human element of significant differences in coverage [06:35] Hrm. The new Qt4.5 packages seem to be working very well. Much faster. [06:36] :) [06:37] dtchen: yes, i know, you went over how stringently you test. gonna show me how to set up an env for doing the same tests on my own packages? [06:38] if you use pbuilder, an example env is already there; see /usr/share/doc/pbuilder/examples/B9[12]* [06:39] see also piuparts [06:46] you mentioned double-building on xfs for the nanosecond timestamps [06:46] dtchen: ^ [06:47] buildtwice [06:47] isnt it called puiparts, not piuparts? [06:47] oh [06:47] nevermind [07:16] rgreening: sorry, I couldn't build it, I've got the random hang and I just rebooted it :/ [07:52] rgreening: you still alive over there? [08:14] rgreening, riddell: take a look at lp:~shtylman/kdebase/ksplash_fix when yall get a chance, thanks === blizzzek is now known as blizzz [09:20] rgreening: could you give me your email/something where I can send the patch === hunger_t is now known as hunger [09:48] Is there any ETA on kde 4.2 being build for intrepid/backports? [09:49] I just upgraded my intrepid install and now I got a nice mix of kde 4.1 and 4.2 which does not really work too well. [09:50] hunger: uhm, http://www.kubuntu.org/news/kde-4.2 [09:50] works just fine here [09:50] on 8.10 [09:51] markey: Is that the one that is currently halfway into backports or the PPA? [09:51] hmm why jockey shows no non-free drivers? I'm pretty sure I'm using radeon driver and fglrx is not installed [09:52] markey: That is the news on kde 4.2 hitting PPA. [09:52] hunger: no idea, but it works fine [09:52] aha. It doesn't work with Xorg 1.6 [09:52] got a fully working KDE 4.2 here [09:52] was pretty easy to upgrade [09:53] following their instructions [09:53] markey: Great QA effort to have a inoffical repo that works and offical ones that break the system of users. [09:53] uhm, you're not bitching, are you? [09:54] if you were, I might not like that [09:54] also, I'm not a kubuntu developer [09:54] just a happy user [09:54] I am afraid I am:-( [09:54] * hunger sighs. [09:54] Looks like I need to fix up my linux again:-| [09:54] mayhaps [09:56] Riddell: http://sinecera.de/jaunty-kusplash.png (the progress bars below show the different states) [10:02] markey: What is mayhaps by the way? [10:02] hunger: it is still building; so hopefully soon [10:02] hunger: mayhaps is a mix of perhaps and maybe [10:03] a|wen: only kdepim is still building for amd64:-( [10:03] markey: if you are using the PPA, you are upgrading from kde4.2 to kde4.2 which hopefully shouldn't break to much... [10:03] markey: Oh, good. Thought it might be shorthand for mayham happens:-) [10:03] I don't have any problems, it's hunger who's bitching ;) [10:04] hmm, fglrx causes segfaults in mesa-utils [10:04] hunger: okay... you may also need to wait a bit more, depending on the mirror you are using [10:05] ..which reminds me, I am getting a little hungry [10:05] should fetch some food [10:05] a|wen: This really annoys me this time round since I tried to keep this box stable for work and did not upgrade it to jaunty. So far it automatically broke twice due to stuff that was put into backports, updates or security repository. [10:06] hunger: sadly we can't build all the packages in backports at once ... they need to be build one by one in the right order [10:07] hunger: but is it like broken in the sense, that it can't start, or is it only broken apps? [10:07] can anyone use ctrl+alt+backspace to restart X server? It doesn't work for me (jaunty) [10:07] a|wen: That obviously does not work as kdebase is not yet installable here while kdepim is building. [10:07] Quintasan: have you set the option for it? [10:07] a|wen: Broken in the sense that I had to fix the boot process the first time round and in the sense that I need to use gnome this time. [10:07] a|wen: where do I set it? [10:08] Quintasan: That was turned off in jaunty. [10:08] ok, so how do I turn it on? [10:08] hunger: kdebase just landed here at my mirror; but would be easier if we could build it all at once :/ [10:08] a|wen: I only had to one issue that size in jaunty in the same time. [10:09] Quintasan: i think it is under display properties (not on jaunty myself) [10:09] a|wen: You have a problem with your deployment process then. [10:10] a|wen: You do understand that this statement of yours implies that ubuntu is unusable for any enterprisy usecase? [10:10] a|wen: thanks [10:10] hunger: i've not been involved in the moving to backports part; but i see, that there is a problem [10:11] Well, enterprises will actually maintain their own mirrors with stuff they have tested. The smaller shops are the loosers:-) [10:11] hunger: it is very valid, what you say; and should definitely be improved [10:12] hunger: but just to note; -backports is unsupported upgrades, and is very different from using -updates [10:12] oh, new ati driver, how nice [10:12] a|wen: You are right... a couple of new debs showed up... but aptitude still insists on downgrading kdebase from 4.1.4 to 4.1.2 while upgrading kde from 4.1.4 to 4.2.0. [10:13] hunger: in -updates everything goes through -proposed; which gives the opportunity to move everything at once [10:13] a|wen: I do know that, but I doubt that updates has any better deployment process:-) [10:14] hunger: it has better deployment, more testing and a far more conservative view on any type of regressions that could occur [10:14] a|wen: Nice! So it should be straight forward to have that implemented for backports, too:-) [10:15] Anyway: backports is pretty straight forward to activate, even to novices. They end up sitting on a timebomb if they do. [10:16] hunger: there is some technical difficulties afaik ... the way the different pockets (-updates/-proposed/-backports) is organized, gives us very different possibilities [10:18] ScottK and Riddell: please see the discussion with hunger ^^ ... this is kind of not good, to cause breakage in -backports in that way; is there any way we can improve on the deployment process there? [10:24] * hunger grumbles that those kde 4.2 debs do not even install cleanly without a force-overwrite. [10:24] hunger: that is indeed not good; we definitely wan't to hear about that, so it can be fixed! [10:26] hunger: please come with the error, so we can get it fixed [10:27] a|wen: kde-window-manager_4%3a4.2.0-0ubuntu1~intrepid1_amd64.deb is conflicting with kdebase-workspace-data on files. [10:27] a|wen: I guess that is due to kdebase-workspace-data still being kde 4.1.4. [10:28] It does conflict with kdebase-workspace-bin, too from the output of dpkg. [10:28] With the first being version 4.1.4 from backports. [10:30] ScottK: are you master of kde4.2 backports? ... all the conflict/replaces on (<= 4.1.3) or (<= 4.1.2) should be changed to (<= 4.1.4) [10:33] ScottK: if you still have all the packages there it is probably easiest if you go through all the debian/control ... if not, i can go through some of them [12:09] ScottK: in kile the application-icon for kile was moved in error, causing no icon to be displayed in kickoff etc. ... fix: http://awen.dk/packages/kile/kile_2.1~svn20090217-0ubuntu2.debdiff [12:41] Riddell: should we try to get arts removed? there is only NBS packages left depending on it, but don't know if we need to wait for those to be gone? if the removal causes any kind of unforseen problems with some apps, then rather have it removed as soon as possible... [13:55] a|wen: I've been trying to coordinate getting them built, but Riddell uploaded them. [13:57] Riddell: If we need to reupload stuff, we ought to do it sooner rather than later. Unfortunately I'll be offline most of today. [13:57] does KDE have to be recompiled because of the new Qt 4.5? [13:57] or can i just update to the new Qt? [14:04] cbr: Qt is supposed to be backwards compatible (binary) [14:05] cbr: so all incompatibilities should be considered bugs somewhere I guess [14:15] i see [14:15] i'll try it out then [14:16] a|wen: Any motu can upload to backports and I can approve them via my phone, so if you can find vorian or someone to upload fixes I can accept them. I'm doing kde4libs right now. [14:22] Fixed kde4libs uploaded [14:24] kdepimlibs is fine [14:26] kde4bindings is fine [14:28] OK, apparently the LP U/I for me to accept stuff is broken. [14:29] Actually it does. It just doesn't update the page to show it did. [14:29] Urgh. [14:35] seems to work [14:35] kdebase-workspace uploaded. And with that I have to run. [14:35] a|wen: Thanks for noticing and please hunt down a MOTU or two to upload the rest. [15:26] kdebase is good. [15:30] kdegraphics is fine [15:33] kdeaccessibility is fine [15:46] kdebase-runtime is ok [15:48] kdegames is OK [15:50] webdev good [15:53] sdk ok [15:54] ScottK: what does ok mean? [15:55] Doesn't need to be reuploaded for intrepid-backports because of conflicts/replaces that didn't take into account 4.1.4. [15:55] oh ok, was seeing a lot of ok messages from you and i didnt 'understand what was going on [15:57] It's in the backscroll. [15:57] I sort of have this vague hope that some other dev will start checking some and so I shouldn't want them to redo what I've done. [15:57] kdepim OK too. [16:00] No problems in kdeutils <- Just for variety. [16:01] a|wen: kile uploaded. thanks for taking care of it. [16:01] kdeadmin good [16:14] artwork fine [16:16] Riddell: The backport is currently blocked on kde4bindings depwait due to insufficient version of python-qt4. Would you please look into that. I'm about to vanish offline. [16:18] toys, edu, and plasma-addons all checked fine. [16:18] I think that's all of them.... [16:23] hunger: I think I got all the conflicts/replaces fixed for the KDE 4.2 backport. Thanks for pointing out the problem. [16:24] The fixed packages are building now. [16:51] Quintasan: roderick.greening AT gmail.com [17:10] rgreening: I did a branch of the kdebase-workspace debian stuff, and added my patch [17:14] shtylman: cool. [17:16] I wonder if you can bzr merge. I can see if there are pending merges to approve.. (assuming that works) [17:19] do I just propose a merge ot teh main branch? [17:19] yeah [17:20] assuming you did it via lp. If you ust did local on your hd, then bzr merge. [17:22] can I popose a merge to the main branch from bzr? [17:24] shtylman: I think just doing a bzr merge will do it [17:24] rgreening: I just porpsed through launchpad (bzr merge just pulls the changes from the main one into mine) [17:24] *proposed [17:25] oh [17:25] looking [17:25] k [17:26] hmm... shtylman I dont see it... [17:27]