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

=== JMS is now known as JoeMaverickSett
LicuadoraA strange thing is happening to me... or to my PC02:53
LicuadoraAfter a power surge failure, I cannot acces the interne via cable, the weird part is, it worked with a Ubuntu Live cd 8.04, but not with 10.0402:54
Licuadoray is a driver issue02:54
LicuadoraSome say02:55
LicuadoraWell, how do i upgrade all my drivers?02:55
LicuadoraI reinstalled the kernel, but still, does not detect the cable02:55
virtualdlicuadora: try running ifdown eth0;ifup eth0 as root02:56
Licuadoravituald: root@djiin:~# ifdown eth0;ifup eth002:58
Licuadoraifdown: interface eth0 not configured02:58
LicuadoraIgnoring unknown interface eth0=eth0.02:58
virtualdso did it work?02:59
Licuadoravirtuald: Whats your diagnosis?02:59
virtualdi'm not a doctor :p02:59
LicuadoraWell, it output that, a few lines up03:00
Licuadoraeth0 not configured03:00
virtualdok, then i have no idea03:00
Licuadorahm...03:00
LicuadoraWhat was tha command suposed to do?03:01
virtualdto bring down and then up your first ethernet interface03:01
virtualdit works sometimes03:01
LicuadoraDo you know how to configure it?03:02
virtualdyes in /etc/network/interfaces03:02
LicuadoraWhat do i do there?03:02
Licuadoraauto lo03:03
Licuadoraiface lo inet loopback03:03
LicuadoraThats whats in there03:03
virtualdok03:03
virtualdtry adding03:03
virtualdauto eth003:03
virtualdinet eth0 inet dhcp03:03
virtualdthen run ifup eth0 again03:03
virtualdoops03:04
virtualdiface eth0 inet dhcp03:04
virtualdso don't put inet .. inet there03:04
LicuadoraAll in one line, or as it is?03:05
LicuadoraI am about to save it03:06
virtualdtwo lines03:06
virtualdauto eth003:06
Licuadoragot it03:06
virtualdiface eth0 inet dhcp03:06
virtualdsave and run ifup eth003:06
virtualdi have food on the stove03:06
virtualdafk03:07
Licuadoraroot@djiin:~# ifup eth0 ifdown eth003:07
LicuadoraInternet Systems Consortium DHCP Client V3.1.303:07
LicuadoraCopyright 2004-2009 Internet Systems Consortium.03:07
LicuadoraAll rights reserved.03:07
LicuadoraFor info, please visit https://www.isc.org/software/dhcp/03:07
LicuadoraListening on LPF/eth0/00:1c:c0:6b:03:c903:07
LicuadoraSending on   LPF/eth0/00:1c:c0:6b:03:c903:07
LicuadoraSending on   Socket/fallback03:07
LicuadoraDHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 403:07
LicuadoraDHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1003:07
LicuadoraI hope that means is working03:08
LicuadoraNA, it didnt worked... *sigh*03:11
Licuadorahttp://ubuntu.pastebin.com/9004uBXJ03:15
njinhello guys, i've got a question09:00
micahg!ask | njin09:02
ubot2njin: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)09:02
njinsorry, i've read not well the bug :-(09:03
micahgnjin: do you need help with something?  I'm about to go to sleep09:13
njinmicahg:no, thanks and good sleep09:13
=== yofel_ is now known as yofel
njinyofel: hello10:27
njinhttps://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/408686 is a bug in the window manager ?10:32
ubot2Ubuntu bug 408686 in xserver-xorg-input-keyboard (Ubuntu) "Cannot move task bar (panel) after changing "movement key" in Window Preferences (affects: 1) (heat: 8)" [Undecided,Incomplete]10:32
zaytsevHey folks13:01
penguin42hi13:01
zaytsevIs there any reason why one wouldn't be able to mark a launchpad bug as wontfix?13:01
zaytsevThe option just seems to be grayed out13:02
gorillazaytsev: Yes, it generally not the right option to select. Which bug are we talking about here?13:03
zaytsevgorilla, I am triaging bugs for Midnight Commander13:03
zaytsevI will look up an exact bug numbers13:03
gorillaWontfix is can only be set by Bug Squad leaders.13:04
zaytsevgorilla, ah, it explains it all13:04
zaytsevgorilla, the fact that I am the maintainer of the package doesn't matter?13:04
gorillazaytsev: Hmmm. I'm not sure in that case.13:05
zaytsevThis is one such example13:05
zaytsevhttps://bugs.launchpad.net/ubuntu/+source/mc/+bug/30132813:05
ubot2Ubuntu bug 301328 in mc (Ubuntu) "midnight commander aggregate patch (heat: 8)" [Undecided,Invalid]13:05
zaytsevFor me the option is just greyed out13:05
zaytsevThis is another one13:05
zaytsevhttps://bugs.launchpad.net/ubuntu/+source/mc/+bug/38083013:05
ubot2Ubuntu bug 380830 in mc (Ubuntu) "mc from hardy crashes when tryied to open bad *.cpio (heat: 2)" [Undecided,Invalid]13:05
zaytsevI didn't want to close them as invalid because it does not really fit into the context13:05
* penguin42 kicks lp to get a move on13:05
zaytsevThe patch for instance is for most parts upstreamed and reporter doesn't want or is unable to help to determine what is left and upstream it. So this sounds like a wontfix in most other BTSs13:06
gorillazaytsev: fair enough.13:06
zaytsevThe other one is indeed fixed in Interpid but not Hardy, but the package in not going to be backported, so in reality the bug is valid and was fixed in a newer Ubuntu, but it's a wontfix for Hardy13:08
njinhello, we support gOS ?13:17
njinit uses ubiquity, then i suppose that is a derivate13:20
njinthen is a Package not provided by Ubuntu13:22
njincan someone help with this https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/408686 , with super+leftclick windows can be grabbed, but the panel no.13:26
ubot2Ubuntu bug 408686 in xserver-xorg-input-keyboard (Ubuntu) "Cannot move task bar (panel) after changing "movement key" in Window Preferences (affects: 1) (heat: 8)" [Undecided,Incomplete]13:26
penguin42njin: I'd ask Bryce since he was the last to change it back to incomplete13:27
njinpenguin42: thanks, i don't change the status because i'm not sure on assigning to xserver o metacity13:30
penguin42or possibly the panel13:31
njinyes13:31
njinbut with alt+mouse it work13:31
njinwhy don't work with super+mouse ?13:32
penguin42<breakfast>13:34
njinstrange13:34
njinpenguin42 have a good breakfast13:35
yofelis compiz being used? that has it's own settings for that too I think (didn't read the bug13:35
yofel)13:35
njinyofel: in compiz and metacity13:35
yofelhm, then I don't know, it's been a while since I used compiz or metacity, and I always used alt13:36
penguin42<burp>14:11
* penguin42 doesn't have a super button on this keyboard14:14
devildantehi all :)14:18
njinpenguin42: have you got a hole instead ?  ;-)14:25
penguin42njin: Pretty much - this keyboard was made before those keys were added14:26
njinah good keyboard then14:28
penguin42Model M14:28
njinmanufacturer?14:29
penguin42IBM Model M - google it, it's a well known model14:30
njinpenguin42: normally a cdlive work or not with touchscreen ?14:31
penguin42dunno, not tried a touchscreen14:31
njini too14:31
penguin42they're getting common, so if it doesn't it should14:32
penguin42anyone using compiz+gnome that can try and reproduce a bug?14:49
BUGabundoI'm on mavericj14:50
penguin42so am I14:50
penguin42but I don't think the guy who reported this is14:50
penguin42bug 61774014:50
ubot2Launchpad bug 617740 in ubuntu "If something changes on a Gnome panel (e.g. window closes or opens), the panel raises above screensaver (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/61774014:50
penguin42it's potentially quite nasty; but it doesn't happen for me (Maverick+metacity)14:51
penguin42hmm actually he's using rss-glx not the standard gnome-screensaver14:52
penguin42oh and the screensaver he uses actually kills me xserver - Radeon bug I guess14:53
devildantepenguin42: can't reproduce the bug with compiz (at least with the "Take a screenshot" thingie)15:04
penguin42devildante: How about something like sleep 10; xterm    and then screen lock ?15:06
devildantepenguin42: wait, I didn't have a window list, but docky15:06
devildantepenguin42: retrying with window list15:07
devildantepenguin42: didn't work15:11
devildantepenguin42: no matter what I do, I can't reproduce this bug15:11
penguin42well, that's good in a way - if it affected everyone it would be pretty serious - but there again I assume he's not just making it up - hmm I wonder how to help15:12
devildantepenguin42: maybe it's because of rss-glx15:12
devildante?15:12
penguin42I've tried installing rss-glx; it just adds some extra creensavers15:13
devildantepenguin42: so rss-glx doesn't replace gnome-screensaver?15:14
penguin42doesn't seem to, it just seems to add new hacks15:14
devildantepenguin42: even with a screensaver (i.e not just a black screen), it doesn't work15:19
penguin42I've flipped the package to gnome-screensaver - I reckon it's the one that's supposed to make sure everything stays out of the way15:31
devildantepenguin42: is he running lucid or maverick?15:35
penguin42hmm I'd say Maverick actually based on the gnome-screensaver version15:36
devildantepenguin42: running Maverick too. maybe we should ask him for a video recording? (I don't know if recordmydesktop would work when locking)15:38
penguin42devildante: Maybe, but 1) I think it's pretty clear what he's saying happens and 2) as you say I doubt the recorders would work with lock15:39
devildantepenguin42: just tested, it seems recordmydesktop works when locking, even showing the screensaver you set! sweet :p15:45
devildantepenguin42: if he records his problem, maybe we'll see something that can guide us15:45
penguin42oh cute, feel free to add that to the bug15:46
devildantepenguin42: done :) but why is it cute? :P15:49
penguin42I really hadn't expected recordmydesktop to survive the screenlock15:49
devildantepenguin42: it even shows the screensaver you put, so it is super-sweet!15:50
njinhelp https://bugs.launchpad.net/ubuntu/+bug/408914 I presume that the bug is valid, in fact in fdisk under the Boot of the 250GB (sdc) we see * 1 and under the first of 1 TB (sda)we can see * 2 or i'm wrong ?16:13
ubot2Ubuntu bug 408914 in ubuntu "SATA drives identified in wrong order (affects: 1) (heat: 8)" [Undecided,Incomplete]16:13
devildantenjin: I *think* you can't rely on order for hard drives if you don't use UUIDs. but I'm not sure about that, so ask someone else :)16:31
njindevildante: thanks, today is a day of orrrrrrible bugs.16:33
penguin42drive order is undefined16:36
njinpenguin42: then what you mentor ?16:37
penguin42?16:37
njinpenguin42: i don't know what to do with this bug16:38
penguin42njin: If you don't know what to do with a bug it's fine to leave it alone16:38
njinpenguin42: ok, thanks16:39
penguin42njin: I think the right thing to do with it would be to assign it as a dupe of 56964516:42
njinpenguin42: looking16:42
penguin42I put a comment on that a while ago16:43
devildantetyping bug 569645 here because I'm too lazy :p16:43
ubot2Launchpad bug 569645 in ubuntu "10.04RC system boot random assignment of sda, sdb (affects: 3) (heat: 41)" [Undecided,New] https://launchpad.net/bugs/56964516:43
penguin42the bug is similar to the bug I originally reported as bug 26117816:43
ubot2Launchpad bug 261178 in linux (Ubuntu) "[intrepid] Random order of disk detection (heat: 5)" [Medium,Expired] https://launchpad.net/bugs/26117816:43
penguin42but I think the idea is that initialisation is now done in parallel, and if you have multiple controllers you get pretty random definitions of the /dev/sd*16:44
njinpenguin4222: strike again16:46
njinpenguin42:strike again16:47
penguin42heck, that bug is almost exactly 2 years old :-)16:48
penguin42njin: So, the important thing is that while sda, sdb etc isn't important, it IS important that things work correctly in the installer/boot loader, and that nothing still uses sda etc16:49
njintrue16:50
penguin42it was a bit unexpected when it first appeared though16:52
penguin42it took me ages to figure out why my RAID wasn't starting up reliably16:53
=== Afwas_ is now known as Afwas
xelisterhttps://bugs.launchpad.net/ubuntu/+source/krusader/+bug/48119818:17
ubot2Ubuntu bug 481198 in krusader (Ubuntu) (and 1 other project) "Krusader always crash on start after todays upgrade of system (ubuntu 9.10) (affects: 1) (heat: 8)" [Medium,Triaged]18:17
xelisterI solved the almost year old bug where krusader always crashes18:17
xelisterlets push the patch upstream?18:17
xelisterits a trivial oneliner18:18
penguin42xelister: Have you mailed the package owner or attached your patch to the bug?18:19
xelisterno18:20
micahgxelister: have you tested with KDE 4.518:20
yofelaccording to the last commenst on kde bug 191167 this seems fixed18:20
ubot2KDE bug 191167 in general "Krusader crashes at startup (PanelManager::slotChangePanel, KrusaderView::start)" [Crash,Unconfirmed] http://bugs.kde.org/show_bug.cgi?id=19116718:20
yofel*comments18:20
penguin42xelister: Often their quite happy to put little fixes in or push them upstream18:21
penguin42xelister: It varies a bit depending on the maintainer etc18:22
xelisteryofel: well it is broken in lucid proposed, why not push NOW this trivial fix to help thousand of users right today19:37
yofelwell, sure, package your patch, do the SRU work19:38
yofeland usually send the patch upstream, but that might not be necessary in this case19:38
yofelyou could check if it happens with the upstream devel version19:38
xelisteryofel: I attached the patch, anything more?19:38
xelisterhttp://launchpadlibrarian.net/53767856/krusader_2.0.0-1ubuntu4.debdiff19:38
yofelfor one, you can't upload it to lucid but only to lucid-proposed, after that follow https://wiki.ubuntu.com/StableReleaseUpdates19:39
xelisterI dont have any write access19:40
yofelmaybe ping someone in #ubuntu-motu or #kubuntu-devel if they have time to review it19:40
micahgxelister: the SRU process describes sponsorship19:40
micahgxelister: if you need review, subscribe ubuntu-reviews19:41
xelister+ if (!(leftActiveTab < leftTabTypes.size())) { leftActiveTab=0; } // fix bug LP: #48119819:41
xelisterlong review ;)19:41
yofelnow let's see if that still happens in maverick..19:45
yofelxelister: it crashes always on start? anything more to be done to reproduce it?19:47
xelisteryofel: you can simulate the bug as described19:48
xelisteredit .kde/share/config/krusaderrc19:48
xelisterset  Right Active Tab=9919:48
xelisterand run krusader.  Sometimes krusader set such out of range variable on its own and then it cant be started untill manually edit or remove the config file above19:49
yofelok, doesn't crash on maverick, I'll set the bug to fix released19:49
xelisterreally doesnt crash?19:49
xelisterfucking amazing, after just 1 year =)19:50
yofelmaverick has 2.2.0-beta1 currently, and the code you fixed was completely rewritten in the upstream source, so I guess the crash reason went to the grave with the old code :P19:50
micahg!coc | xelister19:50
ubot2xelister: The Ubuntu Code of Conduct is a community etiquette document to which we ask all Ubuntu users to adhere, and can be found at http://www.ubuntu.com/community/conduct/ .  For information on how to electronically sign the CoC, see https://help.ubuntu.com/community/SigningCodeofConduct .19:51
xelister!americans_and_europeans_worying_too_much_about_words_and_moral_panic | micahg19:51
ubot2xelister: Error: I am only a bot, please don't think I'm intelligent :)19:51
yofeldoesn't matter, channel policy19:51
xelisteroh well, perhaps another bug that I fix will be actually needed :)19:51
micahg!language is the correct factoid....19:54
yofelxelister: can you do the SRU? fixing it in lucid would be nice19:55
xelisterperhaps we should make my factoid for ballance?19:57
crimsun_I'm with yofel; it should be fixed in 10.04 LTS19:59
crimsun_quite a few of us present can assist you with an SRU19:59
xelisterwell how to do it?19:59
yofelxelister: did you read the link I gave you?20:00
yofelplease do that first20:00
penguin42anyone know if there are any specific things for debugging X crashes - i.e. do I have to stop X doing the backtrace?20:01
crimsun_there's a wiki page (or set of) for that IIRC20:01
yofelif you have a frozen X, there is https://wiki.ubuntu.com/X/Troubleshooting/Freeze20:02
yofeland generally the X/Troubleshooting wiki section20:02
penguin42this is a seg not a hang20:03
yofelnot sure, usually apport should catch segv20:04
penguin42oh it has, and it's got a nice juicy backtrace - I wondered what the best way to attack it was; I can take gdb to it, but I wondered if there were any X specific debug tricks20:05
penguin42ahha https://wiki.ubuntu.com/X/Backtracing20:09
xelisteryofel: nope, Im bussy with 2 girls20:14
xelisterand then I have job20:14
xelisterperhaps in upcoming days when I have vacation though20:14
crimsun_xelister: which bug are you referring to? I'll try to pop in and help if I can.20:14
penguin42sheesh, you're putting your job and sex life before debugging out bugs?20:14
penguin42sorry, lives20:14
xelisterpenguin42: bug is debugged, I dont like the beaurucracy stuff todo20:15
yofelcrimsun_: bug 48119820:15
ubot2Launchpad bug 481198 in krusader (Ubuntu) (and 1 other project) "Krusader always crash on start after todays upgrade of system (ubuntu 9.10) (affects: 1) (heat: 10)" [Medium,Fix released] https://launchpad.net/bugs/48119820:15
micahgxelister: process is easy once you get used to it20:15
xelisterwell "debugged", it took entire 2 minutes to fix20:15
crimsun_yofel: / xelister: thanks, I'll look after I upload a new sawfish SRU candidate in a few moments20:16
yofelthanks :)20:16
xelistermicahg: ok so I know what to change in source, and how to make debdiff.. now what?  also, how to make a clean debdiff, it somehow shows me a diff of 1st try to fix it and the last one,  instead of original20:16
micahgxelister: the SRU page gives a list of steps20:18
micahgxelister: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure20:18
micahgxelister: the only thing missing is that you subscribe ubuntu-sponsors now and they upload and subscribe ubuntu-sru20:19
yofelso the right procedure now is to first subscribe sponsors?20:20
micahgyofel: yeah, now -sru prefers to review in uload queue20:22
micahg*upload20:22
yofelmicahg: can you fix the wiki page then, it still says to subscribe sru20:23
micahgyofel: k20:23
yofelthx :)20:23
micahgyofel: well, the email says to subscribe ubuntu-sru and then upload or subscribe sponsors20:28
micahgI guess I should revert the change...20:28
* micahg goes and asks20:29
njinyofel: heve you received requests from QA to testing iso today ?20:33
penguin42anyone understand what the difference between the -dbg packages ('This package provides debugging symbols...' and the -dbgsym package is?20:41
crimsun_historically (and generally), -dbg are specified in debian/control explicitly and built with nostrip, etc.20:45
crimsun_-dbgsym are generated "automatically" on the buildds20:45
crimsun_someone more familiar with pkg* on the buildds could clarify/correct further20:46
penguin42hmm well if I have both to choose from is there any particular one is more useful?20:47
crimsun_I tend to choose the latter when available20:47
penguin42the -dbgsym?20:47
crimsun_yes20:48
penguin42ok20:48
yofelnjin: for the kubuntu ones I'm subscribed to no20:51
=== JanC_ is now known as JanC
yofelcrimsun_: actually you're right -dbg needs to be specified in control and dh_strip redefined whereas the (official!) buildds create -dbgsym packages for all packages that are built20:53
yofelalso -dbg is afaik for the whole source package whereas -dbgsym is built for every binary package20:53
yofeland the last difference I can think of right now is that -dbg packages are in the primary archive while -dbgsym packages are on ddebs.ubuntu.com20:54
yofelpenguin42: ^20:54
yofelusually -dbgsym packages are preferable as every package has one, but note that -backports and PPAs don't have -dbgsym packages20:55
penguin42yofel: When you have a source package and do a debian/rules binary it's built me the .debs but hasn't build the -dbg - the unpacked directories are in the build directory but it hasn't built a .deb20:55
njinyofel: strange, i've received two request (yesterday and today) to test ubuntu amd64 (20100814 and 20100815) coming from QA Testing Tracker <qatracker@stgraber.org> but these images dont exists (latest is 20100812)20:56
yofelpenguin42: well, what package and does that package have a -dbg package?20:57
yofelthere is no -dbg package by default20:57
penguin42yofel: xserver-xorg-video-radeon and I can see it calls dh_strip passing a flag to produce a -dbg and I can see the files that make up the package in the build directory, just no .deb20:58
yofellet me try21:00
yofelnjin: odd...21:00
njinstsrange, i write a mail to xdatap for further info about21:01
yofelpenguin42: running 'fakeroot ./debian/rules binary' created a xserver-xorg-video-ati-dbg_6.13.1-1ubuntu2_amd64.deb here21:06
njinsuggestion for this https://bugs.launchpad.net/ubuntu/+bug/41193721:07
ubot2Ubuntu bug 411937 in ubuntu "switching between lay-outs is not responding (affects: 1) (heat: 9)" [Undecided,New]21:07
penguin42yofel: Sorry, you're right - I was being dumb and got confused among the pile of debs21:07
penguin42sorry about that21:08
yofelheh, np :)21:10
njini go to sleep, see you tomorrow.22:05
yofelmicahg: should I just close that bug? theoretically that's the case in lucid too, but I just can't find any official statement on this22:10
=== nUboon2Age is now known as nUboon2Ag
LicuadoraI cant turn off my PC23:40
Licuadoraeverytime i try to turn it off, it will send me to the login screen23:40
Licuadoraand if i try it there, nothing happens23:40
penguin42odd23:41
Licuadorai have to push my machine's power off button23:41
LicuadoraI know23:41
LicuadoraTHA has to be a bug23:41
penguin42what happens if in a shell you do sudo shutdown -h now23:41
Licuadorait might turn off, but then am i gonna have to do that everytime i want to turn it off?23:42
penguin42Well the 1st thing to do is to figure out if that turns it off - if it doesn't then it's even weirder23:42
Licuadoralet me try it23:42
LicuadorIt worked23:46
LicuadorSo, what is this happenning?23:46
Licuadorpenguin42: you know whats happenig?23:47
penguin42nope23:47
Licuadorhm...23:47
Licuador*chuckles*23:47
penguin42do you use gnome or kde?23:47
Licuadorgnome23:47
penguin42Licuador: Well, thing is we know from that the BIOS and kernel are happy to turn it off, so that bit works23:48
LicuadorAny command for the terminal to see whtas wrong?23:48
penguin42Licuador: Lets just check; how are you shutting down - what exactly are you clicking?23:49
Licuadorok, i push the on/off icon, then shut down23:50
penguin42ok23:50
Licuadoran then othe login screen23:51
penguin42when you get to the login screen, there's a shutdown button at the bototm right isn't there? Does that work?23:51
Licuadori try there to shut down with the option in th righ lower desktop23:51
LicuadorNo, it does not work23:51
Licuadorit doesent do anything23:52
penguin42hmm well that's 1 thing that works and 2 that don't!23:52
penguin42Licuador: OK, so when it dumps you back at the login screen, log back in and run dmesg > afile   and see what it says in that file, also take a copy of .xsesson-errors (and I think there is a .old), a copy of /var/log/messages as well23:54
=== easter_egg|off is now known as easter_egg
LicuadorSo, after login and typing dmes> afile I go to .xsession-erros and do a copy paste?23:56
Licuadorlet me try it23:56
penguin42take a copy of it23:57

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