[00:37] Hi [00:38] Any idea about the comment #5 in https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/784604 when is it going to be available in the repos ? [00:38] Launchpad bug 784604 in sun-java6 (Ubuntu) "a new java version is available for download (affects: 2) (heat: 14)" [Undecided,Confirmed] [00:43] Can someone please comment about what does confirmed mean [00:43] does it mean its acknowledged by dev team [01:10] Checking in again for the query [01:19] kaushal: confirmed usually means that at least one other person is experiencing the issue [01:22] ok [01:22] greg-g: when is it going to be available ? [01:33] kaushal, unknown ATM. [01:36] ok === augustinT is now known as autra [10:34] Do you know why in Launchpad when I try to Triage a bug it's disabled? [10:36] You're part of bugsquad only ? [10:37] (too late :-( )) === Daviey is now known as Da === Da is now known as Daviey [11:36] lp issues on a bug day. crikes [11:59] yep brendand, lp keeps timeouting here too === pedro_ changed the topic of #ubuntu-bugs to: Today is a Bug Day! : http://is.gd/SGIi1a | Ubuntu Bug Squad - next meeting 6/9/11 | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu === pgraner is now known as pgraner-afk === pgraner-afk is now known as pgraner [14:38] https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/793291 should be Low Importance, as it's pretty much a corner case [14:38] Launchpad bug 793291 in nautilus (Ubuntu) "DoS window manager with extremely long error (affects: 1) (heat: 1134)" [Undecided,Confirmed] [14:42] brendand: done [14:42] RedSingularity - thx [14:42] brendand: no prob :) [14:47] brendand, is that a window manager crash or a nautilus crash? [14:48] can't reproduce it here btw [14:48] pedro_ - well no, the whole window manager doesn't crash. [14:48] pedro - if you run that code no window appears [14:48] pedro_ - but if you run it with a shorter name then one does [14:49] pedro_ - sometimes you see the window flicker and appear briefly before disappearing [14:50] why is it a DoS? [14:51] the title is really confusing.. [14:54] anyways that's something to send upstream, they might have a better idea on what's going on there [14:54] brendand, one exercise left is to find out up the minimum size ;-) [14:54] as brendand said is really a corner case [14:55] pedro_ - do you know anywhere i could look to see if the window manager/nautilus actually crashed? [14:55] brendand: maybe .xsession-errors [14:55] brendand, ~/.xsession-errors [14:55] heh [14:55] roadmr, was faster, hello btw! [14:56] hello! [14:58] pedro_ - astonishingly, this could be a bit more severe than i thought [14:58] pedro_ - once i run 'nautilus `python -c "print 'A' * 1000"`' in a terminal, compiz starts going a bit nuts [14:59] pedro_ - corrupts launcher and dash in the area where the window would have gone [14:59] ah maybe because the window is gigantic [14:59] pedro_ - so might be a compiz thing, just a really big window is a good way to make it happen [14:59] hggdh: meeting at 1900 UTC correct? [15:00] brendand, i'm trying with metacity , wait a sec [15:01] brendand, yeah looks like a window manager issue, its crashing metacity [15:01] i'm getting a nice BadAlloc [15:08] * brendand wishes people would file bugs where you don't have to do 30 mins of your own investigation to figure out what they meant [15:08] is changing (add/remove) tags working for anybody? [15:08] in lp of course :-P [15:09] here is just showing me the loading icon and then nothing is changed [15:09] pedro_ - i still reckon it's low importance. quite the corner case. i think 1000 chars does it at the moment [15:09] brendand, yup indeed [15:10] is there a cli to extract the stuff between ---[ cut here ]- and ---[ end trace ? [15:15] RedSingularity, correct [15:19] https://wiki.ubuntu.com/BugSquad/Meeting [15:19] it says 1700 UTC hggdh RedSingularity [15:20] pedro_, argh! Foiled again by the Google Calendar :-( thanks [15:20] CarlFK, perl is your friend, something like: perl -ne "print if /^---\[cut here/ ... /^---\[end/" path/to/your/trace.file [15:21] CarlFK, modify the regex as needed of course [15:22] jibel: yeah, just thinking if there was a util it would have other fancy features too [15:22] CarlFK, perl has many other fancy features ;-) [15:22] perl is so fancy [15:22] swell [15:26] pedro_ - the bug is in the window manager not nautilus, but seems to happen in both window managers (metacity and compiz). should i move the original to compiz and raise a new one in metacity, or 'also affect' metacity? [15:26] brendand, that sounds good, yes please [15:27] brendand, thanks for looking at the issue! [15:27] [ 0.000000] Your BIOS is broken; DMAR reported at address 0! [15:28] how do I dump the bios so I can compare it to a 2nd box that doesn't error? [15:30] CarlFK, when looking for an utility, it _may_ help running 'apropos' [15:31] CarlFK, for example, 'apropos bios' [15:31] ohh cool [15:31] CarlFK, from the output I see 'biosdecode (8) - BIOS information decoder' <- this may, or may not, help [15:33] CarlFK, a caveat... it all depends on the search argument (and if there actually is anything that deals with it) [15:39] CarlFK, but... this sounds like a bad BIOS. This may, or may not, work: http://forums.fedoraforum.org/showthread.php?t=245794 [15:41] enable virtualization - good chance that's the diff between the 2 boxes [15:41] thanks [15:42] these boxes have really annoying bios setup, so I didn't want to have to try and walk though each screen looking for the diff [15:45] pedro_ - in metacity do you see any 'blurring' in the area where the window should have been? [15:45] pedro_ - that's what i get in compiz [15:47] hggdh: yep. virt was different. synced them, now both crash :) [15:50] brendand, nope i don't see that, that's probably due to the compositor [15:51] brendand, i just see a 'huge' window [15:51] CarlFK, heh [15:51] pedro_ - i thought metacity crashed? [15:52] brendand, yup i'll open the bug about it in a few since it's a memory crash need to get a valgrind log [16:05] hggdh, me too. I have 1900 written here. [16:06] RedSingularity, you may need to update the entry, we did change from 1900 (every other week) to 1700 every week [16:06] RedSingularity, what foiled me is Google calendar never showing UTC [16:07] hggdh: yeah. Looks like someone updated the page already. good. [16:09] compiz bug tracker has only 38 bugs? something fishy about that to me... [16:23] huh? we changed the bugsquad meeting to weekly? [16:25] hggdh: go to calendar settings, add a time zone, utc, and click on show all timezones [16:25] It will then show both UTC and normal timezones side-by-side === zyga is now known as zyga-afk-bbl-sry [16:36] charlie-tca, still... I cannot see the additional TZ :-( [16:40] hggdh: probably told you wrong again. take a look here and find this - http://imagebin.org/157528 [16:53] hi [17:02] Hi loganaden === ogasawara_ is now known as ogasawara [17:06] braiam hi [17:08] charlie-tca, you told me right, it is Google vs. Me ;-) === deryck is now known as deryck[lunch] [17:50] BugSquad Meeting in ~10 minutes at #ubuntu-meeting [17:50] not here at #ubuntu-meeting don't forget about that [17:55] BugSquad Meeting in ~5 minutes at #ubuntu-meeting [17:59] BugSquad Meeting now at #ubuntu-meeting === deryck[lunch] is now known as deryck [20:21] hi everyone, got a question about filing a bug-report and wheter my problem is even a bug [20:22] ma ubuntu 11.04 is not booting after installing the latest updates (which included newer versions of xserver, gdm and plymouth) [20:23] can i revert these packages to the old ones and should i report a bug? === yofel_ is now known as yofel [20:39] drowned1723 - if the updates weren't from -proposed then you should report a bug [20:40] drowned1723, ideally you should report a bug first -- even on a -proposed kernel (may be a regression) [20:40] drowned1723 - what hggdh says is true actually [20:41] happened on a clean install of ubuntu 11.04, just 1 day old. [20:41] i will report a bug against plymouth [20:41] drowned1723 - why plymouth? [20:41] drowned1723 - plymouth is just a splash screen [20:42] i would say it's a graphics problem, as the kernel wasnt updated [20:43] drowned1723, if you can add (screenshots are OK) the boot messages it may help [20:43] no boot messages, as the screen goes blank immediatly after grub beeps [20:44] 1. Hold Shift during Grub boot delay to access the boot menu. [20:44] 2. Select your actual Ubuntu boot line and press "e" to edit it. [20:44] 3. Select the "linux" line and at the end of the line, remove "splash" and "quiet". [20:44] 5. Press "F10" to boot the custom boot line. [20:45] try a recovery startup, or edit the kernel options to take out the graphical options [20:45] as above [20:45] heh. brendand was faster ;-) [20:45] i updated grub via livecd to not include the quiet splash. still the same [20:45] hggdh - with instructions and all ;) [20:45] :-) [20:45] and grub won't show the menu when hitteing shifgt [20:46] drowned1723, even on a recovery boot? [20:46] how do i get into recovery boot? via grub menu? [20:46] oh. You do not see the grub menu... [20:46] yep [20:47] drowned1723: you need to use the left shift key, just keep it pressed while booting the computer, grub menu *should* come up [20:47] drowned1723: also you mentioned grub beeps, that's when you need to hit shift (if grub beeps, it means you enabled the GRUB_INIT_TUNE [20:48] i kept hitting it, not keeping it pressed. i should try that. [20:48] it wont even show the blinking cursor thats normally displayed beore the splash screen [20:49] reinstalling grub from live cd didn't help either [20:49] it's really strange that grub died altogether :-/ [20:50] another option is to boot from a liveCD (or the alternate ISO), and select to mount your root disk [20:51] i mounted my root partition, chroot into it, edited /etc/default/grub to not include quiet splash and did grub-update [20:51] that's also where i enabled GRUB_INIT_TUNE [20:52] you can also change GRUB_TIMEOUT="-1" [20:52] this will cause grub to wait until you select an entry [20:53] um, well if grub is picking up changes, it means it's not entirely dead :) [20:54] for reference, this is my grub setup: http://paste.ubuntu.com/622821/ [20:56] time to restart after upgrades BRB [21:00] i changed GRUB_TIMEOUT="-1" and will try reboot..brb [21:01] drowned1723 - if plymouth is off (quiet splash removed) then the bug can't be in plymouth [21:01] we will see, after the restart ;) [21:01] by [21:02] roadmr - i don't understand his problem :/ [21:03] brendand: I have no idea either, he said after updating, I've done that and I'm still running [21:03] roadmr - hardware specific? [21:04] brendand: maybe, if he upgraded the kernel, but there are usually no nasty regressions like that on minor updates [21:04] his drivers might not have migrated to the new kernel but then again, he'd get at least a splash or some text before crashing [21:05] roadmr - kernel hasn't changed for natty [21:05] roadmr - since release - has it? [21:05] roadmr - i don't recall any SRU's going past [21:05] brendand: you're right, it's still -8 [21:05] brendand: however, -10 is already in -proposed [21:06] roadmr - that's not going anywhere because of a regression. [21:06] afaik [21:06] there was, IIRC, a nasty regression on current natty -proposed [21:07] brendand: wohoo, well I know of at least one bug reporter that was using -10 [21:07] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/792013 [21:07] Launchpad bug 792013 in linux (Ubuntu) (and 9 other projects) "linux: 2.6.38-10.44 -proposed tracker (affects: 1) (heat: 14)" [Medium,In progress] [21:07] i'm back. was able to boot into recovery mode using low graphics. [21:07] drowned1723: hey, great to see you made it! [21:08] thx. [21:08] drowned1723 - what gfx card to you have and what kernel version are you on? (uname -a) [21:08] drowned1723 - and welcome back :) [21:08] 2.6.38-8-generic #42-Ubuntu SMP [21:08] gfx is a radeon 6800 i think. [21:08] the best (guaranteed) way of finding the kernel build is via /proc/version_signature [21:09] drowned1723 - that hasn't changed then since release [21:09] ages old, still using AGP === zyga-afk-bbl-sry is now known as zyga [21:10] brb [21:10] i haven't used proprietary drivers, but the default one [21:10] drowned1723 - 'radeon'? [21:10] i guess? where can i check that? [21:11] lspci -vvnn [21:12] drowned1723 - have to find the card in there and look at the kernel driver in use field [21:12] Kernel driver in use: radeon [21:14] MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM#;/?????????????????????????????????????[ [21:14] i'm confused [21:15] whoa [21:16] my daughter - lol :) [21:16] note to self - keep computer out of reach [21:16] ^^ [21:18] so, how do i proceed, to find the screwup in my system? [21:24] drowned1723 - you really don't see any messages when booting? [21:26] no messages. immediately showing a black screen. [21:27] i havent tried starting it from the grub menu yet. but there is no quiet splash in the bootoptions, just the way i have configured grub [21:28] i'll try booting the normal option from the grub menu, see if there are any messages. brb [21:35] now i'm completely confused. the normal boot option booted whitout splash right into gnome 2, as it's supposed to. only it's very low resolution like in recovery mode [21:36] and system->pref->monitors won't detect my monitor, which worked perfectly fine before the updates [21:39] drowned1723: does everything else work fine? could you check the video driver you're using, as you did earlier? could you run xrandr -q and see which resolutions are listed, and which one you're currently using? [21:42] max resolution listed is 1024x768, but it should be full HD [21:44] kernel driver in use: radeon [21:48] everything seems to work fine, sound, video (flash) etc. [21:49] seems to me, that EDID is not read succesfully [21:51] and this worked well prior to the upgrade, right? for instance, do you see the full list of resolutions if you boot with a livecd? [21:51] yep [21:52] hehe sorry for asking two questions :) I guess the more interesting one is the second: a livecd shows you the full list of resolutions, correct? [21:52] yes it does. and it correctly sets the resolution to 1080p [21:52] drowned1723: ok, so I think you might be on the right track with the EDID thing [21:53] edid is handled by which package? xorg? [21:53] latest Oneiric updates seem to have broken gdm/wireless [21:53] drowned1723: I think so. Maybe comparing the /var/log/Xorg.0.log files could yield a clue; the one from your broken installation, and the one from the LiveCD [21:54] hggdh: heh on Oneiric I don't even get a panel and/or Unity, I have to launch a terminal and work from there [21:56] drowned1723: You could file a bug on xorg, if you decide to do so, I think the copy of the LiveCD Xorg.0.log would be useful, to be attached to the bug in addition to what apport does [21:56] guess i have to restart into the livecd and copy the xorg.0.log. anything else i should look for/copy while i'm at it? [21:57] drowned1723: I don't think so, I think filing a bug is the way to go, apport will attach package version information and relevant log files, just add the LiveCD one afterwards [21:57] ok, will do that. [21:57] drowned1723: that way all the relevant info is in one place and we're not exchanging information piecemeal like we've been doing [21:57] drowned1723: thanks :) [21:58] drowned1723: here's some info on what the X team likes to see in their bug reports: https://wiki.ubuntu.com/X/Reporting [21:58] btw: if i force the older version of xorg to be installed via synaptics, are there going to be severe consequences for my system? [21:59] drowned1723: as long as all the other dependencies get correctly downgraded, I don't think so, but I can't offer any guarantees :P [22:00] drowned1723: you could also ask in #ubuntu-support about the downgrading thing, someone in there might have some experience with that [22:01] thanks. i will file the bug report, attach the live-cd-xorg-log and then try to downgrade. [22:01] thank you all for your help, very much appreciated =)