I wonder if the AP uses the same BSSID for each SSID.  Right now the driver
filters "networks" based on unique BSSIDs.  Perhaps the logic should be changed
to create unique AP entries for every combination provided and only expire based
on vs. whenever a new beacon is provided w/ the same BSSID.

I don't know what BSSID is vs ESSID. I do know that the Windows driver for the
ipw2200 works, as does the Cisco 350 and Proxim based cards under Linux.

Do you have a test patch I could could use to test your theory?

I tried ipw2200 v0.9 but it didn't work. I'm very willing to test any patches or
provide debug that you request.

This post on the mailing list says that this problem doesn't exist with the
current 2100.

http://article.gmane.org/gmane.linux.drivers.ipw2100.devel/2480

I tried with 0.10. No difference, still broken.

Here are more datapoints, I hope it helps.

Here is the output from iwconfig ethX after loading the driver, and running:

iwconfig eth1 ESSID <snipped-my-real-ESSID>
iwconfig eth1 enc <snipped-my-real-key> open

eth1      unassociated  ESSID:"<snipped>"  Nickname:"mentorng.gurulabs.com"
          Mode:Managed  Channel=0  Access Point: 00:00:00:00:00:00
          Bit Rate=0kb/s
          RTS thr:off
          Encryption key:<my-key-snipped>   Security mode:open
          Power Management:off

Now if I force the frequency, something interesting happens:

iwconfig eth1 freq 2.442GHz; iwconfig eth1

eth1      unassociated  ESSID:"<snipped>"  Nickname:"mentorng.gurulabs.com"
          Mode:Managed  Frequency=2.442GHz  Access Point: 02:0E:35:86:A2:7F
          Bit Rate=0kb/s
          RTS thr:off
          Encryption key:<my-key-snipped>   Security mode:open
          Power Management:off

The MAC address of the access point shows up for a second!! However, it is still
"unassociated".

If I wait a second, the MAC address of the access point goes away:

iwconfig eth1
eth1      unassociated  ESSID:"<snipped>"  Nickname:"mentorng.gurulabs.com"
          Mode:Managed  Frequency=2.442GHz  Access Point: 00:00:00:00:00:00
          Bit Rate=0kb/s
          RTS thr:off
          Encryption key:<my-key-snipped>   Security mode:open
          Power Management:off

With the 0.10 driver, I've enabling scanning and association debug. Here is what
I see first:

Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 1
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 2
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 3
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 4
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 5
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 6
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 7
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 8
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 9
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 10
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 11
Sep 30 13:22:08 mentorng kernel: ipw2200: I ipw_rx_notification Scan completed:
type 11, 11 channels, 1 status
Sep 30 13:22:08 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered'
excluded because of privacy mismatch: on != off.
Sep 30 13:22:08 mentorng kernel: ipw2200: U ipw_best_network Network
'OpenInternet' excluded because of privacy mismatch: on != off.

Then when I force the frequency, the ESSID I want shows up on channel 7.

Sep 30 13:22:11 mentorng kernel: ipw2200: U ipw_associate Assocation attempt:
'<snipped-my-ESSID>', channel 7, 802.11g [12].
Sep 30 13:22:11 mentorng kernel: ipw2200: I ipw_rx_notification disassociated:
'<snipped-my-ESSID>' 02:0e:35:39:a2:79

Note that my access point only supports "802.11b", NOT 'g'.

Then I start gettings lots of these messages:

Sep 30 13:22:12 mentorng kernel: ipw2200: U ipw_best_network Network
'<snipped-my-ESSID>' excluded due to capability mismatch.

] Sep 30 13:22:12 mentorng kernel: ipw2200: U ipw_best_network Network
] '<snipped-my-ESSID>' excluded due to capability mismatch.

:)  There's a bug in 0.10 where if you try and associate with an ESSID that it
doesn't know about, and you provide the channel, it tries to create an Ad-Hoc
network (even if in Managed mode).  These messages are the driver saying it
can't associate with that new network.

] Network 'Empowered' excluded because of privacy mismatch: on != off.
] Network 'OpenInternet' excluded because of privacy mismatch: on != off.

