Caroline
I have a feeling that your device has a firmware that doesn't cause hal
to do the hundreds of disconnect/connects when it's attached (see the
last 8 or so comments on
https://bugzilla.redhat.com/show_bug.cgi?id=253096). While I completely
agree with you that "if it ain't broke then don't
Probably just as well. I just noticed that I bumped the wrong value
(MAX_FILE_NAMELEN instead of FD_ALLOC_BLOCK) in my debdiff.
Any chance the upstream patch will make it into hardy?
--
rpc.gssd FD_ALLOC_BLOCK too low
https://bugs.launchpad.net/bugs/191872
You received this bug notification beca
Public bug reported:
rpc_pipefs is usually mounted on /var/lib/nfs/rpc_pipefs and is used for
kernel<->userspace communication for nfs. mlocate most likely shouldn't
go digging around there.
** Affects: mlocate (Ubuntu)
Importance: Undecided
Status: New
--
rpc_pipefs should be in
debdiff attached.
** Attachment added: "debdiff to add rpc_pipefs to PRUNEFS"
http://launchpadlibrarian.net/12128428/mlocate_rpc_pipefs.debdiff
--
rpc_pipefs should be in the PRUNEFS list
https://bugs.launchpad.net/bugs/193920
You received this bug notification because you are a member of Ubu
Right, because drivers/usb/storage/initializers.c now does what huaweiAktBbo.c
was previously required to do.
Sadly, my modem is not Just Working with wvdial, unless I modify initializers.c
per the patch in my previous comment.
--
HUAWEI E220 no longer works in Feisty
https://bugs.launchpad.net
huaweiAktBbo.c sends a zero-sized message when initializing the device, while
usb_stor_huawei_e220_init in drivers/usb/storage/initializers.c does not. By
changing the call to usb_stor_control_msg() to mimic the huaweiAktBbo's call to
usb_control_msg(), the device works flawlessly every time.
I'
** Changed in: hal-info (Ubuntu)
Sourcepackagename: None => hal-info
** Changed in: hal-info (Ubuntu)
Status: Invalid => New
--
HUAWEI E220 no longer works in Feisty
https://bugs.launchpad.net/bugs/105545
You received this bug notification because you are a member of Ubuntu
Bugs, which is
"- If I shut down hal, the device works."
To clarify, I need to stop hal before I plug the device in.
--
HUAWEI E220 no longer works in Feisty
https://bugs.launchpad.net/bugs/105545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
I did some more digging through this:
- If I shut down hal, the device works.
- If I don't, sometimes it works, but usually uhci_hcd decides to do a reset of
some kind. This has the unfortunate side effect of making the usb modem go away
completely.
- If I tell hal to ignore the device by modifyi
This appears to work as expected.
--
[hardy] regression: kernel requires pci=bfsort on dell poweredge 2950
https://bugs.launchpad.net/bugs/181239
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
debdiff attached.
** Attachment added: "Patch to up FD_ALLOC_BLOCK in rpc.gssd"
http://launchpadlibrarian.net/11961434/nfs-utils-fd-alloc-block.debdiff
--
rpc.gssd FD_ALLOC_BLOCK too low
https://bugs.launchpad.net/bugs/191872
You received this bug notification because you are a member of Ubun
Public bug reported:
The max number of sec=krb5 mounts that rpc.gssd will handle is hardcoded at 32.
From utils/gssd/gssd.h:
#define FD_ALLOC_BLOCK 32
This causes problems and errors like:
RPC: AUTH_GSS upcall timed out.
when the number of kerberized nfs mounts approaches the hard limi
Public bug reported:
auth-client-config chokes if a config contains the '%' character, causing some
configuration to fail, e.g.
account sufficient pam_krb5.so ccache=/var/run/ccache/krb5cc_%u
** Affects: auth-client-config (Ubuntu)
Importance: Undecided
Status: New
--
auth-cli
Forgot the traceback.
[EMAIL PROTECTED]:~(0)$ auth-client-config --help
Traceback (most recent call last):
File "/usr/sbin/auth-client-config", line 957, in
opts = process_args()
File "/usr/sbin/auth-client-config", line 776, in process_args
profiles = getProfileNames()
File "/usr/s
Public bug reported:
Every time autofs mounts a new nfs volume, the volume appears on my
desktop and nautilus immediately opens a window. Finding my desktop
swamped with over 50 (and counting) automounted volumes and a nautilus
window for each one is somewhat annoying. There should at least be an
Public bug reported:
In gutsy, the installer kernel would correctly identify the network cards on a
Dell PE 2950 in the correct order - i.e. eth0 would correspond to the first NIC
as the BIOS saw it and eth1 would correspond to the second.
In hardy alpha2 the kernel is identifying the onboard NI
Patch to udev-108 to remove references from rules.d/40-permissions.rules.
Please apply this minorly trivial fix to udev.
Seriously, why has this bug been in this state for a year? If I'm making a
change to several thousand machines so that they boot correctly, it leaves the
realm of 'trivial to
No, it fixes the symptoms. The problem (referenced local groups are not
present) still exists.
--
40-permissions.rules includes non-existent groups
https://launchpad.net/bugs/38203
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: debian-installer
If I have a device that uses usb-storage attached to my machine during the
install, usb-storage claims sda before the sata modules. On reboot, the sata
modules are included in the initramfs which means the first disk is detected as
sda
Ping?
This is actually a serious problem. I really don't like it when a lot of
machines try to mount, read and access several thousand home directories
whenever their users unlock their screensavers, especially when the network in
question is pretty large and distributed.This places unnecessary
OK, this bug is bogus. The cause of this was me only preseeding
d-i passwd/[value]
and not
passwd passwd/[value]
Any chance of making debconf inherit some values from d-i in the future?
--
user-setup insists on creating a user
https://launchpad.net/bugs/53656
--
ubuntu-bugs mailing list
ubuntu
Public bug reported:
Binary package hint: user-setup
user-setup insists that I create a user in spite of me setting the
following preseed options:
d-i passwd/root-passwordpassword test
d-i passwd/root-password-again password test
d-i passwd/root-login boolean true
No idea but it's not on any of the machines I have here, and have polled
some friends about it.
--
40-permissions.rules incorrectly has an nvram group
https://launchpad.net/bugs/51340
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
While I'm at it, my /etc/nsswitch.conf contains this:
passwd: files ldap
shadow: files ldap
group: files ldap
i.e. check files for users and groups first, then fall back to ldap. The
nvram group doesn't exist locally so ldap is tried next.
--
40-permissions.rules incorrectly has an
My system does not have an nvram group. Nor does any other dapper box
I've used. I have not modified /etc/{passwd,shadow}, this group is
incorrectly referenced in 40-permissions.rules and beacuse of this nss
attempts to look for the group in ldap before the network has been
configured and introduce
Public bug reported:
Binary package hint: udev
As summary. The presence of this group is fine unless nsswitch is set to
fetch users/groups from ldap. Then it takes a good 2 minutes for a
machine to boot while it tries to contact an ldap server before the
network is up.
** Affects: udev (Ubuntu)
26 matches
Mail list logo
