As of 10/30/2006 the problem still exists in Kubuntu 6.06 and in Kubuntu
6.10.
The workaround suggested by Brian Fitzgerald and Alain R. did not work
for me.
In either case Kubuntu claims that the 'mount point /dev/fd0 does not
exist.
My workaround for Kubuntu 6.06 follows the latest suggestion
Kubuntu 6.10 has wireless work flawlessly after initial installation.
It gets lost after several boot sequences.
The workarounds suggested above did not work in my case.
I have Kubuntu 6.06 installed on the same computer. I therefore copied
the contents of /etc/networks/interfaces from Kubuntu
Modified 6.10 the same way. It works. I now have the icon and read/write
access to my floppy drive in 6.06 and 6.10.
--
media:/ does not handle floppy mounting correctly
https://launchpad.net/bugs/30207
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
I can now confirm that my workaround posted on 11/01/06 does indeed work
for my installation of Kubuntu 6.10. I have been using the modified
'interfaces' file since then and performed a great number of cold boots
as well as regular boot sequences.
The computer boots with the wireless connection
I know and I am using linux-2.6.20 in several incarnations.
All of them have unstable wireless connections.
Wireless is difficult to get started and even more difficult to keep
'alive' over an extended period of time.
And it is not signal strength.
Brian Murray wrote:
** Changed in:
I did that. It worked for a while and then quit.
Impossible to do it again because I cannot connect to the Net.
Only 6.06 still has wireless going.
Andrew Ash wrote:
Try the info at : https://help.ubuntu.com/community/KeepingUbuntuUpdated
--
wireless assistant does not connect in edgy
NonfreeKernelModules: ath_hal
Package: prismstumbler 0.7.3-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/psfront
ProcCwd: /home/pjj
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: prismstumbler
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/8319701/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/8319702/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/8319703/Disassembly.txt
** Attachment
' when switching to a sub-forum.
The first URL does not produce the error. It also retains the user
name/login name.
The URL with 'www' has the problem.
--- On Mon, 9/15/08, PJJ [EMAIL PROTECTED] wrote:
From: PJJ [EMAIL PROTECTED]
Subject: Re: [Bug 269632] Re: Login reverts back to 'guest' when
in to Kubuntu Forums.
Login to Kubuntu forum is successful. Shows me logged in correctly.
Instead whenever I enter one of the forums for Kubuntu 8.10 after a
successful login to the main forum screen, my status reverts back to
guest.
Login as member 'pjj' is lost.
** Affects: ubuntu
Importance
Firefox 3.0.1 (2?)
--- On Sat, 9/13/08, David D Lowe [EMAIL PROTECTED] wrote:
From: David D Lowe [EMAIL PROTECTED]
Subject: [Bug 269632] Re: Login reverts back to 'guest' when opening forum
To: [EMAIL PROTECTED]
Date: Saturday, September 13, 2008, 1:11 PM
Which browser did you use?
**
Indeed it is FF 3.0.2.
And the error still occurs.
--- On Sat, 9/13/08, David D Lowe [EMAIL PROTECTED] wrote:
From: David D Lowe [EMAIL PROTECTED]
Subject: [Bug 269632] Re: Login reverts back to 'guest' when opening forum
To: [EMAIL PROTECTED]
Date: Saturday, September 13, 2008, 1:11 PM
Replies in order of questions posed:
Yes
Yes, FF only
Yes
No, 8.04 works just fine.
[EMAIL PROTECTED]:~$ apt-cache policy firefox
firefox:
Installed: 3.0.2+build3+nobinonly-0ubuntu2
Candidate: 3.0.2+build3+nobinonly-0ubuntu2
Version table:
*** 3.0.2+build3+nobinonly-0ubuntu2 0
There was one person who said they also experienced this problem.
Guess I either erased the e-mail or it is related to Bug 253224 because the
sender said he also has the problem.
Anyway, it appears to be fixed.
At least it worked this morning.
--- On Mon, 9/15/08, David D Lowe [EMAIL
I hate to tell you: It hapened again.
Login to main forum menu is successful.
Move to 8.10, network forum, etc. results in: Welcome Guest.
So whatever causes the problem, it is back.
--- On Mon, 9/15/08, PJJ [EMAIL PROTECTED] wrote:
From: PJJ [EMAIL PROTECTED]
Subject: Re: [Bug 269632] Re
Thank you for the instructions. I suspected something like that.
Meanwhile, I have first removed the update to 2.6.17-11. Then installed
the restricted modules and reinstalled the update. Things are working again.
Thanks for your help.
Peter
PS: I noticed in the forum that other people
Original Message
Subject:Re: [Bug 84641] Re: Wireless card (Atheros) no longer detected
after upgrade to kernel 2.6.17-11
Date: Wed, 28 Feb 2007 06:10:48 -
From: PJJ [EMAIL PROTECTED]
Reply-To: Bug 84641 [EMAIL PROTECTED]
To: [EMAIL PROTECTED
The information you requested is in the attachment. Kernel version according to
boot screen is:
a. 2.6.17-10 generic (working network)
b. 2.6.17-11 generic (no network).
Strange thing is:
Both versions lead to the same desktop and file system. Any saved file, e-mail
or other material created
Here are the answers to your questions.
Kernel 2.6.17-11- generic:
Adept says:
linux-restricted-modules-generic
Not installed
linux-restricted-modules-2.6.17-11-generic
Not installed
Command line:
sudo modprobe ath_pci
FATAL: Module ath_pci not found.
Konqueror
Corrections to above post:
1. Under kernel 2.6.17-10-generic
Konqueror
Disregard remark no madwifi sub-directory'.
Only second statement is correct.
2. Disregard or delete text of Stephen Drake's e-mail.
How in the world does one correct/edit a post?
I could not find a way of
Here is the clean version:
Here are the answers to your questions.
Kernel 2.6.17-11- generic:
Adept says:
linux-restricted-modules-generic
Not installed
linux-restricted-modules-2.6.17-11-generic
Not installed
Command line:
sudo modprobe ath_pci
FATAL: Module ath_pci not found.
Konqueror
Public bug reported:
Prompted by Adept Package Updater I upgraded a number of packages. Did
not pay too much attention to package information details. However, I
noticed two references to kernel (headers?) 2.6.17-11.
Upgrade/update completed successfully. On the next re-boot
KNetworkmanager
Added repository and updated wlassistant as suggested.
Rebooted.
Wireless working; wlassistant shows active connection.
However, I cannot tell whether this is a result of the update. Most
recently, my wireless access has worked again reliably at each and every
reboot.
I will disconnect now and
Disconnected active connection.
Reconnected repeatedly and successfully to access point with MANUAL SETTINGS.
Attempts to reconnect to a different access point (set to automatic)
repeatedly failed.
Manual works, automatic (DHCP) most likely not.
Furthermore: Upon manual reconnection the
Further to the comment of M. Torres and pursuant to my remarks: I should have
kept my mouth shut.
Everything worked fine until I posted my last confirmation of the workaround.
Trouble started thereafter.
I still get connected over 95% of the time on booting up. However, if I
work too many
None of the 'fixes' and workarounds work reliably, including mine.
On booting the connection is established and works for a while but then decides
to quit.
Once that happens, I can restore it sometimes using one or the other of the
suggested solution.
Simply re-booting appears to be the best of
Where is the list and how does one get to it?
--
Thunderbird uses konqueror as web browser
https://launchpad.net/bugs/52670
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Finally some very good news indeed.
Now a question from a non-programmer and Linux -Wannabe:
How does one apply this patch to an existing 6.10 installation?
I know the very basics of Unix/Linux but my 'Unix for Dummies' says
nothing about applying a patch and debdiffs!
--
wireless assisant
I just attempted to execute mrl586's workaround.
It did not work for me.
The install script terminated with two errors because of dangling links:
background.pnp
and background-1920-1200.png
Fix was attempted from inside 10.04, recovery mode, Konsole, following
mrl586 instructions step by
29 matches
Mail list logo