I assume neither of these is the network you are trying to associate with?

James

]:)  There's a bug in 0.10 where if you try and associate with an ESSID that it
]doesn't know about, and you provide the channel, it tries to create an Ad-Hoc
]network (even if in Managed mode).  These messages are the driver saying it
]can't associate with that new network.

OK. Those messages only show up after I force the frequency, which I shouldn't
have to do, it was just something I was trying.

] I assume neither of these is the network you are trying to associate with?

Correct, I don't want to connect to those ones. The "OpenInternet" is one of the
other two ESSIDs on my AP.

It has OpenInternet (wide open, no wep), and two others that don't broadcast the
ESSID and have different security settings.

The 'Empowered' network is somebody else in the building.

I tried v0.11 no change. I turn on debug for scanning and assoc, but I see zero
messages related.

Here is what I see:

Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 1
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 2
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 3
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 4
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 5
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 6
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 7
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 8
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 9
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 10
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 11
Sep 30 20:37:57 mentorng kernel: ipw2200: I ipw_rx_notification Scan completed:
type 11, 11 channels, 1 status
Sep 30 20:37:57 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered'
excluded because of privacy mismatch: on != off.
Sep 30 20:37:57 mentorng kernel: ipw2200: U ipw_best_network Network
'OpenInternet' excluded because of privacy mismatch: on != off.

There is another report on the mailing of this same problem:

"ipw2200 0.11, Two ESSIDs same AP, one open one with WEP key, can't connect to
the WEP network"

http://article.gmane.org/gmane.linux.drivers.ipw2100.devel/2575

I tried with v0.12, but same results. The debug output didn't change:

Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 1
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 2
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 3
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 4
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 5
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 6
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 7
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 8
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 9
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 10
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 11
Oct 14 09:53:18 mentorng kernel: ipw2200: I ipw_rx_notification Scan completed:
type 11, 11 channels, 1 status
Oct 14 09:53:18 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered
(00:a0:c5:3a:5d:aa)' excluded because of privacy mismatch: on != off.
Oct 14 09:53:18 mentorng kernel: ipw2200: U ipw_best_network Network
'OpenInternet (00:02:8a:0e:39:0c)' excluded because of privacy mismatch: on != off.

'Empowered' is somebody else in the building, the 'OpenInternet' is the network
on my access point that I DON'T want to to connect to.

Then I tried to force the channel with the command:

# iwconfig eth1 freq 2.442GHz

Now the debug says:

Oct 14 09:53:34 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered
(00:a0:c5:3a:5d:aa)' excluded because of channel mismatch: 1 != 7.
Oct 14 09:53:34 mentorng kernel: ipw2200: U ipw_best_network Network
'OpenInternet (00:02:8a:0e:39:0c)' excluded because of channel mismatch: 11 != 7.

Created an attachment (id=48) [details]
Changes method in which hidden networks are identified and associated.

Can you try the attached patch against 0.12 and see if it corrects the problems
being encountered?  It corrects a bug with how association occurs with hidden
networks.

I applied the patch on top of 0.12. 

It *seemed* as if it worked. I was associated, WOOHOO!

Then I rebooted, and I can't associate anymore.

But then...after about 10mins, I'm associated again!!

Here are the log messages...

Oct 14 19:38:30 mentorng kernel: ieee80211_crypt: registered algorithm 'NULL'
Oct 14 19:38:31 mentorng kernel: ieee80211_crypt: registered algorithm 'WEP'
Oct 14 19:38:31 mentorng kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915
Network Driver, 0.12
Oct 14 19:38:31 mentorng kernel: ipw2200: Copyright(c) 2003-2004 Intel Corporation
Oct 14 19:38:31 mentorng kernel: ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 11
(level, low) -> IRQ 11
Oct 14 19:38:31 mentorng kernel: ipw2200: Detected Intel PRO/Wireless 2200BG
Network Connection
Oct 14 19:38:31 mentorng kernel: divert: allocating divert_blk for eth1
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 1
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 2
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 3
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 4
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 5
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 6
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 7
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 8
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 9
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 10
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 11
Oct 14 19:38:31 mentorng kernel: ipw2200: I ipw_rx_notification Scan completed:
type 11, 11 channels, 1 status
Oct 14 19:38:31 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered
(00:a0:c5:3a:5d:aa)' excluded because of privacy mismatch: on != off.
Oct 14 19:38:31 mentorng kernel: ipw2200: U ipw_best_network Network
'OpenInternet (00:02:8a:0e:39:0c)' excluded because of privacy mismatch: on != off.

