/srv/irclogs.ubuntu.com/2008/05/07/#ubuntu-desktop.txt

=== fta_ is now known as fta
dholbachgood morning06:28
huatsmorning everyone09:09
asacmvo: what about bug 19021 ... is that suitable for hardy-updates?09:16
ubottuLaunchpad bug 19021 in synaptic "Should run dpkg --configure -a automatically" [Medium,Triaged] https://launchpad.net/bugs/1902109:16
asacor better: do we have a safe fix for it?09:17
mvoasac: give me a sec09:33
mvoasac: this is implemented in update-manager now, it will fix some common mistakes09:34
asacmvo: safe to take for SRU?09:34
mvothe update-manager bits are part of hardy already09:35
mvofor synaptic that would be a new feature, I don't think we could get it pass the release team09:35
asacoh ok, so ill state that and mark wont fix for hardy. thanks09:35
asaci approved for intrepid09:36
mvoupdate-notifier will show a error symbol (not sure if it detect dpkg --configure -a by itself, but it does a lot of broken situations) - when you left click on it, u-m will kick in and do the repair action09:36
mvoasac: how come you triage those? or is this part of a general milestone cleanup?09:36
asacmvo: well ... i looked at the hardy bug list and found this.09:37
mvocool, thanks09:38
asacdone09:38
asacany way to tell power manager to set powersave governour instead of ondemand when on battery?09:40
mvoseb128: I was debugging a update-manager hang the other day and it seems like it hangs here: http://paste.ubuntu.com/10700/ (strace)09:53
mvoseb128: tihs is in the dist-ugprader, do you have any idea if for svg something else needs to be initialized beside the normal gtk_init() (that is run when importing gtk)09:54
=== asac_ is now known as asac
seb128mvo: no idea no, are you sure that's the thread hanging and that the hang is due to the svg? did you get a gdb stacktrace?10:06
mvoseb128: it looks like it, I'm digging into it a bit more10:12
seb128mvo: do you have steps to trigger the bug easily?10:12
mvonot easily :/10:13
=== crevette_ is now known as crevette
mvoseb128: what beside libgdk-pixbuf2-dbgsym and libgtk2.0-0-dbgsym will I need for #6  0xb78d5b26 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 ?10:18
seb128mvo: the dbgsym seems to be borked, try the dbg maybe10:19
mvo#4  0xb755ff59 in ?? () from /usr/lib/libgdk_pixbuf-2.0.so.010:21
mvoNo symbol table info available.10:21
mvooh well10:21
seb128grumpf, need to rebuild gtk I guess10:22
=== MacSlow_ is now known as MacSlow
seb128mvo: I'm not sure how to debug that, I blame it on pitti that's due to dbgsym thingy I think ;-)10:47
mvo:)10:49
mvothat is ok, I think I found a workaorund for now, I need to wait for feedback from my users10:49
seb128I hate this thing10:49
mvowhat thing?10:49
mvobugs in general ?10:49
seb128neither the gtk dbg nor the dbgsym are working in hardy10:49
seb128no, debug symbols issues10:50
seb128it makes almost impossible to debug crashes we receive10:50
seb128my local builds have working dbg variants10:50
seb128so I guess it's due to the binary mangler but I don't know why it's breaking things10:51
seb128and to make things easier dbgsym are not available for hardy updates10:52
mvoseb128: ok, thanks. I will rebuild it after lunch11:19
seb128I'm debugging11:23
seb128bad pkg-create-dbgsym, no cookie for you11:27
seb128pitti: ok, so pkg-create-dbgsym is buggy and break gtk debugging11:27
seb128pitti: that's what gtk does11:27
seb128dh_strip -s --dbg-package=libgtk2.0-0-dbg -Nlibgtk-directfb-2.0-0-udeb11:28
seb128dh_strip -s -plibgtk-directfb-2.0-0-udeb11:28
seb128pitti: and pkg-create-dbgsym don't respect the package specified in the second call and stip everything again11:28
seb128s/stip/strip11:28
seb128which means the dbg and the dbgsym are b0rked11:28
seb128pitti: do you think that doing an export NO_PKG_MANGLE=1 between the calls would be a good workaround?11:33
seb128no need to export, rather NO_PKG_MANGLE=1 dh_strip -s -plibgtk-directfb-2.0-0-udeb11:34
seb128hum11:35
seb128"dh_strip -s -plibgtk-directfb-2.0-0-udeb" seems buggy in fact11:39
seb128dh_strip -plibgtk-directfb-2.0-0-udeb should do the trick11:39
pittiseb128: give me a second, currently discussing with Matt11:39
seb128sure11:39
pittiseb128: do we have a bug# for the broken mass-storage camera handling?11:39
seb128is it broken?11:40
pittiseb128: i. e. nautilus mounts them, but doesn't check for a DCIM/ folder, as g-v-m did11:40
seb128works for me since you enabled g-v-m again11:40
pittig-v-m handles libgphoto, calls f-spot11:40
pittibut mass-storage cams are mounted, not libgphoto'ed11:40
seb128a right11:40
seb128again due to the gphoto gvfs backend being disable11:40
seb128pitti: bug #20846711:41
ubottuLaunchpad bug 208467 in nautilus "Camera Device button "Open F-spot Photo Manager" doesn't work" [High,Confirmed] https://launchpad.net/bugs/20846711:41
pittiright11:41
pittithanks, seb128, you are faster than google :)11:41
seb128you are welcome ;-)11:41
seb128it's in my few unread bug mails11:41
seb128ie, things to reply on11:42
pittiI mark it for .1, ok?11:42
seb128sure11:42
seb128I think we should consider enabling the gvfs gphoto backend11:42
pittiseb128: I just fail to see what the gphotofs backend has to do with it?11:42
pittiseb128: it doesn't (shouldn't) handle mass-storage cams11:43
pittimdz's problem is that the "open f-spot" button in nautilus doesn't work11:43
seb128right11:43
seb128the feature relies on having a DCIM directory available11:43
mdzis this bug 208467?11:43
pittimdz: ^ on your empty camera, do you have that?11:43
mdzif so, what information can I add to the bug?11:43
ubottuLaunchpad bug 208467 in nautilus "Camera Device button "Open F-spot Photo Manager" doesn't work" [High,Confirmed] https://launchpad.net/bugs/20846711:43
seb128but that's the gphoto code which does the handling I think11:43
mdzpitti: yes11:43
seb128mdz: it is yes, no information is required I think, it just needs somebody working on fixing the issue11:44
pittiit might be the cleanest way to enable gphoto, fix the fuse-mount (so that it works with non-gvfs apps), and disable it in g-v-m again?11:44
mdzseb128: ok, the comments seemed to say it was fixed in g-v-m but I see there is a nautilus task still open11:45
seb128pitti: yes11:45
pittiright, g-v-m was a kneejerk fix for hardy final11:45
seb128mdz: right, we disabled the gvfs code and used g-v-m again in hardy11:45
pittiI guess we can emulate that with an USB stick which has DCIM/ and a few jpgs in it?11:45
seb128yes11:45
* pitti only has a gphoto camera11:46
seb128pitti: you can ignore the dbgsym issue description I made before, the second dh_strip call in the package is simply buggy, I'll fix it after lunch11:49
* seb128 lunch now11:50
pittiseb128: ok, thanks11:50
pittilunch, good idea11:50
seb128pitti: ok, can you accept the gtk sru upload?14:11
seb128it should fix the dbgsym build14:11
seb128mvo: bug #227723 for the record14:11
ubottuLaunchpad bug 227723 in gtk+2.0 "non working debug variants in hardy" [Medium,Fix committed] https://launchpad.net/bugs/22772314:12
mvothanks seb12814:15
seb128mvo: did you figure what was the svg issue then?14:22
mvonot yet, I *think* its something evil with threading a stuff, but I don't know yet14:23
pittiseb128: thanks for that; I'll have another SRU round in a bit, yes14:51
Amaranthmvo: do you have the bug number for the animation fixes?17:05
Amaranthdunno if they made it into -proposed yet, just want to see if i've got a dupe of that17:06
=== vuntz_ is now known as vuntz
* mvo wonders if archive.u.c is slow for everybody just now19:25
mvoAmaranth: I think the bug in animation was #22063119:28
Amaranthd'oh, i was looking in compiz :P19:29
Amaranthmvo: can you reproduce bug 218489 ?19:29
ubottuLaunchpad bug 218489 in openoffice.org "Graphical interface freeze when switching between OpenOffice and another window" [High,Confirmed] https://launchpad.net/bugs/21848919:29
Amaranthseems to be the same thing19:29
mvogive me a sec19:33
mvoI think I have -0ubuntu5 installed already19:33
mvoI created a ~compiz ppa btw19:33
Amaranthyeah, i've used it before19:34
Amaranthwait, maybe that was your ppa19:34
mvoyeah, I used mine but that is not ideal - the ~compiz is better, then you can upload as well without sponsoring19:34
mvoI think I can not reproduce it with 0.7.4-0ubuntu519:35
mvolet me downgrade19:35
pochuasac: hey, Liferea's upstream dev added Xul 1.9 support to both 1.4 series and trunk. That wasn't from your patch though, but from a different one which was sitting in the patch tracker and that doesn't break Xul 1.8 support... you may want to have a look at it. http://liferea.svn.sourceforge.net/liferea/?rev=3849&view=rev20:07
asacpochu: how can i see the complete diff for that commit?20:09
asacpochu: they have think XPCOM_GLUE == GECKO_1_9 ... which is not really true. but if it works for us. fine20:12
pochuasac: I haven't tested it yet, but I'll try to do it before the 1.4.16 release20:15
seb128hey pochu20:15
pochuhi seb128 :)20:16
seb128pochu: interested to get the gthumb new version to hardy?20:17
pochumvo, Amaranth: do you know Kristian Lyngstøl?20:21
Amaranthyep20:21
Amaranthpochu: why?20:22
mvopochu: yes20:22
pochubecause he's my room mate for UDS and I did never hear about him ;)20:23
pochuseb128: there's already a debdiff in the bug, did you see it?20:23
pochuseb128: I've never used gthumb so I'm not very interested on it tbh...20:23
Amaranthpochu: well, he is a compiz-fusion guy20:23
seb128pochu: that's an intreprid update rebased on debian no?20:23
seb128pochu: ok, that's alright, I will try to find somebody else interested then20:24
Amaranthpochu: cool guy, bit heavy on the sarcastic humor sometimes though :)20:24
seb128pochu: I'm too busy to do it but I think we should get the update in hardy, so it's only the matter of finding somebody wanting to do the work there ;-)20:24
pochuI'm sarcastic too :)20:24
Amaranthpochu: remember that if it sounds like he says something bad :)20:25
pochualthough I'm sarcastic in Spanish... not sure how I'll do in English ;)20:25
Amaranthbefore i met him in real life i actually thought he was a jerk, the humor doesn't come through well on IRC :P20:25
Amaranthbut you should get along fine20:26
pochuseb128: ah, ok. I could review it if that's what you want but gthumb is in main anyway so you (or some core-dev) will have to re-review it ;)20:26
pochuheh20:26
seb128pochu: no, somebody needs to do the update for hardy and look at the launchpad bugs that can be closed, etc20:27
seb128pochu: I can do the reviewing20:27
pochuah, right20:27
pochubut the update for Hardy wouldn't be more or less similar to the one for Intrepid?20:27
seb128no, sru are minimal changes, so it's an update using the hardy version and not the debian one20:29
pochuah, I thought we wanted to put the new upstream for Hardy too20:30
pochualthough that would make more sense to go to backports, right20:31
pochuso what needs to be updated for Hardy? backport some patches from the new release?20:31
seb128pochu: right, I was suggesting doing the version update for hardy, just do it using the hardy version and not the current debian one20:32
seb128to not include extra packaging changes where it's not required20:32
seb128s/do/doing20:33
pochuok, understood now :)20:33
seb128well, usually that would be a backport thing20:33
seb128but hardy is a lts and we will do a 8.04.1 so getting bug fix updates there makes sense20:33
seb128seems that gthumb has quite some users and the new version fixes several annoying issues20:34
pochuok, let me have a look20:35

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