I have a customer with a laptop from Linuxemporium, with ubuntu pre-installed. I think it is gutsy, but will have to confirm that. She is using a wireless network (WPA-PSK), with broadband connection.
The problem is with online updates. When logged in, a message informing of new updates is shown. If accepted, the list of headers downloads correctly. But, on clicking install, nothing happens.
If I try running apt-get update / upgrade, update works fine, but upgrade reports that resource [ESSID xxxx} could not be accessed.
However, if I run apt-get from an SSH login, or a virtual terminal, everything work fine.
Any ideas what could be wrong - is there a configuration file for the updater that could be wrong.
On Tue, 2008-08-05 at 16:00 +0100, Stuart Bailey wrote:
If I try running apt-get update / upgrade, update works fine, but upgrade reports that resource [ESSID xxxx} could not be accessed.
However, if I run apt-get from an SSH login, or a virtual terminal, everything work fine.
Sorry Stuart you lost me here, can you clarify when an apt-get upgrade works ?
Are you saying that if you log in to the box you can upgrade the packages but if you try and do it locally you can't ?
Hi Wayne, It seems I can only upgrade when either SSH'd in remotely, or when using a virtual terminal (text). If I use synaptic (I think) or run apt-get from an xterm, it fails.
I hope that clarifies things.
I expect the config for synaptic is wrong, but I'm not too familiar with ubuntu.
Many thanks,
Stuart
On Tue, 2008-08-05 at 16:00 +0100, Stuart Bailey wrote:
If I try running apt-get update / upgrade, update works fine, but upgrade reports that resource [ESSID xxxx} could not be accessed.
However, if I run apt-get from an SSH login, or a virtual terminal, everything work fine.
Sorry Stuart you lost me here, can you clarify when an apt-get upgrade works ?
Are you saying that if you log in to the box you can upgrade the packages but if you try and do it locally you can't ?
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Stuart
This problem has been reported in a number of places. I'm using 8.04 on one machine and was using 7.10 on another.
On the 7.10 pc I installed another desktop environment, had problems and removed it, and then found the update manager didn't work correctly. Somehow a setting was altered or a glitch/bug unveiled. The update manager doesn't find updates but aptitude does!
8.04 works fine on the other pc and i use aptitude all the time as it is a high level package manager compared with apt-get or synaptic.
Most problems one has are the result of something that has been done after the install. All you can do is reinstall... well that's what i've found. Your customer isn't going to remember what they did most likely and it'll take too long to figure out. I'm just about to replace the 7.10 pc with 8.04.
I know that doesn't help much but it's not a problem with ubuntu as a fresh install.
james
2008/8/6 stuart@linusoft.co.uk:
Hi Wayne, It seems I can only upgrade when either SSH'd in remotely, or when using a virtual terminal (text). If I use synaptic (I think) or run apt-get from an xterm, it fails.
I hope that clarifies things.
I expect the config for synaptic is wrong, but I'm not too familiar with ubuntu.
Many thanks,
Stuart
On Tue, 2008-08-05 at 16:00 +0100, Stuart Bailey wrote:
If I try running apt-get update / upgrade, update works fine, but upgrade reports that resource [ESSID xxxx} could not be accessed.
However, if I run apt-get from an SSH login, or a virtual terminal, everything work fine.
Sorry Stuart you lost me here, can you clarify when an apt-get upgrade works ?
Are you saying that if you log in to the box you can upgrade the packages but if you try and do it locally you can't ?
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Thu, 2008-08-07 at 06:49 +0100, James Freer wrote:
Most problems one has are the result of something that has been done after the install. All you can do is reinstall... well that's what i've found. Your customer isn't going to remember what they did most likely and it'll take too long to figure out.
But then how do you ever learn how to fix things when re-installation isn't really a practical solution ?
Even with windows systems are reinstalled to solve problems more frequently than need be, with *nix about the only time you "need" to think about reinstalling is if you know/suspect the box has been compromised (i.e. a root kit)
If this problem is common then there will be a solution, however I am not convinced that the problem you are talking about is the same as what Stuart is experiencing. Do you have any links ?
Wayne
Not sure i quite follow what you're trying to convey?
"But then how do you ever learn how to fix things when re-installation isn't really a practical solution ?" imho that is determined by time and cost - if you can fix a problem in 1 hours workshop time then maybe worth it. Perhaps you have the ability to spend a week rewriting and compiling some glitch... perhaps someone would pay you to do that. Re-install and job done in an hour at no cost!
I did a quick search on Ubuntu and Kubuntu forums and there a numerous problems concerning updating which he probably had a look at and no doubt didn't find what he wanted. More time and money! I'm busy rebuilding an engine and gearbox at present.
Solution - new today 8.04 has a new update manager... maybe.
james
2008/8/7 Wayne Stallwood ALUGlist@digimatic.co.uk:
On Thu, 2008-08-07 at 06:49 +0100, James Freer wrote:
Most problems one has are the result of something that has been done after the install. All you can do is reinstall... well that's what i've found. Your customer isn't going to remember what they did most likely and it'll take too long to figure out.
But then how do you ever learn how to fix things when re-installation isn't really a practical solution ?
Even with windows systems are reinstalled to solve problems more frequently than need be, with *nix about the only time you "need" to think about reinstalling is if you know/suspect the box has been compromised (i.e. a root kit)
If this problem is common then there will be a solution, however I am not convinced that the problem you are talking about is the same as what Stuart is experiencing. Do you have any links ?
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Mon, 2008-08-11 at 20:36 +0100, James Freer wrote:
Wayne
Not sure i quite follow what you're trying to convey?
"But then how do you ever learn how to fix things when re-installation isn't really a practical solution ?" imho that is determined by time and cost - if you can fix a problem in 1 hours workshop time then maybe worth it. Perhaps you have the ability to spend a week rewriting and compiling some glitch... perhaps someone would pay you to do that. Re-install and job done in an hour at no cost!
Yes the investment in time researching a solution is reasonable the first time you encounter a problem but if you just reinstall when you hit a glitch then you have two problems.
a. You cannot be sure you won't just run into the same problem again b. If you do you won't know how to fix it and it is quite likely that once you know what to do the fix is quicker than re-installation.
Now I would agree that some computer problems are not worth fixing but that is generally only when the fix is labour intensive each time you do it or you cannot be sure to have completely "fixed" the problem (i.e. in the case of a heavily compromised machine) But from what you say this sounds like it is more of a bug, and if so it most likely has a fix or workaround that is far quicker than reinstalling your operating system so the investment in time to discover that if it is as common as you suggest is worthwhile no ?
As to whether it would take me a week of "writing and compiling" that I cannot answer as I am still not sure what the problem is you are referring to. Can you give me some links ?
I'd be interested to see a widespread issue relating to ubuntu updates and/or apt do you have a launchpad id or something I can work from ?
-
James Freer -
Stuart Bailey -
stuart＠linusoft.co.uk
-
Wayne Stallwood