[Expired for udev (Ubuntu) because there has been no activity for 60
days.]
** Changed in: udev (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/469376
Hello all,
I can confirm that this modem causes a system freeze in Lucid.
As an experiment, I backported modem-manager from Maverick into Lucid,
with no other changes (it was a rather trivial backport).
After doing so, I am able to insert the modem without any issues.
--
USB device insertion
This is bizarre.
I did a fresh install of Lucid 10.04.1 onto a netbook, then plugged in
my Option modem (0af0:d033).
I confirm that it caused my system to lock up.
I just spent the past 4 hours trying to bisect this issue, and I can't
get it to fail reliably.
In my bisection adventure, I found
Can you run apport-collect 469376 in a terminal?
** Package changed: ubuntu = udev (Ubuntu)
** Changed in: udev (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: modemmanager
Status: New = Invalid
** Changed in: hotplug
Status: Confirmed = Incomplete
** Changed in:
OK, I finally got a chance to try 10.04 and I confirm the lockup still
exists.However, the error you report is easily resolved, you missed
one rather poorly documented step.
Use The Synaptic Package Manager to verify you do not have the default
hsolink package loaded.
Also remember
sudo
I have not tried 10.04 yet, but probably will in the next week or so.
If I had to guess right now I suspect what you are experiencing is an
artifact of the somewhat publicized Ubuntu elimination of HAL in 10.04.
In 10.04 Ubuntu totally eliminated the Hardware Abstraction Layer (HAL).
The
The problem still exists with Lucid 10.4 ... In fact, I couldn't install
the HSO stuff after the clean install. I had to install 9.10 then do an
upgrade to 10.4 ... when connecting now, I get a message that says not
installed properly -- no internet control but I can still get online.
(I'm using
Not resolved, but we have isolated the cause to Gnome Network Manager
and Modem Manager, and we do have a workaround.
As a workaround you can go to the following URL
http://www.pharscape.org/Quicksilver.html
There are three packages you will need to download from the Pharscape
site.Don't
I am Jeff, and my email is mountainho...@yahoo.com. I have a compaq
presario r3000 series laptop, the usb internet stick named in this
issue, and I am a newbie.
When I place this stick in, Ubuntu 9.10 locks up solid, and I am forced
to power down to get a reboot.
Has this issue been resolved ?
Well, I tried Pat's solution again, and succeeded. The only wrinkle is
that once connected, Firefox and Evolution will not connect to the
internet unless started with sudo. So I used Authorizations to give
myself implicit authorization.
Do you know where the problem is?
Curt
--
USB device
Curt:
Don't know about Evolution because I use Mozilla Thunderbird, but if I
had to guess, I would almost be willing to bet this will be what you are
looking for, at least from your description of the problem.
Potential fix ===
1) Launch
Pat,
I remember having a ton of DNS issues for a while (they're all cleared
up, but for the life of me I wouldn't be able to tell you how), and
all the resolv.conf stuff sounds all too familiar. I use static DNS
(OpenDNS is a good DNS server, Google has a DNS server too) and I
haven't had any
I have the same problem, and would greatly appreciate a solution.
I tried Pat's suggestions in note 8 above, and had to re-install the
whole system.
Curt Johnston
--
USB device insertion causes total system lockup on Ubuntu 9.10
https://bugs.launchpad.net/bugs/469376
You received this bug
Curt, I wish I had a solution for you. Pat's workaround was successful
for me. In fact, I'm using the Quicksilver connection right now to
send this.
Ideally, it would seem to me that the GNOME folks would see what's
different between GNOME's tools (network-manager and modem-manager)
and wicd,
Thank you for posting the workaround. I've added the workaround to a
question I had regarding the exact same issue (#91686) and have marked
it solved, even though technically it isn't solved since the answer is a
rather involved workaround. There must not be enough Quicksilver/Ubuntu
users for
Is anyone going to work this?
USB causes Kernel failure?
--
USB device insertion causes total system lockup on Ubuntu 9.10
https://bugs.launchpad.net/bugs/469376
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I reported this problem quite some time ago, and considering it causes a
total system lockup, I am surprised I cannot seem get anyone interested
to actually do anything to get this fixed, but I have now confirmed what
is actually happening.
In a nutshell, when the USB subsystem detects the
As a workaround you can go to the following URL
http://www.pharscape.org/Quicksilver.html
There are three packages you will need to download from the Pharscape
site.Don't build/install then yet, just find and download them to a
directory on your system for now.
1) ozerocdoff (
Finally some progress, I can stop the act of inserting the ATT Quicksilver in
the USB port from locking the system,
and I may have just isolated what is really causing the lockup under Ubuntu
9.10.
Go ahead download, build and install the Ozerocdoff package from
A photo of the contents of /var/log/syslog that were visible on the
screen after the system crashed when inserting the ATT Quicksilver into
my Dell running Ubuntu 9.10 updated on 11/15/09
** Attachment added: 100_0715.JPG
http://launchpadlibrarian.net/35731863/100_0715.JPG
--
USB device
Today I updated to the latest udev patch offered by Update Manager,
still no joy consistently locks system when inserting this USB device.
ID 0af0:d033 Option
** Changed in: udev
Status: New = Confirmed
** Changed in: hotplug
Status: New = Confirmed
** Changed in: ubuntu
Finally got a chance to come back to this. After swapping in a freshly wiped
disk ( mke2fs -c -c ), I then did a total clean default Ubuntu 9.10 Desktop
i386 install.So I am absolutely sure I am starting with a totally clean
base. I wanted this because the two systems I worked with
I have pretty much come to the conclusion this is a udev problem.The
only way the hso driver could have been called into play to replace SCSI
emulation for USB on the ZeroCD is via a udev action, and this udev
action is clearly where the breakage is located.
Done properly the ZeroCD in the
23 matches
Mail list logo
