[00:25] <penguin42> is there an easy way we can tell normal users to add a boot option?
[01:03] <hggdh> penguin42: apart from editing /etc/default/grub and running update-grub, not to my knowledge
[01:03] <hggdh> grub1 had a graphical hack to do that, but I am unaware of one for grub2
[01:03] <penguin42> hggdh: We really could do with something easier; it's hard to describe that to someone unfamiliar with hacking system files
[01:15] <hggdh> I agree
[01:30]  * penguin42 wonders what the right thing to do to bug 653750
[01:30] <ubot2> Launchpad bug 653750 in debian-installer (Ubuntu) "Error Shut down (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/653750
[01:42] <hggdh> penguin42: on the Responses page -- you could use "vague"
[03:33] <upsuper> is anyone here?
[03:33] <nigelb> !anyone
[03:33] <ubot2> A large amount of the first questions asked in this channel start with "Does anyone/anybody..."  Why not ask your next question (the real one) and find out?
[03:34] <upsuper> en.... I think I might find a bug about installer of Ubuntu 10.10
[03:35] <upsuper> I used UNetBootin to put the installer into my flash drive, and installed Ubuntu 10.10 RC via the flash drive
[03:36] <upsuper> and the installer identified my flash drive as /dev/sda, and my hard drive as /dev/sdb
[03:36] <upsuper> then write this to the /dev/fstab
[03:37] <upsuper> so I cannot boot my new system until I edit the fstab file manually
[03:37] <upsuper> is it an important bug? and have anybody filed this bug?
[03:52] <hggdh> upsuper: I do not know if this has been reported before. But I think it is a good idea to report
[03:53] <hggdh> worst scenario, it will be a duplicate; best scenario you get the cake for a brand new bug ;-)
[04:10] <micahg> hggdh: too late :)
[04:29] <hggdh> micahg: heh. I usually run with in/out announcements hidden...
[04:31] <kklimonda> hggdh: same here, I make an idiot out of myself at least once a day ;/
[04:32] <hggdh> kklimonda: glad to know I am in good company :-)
[04:32] <kklimonda> It's especially funny when I answer a question asked few hours earlier.
[04:32] <kklimonda> or even a day in case of some channels
[04:32] <hggdh> happens. A lot, I am afraid, at least with me
[04:47] <AbhiJit> hi
[12:07] <BUGabundo> mornanguetto
[13:31] <dcordes> Hello
[13:31] <dcordes> I am wondering if this a netbooklauncher or an onboard bug: onboard and onboard floating maximize button are both hidden when the 'go home' gnome-panel-applet button is pressed
[13:33] <dcordes> Actually I filled it in onboard already because there was a similar thing: https://bugs.launchpad.net/onboard/+bug/326120 Should I add it in netbook launcher as well ?
[13:33] <ubot2> Launchpad bug 326120 in onboard "RFE: Show onboard also on fullscreen applications (affects: 1) (heat: 4)" [Undecided,New]
[14:02] <Gigacore> AbhiJit: here
[14:03] <AbhiJit> Gigacore, hello! welcome!
[14:03] <Gigacore> hey AbhiJit!
[14:03] <AbhiJit> Gigacore, see this http://picasaweb.google.com/lh/photo/U04Fo6JztJAL9eM9M0YUWg?feat=directlink
[14:03] <AbhiJit> :P
[14:04] <Gigacore> AbhiJit: you a member too?
[14:04] <AbhiJit> Gigacore, yay!!! :D
[14:04] <Gigacore> cool
[14:04] <AbhiJit> omg Gigacore you are indian too!!! wow!!! :P :D
[14:04] <Gigacore> I actually submitted my request to join today.. they approved it now
[14:04] <Gigacore> :)
[14:04] <Gigacore> yea am from Bangalore
[14:04] <Gigacore> you?
[14:04] <AbhiJit> good
[14:04] <AbhiJit> mumbai!
[14:05] <Gigacore> nice
[14:05] <AbhiJit> Gigacore, give me your wiki address
[14:05] <Gigacore> I still don't have it.. just getting started with everything
[14:05] <AbhiJit> :O
[14:05] <AbhiJit> and how they approved you then? :o
[14:05] <Gigacore> only things I've read is Code of Conduct and Triag
[14:05] <AbhiJit> its mentioned in bugsquead requirement that set up wiki!
[14:06] <Gigacore> https://launchpad.net/~santhoshinbang
[14:06] <hggdh> yes, I just approved you :-)
[14:06] <Gigacore> thank you hggdh! :)
[14:06] <bilalakhtar> hggdh: approved him to bugsquad?
[14:06] <AbhiJit> hggdh, isnt it compulsory to have wiki first? it is said so on bugsquad page?
[14:06] <hggdh> Gigacore: you are welcome. Thank you for helping.
[14:07] <bilalakhtar> ah
[14:07] <AbhiJit> bilalakhtar, dont worry. will not stretch this topic just checking thats it
[14:07] <hggdh> AbhiJit: not not bugsquad. You should have a wiki if you apply for Ubuntu membership
[14:07] <AbhiJit> omg :o
[14:07] <hggdh> bilalakhtar: yes, to bugsquad
[14:07] <AbhiJit> i spent whole day setting up my wiki! :(
[14:08] <AbhiJit> when i was about to approved! :(
[14:08] <hggdh> heh
[14:08] <Gigacore> AbhiJit: don't worry.. even am finding out how to setup one ;)
[14:08] <Gigacore> :P
[14:08] <AbhiJit> Gigacore, :D
[14:09] <Gigacore> today is a good day! upgraded to 10.10 RC and got approved to bugsquad team :)
[14:09] <AbhiJit> yah
[14:10] <Gigacore> AbhiJit: mind sharing ur launchpad profile link?
[14:11] <AbhiJit> :)
[14:11] <Gigacore> and is that your desktop?
[14:12] <AbhiJit> Gigacore, offcourse!
[14:12] <AbhiJit> Gigacore, https://launchpad.net/~abhi-navale
[14:12] <Gigacore> cool
[14:19] <AbhiJit> Gigacore, so what you do?
[14:19] <Gigacore> I am studying B.Sc final year
[14:19] <Gigacore> CS
[14:19] <AbhiJit> hmm
[14:20] <AbhiJit> Gigacore, you may request for mentor and start learning bug triaging
[14:20] <Gigacore> yea sure..
[14:21] <Gigacore> when's the next hug day?
[14:36] <mortal> hello, could someone reactivate this https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/653043 bug, I have given the screenshot
[14:36] <ubot2> Launchpad bug 653043 in network-manager-applet (Ubuntu) "network-manager asks pin code on huawei e160e, the pin can not be entered because the pin window is unresponsive (affects: 1) (heat: 6)" [Undecided,Incomplete]
[14:39] <penguin42> mortal: Done
[14:39] <penguin42> mortal: I think it would have let you do that
[14:42] <mortal> thank you
[14:45] <hggdh> mortal: you yourself can change the status from Incomplete to New
[15:01] <mortal> k, I did nit know that before
[15:01] <mortal> o
[15:11] <hggdh> np
[15:27] <penguin42> so what's the right thing to do with bug 636329
[15:27] <ubot2> Launchpad bug 636329 in gimp (Ubuntu) (and 1 other project) "Gimp won't print preview (affects: 10) (heat: 56)" [Medium,Confirmed] https://launchpad.net/bugs/636329
[15:28] <penguin42> The upstream guys have fixed it and I've done a patch to fix it in the Ubuntu package and attached it, how do I suggest it should get released?
[15:31] <hggdh> penguin42: so you rebased Sven's patch?
[15:31] <penguin42> hggdh: Yeh
[15:31] <penguin42> hggdh: It was trivial, just one line in two files
[15:32] <penguin42> it was quite a nice chain really
[15:32] <hggdh> yes, I see.
[15:33] <penguin42> Someone in the bug had spotted that downgrading cairo2 helped, so I asked on #gtk+ and they said that cairo2 was more fussy about cairo_surface_mark_dirty, raised the bug on bugzilla.gnome.org, put that same info in, and it was fixed in a few hours
[15:34] <hggdh> heh
[15:37] <hggdh> YOu can attach a debdiff for it, and then subscribe Ubuntu Sponsors Team
[15:37] <hggdh> penguin42: a Q: are you active on b.g.o?
[15:37] <penguin42> what's b.g.o ?
[15:37] <hggdh> bugzilla.gnome.org
[15:37] <penguin42> hggdh: No, I'm not, just the normal report things that annoy me
[15:38] <BUGabundo> penguin42:  penguin42 penguin42....
[15:38]  * penguin42 looks at BUGabundo
[15:38] <hggdh> penguin42: thank you. You stated you were building GIT for gimp, and I wondered...
[15:38] <devildante> the danse of the penguin42! :p
[15:39] <hggdh> BUGabundo: BUGabundo BUGabundo .....
[15:39] <penguin42> hggdh: Oh I just thought before I reported it upstream I should check to see if the git version exhibited it
[15:39] <devildante> hggdh: hggdh hggdh...
[15:39]  * BUGabundo slaps devildante with a wet trough 
[15:39] <hggdh> penguin42: OK, thanks. We are always looking for people that also dwell on b.g.o (and other upstreams)
[15:40] <hggdh> this is an echo chamber, it seems
[15:40] <devildante> seems, seems, seems...
[15:40] <penguin42>  /bin/echo
[15:40] <penguin42> stty -echo   even
[15:41] <penguin42> hggdh: So, how does one do that with debdiff - I just attached the patch file (that I'd dropped into debian/patches)
[15:41] <devildante> could that be the source of duplicate bugs? (bugs, bugs, bugs...) :p
[15:41] <hggdh> devildante: I think you have something there ;-)
[15:42] <BUGabundo> lol
[15:43] <hggdh> penguin42: (1) grab the current source for gimp on Maverick; (2) add your patch on the correct place (should be ~/debian/patches); (3) run 'dch -i' and add one to the Ubuntu change, and explain what you did
[15:43] <devildante> penguin42, include lp bug number in 'dch -i' if there is one
[15:44] <penguin42> hggdh/devildante: OK, that sounds pretty much what I did for my ppa build of it, but I should actually predict the next package version number?
[15:44] <hggdh> end this comment with '(LP: #636329)'
[15:45] <devildante> penguin42: I guess you should keep the upstream version number and add "ubuntu1"
[15:45] <hggdh> penguin42: well, yes, you are proposing the next Ubuntu revision
[15:45] <penguin42> ooh,didn't know I could do that
[15:45] <hggdh> penguin42: (4) now run 'debuild -S -si' this will build the new source packages
[15:46] <hggdh> penguin42: then run 'debdiff <current gimp>.dsc <proposed gimp>.dsc'; attach the output to the bug
[15:46] <devildante> penguin42: and then subscribe ubuntu-sponsors
[15:46] <hggdh> penguin42: you CAN do that. It does not mean it will be accepted ;-)
[15:47]  * hggdh did not look at the version for gimp
[15:48] <hggdh> Ccurrent gimp seems to be 2.6.10-1ubuntu3, next will be 2.6.10-1ubuntu4
[15:48] <penguin42> yeh so I built my ppa as ubuntu999dag or the like
[15:49] <hggdh> when you bould in a PPA, it is a good idea to have the package as (curent version+1)~<something>
[15:49] <hggdh> like 2.6.10-1ubuntu4~penguin42
[15:50] <hggdh> the tilde makes the version lower than 2.6.10-1ubuntu4, but higher than 2.6.10-1ubuntu3
[15:50] <hggdh> (topologically speaking)
[15:51] <hggdh> so: your PPA would replace gimp-2.6.10-1ubuntu3, but would *be replaced* by 2.6.10-1ubuntu4
[15:51] <penguin42> you mean ubuntu3~penguin42 ?
[15:51] <hggdh> no, ubuntu4~whatever
[15:52] <hggdh> your new package has to have a higher version than the current one
[15:52] <hggdh> but should be lower than next official version
[15:52] <penguin42> really? from an ascii sort I can see ubuntu3~penguin42 would be before ubuntu4 but I would have thought ubuntu4~ would be after - hohum
[15:52] <hggdh> heh
[15:54] <kklimonda> penguin42: package version is not considered a mere string when comparison is made :)
[15:57] <penguin42> right, one debdiff, just check it actually works before uploading :-)
[15:58] <hggdh> of course... you can build it locally, or upload to the PPA for tests
[15:59] <penguin42> hggdh: Yeh I built locally before PPAing, and I've ppad; but I should just check this ubuntu4 debdiff'd version
[15:59] <penguin42> gimp doesn't take too long to build on my i7
[15:59] <hggdh> you should *always* check a new package
[15:59] <penguin42> indeed
[16:14] <penguin42> hggdh: Look reasonable? https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/636329/+attachment/1669306/+files/gimp_2.6.10-1ubuntu4-debdiff
[16:14] <ubot2> Launchpad bug 636329 in gimp (Ubuntu) (and 1 other project) "Gimp won't print preview (affects: 10) (heat: 56)" [Medium,Confirmed]
[16:14] <devildante> penguin42: yep, you're great :)
[16:15] <penguin42> ok, and that's ubuntu sponsors subscribed
[16:36] <hggdh> looks good. penguin42, what patch system does gimp use?
[16:36] <penguin42> hggdh: Ah well there is a messy answer
[16:36] <hggdh> LOL
[16:36] <hggdh> I am grabbing the source, will check
[16:36] <penguin42> hggdh: It claims to use quilt, if you do what-vcs it says quilt, but there is no series file in debian/patches even though there are 3 patches and it includes a simplepatch system in the rules file
[16:37] <hggdh> hum
[16:37] <penguin42> hggdh: Given there are no quilt patches in there at the moment I thought I'd stick with what it had
[16:37] <hggdh> look at the build log, you should be able to find it there. Also, if it uses quilt, there will be a build-depends on it
[16:38] <hggdh> not quilt... dpkg-source -x did not apply patches
[16:39] <hggdh> indeed, it seems to be symple-patchsys
[16:39] <hggdh> yuck
[16:39] <hggdh> simple even
[16:39] <penguin42> hggdh: Yeh, but look at debian/source/format
[16:40] <hggdh> yeah. I think the packagers were preparing for quilt, but did not get there yet.
[16:41] <hggdh> yes, the DD started it in Jan 2010
[16:50] <hggdh> ooooohhh I see a Dr. David just subscribed to the bugsquad ML ;-)
[16:50]  * penguin42 is confused by https://wiki.ubuntu.com/Bugs/Importance  it lists 'network card' under Medium as a 'problem with a non-essential hardware component' and yet 'laptop built-in wireless' as an essential hardware component on High
[16:50] <penguin42> hggdh: Might have done....
[16:50] <hggdh> well.
[16:51] <hggdh> I can see how this could happen, but I agree it is a bit extreme
[16:51] <hggdh> I would take out the network card from the medium list
[16:52] <penguin42> yeh, I guess one that's literally a card you could pull out and put another one in, but that's beyond most users
[16:53] <yofel> we did discuss it in -kernel once, and iirc the answer was that it's medium as there are more important things that 'High' is used for, and network is 'Medium' so those other things can get a higher importance.
[16:53] <penguin42> yofel: But then the wireless is in high
[16:53] <hggdh> penguin42: reason _might_ also be that most systems nowadays are expected to run wireless
[16:53]  * yofel looks for th elogs
[16:56] <yofel> see here: http://irclogs.ubuntu.com/2010/09/11/%23ubuntu-kernel.html#t15:13
[16:58] <penguin42> ok
[17:05] <Gigacore> hey AbhiJit, welcome
[17:05] <AbhiJit> Gigacore, hi
[17:09] <charlie-tca> I guess those of us with desktop systems are "old-fashioned" again
[17:09] <hggdh> charlie-tca: heh, I am quite used to be called one... I still have a Hercules install with MVS
[17:10] <charlie-tca> but we should not be delegated to "not priority unless wireless is working" status
[17:10] <penguin42> charlie-tca: Yeh I'd agree, I very rarely use wireless
[17:13] <nigelb> well, those who use it don't agree.
[17:13] <nigelb> Ubuntu vs Debian => wireless doesn't work until you go through a lot of hoops in Debian :/
[17:13] <charlie-tca> and the never will, nigelb
[17:13] <penguin42> nigelb: Oh we weren't doubting the importance of wireless, just the low importance of wired
[17:14] <charlie-tca> But why shouldn't all the hardware be important?
[17:14] <hggdh> this is a bit of a controversy -- I have no firm stand there. But, OTOH, most _users_ are wireless users
[17:15] <hggdh> charlie-tca: I venture importance would be tied with volume of use
[17:15] <charlie-tca> yeah
[17:15] <hggdh> (but I myself consider network hardware to be a critical piece no matter if wired or wireless)
[17:16] <nigelb> +1
[17:16] <nigelb> a linux system really can't be used without working internet
[17:16] <nigelb> can't install packages properly, can't update, lots of things not having a network can cause
[17:16] <penguin42> charlie-tca: I've never really felt safe unless I can see where my packets have been going :-)
[17:17] <penguin42> nigelb: Well still, can't get attacked by as much either :-)
[17:17] <nigelb> lol
[17:17] <nigelb> true
[17:19]  * hggdh raises non-tempest-protected hardware as a pretty easy attack route even on wired
[17:20] <penguin42> hggdh: You actually worry about tempest? Against who?
[17:21] <hggdh> penguin42: at home, nowadays, no, I do not worry. If someone is targeting me on RF I would say I had bigger problems ;-)
[17:21] <hggdh> but I have been to places where this was a seriously-considered issue
[17:21] <penguin42> hggdh: Although if someone was to come out with kits for it and automated stuff then I might agree
[17:22] <hggdh> there was at least one such kit published a long time ago, at a small cost
[17:26] <hggdh> weird. I opened a VirtualBox VM, and now I am having problems with the network (DNS resolution fails/gets slower)
[18:10]  * penguin42 hugs hggdh
[18:13] <hggdh> penguin42: you are welcome, sir
[18:20] <penguin42> Is the right way to get people to get all the debug from apport for a package after you cahnge hte pakcage in a bug to ask them to run apport-collect bugnumber ?
[18:24] <charlie-tca> I have asked to have them run aport-collect after changing the package. If you need those logs, that is the easiest way
[18:26] <penguin42> ok
[18:49] <penguin42> so as I understand it kernel bugs don't get duped, but what do you do when you find 4 with similar looking oopses ?
[18:57] <crimsun> you ask a kernel engineer during business hours
[18:57] <crimsun> it isn't that they aren't duped per se, but the Canonical kernel staff prefers to fine-comb them manually
[18:59] <penguin42> yeh sure; this/next week I'm around in business hours, but normally I'm at work :-(
[18:59] <penguin42> crimsun: Oh thanks for doing that wireshark fix
[19:00] <crimsun> penguin42: np
[19:04] <BUGabundo> crimsun: you around ?
[19:05] <crimsun> BUGabundo: no
[19:05] <BUGabundo> ok
[19:05] <BUGabundo> ping me when you can
[19:05] <crimsun> BUGabundo: sure, give me about ten minutes, please
[19:05] <BUGabundo> np
[19:12] <AbhiJit> bye gn
[19:34] <stlsaint> drew212: poke
[19:44] <drew212> stlsaint: poke back
[19:44] <stlsaint> drew212: hey you get my email
[19:44] <drew212> stlsaint: you don't need to actually mark bugs as "triaged" to triage, just asking for additional details, etc is considered 'triaging'
[19:44] <drew212> stlsaint: yes i did =
[19:44] <drew212> =)
[19:45] <drew212> vish: BTW, how do i check my students progress, is there a way to subscribe to all bugs they have activity on?
[19:45] <stlsaint> drew212: well most of the bugs im seeing i really cant reproduce
[19:45] <stlsaint> drew212: my biggest issue ^
[19:46] <drew212> stlsaint: i must appologize also, i've recently started school at a new university, so i have been slacking also
[19:46] <micahg> drew212: with the launchpad-gm-scripts, there's a link to gmane for each person
[19:46] <drew212> micahg: it doesn't list anything for either of my students in gmane
[19:47] <drew212> stlsaint: what bug are you working on that you cant reproduce?
[19:47] <micahg> drew212: so either gmane is behind or they're not active
[19:47] <drew212> micahg: alright, will it show even if their email is hidden in launchpad?
[19:47] <stlsaint> drew212: none at the moment
[19:47] <micahg> drew212: no
[19:48] <drew212> micahg: so i have to ask them to show their email in launchpad if they have it hidden in order to follow their bug triage
[19:48] <micahg> drew212: well, you can monitor their subscribed bugs, we don't want to make a public address a requirement
[19:49] <drew212> stlsaint: well if you cant reproduce the bug try to find out why, if they're running a different distro. If they list it as reproducible and don't contain the specific steps needed to reproduce you can ask them provide the steps...
[19:50] <drew212> micahg: where are their subscribed bugs listed? under participation?
[19:51] <micahg> drew212: bugs.lp.net/~user/, there's a link
[19:51] <micahg> drew212: or coommented on bugs
[19:52] <drew212> stlsaint: if they have a different setup than you(distro, arch, etc) you can try VMing their setup, and if all else fails, you have to ask the user to upload the required information in order to triage the bug. (which happens more often than being able to reproduce the bug)
[19:52] <drew212> micahg: thats what i thought, thanks a bunch
[19:53] <stlsaint> drew212: aye
[20:40] <penguin42> anyone got 32bit Maverick running who can try something?
[20:42] <BUGabundo> no, sorry
[20:42] <BUGabundo> all my systems are 64bits
[20:44] <charlie-tca> ubuntu?
[20:44] <yofel> penguin42: my eeePC is 32
[20:44] <penguin42> yofel: Have you got it on? I just want a disassembly of one of the kernel debug modules
[20:44] <charlie-tca> I have one here
[20:45] <yofel> penguin42: ok, now, it was on, just had to start quassel
[20:46] <penguin42> yofel: OK, can you install linux-image-2.6.35-22-generic-dbgsym ? (Or preferably the pae version - but I'm betting it doesn't make much odds)
[20:47] <yofel> sure, will take a while though
[20:47]  * penguin42 is now convinced bug 640154 bug 632430 and bug 653591 are identical and possibly bug 646215 - and that last one is 32bit
[20:47] <ubot2> Launchpad bug 640154 in linux (Ubuntu) "BUG: unable to handle kernel NULL pointer dereference in ips_adjust in intel_ips on Sony VPC-B11KGX (affects: 2) (heat: 294)" [Undecided,New] https://launchpad.net/bugs/640154
[20:47] <ubot2> Launchpad bug 632430 in linux (Ubuntu) "ips-adjust - BUG: unable to handle kernel NULL pointer dereference at (null) (affects: 3) (heat: 20)" [Undecided,New] https://launchpad.net/bugs/632430
[20:47] <ubot2> Launchpad bug 653591 in linux (Ubuntu) "[18446744058.496026] BUG: unable to handle kernel NULL pointer dereference at (null) ips_adjust in intel_ips (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/653591
[20:47] <ubot2> Launchpad bug 646215 in linux (Ubuntu) "BUG: unable to handle kernel NULL pointer dereference at (null) - ips_adjust in intel_ips (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/646215
[20:48] <charlie-tca> Those are kernel bugs, are they exactly the same hardware?
[20:49] <charlie-tca> Please don't mark kernel bugs duplicates unless the hardware matches
[20:49] <penguin42> charlie-tca: Yeh I'm not going to, but I just wanted to categorise them so I could throw them at a kernel guy tomorrow
[20:53] <penguin42> 2 out of the 3 are VAIO VPCB11KGX, one other is another Vaio and the last is an Aspire. but 3 of the 4 have the same oops address
[20:58] <yofel> ddebs.ubuntu.com hates me, I can ping it fine, but the data transfer speed varies from 0 to ~1000kB/s o.O
[21:03] <penguin42> yofel: Don't worry about it
[21:08] <yofel> penguin42: sorry, this won't get anywhere, the server is dropping the transfer every 3-5%
[21:09] <yofel> penguin42: actually, you could to that that in a  i386 pbuilder chroot too I think if you have one
[21:10] <penguin42> yofel: Yeh could do
[23:54] <penguin42> what's the normal story for drm/graphics bugs - the drm:radeon_cs_ioctl will be coming from the kernel but there is a 33/33/33 chance of kernel/mesa/x server
[23:55]  * penguin42 would be attempted to add an also affects of xserver-xorg-video-ati since the ati guys will pick it up