[00:01] <Licuadora> penguin42: hey, this time it worked
[00:01] <penguin42> hmm that's annoying!
[00:01] <Licuadora> penguin42: but, you wann se the log anyway?
[00:02] <penguin42> nah, I don't think it will be interesting except after a failure
[00:02] <Licuadora> So, you dont know what caused this problem?
[00:02] <Licuadora> it stayed like this for some time
[00:03] <penguin42> sorry no, but if it happens again take a copy of the /var/log/messages after it's failed and .xsession-errors and dmesg (you may need sudo to copy some of them) and what's in those files might help someone figure out why
[00:03] <penguin42> it's difficult without seeing what state its in when it tried
[00:03] <Licuadora> ok, also there i s messages, and messages.1
[00:04] <penguin42> some of it might still be in there - I'm happy to take a look if you put them on a pastebin or the like
[00:06] <Licuadora> http://ubuntu.pastebin.com/Bs8ecGMR
[00:06] <Licuadora> tHATS THE message file
[00:08] <Licuadora> penguin42: see anything strange there?
[00:08] <penguin42> Licuadora: Nothing too odd in there - what's in your CD drive?
[00:08] <Licuadora> Oh, it's a Livecd 10.04, I was gonna reinstall
[00:08] <Licuadora> there is another message file
[00:09] <Licuadora> this one has an extension    .1
[00:09] <penguin42> that'll be an older one; I don't think that will help
[00:09] <penguin42> Licuadora: how about a .xsession-errors.old - when is that form ?
[00:09] <Licuadora> So, did you find anything intresting?
[00:10] <penguin42> no, not in the messages file
[00:10] <Licuadora> .xsession? i do not know where that is
[00:10] <penguin42> in your home directory, it's called .xsession-errors and there should be a .old one
[00:10] <Licuadora> let me check
[00:12] <Licuadora> http://ubuntu.pastebin.com/XRznAMG1
[00:12] <Licuadora> there it is
[00:13] <Licuadora> Some of it is in spanish
[00:13] <penguin42> is that .xsession-errors  or .xsession-errors.old ?
[00:13] <Licuadora> .old
[00:14] <Licuadora> You wanna see .xsessions-errors?
[00:14] <penguin42> no, I think that'll be from after you rebooted
[00:15] <Licuadora> So, what did you find out
[00:15] <penguin42> So that has some odd errors - the ones from gnome-power-manager complaining about 'Either HAL or DBUS are not working' are odd
[00:15] <penguin42> although I guess we don't use HAL now - hmm
[00:16] <penguin42> Licuadora: Did you do an update during the session which refused to shutdown?
[00:16] <Licuadora> I dont even know what that is...
[00:16] <Licuadora> Yeah, i installed a driver
[00:16] <penguin42> which one?
[00:17] <Licuadora> Intel, a ethernet driver
[00:17] <Licuadora> e1000
[00:17] <penguin42> you had to explicitly do that?  It normally just happens
[00:18] <penguin42> part of the normal kernel
[00:18] <penguin42> when you did that did it ask you to reboot then?
[00:18] <Licuadora> well, here is what happened
[00:19] <Licuadora> Ater a power surge failure, my eth0 did not reckongnized my cable, weird thing is, Ubuntu liveCD 8.04 DID rckongnize the cable, but not 10.04
[00:20] <Licuadora> So, i was asking at the forums and stuff, and someone suggested to install some backport files
[00:20] <Licuadora> and then downloading the drivers from intel
[00:20] <Licuadora> And i reboted
[00:20] <Licuadora> rebooted
[00:21] <Licuadora> after that, is when it started failing
[00:22] <penguin42> ok - it's good to have the story; did the reboot immediately after installing the driver work OK?
[00:22] <Licuadora> and still, no cable internet
[00:22] <Licuadora> yes
[00:23] <penguin42> you say you downloaded drivers from Intel - excatly what?
[00:23] <Licuadora> let me check
[00:23] <penguin42> and how did it ask you to install them?
[00:25] <Licuadora> Move the base driver tar file to the directory of your choice.  For
[00:25] <Licuadora>    example, use /home/username/e1000 or /usr/local/src/e1000.
[00:25] <Licuadora>  /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000/e1000.[k]o
[00:26] <Licuadora> there it is, installed
[00:26] <penguin42> ok, if that was broken it could upset stuff - but it's a bit weird; anyway, what we really need is a dmesg and as much as possible in the state where it's just faield to shutdown - I'd probably pull that Intel driver out and put it back to the default one from Ubuntu
[00:27] <Licuadora> And where that might be?
[00:27] <penguin42> good question - it depends what the Intel driver did to it
[00:28] <penguin42> did you say that it was working ok on 10.04 prior to the power problem?
[00:28] <Licuadora> Yeah, it was working, until that day
[00:29] <penguin42> ok, so it was probably a bad idea to install the driver from intel
[00:29] <Licuadora> then, i had to take out my PCI sound card to install a PCI WIFI card, and now, i do not have sound either
[00:30] <Licuadora> the built in sound did not work
[00:30] <Licuadora> it was intel then
[00:31] <Licuadora> Anywho... I dont think is a physical thing, since Ubuntu 8.04 DID detected my cable
[00:31] <penguin42> I think you need to clear stuff out and get back to a normal setup with just the Ubuntu ethernet driver and then someone can try and figure out why that isn't working
[00:31] <Licuadora> re install?
[00:32] <Licuadora> I did reinstall after that day
[00:32] <penguin42> I normally would suggest not to, but probably best
[00:32] <penguin42> you could try seeing if you can get ethernet to work from the install cd
[00:32] <Licuadora> i even tried to install Sabayon, but it didnt detected my cable, not evenubuntu Studio
[00:33] <Licuadora> No, i tried the 10.04 live cd, and no
[00:33] <penguin42> I'd try and debug the ethernet from there
[00:34] <Licuadora> If i upgrade to 10.10, will it fix it?
[00:34] <Licuadora> What about a fresh install?
[00:34] <penguin42> 10.10 is still quite unstable
[00:35] <penguin42> but if 10.04 used to work for you then I think you should try and figure why it stopped
[00:35] <Licuadora> Pff, i am no programer, i dont know any machine languaje
[00:36] <penguin42> are you ircing from the same machine or have you a separate machine?
[00:36] <Licuadora> I just use Blender, but is kindda anoying not having sound
[00:36] <Licuadora> Same machine
[00:36] <Licuadora> i have a WIFI card
[00:36] <Licuadora> And the cable works in my Netbook
[00:37] <penguin42> what is in /sys/class/net ?
[00:37] <Licuadora> let me check
[00:38] <Licuadora> etho lo wlan0 folders
[00:38] <penguin42> ok, and what does ifconfig eth0 say?
[00:39] <Licuadora> eth0      Link encap:Ethernet  direcciónHW 00:1c:c0:6b:03:c9
[00:39] <Licuadora>           ACTIVO DIFUSIÓN MULTICAST  MTU:1500  Métrica:1
[00:39] <Licuadora>           Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:0
[00:39] <Licuadora>           Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:0
[00:39] <Licuadora>           colisiones:0 long.colaTX:1000
[00:39] <Licuadora>           Bytes RX:0 (0.0 B)  TX bytes:0 (0.0 B)
[00:39] <Licuadora>           Memoria:e3100000-e3120000
[00:39] <penguin42> and is the cable currently plugged in?
[00:39] <Licuadora> yes
[00:40] <penguin42> ok, could you get the result of sudo LANG=C ethtool eth0   into a pastebin? (You may need to install ethtool)
[00:42] <Licuadora> http://ubuntu.pastebin.com/4sY5XiMN
[00:42] <penguin42> wow - never seen that before
[00:43] <penguin42> the 'Speed: Unknown!' and 'Duplex: Unknown! (255)' is VERY odd
[00:43] <Licuadora> What do yous'
[00:43] <Licuadora> What do you think that is happenning?
[00:44] <penguin42> http://paste.ubuntu.com/478572/ is mine
[00:45] <Licuadora> twisted pair
[00:45] <penguin42> that could be that new intel river you've put in, you could try it after a reinstall - when you say a power problem, what exactly happened
[00:45] <Licuadora> So...
[00:46] <Licuadora> A lighting bolt striked near my house
[00:47] <penguin42> ah
[00:48] <penguin42> that could have caused permanent damage to the card
[00:48] <Licuadora> but why the 8.04 detected?
[00:49] <penguin42> good question; you could try reinstalling 10.04 and do the ethtool eth0 again and see if it gives sane output
[00:50] <penguin42> but if it did damage something then it is possible its damaged in a way that 8.04 happens not to have problems with; bit odd though
[00:52] <Licuadora> Na, i think i'll just wait for 10.10 for a fresh install
[00:53] <Licuadora> Or... do you think is a possibility for a fix?
[00:53] <penguin42> difficult to know - you have an unusual problem
[00:54] <Licuadora> Well, thanks anyway
[00:55] <Licuadora> Hey...
[00:55] <Licuadora> are you a developer?
[00:56] <penguin42> I only fix things that bug me, not a full time dev
[00:56] <Licuadora> penguin42: maybe you could put some 8.04 ethernet code...oh
[00:57] <Licuadora> well, can you tell the guys from developing, to use some 8.04 code in 10.10?
[00:57] <penguin42> well stuff normally gets better not worse! So if you really can find something that works in 8.04 but not in 10.04 it would need to understand why - but if the only fix is to fix a card damanged by lightening they might not be very sympathetic
[00:58] <Licuadora> hm.. you have logic in you typing....
[00:59] <Licuadora> Then again, it could be useful and be maketed as : LIGHTING BOLT PROOF
[00:59] <penguin42> hehe true
[00:59] <penguin42> I'm not sure what the testing procedure would be
[01:00] <Licuadora> So, there is no way to give my machine an analisys an nd then send it someplacde for checkup?
[01:01] <penguin42> no, I don't think so - but there are things which normally will help; e.g. the dmesg, or output of ethtool help find most problems
[01:01] <Licuadora> well, i already wrote down tds for futere reference
[01:01] <Licuadora> thank you very much
[01:02] <Licuadora> now, i am outta here
[09:02] <kiwinote> hggdh: hi!
[09:02] <kiwinote> hggdh: as you may recall I applied for bug control membership a few months ago
[09:03] <kiwinote> hggdh: there was some discussion about importance settings in an upstream product (ie software-center) vs importance settings in Ubuntu as a whole
[09:05] <kiwinote> hggdh: would you be able to describe how to proceed? do I need to reapply, or are 3 +1's and one -1 sufficiant?
[09:14] <nigelb> kiwinote: what's your LP id?
[09:14] <kiwinote> nigelb: it's kiwinote
[09:15] <nigelb> kiwinote: oh, you got the expiring mail?
[09:15] <nigelb> wait, didn't you get approved by Brian that time?
[09:15] <nigelb> I thought you did.
[09:16] <kiwinote> nigelb: no, I applied, but there was some discussion about whether my application was good enough to join yet
[09:16] <nigelb> kiwinote: talk to pedro when he comes on.
[09:16] <kiwinote> nigelb: ok, thanks
[09:16] <vish> kiwinote: one problem while applying is that others dont know who you are..
[09:17] <vish> kiwinote: so its always better have mentioned that you have done loads of SC work
[09:17] <vish> initially itself
[09:17] <kiwinote> vish: yeah, although when I applied was before I started coding on s-c
[09:17] <kiwinote> vish: at that stage I had only done bug triage
[09:19] <vish> kiwinote: yeah that too could have been mentioned initially , you should have had mvo replying immediately than later..
[09:19] <nigelb> yeah, ack's should come immediately.
[09:19] <kiwinote> vish: tremolux (a s-c developer) replied positively straight away, but there was discussion about how I choose the importance levels
[09:20] <kiwinote> I knew to much about s-c to follow the importance guidelines all the time ;)
[09:20] <kiwinote> too
[09:21] <kiwinote> 24/25 march is the date of the application if anyone wants to look back
[09:21] <vish> kiwinote: oh had tremolux replied too? but mvo is more illustrious i guess ;p
[09:21] <kiwinote> hehe
[12:27] <Laibsch> requesting confirmation for bug 618620 from people who run postgrey
[12:27] <ubot2> Launchpad bug 618620 in postgrey (Ubuntu) "warning in syslog about /var/run/postgrey.pid (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/618620
[14:02] <hggdh> kiwinote: there?
[14:02] <kiwinote> hggdh: hi
[14:02] <hggdh> morning/evening kiwinote ;-)
[14:03] <hggdh> kiwinote: I am looking at your application now
[14:03] <kiwinote> hggdh: ok, thanks
[14:03] <hggdh> (meaning *will*
[14:03] <hggdh> now
[14:03] <hggdh> dammit
[14:03] <hggdh> too early
[14:03] <kiwinote> hggdh: aha, don't worry, take your time
[14:06] <hggdh> kiwinote: yes, you more than qualify. Give me a few
[14:07] <kiwinote> hggdh: ok, thanks a lot
[14:13] <hggdh> kiwinote: welcome in!
[14:13] <hggdh> :-)
[14:14] <kiwinote> hggdh: great, thanks!
[14:31] <njin> pedro_: Hello
[14:34] <njin> pedro_: I'm going outside, repair a friend's pc and have a good cup of coffe, and if possible install uby. See you late
[14:35] <pedro_> njin, hey! ok see you later ;-)
[15:31] <hallyn> general bug question - when i have a bug that's reported as affecting 3-5 projects, is it normal to change the priority/status for each project?  Or just one, bc that's enough info?
[15:32] <hallyn> and also, is marking it invalid against a particular project considered ok (if it has nothing to do with that package)?
[15:41] <hggdh> hallyn: (1) yes -- each project/task may have its own importance; (2) samewise, each project/task may be marked INVALID as needed (or any other applicable status)
[15:45] <hallyn> hggdh: i guess what i'm asking out of laziness is the inverse - is it ok to only mark status/importance in a single one of the lines?
[15:46] <hallyn> hggdh: but thanks, that's very helpful.  i'll now feel free ot mark invalid :)
[15:49] <hggdh> hallyn: heh. Ideally, each would be marked... sorry for the extra work ;-)
[15:54] <hallyn> hggdh: will do that then, thanks :)
[16:13] <njin> pedro_: i'm back
[17:22] <nigelbabu> pedro_: poke?
[17:22] <pedro_> nigelbabu, hello
[17:22] <pedro_> changed your nickname? ;-)
[17:22] <nigelbabu> pedro_: No, xubuntu won't let me in.  Trying to fix that.  On a live cd now.
[17:23] <nigelbabu> pedro_: can you blog about the patch day and how awesome it was? I was supposed to, but my system is not being very friendly today.
[17:23] <micahg> pedro_: I'm still on the list so all seems good :)
[17:23] <pedro_> micahg, \o/! great so lp is not *that* broken ;-)
[17:23] <pedro_> nigelbabu, will do it trough the qa blog
[17:24] <nigelbabu> pedro_: \o/
[17:24] <nigelbabu> Thank you :)
[17:24] <pedro_> nigelbabu, you're welcome , good luck fixing your system :-)
[17:24] <nigelbabu> pedro_: Might reinstall.  Looks like.
[17:24] <pedro_> eek...
[17:25] <nigelbabu> ugh, a lof of hacking I did for a project is on the hard disk :(
[17:29] <devildante> nigelbabu: too much hacking kills hacking, I guess :P
[17:29] <nigelbabu> devildante: looks like
[17:29] <devildante> anyway, the patch/bug day was really awesome! thanks guys :)
[17:30] <nigelbabu> devildante: No.  Thank YOU for participating
[17:30] <devildante> Thank YOU for thanking ME for participating :p
[17:33] <nigelbabu> devildante: how did the process feel though
[17:33] <nigelbabu> ?
[17:33] <nigelbabu> was it complicated?
[17:34] <devildante> nigelbabu: not at all :)
[17:34] <nigelbabu> devildante: just about getting a hang of it?
[17:35] <devildante> nigelbabu: it's easy, all we need is volunteers ;)
[19:18] <simar> ashams: There??
[19:21] <penguin42> pedro_: hi
[19:21] <pedro_> penguin42, hello
[19:21] <pedro_> vish, around?
[19:22] <penguin42> pedro_: You commented on my bug 617912 that the retrace failed and marked as incomplete, however there is a lot of other debug  attached to the bug which may be of use - was this an automatic marking as incomplete or not?
[19:22] <ubot2> Launchpad bug 617912 in gtk+2.0 (Ubuntu) "gnome-terminal crashed with SIGSEGV in g_object_set() (affects: 1) (heat: 8)" [Medium,Incomplete] https://launchpad.net/bugs/617912
[19:24] <pedro_> penguin42, no it was not, I've read the stacktrace before
[19:24] <pedro_> penguin42, if you look at it you'll see that it's missing a lot of symbols that might be important for the developers to determine where's the crash
[19:25] <vish> pedro_: hi!
[19:25] <sinurge> mm alpha3 - rhythmbox[1847]: segfault at 30 ip 049ebf35 sp bfca2300 error 4 in libindicate.so.4.0.3[49e7000+d000] am not sure how to read this
[19:25] <pedro_> penguin42, look at Stacktrace.txt and ThreadStacktrace.txt
[19:25] <pedro_> sinurge, enable apport and report the bug :-)
[19:25] <pedro_> penguin42, sudo service apport start force_start=1 ; reproduce the crash and report the bug
[19:25] <penguin42> pedro_: ok, I'm not quite sure I can retrigger the seg - but it's still giving out loads of menu related debug which I suspect are related
[19:26] <sinurge> just did that :)
[19:26] <pedro_> penguin42, they maybe are, just having a good stacktrace we could determine that :-)
[19:27] <sinurge> just wanted to know if anyone can help read anything that is apparant in that line
[19:28] <pedro_> vish, awesome, you got email ;-)
[19:29] <penguin42> pedro_: OK, I'll see if I can retrigger it - if not, I've still got it spewing tones of menu related debug, do you want that as a separate bug - I'm farily sure they're actually the same underlying problem
[19:29] <pedro_> sinurge, that's no use, it only indicates that there was a crash related to that library
[19:29] <pedro_> penguin42, yes, one issue per bug please
[19:29] <vish> oh!
[19:30] <penguin42> pedro_: OK will do, although to be honest I really do think it's the same issue
[19:38] <vish> pedro_: you got mail , too! :p
[19:40] <pedro_> vish, \o/!
[19:41] <vish> :)
[19:43] <penguin42> pedro_: Right, have backtrace - I'll get it onto the bug in a few seconds
[19:44] <devildante> I didn't get mail :(
[19:44] <devildante> :p
[19:49] <penguin42> pedro_: Can you let me know if that's enough
[19:51] <pedro_> penguin42, looks ok, could you execute 'thread apply all bt full' in gdb and attach that resulting output to the report?
[19:51] <pedro_> penguin42, please attach it because it's going to be a bit long
[19:51] <pedro_> penguin42, thanks for the stacktrace ;-)
[19:52] <penguin42> pedro_: OK, will do - do you know if there is anyway of getting the gnome warnings to give more debug - I'm fairly sure they're the underlying reason
[19:52] <Laibsch1> requesting confirmation for bug 618620 from people who run postgrey
[19:52] <ubot2> Launchpad bug 618620 in postgrey (Ubuntu) "warning in syslog about /var/run/postgrey.pid (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/618620
[19:52] <penguin42> pedro_: I suspect the code in the 043 patch in gtk+2.0 isn't doing enough checking but I don't understand enough how it's supposed to work
[19:57] <njin> pedro_: hello
[20:31] <penguin42> bah, doesn't want to trigger again at the moment
[20:47] <penguin42> pedro_: OK, one thread apply all bt full
[20:50] <pedro_> penguin42, thank you
[20:50] <penguin42> pedro_: It's a bit hit and miss whether it segs - I guess it just depends what crud it dereferences