This bug, due in very large part to the huge amount of comments it has
received, is no longer useful at all from a bug fix standpoint. As such,
I am marking this bug Won't Fix.
There are plenty of detailed logs in the comments (including my own)
that are presented to help fix this long-standing
@Pi - without more information, we can only cluck sympathetically.
Please attach the results of lspci -vvnn and lsusb - and tell us the
result of trying the workarounds described above.
Newer kernels have unmodularised ehci_hcd so it cannot be removed.
You don't really want to remove it because
You can also right-click on the bottom pixel of the panel - that works.
--
Adding an applet to the Gnome panel
https://bugs.launchpad.net/bugs/424890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I bumped into this bug - actually
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/105938 (marked as a
dup of this).
I found a workaround - which I document here for others.
The problem is not xdmcp - the problem is a failing dns lookup of the
hostname of the machine.
I configured dnsmasq on
I have found that most of my problems have cleared up by doing the
following :-
1. Adding the following to /etc/initramfs-tools/modules :-
ohci_hcd
ehci_hcd
2. Rebuilding the initramfs by running 'update-initramfs'
3. Reboot.
This (I believe) ensures the modules are loaded in the right order
Mike's solution in
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/500
(Change load order in initrd image) did indeed fix it for me. I rebuilt
the initrd for my kernel.
Using Intrepid, 2.6.27-9-generic,
ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card
Ugh. I spoke too soon. I had ehci blacklisted. In summary, unplugging
the Alcor Flash reader allows me to keep ehci, but leaving it in causes
reset high speed USB device events.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug
davotibarna,
Please run the command 'lspci -vvnn lspci-vvnn.log' and attach the
resulting file 'lspci-vvnn.log' to this bug report.
Do you have any USB 1.X devices or hubs ? The solution for me
(documented above) was to unplug the USB multi-card reader thing from my
computer. I did not have to
Public bug reported:
Binary package hint: slapd
Using Intrepid Ubuntu 8.10, slapd 2.4.11-0ubuntu6
Steps to reproduce bug :-
* Take a properly constituted ldap database, with an index on uid - index uid
eq and containing user fred
* stop slapd - /etc/init.d/slapd stop
* Remove index uid eq
Public bug reported:
Binary package hint: slapd
Using Intrepid Ubuntu 8.10, slapd 2.4.11-0ubuntu6
Steps to reproduce bug :-
* Take a properly constituted ldap database, with an index on uid - index uid
eq and containing user fred
* stop slapd - /etc/init.d/slapd stop
* Remove index uid eq
David, please attach lspci -vvnn and lsusb. Do you have an Alcor chipset
? can you unplug it and try again ?
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have a feeling there are two different bugs here. All these filesystem
comments, and echo 64 /sys/block/sdh/queue/max_sectors_kb make no
sense to me, as often the device (/dev/sdh or whatever) has not even
come up.
I tried formatting my USB stick as ext2 - but it makes no difference.
As
I have a brand new machine, with Intrepid installed on it. My hardware
combination triggers this bug.
After reading this thread, and many others similar to it, I have
narrowed my problem down to the boot time interaction of ehci_hcd and my
Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card
MountainX, do you have any USB 1.X devices plugged in, like my card
reader ? Can you live without them ? What does lsusb say ?
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: system-config-printer-gnome
python /usr/share/system-config-printer/system-config-printer.py in a
terminal reports :-
ValueError: unknown locale: en_NG
LANG=C python /usr/share/system-config-printer/system-config-printer.py
works.
Launchpad said this
gotcha re: --mirror option, I missed that. I have re-installed, but
cannot repeat my initial install error. Sorry.
--
ltsp-build-client requires 'net access to run
https://bugs.launchpad.net/bugs/205466
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: ltsp-server
Ubuntu: Hardy 8.04 Beta.
ltsp-server: 5.0.40~bzr20080212-0ubuntu3
I have a boot server, and an application server, which is my LDM_SERVER.
I need to extract the ssh pub keys of the application server and put them in
Public bug reported:
Binary package hint: ltsp-server
Hardy beta release
Description:Ubuntu hardy (development branch)
Release:8.04
ltsp-server:
Installed: 5.0.40~bzr20080212-0ubuntu3
Candidate: 5.0.40~bzr20080212-0ubuntu3
Version table:
*** 5.0.40~bzr20080212-0ubuntu3 0
This bug occurred when the machine had an IP address from DHCP, but no
default route.
With a statically configured network, it succeeded.
--
ltsp-build-client requires 'net access to run
https://bugs.launchpad.net/bugs/205466
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Using Etherboot 5.0.8 ROMs, and tftp logging cranked up, I see this in
the logs :-
Jan 7 15:13:52 zululand in.tftpd[23913]: RRQ from 172.20.1.158 filename
/ltsp/i386/nbi.img
Jan 7 15:14:19 zululand in.tftpd[23920]: RRQ from 172.20.1.158 filename
/lts.conf
Jan 7 15:14:19
SZABO Zsolt's patch to $client/usr/share/ldm/rc.d/S20-delayed-mounter
and /usr/sbin/ltspfsmounter should be implemented.
It is an arbitrary and hard-to-find bug to NOT be able to use ssh -X to
the server - and Seriously Ugly.
Andy
--
Local devices don't work because an X11 authentication
Yes, it is quite likely I changed the path.
Perhaps this should be a feature request instead - that if the path is
changed, that the directory is created ?
--
Lock directory not created in startup script
https://bugs.launchpad.net/bugs/84692
You received this bug notification because you are a
/etc/apcupsd/apcupsd.conf has a line (line 72 in my copy)
# LOCKFILE path to lockfile
# Path for device lock file.
LOCKFILE /var/lock/apcupsd
I believe the lock is used to police access to the USB port to the UPS.
--
Lock directory not created in startup script
Public bug reported:
Binary package hint: apcupsd
apcupsd 3.12.1-1 (dapper current)
Add the following line to /etc/init.d/apcupsd :-
if [ `pidof apcupsd` = ]
then
+ install -o root -g root -m 755 -d /var/lock/apcupsd
24 matches
Mail list logo
