Dear Mr Thomas, The point is that it usually does not produce any information other than a failure of the USC software to load with a break down. When a breakdown occurs, I usually get it to report to Launchpad if it deigns to, using the apport programme. Is that it?
Now this started nearly a month ago. What I do when I get this sort of problem is sidefile all my files, save them on a USB (or two), chck that the sidefile has worked. Then do a clean reinstall. I do have other machines but I am so happy with the way Ubuntu works (I am not in a production envieronment) that I am willing to risk things going wrong, and this is what I have been doing since 11.04 alpha 2. This is really the only problem I have had ! It is a bit of a B*. I don't think it can be me. I am using a standard laptop Sony Vaio VPECH1SOE. I have never heard of a hardware fault that one remarkably ordinary programme causes this sort of problem, and if it is hardware, I think I can check that out, as I have another Sony Vaio to hand, a dual boot though, so the test will not be quite identical. I shall run what hardwre tests I can on my Vaio (this one - the white one) and the other the black. I shall report back what I find. If it is not my hardware, I cannot understand why you cannot reproduce it. But, I don't think, if the problem is in USC (and I am not the only person who has had some issues, I believe) that Ubuntu 12.10 could be released. Perhaps there are other machines with hardware faults similar to mine who are having this issue. But I am not enough of a programmer to be able to help you much. My thanks for your interest. Charles Norrie On 30 August 2012 09:49, Matthew Paul Thomas <[email protected]> wrote: > Sorry, but without any information on what the problem is, let alone how > to reproduce it, there's nothing we can do here. > > If you are doing "sudo apt-get update" and "sudo apt-get upgrade" from a > Terminal, this almost certainly isn't a problem with USC in the first > place. If it printed an error message, then copy the error message and > paste it into the bug report. > > ** Package changed: software-center (Ubuntu) => apt (Ubuntu) > > ** Changed in: apt (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1043596 > > Title: > The usual software center updater problem encountered > > Status in “apt” package in Ubuntu: > Incomplete > > Bug description: > This is the same old software center updater bug, but Launchpad has > not identified USC as one of the possibilities, ao I've had to repoty > thi as a new bug. I am finding Launchpad a delicate beast to learn. > > All I was doing was the daily sudo apt-get update and sude apt-bet > upgrade and all goes along spiffingly until Ubuntu tells me it wants > to reprt a system oroblem. And so, fudge, honest, it just broke in mt > hands and I have no more information other than you've got. It's a > real nasty isn't it. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1043596/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043596 Title: The usual software center updater problem encountered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1043596/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
