=== yofel_ is now known as yofel [02:15] Linux and Ubuntu is cancer that attaches itself in an intellectual property sense to everything it touches. [02:16] Linux and Ubuntu is cancer that attaches itself in an intellectual property sense to everything it touches. [02:16] !ops [02:16] Help! bhale, infinity, Hobbsee, jdub, thom, fooishbar, fabbione, mdz, lamont, or Keybuk [02:16] damn lag. [02:16] Thanks. [02:16] \o/ win! [02:16] wasn't even a very creative troll [02:17] beat me to it [02:17] * Hobbsee ^5 cjwatson [02:17] is today official troll day? [02:17] seems so [02:17] He could of at least claimed we were insecure or something. [02:18] well, now he's claiming that i can't see him, so... [02:19] * TheMuso wonders whether DrCheese created #windows, however I can't seem to see the topic or names without going in there. [02:19] why does that IP look familiar. [02:19] TheMuso: highly unlikely. People who create large channels are usually too busy to petty troll. [02:19] @btlogin [02:20] Hobbsee: It's not a large channel, he's in ##windows, not #windows. [02:20] Hobbsee: Although, even that's moderately large, actually. [02:21] infinity: ah, i didn't do a whois to check. [02:21] Hobbsee: part of the big MA Comcast DHCP pool; identifying him is probably hopeless. [02:21] jdong: ah yes, you should recognise that IP. check the BT. [02:22] Hobbsee: I don't have access to it, do I? [02:22] ah I see it. [02:22] yeah I should've recognized that indeed. [02:22] ? [02:22] frequent customer. [02:22] Heh. [02:22] Snova: ubuntu-ops log 4/13 and 4/08 [02:23] hallo [02:23] and under the other aliases. Here's a cross-channel hammer [02:23] Comcast generally gives you the same IP for each lease renewal, so unless he knows how to ask for a new one, it should ~work. === calc_ is now known as calc [05:46] has anybody found that the ATI Mobilitiy cards (X2300) doesn't detect in restricted drivers in jaunty [05:46] i seem to not be able to get ubuntu to use the restricted driver manager for teh ati x2300 [05:50] clear [06:19] good morning [06:34] dholbach: wow you're up early [06:35] hiya Amaranth - it's 7:34 - and I was out running already! :-) [06:35] ah, right, dang daylight savings [06:44] bryce_: wiki edited [06:52] siretart: great === tkamppeter_ is now known as tkamppeter [07:19] slangasek, i've got a resolution for bug 355242 that involves only a 2 line diff [07:19] Launchpad bug 355242 in mesa "mythfrontend.real crashed with SIGSEGV in QGLWidget::resizeEvent()" [High,Fix committed] https://launchpad.net/bugs/355242 [07:20] mythbuntu rc disks will need a re-roll with it === ScriptRipper_ is now known as ScriptRipper === thekorn_ is now known as thekorn [07:46] superm1: it's a patch to mesa? That implies invalidating all the ISOs [07:47] slangasek, perhaps can you just reroll mythbuntu after the others have been verified then? [07:49] we can consider that. it does effectively mean we don't get jigdo support for the RC, but if we time it fairly close then we can at least get some jigdo benefit [08:04] slangasek: there's also a candidate for the wacom crashes, but it's still untested so not meant for RC [08:04] ok [08:06] Good morning [08:07] * slangasek waves [08:08] * siretart bounces happily through the channel - finally working intel driver.. :-) [08:09] siretart: oh, what did you change? [08:09] pitti: see my latest post to ubuntu-devel. I've reverted to the 2.4 branch [08:09] siretart: interesting; that still works with current X then? [08:10] pitti: you need to compile it against jaunty's X and libdrm, which works with some patching.. :-) [08:10] working packages can be found in my ppa [08:11] well, at least WFM [08:15] cody-somerville: hi, do you have plans to fetch xubuntu-docs translations from rosetta and upload a new xubuntu-docs with those included? [08:16] Is there a non-historical reason for USNs to list Xubuntu but not other unofficial flavours as affected? [08:40] Has anyone else recently seen dbus-daemon go crazy, consume a core, and all available memory (it's up to 1.6GiB, and still rising)? [08:41] RAOF: something sending it a lot of timing out messages? [08:41] dbus-monitor is your friend [08:42] Hello, tracker! [08:42] Hm. Apparently tracker would like to tell me that my index is corrupted. [08:43] does tracker work for anyone else? it's never done anything useful for me :( [08:45] liw: using all your cpu is useful [08:45] we don't even install it by default now [08:45] liw: it tests your cpu [08:45] and I'm pretty sure it's removed by update-manager on upgrade [08:46] ta dholbach [08:46] Keybuk: I can confirm that update-manager didn't remove it on my amd64 desktop last week when I upgraded from intrepid->jaunty [08:46] I can ensure that it gets removed if thats what we want [08:47] +1 [08:47] (sorry, I have not followed the state of tracker) [08:48] mvo: we decided again doing that in a systematic way because some users are using it [08:48] Keybuk, it didn't get removed from my laptop, actually [08:48] ok [08:48] Keybuk: Thanks; looks like the bug is tracker spamming "OMGINDEXCORRUPTED" messages into the void. [08:49] I'd love to have something like tracker, if it didn't hog my computer and actually found things when I search [08:49] tracker will probably be better next cycle [08:49] good to hear [08:49] the jaunty version is basically a rewrite, it still has some issue but gets lot of work [08:50] RAOF_: where does it spam to? [08:50] nokia is paying to get it working fine on their device apparently [08:51] seb128: is there going to be a rewrite to use fsnotify instead of inotify? [08:52] fsnotify? [08:53] ah, some new kind of implementation, good [08:53] liw: lwn.net/Articles/311350 [08:54] Keybuk: that I don't know, but now it's possible to have applications pushing datas rather than the indexer going through the disk all the time [08:54] Keybuk: ie your mailed can send datas to tracker when receiving emails rather than relying on inotify to go through the disk emails [08:55] mailed -> mailer [08:55] seb128: Do we actually have the evolution side of that system in jaunty? [08:55] no ;-) [08:55] the new version is still new, I expect it to work better [08:55] I would not bother too much with the jaunty version [08:55] there is frequent db corruptions and still issues [08:55] ah [08:56] wgrant, Xubuntu *is* an official flavour :) [08:56] Mirv, I'd like to, yes. [08:56] evolution db corruptions? never :) [08:56] one of the neat features of fsnotify/fanotify is that a watching application gets a file descriptor to the data just written/read [08:56] so you don't need to stat(), open(), etc. massively saving on overhead [08:57] liw: no, tracker db corruptions ;-) [08:57] cody-somerville: It's no more official ('supported', I suppose the correct term is) than Mythbuntu or UbuntuStudio, is it? [08:57] Keybuk, can fsnotify do things like "show me everything that ever changes in this filesystem" or "...inside this directory tree"? [08:57] liw: btw have you seen this bug about computer-janitor using update-manager as translation domain? [08:58] liw: in theory, yes [08:58] seb128, I have; I haven't investigated yet, I'll have to discuss the gettext domain issue with mvo [08:58] wgrant: not supported by Canonical, but official (like Mythbuntu, Ubuntu Studio)... it's good to refer to those as official as there are also unofficial Ubuntu variants like Eeebuntu, Ubuntu ME etc.. [08:58] liw: fanotify is by-filesystem rather than by-file/directory [08:59] ok [08:59] Keybuk, übercool! [08:59] Mirv: True. But my point is that it's odd to single out Xubuntu. [08:59] I'm going to have to add support for that in my backup program [08:59] wgrant: yes, regarding your actual point, it's probably just historical, there have been other such cases as well [08:59] liw: inside-this-directory-tree is harder, in that you'd have to read the filename and strncmp or something ;) === azeem_ is now known as azeem === Nicke_ is now known as Nicke [09:00] Keybuk, that'd be one way; I'd have to benchmark whether it'd be faster to scan the directory tree and remember all inodes and then compare with indoes that change [09:01] liw: I can't imagine that it wouldn't be faster ;) [09:01] though the overhead for a smaller directory of processing and discarding unwanted events could be high, I guess [09:01] wgrant, I'm not sure what their status is [09:01] Keybuk, depends on size of tree and number of changes, but I'm too stupid to know which is faster without benchmarking [09:08] lool: you'll upload the fix for bug 339466 to the queue? [09:08] Launchpad bug 339466 in python-debian "cron.weekly script produces a warning since the Python 2.6 transition" [Medium,Triaged] https://launchpad.net/bugs/339466 [09:23] pitti: bug #361543 for you :( [09:23] Launchpad bug 361543 in apport "/etc/default/apport mistakenly installed as /etc/default/apport.default" [Undecided,New] https://launchpad.net/bugs/361543 [09:23] owch [09:25] cody-somerville: is there a technical-overview-esque page for Xubuntu to link from https://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview for RC? [09:25] Riddell: will there be an RC technical overview for Kubuntu as well? [09:26] mvo: are you around? [09:26] tseliot: yes [09:27] mvo: any ideas on this? https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/351394 [09:27] Launchpad bug 351394 in nvidia-common "nvidia -177 needs to be transitioned to -180 on upgrade" [High,Triaged] [09:27] tseliot: let me have a look [09:28] mvo: also, what driver version do you migrate to "nv" in Jaunty? [09:28] s/version/versions/ [09:34] pitti: I was waiting for some ubuntu-release ack [09:34] pitti: (I sub-ed the team yesterday) [09:35] lool: you got it [09:36] cjwatson, evand: yay, thanks for fixing the default grub target; in the beta I still had to change it from (hd0) to my USB stick (sdc), now it automatically DTRT [09:37] pitti: Yup, uploaded [09:42] slangasek, There shall be. === dpm_ is now known as dpm [10:11] Riddell: https://wiki.ubuntu.com/JauntyJackalope/RCAnnouncement is up for consideration, pulling in the same kubuntu text from the beta; please let me know if changes are needed [10:13] slangasek: good with me [10:38] seb128: did you have any problems with the retracers last week? they seem surprisingly stable now [10:38] seb128: I remember some weird HTTP errors, but no real crashes any more [10:39] * pitti -> offline, CD testing [10:40] /join #ubuntustudio [10:40] bah [10:47] gosh, reading scrollback for martinw [10:47] how is everyone here today? [10:48] busy testing ;) [10:50] up at strange hours, right on schedule :) [10:50] slangasek, i see no 14.2 respin for armel desktop, did you forget us ? [10:51] sabdfl: martinw == Patrick Frank, fwiw; he has Issues with Authority :/ [10:51] ogra: didn't forget, just got caught up getting other things squared away - I'll do the ports run now [10:51] me too! i'll try and chat privately with him when he comes online [10:51] thanks, i'll test it ;) [10:55] pitti: no, good work ;-) [11:09] cjwatson: What would be the right seed to list redboot-imx51-babbage [11:09] cjwatson: We use it to build the official images, but it's not pulled by any package and the package itself is not included in any media, only its contents [11:10] lool: I'd say platform.jaunty/supported-installer-common then [11:11] Ok, thanks [11:11] siretart: I gather your adventure in Intel bleeding edge stuff did not have a happy ending? [11:16] ScottK: for my laptop, yes, I'm happy with the 2.4 branch on my laptop [11:17] siretart: Weren't you also testing the latest 2.6? [11:18] ScottK: jaunty ships some later revision of the 2.6 branch. I've tried the 2.6 HEAD, 2.7 HEAD and 2.4 HEAD [11:18] ScottK: I got the best results from the 2.4.1 package with bryce's patches as found in intrepid [11:19] ScottK: having said this, I'd suggest to include my package in universe for people like me. [11:19] I see. Some Gentoo guy was recently telling me that his had recently gotten better with the bleeding edge stuff. [11:19] siretart: As long as you're willing to support it for the life of Jaunty, I think it's a great idea. Otherwise a PPA might be better. What do you think? [11:20] yes, 2.7 is a big improvment on my laptop compared to 2.6. but still hasn't acceptable performance [11:20] siretart: where do you notice those slowness issues? [11:20] ScottK: I'm willing to integrate updates from intrepid-updates to the package, yes. [11:20] ScottK: I'm not familiar with the code to actually start hacking on [11:21] seb128: compiz and planet-pengiun-racer are not usable at all. [11:21] siretart: OK. The only issue then would be any -security issues that come up after Intrepid eol [11:21] what in compiz? [11:21] normal actions, ie alt-tab switch [11:22] seb128: resizing windows, the expose effect, alt-tab switch, etc. [11:22] hum ok [11:22] I guess it's not that slow on my card [11:22] seb128: alt-tab switch was unnaceptable in metacity with compositing as well [11:22] I was just wondering if people were using extra features which showed the issue [11:23] siretart: Did you try Option "MigrationHeuristic" "greedy"? While it's still not up to Intrepid, I find it usable. [11:24] ScottK: err - I'm not suggesting to put it in main but universe. and for universe we don't promise security (or other) updates at all [11:24] siretart: True. [11:24] ScottK: no, I haven't tried that option [11:25] siretart: You might. I understand it makes some people have crashes so is not suitable for a default, but it made a huge difference for me. [11:25] For me it's like uxa without crashes. [11:25] is that option for the 2.4 branch or 2.6 branch? [11:25] Either as I understand it. [11:26] hm [11:26] siretart: Bug #359600 has some information [11:26] Launchpad bug 359600 in xserver-xorg-video-intel "Solved slow 2D performances with EXA" [Wishlist,In progress] https://launchpad.net/bugs/359600 [11:26] I've been testing the 2.6 and 2.7 branches both with UXA [11:26] We had it for default for a while in Intrepid, but didn't keep it, so it must be for both. [11:27] so I cannot really comment on EXA. EXA was more than unacceptable for me in 2.6, and I didn't even bother trying it in 2.7 [11:27] I see. It made a huge difference for me with exa. [11:27] siretart: For a new package you'll need two motu-release acks. You have mine to get you started. [11:29] ScottK: okay. who else from motu-release is around here? :-) [11:29] ScottK: I don't know of any reports of crashes due to greedy migration being enabled, but the patch to xserver-xorg-video-intel to /try/ to enable it by default for those chips causes crashes [11:30] the only issue I've found with greedy migration here is pixmap lossage [11:30] (firefox in particular likes to go black in patches) [11:31] slangasek: I have also noticed some black areas with greedy (but not to the level that I would go back to non-greedy ;-)) [11:39] to which package should I reassign a bug in the nvidia binary driver? [11:41] which version? [11:44] pochu: nvidia-graphics-drivers-$VERSION (where VERSION is 180, 173 or 71) [11:49] tseliot, there are only three nvidia-graphics-drivers now? [11:50] directhex: I forgot 96 [11:50] that's better ;) [11:51] tseliot, so, anything worth having in the 185 betas, that you know of? [11:52] tseliot: ty [11:52] np [11:53] Keybuk: nice, the current c't (famous German computer magazine) has a 3-page article about upstart [11:53] directhex: mainly fixes for VDPAU and support for new cards: http://www.nvnews.net/vbulletin/showthread.php?p=1976912 [11:55] tseliot, neat [11:56] directhex: only for Karmic and/or backports to Jaunty though [11:56] tseliot, my main issue currently is trying to get actual audio out the hdmi port on an nvidia 9300 motherboard. it appears non-trivial [11:56] directhex: isn't that something that alsa/pulseaudio should deal with? [11:57] * tseliot > lunch [11:57] tseliot, oh, yeah, sure. but i can't get a bloody thing via speaker-test. and it's hell trying to get sound out of assorted command-line alsa utils which all use totally different device naming syntax [12:00] pitti: got a url/translation? [12:00] Keybuk: it's not online, just in the paper magazine [12:01] Keybuk: http://www.heise.de/ct/inhalt/2009/09/176/ === evand1 is now known as evand [12:25] soren: ever used kvm for testing images and ran into "kvm: 27711: cpu0 unhandled wrmsr 0xc0010117 data 0"? [12:25] amd64 dvd ubiquity install hanging at 78% "System locale is being configured" (or something like that) === Rafik_ is now known as Rafik [12:33] dholbach: That could very well be unrelated. [12:33] dholbach: I consider those messages debug messages more than anything. [12:33] soren: ok, I'll re-test and see what happens [12:34] dholbach: The guest kernel sometimes pokes at various MSR's to see if there's something there, and that gets logged by the host kernel. Most of the time, it's benign. [12:34] Most of the time. [12:35] ScottK, Riddell: does the Kubuntu KDE4 remix warning on https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes still apply in the case of upgrades to 9.04? [12:42] hmm, so 24h later i see my system starting to eat my swapspace again ... it went from 0M to 264M within the last 30min, without me doing anything special or additional to what i did 1h before [12:43] (i have htop running constantly since i ran out of swap yesterday ) [12:43] heh, and between me starting to type the above and now it went to 379M swap usage [12:45] * ogra closes evo and firefox [12:45] (only xchat and two terminals are open now, system is at 429M swap usage) [12:48] ogra: how's the armel candidate ISO looking, BTW? [12:48] livesession is fine, install is at 57% [12:48] no unknown bugs seen yet [12:49] sabdfl, good push for the new TZ map, it looks a lot better now [12:49] slangasek: I think that can go [12:49] ogra: thanks to kwwii and evand's work, i agree [12:50] evand: know anything about this? http://pastebin.ubuntu.com:80/151367/ when running OEM mode [12:51] Riddell: not until now. [12:51] * evand digs [12:51] thanks sabdfl [12:54] evand: davmor2 says that didn't happen yesterday [12:54] has anything changed since then? [12:55] it happened in 1.12.5 [12:55] fix incoming [12:56] evand: does this affect kubuntu only? or ubuntu desktop too? [12:56] kubuntu only [12:56] Riddell: I just done ubuntu oems [12:57] Riddell: it can go because 8.04->9.04 is only a supported path for kde, not kde4 remix? [12:57] slangasek: right [12:57] ok [12:57] slangasek: OEM broken on Kubuntu desktop CDs ^^ [12:58] waah [12:59] evand: also reboot didn't seem to be working at the end of a Kubuntu install [12:59] Riddell: where did it break? Did pressing the button not do anything, or did the computer fail to restart after shutting down? [13:00] evand: ubiquity quit, desktop sits there being itself [13:01] hrm, ok. I'll pull down the latest Kubuntu daily-live and see if I can reproduce it. [13:01] sorry about the OEM breakage, apparently my fault way back in 1.12.0 [13:01] I have the Kubuntu image here, I can have a look ... [13:01] ah great [13:01] should I go ahead and upload this change and we'll deal with the reboot issue as another upload? [13:02] my instinct is to batch it up for post-RC, since we have some other changes for then anyway [13:02] Riddell,slangasek: what do you think? [13:02] slangasek: get it in now before there are many tests on it :) [13:02] I'm tempted to upload the OEM fix and respin that for RC [13:02] I'd kind of like to fix the colours on the Kubuntu partition bars too [13:02] cjwatson: I though that got fixed [13:03] not to my knowledge [13:03] I don't like shipping the RC with broken OEM mode, but doing a respin now cuts into our testing time and our image prepublishing time [13:03] Riddell: is #133d80 a plausible Kubuntu-blue colour to use for the partition bars? [13:03] kwwii's area really ^^ [13:05] erm, where? [13:05] slangasek: there aren't that many test on kubuntu are there [13:06] cjwatson: that is a pretty kubuntu-ish color, but it might be too dark bepending on where/how it is used [13:07] davmor2: rerolling kubuntu includes rerolling DVDs, which takes > 1.5h just for the livefs rebuild [13:08] slangasek: toss a coin :) [13:08] Riddell: is it acceptable to you to ship the RC without a usable OEM mode? [13:08] yes, it's not the end of the world [13:09] ok, then that's my preference [13:09] I'm just mindful that it's not well tested so if there's further problems (and davmor2 had issues yesterday) they won't be picked up [13:09] we can make images available immediately post-RC for testing, then? [13:09] we can indeed [13:10] and we have alternate OEM to test [13:12] kwwii: bug 348461, though I don't have a screenshot to hand unfortunately [13:12] Launchpad bug 348461 in ubiquity "Jaunty: Kubuntu shouldn't use grey for the installed system bar in ubiquity" [Undecided,New] https://launchpad.net/bugs/348461 [13:12] evand: bug 361668 [13:12] Launchpad bug 361668 in ubiquity "kubuntu OEM mode broken" [Undecided,New] https://launchpad.net/bugs/361668 [13:12] I can explicitly test Kubuntu OEM immediately post-RC, since we need to update the oem-config timezone map anyway [13:13] or, indeed, I can test it now with evand's fix [13:14] cjwatson: ouch, without seeing the problem it is pretty hard for me to just suggest a color :( [13:15] let me see if I can produce a screenshot [13:15] cjwatson: the blue you suggested fits well with kubuntu colors so testing it can't hurt [13:15] I could download a CD and test it myself but that would take a bit [13:16] nggh, partition bars are still invisible in Kubuntu? [13:17] I have to take my son to the dentist, bbiab...I'll read the log when i return [13:18] doko: do you think we can fix bug 353704? [13:18] Launchpad bug 353704 in ia32-libs "Wrong path for lib plugins in amd64 build" [High,Triaged] https://launchpad.net/bugs/353704 [13:20] doko: it breaks Skype on amd64, is it feasible to fix in an SRU of 9.04 [13:20] robbiew: I think Bo is fixing this [13:20] Riddell, slangasek: right so the out come is we can carry on testing the images that are up, and you'll do a respin friday (or something) for us to nail all the oem issues is that correct? [13:20] argh [13:21] davmor2: yes [13:21] slangasek, gdm sudeenly crashes on babbage/imx51 [13:21] slangasek: Cool :) Cause I just finishe ubuntu desktop :) [13:21] install went flawless [13:22] * ogra checks what seb128_ changed between beta and now in gdm :/ [13:22] no === seb128_ is now known as seb128 [13:22] looks like Robert's the one who changed it [13:22] no ? [13:22] what changed? [13:22] ah [13:22] though it could be a library regression, rather than the gdm change [13:23] seb128, i get the "greeter is crashing, trying with another greeter" message in gdm suddenly [13:23] slangasek: the change he did was a one line boolean logic for the hours format combo [13:23] yeah, that doesnt really look like it could cause anything [13:23] ogra: that means the greater is crashing, could be any library gdm is using or xorg [13:24] that patch doesn't touch the greeter, so probably not [13:24] do you get apport triggering? anything in the logs about a crash? [13:24] noting in Xorg.0.log ... inspecting the rest atm [13:24] i see 7usr/bin/gdm in the processlist [13:26] slangasek, bryce: I updated the "known issues" bits on https://wiki.ubuntu.com/JauntyJackalope/TechnicalOverview#Known%20issues with the workarounds known to me (we have a few more crashers, but they involve patching the driver, which is a bit out of scope for release notes); does that look okay to you, or is it too technical? [13:26] gdm log only has xkbcomp messages ... [13:26] nothing in /var/crash [13:26] pitti: it's the wrong place for it; bugs that aren't fixed for final should be documented at https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes [13:27] pitti: I can take care of porting that over, though [13:27] slangasek: ah, I'll move it over [13:27] slangasek: I guess it doesn't hurt to also keep it on TechOverview, for the RC? [13:28] if the tech overview will go up on the ubuntu.com website again, then we should have it ready for final, i.e., eliminate duplication w/ the release notes [13:29] slangasek: your lock on ReleaseNotes timed out, are you still working on it? [13:29] pitti: no [13:31] I am suspicious that this gdm issue might be cause by the gtk+2.0 issue [13:31] we'll confirm soon [13:31] slangasek, bryce: okay, put on https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes now [13:31] thanks [13:32] lool: right, I wondered... [13:33] what irritates me here is that i indeed get a gtk window telling me the greeter cant start [13:34] soren: can you join #ubuntu-testing? [13:34] lool, slangasek same thing with new gtk [13:35] ogra: Could you try moving away your /usr/lib/vfp? [13:35] soren: I'm having the same issue again (amd64 jaunty host, jaunty guest): freeze during the installation - how best to debug it? [13:35] ogra: sudo mv /usr/lib/vfp /usr/lib/vfp.bak [13:37] same thing [13:38] ogra: Does dbus run? [13:38] On my install it doesn't [13:39] yes [13:39] Can't start Hardware abstraction layer - please ensure dbus is running [13:39] if you log in, can you run gdmthemetester? [13:39] * ogra tries startx [13:39] or gdmflexiserver [13:39] one sec, just installing sshd [13:40] btw, i cant stop gdm with the initscript [13:41] kirkland: hiya - can you join #ubuntu-testing so we can chat a bit about kvm on amd64 jaunty? I'm having hangs during test installations [13:42] dholbach: during language pack en ? [13:42] hmm, startx does nothing now [13:43] ah, its just slow [13:43] ~/.xsession-errors has nothing special [13:43] no panel though [13:44] your install seems to be busted [13:44] my live session runs flawless [13:45] and my install i did from beta was upgraded yesterday [13:45] and worked flawless as well [13:46] so what is not working? [13:47] my desktop doesnt come up with startx [13:47] gdm pops up the "greeter is dying, trying another one" msg [13:48] hmm, and avahi doesnt seem to work, i cant ssh into the .local address ... [13:48] you say it waorsk flawless and that it crashes and doesn't run at normal speed [13:48] I'm confused now [13:48] i just did an install from a fully working livesession [13:48] after reboot i hang at the greeter message [13:49] killing gdm and running startx only gets me a wallpaper [13:49] the testinstall i did with the beta image was upgraded yesterday and didnt show any issues [13:50] ok, so maybe that new install is busted in some way [13:50] i see nothing in the gdm or xorg logs [13:51] the .xsession-errors file looks fine as well [13:51] that's not gdm specific apparently if you get only the desktop and no normal session [13:51] yes [13:51] is your lo interface working correctly? [13:51] ping localhost [13:51] slangasek: hi, could you please accept my new telepathy-mission-control upload? (I've rerun libtoolize to fix FTBFS) [13:51] ping 127.0.0.1 [13:51] works fine [13:51] ok so that's not that [13:52] nope [13:52] bigon: a bit occupied at the moment [13:52] if you run a non GNOME session and try running nautilus or something there, what happens? [13:52] whats that, startx --xterm ? [13:53] * ogra totally forgot how to do that manually [13:54] ah, well ... i'll create an .xsession file [13:54] aha, running nautilus from the xterm segfaults [13:54] * ogra tries gnome-session [13:55] hmm [13:56] can you get a nautilus stacktrace? [13:56] x-session-manager[7681]: WARNING: Application 'gnome-wm.desktop' failed to register before timeout [13:56] x-session-manager[7681]: WARNING: Application 'gnome-panel.desktop' failed to register before timeout [13:56] doe that look ok ? ^^^ [13:58] those are only warnings but that's nor normal [13:58] can you get the nautilus stracktrace? [13:58] slangasek: The release not on does not boot with Intel D945 is still relevant, but needs rewording as the problem is much more widespread than we knew at Intrepid release time. It needs to be generalized, but I'm not at all certain how to word it. [13:58] will try to [13:58] not/note [13:58] i dont get a metacity either though [13:59] ScottK: right, I remembered that was why the release-notes bug was open; I don't know how to word it, either [14:00] slangasek: My recommendation would be: "It's a kernel bug, give it to the kernel team to figure out how to word it". [14:00] After all, an action passed is an action completed. ;-) [14:00]