[01:28] <amastronardi> hello
[01:29] <amastronardi> i'm new in BugSquad team and would like some help triaging a bug
[01:29] <amastronardi> there is someone that can help me?
[01:33] <amastronardi> hi zlj
[01:36] <amastronardi> hi ogasawara
[01:43] <hggdh> amastronardi: all you need to do is ask a question, somebody will answer
[01:45] <amastronardi> hi hggdh
[01:45] <hggdh> hi amastronardi
[01:45] <amastronardi> i-m triaging https://bugs.launchpad.net/ubuntu/+source/evince/+bug/662346
[01:45] <ubot2> Launchpad bug 662346 in evince (Ubuntu) "Faulty PDF print preview with specific pdf file (provided) (affects: 1) (heat: 6)" [Undecided,New]
[01:46] <amastronardi> i reproduced it and i-m finding duplicates now
[01:46] <amastronardi> i think that the bug i-m triaging is a duplicate of this https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/443026
[01:46] <ubot2> Launchpad bug 443026 in evince (Ubuntu Karmic) (and 6 other projects) "Printing produces broken PDF (affects: 7) (dups: 2) (heat: 45)" [High,Fix released]
[01:48] <amastronardi> if i-m not wrong, evince depends on poppler/cairo
[01:48] <amastronardi> but launchpad says it was fixed in 9.10
[01:50] <hggdh> amastronardi: they do not seem to be the same issue
[01:51] <amastronardi> ok, will continue looking for duplicates and if not will mark as "confirmed"
[01:53] <hggdh> amastronardi: 443026 deal with embedded graphics that do not print, 662346 shows rendering issues on titles
[01:55] <amastronardi> your are right
[02:02] <hggdh> amastronardi: if it were to be a perfect match, we would then have a regression; since the original bug was from 9.10, the best would be to tag the new bug as 'regression release maverick', add alink to the old bug, and *keep* with the new bug
[02:02] <hggdh> er, 'regression-release maverick'
[02:22] <amastronardi> hggdh: ok, thanks for that explanation ;-)
[02:43] <andersk> Can someone set bug 658907 to priority Medium (moderate impact on a core application)?
[02:43] <ubot2> Launchpad bug 658907 in eglibc (Ubuntu) "[SRU] crash in getlogin() (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/658907
[02:45] <hggdh> andersk: done
[02:46] <andersk> Thanks!
[03:19] <amastronardi> I marked a bug as duplicate. What status and importance shall I assign it?
[03:20] <micahg> amastronardi: no status/importance change for duplicates
[03:20] <amastronardi> thanks micahg :-)
[04:27] <amastronardi> i just confirmed a bug for a package Maintained by the Ubuntu Kernel Team. How shall I assign the bug to them?
[04:27] <persia> You shouldn't.
[04:28] <persia> Work on Ubuntu is entirely on a volunteer basis (although some folk are paid to do specific things, so may have an unusual reason to volunteer).  Because of this, we don't assign bugs to people, but rather encourage people to assign bugs to themselves.
[04:29] <persia> In the specific case of the kernel team, I know they have at least one member who spends all his time processing and reviewing bugs to prepare available worklists for folks interested in different parts of the kernel.
[04:30] <persia> So, if you've confirmed a bug, they will likely notice, and someone will assign themselves when they have time to work on it.
[04:30] <amastronardi> ok, thanks persia :-)
[04:30] <persia> If a long time passes and nobody felt like working on it, you might be asked to reconfirm with a newer kernel, because there's lots of people who have nothing to do with Ubuntu who prepare kernel patches.
[04:31] <amastronardi> i'm new in the BugSquad and learning the procedures here
[04:35] <persia> No worries.
[04:36] <persia> The key bit is that we're the second line of response.  The support team does a lot, but some users have problems that go beyond support, so they (or the support team) tend to file bugs.
[04:36] <persia> It is our responsibility to make sure the bugs are the best they can be, and accurately describe a problem, how to reproduce the problem, and where the problem occurs.
[04:37] <persia> We also try to make sure the problems are widely known in hopes folks not directly involved in Ubuntu can help fix stuff.
[04:37] <persia> So we spend a lot of time testing upstream or Debian packages to see if the bug is there, and reporting the bug in their bug trackers.
[04:40] <amastronardi> leaving for today, bye everyone
[05:54] <RedSingularity> Can someone check if bug 659696 is worth marking wishlist?  The guy is insisting I mark it as wishlist but I am not sure that it is good for that.  I sent him to ubuntu brainstorm but he wants a wishlist marker.
[05:54] <ubot2> Launchpad bug 659696 in update-manager (Ubuntu) "Terminal screen grows too big (affects: 1) (heat: 1155)" [Undecided,Incomplete] https://launchpad.net/bugs/659696
[05:54] <RedSingularity> Any help would be great.
[05:55] <micahg> RedSingularity: wishlist is fine
[05:55] <RedSingularity> Really?
[05:56] <micahg> RedSingularity: sure, it's a feature request
[05:56] <RedSingularity> He wants a font size change though
[05:56] <micahg> RedSingularity: it might end up won't fix, but it's still wishlist
[05:56] <RedSingularity> Ok....can you mark it?
[05:57] <RedSingularity> micahg:  I never worked with a wishlist item.  WHat can I do with it next?
[05:58] <micahg> RedSingularity: nothing, as long as there's enough information for the developer to work/make a decision about it, it can be marked triaged
[05:58] <micahg> RedSingularity: done
[05:58] <RedSingularity> micahg:  well i did test it on a screen like his and it seems to be "confirmed"
[05:58] <RedSingularity> i can reproduce
[05:59] <micahg> RedSingularity: right, that's fine, that's usually good enough, I marked it triaged already though
[05:59] <micahg> RedSingularity: in these cases, you just want to make sure the feature doesn't already exist in which case, you can convert to question and help the user w/the feature
[06:00] <RedSingularity> ok great!  Thanks as usual micahg :)
[06:00] <micahg> RedSingularity: np, I'm heading to sleep, night
[06:00] <RedSingularity> night :) :)
[06:10] <persia> micahg, That bug isn't sensibly triaged.  Just changing the font size won't solve the issue for the full span of screens.
[06:11] <micahg> persia: as I read it the request was to make it dynamic based on screen size
[06:11] <micahg> persia: perhaps I skimmed it too quickly
[06:11] <persia> It's dup to something else.  I'm looking
[06:11] <micahg> persia: k, thanks
[06:12] <persia> maybe bug #263651 but that seems too high a number
[06:12] <ubot2> Launchpad bug 263651 in thunderbird (Ubuntu) "Thunderbird renders fonts too small w/o dpi pref set (affects: 3) (heat: 7)" [Undecided,Confirmed] https://launchpad.net/bugs/263651
[06:12] <micahg> persia: that's thunderbird specific
[06:13] <persia> Oh, it's a chrome thing?  OK.  Bug #88289 looks clearly firefox, and is maybe closed?
[06:13] <ubot2> Launchpad bug 88289 in firefox (Ubuntu) "Firefox default layout.css.dpi config wrong. (affects: 1) (heat: 2)" [Low,Confirmed] https://launchpad.net/bugs/88289
[06:13] <micahg> persia: yeah
[06:14] <persia> Right.  It's bug #118745, which is incorrectly "Fix Released" just because someone stuck a workaround in place.
[06:14] <ubot2> Launchpad bug 118745 in xorg-server (Ubuntu) (and 4 other projects) "Font sizes in Gutsy are affected by bad X.org DPI detection (dups: 15) (heat: 166)" [Medium,Fix released] https://launchpad.net/bugs/118745
[06:14]  * micahg needs to do a Mozilla bug cleanup after the packaging work for natty is done
[06:15] <persia> But there was some 5 digit bug: I remember arguing strongly that 40 and 300 were not insane values for DPI.
[06:15] <micahg> persia: there's an upstream commit mentioned, so it seems to not just be a workaround, but the upstream bug is targetted at radeon, so other drivers might not be fixed
[06:16] <persia> No, it's a GNOME bug.
[06:18] <persia> http://mail.gnome.org/archives/gtk-devel-list/2008-August/msg00044.html is some old discussion.  Might get used in GTK+3.0
[06:21] <persia> Aha, I went off on bug #157398, which is really dup to 118745
[06:21] <ubot2> Launchpad bug 157398 in gnome-control-center (openSUSE) (and 2 other projects) "GNOME default DPI doesn't match X default DPI (affects: 9) (dups: 2) (heat: 70)" [Unknown,Fix released] https://launchpad.net/bugs/157398
[06:21] <persia> https://bugzilla.gnome.org/show_bug.cgi?id=378338 is slightly more interesting, although we don't have functional application support.
[06:21] <ubot2> Gnome bug 378338 in settings-daemon "Deal with X servers which misreport the screen's dimensions" [Normal,Resolved: fixed]
[06:21] <RedSingularity> Guys, what is the command to perform a distribution upgrade?  apt-get dist-upgrade was it?
[06:22] <micahg> RedSingularity: as in to a new Ubuntu version?
[06:22] <persia> RedSingularity, Support in #ubuntu.  `do-release-upgrade`
[06:22] <RedSingularity> micahg yes sir
[06:23] <RedSingularity> persia thanks
[06:25] <RedSingularity> persia:  I cannot find a "do-release" in the options
[06:25] <persia> Anyway, regardless of which of the various bugs about it one uses: the issue is likely in one of GTK, Cairo, or gnome-control-center.  It's unlikely that any leaf application can do the right thing until those are sorted (and I don't believe them to be sorted).
[06:25] <persia> RedSingularity, `do-release-upgrade` is the entirety of the command.
[06:26] <micahg> persia: ok, I've seen a number of mozilla bugs related to teh topic as well
[06:26] <RedSingularity> persia:  Just found out :)
[06:30] <persia> micahg, Indeed.  It's not so bad for people in the 80-125 DPI range, but outside that things get a little odd.
[06:31] <persia> And I'm really not convinced we even have any idea how to do things properly for > 300 DPI range, except when projected.
[06:31] <micahg> persia: probably not too many practical applications yet
[06:32]  * persia owns a few devices that are > 300 DPI
[06:32]  * persia owns one device that is ~ 1300 DPI
[06:34] <micahg> k, going to sleep for real this time :)
[06:35] <persia> And there are mass-market 1024x600 2.5" screens on the market here (that's ~475 DPI)
[06:35]  * micahg didn't realize that small could go that high...
[06:35] <persia> Good night.
[06:36] <micahg> night :)
[06:36] <persia> Yeah.  It's a "phone" with a shiny high-res interface.
[06:57] <RedSingularity> Will "apport-collect" gather info about the OS itself?  Like Installation media and current distro and architecture?
[06:59] <persia> Depends on the apport-hooks engaged when it is called.  Typically not.
[06:59] <persia> architecture is always interesting.  Release is often interesting (although package version is usually more interesting than release).  Installation media is almost never interesting.
[07:07] <RedSingularity> persia: hmmmm so i guess i should just ask for things like that then if they are not included?
[07:19] <RedSingularity> Oh how can I remove bugs from my "related" list on launchpad?
[07:25] <persia> RedSingularity, Only ask for things that are interesting: things you believe will help understand the bug.  Asking a useless question is worse than ignoring the bug, because the user has to do potentially complicated things for no benefit.
[07:25] <persia> And you can't remove bugs from your related list: it's generated automatically based on comments, subscriptions, assignments, team interactions, etc.
[07:26] <RedSingularity> persia:  I see, Thanks x2 :)
[07:42] <RedSingularity> Can someone mark bug 660851 as "low"?
[07:42] <ubot2> Launchpad bug 660851 in update-manager (Ubuntu) "Update manager very slow on 10.10 (affects: 1) (heat: 1157)" [Undecided,Incomplete] https://launchpad.net/bugs/660851
[07:44] <persia> Why?  More importantly, why when it's still incomplete?
[07:45] <persia> Also, have you tried to replicate running update-manager on 10.04 and 10.10 to see if they require different resources?  The `time` utility is a good way to check usage when things are quick enough you wouldn't notice.
[07:46] <RedSingularity> Time?  Let me see........
[07:47] <persia> So you might run `time update-manager` in both environments, and see if there is a difference.
[07:47] <persia> If there is a difference, you can confirm the bug, and then you want to try to find out *why* there is a difference.
[07:48] <RedSingularity> Ok disregard, I will try that out.  That "time" command is something I could have used a lot in the past!  Seems very useful.
[07:48] <persia> When you're unsure how to get some bit of information, just ask here.  It's very likely someone has encountered the issue before.
[07:55] <RedSingularity> Is there a command to get system usage info for a particular command?  CPU, RAM, HDD, etc
[08:05] <persia> There are different commands for different information requirements.  What problem are you trying to solve?
[08:12] <RedSingularity> persia:  I want to know if the update-manager is using a lot of CPU while updating.
[08:25] <persia> RedSingularity, And time doesn't give you enough information?
[08:25] <RedSingularity> Time gives me the time factor but not a CPU load
[08:26] <persia> RedSingularity, So, you compare the "sys" and "user" times between the two releases, and you have a relative comparison between the loads.
[08:27] <persia> I suspect you could write something with getrusage if you need more specific information
[08:29] <RedSingularity> persia:  I will look into that then tomorrow.  I am off to bed now.  Have a good one :)  And thanks
[14:44] <xteejx> bug 662388 if anyone remembers from yesterday, I've kinda solved it... vbox doesn't play nicely with encrypted home folder .VritualBox inlcuding hard disks are in there
[14:44] <ubot2> Launchpad bug 662388 in virtualbox-ose (Ubuntu) (and 1 other project) "virtualbox-ose and VBoxManage hang when creating hard disk with encrypted home directory (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/662388
[14:47] <xteejx> Can someone set Triaged for me on bug 662388 (I have privilege just not meant to)
[14:47] <ubot2> Launchpad bug 662388 in virtualbox-ose (Ubuntu) (and 1 other project) "virtualbox-ose and VBoxManage hang when creating hard disk with encrypted home directory (affects: 1) (heat: 6)" [Medium,New] https://launchpad.net/bugs/662388
[14:48] <charlie-tca> done
[14:48] <xteejx> thanks charlie )
[14:48] <xteejx> * :)
[14:48] <charlie-tca> You are welcome
[14:48] <charlie-tca> Thanks for sending it upstream
[14:48] <xteejx> No prob
[14:49] <charlie-tca> BUGabundo: u+1 is open already!
[14:50] <xteejx> It's not something stupid like vbox doesn't have access because of groups?
[14:50] <xteejx> Is it
[14:50] <BUGabundo> charlie-tca: YAY
[14:50]  * xteejx gets the defibrillator
[14:50] <xteejx> Stand back, heart attack lol
[14:50] <BUGabundo> PUM
[14:51] <BUGabundo> so who was that kid that was lost in here, running natty without ever have gonne into +1 ?
[14:51] <charlie-tca> xteejx: I don't think so. I would think it has more to do with encrypted VBox directory
[14:51] <xteejx> what?? lol
[14:52] <xteejx> charlie-tca: So chance of a fix would be unlikely then? :(
[14:52] <charlie-tca> Don't know that part. I suspect they will try to come up with a fix
[14:52] <xteejx> yeah "don't use encryption" :P
[14:53] <charlie-tca> That, too
[14:53] <xteejx> only wanted it for natty
[14:53] <charlie-tca> I don't encrypt /home, but I use the puel edition, too
[15:04] <hggdh> well, this, then, explain why it worked for me -- my VMs are set on a different filesystem
[15:04] <hggdh> and only $HOME is encrypted
[15:06] <xteejx> hggdh, hence no encryption on the vdi's ahh :)
[15:07] <xteejx> it works if i create them in /tmp and move them
[15:07] <xteejx> its just the creation
[15:09] <hggdh> sounds like it
[15:10] <xteejx> I don't think it'll be an easy fix other than using /tmp as standard for creation
[15:10] <xteejx> and then moving it
[15:12] <xteejx> I dunno, its working now, gonna crack on and install natty in vbox
[15:17] <hggdh> xteejx: creating 512 and 1024 Mbytes images in $HOME works
[15:17] <xteejx> hggdh, I haven't tried to be honest, are you encrypted?
[15:18] <hggdh> on $HOME, yes
[15:18] <xteejx> strange that 8000 doesn't and 1024 does....
[15:19] <hggdh> 2048 also works.
[15:20] <xteejx> :O
[15:20] <xteejx> thats weird
[15:20] <hggdh> not really
[15:20] <xteejx> how so?
[15:20] <hggdh> perhaps a boundary condition
[15:20] <xteejx> 2G limit?
[15:21] <hggdh> also, usually you can monitor execution via iotop and htop
[15:21] <hggdh> and even via the HD light
[15:21] <xteejx> yeah i did, vboxsvc i think it was was sitting at 100%
[15:21] <xteejx> but doing nothing with hd
[15:21] <hggdh> what was 100%?
[15:22] <xteejx> It was either vboxsvc or the other vboxXXXX one
[15:23] <hggdh> yeah. System is a bit unresponsive now, with 4096
[15:23] <xteejx> so maybe its not failing but just taking so damn long to decrypt/encrypt everyhting for 8G
[15:24] <hggdh> on creation, yes
[15:24] <xteejx> yes creating in /tmp and moving to HardDisks took a fe minutes with 8G lol
[15:24] <xteejx> *yet
[15:25] <hggdh> C4096 at 50%
[15:26] <xteejx> taking w hile
[15:26] <xteejx> a while...why cant I type today?!
[15:26] <hggdh> yes
[15:26] <hggdh> it might be interesting to run the vdi creation under time
[15:26] <hggdh> for both encrypted and clear-text
[15:26] <xteejx> what does that do?
[15:27] <hggdh> 'time' will write, at the end of the run, how long it took to run the command
[15:27] <xteejx> just a timer?
[15:27] <xteejx> simple enough I suppose
[15:28] <hggdh> more than that, but on the basic invocation yes
[15:28] <xteejx> I fI get a chance later I'll have a go at that and tick it in the bug report
[15:28] <hggdh> (man time will show you the light)
[15:28] <hggdh> or, perhaps, quite confuse you ;-)
[15:28] <xteejx> lol no change there then ;)
[15:29] <hggdh> xteejx: it would be interesting, giving a simple table with 'n' runs of 512, 1024, 2048 on both clear-text and encrypted
[15:30] <xteejx> hggdh, that can be arranged no problem
[15:30] <hggdh> even more since the upstream bug has been closed with a WFM
[15:30] <xteejx> I'll get on hat later on
[15:30] <hggdh> xteejx: thank you
[15:30] <xteejx> hggdh, no thank you for helping (as always)
[15:31] <xteejx> off for a bit anyway all catch ya al alters
[17:20] <xteejx> How do I upgrade to natty in vbox? I forgot
[17:21] <jpds> do-release-update -d ?
[17:22] <vish> xteejx¦ ^
[17:22] <xteejx> Will that work yet? ok
[17:22] <jpds> xteejx: Only one way to find out.
[17:22] <xteejx> $ do-release-upgrade -d
[17:22] <xteejx> Checking for a new ubuntu release
[17:22] <xteejx> No new release found
[17:23] <xteejx> maybe not lol
[17:23] <jpds> xteejx: sudo -i; cd /etc/apt/; sed -i s/'maverick'/'natty'/ sources.list
[17:23] <xteejx> oh change mavertick to natty in sources?
[17:23] <xteejx> ;)
[17:23] <jpds> Yes; sauces.
[17:23] <xteejx> No prob, I'll get my ketchup on
[17:24] <vish> yummy!
[17:24] <xteejx> ;)
[17:24] <xteejx> Think I'll have diner soon actually am hungry now heh
[17:24] <xteejx> jpds: Thanks
[17:27] <charlie-tca> I think you have to change all the sources, then use apt-get dist-upgrade or aptitude ??? to upgrade at this time, don't you?
[17:27] <charlie-tca> Oh, maybe I am behind again
[17:27] <xteejx> I've changed the sources and did apt-get update, but worried about what next
[17:27] <xteejx> I would ask in +1 but everyone's asleep
[17:28] <charlie-tca> You have to do apt-get dist-upgrade to get everything to move to natty
[17:28] <charlie-tca> and then you get whatever breaks, too.
[17:28] <xteejx> I was always told the partial upgrade thing is a big no no
[17:29] <hggdh> natty is open, but not ready for installs/upgrades
[17:29] <xteejx> hggdh, I wanna start on merges, but need to use whatever is available in natty (am using vbox)
[17:29] <hggdh> I hope you are aware that we should expect some significant breakages when moving to Gnome-3...
[17:29] <xteejx> hggdh, we're moving to gnome 3??
[17:29] <charlie-tca> xteejx: apt-get upgrade does a safe upgrade, but I don't think it upgrades all of it, does it?
[17:30] <xteejx> I'll try the apt-get dist-upgrade thing
[17:30] <charlie-tca> OTOH, it is VBox, you can always delete and start again
[17:30] <xteejx> Any objections?
[17:30] <xteejx> or suggestions why not lol
[17:30] <hggdh> go for it!
[17:30] <xteejx> charlie-tca: True, but I don't wanna hang myself starting over hehe
[17:30]  * hggdh grabs some popcorn and sits down to watch
[17:31] <charlie-tca> If it works, I may try it next
[17:31] <xteejx> 216 upgrades, 13 installs, 0 removals....let's see
[17:32] <xteejx> I've subscribed to natty m-l and dev-announce so keeping up2date this time
[17:32] <xteejx> didn't even know about gnome 3, but def happy
[17:35] <xteejx> I'll ping you when it's done charlie and let you know if it's "stable"
[17:36] <hggdh> right now it should be stable, there are not that many critical pacakges
[17:36] <hggdh> that have been ported to natty, I mean
[17:37] <xteejx> gcc, python, binutils, busybox << what about them?
[17:39] <hggdh> they should have been updated; python is a special case, I am not sure we are going to 3.x (and _which_ 3.x)
[17:43] <xteejx> hggdh, ahh ok
[17:54] <hggdh> also, a lot of the initial uploads to Natty will probably be a no-change-just-rebuild under the new toolset. So... one is usually safer at the very start of the cycle
[17:54] <hggdh> or it breaks horribly from start. Hum. Choose your poison
[17:56] <xteejx> lol
[17:56] <micahg> hggdh: doubtful, most uploads will be new versions and then probably FTBFS fixes :)
[17:57] <xteejx> ftbfs for the new gcc probs
[18:00] <xteejx> rebooting vm in a min here goes nothing.....or everything :P
[18:07] <xteejx> charlie-tca: It seems relatively fine in vbox at the mo, just to let you know
[18:08] <charlie-tca> Great! Of course, this is just the beginning. Should be plenty of breaking things down the road.
[18:08] <devildante> is anyone having problems to boot with UUID in natty?
[18:08] <xteejx> Of course, I'm gonna expect pklenty o breakages
[18:08] <xteejx> like my keyboard for example..... lol
[18:09] <xteejx> devildante: No idea, using vbox
[18:10] <charlie-tca> hmm, xteejx. Shouldn't matter, fstab will still use uuid, won't it?
[18:10] <devildante> yeah...
[18:10] <xteejx> you mean devildante ;)
[18:11] <xteejx> oh dear........
[18:11] <xteejx> screen buggered when installing vbox aditions in natty
[18:22] <charlie-tca> Well, it sounds like time to do my hardware upgrade then.
[18:27] <xteejx> It's ok I rebooted and done it again, it was fine
[18:28] <njin> pedro_: around ?
[18:36] <njin> Hello to all, what can i suggest to this reporter ? https://bugs.launchpad.net/ubuntu/+bug/662109
[18:36] <ubot2> Launchpad bug 662109 in ubuntu "incorect menu opening up0 (affects: 1) (heat: 8)" [Undecided,Incomplete]
[18:37] <xteejx> njin: What version of ubuntu?
[18:37] <xteejx> Does he mean a download, or the Downloads folder?
[18:39] <njin> xteejx: i think that happen when he  open Downloads folder
[18:40] <charlie-tca> version of Ubuntu? is that Unity?
[18:40] <charlie-tca> or just a very customized desktop?
[18:41] <njin> no, i don't think, but i require a better description
[18:41] <charlie-tca> Does it work if using Gnome?
[18:41] <pedro_> IIRC the reporter is trying to install a theme which is located on the Downloads folder and instead of choosing the 'theme' he selected the Downloads folder instead
[18:41] <pedro_> ?
[18:41] <pedro_> how's that a bug?
[18:41] <charlie-tca> Then it would not be a bug, would it?
[18:42] <xteejx> Maybe it's not, is isn't filed well
[18:42] <xteejx> *it
[18:42] <xteejx> njin: The bug description needs to be clearer, including reproduction steps
[18:42] <njin> ok mi ask  a better description
[18:42] <pedro_> njin, ask the reporter for steps to reproduce the issue, because it doesn't say anything
[18:43] <xteejx> pedro_: Snap :)
[18:43] <njin> ok, thanks
[18:43] <pedro_> xteejx, :-)
[18:43] <devildante> pedro_: can you change the topic of the channel, please? :)
[18:44] <xteejx> next meeting TBA?
[18:44] <pedro_> let me see if i can do it
[18:44]  * xteejx says "Computer, change the topic in #ubuntu-bug"
[18:45] <xteejx> Well that didn't work
[18:45] <pedro_> i don't have the rights to do that
[18:46]  * micahg wonders who does
[18:46] <pedro_> bdmurray, ^ may you please change the topic?
[18:47] <bdmurray> when is the next meeting?
[18:47] <devildante> TBA, I suppose...
[18:47] <micahg> Tue Nov 9
[18:47] <devildante> ah
[18:47] <pedro_> 09 Nov
[18:47] <xteejx> 9th
[18:47] <pedro_> yeah
[18:47] <devildante> 09 Novembre :p
[18:47] <pedro_> devildante, it's the second Tuesday of the month
[18:48]  * devildante forgot that :p
[18:48] <xteejx> hehe
[18:48] <xteejx> I forget my name sometimes, don't worry ;)
[18:48] <pedro_> lol
[18:49] <bdmurray> I'm wokring on an lp change atm but will get to it shortly
[18:50] <pedro_> thanks bdmurray
[18:50] <devildante> thanks :)
[18:52] <xteejx> Why am I getting W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/natty/main/source/Sources.gz  404  Not Found
[18:52] <xteejx> , W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/natty/main/binary-i386/Packages.gz  404  Not Found
[18:52] <charlie-tca> Maybe you need to add the key again?
[18:53] <xteejx> I never had the key afaik
[18:53] <devildante> I get it too, weird...
[18:53] <charlie-tca> Oh, no. Probably doesn't exist, too early for extras.ubuntu.com
[18:54] <devildante> whoops, I thought it was for main repos :p
[18:54] <micahg> yeah, extras is a post release thing AFAIK
[18:54] <xteejx> oh fair enough :)
[18:54] <devildante> oh, 2.6.36 landed in natty! great :)
[18:55] <xteejx> devildante: Certainly did :)
[18:55] <devildante> thanks bdmurray :)
[18:56] <bdmurray> no problem
[20:13] <njin> hello, can someone set importance https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659444 thanks
[20:13] <ubot2> Launchpad bug 659444 in linux (Ubuntu) "HP Pavilion DV6 Wifi Button Red/Blue blinking (affects: 1) (heat: 10)" [Undecided,Confirmed]
[20:14] <devildante> njin: did he enable bluetooth? (from the bluetooth icon)
[20:14] <devildante> if not, then this is normal
[20:15] <njin> But the problem is, that when i transfer data (example: surfing internet), the button blinks to show it (red blue red blue..). But it shouldn't.
[20:16] <njin> devildante: ^^
[20:18] <vish> njin¦ actually it should in my laptop
[20:18] <vish> njin¦ that bug is a dup
[20:18] <njin> vish: ok thanks
[20:19] <vish> njin¦ there are two types of behavior, certain laptops it is supposed to blink and in some it is not supposed to , there was a bug that it was not blinking, that got fixed … but a few it shouldnt not
[20:19] <vish> there still a bug somewhere regarding the blinking where it is not supposed to..
[20:20] <njin> vish: thanks, i'm looking for the dup
[20:20] <vish> np..
[20:36] <simar> how to open recovery mode in a live usb ubuntu... maverick is not booting up in my computer .. so iwant to test using live usb to avoid spoiling my current release ... is there a way
[20:36] <micahg> !support | simar
[20:36] <ubot2> simar: The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org
[20:37] <simar> micahg, i asked there but in vain..
[20:37] <simar> micahg, actually i want this regarding testing ..
[20:38] <simar> micahg, i hope there must be a solution else fixing bootup issue will be a big mess..
[20:51] <njin> hello, sytem restart session after 4 hours https://bugs.launchpad.net/ubuntu/+bug/659576 what can it be?
[20:51] <ubot2> Launchpad bug 659576 in ubuntu "from 10.04 to 10.10 system itself goes to the user's choice (10.10 система сама уходит на выбор пользователя) (affects: 1) (heat: 10)" [Undecided,Incomplete]
[20:52] <hggdh> simar: I never used the liveCD (either on a CD or on a USB stick); but if you can interrupt grub when it loads, you should have the option to start in recovery mode. Otherwise an alternate ISO will do it
[20:53] <hggdh> simar: but, really, this is not the place for support questions...
[20:56] <njin> pedro_: hello sytem restart session after 4 hours https://bugs.launchpad.net/ubuntu/+bug/659576 what can it be?
[20:56] <ubot2> Launchpad bug 659576 in ubuntu "from 10.04 to 10.10 system itself goes to the user's choice (10.10 система сама уходит на выбор пользователя) (affects: 1) (heat: 10)" [Undecided,Incomplete]
[20:57] <xteejyx> that bug title makes no sense
[20:57] <simar> hggdh, I think I should maintain the rules and regulation of the room. I will not like to discuss this any further here and I have already posted this issue on ubuntu forums . I hope someone will look there at this .. well thanks for your suggestion though, I will try the rest myself
[20:58] <pedro_> njin, kernel, xorg, temperature?
[20:58] <pedro_> njin, you might want to change the title as xteejyx said as well
[20:59] <njin> pedro_: thanks, looking for syslog and dmsg
[21:00] <pedro_> you're welcome
[21:01] <njin> you too
[21:01] <charlie-tca> njin: might want to ask the reporter to try turning off "auto-login" and see if it still happens
[21:02] <njin> charlie-tca: he change in auto-login to try workaround it
[21:02] <charlie-tca> okay
[21:06] <xteejyx> persia: You rang?
[21:06] <killoo> hi. I've recently upgraded from 10.04 to 10.10. 10.04 run without any problems. 10.10 now randomly completely freezes several times each day. screen, mouse and keyboard are dead (even magic keys aren't working).
[21:06] <xteejyx> !support > killoo
[21:06] <ubot2> killoo, please see my private message
[21:35] <njin> what is this ? https://bugs.launchpad.net/ubuntu/+bug/662919
[21:35] <ubot2> Launchpad bug 662919 in ubuntu "UPnP MediaServer KIO-slave (affects: 1) (heat: 6)" [Undecided,New]
[21:38] <xteejyx> At quick glance it looks like a wishlist bug
[21:38] <njin> it has attached tar with sources ??
[21:39] <njin> I ask to reporter
[21:39] <xteejyx> njin: That's fine, just clean it up to our standards for Wishlist bugs and find the url to link it
[21:39] <xteejyx> Oh, and the license
[21:41] <xteejyx> i.e. http://gitorious.org/kio-upnp-ms/mainline
[21:54] <njin> xteejyx: sorry, but this is the first time that i look a a wishlist and i really don't know how to do, the GNU license is attached named copying, can you complete this process ?
[21:57] <njin> xteejyx: don't worry, i think that is better for me to look at it with my mentor tomorrow.
[21:57] <njin> l
[22:16] <xteejyx> In natty I tried to run "sudo pbuilder create" and I got this at the end "W: Failure trying to run: chroot /var/cache/pbuilder/build/16738/. dpkg --force-overwrite --force-confold --skip-same-version --install"
[22:17] <xteejyx> it donloaded installed and configured and then done that
[22:19] <flipefr> hello
[22:20] <micahg> xteejyx: more appropriate in -motu
[22:20] <xteejyx> micahg: Oh ok
[22:21] <devildante> phew, I was worried no one could respond to xteejyx, I didn't know what to answer and I didn't want to let him cry :p
[22:21]  * devildante is over-sensitive sometimes
[22:21] <xteejyx> devildante: Bloody cheek! :P
[22:21] <flipefr> hi everyone
[22:21]  * xteejyx pokes devildante with a pitchfork
[22:21] <devildante> lol
[22:22] <flipefr> i have a bug that would like anybody to see
[22:22] <xteejyx> It's not artificially intelligent is it?
[22:23] <devildante> hmm... maybe :p
[22:23] <devildante> JFo: around?
[22:27] <charlie-tca> flipefr: bug and #
[22:27] <charlie-tca> unless it is moving too fast to catch
[22:29] <flipefr> charlie-tca: bug 658442
[22:29] <ubot2> Launchpad bug 658442 in nautilus (Ubuntu) "nautilus does not sort users's home directory content (affects: 1) (heat: 497)" [Undecided,Incomplete] https://launchpad.net/bugs/658442
[22:31] <charlie-tca> Well, that does not look right. What would you like to do with that?
[22:32] <flipefr> dont know, what do you recomend?
[22:34] <charlie-tca> Confirm it, it appears to be valid at least for Canadian locale
[22:34] <charlie-tca> Both the reporter and the confirm are using the same locale
[22:34] <flipefr> i will confirm it
[22:36] <flipefr> done
[22:46] <flipefr> charlie-tca: bye and thanks
[23:02] <valorin> Hey all.. I've got a critical bug (imho) which is being ignored... Can anyone help bump its priority for me? Bug #658069
[23:02] <ubot2> Launchpad bug 658069 in gvfs (Ubuntu) "Empty files written over gvfs by some editors (affects: 27) (dups: 3) (heat: 112)" [Undecided,Confirmed] https://launchpad.net/bugs/658069
[23:08] <greg-g> valorin: have you checked to see if those other bugs mentioned are not this bug? Could you write out a set of specific steps to take to recreate this bug?
[23:09] <kklimonda> they all seem to have the same root cause
[23:10] <valorin> All the mentioned bugs look to be the same bug, which is a problem in gvfs. Mine is the only one reported in gvfs though
[23:10] <valorin> Steps to reproduce are simple: use gvfs, use eclipse, get empty file...
[23:11] <kklimonda> it's actually reproducable with any editor that doesn't do the right thing
[23:11] <kklimonda> vim works fine, nano doesn't
[23:11] <kklimonda> the problem is applications shouldn't really save data in place.
[23:11] <kklimonda> but it's still a bug in gvfs that has to be fixed
[23:12] <greg-g> kklimonda: do you know of an upstream bug about this?
[23:12] <valorin> I believe this is an upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=627567
[23:12] <ubot2> Gnome bug 627567 in fuse "Data loss when writing files" [Major,Assigned]
[23:12] <kklimonda> indeed it is
[23:13] <hggdh> yes. I added the upstream bug, marked it Triaged/High, and proposed for Maverick
[23:13] <hggdh> this is serious food for SRU
[23:14] <kklimonda> yeah, I'm checking the patch now
[23:14] <hggdh> valorin: thank you for bringing this up
[23:15] <xteejyx> Have I done this right: bug 662986
[23:15] <ubot2> Launchpad bug 662986 in wwwoffle (Ubuntu) "wwwoffle-2.9f FTBFS (affects: 1) (heat: 6)" [High,In progress] https://launchpad.net/bugs/662986
[23:15] <valorin> Thank you for working on it for me :)
[23:15] <mgunes> is the bug in question bug #658069?
[23:16] <ubot2> Launchpad bug 658069 in gvfs (Ubuntu Maverick) (and 2 other projects) "Empty files written over gvfs by some editors (affects: 27) (dups: 3) (heat: 112)" [Undecided,New] https://launchpad.net/bugs/658069
[23:16] <hggdh> mgunes: yes
[23:16] <xteejyx> oops I haven't said what the change is :$
[23:18] <mgunes> I recall seeing another dupe of that which isn't marked as such now; but can't find it. pedro had responded to it.
[23:19] <mgunes> do we have a policy on closing or keeping bugs reported on installations upgraded from Debian or a derivative, which should be unsupportable?
[23:22] <mgunes> bug #662699 mentions an upgrade from Debian Lenny to 10.04 and then to 10.10; I feel like closing it without further inquiry.
[23:22] <ubot2> Launchpad bug 662699 in xserver-xorg-video-ati (Ubuntu) "documented x.org.conf module option is ignored (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/662699
[23:29] <kklimonda> hggdh: any idea where does fuse have a bugtracker? source is hosted on sf.net but there is no link to any bts neither there nor on its homepage.
[23:31] <charlie-tca> You report ssh-fuse bugs to the mailing list at fuse-sshfs@lists.sourceforge.net
[23:37] <mgunes> there seem to be FUSE bugs in bugzilla.kernel.org under product: filesystem, component:other.
[23:38] <charlie-tca> Fuse bugs should be reported upstream to the mailing list
[23:39] <charlie-tca> the docs on fuse-ssh installed with it tell you the procedures
[23:39] <hggdh> thanks charlie-tca
[23:41] <kklimonda> charlie-tca: thanks
[23:41] <charlie-tca> You are welcome
[23:55] <kklimonda> argh, I don't have a natty pbuilder :/
[23:55] <persia> kklimonda, Then make one :)
[23:56] <kklimonda> persia: It's just a facepalm moment, I was supposed to do it few days ago and forgot about it
[23:56] <persia> heh
[23:56] <micahg> persia: that chromium/firefox libmoon issue is old, bug 538796 seems to be where's they're being duped now
[23:57] <ubot2> Launchpad bug 538796 in moon (Ubuntu) (and 1 other project) "cannot open Firefox/Chromium/Google Chrome when libmoon is installed (affects: 86) (dups: 17) (heat: 426)" [High,Confirmed] https://launchpad.net/bugs/538796
[23:57] <persia> sille777, ^^
[23:58] <sille777> hello again persia
[23:58] <persia> Do we have a stacktrace somewhere?
[23:58] <hggdh> anybody remember which channel deals with X?
[23:58] <kklimonda> hggdh: #ubuntu-x?
[23:59] <charlie-tca> yup
[23:59] <hggdh> kklimonda: now it is the time for me to facepalm...
[23:59] <micahg> hggdh: this is useful: https://wiki.ubuntu.com/IRC/ChannelList
[23:59]  * charlie-tca thinks "that's the one I can not remember"