...(5 minutes go by with the same messages)....

Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 1
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 2
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 3
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 4
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 5
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 6
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 7
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 8
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 9
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 10
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 11
Oct 14 19:43:48 mentorng kernel: ipw2200: I ipw_rx_notification Scan completed:
type 11, 11 channels, 1 status
Oct 14 19:43:48 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered
(00:a0:c5:3a:5d:aa)' excluded because of privacy mismatch: on != off.
Oct 14 19:43:48 mentorng kernel: ipw2200: U ipw_best_network Network
'OpenInternet (00:02:8a:0e:39:0c)' excluded because of privacy mismatch: on != off.

...still no go, but 5 seconds later....

Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 1
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 2
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 3
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 4
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 5
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 6
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 7
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 8
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 9
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 10
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 11
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification Scan completed:
type 11, 11 channels, 1 status
Oct 14 19:43:53 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered
(00:a0:c5:3a:5d:aa)' excluded because of privacy mismatch: on != off.
Oct 14 19:43:53 mentorng kernel: ipw2200: U ipw_best_network Network
'<snipped-my-ESSID> (00:02:8a:0e:39:0c)' is a viable match.
Oct 14 19:43:53 mentorng kernel: ipw2200: U ipw_associate Assocation attempt:
'<snipped-my-ESSID>', channel 11, 802.11b [4], enc=on (open).
Oct 14 19:43:53 mentorng kernel: ipw2200: I ipw_rx_notification associated:
'<snipped-my-ESSID>' 00:02:8a:0e:39:0c

Tada!

# iwconfig eth1
eth1      IEEE 802.11b  ESSID:"<snipped-my-ESSID>"  Nickname:"mentorng.gurulabs.com"
          Mode:Managed  Frequency:2.462GHz  Access Point: 00:02:8A:0E:39:0C
          Bit Rate=11Mb/s   Tx-Power=20 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:<snipped-my-key>  Security mode:open
          Power Management:off
          Link Quality=40/100  Signal level=-35 dBm  Noise level=-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:6   Missed beacon:0
 
[root@mentorng ipw2200-0.12]# iwlist eth1 scanning
eth1      Scan completed :
          Cell 01 - Address: 00:A0:C5:3A:5D:AA
                    ESSID:"Empowered"
                    Protocol:IEEE 802.11b
                    Mode:Master
                    Channel:1
                    Encryption key:off
                    Bit Rate:11Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 11
                    Extra: RSSI: -49  dBm
                    Extra: Last beacon: 24ms ago
          Cell 02 - Address: 00:02:8A:0E:39:0C
                    ESSID:"OpenInternet"
                    Protocol:IEEE 802.11b
                    Mode:Master
                    Channel:11
                    Encryption key:off
                    Bit Rate:11Mb/s
                    Extra: Rates (Mb/s): 1 2 5.5 11
                    Extra: RSSI: -43  dBm
                    Extra: Last beacon: 1ms ago
 
Notice how the scanning doesn't show it. Should it?

OK. I verified. The interval is ~6 minutes. After that time, it will associate.

I was associated, then I ran:

iwconfig eth1 key off
iwconfig eth1 enc <my-key> open

Oct 14 19:56:27 mentorng kernel: ipw2200: I ipw_rx_notification disassociated:
'<snipped-my-ESSID>' 00:02:8a:0e:39:0c

