/srv/irclogs.ubuntu.com/2010/08/16/#ubuntu-bugs.txt

Licuadorapenguin42: hey, this time it worked00:01
penguin42hmm that's annoying!00:01
Licuadorapenguin42: but, you wann se the log anyway?00:01
penguin42nah, I don't think it will be interesting except after a failure00:02
LicuadoraSo, you dont know what caused this problem?00:02
Licuadorait stayed like this for some time00:02
penguin42sorry 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 why00:03
penguin42it's difficult without seeing what state its in when it tried00:03
Licuadoraok, also there i s messages, and messages.100:03
penguin42some of it might still be in there - I'm happy to take a look if you put them on a pastebin or the like00:04
Licuadorahttp://ubuntu.pastebin.com/Bs8ecGMR00:06
LicuadoratHATS THE message file00:06
Licuadorapenguin42: see anything strange there?00:08
penguin42Licuadora: Nothing too odd in there - what's in your CD drive?00:08
LicuadoraOh, it's a Livecd 10.04, I was gonna reinstall00:08
Licuadorathere is another message file00:08
Licuadorathis one has an extension    .100:09
penguin42that'll be an older one; I don't think that will help00:09
penguin42Licuadora: how about a .xsession-errors.old - when is that form ?00:09
LicuadoraSo, did you find anything intresting?00:09
penguin42no, not in the messages file00:10
Licuadora.xsession? i do not know where that is00:10
penguin42in your home directory, it's called .xsession-errors and there should be a .old one00:10
Licuadoralet me check00:10
Licuadorahttp://ubuntu.pastebin.com/XRznAMG100:12
Licuadorathere it is00:12
LicuadoraSome of it is in spanish00:13
penguin42is that .xsession-errors  or .xsession-errors.old ?00:13
Licuadora.old00:13
LicuadoraYou wanna see .xsessions-errors?00:14
penguin42no, I think that'll be from after you rebooted00:14
LicuadoraSo, what did you find out00:15
penguin42So that has some odd errors - the ones from gnome-power-manager complaining about 'Either HAL or DBUS are not working' are odd00:15
penguin42although I guess we don't use HAL now - hmm00:15
penguin42Licuadora: Did you do an update during the session which refused to shutdown?00:16
LicuadoraI dont even know what that is...00:16
LicuadoraYeah, i installed a driver00:16
penguin42which one?00:16
LicuadoraIntel, a ethernet driver00:17
Licuadorae100000:17
penguin42you had to explicitly do that?  It normally just happens00:17
penguin42part of the normal kernel00:18
penguin42when you did that did it ask you to reboot then?00:18
Licuadorawell, here is what happened00:18
LicuadoraAter 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.0400:19
LicuadoraSo, i was asking at the forums and stuff, and someone suggested to install some backport files00:20
Licuadoraand then downloading the drivers from intel00:20
LicuadoraAnd i reboted00:20
Licuadorarebooted00:20
Licuadoraafter that, is when it started failing00:21
penguin42ok - it's good to have the story; did the reboot immediately after installing the driver work OK?00:22
Licuadoraand still, no cable internet00:22
Licuadorayes00:22
penguin42you say you downloaded drivers from Intel - excatly what?00:23
Licuadoralet me check00:23
penguin42and how did it ask you to install them?00:23
LicuadoraMove the base driver tar file to the directory of your choice.  For00: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]o00:25
Licuadorathere it is, installed00:26
penguin42ok, 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 Ubuntu00:26
LicuadoraAnd where that might be?00:27
penguin42good question - it depends what the Intel driver did to it00:27
penguin42did you say that it was working ok on 10.04 prior to the power problem?00:28
LicuadoraYeah, it was working, until that day00:28
penguin42ok, so it was probably a bad idea to install the driver from intel00:29
Licuadorathen, i had to take out my PCI sound card to install a PCI WIFI card, and now, i do not have sound either00:29
Licuadorathe built in sound did not work00:30
Licuadorait was intel then00:30
LicuadoraAnywho... I dont think is a physical thing, since Ubuntu 8.04 DID detected my cable00:31
penguin42I 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 working00:31
Licuadorare install?00:31
LicuadoraI did reinstall after that day00:32
penguin42I normally would suggest not to, but probably best00:32
penguin42you could try seeing if you can get ethernet to work from the install cd00:32
Licuadorai even tried to install Sabayon, but it didnt detected my cable, not evenubuntu Studio00:32
LicuadoraNo, i tried the 10.04 live cd, and no00:33
penguin42I'd try and debug the ethernet from there00:33
LicuadoraIf i upgrade to 10.10, will it fix it?00:34
LicuadoraWhat about a fresh install?00:34
penguin4210.10 is still quite unstable00:34
penguin42but if 10.04 used to work for you then I think you should try and figure why it stopped00:35
LicuadoraPff, i am no programer, i dont know any machine languaje00:35
penguin42are you ircing from the same machine or have you a separate machine?00:36
LicuadoraI just use Blender, but is kindda anoying not having sound00:36
LicuadoraSame machine00:36
Licuadorai have a WIFI card00:36
LicuadoraAnd the cable works in my Netbook00:36
penguin42what is in /sys/class/net ?00:37
Licuadoralet me check00:37
Licuadoraetho lo wlan0 folders00:38
penguin42ok, and what does ifconfig eth0 say?00:38
Licuadoraeth0      Link encap:Ethernet  direcciónHW 00:1c:c0:6b:03:c900:39
Licuadora          ACTIVO DIFUSIÓN MULTICAST  MTU:1500  Métrica:100:39
Licuadora          Paquetes RX:0 errores:0 perdidos:0 overruns:0 frame:000:39
Licuadora          Paquetes TX:0 errores:0 perdidos:0 overruns:0 carrier:000:39
Licuadora          colisiones:0 long.colaTX:100000:39
Licuadora          Bytes RX:0 (0.0 B)  TX bytes:0 (0.0 B)00:39
Licuadora          Memoria:e3100000-e312000000:39
penguin42and is the cable currently plugged in?00:39
Licuadorayes00:39
penguin42ok, could you get the result of sudo LANG=C ethtool eth0   into a pastebin? (You may need to install ethtool)00:40
Licuadorahttp://ubuntu.pastebin.com/4sY5XiMN00:42
penguin42wow - never seen that before00:42
penguin42the 'Speed: Unknown!' and 'Duplex: Unknown! (255)' is VERY odd00:43
LicuadoraWhat do yous'00:43
LicuadoraWhat do you think that is happenning?00:43
penguin42http://paste.ubuntu.com/478572/ is mine00:44
Licuadoratwisted pair00:45
penguin42that 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 happened00:45
LicuadoraSo...00:45
LicuadoraA lighting bolt striked near my house00:46
penguin42ah00:47
penguin42that could have caused permanent damage to the card00:48
Licuadorabut why the 8.04 detected?00:48
penguin42good question; you could try reinstalling 10.04 and do the ethtool eth0 again and see if it gives sane output00:49
penguin42but 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 though00:50
LicuadoraNa, i think i'll just wait for 10.10 for a fresh install00:52
LicuadoraOr... do you think is a possibility for a fix?00:53
penguin42difficult to know - you have an unusual problem00:53
LicuadoraWell, thanks anyway00:54
LicuadoraHey...00:55
Licuadoraare you a developer?00:55
penguin42I only fix things that bug me, not a full time dev00:56
Licuadorapenguin42: maybe you could put some 8.04 ethernet code...oh00:56
Licuadorawell, can you tell the guys from developing, to use some 8.04 code in 10.10?00:57
penguin42well 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 sympathetic00:57
Licuadorahm.. you have logic in you typing....00:58
LicuadoraThen again, it could be useful and be maketed as : LIGHTING BOLT PROOF00:59
penguin42hehe true00:59
penguin42I'm not sure what the testing procedure would be00:59
LicuadoraSo, there is no way to give my machine an analisys an nd then send it someplacde for checkup?01:00
penguin42no, I don't think so - but there are things which normally will help; e.g. the dmesg, or output of ethtool help find most problems01:01
Licuadorawell, i already wrote down tds for futere reference01:01
Licuadorathank you very much01:01
Licuadoranow, i am outta here01:02
=== jjesse_ is now known as jjesse
=== nUboon2Ag is now known as nUboon2Age
=== easter_egg is now known as Ayrton
=== davmor2_ is now known as davmor2
kiwinotehggdh: hi!09:02
kiwinotehggdh: as you may recall I applied for bug control membership a few months ago09:02
kiwinotehggdh: there was some discussion about importance settings in an upstream product (ie software-center) vs importance settings in Ubuntu as a whole09:03
kiwinotehggdh: would you be able to describe how to proceed? do I need to reapply, or are 3 +1's and one -1 sufficiant?09:05
nigelbkiwinote: what's your LP id?09:14
kiwinotenigelb: it's kiwinote09:14
nigelbkiwinote: oh, you got the expiring mail?09:15
nigelbwait, didn't you get approved by Brian that time?09:15
nigelbI thought you did.09:15
kiwinotenigelb: no, I applied, but there was some discussion about whether my application was good enough to join yet09:16
nigelbkiwinote: talk to pedro when he comes on.09:16
kiwinotenigelb: ok, thanks09:16
vishkiwinote: one problem while applying is that others dont know who you are..09:16
vishkiwinote: so its always better have mentioned that you have done loads of SC work09:17
vishinitially itself09:17
kiwinotevish: yeah, although when I applied was before I started coding on s-c09:17
kiwinotevish: at that stage I had only done bug triage09:17
vishkiwinote: yeah that too could have been mentioned initially , you should have had mvo replying immediately than later..09:19
nigelbyeah, ack's should come immediately.09:19
kiwinotevish: tremolux (a s-c developer) replied positively straight away, but there was discussion about how I choose the importance levels09:19
kiwinoteI knew to much about s-c to follow the importance guidelines all the time ;)09:20
kiwinotetoo09:20
kiwinote24/25 march is the date of the application if anyone wants to look back09:21
vishkiwinote: oh had tremolux replied too? but mvo is more illustrious i guess ;p09:21
kiwinotehehe09:21
=== yofel_ is now known as yofel
Laibschrequesting confirmation for bug 618620 from people who run postgrey12:27
ubot2Launchpad bug 618620 in postgrey (Ubuntu) "warning in syslog about /var/run/postgrey.pid (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/61862012:27
=== easter_egg is now known as easter_egg|off
hggdhkiwinote: there?14:02
kiwinotehggdh: hi14:02
hggdhmorning/evening kiwinote ;-)14:02
hggdhkiwinote: I am looking at your application now14:03
kiwinotehggdh: ok, thanks14:03
hggdh(meaning *will*14:03
hggdhnow14:03
hggdhdammit14:03
hggdhtoo early14:03
kiwinotehggdh: aha, don't worry, take your time14:03
hggdhkiwinote: yes, you more than qualify. Give me a few14:06
kiwinotehggdh: ok, thanks a lot14:07
hggdhkiwinote: welcome in!14:13
hggdh:-)14:13
kiwinotehggdh: great, thanks!14:14
njinpedro_: Hello14:31
njinpedro_: I'm going outside, repair a friend's pc and have a good cup of coffe, and if possible install uby. See you late14:34
pedro_njin, hey! ok see you later ;-)14:35
hallyngeneral 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:31
hallynand also, is marking it invalid against a particular project considered ok (if it has nothing to do with that package)?15:32
hggdhhallyn: (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:41
hallynhggdh: 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:45
hallynhggdh: but thanks, that's very helpful.  i'll now feel free ot mark invalid :)15:46
hggdhhallyn: heh. Ideally, each would be marked... sorry for the extra work ;-)15:49
hallynhggdh: will do that then, thanks :)15:54
=== easter_egg|off is now known as easter_egg
njinpedro_: i'm back16:13
=== seb128_ is now known as seb128
nigelbabupedro_: poke?17:22
pedro_nigelbabu, hello17:22
pedro_changed your nickname? ;-)17:22
nigelbabupedro_: No, xubuntu won't let me in.  Trying to fix that.  On a live cd now.17:22
nigelbabupedro_: 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
micahgpedro_: 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 blog17:23
nigelbabupedro_: \o/17:24
nigelbabuThank you :)17:24
pedro_nigelbabu, you're welcome , good luck fixing your system :-)17:24
nigelbabupedro_: Might reinstall.  Looks like.17:24
pedro_eek...17:24
nigelbabuugh, a lof of hacking I did for a project is on the hard disk :(17:25
devildantenigelbabu: too much hacking kills hacking, I guess :P17:29
nigelbabudevildante: looks like17:29
devildanteanyway, the patch/bug day was really awesome! thanks guys :)17:29
nigelbabudevildante: No.  Thank YOU for participating17:30
devildanteThank YOU for thanking ME for participating :p17:30
nigelbabudevildante: how did the process feel though17:33
nigelbabu?17:33
nigelbabuwas it complicated?17:33
devildantenigelbabu: not at all :)17:34
nigelbabudevildante: just about getting a hang of it?17:34
devildantenigelbabu: it's easy, all we need is volunteers ;)17:35
simarashams: There??19:18
penguin42pedro_: hi19:21
pedro_penguin42, hello19:21
pedro_vish, around?19:21
penguin42pedro_: 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
ubot2Launchpad 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/61791219:22
pedro_penguin42, no it was not, I've read the stacktrace before19: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 crash19:24
vishpedro_: hi!19:25
sinurgemm 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 this19:25
pedro_penguin42, look at Stacktrace.txt and ThreadStacktrace.txt19: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 bug19:25
penguin42pedro_: 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 related19:25
sinurgejust did that :)19:26
pedro_penguin42, they maybe are, just having a good stacktrace we could determine that :-)19:26
sinurgejust wanted to know if anyone can help read anything that is apparant in that line19:27
pedro_vish, awesome, you got email ;-)19:28
penguin42pedro_: 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 problem19:29
pedro_sinurge, that's no use, it only indicates that there was a crash related to that library19:29
pedro_penguin42, yes, one issue per bug please19:29
vishoh!19:29
penguin42pedro_: OK will do, although to be honest I really do think it's the same issue19:30
vishpedro_: you got mail , too! :p19:38
pedro_vish, \o/!19:40
vish:)19:41
penguin42pedro_: Right, have backtrace - I'll get it onto the bug in a few seconds19:43
devildanteI didn't get mail :(19:44
devildante:p19:44
penguin42pedro_: Can you let me know if that's enough19:49
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 long19:51
pedro_penguin42, thanks for the stacktrace ;-)19:51
penguin42pedro_: 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 reason19:52
Laibsch1requesting confirmation for bug 618620 from people who run postgrey19:52
ubot2Launchpad bug 618620 in postgrey (Ubuntu) "warning in syslog about /var/run/postgrey.pid (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/61862019:52
=== Laibsch1 is now known as Laibsch
penguin42pedro_: 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 work19:52
njinpedro_: hello19:57
penguin42bah, doesn't want to trigger again at the moment20:31
penguin42pedro_: OK, one thread apply all bt full20:47
pedro_penguin42, thank you20:50
penguin42pedro_: It's a bit hit and miss whether it segs - I guess it just depends what crud it dereferences20:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!