© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
> Why did you all of a sudden change the summary of the bug?
I'm trying to sort out the SD card reader bugs so there is one open bug for each specific piece of hardware that doesn't work. I thought this bug looked like it should be about this hardware, not yours, since you jumped in later and realized that you were reporting something different from the others.
I guess you assumed that this bug was now about your problem, which is fair enough given the several replies on that topic. So maybe I was a little cavalier in taking over this bug to make it into the originally reported issue. However, something has to change, since this bug # can't be about two separate bugs... Bugs have to be very specific so they can eventually get closed when fixed, instead of morphing into the next problem. I was trying to figure out my own hardware, and eventually reported bug 303844.
> This affects me and it has nothing to do with a sony card reader.
You have a Ricoh R5C822, which is not the same hardware as the original reporter, or Matt LaPaglia. Are the problems you're reporting more like bug 247819?
I tagged some other bugs with "sd":
https:/
but there are probably others about SD card readers that aren't tagged. Hmm, maybe I shouldn't have picked a tag that also stands for scsi-disk. Ubuntu maintainers, please advise... I can go retag bugs with sdhci or something. (although some hw uses tifm...)
So sorry for the inconvenience, but could you open a new bug report for your bug? You can link to this bug for reference, but it would be good to include a current lspci -vvnn, dmesg, and kernel version in the new bug. Or if you find another bug that looks like what's affecting you, see if it needs more info or something.
thanks.