Why BROKEN 7.04 is still distributed?!

Thanks for your opinion.

Is there any concrete problem will can help you with a solution or work around?

Thanks

Thanks for your comment. Was it auto-generated? I believe that you missed the point: concrete problem is that on some hardware (see many reports) LiveCD 7.04 does not boot, on the same machines 6.10 boots OK. This is booting live CD stage, installation to hard drive is not even possible to attempt. Work around? Yes, one can boot 6.10 or different distribution, or Windows Vista. A self booting operating system CD should not be released for distribution if there are many reported cases where previous version CD boots, new version CD fails consistently with the same error. Before installation, live CD.

derek324

ubuntu is software libre, if you payed attention to Edgy Eft CD cases, you will notice the 'No Warrenty' text. Ubuntu is free software and it always will be.

Apart from that, we have deadlines to meet, we have made at least half a dozen releases before, all good and working. This is the first release with a few bugs. Mainly networking.

If you want it to be fixed, make some contribution, and feisty will get fixed that much quicker.

A good start would be making a list of all the bugs you think need to be fixed immeidiatly, and pass it on to me. I will then present to the MOTU's

We are working hard to get things fixed, the reason 7.04 is still being distributed, is that for some people it still works fine, we have to take both sides into account, and we are doing so.

Sorry about my bitching earlier, its 4am here, and i havnt slept since the last 9am

Hi Sam, thanks for replying. My observations are: 7.04 LiveCD does not boot at all on some machines on which 6.10 booted, the bug "/bin/sh:..." was reported before Ubuntu released 7.04. Ubuntu front page does not warn about it, so how many people tried 7.04, found that it does not boot, and do not have a clue why? Even people who used 6.10 before? Think about them, warn them on the Ubuntu home page. This is more than a bug, this is a show stopper. Distributing broken build is not cool.

I do understand that Ubuntu is free, there is no warranty, and I do appreciate terrific job people involved in this project are doing. I am also aware that every software has bugs, this is normal and expected. I can't contribute directly, this is not my area. But the list of reported bugs already exists, where this "no go (for some)" bug is classified as: "severity: 'medium" (!).

cheers, Derek

No it wasn't an auto-generated message. While I can understand your frustrations, maybe you might understand as well that we have no influence in those decisions, but try to help here everybody with their problems as far as it is possible.

It must also be noted that the bug you refer to differs in the consequences. I get the same message on one of the machines on which I have install feisty on, but it goes into an initramfs shell and after entering exit everything works fine. On several other feisty machines there are no problems at all.

So, please give us the information we need to help you, or to file additional bugs if this is necessary and we are more than willing in trying to help you.

Thanks

Hello txwikinger,
Thank you for responding. If "you" have no influence in those decisions, please disregard my comments, they are directed at "them" who such influence have.

I already gave all information I have. This is booting from LiveCD only, PC does not have Ubuntu installed on hard disk. The scenario is:
1) I insert LiveCD with 6.10, it boots OK
2) the same PC, I insert 7.04, it does not complete booting. The last screen is with previously quoted BusyBox error: "/bin/sh: can't access tty; job control turned off". The problem is reproducible. Other people described identical problem as well.

I am glad to see that you have some machines with different bug, and some which boot cleanly, though I fail to see any relevance of this observation.

Your questions are unclear. Yes, it is a concrete, reproducible problem. What work around can there be if a LiveCD refuses to boot? Replace the PC? Yes, I burned a few more copies. Yes, I checked them on another PCs, and they booted OK.

What information would you like to collect and how such collection could be done if a scenario described here is: LiveCD fails to complete booting process???

cheers, Derek

What kind of processor do you have? Motherboard etc.? Computer specs.

Thanks

"They" don't read this Derek, "we" do. To contact "them" you should report bugs and/or comment on existing ones.

As this is a known bug I would recommend you continue any further discussion within the bug report (if indeed it details what your problem is) - bug 96084. By adding to that bug you are improving the likelyhood it will be fixed. Replying here will likely result in someone suggesting a workaround, not a fix.

