hyperair | anyone here i can talk to about mesa's build system and 64-bit issues? | 14:03 |
---|---|---|
hyperair | bryce_: ping | 14:41 |
jcristau | talking about mesa's build system. hah. | 14:41 |
hyperair | heh yes i am =p | 14:43 |
hyperair | it's miserable and annoying by the way | 14:43 |
tormod | hyperair: I think you already talked a lot about it in #ubuntu-devel, maybe you can file a bug and sum up what is needed? | 14:43 |
hyperair | tormod: actually i think i'll use an existing bug. | 14:44 |
tormod | even better | 14:44 |
hyperair | but yeah i'll sum it up with a debdiff as well soon | 14:44 |
tormod | even better yet :) | 14:44 |
apw | tseliot, this dell 10v touchpad detect does not seem to take every time you boot, more like 4 out of 5 | 14:44 |
hyperair | and an upstream patch. | 14:44 |
tseliot | apw: what do you mean? And can I see a log? | 14:46 |
tormod | hyperair: then it can't get better :) | 14:46 |
hyperair | heh =) | 14:46 |
hyperair | i should have looked at this earlier though =\ | 14:46 |
apw | tseliot, all i know is that sometimes i boot the boundary and 90pixel or less thing don't get applied ... i can apply them by hand successfully | 14:47 |
apw | tseliot, i am not the only one seeing the same | 14:47 |
tseliot | apw: maybe Hal fails to apply your settings? | 14:48 |
apw | tseliot, perhaps ... /me knows nothing :) | 14:48 |
apw | i report it to you having watched scott beat the crap out of his machine for it :) | 14:48 |
tseliot | hehe | 14:49 |
tseliot | apw: maybe try reinstalling the synaptics package? It could be that the fdi cache was corrupted | 14:49 |
tseliot | oh and reboot, just to be sure | 14:50 |
apw | tseliot, its random when it does it, ie not all the boots | 14:50 |
tormod | apw, blame upstart ;) | 14:51 |
apw | he'll love you for that | 14:51 |
tseliot | apw: it sound like a Hal bug. You might want to ask pitti about this | 14:51 |
tseliot | hehe | 14:51 |
apw | tseliot, thanks | 14:51 |
tseliot | thanks for reporting the problem | 14:51 |
=== ripps_ is now known as ripps | ||
* hyperair notes that mesa has some real huge lintian issues | 15:40 | |
jcristau | namely? | 15:42 |
hyperair | jcristau: you should have asked faster, i lost my logs already =.= | 15:48 |
hyperair | lemme re-lintian it | 15:48 |
jcristau | it should have a couple warnings, but nothing "huge" | 15:49 |
hyperair | http://pastebin.com/f3aff1fde | 15:50 |
hyperair | lots of nice Es | 15:50 |
jcristau | that's fine | 15:51 |
jcristau | it's not lots of Es, it's one E | 15:51 |
hyperair | eh? | 15:54 |
hyperair | i'm quite sure i saw more than one | 15:54 |
hyperair | oh well | 15:54 |
jcristau | it's the same, once for each lib | 15:55 |
* hyperair thinks dpkg/apt should gain some real multiarch support | 15:57 | |
* hyperair pulls out hair after the third compilation of mesa that failed to do what was needed | 16:54 | |
hyperair | good lord. there has to be a reason why mesa's debian/rules is so bloody cluttered. | 16:57 |
jcristau | what the hell are you trying to do? | 16:57 |
hyperair | oh i was trying to pass an environment variable into make | 17:13 |
hyperair | first i exported, then i realized make doesn't honour exported variables =.= | 17:14 |
hyperair | first compilation. | 17:14 |
hyperair | so i passed it into one of the $(MAKE)s, but got the wrong one instead | 17:14 |
hyperair | install instead of build | 17:14 |
* hyperair facepalms | 17:14 | |
hyperair | so after loads of digging, i finally found the build one | 17:14 |
* hyperair gapes at lzma's memory usage | 17:16 | |
hyperair | 400M to compress a deb. woo | 17:16 |
bryce_ | tjaalton, I went ahead and posted about the scheduling conflicts we've had with X in ubuntu to xorg-devel@ | 19:40 |
bryce_ | tjaalton, so far looks like I'm being ignored as usual ;-) | 19:40 |
tjaalton | bryce_: yeah I noticed.. we'll see if someone responds :) | 19:44 |
micahg | are there any known issues with GTK apps and nvidia drivers in karmic? | 19:55 |
micahg | hi seb128 | 20:15 |
seb128 | hey micahg | 20:15 |
micahg | seb128: do you know anything about GTK problems in karmic with nvidia chipsets? | 20:15 |
seb128 | no | 20:15 |
micahg | or rather the proprietary drivers? | 20:15 |
micahg | oh | 20:15 |
seb128 | what sort of issue do you get? | 20:16 |
micahg | well, people keep reporting sefaults and crashes with our firefox in karmic | 20:16 |
micahg | but the mozilla version seems to work fine | 20:16 |
micahg | that's why I was wondering if our GTK apps are having issues | 20:16 |
seb128 | our gtk has no distro change | 20:17 |
seb128 | and I don't think mozilla has a gtk copy | 20:17 |
seb128 | could be some cairo changes though | 20:17 |
seb128 | do you have a bug example? | 20:17 |
micahg | i'll have to find one | 20:17 |
seb128 | upstream mozilla has a cairo copy I think | 20:18 |
seb128 | we use the system one in ubuntu, so they might have changed their copy to fix issues | 20:18 |
seb128 | not sure though, asac would be a better person to ping about that | 20:18 |
micahg | bug 457594 | 20:19 |
ubottu | Bug 457594 on http://launchpad.net/bugs/457594 is private | 20:19 |
seb128 | micahg, the stracktrace on this bug is not really useful | 20:21 |
seb128 | the other bug mentioned is a crash due to flash though | 20:22 |
micahg | bug 452856 | 20:22 |
ubottu | Bug 452856 on http://launchpad.net/bugs/452856 is private | 20:22 |
kervel | hi, i'm running ubuntu-x-swat on karmic and i'm running into http://bugs.freedesktop.org/show_bug.cgi?id=24734 | 20:23 |
ubottu | Freedesktop bug 24734 in Drivers/DRI/i915 "Changes in Mesa prevent Gnome desktop (with Compiz) from starting normaly" [Critical,Resolved: fixed] | 20:23 |
kervel | i wonder if the guys running the ppa know it is broken and needs update | 20:24 |
Duke` | tormod is following the bug | 20:27 |
Duke` | erf. | 20:27 |
tormod | it is fixed in the PPA already, for Jaunty | 20:28 |
tormod | x-updates for karmic will be fixed in a few hours | 20:29 |
tormod | erf | 20:30 |
* hyperair wonders if cross-compiling 32-bit mesa on 64-bit arches is a good idea -- as in have lib32mesa* rather than bundling everything in a huge ia32-libs package | 20:33 | |
seb128 | micahg, those bugs seem to indicate xulrunner issues | 20:35 |
seb128 | the stacktraces are not really useful though | 20:35 |
micahg | ok, I'll chat with asac about it then | 20:35 |
micahg | I was just wondering if anyone knew of any major issue | 20:35 |
micahg | *issues | 20:35 |
micahg | I still have to go through all the bugs and see if there are any commonalities | 20:36 |
bryce_ | wow, #xorg-devel is thick with ubu-hate. | 21:55 |
tjaalton | bryce_: the cloud reference? nothing ubu-related except in the first comment, I think | 22:04 |
bryce_ | tjaalton, there was also some stuff about gdm/upstart last night | 22:05 |
tjaalton | seems like aaronp has issues with karmic :) | 22:08 |
tjaalton | not being able to start gdm if you come from the recovery shell is a bug though | 22:08 |
bryce_ | tjaalton, could you check that there's an appropriate bug filed about that against gdm? | 22:15 |
bryce_ | I targeted+milestoned the gdm/upstart blinking issue | 22:16 |
tjaalton | it is filed already | 22:18 |
tjaalton | I'll check which one it was | 22:18 |
bryce_ | might be worth milestoning too | 22:18 |
tjaalton | triaged too.. the upstart job "checks kernel command-line for inhibitors" | 22:19 |
tjaalton | and that's a bit silly | 22:19 |
tjaalton | bug 436936 | 22:21 |
ubottu | Launchpad bug 436936 in kdebase-workspace "gdm upstart job checks /proc/cmdline for single user mode, won't dtrt on post-boot runlevel change" [Medium,Triaged] https://launchpad.net/bugs/436936 | 22:21 |
tjaalton | would karmic-updates be the correct milestone? | 22:25 |
bryce_ | yep | 22:25 |
tjaalton | done | 22:27 |
bryce_ | excellent | 22:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!