Hi,
I am also affected by this problem. It is an overflow check
using undefined behavior in an overflow check in test.c
that looks like "if (pe + SPINSZ > pe && pe != 0)"
but with >4G memory pe + SIINSZ wraps around.
I think the most simple fix would be the follo
Public bug reported:
grub-common 2.04-1ubuntu26.7 installs two handlers which run in
parallel:
/lib/systemd/system/grub-initrd-fallback.service
which does:
ExecStart=/usr/bin/grub-editenv /boot/grub/grubenv unset initrdfail
ExecStart=/usr/bin/grub-editenv /boot/grub/grubenv unset prev_entry
and
*** This bug is a duplicate of bug 1910815 ***
https://bugs.launchpad.net/bugs/1910815
** This bug has been marked a duplicate of bug 1910815
race on boot between multiple invocations of grub-editenv
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
here is the latest network-manager patch for 14.04
** Patch added: "updated network-manager patch for ubuntu 14.04"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1181964/+attachment/4523005/+files/network-manager-wifi-fix.diff
--
You received this bug notification because yo
Status update
finally I was able to fix this issue upstream see:
https://bugzilla.gnome.org/show_bug.cgi?id=733105
But it is only completely fixed in network-manager 1.0
If you want to fix something for ubuntu 12.04 or ubuntu 14.04
you can use my latest local patches.
Note: that in ubuntu 14.04
This is a wpa_supplicant fix that was found upstreams.
It is only necessary for ubuntu 14.04.
The wpa_supplicant from ubuntu 12.04 did not try to
do an internal scan for the AP, and does not need any fix.
** Patch added: "wpa-wifi-scan-fix.diff"
https://bugs.launchpad.net/ubuntu/+source/netwo
Public bug reported:
If the Access point is rebooted, Linux wont re-connect.
That behaviour is reproducable with the -43 Kernel version.
Only way to re-connect is disable & enable Wireless connection or reboot.
Previous version, -41 and -39 did automatically re-connect after a few
seconds.
Probl
This is the Log file from yesterday, where I tried to reboot the Access point
several time.
Later tries were successful, but I switched back to previous kernel versions
-41 at 18:20 and following
** Attachment added: "Syslog from yesterday, look at Time index May 19 13:14:05
where Access point
Ok, I installed the following kernel: linux-image-3.2.45-030245-generic-
pae_3.2.45-030245.201305140735_i386.deb
This bug is definitely fixed with this image:
A short disconnect (reboot AP) => network re-connects immediately.
A long disconnect (1 minute power-off AP) => network re-connects after 5
Oops, sorry...
A few hours later the bug showed up again -- in the upstream kernel,
without me trying to reproduce it.
The traces in the event at time index 43224.360095 look very similar to the -43
kernel.
[43223.763471] wlan0: authenticate with 00:13:49:e3:9d:8e (try 1)
[43223.960105] wlan0: a
Hello,
unforutnately, I must admit, that I am no longer able to reproduce this
bug here.
what I did was compile & install a locally generated test kernel over the
3.2.0-43 and later
re-install the 3.2.0-43 kernel from the .deb file in /var/cache/apt/archives
and, guess: now the network connects
PING...
this patch did run non-stop for 6 weeks now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181964
Title:
Wireless connection does not re-connect
To manage notifications about this bug go
Now it did happen again. The Network Manager traces show the Access point has a
short interruption,
and access point is removed from the Network List, only one other AP in the
list, but the data is wrong:
ap_list_dump() does not show the same data than "iwlist wlan0 scanning".
=> therefore it se
OK, when you look at nm-device-wifi.c I think I see what is wrong:
When the AP is almost always sending its beacons, but reboots quickly at some
point in time, it can be
deleted by cull_scan_list() if it is scheduled exactly at the second because it
is not the active AP, and the list entry
was
I am pretty sure that this is a network manager bug, and how to solve
it.
** Package changed: linux (Ubuntu) => network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181964
Title:
I compiled the network-manager component as follows:
cd network-manager-0.9.4.0
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--enable-more-warnings=no
make
installed (as root): src/.libs/NetworkManager to
/usr/sbin/NetworkManager (renamed original NetworkManager for possible
Yes, it is a patch.
Steps to reproduce:
- configure a permanent connection to a WEP-encrypted AP.
- the AP has very good signal quality, and is 99.9% of the time available.
- only sporadic short 1-2 seconds interruptions of the beacon.
- one or two other APs have very poor signal quality, and ent
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181964
Title:
Wireless connection does not re-connect
To manage notific
18 matches
Mail list logo
