[00:04] What's Ipia? [00:05] Milosz: why do you ask? [00:05] azeem, adding packages to my PPA [00:05] do you mean LPIA? [00:05] LPIA [00:05] sorry I wasn't sure if it's an uppercase i or a lowercase L [00:06] I would google it but there is no information about it [00:06] anyway if this is not the right place to ask... [00:06] Low Power Intel Architecture [00:06] (i.e. Atom) [00:06] thanks jdong [00:06] ok it's Atom, I see [00:07] although Atom is more or less x86 compatible, an Atom-aware compiler can generate code that executes more efficiently on the Atom [00:07] I know [00:07] primarily due to in-order vs out of order execution; as I understand [00:07] I've only never heard the term LPIA before really [00:07] interestingly, the patches for that may or may not be in our GCC :) [00:07] heh [00:08] I'd think you can optimize a great deal for Atom's in-order execution [00:08] I mean optimize the asm by knowing it's an Atom CPU it will run on === Snova_ is now known as Snova [00:09] I'd expect so, too === mrsteveman1 is now known as mrsteveman1-afk [02:50] #ubuntu-devel [02:50] I don't suppose anyone online is familiar with AppArmor? [02:50] specifically, how to deal with the possibility of /etc/krb5.conf being a symlink [03:02] geofft: https://wiki.ubuntu.com/DebuggingApparmor [03:06] ScottK: Hm, that doesn't help me a whole lot. I can just add the target of the symlink to the apparmor profile [03:06] but what I'm really trying to ask is, can I make AppArmor follow symlinks? [03:06] OK. No idea about that. jdstrand would be the one to ask. [03:07] It looks like bug 132468 was kinda about this, and the profile just picked up the target of the symlink [03:07] Launchpad bug 132468 in apparmor "Nameservice abstraction should also include /var/run/resolvconf/resolv.conf" [Low,Fix released] https://launchpad.net/bugs/132468 [03:07] and so was 203898, and the program just stopped making symlinks. So maybe you can't do this? [03:08] apparmor does not, no. [03:08] it's one of the things i'm looking at for LTS [03:09] so there's no existing functionality for saying "it's safe to follow /etc/krb5.conf being a symlink" [03:09] any idea if upstream or ubuntu would be interested in a patch to add this support? === mrsteveman1-afk is now known as mrsteveman1 === nixternal_ is now known as Guest34903 === Snova_ is now known as Guest78048 === Guest78048 is now known as Snova [03:45] Any idea why a program would SIGSEGV with a fileno.c: No such file or directory. ? [03:45] I can't find this fileno.c in any ubuntu packages; nearest I can tell it is part of the gnu c library === Snova_ is now known as Snova [03:46] is it reproducible, and if so, can you get a backtrace out of gdb or something? [03:47] geofft: very, and that is the GDB output when the crash occurs [03:47] geofft: well, actually, there are a couple more lines, see here https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/357556/comments/5 [03:47] Error: This bug is private [03:47] Let's try that again.... https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/357556/comments/5 [03:48] Ubuntu bug 357556 in xscreensaver "phosphor crashed with SIGSEGV in fileno_unlocked()" [Medium,New] [03:50] Trying to get an actual backtrace now (sorry, haven't used GDB before, still learning :-) ) [03:53] type "bt" [03:53] (or "backtrace") [03:54] I believe libc6-dbg will get you the debugging symbols to make GDB happy? Dunno if they'd help much [03:54] geofft: OK, just waiting for it to crash again. It usually crashes between 5 and 45 minutes after starting === ScottK2 is now known as ScottK === d1b_ is now known as d1b [05:46] geofft: Not sure if you're still there, but it finally crashed again on two machines, and I uploaded the backtraces here: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/357556/comments/7 [05:46] Ubuntu bug 357556 in xscreensaver "phosphor crashed with SIGSEGV in fileno_unlocked()" [Medium,New] [05:46] geofft: It's not much more information to go on, unfortunately [05:47] geofft: The funny thing is GDB claimed it found all the needed debugging symbols when I attached to the running phosphor process, but there are still unresolved functions [06:01] kb9vqf: The unresolved ones look like invalid addresses. From that backtrace, I can't tell anything... [06:02] geofft: me either :/ [06:03] geofft: there are only four instances of fileno() in the program [06:04] geofft: I am wondering if the problem is more severe, and possibly lurking somewhere in glibc or the X server, as phosphor is not the only screensaver to crash after a certain amount of time [06:05] geofft: I have had almost all of the opengl xsavers I have tried crash in this manner (dunno yet if all are crashing on fileno_unlocked or not) === LucidFox is now known as LucidFox_away === asac_ is now known as asac === apachelogger_ is now known as apachelogger [12:28] Latest upload of adobe-flashplugin to partner breaks flash everywhere. [12:28] (in jaunty). === azeem_ is now known as azeem === yofel_ is now known as yofel === RainCT_ is now known as RainCT === jdstrand_ is now known as jdstrand === hyperair is now known as hyper === hyper is now known as hyper__ [16:42] kwwii_: any luck on the ubiquity changes? [16:47] * maxb blinks at the ftbfs report and wonders why linux-ports and linux-ports-meta tried to build on amd64 [16:49] maxb: they aren't in P-a-s [16:49] therefore they try to build and immediately fail [16:51] worth adding, now there is an Ubuntu-specific P-a-s ? [16:51] although we have the capability now, I'd explicitly prefer to keep them in sync (and so would the Debian maintainer) [16:51] you could file a bug on buildd.debian.org asking for Ubuntu-specific entries, since there's no linux-ports package in Debian [16:51] right [16:52] err, on bugs.debian.org, but with "Package: buildd.debian.org", I mean === Sp4rKy is now known as Guest55850 === Guest55850 is now known as Sp4rKy [17:36] * calc is getting tornadoes for easter :\ [17:36] tornadoes? [17:36] as in those swirly windy things? [17:37] yea tornado watch for my area all day i think [17:37] really bad thunderstorms, etc [17:37] ouch [17:37] =( [17:38] 60mph wind, ~ 2cm hail, etc [17:38] sounds very bad [17:39] its luckily not hailing here at least at the moment, but the wind sounds pretty high [17:39] the hail was spotted around 10km away i think [17:40] but the storm is moving this way, heh [17:52] slangasek: so, what's the policy for packages that have ftbfs since Nov? do we leave them that way since fixing them would essentially break feature freeze? === bureflux is now known as afflux [19:04] I've updated the orbit2 package to create a -dbg symbol package. Currently it has always been a direct sync from Debian with no Ubuntu changes. I've added an Ubuntu version suffix but I'm not sure where/what to set the debian/control Maintainer to since it currently points to the Debian maintainer. Do we have a team that it should be set to? [19:06] IntuitiveNipple: why does it need a -dbg package, as opposed to the -dbgsym package on ddebs.ubuntu.com? Does it need a separate build pass with different compiler options? [19:06] IntuitiveNipple: the general answer to your question is that running 'update-maintainer' from ubuntu-dev-tools will sort it out for you, but ... [19:06] Hmmm... we have two debug symbol systems? [19:07] -dbg is for (a) packages that already had it in Debian, where it isn't worth diverging to remove it (b) cases where it needs a separate build pass [19:07] -dbgsym handles cases where the debug symbols can be extracted entirely automatically [19:08] Oh! that explains alot! I am debugging a complex AT-SPI > java > eclipse issue and almost all other packages had -dbg packages so I *assumed* in view of bug #29294 that it was 'missing' [19:08] Launchpad bug 29294 in orbit2 "please provide a liborbit2-dbg debug package" [Wishlist,Confirmed] https://launchpad.net/bugs/29294 [19:09] This is what happens when constantly testing new installs... this one didn't have the ddebs repo added to apt sources ! [19:11] it's possible that 29294 predates ddebs [19:11] or at least predates them being widely known and used [19:11] I'll close that bug with an explanation [19:12] Yes, although alter comments fooled me too... from late last year. I'll update with a comment to where they are :D [19:12] i'm already doing it... you want me to stop? [19:12] I'm happy to do it since I have authoritative and helpful links to hand [19:12] Thanks [19:12] I was referring to pitti's email of Novmeber 2007 on devel-discuss announcing it [19:13] there's a wiki page with up-to-date information and help [19:13] Good... Google didn't find that for me so far [19:13] DebuggingProgramCrash [19:14] I looked at all the other Debug* pages except that one earlier! [19:14] could have saved myself 1/2 hour [19:14] bug updated [19:15] I only got onto that because I've finalyl pinned down why the Gnome at-spi/gail/atk-bridge causes problems for eclipse (got a decent backtrace from one of the threads) and wanted to see if there was more debug info for gdb... turns out there isn't after all :s [19:19] Hi, it seems that bug 235105 isn't properly fixed for me; I'm running stock jaunty and my harddisk spins down on *AC* as well as on batt often. (a about once every 5 minutes or so) Should I comment on the bug? [19:19] Launchpad bug 235105 in pm-utils "scripts in /etc/pm/power.d should be called after resuming/ thawing" [Undecided,New] https://launchpad.net/bugs/235105 [19:19] * bug 59695 [19:19] Launchpad bug 59695 in pm-utils "High frequency of load/unload cycles on some hard disks may shorten lifetime" [Critical,Fix committed] https://launchpad.net/bugs/59695 [19:31] guud eater afternoon [19:31] is pitti back? [19:31] is it known that apport / ubuntu-bug won't work with proxy? === emgent_ is now known as emgent [19:40] BUGabundo: https://bugs.edge.launchpad.net/ubuntu/+source/python2.5/+bug/94130 [19:40] Ubuntu bug 94130 in apport "HTTPS over proxy fails" [Undecided,Confirmed] [19:42] lfaraone: thanks [20:40] kees: eh, we generally want them fixed, since otherwise they're hardly security-supportable... which package are you looking at? === ScriptRipper_ is now known as ScriptRipper === jussi01 is now known as android === android is now known as jussi01 === james_w` is now known as james_w === yofel_ is now known as yofel === Seeker`_ is now known as Seeker` [21:51] I'm having some major problems with my Jaunty KDE3.5 torrent tracker...which tracker does Ubuntu use? [21:53] Ah, never mind, found it on the main tracker page. BitTornado. [21:53] * kb9vqf feels kinda stupid [22:11] slangasek: linux86. i can upload the fix shortly. [22:23] cjwatson: almost done, I had the family at my house this afternoon/evening...I plan on finishing things up tomorrow, is that ok? [22:25] cjwatson: I still haven't recieved a green light from mark, but I am doing all this hoping that it will come...I know he wants a change and everyone has responded well to the new version === andresmujica2 is now known as andresmujica [22:35] kwwii_: I'll be away all day tomorrow, unfortunately, so I hope Evan is around ... [22:38] #ubuntu-wisconsin [22:42] cjwatson: I've snet him an email. I'll just have to see how this plays out. Mark might request changes anyway [22:43] What changes are you talking about, btw? [22:44] ion_: are you talking to me? (with my best DeNiro accent) [22:45] kwwii: Well, you’re the only one here. [22:45] ion_: http://sinecera.de/time_zones.png [22:46] and soon I am gone as well :p [22:46] Neat === |Baby| is now known as Baby [23:05] hello, how do i get a package in the "partner/web" category in the ubuntu repositories [23:05] i'm a programmer for a IM archival company in massachusetts [23:06] and I've crafted a debian file for each system {hardy,intrepid,jaunty} === Tonio__ is now known as Tonio_ [23:37] ni|: I don't think that's the point of the partner repo [23:40] I think the most logical thing for you to do would be to set up your own repo [23:40] for further assistance, use #ubuntu-motu though === asac_ is now known as asac [23:46] Chipzz: thanks [23:48] kwwii_: I think I'm going to have to go ahead and upload ubiquity; we need to get the other changes tested in a definite timeframe [23:49] kwwii_: we'll just have to consider the map changes separately