[10:03] <mote> Hi. If i test the "lucid-desktop-i386.iso" live session on my laptop, and there are hardware incompatibility problems. Like, the usb ports dont, no WiFi, and sound. Is that bugs i should file on launchpad?
[10:33] <ara> mote, is that the daily iso?
[10:35] <mote> yes
[10:37] <ara> mote, if you go System -> Administration -> HW drivers, what do you get?
[10:40] <mote> Oh. Rebooted again i 9.10 where i got most things working. Its a brand new Asus eee 1005p and there are a bunch of things that dont work out of the box. I hope that by testing on it i would help ubuntu to know what drivers are missing.
[10:41] <mote> I am running the beta 1 on my amd pc, all there hardware works fine on it. and i have not found any new problems with the software.
[10:42] <ara> mote, of course it is helpful to test
[10:42] <mote> except for the windows buttons being placed on the left side ;-)
[10:42] <ara> mote, and all those bugs are worth filing
[10:44] <mote> So i should file them on Launchpad if nobody else have already? and then ad them to the bugs tracker on http://iso.qa.ubuntu.com/
[10:45] <mote> sorry for me asking again, but its a bit confusing being a newbee tester.
[10:49] <ara> mote, no worries. On IRC, please, if talking to me, put ara: before, so I can see your replies easier :)
[10:49] <ara> mote, the ISO tracker is used only for milestone testing
[10:49] <ara> mote, i.e. next week for RC
[10:49] <ara> mote, on daily testing just file the bugs on Launchpad
[10:50] <ara> mote, this is a good document on how to report bugs https://help.ubuntu.com/community/ReportingBugs
[10:52] <mote> ara: sure. ok. I read it all ready. (among 50 others) are the RC being tested allready
[10:52] <ara> mote, not yet, next week
[10:52] <mote> ara. yes sorry
[10:53] <ara> mote, here it explains how to receive email notifications when the new builds are posted: https://wiki.ubuntu.com/Testing/ISO/Procedures
[10:57] <mote> ara: thanks. I read that as well.I have been reading to much i think. I will go on testing.
[10:57] <ara> mote, great! thanks for testing and welcome!
[10:58] <mote> Have a good weekend.
[11:02] <davmor2> morning all
[11:23] <ara> morning davmor2
[14:12] <davmor2> plars: can you drop onto ubuntu-desktop and talk with didrocks about bug #551860 if you can still produce it
[14:12] <ubot4`> Launchpad bug 551860 in metacity (Ubuntu Lucid) (and 1 other project) "Crash on login with accessibility enabled (affects: 1) (heat: 8)" [High,Incomplete] https://launchpad.net/bugs/551860
[14:12] <plars> davmor2: certainly
[15:39] <mcas> the "old" daily iso works for me and didn't show bug #546743
[15:39] <ubot4`> Launchpad bug 546743 in linux (Ubuntu Lucid) (and 1 other project) "Blank screen at first boot with ATI ES1000 and 10.04 server (affects: 5)" [High,Fix released] https://launchpad.net/bugs/546743
[16:01] <fader_> mcas: You tried with ubuntu-server?
[16:05] <mcas> yes
[16:05] <mcas> right after the email
[16:06] <mcas> but now there is a new build
[16:06] <mcas> but wait
[16:06] <fader_> mcas: Can you please report the PCI ID of your graphics card on that bug?
[16:07] <mcas> oh my fault
[16:07] <mcas> its not eth es1000 ... wrong server
[16:07] <mcas> s/eth/the
[16:07] <mcas> sorry
[16:08] <fader_> Ah, okay thanks :)
[16:49] <metalf88011> is the display on Ubuntu server 10.04 Beta 2 supposed to be "jerky"?
[16:51] <metalf88011> I'm testing it in Virtualbox and the way the screen moves is rather unpleasant and I'm just wondering if its supposed to be like that or if it's a bug that's going to be fixed
[17:04] <fader_> metalf88011: No, it should not be like that... I don't see anything right away in launchpad, either
[17:04] <fader_> metalf88011: Could you please try with the latest daily and see if you still have the issue?
[17:09] <metalf88011> yes
[17:09] <metalf88011> wait my install is up to date isn't that just as good as test the daily release?
[17:13] <metalf88011> fader_ have you been testing the server version?
[17:14] <fader_> metalf88011: Yes, if it's up-to-date you should be on the right version.  I have not tested the graphics for server under virtualbox, but I'm not seeing anything wrong with the display on physical hardware
[17:14] <fader_> With -server
[17:14] <metalf88011> ok I'll have to test it on the metal later
[17:15] <metalf88011> I think I have a working testing box
[17:20] <fader_> metalf88011: If you can reliably reproduce the issue on virtualbox, please do file a bug
[17:22] <metalf88011> I'll have to do a fresh install and if I still notice it
[17:22] <metalf88011> and yeah I'll try to file a bug report
[17:24] <fader_> metalf88011: Awesome, thanks!
[17:29] <sbeattie> metalf88011: jerky in what way? I installed -server yesterday and have no issues with the display.
[17:29] <sbeattie> metalf88011: did you install the guest-utils?
[17:30] <sbeattie> (I don't have them installed)
[17:30] <metalf88011> no I'm I didn't think I could with the server version
[17:31] <metalf88011> I didn't install a gui
[17:32] <sbeattie> metalf88011: what's your host os/version of virtualbox?
[17:32] <metalf88011> its just as the display moves down line by line it isn't nearly as smooth as is with older version
[17:33] <metalf88011> host is Ubuntu 9.10 desktop
[17:34] <metalf88011> and it's the newest version of virtualbox which is Version 3.1.6
[17:35] <sbeattie> ah, I suspect the difference is server using a vesafb display instead of vga.
[17:35] <metalf88011> I also have Ubuntu 8.04 server installed in virtualbox and it doesn't have this problem
[17:39] <sbeattie> right, I think plymouth is setting up a vesa console at some point; I *think* you'd see a similar slowdown on the display if you booted the older versions with e.g. vga=0x314 on the kernel boot line.
[17:43] <metalf88011> sbeattie can you tell me how I could test to see if that's the case?
[17:47] <sbeattie> metalf88011: sure, in karmic, reboot and hold the shift key to bring up the grub menu, hit 'e' to edit the default boot entry, arrow down to the line that begins with linux, ctrl-e to jump to the end of the line and add vga=0x314 , then do ctrl-x to boot.
[17:48] <sbeattie> pre-karmic has a different version of grub, which requires a slightly different set of steps.
[17:49] <metalf88011> oh ok
[17:55] <metalf88011> oh wait I'm using the same version of grub for both of them I had the virtual hard drive 8gb which is a lot more space then I need for one server so I installed them both side by side
[18:08] <sbeattie> testmonkey: go away
[18:08] <testmonkey> sbeattie: okay then
[18:10] <sbeattie> argh, why does apport not report assertion failures?
[20:08] <elopio> hello
[20:09] <elopio> I've just executed the extended suspend/resume test from http://testcases.qa.ubuntu.com/Plans/LaptopTesting
[20:10] <elopio> but on the first test it said: SUSPEND FAILED, did not go to sleep
[20:10] <elopio> should I report something about that?
[20:11] <elopio> the test doens't say anything, and apport didn't show up.
[20:24] <fader_> elopio: Hmm, does your system suspend when you close the lid or select the 'sleep' option from the power menu?
[20:24] <fader_> If so, it sounds like a checkbox bug.  If not, it's probably a kernel bug :)
[20:36] <elopio> fader_: yes it does. The manual suspend test passed.
[20:37] <fader_> elopio: Then this sounds like a checkbox problem.  Could you please file a bug against checkbox?
[20:41] <elopio> ok. I don't know what's checkbox but I'll look for it.
[20:41] <elopio> thanks fader_
[20:41] <fader_> elopio: "ubuntu-bug checkbox" should work
[20:41] <fader_> (Checkbox is the package that the suspend test comes from)
[20:41] <fader_> elopio: And thank you! :)
[20:41] <elopio> np