Comment 42 for bug 294667

Hi there,

do you know how to add numbers to the comments in the launchpad gui? I had to count the permalinks in a text editor. Anyway,

The difference between comment 34 and 35 is:

lbm_cw_cfg80211

Are you annoyed by the amount of data? Sorry about that, I am just trying to help in debugging. What do you suggest?

Anyway,

I had some rather atypical stuff happening. Since I only use wireless through the Intel wireless card and 3 USB modem (which I am using right now) I could not connect to the internet for a while. I mistakenly judged that this bug was fixed as adding the backports and doing modprobe after 'root# dpkg-reconfigure linux-backports-modules-2.6.27-8-generic' did reveal the symbols errors, but did not make my wifi connection disappear. That happened only after rebooting, and is still not fixed yet.

In contrast with the last time I experienced this bug, and also had the connectivity issues, I cannot restore this with '$ sudo apt-get remove linux-backports-modules-2.6.27-8-generic'. Maybe this is because apt-get build-dep linux-backports-modules-2.6.27-8-generic prompted me to install linux-headers-2.6.27-10-server, which I did. I have since removed both packages and ran root# dpkg-reconfigure -au. I have deconf configured to readline and -p low.

I will search for other 2.6.27-10-server packages now and try to uninstall/delete them.

I have just downloaded a lot of dbgsym's and will try to get a Backtrace of sudo nm-connection-editor. I get WARNING: resetting 'something' with page size more than zero is deprecated. Also one of the build-dep's of network-manager network-manager-gnome or gnome-keyring was automake1.9 I believe.

This package is known to cause problems with installing build-dep's for virtualbox-ose. The problem is that there is specifically referred to automake 1.9 and not 'any automake'. I think installing backports may actually refer to this previous automake, and some program will not be able to use a later version of automake instead of that program.

I think that program is gnome-keyring or gnome-keyring-daemon. I know this because I had 'sudo NetworkManager' access to gnome-keyring made subject to a password, which is my old gnome-session (and sudo) password. I changed this login password, but I still had to give in the old password for access to the gnome-keyring for NetworkManager, after startup. I can now start both NetworkManager and gnome-keyring, as well as nm-applet, dbus-launch, nm-connection-editor and gnome-keyring-daemon. I am no longer prompted for my old password however. I think that is ample proof.

Anyway, I also got the compiz.real bug again, which is still related to the Alsa mixer I see, but that is possibly not causally related to this bug (but maybe also to automake?).

Please pardon me also for the referral to the UFW kernel crash bug. I saw the same output in dmesg in Intrepid, but not in Jaunty. I guess it is unrelated.

Cheers,

Thomas