[03:03] So what other feasible methods of testing Lucid would there be? I've already tested the Nouveau driver on my system, used checkbox, and reported any application crashes with apport so far. [03:04] Anything else that's fairly straightforward to do, or? [03:21] Takyoji: there is some stuff about testing on the Ubuntu QA site. http://qa.ubuntu.com/ [03:22] Takyoji: some testcases you can do manually. http://testcases.qa.ubuntu.com/ [03:23] Otherwise Mago; is that of writing scripts to automate the process of doing test cases [03:23] Takyoji: yes [03:33] So if something doesn't work as intended, where would the issue be reported to? [03:34] For example, I can't do anything to SD cards; they only mount as read-only on two of my systems (while on my other laptop, I'm able to read and write) [03:36] you would report it to launchpad [03:40] Takyoji: there is soome usefull info here. https://help.ubuntu.com/community/ReportingBugs [03:41] Takyoji: here is some info specific to Removable Media: https://wiki.ubuntu.com/DebuggingRemovableDevices [03:42] Thank you [03:48] 9.10 and above doesn't use HAL anymore, right? [03:48] or am I think of something completely different? [03:50] thinking* [03:53] Takyoji: you are thinking of the right thing [03:53] Takyoji: I am not sure how fully its been removed. [03:55] because I noticed the documentation was referring to it [03:59] Takyoji: looks like hald is still in use in 9.10. Cant say about Lucid [04:00] you can check with: ps uaxxc | grep hal [04:01] There's about 10 processes running starting with "hald" [04:03] Should I add my generated files to this bug, or file a new one? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228941 [04:03] Launchpad bug 228941 in linux (Ubuntu) "sd card detected as read only" [Undecided,New] [04:05] Filed about 1.8 years ago [04:21] Takyoji: if you wanted to attach it to that bug you would need to determine if you share the same problem. Which could take a little investigating. In order to add to that bug you would need to be certain you bothe suffered from the same 'root cause' [04:21] not symptoms. Many problems can cause the same symptom, but might not be the same bug [04:22] So then file it as a new bug, and if it is deemed to be the same thing, it'd be marked as a duplicate? [04:22] if you are unsure file a seperate bug [04:22] alright [04:23] And just mark it to only affect the "linux" package? [04:24] or would there be any other packages that I should tag it to as well? [04:27] Takyoji: that is tought o say. There a couple of different things that could prevent the SD Card reader from working correctly [04:27] certain bugs it is not always so obvious what the right package is [04:27] you might look through your 'dmesg' and see if there is any clue [04:28] There's nothing that implies an error of when the SD card was mounted [04:29] the only thing directly relevant is that it implies "Write Protect is on" [04:29] although the card is not locked [04:29] and I've tried vacuuming and canned air to clear the SD card port. [04:32] Takyoji: you can try running: tail -f /var/log/syslog [04:33] while monitoring the Terminal insert the card and see if anything comes u;p [04:34] just the same information as dmesg [04:34] Takyoji: what format is the card? [04:34] also, I noticed a broken link [04:34] FAT32 [04:35] I can't even change the partition type (and yes, after unmounting the device first) [04:36] In other words, I can't reformat it as EXT3, EXT4, FAT16, anything. [04:37] the error message provided is "Error creating file system: helper exited with exit code 1: cannot open /dev/sdb1: Read-only file system" [04:40] As I was implying; I noticed a broken link. On Launchpad, when you're reporting a bug related to the linux package, there's a section titled "linux (Ubuntu) guidelines:" that refers to a page of instructions on the Ubuntu Wiki, a page which doesn't exist. [04:41] Takyoji: you can check the disk for errors [04:41] sudo dosfsck -a -v /dev/sdb1 [04:43] It implies the version of it at first; then it implies "open: Read-only file system" and returns back to bash [04:44] "dosfsck 3.0.7 (24 Dec 2009) [04:44] dosfsck 3.0.7, 24 Dec 2009, FAT32, LFN [04:44] open: Read-only file system" [04:48] what does : ls -l /dev/sd* [04:48] say for sdb1 [04:49] Takyoji: also: cat /etc/fstab [04:50] should have an entry like this: /dev/sdc1 /media/usb vfat defaults 0 0 [04:50] http://paste.ubuntu.com/378136/ [04:54] ok [04:55] /dev/sdb1 /media/usb vfat defaults 0 0 [04:56] add that to your fstab. [04:56] gksudo gedit /etc/fstab [04:58] alright [04:59] Then restart thereafter, or? [04:59] Otherwise it's actually an SD card, and wouldn't I have to create the directory /media/usb? [04:59] Or is that only if I was going to manually mount it? [05:01] Takyoji: yes you would if it does not exist [05:01] create the directory that is [05:02] sudo mkdir /media/usb [05:02] Now restart the system? [05:02] yes [05:04] Still read-only [05:04] :( [05:07] I've actually added it to fstab previously, and tried forcing read/write capability to no avail and so forth [05:08] Takyoji: ahhh [05:08] So would it be conclusive to file the bug then? [05:09] I have various SD cards by the way; not just one. All of varying sizes and speeds. None of them seem to ever mount as read and write [05:09] Takyoji: i am out of ideas :) [05:09] As implied; it's the case for two of my desktops, except for one laptop [05:09] And the two desktops are completely different in hardware [05:11] otherwise thank you for your assistance and time [05:20] your welcome i hope you get it working [05:20] hopefully [06:06] Takyoji: did the desktops have different SD card readers, or were you sharing one between them? [06:06] Completely different card readers [06:06] They're both internal ones [06:09] otherwise I'll be leaving in a couple minutes or so [06:10] Takyoji: are they usb internally or something else? Do they show up in lsusb or lspci? [06:10] They might be USB; I'm not entirely certain. I'd have to check [06:11] It'd be interesting to search for those specific reader devices and see if they're mentioned in other launchpad reports or elsewhere. [06:11] tomorrow I'll check when I get the chance and hopefully remember to report back [06:13] Given that multiple cards are having the problem, I'd be looking at the kernel's interactions with the readers as to be the likely source of the issues; I've had no difficulty mounting sd cards, but I don't have a wide variety of readers to work with. [06:14] They can read the cards fine; it's just they're never mounted as read and write; even when forced or manually implied [06:15] So I can't ever change anything on the SD cards [06:16] Right, what I mean is that the kernel and the SD readers are having a difference of opinion as to whether the RO bit is set on the card. [06:17] Yea, dmesg implies that it has write protection enabled when it's mounting it [06:17] which is why it can't be mounted RW. [06:17] "Write Protect is on" [06:18] Yet I don't even know if I could "override" that somehow [06:20] Anyway, I'll try to return tomorrow. 20 minutes past midnight here. [06:28] good morning all! [07:56] mvo, morning [07:56] mvo, can you paste again the branch with your kvm autotests for upgrade testing? I am interested in having a look [07:56] mvo, thanks [08:02] ara: good morning [08:03] https://code.edge.launchpad.net/~mvo/autotest/gui-upgrades [08:03] that is the branch [08:03] mvo, thanks! [08:03] it contains a step file for karmic->lucid and hardy->lucid [08:03] mvo, awesome, thank you [08:03] problem is that hardy-lucid will not work because of bugs during the upgrade (unexcpeted config file, networkmanager starting to fail etc) [08:03] but I guess that is a good thing :) [08:04] mvo, :) [08:04] I got a machine to run the kvm tests on, I'm currently investigating if it could be used for autotest too [08:06] but its having a really old kvm (kvm-62) that I'm not 100% trust [08:06] but in general ... stepmaker == love [11:05] Morning all [11:16] morning davmor2 [12:41] * ara -> lunch === fader|away is now known as fader_ [13:31] fader_: morning Muppet Boy. How's tricks? [13:31] davmor2: Hey dude, what's shakin'? [13:32] fader_: The tree branches outside in the wind [13:32] Heh [13:34] or http://www.youtube.com/watch?v=28TR06gLsiw [13:43] fader_: did you forget my awesome ability for bad taste ^ [13:43] davmor2: never ;) [13:45] davmor2, fader_, ara, marjo : G'morning [13:45] moustafa: Hey dude [13:45] hey moustafa [13:46] How are you fine folk doing? [13:54] moustafa: how's things dude? [14:33] davmor2: It's a work in progress [14:33] :) [14:39] cr3: Baguette! [14:45] cr3: No baguette? [14:46] moustafa: sorry, in the middle of a conference right now, not much time for soupe du jour [14:47] cr3: gotcha [15:40] alexmoldovan, hey - > come to #ubuntu-qc [15:41] hey MagicFab! [15:44] moustafa, o/ === hggdh_ is now known as hggdh [17:17] alexmoldovan: Do you remember the bug number for the nvidia freeze bug? [17:17] davmor2: I thought I had the bug tagged but it looks like I didn't :/ [17:17] :( [17:18] let me see [17:18] according to keybuk it sounds like it's known :) [17:19] alexmoldovan: nm, found it -- bug 522692 [17:19] Launchpad bug 522692 in plymouth (Ubuntu) "Pressing key causes X to freeze (affects: 15)" [Undecided,Confirmed] https://launchpad.net/bugs/522692 [17:19] And yeah, it's a known issue [17:19] that's the one [17:19] Seems to be a plymouth thing [17:19] yes [17:20] I tagged it this time :) === fader_ is now known as fader|lunch === fader|lunch is now known as fader_ [20:09] bye [20:31] Hello, is there a possibility to get sun java 6 installed on Lucid lynx? [20:46] ppine: You might have better luck asking on #ubuntu+1 [20:47] This channel is mostly for coordinating ongoing tests and is rather quiet at the moment [20:50] fader_: thanks, i'll try that. === fader_ is now known as fader|away