[00:36] Hey can I get in on the Ubuntu One private beta that's rumored to exist (I read the desktop team minutes ;) ) [00:37] YokoZar: you'll have to ask kenvandine_wk i think its going to be more widely beta at UDS or something like that, but i'm not certain [00:37] I can wait till then I guess [01:01] YokoZar: Still there? [01:01] rickspencer3: yeah [01:01] so, I think the Ubuntu 1 team is planning a limited beta around the time of UDS [01:02] but I *think* it starts out invite only [01:02] are you on loco team or Ubuntu? [01:02] Then I'll give you a business card at UDS and you can invite me ;) [01:02] sweet [01:02] We've met before actually [01:02] oh? [01:02] https://launchpad.net/~scottritchie [01:03] Scott! [01:03] hi [01:03] okay, so you'll meet up with those guys at UDS [01:03] Will do ;) [01:03] looking forward to seeing you in Barcelona! [01:03] Ole! [01:03] I tend to avoid going by Scott in the Ubuntu circles because there's a much more well known Scott, heh [01:03] lol [01:04] well, sometimes it takes me a while to connect irc nicks and real names [01:04] notice my incredibly uncreative nick [01:04] Yeah no kidding. I've given half serious thought to changing my real name to Yoko ;) [01:32] hehe... i am kenvandine and i hide behind the kenvandine irc nick... super secret [02:39] robert_ancell: good morning [02:39] rickspencer3: hey rick [02:40] robert_ancell: I just sent the meetings from the team meeting [02:41] you may want to refer to the irc log related to our discussion yesterday about bug workflow [02:42] reading now [02:49] kenvandine_wk: my UI always fails to authenticate - is there anything I can do to debug it? [02:50] rickspencer3: looks like it will be quite a discussion at UDS regarding bugs! [02:50] heh [02:50] too bad seb128 wasn't there, it would have been an even more spirited discussion! [02:50] :) [02:51] kenvandine_wk: s/UI/U1/ [02:52] rickspencer3: In Ekiga are you using the SIP proxy voip.canonical.com? [02:52] robert_ancell: nope [02:52] I use ekiga.net (like users would ;) ) [02:53] also, I haven't gotten around to setting up the canonical sip :( [02:53] rickspencer3: you go through a router? do you have any port forwarding setup? [02:53] robert_ancell: I do go through a router, but ekiga works with most people [02:53] I mean, it works when I talk to most people [02:54] not sure if port forwarding is set up for it though [02:54] I set it up for some protocols, but don't think I did it for sip [02:54] * calc needs a faster computer to build OOo, a 2-way 6-core xeon would be nice :) [02:54] rickspencer3: it will work as long as one has port forwarding or uses a proxy. I think both of us have neither so it can't make a direct connection (which is why 500@ekiga.net works but dialing users doesn't) [02:55] calc: does OOo build in parallel that well? [02:55] hmm [02:55] rickspencer3: this is a documented requirement for Ekiga and there is a bug requesting Ubuntu have a default SIP proxy [02:55] robert_ancell: I don't have time tonight, but perhaps tomorrow [02:55] ajmitch: i think up to 10 thread not sure about higher [02:55] rickspencer3: ok, will play around [02:55] ajmitch: of course some of the stuff isn't parallelizable like the dh_shlibdeps crud [02:55] rickspencer3: (either way Ekiga does not give enough feedback) [02:55] yeah [02:55] calc: as long as you wouldn't have all but 1 core sitting idle :) [02:55] but when it works, it so cool and useful :) [02:57] * calc is thinking about buying a core i5 at the end of the year [02:58] I'm getting very tempted to replace my main computer, at about 3 years old [02:58] all i have currently is a c2d e6300 which is pretty slow for OOo, takes ~ 4hr initial build and 1.5hr for rebuilds [02:58] I thought you were dropping OOo soon? [02:59] ajmitch: going to 20% time for maintaining it later this week, but still will be working on it [02:59] then not wasting any of that 20% will be important [02:59] ajmitch: yea, with a single build taking 4hr doing triage while i wait on it is important and hoping it doesn't fail after a few hours also is good [03:03] rickspencer3: if we can come up with a good plan for bug handling, wrt UDS etc, once i am back fulltime i should have time for more than just OOo :) [03:03] calc: right [03:03] OR [03:04] have time to really do some cool stuff with OOo [03:04] or both [03:04] yea [03:04] well time for more than just triaging anyway :) [03:06] doing cool stuff with OOo is somewhat complicated by the fact it is a giant monolithic blob of code :-\ [03:07] but it looks like there are real rumblings inside of Sun finally to do a real split similar to the Novell work instead of just the current branding stuff [03:08] the way OOo currently works is a pretty high barrier for developers [03:09] * ajmitch has never been tempted to dive in & improve it [03:12] ajmitch: its pretty gross ;-\ [03:13] ajmitch: i had thought about trying to fix up things like getting it FHS compliant but its such an apparent mess (at least that I saw) that I just gave up, it would haven't taken a long time to determine how to fix it and even longer to convince Sun to take the patches [03:13] s/haven't/have/ [03:14] once they eventually get it split up it will probably be easier to fix things like that [03:14] hopefully it'll end up with some more community input & development in the long term [03:15] ajmitch: yea that is the thinking of what will probably happen now that Sun has been bought by Oracle [03:16] would be nice to get it converted over to gettext, if that is actually doable for a cross platform project [03:16] but things like that and getting it converted to a real dialog layout format are huge projects [03:16] I don't really use OOo much, but it would be nice to not see it die off & stagnate [03:16] yea [03:17] it seems that things that originally come from closed source have issues converting over to real open source projects [03:17] because the development culture grows along with the project [03:18] it's not something that is easily added in later [03:18] good night all [03:18] yea, and getting the company that released it openly to let go to a community organization is hard too [03:18] robert_ancell: need anything before I shut down? [03:18] rickspencer3: goodnight [03:19] rickspencer3: nope, have a good night [03:19] tanks === rickspencer3 is now known as rickspencer3-afk === nhandler_ is now known as nhandler [06:27] Good morning [06:35] bryce: with that recipe, i915 gets probed (and the mode set) about 2/3 into the boot process [06:35] bryce: which is a fairly nasty time, since it will interrupt usplash, etc, and also not look good with plymouth [06:35] bryce: I guess it should be moved into the initramfs, as the first thing it does? [07:05] pitti: hello [07:05] pitti: I have a question about building new debs. I've made the merge for glade but when I run dpkg-buildpackage it reverts my changes. How do I build it with the changes? [07:06] robert_ancell: what did you change? [07:07] pitti: and the new avahi requires a new libcap-dev package - what is the process to update that? [07:07] pitti: debian/control - added a new conflicts [07:07] aah [07:07] robert_ancell: I bet it uses a debian/control.in [07:07] duh... [07:07] I often stumble over this as well [07:08] robert_ancell: if you need a newer libcap2 source, just update it; however, we have the latest one from Debian in Karmic (2.16-5), isn't that recent enough? [07:08] robert_ancell: if you need a newer version, please package it and ask me to sponsor it [07:09] pitti: why does http://packages.ubuntu.com/karmic/libcap-dev show an older version? [07:09] I guess it takes a while to catch up [07:09] robert_ancell: use rmadison [07:09] rmadison libcap-dev [07:10] or, if you are on karmic, just apt-cache show libcap-dev, but I guess you are on jaunty? [07:10] yup in jaunty [07:11] so, should I try building on jaunty or just propose it for karmic and fix any problems later? [07:13] robert_ancell: generally, all development happens for karmic now (and preferably _on_ karmic as well) [07:13] robert_ancell: you can use a pbuilder or a chroot [07:14] robert_ancell: but if it's just libcap-dev, just download the karmic source and build/install it on your jaunty system [07:14] that's easier [07:14] ok. Is it safe to upgrade to Karmic yet? [07:14] "safe" [07:14] works for me :) [07:14] I surprisingly little damage [07:14] alright, I think I'll do that then.. [07:15] if you dist-upgrade, you should have a look at which packages it wants to remove [07:15] with the current buildd activity, we often have some version skew which sometimes causes packages to be removed [07:19] hello [07:37] robert_ancell: I replied to your compiz bug management mail; please feel free to kick the discussion to u-devel@ [07:37] I need to leave for about 2 hours, doctor appointment [07:37] pitti: thanks. One last question - if there is a control.in should the diff.gz contain the control file? === tkamppeter_ is now known as tkamppeter [08:04] seb128: morning [08:04] robert_ancell: hello from london [08:04] how was your day? [08:05] seb128: a steep learning curve... I have the glade package ready. I think I've got the avahi package produced but I'm currently upgrading to Karmic so I can build it easily [08:06] ok, so none of those are syncs now? [08:06] I will try to review those today if they are ready for review [08:06] seb128: no [08:06] I'll do gdm tomorrow [08:07] maybe do the totem* srus if you didn't start on those yet? [08:08] sure, I'll do those now [08:10] don't forget to do some bug triage too, we are lagging behind after jaunty again [08:10] triaging new bugs for a package a day could be a good goal [08:10] for reasonable packages [08:10] ie gnome-games [08:18] seb128: hey seb! had a good flight? [08:19] hello mvo, yes very good [08:19] one hour flight, london public transportation running fine during the week [08:31] seb128: when using quilt and autoreconf is there an easy way to quilt add all the files? [08:33] robert_ancell: find . | xargs quilt add [08:34] :) that's what I did. Feels a bit hacky though... [08:34] morning all; I have a noob question... I'm trying to fix that epiphany user-agent bug, and I've been reading the packaging guides and trying to figure out how to do a substitution string for the target platform version at build time... is that a pointless search? i.e. is the package *always* going to be built on a system with the same /etc/lsb-release info as the target platform? [08:35] robert_ancell: careful of .swp files your text editor creates, ctags files, or anything else you might have accidentally put in the directory ;) [08:35] robert_ancell - you also have to be careful of files that get automatically created by running autoreconf whilst you edit the patch [08:35] i've fallen in to that trap before and you end up with a diff outside of the /debian directory [08:35] * chrisccoulson loves quilt [08:35] yuck. Easiest solution is to manually edit the patch afterwards? [08:36] I tend to change the rules to comment quilt-patchsys and use cdbs-edit-patch [08:36] one good move would be to make cdbs-edit-patch work on quilt packages [08:36] not using quilt, just the same way it's working for simple patchsys [08:37] sometimes when i run something that i know might create new files, i just create a copy of the source directory i'm working in, run the command in one (ie, autoreconf), then take a diff of the two folders and use that as the patch [08:37] that would be nice. Is upstream likely to support changing from quilt if we send them a cdbs patch? [08:37] seb128's method makes sense though [08:37] re [08:37] hey seb128 [08:37] so, that was pleasingly quick [08:37] robert_ancell: "upstream" being debian? no, they switched to quilt [08:37] hello pitti, what was quick? [08:37] robert_ancell: yes, debian/rules will create debian/control from control.in on clean [08:38] seb128: doctor appointment [08:38] seb128: oh [08:38] pitti: everything is ok? [08:38] . o O { oh, wow, KMS, UXA, and compiz running flawlessly } [08:38] seb128: just my weeks-old small hand injury from board breaking, nothing serious [08:39] pitti: I tried deleting control and dpkg-buildpackage failed. So I've left it in [08:39] pitti: ok good [08:39] robert_ancell: just change control.in and run debclean [08:39] that should do [08:39] thx [08:40] hey [08:40] good morning [08:44] lut crevette [08:44] seb128: how's the sprint? [08:46] pitti: just starting for me, they are going through the first 2 days discussions and doing a summary now [08:52] salut * [08:53] hey didrocks [08:55] Hi pitti! Are you also at the sprint? [08:58] lut didrocks [09:02] plop seb128 ;) [09:17] I seem to have $GTKDOC_REBASE missing from a build, anyone know what it is? [09:19] robert_ancell: run the gnome autogen.sh, there is not gtk-doc autocommand [09:19] or copy the change from the previous version [09:20] only configure doesn't apply usually you can force the patch run autoconf and refresh [09:20] hey seb128 - i saw your comments on the gnome-sesion update. i'll work on those later - sorry i've not done it yet, i've not had a chance yet. [09:20] so I should ammend the autoreconf patch by running autoconf? [09:21] chrisccoulson: no hurry, I'm at a dxteam sprint for 2 days anyway so I will not have lot of review time [09:21] robert_ancell: if only configure conflicts yes [09:21] seb128 - that's ok then. it should be done by the time you get back:) [09:22] good ;-) [09:24] hello, for those interested I did a upload request for gnome-bluetooth 2.27.x which it aims to replace bluez-gnome (https://bugs.edge.launchpad.net/bugs/372395) [09:24] Ubuntu bug 372395 in gnome-bluetooth "[karmic] Please sponsor gnome-bluetooth 2.27.4" [Undecided,New] [09:25] if the people who will upload can do some more testing, I'm a little afraid that break something [09:25] hey rodrigo_ [09:26] hi [09:26] how do I know what's ok vs. not-ok to put in the postinst script? is there a guideline somewhere? [09:26] hello rodrigo_ [09:27] mpontillo: the less you put there the better for system upgrade stability [09:36] does "time-admin" work for you guys? when I start it, I get a dialog "your system is unknown, please select your distro" [09:37] pitti - there's already a related bug report for services-admin i think [09:37] doesn't this break at the start of every cycle? [09:37] ah, that might be, I'll look into it [09:38] i'm not sure whether thats a g-s-t, liboobs or s-t-b issue though [09:38] pitti - bug 371234 [09:38] Launchpad bug 371234 in gnome-system-tools "system::admin::services is broken in karmic (says platform is unsupported)" [Undecided,New] https://launchpad.net/bugs/371234 [09:38] chrisccoulson: thanks [09:39] The selection box lists nothing newer than hardy.... does that mean it's broken in intrepid and jaunty too? [09:40] I don't think so, worked fine there [09:42] pitti - i started working on a MIR for vala last night. is it a show-stopper that it has no gettext support (bearing in mind that it's primary purpose is converting vala source in to C source+headers, so it's a tool that only developers will use) [09:42] chrisccoulson: I don't think so [09:42] this is a build chain tool [09:43] pitti - thanks. i'll carry on working on that later then [09:48] pitti: bonus if you do the debian merge, they have a patch to drop the list of known distro thing [09:48] yay, will do that [09:48] thanks [09:48] I'm amazed that so many people are running karmic yet [09:49] several users confirmed this bug [09:49] why? [09:50] because it just opened and still around breakage time [09:51] we want to support ubuntu [09:51] we usually don't get bugs such details so early [09:51] dogfooding FTW :) [09:51] tkamppeter: have you seen bug 39078? are you aware of any time when there may have been recursive symlinks in /usr/share/ppd? [09:51] Launchpad bug 39078 in cups "cups-driverd endless loop on recursive symlinks" [High,Incomplete] https://launchpad.net/bugs/39078 [09:51] usually first month is focussed on making things build and install [09:51] usually is there more breakage in the beginning of the cycle [09:51] from what I recall [09:52] right which is why you don't upgrade so early [09:52] especially that so early bugs on user applications are not really useful [09:52] because that adds paper work for things which will autosettle with merges, etc [09:53] see you guys tomorrow [09:53] yeah - the other thing that always breaks at the start of every cycke is software-sources, and that was reported straight away and confirmed by lots of people too [09:53] robert_ancell: see you [10:09] seb128: ah, good merge; our remaining changes are patches which are sent upstream, no packaging changes any more [10:10] nice to see Debian pick up PolicyKit [10:11] pitti: good [10:17] seb128: it also finally removes the init script [10:18] pitti: you are reviewing iulian's merge? [10:18] james_w: erm, no? I just did it myself [10:18] oh [10:19] bug 372599 from around an hour ago :-) [10:19] Launchpad bug 372599 in policykit "Merge policykit 0.9-3" [Wishlist,Confirmed] https://launchpad.net/bugs/372599 [10:19] I see no bug on https://bugs.edge.launchpad.net/ubuntu/karmic/+source/system-tools-backends/+bugs [10:19] james_w: oh, polkit, *phew* [10:19] ah, sorry [10:19] you meant they've enabled policykit in s-t-b? [10:19] yes, in Debian [10:19] cool [10:19] so we could drop our delta for that [10:20] sorry for the noise [10:20] james_w: no worries, thanks for bringing it up [10:23] mdz, bug 39078 is a severe upstream bug in CUPS. A tool which searches a directory structure recursively should be aware of link loops. [10:23] Launchpad bug 39078 in cups "cups-driverd endless loop on recursive symlinks" [High,Incomplete] https://launchpad.net/bugs/39078 [10:23] mdz, I am currently seartching whether it already got reported to CUPS. [10:24] tkamppeter: I agree, though multiple people have experienced this issue without knowingly creating recursive symlinks, so there's likely a bug somewhere which creates them [10:38] mdz, as there are many sources for PPD files, especially also driver packages from printer manufacturers, CUPS should handle these link loops gracefully. I will report a bug to CUPS. [10:40] tkamppeter: I agree with you, CUPS should handle the loop more gracefully, and reporting the bug to CUPS is a good idea. However, I also feel that a symlink loop created by an Ubuntu package is a bug in itself. === eeejay is now known as eeejay_lunch [10:52] pitti: i would like apport's xorg hook to collect xorg.log, xorg.log.old, lspci -vvnn and dmesg for packages rss-glx and gdm... should I open a wishlist bug against apport for that? [10:53] mnemo: rather against rss-glx and gdm [10:53] package hooks should be shipped in the packages themselves [10:53] ok [10:54] mnemo: are many gdm bugs really so x.org related? [10:54] not that many, but it happens [10:54] should we more conservative with collecting files you think? [10:55] pitti: is there a good "sample hook" that ships in an app package (in case I want to try adding it myself)? [10:56] I filed a bug against gdm to add an xorg-like apport hook last week [10:56] ah ok great [11:03] mnemo: just look at the existing ones in /usr/share/apport/package-hooks/ [11:04] asac, around? [11:05] thanks [11:05] crevette: yeah. what can i do for/to you ;)? [11:05] crevette: better to just ask your question so he can reply [11:05] asac, hey [11:06] asac, just a question, not sure this is the NM fault, but I shoot, do you know if there is a change in linux kernel 2.6.30 that make me impossible to connecto to my WPA connection with NM ? [11:06] if I switch back the 2.26.28 kernel shipped with jaunty no problem, as expected [11:07] crevette: which driver/chipset? [11:07] I have a lenovo laptop with intel chip if it matters [11:08] for the record, WPA/2.6.30rc3 (karmic) works just fine on my 3945 [11:08] * crevette whould have write its laptop properties somewhere [11:09] you refer to yourself as it? [11:10] crevette: sounds a bit oddd, but i dont want to rule that out [11:10] crevette: can you check if you can narrow down when this happened by going through the milestones from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ [11:10] asac, I didn't tested / troubleshoot intensively, I just test 2.6.30 this morning just before leaving to go to the job [11:11] ok. if it persists, check out the mainline vanilla packages [11:11] having regression window there would be good i guess [11:11] there is rc4 already ffiw [11:15] mvo, hi, njpatel showed me yesterday the bug with update-manager popping up whenever you use apt-get [11:21] seb128: does the new libsoup in karmic fix bug 340785 and bug 313686? [11:21] Bug 340785 on http://launchpad.net/bugs/340785 is private [11:21] Launchpad bug 313686 in libsoup2.4 "totem-mozilla doesn't work when the URL has whitespace chars" [Low,Fix committed] https://launchpad.net/bugs/313686 [11:22] pitti: yes [11:23] seb128: likewise, bug 362307 and bug 326771? [11:23] Launchpad bug 362307 in nautilus "does not support g-a-i mime search anymore" [Low,Fix committed] https://launchpad.net/bugs/362307 [11:23] Launchpad bug 326771 in scim-bridge "scim-bridge crashed with SIGSEGV in scim::IMEngineInstanceBase::get_frontend_data() (dup-of: 243344)" [Undecided,New] https://launchpad.net/bugs/326771 [11:23] Launchpad bug 243344 in scim-bridge "scim-bridge crashed with SIGSEGV in scim::IMEngineInstanceBase::get_frontend_data()" [Medium,Confirmed] https://launchpad.net/bugs/243344 [11:24] pitti: yes [11:24] pitti: dunno about scim but nautilus bugs yes [11:24] seb128: thanks, closed those four [11:25] thanks [11:25] pitti: I don't know about the scim one as said though [11:25] I assume you used the wrong number but meant the other nautilus bug fixed in sru [11:26] seb128: naturally, I meant but 362771, sorry [11:26] tpying is hrad [11:26] don't tell me ;-) [11:38] hum, how do I tell dd to write 6Gb of datas? [11:42] seb128, for kvm ? [11:42] if yes, you can use qemu-disk utilities IIRC [11:43] else you can do a dd if=/dev/zero of=/virtualfs bs=1024 count= [11:44] crevette: ok thanks, I tried that without the bs option [11:44] seb128, else qemu-img is your friend :) === dpm_ is now known as dpm [12:16] hmm irc.gnome.org seems busted for me ... i cannot connect anymore ;) [12:17] asac - i' m connected [12:21] yeah. better dont disconnect ;) [12:31] mpt: right, I have a fix in karmic, we can SRU it for jaunty too [12:31] mvo, I think it would be a good idea :-) [12:32] mvo, 1 day for security updates, and the usual delay (e.g. 7 days by default) for non-security, I think [12:37] mpt: ok [12:38] mvo, btw, sorry, I wasn't here on Monday, I forgot it was a public holiday here [12:38] mpt: no problem, its pretty busy here too, I'm doing a one-to-one sprint currently, but we can have the phone call anytime this week you have time [12:40] mvo, I'm in user testing all today, but I can call you tomorrow if that's ok === eeejay_lunch is now known as eeejay [12:52] sure [13:10] i remember that there was a pidgin upstream at last UDS ... he had some experience on online/offline status things; anyone remembers who that was? [13:23] seb128: hi. bug 372168 is ready for review, I think. [13:23] Launchpad bug 372168 in gnome-utils "Please sponsor version 2.27.1 in karmic" [Wishlist,Confirmed] https://launchpad.net/bugs/372168 [13:41] Ampelbein: ok thanks, I'm at a sprint for 2 days so I will probably not review those today or tomorrow [13:51] seb128: hey - do you have some (gnome) packages that I can update with muharem (that are no merges) ? [13:55] mvo: yes [13:55] mvo: easy one? [13:56] mvo: http://download.gnome.org/sources/gnome-themes/2.27/gnome-themes-2.27.1.tar.gz [13:59] mvo, seb128: ^ please noe that this is in bzr [13:59] with bzr-buildpackage [14:02] seb128: excellent, thanks [14:02] mvo: thank to you ;-) === rickspencer3-afk is now known as rickspencer3 [14:13] hi seb128, how is the sprint? [14:13] rickspencer3: good morning [14:13] hey rickspencer3, pretty interesting so far [14:14] some crack ideas though ;-) [14:14] hi pitti [14:14] seb128: :) [14:14] ie people have been suggesting to replace gnome-panel by xfce-panel to win some login seconds [14:14] of course, why not [14:14] ? [14:14] the time to sort out the configuration migration will be better spent fixing gnome-panel [14:14] spend hundreds of development hours replacing something that's going to be replaced by GNOE 3.0 anyway [14:15] [14:15] hehe [14:15] I suppose the message for us is that log in time is important to them, and we should help with that goal [14:15] right [14:16] rickspencer3: gnome-panel won't go away anytime soon [14:16] we still need it for the cases where we don't have composite [14:16] pitti: well ... the things that make it slow will, right? [14:16] rickspencer3: right, gconf and bonobo [14:16] I thought in GNOME 3.0 they were removing some of the libraries and such that made it start up slow [14:16] the recommendation is to spend some time to investigate what work would be required to improve that [14:17] according to Scott the issue is mainly that gnome-panel is doing a lot of synchronous loading [14:17] ie blocking waiting for applets to load and register [14:17] this is 100% fixable [14:17] hi vuntz! [14:17] yes, we just need to "budget" ressources for that [14:17] ah, the whole "waiting for applets before showing" issue [14:17] a fun one [14:18] some people would like the panel to show asap and then have some uglyness with applets appearing [14:18] vuntz: that's the case already [14:18] some other people prefer the panel to show when it's really ready [14:18] right now it seems to be a wild mix in the middle [14:18] vuntz: what would be your recommendation to improve start time in gnome-panel [14:18] pitti: nope, in 2.26, you should have the second case [14:18] * rickspencer3 gets ready to create another blueprint [14:18] vuntz: gpm and n-m appear after the panel appears, for me [14:19] pitti: they are not applets :-) [14:19] vuntz: what's the difference? [14:19] it's a little thingy in my panel [14:19] pitti: well, they are localized in one small place [14:19] I stress that I've only done cursory examination of the panel [14:19] the biggest problem with gnome-panel is that is re-arranges all my launchers in random order every few months... sometimes when I use another resolution and sometimes on package upgrades.. [14:19] pitti: it's not like your whole panel is flashing multiple times during login [14:19] other than identifying it as a culprit of slow login time [14:19] vuntz: right; I wasn't complaining, just stating how it looks [14:20] pitti: oh, sure, and that's a fair point. But I still think it's better now [14:20] (also, the slide-in animation is now smooth instead of being completely broken) [14:20] (or entirely gone :) ) [14:20] hi Keybuk [14:21] vuntz: what would be your recommendation to improve start time in gnome-panel? [14:21] seb128: recommendation would be to see what's slow, of course ;-) [14:21] right, I'm just asking if you know what is slow [14:21] since you probably know the code better than any of us there [14:21] ie where we should start looking [14:21] if you don't that's fine [14:21] still worth asking ;-) [14:22] well, it'd be interesting to see if a panel with absolutely no applet is still slow, I guess [14:22] that would be a first interesting data point [14:22] good point [14:22] then panel with only in-process applets [14:22] also impact of the applications menu [14:22] etc. [14:23]