...then after ~6mins...

Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 1
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 2
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 3
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 4
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 5
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 6
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 7
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 8
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 9
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 10
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan result for
channel 11
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification Scan completed:
type 11, 11 channels, 1 status
Oct 14 20:02:15 mentorng kernel: ipw2200: U ipw_best_network Network 'Empowered
(00:a0:c5:3a:5d:aa)' excluded because of privacy mismatch: on != off.
Oct 14 20:02:15 mentorng kernel: ipw2200: U ipw_best_network Network
'<snipped-my-ESSID> (00:02:8a:0e:39:0c)' is a viable match.
Oct 14 20:02:15 mentorng kernel: ipw2200: U ipw_associate Assocation attempt:
'<snipped-my-ESSID>', channel 11, 802.11b [4], enc=on (open).
Oct 14 20:02:15 mentorng kernel: ipw2200: I ipw_rx_notification associated:
'<snipped-my-ESSID>' 00:02:8a:0e:39:0c

Why the delay in associating?

I tried v0.12 w/patch at home. No regressions, it works as normal with my home
AP.

Tried out the patch with "Changes method in which hidden networks are identified
and associated".  A major step in the right direction, I'm associated!  It does
not seem quite flawless.  I had to go via security mode open, not restricted, to
get associated.  The ifup script somehow managed to turn off the encryption,
even though the setup on Fedora Core 2 indicates WEP key, and worked fine with
the previous chipset, so I had to manually set wep key (and mode open) and run
dhclient.

There were at times a large amount of DUPs, so I suspect the radio handshake is
not good (signal quality is excellent here).  Also, there were peculiar hangs in
X login, finally I had to reboot.  And the need to do rmmod and modprobe to get
any eth1 device at all is still there.

Is there anything I could list out with debug that would help in pinning down
the other problems?

Can you try the following patch?  It increases the dwell time used during a
directed scan.  In looking at the dmesg logs, this is my main guess at why it
was taking so long to associate -- it wasn't sitting on a channel long enough to
get the probe response.

diff -u -p -u -p -r1.365 ipw2200.c
--- ipw2200.c   14 Oct 2004 19:54:05 -0000      1.365
+++ ipw2200.c   15 Oct 2004 15:47:50 -0000
@@ -4456,12 +4456,8 @@ static int ipw_request_scan(struct ipw_p
        memset(&scan, 0, sizeof(scan));

        scan.dwell_time[IPW_SCAN_ACTIVE_BROADCAST_SCAN] = 20;
-       scan.dwell_time[IPW_SCAN_ACTIVE_BROADCAST_AND_DIRECT_SCAN] = 20;
+       scan.dwell_time[IPW_SCAN_ACTIVE_BROADCAST_AND_DIRECT_SCAN] = 100;
        scan.dwell_time[IPW_SCAN_PASSIVE_FULL_DWELL_SCAN] = 120;
-       /* if (priv->config & CFG_STATIC_ESSID)
-          ... set SSID ...
-          ... set scan type to IPW_SCAN_ACTIVE_BROADCAST_AND_DIRECT_SCAN
-       */

        scan.full_scan_index = ieee80211_get_scans(priv->ieee);
        if (priv->config & CFG_STATIC_ESSID) {

I tried the increase-dwell-time patch.

It seemed better, but (associate within 10 or so seconds), but then on a reboot
not so good (several minutes to associate). I can't get consistent results.

It seems like we getting close.

As a comparison, when associating to a network on an access point with just one
ESSID (or to the OpenInternet ESSID on the multiple-ESSID AP), it associates
very very quickly. Within a second or two (or less) I would say (and that is
without the increase-dwell-time patch).

Any thoughts on this? We have a whole office of guys with Thinkpads and the
ipw2200 cards who are either dragging long cables around or are using other
wireless cards.

I believe we have a viable fix in the works for this; we will hopefully be able
to get it in next week.

A new attempt to fix this is included in 0.14.  As of 0.14, a network is defined
by the combination of BSSID, ESSID, and channel.  Previously, only the BSSID was
used.

Confirmed that this fixes the problem. Should the earlier changes to the dwell
time be reverted?

It seems to take my 2200BG longer (5-6 seconds longer) to associate versus my
Cisco card.

The bug is verified by Dax Kelson. Mark it as verified. 

"It seems to take my 2200BG longer (5-6 seconds longer) to associate versus my
Cisco card." 
  -- If you confirm this is also a problem, please submit another bug for it, 
thanks!