/srv/irclogs.ubuntu.com/2011/02/09/#ubuntu-desktop.txt

dcghi all, having some issues getting multiple X servers running on maverick.01:30
dcghave 2 servers running :0 on VT7 and :1 on VT9  unfortunately I can only have one of them displaying at a time, (yes I do have a working setup for 2 monitors/keyboards/mice)  basically to view the other X server I have to hit CTRL-ALT-F7 or CTRL-ALT-F9 from the currently focused keyboard.01:32
dcgdoes anyone have some suggestions?01:32
=== smspillaz|swap is now known as smspillaz
TariQMowafyhello03:07
TariQMowafyhello03:08
TariQMowafyanybody here?03:08
=== Bertrand is now known as bl8
=== oubiwann_ is now known as oubiwann
kklimondagood morning05:13
latenalhello, I need some help. I have a built-in blueotooth device. Few days ago it start to have trouble to connect to my handsfree but was ok with my cellphone. I tried to install/uninstall blueman and bluez and after few manipulations the daemon stopped working. I can't start it any more05:51
RAOF!support05:52
ubot2The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org and http://askubuntu.com05:52
RAOFYou'll probably get more help in any of those avenues.05:52
latenalthank you05:53
broderby the way, in case there was ever any doubt, NV-CONTROL is a really crappy protocol to work with05:58
broderon the plus side, i think the daemon i'm currently writing for work that tries to automatically handle hotplug events on NVIDIA is GPL tainted, so it might get to see the light of day :)05:59
RAOFOh!  Does NV-CONTROL actually generate hotplug events?  Cool :)06:04
broderno, but i'm polling for them :)06:05
brodergenerating useful events would be entirely too, well, useful for NV-CONTROL06:05
TheMusolol06:17
didrocksgood morning07:35
pittiGood morning07:57
Sweetsharkdidrocks, pitti: Good Morning!08:06
pittihey Sweetshark, moin moin!08:06
didrocksGuten Morgen pitti und Sweetshark08:07
glatzormorning mvo pitti08:09
pittihey glatzor08:10
pittiglatzor: great work on aptdaemon! looks really cool08:10
glatzorthanks pitti08:10
pittimvo: speaking of which, do you want to sponsor this? or want me to?08:12
pittirobert_ancell: hey Robert, good evening!08:13
* Sweetshark reboots08:14
mvohey glatzor! thanks for your mail08:14
mvopitti: I'm working on it currently, there is a test-failure left (but only on build anoyingly)08:15
pittiah, great08:15
* pitti hugs glatzor and mvo08:15
pittirobert_ancell: do you have some time to look into this webkit bug 710582?08:18
ubot2Launchpad bug 710582 in webkit "webkit crashes on amd64 architecture with SIGSEGV in WTF::OSAllocator::reserveAndCommit() was: webkit does not implement "assert" sanely" [Critical,Confirmed] https://launchpad.net/bugs/71058208:18
didrockshey glatzor, mvo08:23
glatzormorning didrocks08:23
mvohey didrocks08:27
robert_ancellpitti, not tonight but can tomorrow08:30
pittirobert_ancell: I was just wondering in general, depending on your current workload; if you are already overloaded, I'll look for someone else08:30
robert_ancellpitti, assign it to me08:32
pittirobert_ancell: ok, thank you08:33
jasoncwarnerhey robert_ancell, I think we are good on that meeting for tonight...no worries...pitti set my mind at ease ;)08:33
robert_ancelljasoncwarner, oh, np08:34
mvohey jasoncwarner, welcome back, isn't it terrible late in your TZ ?08:35
jasoncwarnerhey mvo, not terribly, ;)08:35
jasoncwarnerbut for what time I normally wake up, it is getting late!08:35
mvoheh .)08:35
didrockshey jasoncwarner08:43
jasoncwarnermorning didrocks!08:44
jasoncwarnerpitti tells me that you've been slacking ;)08:44
jasoncwarnersays you are never doing awesome things and never completely amazing him with your work ethic and dedication ;)08:44
pittiyeah, a whole 4 hours during his sleep!!!!08:44
Sweetsharkjasoncwarner: Oh, just a short question: What are your usual work hours currently? I know nothing is usual currently with all that exciting stuff going on, but I keep calculating timezones ... ;)08:45
jasoncwarnerSweetshark: I normally work San Francisco hours....08:46
jasoncwarnerwhich was easier to tell people when the clocked worked with timezones ;)08:46
didrocksjasoncwarner: yeah, totally slacking :)08:49
didrocksI +1 pitti08:49
didrockssorry, time for one of my 20 naps of the day :)08:49
jasoncwarnerha!08:49
pitti*chuckle*08:49
* pitti hugs didrocks08:49
* didrocks hugs pitti back08:50
pittididrocks: don't forget to watch Big Bang Theory in between them!08:50
SweetsharkWhen I met didrocks at FOSDEM he wasnt even sleeping ...08:50
didrockspitti: hehe, I have 3/4 episod late on the last season!08:50
didrocksyou see, unity destroy my life, I even can't keep up Big Bang Theory :)08:50
jasoncwarnerrock paper scissor lizard spock!08:50
pittididrocks: ah, I already caught up all the way until 4/1408:51
pittididrocks: I informed you thusly!08:51
didrockspitti: excellent, I'm still at 4/11 IIRC ;)08:51
pittiman, I love that show08:51
didrocksyeah, it's so nice :)08:52
didrocksI think now that I saw that one, I even prefer it than The IT Crowd08:52
didrocks(well, maybe not the "The Internet" episod) ;)08:52
Sweetsharkpitti: Dont be cruel, I got the first two seasons as DVDs from my brother for my birthday, but he insisted he would like to look them together with me. And he is currently in Ingolstadt helping making nice german cars during the week that prolongs stuff needlessly.08:52
pittiSweetshark: argh, poor you08:53
pittididrocks: yeah, me too; but at least I still have the 4th episode of IT crowd left to watch08:54
didrockspitti: oh right, I hadn't started watching the last season as well!08:55
SweetsharkIn my desperation I already stopped the DVD in one of the episodes we had already seen and analysed the physics on the whiteboards.08:55
didrocksSweetshark: and so? are things correct or is it nuts?08:56
Sweetsharkdidrocks: correct mostly08:56
didrockswithout any stop, it seemed to be correct as well, but I didn't analyse closly08:56
didrocksclosely*08:57
Sweetsharkat least the quantum mechanics stuff. Dunno about the string theory. Im not into esoterics ;)08:57
pittiSweetshark: at least you can live in the peace of mind that _nobody_ knows whether it's correct :)08:59
pittiso your guess is as good as anyone elses's09:00
didrocks(small notice: so, the invisible window bug is still there, but very very rare though… The good news is that *now* we have a reproducible test case \o/)09:02
pittiat least I'm using unity again since yesterday evening, and I haven't gone nuts again yet09:03
didrocksyou can trigger it in the classic session as well  ;)09:05
didrocksyou won't escape compiz bugs like that!09:05
didrocksbut agreed, the situation is way better09:05
pittididrocks: not in classic+metaicy :)09:06
pitti(which is what I was using)09:06
didrockspitti: that's cheating though :)09:06
pittiyou should try metaicy, it's yummy09:06
pittimetacity works as well, though09:06
didrocksI was using metacity the past last years TBH :)09:06
didrocks(just switched for a cycle to compiz when it was the new bling bling)09:06
dpmgood morning all09:17
pittihey dpm09:17
dpmhey pitti. It seems there's been some feedback of non-working FF lucid translations in the -proposed langpacks -> https://lists.ubuntu.com/archives/ubuntu-translators/2011-February/004395.html09:17
didrockshey dpm09:18
dpmheya didrocks :)09:18
pittidpm: oh, thanks; I'll remove that one from -proposed right away then09:19
dpmok, let's see if we get some more feedback09:20
pitti$ cat 10.04/whitelist.txt09:20
pittifi09:20
pittioc09:20
dpmhm :(09:20
pittidpm: I'm not entirely sure what the whitelist is, but that might not be a coincidence09:20
pittiis -oc broken as well?09:20
dpmit seems po2xpi is the culprit here then?09:20
dpmnot sure09:20
dpmlet me see if I can install a few in my lucid pc09:21
seb128hey09:25
didrockssalut seb12809:28
rodrigo_morning09:29
seb128hey didrocks rodrigo_09:31
seb128how are you?09:32
didrocksgood morning rodrigo_09:32
didrocksI'm fine, thanks, you?09:32
rodrigo_hi seb128, didrocks09:33
seb128didrocks, I'm fine as well, a bit late to start, I ran out for some errands before starting09:34
didrocksseb128: sunny days?09:34
didrocksor cloudy weather like in Lyon? :)09:35
seb128no, it's not sunny here, rather went out to get some coffee and something to eat09:35
seb128running out of breakfast stuff here ;-)09:35
pittibonjour seb12809:35
seb128hey pitti09:35
didrocksseb128: hehe, not a nice way to start the day, right. errands were mandatory then :)09:36
seb128I got coffee and cake so that's fixed, I can work ;-)09:36
seb128didrocks, did you get comments about the compiz update?09:42
seb128pitti, do you run again unity?09:42
pittiseb128: yes, I do09:42
pittisince the update last night09:42
didrocksseb128: yeah, still some invisible window issue09:42
seb128working fine?09:42
pittiseb128: no problems so far09:43
seb128didrocks, ok, as you thought09:43
didrocksseb128: but the good news is that we have a reproducible test case now09:43
seb128didrocks, using apport? ;-)09:43
didrocksseb128: no, synaptic :-)09:43
seb128I didn't try yet here but I get it almost every time I use update-manager and the polkit daemon crashes09:43
seb128which triggers apport and let compiz in a broken state09:44
didrocksyeah, it's really a criptic path that has been reported as well :)09:44
didrocksbut it "works" as triggering the bugs reliably09:44
didrocksbug*09:44
didrocksso nice :)09:44
seb128or rather than waiting for polkit to crash just hit esc on the password dialog09:44
seb128update-manager freaks out and freeze for 5 minutes and apport display a dialog and break compiz09:44
didrocksyeah, apparently, compiz just ask for paint rather than create create reparent…09:44
seb128didrocks, ok, great, it means sam can work on it now then?09:45
didrocksas it is thinking the window is already there09:45
didrocksyeah, he's already aware of that :)09:45
didrocksso, basically, 3 bugs before merging back the glib branch to trunk:09:45
Sweetshark.oO(apt-get build-dep libreoffice <= WooHa!)09:46
didrocks1. alt / tab being slow (almost finished)09:46
didrocks2. this invisible window09:46
didrocks3. test the new order with the sn_* crash09:46
seb128I get the sn_ crash every second login09:46
seb128would be nice to get it fixed ;-)09:47
didrocksmaybe removing my workaround with the new patch for it can be an help09:47
seb128Sweetshark, hey, what about it? hours of downloads? ;-)09:47
didrocksbut there is an ABI break and such…09:47
didrocksso I prefer rather than running untested stuff that it lands to trunk + make dist as we need to do that rebase09:47
Sweetsharkseb128: nah, downloads are fast here ...09:49
* Sweetshark has 100MBit downstream at home ...09:49
seb128didrocks, right09:49
seb128Sweetshark, that's quite a nice internet access indeed ;-)09:50
pittiSweetshark: wow, but you don't have a large "Uni Hamburg" plate on your front door, do you?09:50
Sweetsharkpitti: nope. Than it would even be faster. Uni Hamburg also has some huge IPv4 ranges. Good that they build DESY here before the dawn of the WorldWideWeb ...09:52
Sweetsharkwe got fibreglas connections around here and cable TV and phone are served over that connection as a sideeffect. 100MBit/s almost never get saturated for simple downloads as some server on the way will choke. bittorrrent is the only thing that lights up stuff completely ...09:58
=== zyga_ is now known as zyga
SweetsharkNo I was wondering about all the additional packages that got installed as I already build LO without them ;)09:59
Sweetshark... but that was without --with-system-libs ...10:00
seb128Sweetshark, right, debian and ubuntu tend to not like using lib copies10:01
seb128it means you have copies of the code to update every time you fix a bug or a security issue10:01
=== smspillaz is now known as smspillaz|dinner
=== kamstrup is now known as kamstrup|hackfes
SweetsharkIs there a policy that packages must build single-threaded? Because LO does and well, it could be a lot faster ...10:02
pittiSweetshark: no, the buildds use DEB_BUILD_OPTIONS=parallel=410:03
pittiSweetshark: most packages actually build with "debuild -j4"10:03
pittibut that also runs debian/rules in parallel10:03
pittiwhich the current LibO package fails on10:03
pittiSweetshark: but if you set the above, it'll be a lot faster indeed (replace 4 with your number of cores)10:04
pittiSweetshark: on my core i5 2.4 GHz/4 GB RAM, the last OO.o built in about 3 hours10:04
Sweetsharkseb128: sure, nobody likes it. But from a dev point of view it might make sense because you dont want to recompile LO everytime some system lib got updated (as LO is linking a lot of those, that would be pretty often)10:05
seb128Sweetshark, which is another reason to use the system libraries?10:06
seb128if they are dynamically loaded you don't need to rebuild l-o when a library is updated10:06
seb128if you use a copy you need to patch l-o and rebuild it...10:06
pittiSweetshark: yeah, it's actually considered a bug if a package includes copies of system libraries10:07
pittiif it's a security sensitive thing like poppler, zlib, or pcre, the security team haunts maintainers pretty severely (and rightly so)10:07
Sweetsharkseb128: In theory. In practice, API might change, LO might depend explicitly on an outdated lib or even might only run against a patched version ...10:09
Sweetsharkof course, Nothing of that should happen, but it does ;)10:10
=== kamstrup|hackfes is now known as kamstrup|hackfez
SweetsharkHmmm, another stupid question about the debian way of building: When I apt-get source, apt-get build-dep and then apt-get source -b so that it is build via dpkg-buildpackage, what does the unpacking of tarballs?10:41
pittiSweetshark: apt-get source -b is pretty much overkill there10:48
pittiSweetshark: apt-get source does the unpacking, through dpkg-source -x foo.dsc10:49
=== smspillaz|dinner is now known as smspillaz
Sweetsharkpitti: I just trying to get my head around all the stuff that happens "around" the "real" build by the build.pl up to a complete package.10:53
pittiSweetshark: build.pl?10:53
pittiSweetshark: the most low-level program you should be concerned about is dpkg-buildpackage10:54
pitti-S -> build source package, -b -> build binary pacakge10:54
Sweetsharkpitti: the build script in the LO build itself. Scary stuff.10:54
pittiI think most people use the "debuild" wrapper, which calls lintian and provides some extra configurability10:54
pittiSweetshark: ah10:54
pittiSweetshark: the entry point to building a source package is the debian/rules Makefile10:55
pittiSweetshark: for that I suggest to do the packaging tutorial first; trying to understand that stuff on the LibO package will be ... not easy10:55
SweetsharkSo one working set of commands would be: apt-get build-deps && apt-get source && dpkg-source -x && dpkg-buildpackage, right? Or is there anything missing in the chain?10:56
dpmpitti, I've had a quick look at some of the langpacks which have already been buit: es, bn, de, pt, pt_BR (same langpack), bn. In all of them firefox translations look ok to me (i.e. no obvious breakage). I could not install any other language, as the 'language-pack-LL' packages are still on the old version (I guess they haven't been built yet), and I get a conflict when trying to install the corresponding 'language-pack-LL-base', which is already on11:00
dpmthe latest version for most of the languages. So I'm not sure how the translator installed the Finnish langpack, and I'm not sure if he might have created the breakage himself11:00
* Sweetshark tries (but with replacing dpg-buildpackage replaced by dpkg-source -b in the unpacked dir)11:00
pittiSweetshark: apt-get source already unpacks the source, unless you add -d11:00
pittiSweetshark: dpkg-source -b is not what you want; you want debuild -b or dpkg-buildpackage -b11:01
pittiSweetshark: dpkg-source -b is a very low-level (i. e. not meant for users) interface for building a source pacakge, i. e. the diff.gz/dsc11:01
pittidpm: hm, might be your mirror which is behind? they all built over night11:01
pittidpm: this morning at 9 am the queue was empty11:02
dpmah, let me see...11:03
=== MacSlow is now known as MacSlow|lunch
Sweetsharkpitti: I want to go 'very lowlevel' to see what happens in each step that dpkg-buildpackage would do as per http://www.debian.org/doc/maint-guide/ch-build.en.html ...11:09
pittiSweetshark: essentially it calls "debian/rules build", then "debian/rules binary" (for binary builds)11:10
pittifor source packages, it cleans, calls dpkg-source -b, etc.11:10
pittibut it's not all that important11:10
SweetsharkI just want to get a feel where the magic happens ;)11:13
pittiSweetshark: which package do you use for studying this?11:14
Sweetsharkwhen I run dpkg-source -b . in the dir where I ran apt-get source, I get cannot open `./debian/changelog' for reading, which is to be expected as debian is in the subdir libreoffice-3.3.0 ...11:15
Sweetsharkpitti: libreoffice ;)11:15
pittiuh11:15
Laneymaybe 'hello' is a better place to start ;-)11:15
pittiSweetshark: yeah, you need to be in the source tree for every dpkg-buildpackage operation11:15
Sweetsharkwhen I am in libreoffice-3.3.0 (actually I tried that first), I get "no orig.tar file found"11:16
pittiyeah, hello is already nontrivial, and still uses plain debhelper11:16
pittiSweetshark: doc says dpkg-source -b <source dir>11:17
* pitti never used that himself11:17
Sweetsharkwhich is true, there is only a libreoffice_3.3.0.orig.tar.gz in ../11:18
Laneyactually the hello I just got doesn't even use debhelper at all o_o11:18
pittiindeed11:19
broderright - you want hello-debhelper :)11:19
pittiSweetshark: right, so dpkg-source actually does need to run outside the source tree11:19
Laneyso if you want low level then this might be good reading11:19
SweetsharkI just want to do the low level stuff once now, to get a feeling for it so I will not freak out should the need arise someday ...11:21
seb128rodrigo_, hey11:21
seb128rodrigo_, just read your comment, we already build tomboy without the applet enabled11:22
pittiseb128: hm, do you know what the new geoclue stuff is actually supposed to do? empathy doesn't show me the location of people anywhere11:22
seb128pitti, the indicator-datetime is supposed to show "do you want to change your tz" when travelling11:22
pittiah11:22
seb128pitti, set your tz to an u.s one and restart it11:22
seb128it should tell you "you are in germany, do you want to set that tz"11:22
seb128pitti, we don't build empathy with geoclue, it would require bringing in libchamplain to gets the maps etc11:23
pitti$ killall indicator-datetime-service; TZ=America/Chicago /usr/lib/indicator-datetime/indicator-datetime-service11:23
pitti(process:15280): Indicator-Datetime-WARNING **: Unable to create GeoClue address: Address interface already started11:23
pittihm, I guess it's very racy with the auto-respawn11:23
seb128pitti, it's likely you need to restart geoclue as well11:24
pittioh, indeed11:24
seb128pitti, it's rather geoclue which picks the tz11:24
pitti-ETOOMANYDAEMONS11:24
seb128the indicator just talk to geoclue11:24
pittihm, restarted geoclue-master, and it talked to Ubuntu GeoIP; now restarted indicator-datetime-service, but no question here11:25
seb128pitti, it should be a line in the indicator11:25
seb128not a popup11:25
pittinope11:25
seb128how did you change your tz?11:25
pittiI have them both in the foreground now11:26
pittiseb128: running the daemons with TZ=America/Chicago11:26
seb128not sure how they get the tz or if they respect that11:26
seb128or if they just read /etc/timezone or something11:26
pittithat'd be a bug11:27
pittibut let me try changing that11:27
* pitti changes it in time-admin11:27
pitti(process:15490): Indicator-Datetime-WARNING **: Unable to create GeoClue address: Address interface already started11:28
pittiI keep getting that11:28
pitti(process:15490): Indicator-Datetime-WARNING **: Unable to get Geoclue address: Geoclue master client has no usable Address providers11:28
pittianyway, I was just curious11:28
seb128pitti, ok, check with ken or ted when they are online, I didn't play much with it11:29
seb128pitti, I know it's supposed to show a "set the tz to ..." line in the indicator when it detects you are on a different tz11:29
pittiargh, argh! I have an invisible window again11:30
seb128pitti,11:31
seb128<smspillaz> oh, heh11:31
seb128 interesting workaround for the invisible window bug11:31
seb128 hide and show the desktop11:31
seb128pitti, try that maybe ;-)11:31
pittihow?11:31
seb128if you have a gnome-panel running put the "show desktop" applet11:31
pittiI don't11:31
seb128otherwise dunno11:31
seb128smspillaz, ^11:31
smspillazseb128: wassup ?11:31
seb128pitti, thereis probably a show desktop keybinding in compîz11:31
pittiand apparently the nasty window is on top of the unity panel, I can't even open the launche rnow11:31
smspillazseb128: pitti: Ctrl-Alt-D11:31
seb128smspillaz, how do you hide and show desktop to workaround this bug11:32
pittismspillaz: doesn't work11:32
seb128smspillaz, thanks11:32
smspillazI used the thing on the gnome-panel11:32
pittismspillaz: might only work with gnome-panel?11:32
smspillazpitti: might have changed11:32
seb128ctrl-alt-D works there11:32
smspillazshowdesktop handling is done within the wm11:32
smspillazpitti: ccsm -> general -> keybindings -> show desktop11:32
=== smspillaz is now known as smspillaz|eating
rodrigo_seb128, yes, found out the peditor stuff is in libgnome-cil, that's where the dep comes from11:33
rodrigo_seb128, so moving those files to gconf-cil and testing11:33
pittismspillaz|eating: thanks, I used gnome-keybinding-properties and that worked (it was Mod4+D before)11:33
pittifound a time-admin window hiding itself11:33
smspillaz|eatingok11:34
pittinice11:34
smspillaz|eatingpitti: yeah we've got a reproducible test case now so I'm going to look into it tonight11:34
* pitti calls that "sanity key"11:34
seb128rodrigo_, well I assumed it was in libgnome-cil for a reason, that's why I asked you if we could move to plain gconf#11:34
seb128rodrigo_, but if we can move it to another binary nice11:34
seb128rodrigo_, check with Laney or pkgcli guys maybe though11:35
rodrigo_seb128, yes, I guess it's there for some reason, not sure which though, so yes, testing11:35
rodrigo_Laney, ^11:35
Laneyyou could split the peditors assembly out into another package yeah11:36
LaneyI don't know if that would save you anything on the dep chain, but it's worth a try11:36
seb128is there a way to do the equivalent of "ldd" on mono bindings?11:36
seb128i.e to see what peditor depends on11:36
Laneygive us a patch in Debian and we'll take it11:36
SweetsharkIn case anyone is interested: mkdir foo && cd foo && apt-get source libreoffice && dpkg-source --before-build libreoffice-3.3.0 && dpkg-source -b libreoffice-3.3.0 && make -C libreoffice-3.3.0 -f libreoffice-3.3.0/debian/rules build11:37
Laneymonodis --assemblyref I think11:37
seb128Laney, thanks11:37
seb128Laney, well, it would save "Name=gnome-vfs-sharp"11:37
seb128coming from /usr/lib/cli/gnome-sharp-2.24/gnome-sharp.dll11:37
Laneyis that where your problematic dep comes from?11:38
seb128doh11:38
seb128the peditor one depends on gnome-sharp11:38
Laneyif peditors depends on gnome-sharp thoug...11:38
Laneyyeah, :(11:38
seb128right11:38
seb128that brings the gnome-vfs stack in11:38
rodrigo_seb128, the peditor stuff is in libgnome-2.24-cil11:39
rodrigo_in the upstream source code, they are with the gconf 'basic' bindings11:39
seb128rodrigo_, yes, but it doesn't make sense to split it out since gconf-sharp-peditors.dll depends on the gnome-sharp.dll11:39
seb128rodrigo_, which depends on gnome-vfs11:39
rodrigo_doesn't seem to depend on gnome-sharp.dll11:39
* rodrigo_ re-checks11:39
seb128rodrigo_, monodis --assemblyref /usr/lib/cli/gconf-sharp-peditors-2.24/gconf-sharp-peditors.dll11:40
Laneyrodrigo_: try monodis --assemblyref /path/to/dll | grep Name11:40
seb128        Name=gnome-sharp11:40
Laneyyou can see it probably with "using Gnome;" in the sources11:40
Laneyit probably follows the c lib11:40
seb128$ monodis --assemblyref /usr/lib/cli/gconf-sharp-2.0/gconf-sharp.dll | grep Name11:40
seb128Name=mscorlib11:40
seb128Name=glib-sharp11:40
seb128that one is better ;-)11:41
LaneyI don't know the API at all, but maybe you can replicate it on top of gconf#11:42
seb128pitti, https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/71544511:43
ubot2Launchpad bug 715445 in ubuntu-geoip "indicator-datetime doesn’t get geoclue information from ubuntu-geoip-provider" [Undecided,New]11:43
pittiseb128: ah :)11:43
seb128pitti, you might get that bug11:43
rodrigo_right, it indeed uses some Gnome. stuff, just for the filepicker button11:43
rodrigo_I guess we can just change that to use Gtk.FileChooser11:43
seb128rodrigo_, is that exposed to the clients? i.e would that be an api, abi breakage?11:44
rodrigo_not exposed, afaics11:45
seb128rodrigo_, did you talk to upstream tomboy about that?11:45
seb128just to know what they think11:45
rodrigo_seb128, yes, but it's got nothing to do really with tomboy, tomboy just uses the PropertyEditor objects in gconf#11:46
Laneyddd11:46
seb128rodrigo_, well, it uses an api which use libgnome11:46
rodrigo_yes, but lignome usage is internal to gnome-sharp11:46
seb128rodrigo_, so they need to clean that in some way, either by moving away from propertyeditor or by changing the bindings11:46
seb128rodrigo_, right, so either we move the issue to gnome-sharp11:47
rodrigo_yes, changing the bindings is the easiest, it seems11:47
seb128or we port tomboy to not use propertyeditor11:47
rodrigo_the usage of PEditor in tomboy is huge11:47
seb128bah11:48
seb128so it means gconfpeditor should be updated to stop using libgnome11:48
seb128then the libgnome2.24-cil should be splitted11:48
Laneyit would be an api break as far as i can see11:48
seb128or the gconfpeditor binding moved with gconf#11:48
Laney        void Changed (object obj, Gnome.ColorSetArgs args)11:49
rodrigo_yeah, indeed11:49
seb128k11:49
seb128tomboy really need to stop using gconfpeditor11:49
seb128to switch to gsettings or something11:49
seb128rodrigo_, just forget about it for this cycle then, porting tomboy to gconf# seems work over what it's worth11:50
rodrigo_ok, but I'll change the description of the bug11:50
seb128shame because it's the only thing keeping libgnomeui and libgnome on the default install11:50
seb128rodrigo_, can you check with upstream what are they gnome3 plans anyway?11:50
seb128they need to stop using libgnome some day11:50
seb128using gsettings or something else11:50
rodrigo_seb128, sure11:50
seb128thanks11:51
Laneythe mono gi stuff is currently being hacked on11:51
Laneyso we should be able to get better bindings in the near future11:51
seb128those will be really welcome11:52
seb128it sucks to be stucked with old libs because mono is so behind11:52
seb128ups11:52
seb128Laney, btw is there any plan in debian to update mono from 2.6 to 2.8?11:53
seb128Laney, or alternatively any reason why 2.6 is better?11:54
Laneywe are skipping to 2.10 and it's being worked in git currently11:55
Laneymost of the work was on polishing for squeeze11:55
seb128ok...11:56
seb128is 2.10 out yet? will that land in debian before natty feature freeze or not?11:56
seb128just trying to figure what we should do in natty11:56
seb128hum, lunch time11:56
Laneyit's on RC2 currently, and no probably not11:56
seb128ok11:56
seb128so I guess stay on 2.611:56
seb128thanks11:56
=== artir is now known as Artir
dpmhey didrocks, are you still having issues ssh'ing to people.canonical.com? I am having them now, but I want to confirm it's not just me before asking IS12:16
didrocksdpm: just tried, it seems to be okayish… the ssh connectin hasn't dropped for a minute…12:17
dpmok, thanks didrocks12:18
dpmah, it just worked for me right now as well12:19
didrocksseems that there are some underlaying network issue in any case…12:20
=== MacSlow|lunch is now known as MacSlow
seb128rodrigo_, did you confirm the vino issue or just reopened the bug to track it?12:32
=== smspillaz|eating is now known as smspillaz
rodrigo_seb128, confirmed it, and found it seems to be an avahi issue12:33
rodrigo_seb128, see my last comment12:33
seb128rodrigo_, ok, emails are lagging behind, I just got the one about the bug being reopen and assigned to you12:35
rodrigo_seb128, my comment: "Following DaveHansen's comment, if you stop avahi daemon, no CPU high usage. Ditto if you restart avahi daemon again after having stopped it. So seems it's indeed an avahi problem"12:35
seb128just read the comment on launchpad12:35
seb128rodrigo_, yeah, got it now, thanks ;-)12:35
rodrigo_I'm debugging avahi-daemon now, although it seems I'll need to restart the session12:36
rodrigo_can't get it to use 100% cpu now12:36
rodrigo_well, 40% for me, rather than 100%12:36
seb128I usually get the issue by running vino-preference and checking, unchecking the checkbox to share12:37
=== evilvish is now known as vish
rodrigo_seb128, yes, me too, but after restarting avahi-daemon, can't12:38
dpmpitti, chrisccoulson, ok re: the lucid-proposed language packs, it seems that FF translation breakage only affects the whitelisted languages in po2xpi (that's 'fi' and 'oc').  I've reported it on bug 71573312:39
ubot2Launchpad bug 715733 in po2xpi "XPI files are not correctly built for whitelisted templates" [Undecided,New] https://launchpad.net/bugs/71573312:39
seb128chrisccoulson, current firefox failed to build on armel and powerpc, fix it! ;-)12:47
seb128didrocks, current unity failed to build, fix it ;-)12:47
didrocksseb128: trunk or the package?12:48
seb128if you wonder about those it's thanks to robert_ancell who made build failures be listed on http://people.canonical.com/~platform/desktop/versions.html12:48
seb128didrocks, 3.4.0-0ubuntu212:48
seb128didrocks, though a retry now that glew is fixed might work?12:48
seb128let me try that12:48
chrisccoulsonseb128 - one step ahead of you already ;) http://bazaar.launchpad.net/~mozillateam/firefox/firefox-4.0.head/revision/75912:49
didrocksseb128: yeah, it was due to glew12:49
didrocksseb128: I didn't retried on purpose, thinking that for such a small fix in alpha2, it will prevent people pushing their bugs with apport12:49
didrocksnow, I think it's fine12:49
seb128didrocks, ok, let's try then12:49
seb128chrisccoulson, ok, you are fine for this time but we are watching you :p12:49
didrocks(taking the predicate that apport is basing the version on the published binary )12:49
chrisccoulsonheh :)12:50
didrockshope that the second time I'm fixing the same issue in glew will be the latest12:50
seb128didrocks, there is a new glew in debian btw12:50
seb128should we sync? ;-)12:50
didrocksseb128: just look if the .pc file requires glu :)12:51
didrocksthen, for driver issue, I'm not there anymore \o/12:51
didrocksmaybe better to wait on an unity release to blame dx :)12:51
didrockslike "I updated glew and unity and unity doesn't run!" :)12:52
seb128lol12:52
seb128yeah ;-)12:52
didrocks(I can also update compiz too to add to the confusion ;))12:52
Sweetshark\o/ the libreoffice package finished to build ...13:02
Sweetshark... kinda ...13:02
Sweetshark... well, it chrashes in smoketest, but thats what smoketests are for, right?13:03
pittidpm: thanks; so let me remove them from the whitelist and rebuild these two13:17
dpmpitti, ok. Could you please also remove the 'ca' language packs from lucid-proposed? They are failing as well (Firefox in English, no FF translations in the langpack), but probably for some other reason13:18
pittidpm: ah, oc and fi's mozilla.tar.gz are unpacked, while the others have a XX.jar archive13:23
mvodidrocks: what is the best way to test oneconf when you only have one machine?13:29
mvodidrocks: is there something like FAKE_MACHINE=1 ;) ?13:29
pittiVMs?13:30
didrocksmvo: I think I wanted to implement that, not sure I've done, let me check :)13:30
didrocks        # faking this id for testing purpose13:31
didrocks        #self.hostid = 'BBBBBB'13:31
didrocks        #self.hostname = "foomachine"13:31
didrocksin oneconf/hosts.py13:31
didrocksmvo: ^13:31
didrocksjust uncomment to override real values :)13:31
didrocksthen oneconf-query --update to get a first set13:31
mvocool, thanks didrocks13:32
cyphermoxhey didrocks13:41
mterryseb128, still able to crash reliably?  I have a test package for you to try13:41
seb128mterry, hey, just tried, first try, first crash13:42
seb128so I guess it's a "yes" ;-)13:42
mterryseb128, https://launchpad.net/~mterry/+archive/ppa13:42
didrockshey cyphermox13:42
cyphermoxdidrocks, about my issues with building unity ;) what I was referring to was specifically using  "bzr bd" to locally build a deb for hacking. I'm aware it's no good for making sure that it builds cleanly, but it's fewer steps for hacking and testing than bzr bd -S && pbuilder, for example13:43
seb128mterry, do you have a vcs for it?13:43
mterryseb128, it's got a new version of libdbusmenu with a patch that avoids freeing a particular object.  It quieted a lot of warnings about trying to disconnect signals from invalid objects for me13:43
seb128mterry, don't bother I will grab the debdiff13:43
mterryseb128, not yet, but will have one in a sec13:43
didrockscyphermox: right, but you have a FTBFS, right?13:43
mterryseb128, ok13:43
didrockscyphermox: I think it's related to your branch13:43
seb128mterry, I just want to build locally so I still have the dbgsym for it13:43
didrockscyphermox: or you can, for hacking installing unity13:43
didrockscyphermox: then, with next release, unity --distro to remove all the cruft13:44
seb128we need soyuz dbgsym support13:44
cyphermoxdidrocks, it fails if I take lp:~ubuntu-desktop/unity/ubuntu ;)13:44
seb128didrocks, is anybody else than you is able to build unity?13:44
pittidpm: I uploaded (hopefully) fixed -oc and -fi langpacks to lucid-proposed13:44
seb128didrocks, you are sure you don't have a special compiz environment set?13:44
didrocksseb128: you were, I didn't change the packaging though13:44
seb128didrocks, not I'm not13:44
didrocksnothing in my env13:44
seb128it try to install to debian/$curdir/$destdir13:45
didrocksseb128: like, it's not building for you?13:45
cyphermoxdidrocks, the issue is really that somehow, unless I set COMPIZ_DESTDIR, stuff gets installed in an invalid path13:45
seb128remember?13:45
didrockscyphermox: COMPIZ_DESTDIR shouldn't be used13:45
dpmpitti, ah, cool. Did you read the message about the 'ca' ones above? ^ I don't know what's going on there, so for now I think it might be best just to remove it from -proposed13:45
didrockscyphermox: it's breaking COMPIZ and other wrapper13:45
didrockscyphermox: we will remove it as told13:45
cyphermoxdidrocks, I realize it might not be a good idea, just saying it "works" for now13:45
pittidpm: yes, I removed it13:45
didrocksseb128: and there was no issue in a pbuilder, right?13:45
seb128didrocks, we did chat a bit about that a few weeks back13:45
dpmpitti, ok, thanks13:46
pittidpm: I responsed, but apparently you got hit by DSL reconnect or so?13:46
seb128didrocks, didn't try pbuilder but it builds on the buildds13:46
didrocksseb128: yeah, I remember now, I would say that you have something in your env then :)13:46
seb128didrocks, ok, I though you were discussing similar issues13:46
didrocksfor the same reason I can't build nux here, but ona pbuilder it works13:46
seb128I will go back in my corner13:46
dpmpitti, yeah, sorry, I didn't get the response13:46
didrockscyphermox: setting COMPIZ_DESTDIR is a workaround that is bad. The thing is to find what causes that to you13:47
didrocksI build unity in another box to check as well13:47
didrocks(a clean install)13:47
didrocksit's working as well13:47
cyphermoxdidrocks, there is nothing I can think of in env that would cause this -- I'm trying another box now13:47
didrockscyphermox: yeah, please, keep me posted13:47
=== oubiwann is now known as oubiwann_
cyphermoxdidrocks, I'll try on a live session jsut for you ;)13:47
seb128didrocks, it's weird, this box has for sure nothing not coming from the distro13:48
ari-tczewis there anyone familiar with gnutls26 ?13:48
ari-tczewI'm going to upgrade this package and looking for concerns, if so.13:48
didrocksseb128: yeah, there should be something, if someone with a box providing this issue wants to investigate13:48
didrocksbut not setting COMPIZ_DESTDIR :)13:48
seb128it's a weird one13:49
cyphermoxdidrocks, I'm getting a usb key ready, then I'll post full bzr bd logs from a clean copy of lp:~ubuntu-desktop/unity/ubuntu13:49
seb128seems cmake related13:49
didrocksseb128: yeah, as my nux and doxygen not building :/13:49
seb128but I don't know enough about cmake to debug it13:49
didrockscyphermox: excellet13:49
didrocksseb128: all the compiz cmake should be rewritten, honestly…13:50
seb128ari-tczew, no one here13:50
cyphermoxseb128, it is, somehow it's detecting compiz's install path wrong, but I'm convinced it's not env13:50
didrocksI spent enough time to just make it works aleady13:50
didrocksalready*13:50
Amaranthdidrocks: Hey, I like the compiz build system :)13:56
AmaranthThe way plugin building is setup mainly13:56
didrocksAmaranth: well, it's broken…13:56
didrocksneeds a good refresh and refactoring13:56
AmaranthYou can pull a single plugin out and build it standalone but core know how to handle them all as well with the same CMakeLists.txt13:57
didrocksyeah, this part is good :)13:57
didrocks(and we use it)13:57
Amaranthalthough some of it ended up being the usual build system hacks on top of hacks13:57
* bcurtiswx waves to room14:07
seb128hey bcurtiswx14:12
seb128mterry, ok, seems to fix it, I tried 6 times without issues14:12
seb128mterry, it crashed every second time in average before14:12
seb128mterry, I will keep playing a bit with it but seems to work14:13
mterryseb128, sweet.  Now I have to figure out how to make a real patch vs that quick fix14:13
seb128bcurtiswx, the m-c bug you emailed me about, not sure it's really a bug...14:13
seb128mterry, do you know what is wrong or do you need a valgrind log pointing it?14:14
seb128mterry, I guess valgrind would show the issue14:14
bcurtiswxseb128, OK, thanks for looking at it :)14:14
seb128kklimonda, hi.14:14
mterryseb128, no, I know the issue...14:14
seb128mterry, ok, great, let me know if you need testing for the proper fix later on then14:14
mterryseb128, when the app's menu items are finalized, they try to disconnect from the accel group that the dbusmenu client is holding14:14
mterryseb128, I just haven't been able to find the appropriate point at which to let go of the accel group yet14:15
seb128ok14:15
mterryseb128, I shouldn't need further testing.  I see warnings when I hit the bug, it just doesn't crash like it does for you.  So as long as I can make those warnings go away, I'm good14:15
seb128mterry, ok, excellent14:16
kklimondaseb128: hey14:16
seb128kklimonda, how are you?14:16
didrockscyphermox: did it build?14:16
cyphermoxdidrocks, didn't get to it yet, my iso from yesterday would oops.14:17
kklimondaseb128: a bit tired, just got back from a long walk and I'm trying to  make a fire in the fireplace ;)14:17
seb128heh, some exercice!14:18
seb128kklimonda, bug #715046, do you want to work on it?14:18
ubot2Launchpad bug 715046 in transmission "[Natty] Update Transmission to version 2.21" [Undecided,New] https://launchpad.net/bugs/71504614:18
seb128kklimonda, if so can you tag it desktop-upgrade and assign it to you?14:18
kklimondaseb128: I will work on it, but it may not be possible to update it in natty.14:19
seb128kklimonda, why?14:19
seb128kklimonda, well in any case just comment on the bug if it's not14:19
kklimondaupstream has decided to use the new libevent, which isn't completely API comptaible with the old one, and I can't couldn't fix all packages that depend on the old libevent so far.14:20
seb128kklimonda, can we use the new one with the commit requiring the new libevent reverted?14:21
kklimondawhoa, nothing like a 4 second lag to make what your write sound like a complely blabbering ;)14:21
kklimondaseb128: I don't think it's worth an effort (the rewrite has been one of the most important things in 2.20) but I'll take a look when I'm back, and ask upstream to reconsider bundling libevent2 in their source, like they did before with libevent1. We could also consider doing it ourselves.14:22
seb128kklimonda, well in any case if you tag and assign the bug that will avoid work duplication14:23
seb128so maybe just drop a comment on the bug saying what you wrote there?14:23
seb128kklimonda, thanks14:23
kklimondayes, I'll coment on the bug in a minute.14:24
kklimondaat least assign it to myself, I'd like to ask T dev about rebundling libevent2 before I I do any more commenting :)14:24
cassidyhey guys. Any plan to ship glib-networking? You need it to be able to use proxies in Telepathy14:32
didrockskiwinote_: hey, are you around?14:37
kiwinote_didrocks: yep14:37
didrockskiwinote_: I was wondering if you can shed some light on the -2 magic :)14:38
lamalex_bryceh, is there any eta on nvidia drivers?14:38
didrockskiwinote_: in the ref count, when there is a direct match to the serach14:38
kiwinote_didrocks: um yeah, that's a bit quirky14:38
kiwinote_didrocks: I aren't quite sure, but I think the query consists of different parts, and on each iteration the nr_pkgs, nr_apps counters aren't reset14:39
kiwinote_didrocks: I made that change because it would seem to give correct results now, if it disadvantages any oneconf stuff, just let me know14:40
didrockskiwinote_: no, I'm fixing other stuff for oneconf, but the match seems correct now14:40
didrockskiwinote_: so, I was just unfortunate that pkgs - apps was exactly the right count. I was assuming pkgs was the total, not only technical items :)14:41
didrocksI was quite curious of the fix though14:41
kiwinote_didrocks: yeah - in maverick the nr_pkgs was the total of all pkgs and apps, but that's changed now14:41
didrockskiwinote_: right ;) well, I'm adapting to it, but the "look at the total result if there is no app found" is giving me some headaches :)14:42
seb128cassidy, is that in debian? we could just sync it if that's there14:53
cassidyit is14:53
cassidyI'm trying to open a lp bug about that since 10 minutes..14:53
cassidybut I'm always redirected to https://help.ubuntu.com/community/ReportingBugs14:53
chrisccoulsondoes anybody actually use thunderbird? i've had no bugs about the menus so far. not sure if that's good or bad ;)14:55
kenvandinechrisccoulson, hehe... there are always bugs :)14:57
seb128cassidy, right, we turn off bug reporting for non bugsquad by default14:57
cassidydidrocks, rahh I could have spend my day on this :p14:57
seb128cassidy, see the ?no-redirect url in the wiki14:57
cassidyI tried, didn't work14:57
didrockscassidy: I know that, hence the ?no-redirect pointer I gave you14:58
seb128cassidy,     http://bugs.launchpad.net/ubuntu/+filebug?no-redirect14:58
seb128doesn't work?14:58
cassidyit does !14:58
* cassidy blames didrocks14:58
didrockswhy?14:58
cassidy<didrocks> c'est le ?no-redirec la magie14:58
seb128lol14:58
seb128with a "t"14:58
seb128cassidy, subscribe ubuntu-sponsors to the request while you are at it14:59
cassidyisn't that a bit too complex to just report a bug ? :\14:59
seb128cassidy, well usually you use "report a bug" in the menus14:59
seb128or ubuntu-bug14:59
seb128which collect infos etc for you14:59
didrockscassidy: I told you it's written on https://help.ubuntu.com/community/ReportingBugs :p15:00
seb128cassidy, the goal is to discourage opening bug without apport since those lack infos15:00
cassidyyeah but ubuntu-bug doesn't work for the ubuntu component15:00
didrockscassidy: ubuntu-bug without anything15:00
cassidyyeah didn't work, there is "I want to report on Ubuntu"15:01
cassidyit asks if that's a security, X issue, etc15:01
seb128hum indeed15:01
seb128well those are sort of a corner case15:01
seb128but seems an apport bug as well15:01
seb128you can probably open a bug on apport about it15:02
seb128seems it should be working15:02
cassidyseb128, didrocks: bigon: https://bugs.launchpad.net/ubuntu/+bug/71582115:02
ubot2Launchpad bug 715821 in ubuntu "Sync glib-networking from Debian" [Undecided,New]15:02
didrockscassidy: thanks15:02
bratschedidrocks around?15:21
didrocksbratsche: yes?15:21
seb128hey bratsche, how are you?15:21
bratschedidrocks: I was told I should ping you and let you know I'm trying to get libgrip into universe.  I submitted a request here: https://bugs.launchpad.net/ubuntu/+bug/71583015:22
ubot2Launchpad bug 715830 in ubuntu "New Source Package: libgrip" [Undecided,New]15:22
bratscheHi seb128, I'm okay.  How are you?15:22
seb128bratsche, I'm fine thanks15:22
didrocksbratsche: ok, I can check the package and look at it, thanks :)15:22
bratschedidrocks: Thanks!15:22
didrocksbratsche: not exactly right now, but later today or tomorrow15:22
bratscheSure, no worries.15:23
didrocksyw ;)15:23
rodrigo_in which branches are the maverick packages?15:36
dobeyrodrigo_: lp:ubuntu/maverick/$sourcpkgname15:39
dobeyrodrigo_: or did you mean something else?15:39
rodrigo_dobey, that's what I mean, but the gtk package is not there15:40
seb128rodrigo_, we don't keep stable vcs for most of the desktop things15:40
seb128we don't work enough on stable versions to do that15:40
rodrigo_right, but I thought they were pushed to maverick branches automatically15:41
seb128rodrigo_, so I guess you need to checkout the revision before we started worked on natty or check the sru version control15:41
* Sweetshark just got work: http://cgit.freedesktop.org/libreoffice/build/tag/?id=libreoffice-3.3.1.115:41
seb128rodrigo_, well the autoimport will work, what dobey said15:41
dobeyrodrigo_: it looks like it is there to me15:41
dobeyrodrigo_: https://code.launchpad.net/~ubuntu-branches/ubuntu/maverick/gtk+2.0/maverick15:41
rodrigo_ah, it's gtk+2.015:41
dobey:)15:42
SarvattMacSlow: any chance you could merge https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/654921 somtime? been blocking a pixman update on that getting fixed since it will look ugly15:43
ubot2Launchpad bug 654921 in notify-osd "Black border in the notifications when effects are turned off" [Undecided,Confirmed]15:43
jcastrochrisccoulson: when in the cycle do you plan on landing appmenu for firefox?15:44
MacSlowSarvatt, on the weekend I will address notify-osd... right now there's still unity-features on my plate that need to land before the weekend15:45
Sarvattsounds good, thanks for taking a look at it! pixman wasn't building with our GCC for a few months anyway so no rush, just would like to update it before natty release because it has quite a few speedups for the people using ARM systems15:46
dpmpitti, ok, it seems that the problem might not be with po2xpi, but with the exported files from LP: bug 71585416:00
ubot2Launchpad bug 715854 in launchpad "Exported Firefox translations contain wrong references to languages other than the current" [Undecided,New] https://launchpad.net/bugs/71585416:00
seb128kenvandine, mterry: it's getting hard finding appmenu issues!16:04
mterryseb128, yay16:04
seb128I've been triaging the bugs and playing it there, only find really minor issues16:04
seb128mterry, seems there is one issue with icons, interested by working on it?16:05
mterryseb128, sure16:06
seb128mterry, ok, I will open a bug and assign it to you16:06
seb128mterry, nautilus "go" menu has no icons for the standard locations16:06
seb128computer, trash, etc16:06
seb128u1 in the file menu also has an icon where it doesn't in the normal menu16:06
seb128mterry, I've set APPMENU_DISPLAY_BOTH=1 in my session to test16:07
seb128comparing both menus16:07
mterryseb128, weird, cool.  assign me up16:08
seb128mterry, bug #71586416:11
ubot2Launchpad bug 715864 in indicator-appmenu "icons not always displayed as they should" [Undecided,New] https://launchpad.net/bugs/71586416:11
cyphermoxdidrocks, I can't reproduce it on a live session -- seems like somehow once my environment is all set for building packages, there's a difference from an install of just bzr, bzr-builddeb and unity build-deps16:11
didrockscyphermox: right, if you see something, do not hesitate to ping me :)16:11
cyphermoxdidrocks, I did see something16:11
didrocks(I'm using bzr bd as well)16:12
didrockscyphermox: oh? a fix?16:12
cyphermoxlooks like changing COMPIZ_PLUGIN_INSTALL_TYPE to compiz from package will get good results, but I guess that might break something else16:12
cyphermoxalso didn't try that on buildds or pbuilder yet :/16:13
rodrigo_oh, accountsservice from the gnome3 ppa is now in universe?16:13
seb128rodrigo_, right, got synced from debian16:13
rodrigo_cool16:13
cyphermoxdidrocks, seems like something is setting both DESTDIR and COMPIZ_DESTDIR, which is why the paths are doubled there when the plugin gets installed (in the bug I filed)16:13
didrockscyphermox: wait? I didn't set it to package?16:13
cyphermoxdidrocks, no, you did16:13
didrockscyphermox: yeah, hence my "COMPIZ_DESTDIR is broken"16:14
didrockspackage is what should be set16:14
didrocksto get the right debug options triggeed16:14
didrockstriggered*16:14
didrocksand so generating -dbgsym16:14
cyphermoxright16:14
cyphermoxbut nah, it still didn't work anyway16:14
cyphermoxdidrocks, the issue is that here DESTDIR is already set, but in CompizPlugin.cmake COMPIZ_DESTDIR also gets set to DESTDIR -- in the same file, the plugin is set to be installed to ${COMPIZ_DESTDIR}/somethingsomething16:16
didrockscyphermox: I know, but CompizPlugin.cmake set COMPIZ_DESTDIR only in Compiz mode normally16:16
didrocksnot package one16:16
cyphermoxhm16:17
seb128ok...16:19
seb128mterry, do you know where is the code to display the "close" item for dialogs which don't have a menu to display?16:19
mterryseb128, I believe in indicator-appmenu16:19
seb128mterry, ok, can you confirm the "close" entry is inactive on i.e vino-preference16:20
mterryseb128, works for me16:20
seb128hum, k16:20
seb128mterry, it seems random there but is the entry is unactive for quite some capplets there16:22
seb128does it work for others?16:23
seb128didrocks, pitti, rodrigo_: ^16:23
desrtmterry: 0.7.2 makes you happy?16:24
rodrigo_seb128, hmm, 2.32 capplets you mean?16:24
seb128rodrigo_, yes, well dialogs which don't have a menu, gnome-mouse-properties, vino-properties, alacarte, etc16:25
mterrydesrt, except for https://bugzilla.gnome.org/show_bug.cgi?id=640683 yes16:26
ubot2Gnome bug 640683 in gsettings backend "Mutex deadlock on unsubscribe" [Normal,Unconfirmed]16:26
rodrigo_seb128, I have gcc 3.0 here, but for vino-preferences, it's not inactive16:26
mterrydesrt, but I have worked around that for my case, and I think it's a hard-to-reproduce one16:26
seb128rodrigo_, ok, thank you16:26
desrtthat's probably gdbus, right?16:26
seb128rodrigo_, small issue but I will watch for it16:26
rodrigo_seb128, you're welcome :)16:26
* desrt catches up on the bug16:27
mterrydesrt, either that or how dconf uses it16:27
desrtmterry: we have another bug open about 'use of gdbus' too :)16:27
desrtBut notably, these widgets don't make an attempt to avoid setting a value if16:30
desrtthat same value is in GSettings already.16:30
desrtmterry; :(16:30
desrtdoes that include when the initial value of the widget is set (ie: when starting up the app?)16:31
desrtif so, it's **very** broken16:31
pittihey desrt, how are you?16:32
desrtpretty good16:32
desrtgot a fun project this week :)16:32
desrtso i'm happy :p16:32
pittidesrt: FTR, my pygobject patch for gsettings landed :)16:32
pittidesrt: oh, what are you doing?16:32
desrtwhat're you working on?16:32
desrtNICE16:32
desrtthe settings['key'] = (1,2,3) thing?16:33
pittidesrt: the "dict-like settings object", yes16:33
desrtdid you do the automatic type hinting for the GVariant construction?16:33
pittidesrt: we are currently discussing how/when to release16:33
pittidesrt: yes, with the get_range() thing; although only with some limited support16:33
desrtwhat limits?16:33
pittidesrt: I only support the "type" range16:34
desrtbtw: you can use the information from get_range() to ensure you never make a call that issues a g_critical() or aborts16:34
desrtah.  i see :)16:34
pittidesrt: I haven't had time yet to implement the others (range/flags), they just throw a NotImplementedError for now16:34
pittiI think that's ok given that code which uses that is mostly 'static'16:34
desrtwould be really nice if you could throw a range exception for the others16:34
desrti guess you already throw a type exception if gvariant conversion fails?16:35
pittidesrt: once they are implemented? yes, shoudl be a ValueError then16:35
pittidesrt: yes16:35
desrt(which should automatically ensure that you always have the right type...)16:35
desrtthat's really slick :)16:35
desrtbrings us somewhere close to the QML API now16:35
pittidesrt: yeah, I noticed that the current gvariant implementation is very sensitive -- one false step and BANG! you program crashes16:35
desrtexcept that python has no convention for monitoring property values for changes, unfortunately16:36
pittidesrt: that's why I need to do rather expensive "does this key exist" tests before calling set_value() etc.16:36
desrtpitti: i went through a phase a year or so ago about "WTF is with all of these g_critical() errors in my xsession-errors"?16:36
desrtwhich motivated me to turn all of my g_criticals into asserts :)16:36
AmaranthOr get people to run with GDEBUG again16:37
Amaranthcritical-errors or whatever16:37
desrtthe best suggestion i heard is to sleep(10) on each g_critical :)16:38
* desrt . o O ( wonder how long it takes for you guys to vendor-patch that one out )16:38
mterrydesrt, right, my app didn't have any smarts to avoid the changed-set cycle on startup.   I would argue that using the api like that shouldn't cause a bug, but it was inefficient16:39
desrtanyway... it's vaguely on my list of things to do to go through and turn a lot of those asserts into return_if_fail()s16:39
mterrydesrt, is there a reason that dconf doesn't guard against that for apps?16:39
desrtmterry: it's sometimes difficult for dconf to know what is already in the database16:40
desrtsince some changes might be in-flight16:40
desrtit's not really a problem of what ends up in the database at the end of it all because that's inherently a simple (non-buggy) race16:41
desrtbut it's an issue of ensuring that the state of the widget is consistent with what the final value ends up being16:41
desrtand it's not always possible to ensure that we'll always see a change signal after the skipped set request16:41
desrtlast time i looked at it i was unable to convince myself that it would be 'safe' in all cases16:42
=== alecu is now known as alecu-lunch
desrtwe also need to carefully make the distinction about the meaning of writing a setting which is equal to the value of the setting in the systems-wide default database16:44
desrtsince probably we *do* want to write those even still16:44
desrtthe rule for app authors is quite simple, though: only do GSettings writes in response to explicit user action16:44
ogradidrocks, tickle16:45
* desrt should document that16:45
didrocksogra: hey16:46
ogradidrocks, the unity-2d team asked for two more patches to be included in metacity16:46
ograhttps://code.launchpad.net/~unity-2d-team/unity-2d/metacity (commits 100 to 102)16:47
didrocksogra: is there an ABI break?16:47
ograi would like to get a signoff from the desktop team16:47
ograhmm, not sure, it adds new functions16:47
ograbut doesnt modify existing ones as far as i can see16:47
didrocksdebian/patches/17-workspace-switcher-cycle.patch16:48
didrocks-> we don't have that behavior in compiz16:48
didrocksit seems wrong16:48
ograweird, wha does bfiller think we do then16:48
ogra*why16:48
bfillerdidrocks: compiz desktop cube has this behavior will allow you to rotate from last side of cube to first side16:49
ograah, here he is16:49
didrocksbfiller: right, but we don't use cube by default16:49
didrocksbfiller: we have staticswitcher, where we don't use the behavior on purpose16:49
didrocksthat*16:50
didrocksogra: /apps/metacity/general/capture_before_unmap change seems fine if you can confirm it doesn't slow down on minimize16:50
ograi will test it tomorrow16:50
ograthanks16:50
bfillerdidrocks: what if I made it configurable via gconf whould it be acceptable?16:50
didrocksbfiller: sure, but the default should be off16:50
bfillerdidrocks: sounds good, I will rework it then16:51
ogradidrocks, apart from that change it is ok to go in ?16:51
didrocksbfiller: propose it upstream as well btw16:51
didrocksogra: yeah, after the test :)16:51
ograi.e. i dont need to bother you again and just upload after testing16:51
ograright :)16:51
ogragreat, thanks16:52
bfillerdidrocks: ok16:52
didrocksyw16:52
desrtmterry: i just committed a docs patch that makes your code officially buggy :)16:57
desrtmterry: of course, i'll still keep the bug open and investigate the root issue, though16:57
desrtsince it's quite likely that this issue could pop up in legitimate cases too16:58
mterrydesrt, dammit  :)16:58
desrtmterry: if you have some time to kill, a small test case would go a long way :)16:59
desrtuhhhh17:00
desrtchild_watch_helper_thread17:00
desrtSIGCHLD implicated in this bug?  we have an open bug about a race here (that's exceptionally difficult to solve)17:01
desrtthe bug only happens in the single-threaded case of GMainLoop but what matters is how many threads GMainLoop saw by the time the child was spawned...17:01
* desrt tries to find that bug17:02
brycehlamalex_, there is not a public eta on the nvidia drivers, no17:02
lamalex_bryceh, yah- i got the memo17:03
lamalex_im really pissed at myself for just running a dist upgrade and not looking at it17:03
brycehlamalex_, sorry to hear; we did try to give plenty of heads up, mentioned it in the release notes, etc.17:05
desrtmterry: here is the bug for reference: https://bugzilla.gnome.org/show_bug.cgi?id=398418 .  not sure it's related though17:05
ubot2Gnome bug 398418 in mainloop "GChildWatch race condition?" [Major,New]17:05
lamalex_bryceh, yah i know it was completely my fault17:05
lamalex_i have been careful about not updating, but this morning i just f'ed up17:05
brycehlamalex_, for future reference, in EVERY release nvidia and fglrx ALWAYS break at some point, so if you want to track the development version just be prepared for being proprietary-driverless for about a month17:06
bryceh(longer in fglrx's case)17:06
mterrydesrt, seems different, since later comments say only present if you don't link against gobject17:09
desrtmterry: that's because we g_thread_init() from g_object_init() these days17:10
desrtand a thread-safe mainloop is immune to this bug17:10
desrtit looks like you have two separate bugs here, though17:11
desrtone of them is a deadlock on a GDBusConnection lock (with no all-threads backtrace to discover the true issue)17:11
desrtthe other two are GMainLoop deadlocks17:11
desrthmm.  this really really looks like heap corruption17:13
desrtcould just as easily be dconf's fault, of course17:15
desrt(for corrupting the heap)17:15
mterrydesrt, well, it's just that it goes away with a really small patch to avoid spamming dconf17:17
desrtmterry: there's a rather insideous bug hiding here17:17
desrtyou've exposed it.  i'm rather happy that you did.  please don't hide it again :p17:18
mterrydesrt, it's simple enough to turn off my patch in my code and test dconf in future17:18
desrttrue.  but that will never happen :)17:18
desrthave you tried valgrinding?17:19
mterrydesrt, well, I can easily test patches is all I'm saying.  But the combination of difficulty of creating a test case and since I worked around it...17:20
mterrydesrt, yeah17:20
mterrydesrt, nothing notable, except for a memory leak due to bad vala bindings  :)17:20
desrtvalgrind is particularly bad at telling you when you're trashing the heap as long as your trashing falls nicely within the bounds of existing objects :p17:21
desrti guess you used always-malloc, of course...17:22
mterrydesrt, probably not.  this was a relatively simple valgrind run17:24
desrtah.  you should always do that :p17:24
desrtthe slice allocator is quite good about giving out the same memory twice17:24
mterrydesrt, when running valgrind?  OK17:24
desrtit makes it really hard for valgrind to detect accesses to freed objects17:25
desrtwhich is the sort of thing that results in what we're seeing here17:25
desrtit could be a dumb refcounting bug or something17:25
mterrydesrt, documentation likes debug-blocks even better17:26
desrti don't know what one17:26
* desrt reads up :)17:26
mterrywell, I guess not 'better' but 'in conjunction'17:27
desrtneat option.17:31
desrtit's quite a good one to have too17:31
desrtgslice is pretty quick about what it does with memory, particularly when it comes to its 'magazine'17:33
desrtif you tlel it "here's a 16-byte chunk of memory that i'm freeing" it will toss it in a list and give that chunk back out to the next person who asks for a 16-byte chunk of memory with no additional checking at all17:34
desrtso you can do some pretty funky things, as you might imagine17:34
desrtlike donating malloc()'d or mmap()'d memory to the next g_slice_alloc() user :)17:35
desrt(or, as in the example that was given, memory that is from the slice allocator, but the wrong size)17:35
chrisccoulsonpitti - did your firefox stop crashing btw? i just had a look on crash-stats, and the last submitted crash report due to the globalmenu was on 4th feb18:33
=== smspillaz is now known as smspillaz|sleepi
=== smspillaz|sleepi is now known as smspillaz|asleep
didrocksmterry: you can give me all the utouch-* stack + girr18:52
didrocksginn18:52
mterrydidrocks, hah!  will do18:52
didrocksmterry: I've already done the work when checking for NEWing :)18:52
didrocksmterry: so, just a quick look again for the MIR, but all is basically done :)18:53
mterrydidrocks, cool18:53
didrocksmterry: will get to it tomorrow18:53
didrocksnow, time for dinner + some work offline!18:53
bcurtiswxcya didrocks18:53
didrockssee you bcurtiswx18:53
RoAkSoAxanyone might have an idea why a .desktop file is not updating the path to the icon? (this software was initially created with quickly and everything was working fine till last upload)19:08
mterryRoAkSoAx, you talking about natty quickly?19:10
mterryRoAkSoAx, it started using svg icons in the latest update, maybe that's related?19:11
RoAkSoAxmterry: not really natty quickly, but I uploaded new release of testdrive couple weeks ago and during the build process the icon path for the .desktop file was updated correctly. I uploaded a new testdrive earlier this week and the path has not been updated in the .desktop file. I'm building in pbuilder's today, and the path gets updated correctly19:12
mterryRoAkSoAx, oh, odd.  so quickly didn't change...19:13
RoAkSoAxmterry: nope the setup.py hasn't been touched for a long time19:14
RoAkSoAxand quickly just updated the .quickly file version19:14
RoAkSoAxbut that the weird thing is that the package in the archives does not update the path of the image for the .desktop file, while the ones I'm building right now in pbuilders do19:15
RoAkSoAxI guess I'll just have to upload a new testdrive and see if it is fixed19:15
chrisccoulsonseb128 - are you able to accept firefox for me please? (it's sat in binary NEW atm)19:26
seb128chrisccoulson, hum, how can I money that? :-)19:26
chrisccoulsonheh :)19:27
seb128chrisccoulson, can do, is the new binary for main or universe?19:27
chrisccoulsoni'll buy you a beer at UDS ;)19:27
chrisccoulsonseb128 - for main, i would like to build icedtea-plugin against it19:27
seb128chrisccoulson, done19:29
chrisccoulsonseb128 - excellent, thanks :)19:29
seb128chrisccoulson, yw19:30
=== tkamppeter_ is now known as tkamppeter
jcastromterry: so the eclipse menu was too scary?21:27
mterryjcastro, yeah  ;)21:27
mterryjcastro, I'll revisit it if no one else does21:28
dobeyrodrigo_: around?21:28
jcastromterry: on the plus side hopefully you're not permanently damaged from the experience, heh21:29
* mterry hopes21:29
seb128robert_ancell, hey22:26
robert_ancellseb128, hello22:26
seb128robert_ancell, how are you?22:27
robert_ancellgood22:27
seb128robert_ancell, great ;-)22:27
seb128robert_ancell, can you make sure that the versions update you do keep a clean stdout?22:27
seb128robert_ancell, otherwise the cron job sends an email with the log every time it runs22:28
robert_ancellit does, doesn't it?22:28
robert_ancelloh, so that's why you did that22:28
seb128no, it sends email about build records22:28
robert_ancelldid I leave some debugging in?22:28
seb128seems you added that yesterday in your commit22:28
robert_ancellShould we just change that to 1>/dev/null?22:28
robert_ancellIt's only stderr we really care about22:29
seb128"        print '    failed to build on on %s' % record.arch_tag"22:29
seb128I think is the issue22:29
seb128robert_ancell, we could as well, or just redirect stdout to a log file or something22:29
robert_ancellI think that would be better.  The log output is useful22:29
seb128k, I will rework that what I've so time to write a log on put it online in the same directory22:30
seb128so maybe just drop that print for now to stop the email spam until then22:30
seb128I will also do some cleaning tomorrow I think in the list22:31
robert_ancellclean what?22:31
robert_ancellI'll fix up the print now22:31
seb128robert_ancell, there is a bunch of lines which have no upstream versions, wrong url22:32
seb128robert_ancell, there is also some sources where we should track a stable serie22:33
seb128like glom22:33
seb128I've been reviewing some todays and taking some notes, will update the .py tomorrow22:33
seb128we should perhaps drop some sources from the list as well, i.e plymouth22:34
seb128things which are from the foundation team and we will not update22:34
robert_ancelljust blacklist them so they only show on the extended view22:35
seb128could do that22:35
seb128well I just reviewed it, there is only plymouth being annoying22:36
seb128robert_ancell, btw I didn't sync farsight2, there is an ubuntu diff for it22:37
seb128changing the gst depends to good since we moving the farsight code there22:37
robert_ancelloh, I was supposed to take that one off the list, thanks22:37
seb128TheMuso, why is the espeak version 1.44.05~really-1.44.04-0ubuntu1?22:44
seb128or, you repacked it, weird version22:45
seb128rather than using current-repacked or something22:45
=== bjf is now known as bjf[afk]
chrisccoulsonm'eh, just got the invisible window bug again22:50
chrisccoulsoni thought didrocks said that was fixed ;)22:51
seb128chrisccoulson, it's not but they go a way to trigger it reliably now and know what's going on22:51
seb128sam said he would fix it tomorrow22:51
chrisccoulsonseb128 - oh, that's good :)22:51
seb128you can hide and show the desktop to workaround it22:51
seb128ctrl-alt-d22:51
seb128robert_ancell, btw do you see any compelant reason to try to get cairo 1.11?22:52
seb128or should we just stay on 1.10? I don't really trust their schedules22:52
robert_ancellnot that I know of.  I'd like to have the latest because that makes support easier post-release22:52
robert_ancellhow late do you think we can wait?22:53
TheMusoseb128: I had a weird problem when I uploaded it, I detailed the problem in teh changelog.22:53
TheMusoI hope to merge the latest Debian revision before FF, so hopefully that problem won't show itself again.22:53
TheMusoIt had something to do with the binary files in the tarball, can't remember exactly without checking the changelog myself.22:54
seb128TheMuso, ok, yeah the changelog explain it, it's just the version you picked which is confusing22:56
seb128TheMuso, rather than doing version-repacked you did next-version...22:57
seb128robert_ancell, well, we should decide around feature freeze I guess22:57
robert_ancellseb128, interesting, why doesn't cairo show up on versions by default?22:58
seb128robert_ancell, I will check with upstream if they are a fixed schedule, but seems they started recently to roll 1.11 tarballs so I'm not really confident it will turn stable this cycle22:58
seb128they got over one cycle delay for 1.1022:58
seb128robert_ancell, it does but on the non default list...not sure why22:59
seb128do, launchpad off in 2 minutes it says22:59
seb128it's not in the germinate desktop list23:00
seb128it's in the standard one23:01
seb128ok, enough irc for today here, see you tomorrow23:04
bcurtiswxaww darn, bzr just went down...23:09
bcurtiswxsorry23:10
bcurtiswxLP went down for the bzr get etc..23:10
micahgbcurtiswx: should be about 90 minutes23:12
bcurtiswxmicahg, yup plenty of time for me to go take care of dinner and clean it up. lol23:15

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!