Doug Engert wrote:
>The real fix is to get the gnutls people to support certificate
>directories, like OpenSSL. Why the rush to convert to gnutls
>when it has so many issues. (Licencing issues are low on my list of
>reasons.)
Indeed, for a security tool you want a package written by experienced
s
So despite the broad cross-section of drivers being affected, Dan
Williams on the networkmanager team still thinks this is a driver bug,
and still thinks that periodic scanning is a good thing (completely
ignoring the network lag it causes whenever a scan is done). See his
followup:
http://mail.gn
I have a similar problem, right now my pidgin's virtual size is over
25GB and still growing. Of course the real memory used isn't anywhere
near that (and I only have 4GB on this laptop anyway).
top - 16:29:17 up 2 days, 18:09, 9 users, load average: 0.18, 0.29, 0.34
Tasks: 152 total, 3 running
I have a similar problem, right now my pidgin's virtual size is over
25GB and still growing. Of course the real memory used isn't anywhere
near that (and I only have 4GB on this laptop anyway).
top - 16:29:17 up 2 days, 18:09, 9 users, load average: 0.18, 0.29, 0.34
Tasks: 152 total, 3 running
Alex - this patch turns off scans while an A/B/G card is associated to
an AP. That means whatever was in the scan list when the connection was
started is all that the nm-applet (or the nm=-ool) will show you, for
the duration of that association - it won't update by itself. Of course,
a superuser c
>> If you're in an environment with overlapping coverage from multiple
APs, and you're walking around from one area to > another, you may lose
connectivity until you manually rescan.
>At least we should take care that the scanning starts again after
association/connection is lost. I haven't check
>Regardless of whether I am connected or not, when I open the NM menu to see
>broadcast networks, it is going to have to scan then, right?
No. Opening the menu only shows you the results of the last scan,
whenever that was. It doesn't initiate a scan.
>So if that scan causes me to temporarily los
>> No. Opening the menu only shows you the results of the last scan,
whenever that was. It doesn't initiate a scan.
>But the problem is that you cannot look in the menu to connect to a new AP
>because that list is outdated or non-existing.
>This feels kind of a regression to me.
The list will be
I have the same behavior on my Asus M6Ne with Mobility 9700 Radeon.
xrandr -q says S-video disconnected even though it's actually connected.
I've tried on both the Intrepid 8.10 LiveCD and a recent Jaunty 9.04
beta.
** Attachment added: "Xorg.0.lo"
http://launchpadlibrarian.net/25724765/Xorg.0
lspci -vvnn output
** Attachment added: "pci.txt"
http://launchpadlibrarian.net/25724791/pci.txt
--
xrandr not detecting S-Video connection
https://bugs.launchpad.net/bugs/318184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Using the --set command from jcdutton's comment works; xrandr then
reports that the S-video is connected. I can then use the Display tool
to enable the display and extend my desktop onto it. But the TV display
starts out with a hash; you can see ghosts of the main laptop display
sprayed across it a
I'd forgotten this bug report was here. I found that reverting this
patch fixed it for me (ath9k)
commit 98f392b085985a75274fe02ec8aa92f4ac0d8a80
Author: Dan Williams
Date: Sat Oct 11 18:32:24 2008 +
2008-10-11 Dan Williams
* src/nm-device-wifi.c
- (can_
Here's the git diff
** Attachment added: "Restore madwifi hack"
http://launchpadlibrarian.net/25829754/dif.txt
--
network-manager roams to (none) ((none))
https://bugs.launchpad.net/bugs/291760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Interesting. Is that WPA with a Pre-Shared Key? I use WPA/EAP and
obviously had the problem. Haven't tried WPA2 at all.
--
network-manager roams to (none) ((none))
https://bugs.launchpad.net/bugs/291760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
My mistake. ALSA appears to work fine if I disable pulseaudio.
--
ALSA audio broken in current 8.10 beta
https://bugs.launchpad.net/bugs/281536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Public bug reported:
When used in the upcoming OpenLDAP 2.4.12 release, db-4.7 will deadlock
in its default configuration on single-core machines. The default
configuration on multi-core machines works fine, and it's simple to
configure on single-core to avoid the deadlock. This is a bug in
Berkel
What "these kind" ? Provide a stack trace.
--
[SRU] (ITS#5518) Assertion error in io.c:234: ber_flush2
https://bugs.launchpad.net/bugs/215904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Public bug reported:
Cyrus SASL's sasl_set_mutex() API will allows multiple callers to reset
its state, so mutexes created earlier may not be usable after a
subsequent call. This problem is discussed here
http://asg.andrew.cmu.edu/archive/message.php?mailbox=archive.cyrus-
sasl&msg=8954
and a fi
Public bug reported:
Binary package hint: alsa-base
I hadn't installed any updates in 5-6 days. After installing a round of
new updates last night the audio on my HP dv5z laptop stopped working.
It doesn't appear to be a kernel driver issue; I had been running my own
build of 2.6.27final before a
** Bug watch added: Email to [EMAIL PROTECTED] #
mailto:[EMAIL PROTECTED]
** Also affects: network-manager via
mailto:[EMAIL PROTECTED]
Importance: Undecided
Status: New
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/192643
Y
Just a few comments on prioritizing this wishlist item - I think using
this feature should be the default on any desktop install; using dnsmasq
improves all name resolver lookup response times, and by eliminating
rewrites to /etc/resolv.conf it makes it a lot easier to run a secure
system with a re
If you're referring to Gnome bug 551747, yes, I submitted that bug
report and patch, but it appears to have received no attention upstream
yet.
For the reasons I already listed in my previous comment, resolvconf is a
poor solution. I already tried using it here; it still rewrites the disk
too freq
In frame 3, can you please print *sb, and in frame 4, print *ld, print
*lr and attach the info here, thanks.
** Summary changed:
- Assertion error in io.c:234: ber_flush2
+ (ITS#5519) Assertion error in io.c:234: ber_flush2
** Summary changed:
- (ITS#5519) Assertion error in io.c:234: ber_flush
Yes, that helps. Please also print *lc from frame 4, thanks.
--
(ITS#5518) Assertion error in io.c:234: ber_flush2
https://bugs.launchpad.net/bugs/215904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Hmmm, *lc is completely bogus. 7f3a11313ab0 is clearly in the text
segment of the process, and the values starting from lconn_sasl_sockctx
are ASCII:
00: 6d 70 2f 6f 70 65 6e 6c 64 61 70 32 2e 34 2e 37 mp/openldap2.4.7
01: 2f 6c 69 62 72 61 72 69 65 73 2f 6c 69 62 6c 62 /libraries/liblb
Thanks for the report, a patch for this (ITS#5526) is now in OpenLDAP's
CVS HEAD for testing.
--
dnPrettyNormal: Assertion `pretty != ((void *)0)' failed.
https://bugs.launchpad.net/bugs/234196
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Please test this patch and let me know if you can still reproduce this
failure.
http://www.openldap.org/lists/openldap-commit/200805/msg00112.html
--
(ITS#5518) Assertion error in io.c:234: ber_flush2
https://bugs.launchpad.net/bugs/215904
You received this bug notification because you are a me
I don't see a crash with stock 2.4.7 or 2.4.9. Please provide the actual
slapd.conf used to reproduce this bug, and the stack trace for the
crash.
** Summary changed:
- slapd segfaults when using dynlist
+ (ITS#5527) slapd segfaults when using dynlist
--
(ITS#5527) slapd segfaults when using dy
Thanks for catching that. Should also be fixed in OpenLDAP CVS now.
--
dnPrettyNormal: Assertion `pretty != ((void *)0)' failed.
https://bugs.launchpad.net/bugs/234196
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Thanks for this. I see it crashing in 2.4.7 but not in 2.4.9.
--
(ITS#5527) slapd segfaults when using dynlist
https://bugs.launchpad.net/bugs/218734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Actually Paul, your last comment regarding the bug status here was that
you'd be testing, but you hadn't actually posted a confirmation that
your problem was resolved.
And MikMak still hasn't provided any further details on whatever crash
he's still seeing. So while I'm certain that the patch is c
This should probably be filed upstream so it can be handled as a
Documentation bug there.
Note that there are only 3 main debug flags used in the libraries and
command line tools - 1, 2, and 16. The rest are only used by slapd. 16
isn't all that useful if you already have 2 set.
--
debuglevels a
I've been having this problem as well, on Intrepid but with my own build
of 2.6.28.6 kernel and ath9k driver, and NetworkManager from SVN. Fairly
certain this was not occurring with an older SVN update but I'd have to
dig up my backup disk to check the revision that was working before.
--
network
Just to be explicit - like clockwork:
tail /var/log/syslog
Mar 1 14:47:29 violino NetworkManager: [1235947649.095987]
periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:26:56:10
(HighlandSun)
Mar 1 14:48:46 violino dhclient: DHCPREQUEST of 192.168.1.20 on wlan0 to
192.168.1.7
Ah, I forgot that NetworkManager migrated from SVN to git; the SVN tree
I was looking at was old. Last updated 2008-10-22. My git tree was last
updated 2008-12-27 and doesn't appear to have the problem now.
--
network-manager roams to (none) ((none))
https://bugs.launchpad.net/bugs/291760
You r
libldap is now patched in OpenLDAP cvs HEAD. We anticipate releasing a
bugfix-only 2.4.16 release very soon, with this fix included.
--
gnutls regression: failure in certificate chain validation
https://bugs.launchpad.net/bugs/305264
You received this bug notification because you are a member of
Mathias, in regards to the wiki you linked above, my preference when
debugging these issues is to recommend debug level 7, which includes
packet traces, instead of debug 1. It's much better (to me) to be able
to see all the traffic, which includes the raw transfer of certificates
and their DER DNs,
I've also run into this problem a few times. I set my laptop's 1680x1050
display to 640x480 to try to watch a video, since there was no Xv
support for this video card and the image was too small at native
resolution. I was unable to get back to the original resolution after I
finished watching the
This missing feature in NetworkManager was really annoying me so I wrote a
patch for it, which you can find here
http://mail.gnome.org/archives/networkmanager-list/2008-September/msg00042.html
--
dnsmasq with enable-dbus doesn't work properly with NetworkManager
https://bugs.launchpad.net/bugs/1
Public bug reported:
This bug was reported as OpenLDAP ITS#6252 against Ubuntu Jaunty. It
occurs in all revisions since GnuTLS 2.4.2, I have not checked anything
older. It causes certificates with XMPP subjectAltNames to fail to match
with a spurious SHORT_BUFFER error, because libgnutls overwrite
I've filed this report in the GnuTLS tracker as well
https://savannah.gnu.org/support/index.php?106975
launchpad doesn't seem to recognize Savannah, so I couldn't link it
directly.
--
GnuTLS subjectAltName parsing is broken
https://bugs.launchpad.net/bugs/412774
You received this bug notificati
Public bug reported:
Binary package hint: ubuntu-docs
On this page
https://help.ubuntu.com/8.10/serverguide/C/openldap-server.html
In the steps for adding schema - we do not recommend editing or
referencing the slapd.d ldif files. These are after all internal files
of a slapd backend, they are
Ryan, of course you still have to edit the dn/cn, that's step 4. I
didn't say to drop step 4, only to perform it on the output of slapcat
instead of directly editing a slapd internal file.
--
OpenLDAP doc page, schema config
https://bugs.launchpad.net/bugs/416520
You received this bug notificatio
Just noting for posterity, as of GnuTLS 2.8.0 (released 2009-05-27) you
can use %VERIFY_ALLOW_X509_V1_CA_CRT in the TLSCipherSuite options to
enable V1 CA certs. I will probably #ifdef the current OpenLDAP patch to
turn it off for GnuTLS >= 2.8.0. (Haven't decided on best course of
action yet, give
** Tags added: apport-collected
** Description changed:
When wpa_supplicant is spawned by DBUS it doesn't open any other control
interfaces, so you can no longer use wpa_cli to talk to it. Please consider
adding something like the patch here to re-enable wpa_cli support.
http://w1.fi/b
By the way, if you apply the wpasupplicant patch I referenced in
bug#549269 you can then do manual scans with wpa_cli without interfering
with network-manager. (The feature is already in upstream wpasupplicant
0.7.x so upgrading that would work too.) With easy mechanisms for manual
scanning, there'
That's unfortunate, I didn't realize libpam-ldapd was so incomplete. You
can still use nssov for full pam support.
Your best option for an immediate fix is still the libgcrypt patch I
posted. Without that basically all Karmic and Lucid nss-ldap+SSL
installations are dead in the water. As a longer
http://www.openldap.org/devel/cvsweb.cgi/~checkout~/contrib/slapd-
modules/nssov/README?rev=1.11
It's an overlay for OpenLDAP slapd which implements all of the nss and
pam calls, replacing Arthur deJong's nslcd.
--
NSS using LDAP+SSL breaks setuid applications like su and sudo
https://bugs.launc
I read all of the diffs between 1.4.1 and 1.4.4 but didn't find any
likely suspects. However, tracing the library initialization in gdb, I
found the specific problem.
Ordinarily gnutls will initialize the gcrypt library, if no app has done
so already. In the gnutls initialization, it specifically
Probably the best fix: don't call global_init when setting the thread
callbacks.
** Attachment added: "potential libgcrypt fix"
http://launchpadlibrarian.net/45701569/dif1.txt
--
NSS using LDAP on Karmic breaks 'su' and 'sudo'
https://bugs.launchpad.net/bugs/423252
You received this bug notif
Potential gnutls fix: do gcrypt initialization as long it isn't already
finished. probably a bad idea.
** Attachment added: "potential gnutls fix"
http://launchpadlibrarian.net/45701794/dif2.txt
--
NSS using LDAP on Karmic breaks 'su' and 'sudo'
https://bugs.launchpad.net/bugs/423252
You rece
Rune: just google for nscd problems, it has a long history of stability
issues. But on top of the issues caused by poor implementation, it also
has problems due to an inherently inadequate design. Some of these
issues are outlined in my LDAPCon presentation linked above. All of this
is well documen
There are a number of bug reports for NM already. You can start with
this
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/291760
and the subsequent Gnome bug report
https://bugzilla.gnome.org/show_bug.cgi?id=580185
I provided a patch to remove the offending background scanning behavior
in
** Also affects: linux via
https://bugzilla.gnome.org/show_bug.cgi?id=580185
Importance: Unknown
Status: Unknown
--
network-manager roams to (none) ((none)) - background scanning
https://bugs.launchpad.net/bugs/291760
You received this bug notification because you are a member of Ubu
That was explained in one of the previous discussions. The ath9k is an
a/b/g/n interface and has a lot more channels to scan, and it's the
extra time required to scan these additional channels that causes the
association to time out. Or that's the theory anyway; the ath9k driver
seems to still have
@Kunal,
Yes, scanning is required to find a network to connect to, when you initially
have no connection at all. My point is that once you're successfully associated
to a network, automatic/background scanning should stop. You don't need
scanning to happen any more unless the environment changes
I have a number of machines that all have different problems which require
custom DSDTs. With the latest kernels none of these machines work any more. 1)
An Asus A8V-Deluxe Socket 939 motherboard with Opteron 185 CPU. Asus stopped
providing updated BIOS images for this machine years ago, and it
Ok, so after the patch was removed from 2.6.25 in February 2008, it was
fixed and reposted in July 2008 http://lkml.org/lkml/2008/7/21/338 but
there were no further followups. What happened?
--
[karmic] 2.6.31 kernel does not load custom DSDT
https://bugs.launchpad.net/bugs/395239
You received th
I'm hitting the same problem now, having just updated to Lucid Alpha 2
from Karmic. Unfortunately, my libdrm-radeon1 is already at the correct
version and the problem persists. objdump -T confirms that
/usr/lib/libdrm_radeon.so.1 exports radeon_cs_create but I'm still
getting this error. Quite puz
Never mind me I found an old libdrm in /lib. Deleting that fixed the
issue.
--
xserver-xorg-video-radeon has insufficient (even missing) dependency on
libdrm-radeon1
https://bugs.launchpad.net/bugs/507618
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Fixed in CVS slapd/bconfig.c 1.402
--
[karmic] slapd hangs at 100% cpu and is unkillable
https://bugs.launchpad.net/bugs/485026
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
Another possible solution would be just to add a mechanism to
NetworkManager (and the applet) to explicitly inform it of the existence
of a connected interface. I'm using adb from the Android SDK to start a
ppp session with my G1 phone, and ppp0 comes online with no trouble but
NetworkManager doesn
On a slightly related note - I have a number of status update daemons on
my network that send status updates using UDP broadcast. They generally
only broadcast each update packet once. (UPS monitoring, a few other
misc things.) With NetworkManager doing its periodic scans, these UDP
broadcast packe
One more request - if you're not going to integrate the custom DSDT
patch, please provide a .deb package for your kernel build tree with all
.o files intact. Then we can insert our own DSDT.hex and rebuild without
having to spend hours recompiling the entire kernel. This is getting to
be a real pai
Great find, Andreas. So gnutls is calling gcrypt's secure memory
functions. And yet, the gnutls docs say these functions are not used by
default, and certainly OpenLDAP does not configure gnutls to use them.
Something else in the stack must be setting that behavior.
--
NSS using LDAP on Karmic br
Regardless of what the root cause turns out to be, you guys really need
to switch to libnss-ldapd, which will reliably isolate the user apps
from whatever junk is going on inside libldap / gnutls / whatever. (And
if you're not using the latest version, which also handles pam_ldap,
then you need to
You can find detailed design docs at its home page
http://arthurdejong.org/nss-pam-ldapd/
You can also find my LDAPCon2009 presentation on the subject here
http://www.symas.com/ldapcon2009/papers/hyc1.shtml
--
NSS using LDAP on Karmic breaks 'su' and 'sudo'
https://bugs.launchpad.net/bugs/423252
I'd be happy to write a patch for the documentation. And given all of
the problems with the design (and implementation) of libnss-ldap, I'd
say any analysis will show that libnss-ldapd is still the path of lowest
risk and greatest stability. (In particular, when used with OpenLDAP
nssov.)
--
NSS
Right, given the timing for the Lucid release it's probably way too
late. I can't comment on your experience with nslcd as I have never used
its code or read it in depth. The stub library and nssov have been
pretty well tested internally in Symas; since the stub library is almost
entirely cookie-cu
Looking at the gcrypt code, it seems this bug should be reported against
that; this whole secmem implementation (1) requires a program to be
started as root (setuid) and (2) always drops the root priv when it has
initialized its secure memory. These behaviors would certainly interfere
with any setu
his page
http://www.broadcom.com/support/802.11/linux_sta.php
linux-wlan-client-support-l...@broadcom.com
but received no acknowledgement. Which I believe is the usual result from
reporting driver bugs to vendors...
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director
re: Filing bugs against the kernel - that's only reasonable when there
is in fact a kernel bug. There are plenty of ACPI bugs that cannot be
labeled as kernel bugs, or fixed by other kernel patches. E.g. the new
AMD-based Lenovo Thinkpads are *missing* the PSS tables, because Lenovo
simply released
Yes, I'm using a compiled-in DSDT now but it's a PITA to have to
recompile it with every kernel update. (Echoing a previous request - if
this is going to be the standard "solution" then you guys need to
provide a kernel package that contains a kernel build tree with .o files
ready to be linked, so
I just updated to the current Lucid beta on a new Dell Precision M4400
laptop with Broadcom BCM4322 wifi, and network-manager-0.8, the problem
is even worse now.
Mar 26 18:03:04 violino NetworkManager: [1269651784.005430]
periodic_update(): Roamed from BSSID 00:12:17:26:56:10 (HighlandSun) to (n
Public bug reported:
When wpa_supplicant is spawned by DBUS it doesn't open any other control
interfaces, so you can no longer use wpa_cli to talk to it. Please consider
adding something like the patch here to re-enable wpa_cli support.
http://w1.fi/bugz/show_bug.cgi?id=335
(Note - this feature
Also note - without a working wpa_cli it's a lot harder to diagnose
problems such as https://bugs.launchpad.net/bugs/291760 ...
--
WPA supplicant control interface fix
https://bugs.launchpad.net/bugs/549269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I just got a Thinkpad Edge yesterday and installed 10.04 beta1 x64 on
it. Out of the box the driver was only seeing 1 unencrypted network. I
grabbed the latest realtek driver and then was able to see the other
networks (my own is WPA/Enterprise). After I deleted the original driver
(from /lib/modul
Where's the changelog, was there even any related change in that kernel
update?
I've switched to 2.6.32-rc3 built directly from kernel.org source. The
ath9k driver appears to work a lot better there, but the kernel crashes
on me. I'm guessing the crashes are related to the ATI r600 KMS support
tho
Another "me too" on Jaunty but with 2.6.31-rc9. Switching to current
wireless-testing driver is even worse. Stability on ath9k has gone done
continuously since 2.6.31. I don't have any 2.6.30 builds but the last
kernel that worked half-decently for me with this wifi driver was
2.6.29.
--
ath9k di
>With the backports I see no more than 3% packet loss while I was
transfering 7,5GB of data with the speed of 21mbps.
>When the 3% packet loss happens I see on my syslog this message:
>wpa_supplicant[1297]: CTRL-EVEN-SCAN-RESULTS
That's caused by NetworkManager's background scanning. If you run
Running a current wireless-testing, it appears that commit c93f7c14
fixes a lot of the random disconnects for me. But I still get hangs
under sustained transfers, with the "DMA failed to stop" message in the
kernel log.
--
ath9k disassociates/reassociates a lot
https://bugs.launchpad.net/bugs/414
Public bug reported:
I filed this bug and a patch upstream already but the patch has been
ignored. It's getting pretty annoying having to fix this manually all
the time.
The VT100 command sequences CSI ? 47l (switch to primary screen) and CSI
? 47h (switch to alternate screen) are supposed to be
** Attachment added: "Trivial fix"
http://launchpadlibrarian.net/33779026/dif
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33779027/Dependencies.txt
** Bug watch added: GNOME Bug Tracker #591648
https://bugzilla.gnome.org/show_bug.cgi?id=591648
** Also affects:
Actually I was referring to Bug #414560
However now that you mention it, I've seen the symptoms described here
as well. My guess is these are caused by the same bug.
--
ath9k - nm-applet don't connect to any network after 2 hours (+-)
https://bugs.launchpad.net/bugs/439723
You received this bug
Note - I've killed NetworkManager and the issue still remains. This is
an ath9k driver bug, not a NetworkManager bug.
Sep 30 23:15:11 violino kernel: [329813.143845] wlan0: no probe response from
AP 00:12:17:26:56:10 - disassociating
Sep 30 23:15:17 violino kernel: [329818.803730] wlan0: authenti
Even with current wireless-testing the same problems remain, they just
occur less frequently now.
Sep 30 22:39:52 violino kernel: [327694.163945] wlan0: authenticate with AP
00:12:17:26:56:10
Sep 30 22:39:53 violino kernel: [327694.360741] wlan0: authenticate with AP
00:12:17:26:56:10
Sep 30 22:
That's right. I've also tried ath9k drivers from wireless-testing up to
2009-09-23. There hasn't been anything newer for ath9k that I'm aware
of.
Possibly there are two bugs at work in this bug report. The
NetworkManager background scanning issue also had an extremely bad
effect on the ath9k stabi
I've been running without NetworkManager and just with manually
configured wpa_supplicant; the disconnects and performance issue still
remain. But NetworkManager aggravates the situation, which is why I now
disable it. (I described the other issue with NetworkManager in bug
439723)
--
ath9k disas
I got sick of NetworkManager taking away control here, so I wrote this
patch
http://hostap.epitest.fi/bugz/show_bug.cgi?id=335
It restores access to the wpa_supplicant using the normal control
interface, even with the DBUS interface active. This allows tools like
wpa_cli and python wpa_ctrl to ke
Public bug reported:
These days a typical flash drive has much larger capacity than a typical
OS iso image. It's a shame to waste all the extra space just to load a
single OS image. It would be nice to add an option to copy the OS image
to a specific partition of the flash drive instead. I've been
I think we can close this out, we were able to reproduce the issue
without kvm. Sorry for the false alarm.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
** Changed in: openldap (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openldap (Ubuntu)
Status: Invali
Just to note - in OpenLDAP 2.5, which is currently being released, we've
added symbol versioning to libldap and liblber, so mixing of libraries
should no longer be a problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
Running a continuous stream of operations against OpenLDAP slapd
eventually causes a SEGV in liblber, in a segment of code that cannot
fail:
gdb /opt/symas/lib64/slapd CoreDump
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
Li
** Package changed: ubuntu => kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749247
Title:
Spurious SEGV running inside kvm
To manage notifications about this bug go to:
https://bugs.l
Will try to come up with a minimal reproducer. Currently it takes
several hours to run the complete test, and a few hours before the SEGV
occurs. But the stack trace is always identical when it happens. In
multiple runs, it always succeeds on the host and always fails in the
VM.
--
You received t
3 sets of LDAP client libraries? That sounds like a terrible solution.
Fwiw, I wrote a version of OpenLDAP's TLS support that could use any/all
of OpenSSL, GnuTLS, and MozillaNSS simultaneously, and never released
it, because it seemed that would be too confusing if separate apps had
different exp
My point being, if you want to accommodate multiple TLS libraries
simultaneously with only a single libldap, that code is still available
in the OpenLDAP git repo. The relevant changes are between
a225b02f17fe79f6680d5d31db37320981e24774..4dff3e6807fb3451405373c2b85e02ccf27b882f
--
You received t
** Bug watch added: Debian Bug tracker #663195
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663195
** Also affects: pidgin (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663195
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
For completeness' sake, another bug tracker with the same issue
https://bugs.g10code.com/gnupg/issue1181
** Bug watch added: GnuPG Bugs #1181
https://bugs.g10code.com/gnupg/issue1181
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As I noted in our ITS#8025, this has nothing to do with upstream
OpenLDAP. It may be specific to the particular way you built OpenLDAP in
your distro, or it may be due to pam_ldap itself, but neither of these
are in the purview of the OpenLDAP Project. Certainly there is nothing
in vanilla OpenLDAP
1 - 100 of 119 matches
Mail list logo