For your information the technical detail is *exactly* what is required. Many oddball chipsets on wierd motherboards don't boot well. Some CPUs have issues. Some SATA chipsets are flaky. Without knowing what devices you have, we have no hope at all of helping you. Please don't mis-interpret our responses as not caring about this problem. We do care, and we do want to see this kind of problem solved.

Whilst I appreciate it must be frustrating for you, it's equally frustrating for us to ask you twice for the same information and not get it and then be told by you that you don't think we need it and you're giving up.

I hope in the future you will consider that the people here (and in other communities) are attempting to help you with the limited information you give them. You have had 3 people reply to you so far in the space of 10 hours. All offering help and support to you in their own time. Now that you have given up on this, there may be other people out there with similar problems who will not be as technically competent as you, and aren't able to articulate the problem as well as you might.

All the best. Good luck with whichever version of Linux you choose. :)

Hi:

1. I do have Ubuntu 7.04 in three forms: The "live cd"; the "alternate cd", and the "dvd"

2. I have tested some of these on 4 completely different machines:

a. Three machines running under "pata" control
b. One machine under "sata" control

3. I can't get ANY of the "pata" controlled machines to run Ubuntu 7.04: "can't access tty; job control turned off", followed by "initramfs" error messages

4. The "sata" machine IS running the "live cd" without any problems!!

My conclusions: I do agree with "derek 324" that something changed between 6.10 and 7.04...... That "something" is that 7.04 seems to be written for "sata" controlled machines.... That "something" means that 7.04 is NOT supporting "pata" controlled machines..... That "something" is probably kernel 2.6.20!!!

N.B. I did "upgrade" one Ubuntu 6.10 system to Ubuntu 7.04, on one "pata" controlled machine.... The "kernel put in place on that system upgrade was Linux XL918 2.6.17-11-386 #2 Tue Mar 13 23:30:30 UTC 2007 i686 GNU/Linux

Ubuntu spirit is dead. This is why:

Please read the title of this thread: "Why BROKEN 7.04 is still distributed?!". It is not: "could someone help me finding workaround for "/bin/sh:..." bug?". It is not true that many people responded: indeed many many reacted, but of topic. Nobody responded with explanation: WHO decided to release broken distribution? WHY such decision was made? Is the same person (people) concerned now? Obviously not, read the Home page, everyone is happy and congratulates themselves. I know, this is not the right forum to discuss this -- but there is no right forum or email address, I failed to find it. Maybe we now have different communities: "them" and "us", one with Ubuntu spirit, one commercial? This is what I found frustrated, not the fact that a piece of software is buggy.

No point in appending more info to the bug 96084 report: for months it is dormant, and remains classified as "severity: medium". I also asked there: why is it "medium" not the highest, who decides that, what are the criteria? No response. I will keep checking from time to time, but for me something died in Ubuntu spirit, it became just the same as others. Actually probably less -- I am not aware of any other software developer deciding to release a new self booting distribution knowing that it boots for less people then the previous distribution did.

Thank you again all for your responses, 8.0 six months from now will probably fix it for those who will stay with Ubuntu.

cheers, derek.

The new ubuntu 7.04 Fesity fawn CD's are not working properly on my PC.Whenever i insert the cd into my pc cd rom then chooose the option "start or install ubuntu" then a bar travelling for little moment comes appear on the screen and the an error messege comes
(BusyBox error ,can't acess tty, /bin/sh..

please help me if any one fix this problem

Hello M.Salman,

I am sorry but I don't think anybody there can give you a solution. What I can tell you is that this is a known bug reported several times. But so far I haven't not seen anyone that can provide a solution solving my case. I am having the same issue than you on my laptop Samsung X10. Like most of the person that have reported this bug my laptop was working fine with the liveCD 6.10.

The root cause of this seems to come from the customisation done by Ubuntu on top of the kernel. At least this was the conclusion of that bug report: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/96084
This affects all the sister distro : kubuntu, xubuntu, ...

I hope that save you the time I spent trying to get 7.04 installed on my laptop.