| 2008-03-28 04:28:29 |
Mary Gardiner |
bug |
|
|
added bug |
| 2008-03-28 12:39:15 |
Mary Gardiner |
bug |
|
|
added attachment 'unnamed' (unnamed) |
| 2008-03-28 22:34:33 |
Mary Gardiner |
bug |
|
|
added attachment 'dmesg-afterbootubuntu5.log' (dmesg output after booting, using pm-utils 0.99.2-3ubuntu5) |
| 2008-03-28 22:37:08 |
Mary Gardiner |
bug |
|
|
added attachment 'dmesg-afterresumeubuntu5.log' (dmesg after suspending and resuming and network-manager successfully has brought the connection up, using pm-utils 0.99.2-3ubuntu5) |
| 2008-03-29 08:45:45 |
Mary Gardiner |
title |
Upgrade from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 breaks wireless after resume (iwl3945) |
/etc/udev/rules.d/70-persistent-net.rules file needed to be regenerated to be able to use wireless after suspend (iwl3945) |
|
| 2008-03-29 08:49:20 |
Mary Gardiner |
description |
Binary package hint: pm-utils
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer works after suspend-and-resume. A full reboot is required to make it work again, as far as I can tell (reloading the driver does not work). This is a regression: I have not had this fail before on Hardy.
If I use dpkg -i to downgrade to pm-utils 0.99.2-3ubuntu5 (and downgrade nothing else) the wireless works even after suspend-and-resume.
I originally thought I was affected by bug 204040, but that bug was reported well before 0.99.2-3ubuntu6 was uploaded. I have only been affected by this problem since installing 0.99.2-3ubuntu6 this morning.
Relevant info was attached to bug 204040 (all with the failing 0.99.2-3ubuntu6 installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer works after suspend-and-resume. A full reboot is required to make it work again, as far as I can tell (reloading the driver does not work). This was a regression: I have not had this fail before on Hardy.
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file)
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
|
| 2008-03-29 08:50:12 |
Mary Gardiner |
bug |
|
|
added attachment '70-persistent-net.rules' (Version of 70-persistent-net.rules that did not work) |
| 2008-03-29 08:51:02 |
Mary Gardiner |
bug |
|
|
added attachment '70-persistent-net.rules' (Newly generated 70-persistent-net.rules that allows wireless to work after resume) |
| 2008-03-29 08:53:00 |
Mary Gardiner |
description |
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer works after suspend-and-resume. A full reboot is required to make it work again, as far as I can tell (reloading the driver does not work). This was a regression: I have not had this fail before on Hardy.
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file)
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer worked after suspend-and-resume. A full reboot was required to make it work again. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file).
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
|
| 2008-03-30 02:40:07 |
Daniel Hahler |
udev: importance |
Undecided |
High |
|
| 2008-03-30 02:40:07 |
Daniel Hahler |
udev: status |
New |
Triaged |
|
| 2008-03-30 02:40:07 |
Daniel Hahler |
udev: milestone |
|
ubuntu-8.04 |
|
| 2008-03-30 21:45:48 |
Daniel Hahler |
description |
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer worked after suspend-and-resume. A full reboot was required to make it work again. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file).
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
The logic in udev according to /etc/udev/rules.d/70-persistent-net.rules seems to have changed:
Old lines look like:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:ea:8c:2d:36", NAME="eth0"
which causes udev to add new lines like the following after suspend/resume (module unload/reload):
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", ATTR{type}=="1", NAME="eth2"
After removing 70-persistent-net.rules and rebooting, the following line gets created:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0f:ea:8c:2d:36", ATTR{type}=="1", NAME="eth0"
The old entries are missing an ACTION and ATTR{type} attribute, which seems to cause udev to add the extra line and therefore renaming the interface somehow.
ORIGINAL DESCRIPTION:
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer worked after suspend-and-resume. A full reboot was required to make it work again. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file).
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3.
WORKAROUND:
1. sudo rm /etc/udev/rules.d/70-persistent-net.rules
2. Reboot
/etc/udev/rules.d/70-persistent-net.rules should have been regenerated correctly. |
|
| 2008-03-31 04:46:35 |
Alex Fraser |
bug |
|
|
added attachment 'dmesg.txt' (Output of dmesg) |
| 2008-03-31 20:36:14 |
Mary Gardiner |
bug |
|
|
added attachment 'unnamed' (unnamed) |
| 2008-03-31 22:48:59 |
James Troup |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2008-04-01 22:07:17 |
Mary Gardiner |
description |
The logic in udev according to /etc/udev/rules.d/70-persistent-net.rules seems to have changed:
Old lines look like:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:ea:8c:2d:36", NAME="eth0"
which causes udev to add new lines like the following after suspend/resume (module unload/reload):
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", ATTR{type}=="1", NAME="eth2"
After removing 70-persistent-net.rules and rebooting, the following line gets created:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0f:ea:8c:2d:36", ATTR{type}=="1", NAME="eth0"
The old entries are missing an ACTION and ATTR{type} attribute, which seems to cause udev to add the extra line and therefore renaming the interface somehow.
ORIGINAL DESCRIPTION:
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer worked after suspend-and-resume. A full reboot was required to make it work again. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file).
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3.
WORKAROUND:
1. sudo rm /etc/udev/rules.d/70-persistent-net.rules
2. Reboot
/etc/udev/rules.d/70-persistent-net.rules should have been regenerated correctly. |
The logic in udev according to /etc/udev/rules.d/70-persistent-net.rules seems to have changed:
Old lines look like:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:ea:8c:2d:36", NAME="eth0"
which causes udev to add new lines like the following after suspend/resume (module unload/reload):
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", ATTR{type}=="1", NAME="eth2"
After removing 70-persistent-net.rules and rebooting, the following line gets created:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0f:ea:8c:2d:36", ATTR{type}=="1", NAME="eth0"
The old entries are missing an ACTION and ATTR{type} attribute, which seems to cause udev to add the extra line and therefore renaming the interface somehow.
SYMPTOMS:
This often shows up as an inability to use any wireless networks after suspending/hibernating and resuming. "iwlist config" will show an interface named "wlan0_rename" or similar.
WORKAROUND:
1. sudo rm /etc/udev/rules.d/70-persistent-net.rules
2. Reboot
/etc/udev/rules.d/70-persistent-net.rules should have been regenerated correctly.
ORIGINAL DESCRIPTION:
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer worked after suspend-and-resume. A full reboot was required to make it work again. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file).
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
|
| 2008-04-01 23:04:16 |
Mary Gardiner |
description |
The logic in udev according to /etc/udev/rules.d/70-persistent-net.rules seems to have changed:
Old lines look like:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:ea:8c:2d:36", NAME="eth0"
which causes udev to add new lines like the following after suspend/resume (module unload/reload):
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", ATTR{type}=="1", NAME="eth2"
After removing 70-persistent-net.rules and rebooting, the following line gets created:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0f:ea:8c:2d:36", ATTR{type}=="1", NAME="eth0"
The old entries are missing an ACTION and ATTR{type} attribute, which seems to cause udev to add the extra line and therefore renaming the interface somehow.
SYMPTOMS:
This often shows up as an inability to use any wireless networks after suspending/hibernating and resuming. "iwlist config" will show an interface named "wlan0_rename" or similar.
WORKAROUND:
1. sudo rm /etc/udev/rules.d/70-persistent-net.rules
2. Reboot
/etc/udev/rules.d/70-persistent-net.rules should have been regenerated correctly.
ORIGINAL DESCRIPTION:
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer worked after suspend-and-resume. A full reboot was required to make it work again. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file).
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
The logic in udev according to /etc/udev/rules.d/70-persistent-net.rules seems to have changed:
Old lines look like:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0f:ea:8c:2d:36", NAME="eth0"
which causes udev to add new lines like the following after suspend/resume (module unload/reload):
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", ATTR{type}=="1", NAME="eth2"
After removing 70-persistent-net.rules and rebooting, the following line gets created:
# PCI device 0x10de:0x0057 (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0f:ea:8c:2d:36", ATTR{type}=="1", NAME="eth0"
The old entries are missing an ACTION and ATTR{type} attribute, which seems to cause udev to add the extra line and therefore renaming the interface somehow.
SYMPTOMS:
This often shows up as an inability to use any wireless networks after suspending/hibernating and resuming. "iwlist config" will show an interface named "wlan0_rename" or similar.
WORKAROUND:
1. sudo rm /etc/udev/rules.d/70-persistent-net.rules
2. Reboot
/etc/udev/rules.d/70-persistent-net.rules should have been regenerated correctly.
Note that this probably will change the names of your network interfaces, particularly your wireless ones. If you rely on them having particular identifiers (eth0, eth1, wlan0 etc) for the purposes of custom scripts, firewall rules or anything similar, you may need to update these settings after the file is regenerated.
ORIGINAL DESCRIPTION:
After upgrading pm-utils from 0.99.2-3ubuntu5 to 0.99.2-3ubuntu6 my iwl3945 wireless driver no longer worked after suspend-and-resume. A full reboot was required to make it work again. https://bugs.launchpad.net/ubuntu/+source/udev/+bug/208103/comments/5 suggested a solution that seems to work: removing /etc/udev/rules.d/70-persistent-net.rules and rebooting so that it was regenerated. I am leaving this bug open so that it can be evaluated by udev (duplicate, invalid, or a genuine problem with some earlier versions of this file).
System info was attached to bug 204040 (all with the failing pm-utils 0.99.2-3ubuntu6 and /etc/udev/rules.d/70-persistent-net.rules file installed):
$ uname -a
Linux gertrude 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Output of "lspci -vvnn":
http://launchpadlibrarian.net/12935525/lspci-vvnn.txt
Output of dmesg immediately after boot (no attempt at suspend at this point)
http://launchpadlibrarian.net/12935528/dmesg-afterboot.txt
Output of dmesg after resuming from suspend:
http://launchpadlibrarian.net/12935535/dmesg-afterresume.txt
Output of dmesg after resume and after running "modprobe -r iwl3945 && modprobe iwl3945" as root:
http://launchpadlibrarian.net/12935544/dmesg-aftermodprobe.txt
Other possibly relevant info: I am using Network Manager to manage the wireless connection, version 0.6.6-0ubuntu3. |
|
| 2008-04-02 06:07:53 |
Colin Watson |
udev: assignee |
|
keybuk |
|
| 2008-04-02 11:36:41 |
Scott James Remnant (Canonical) |
marked as duplicate |
|
183968 |
|
| 2008-04-04 14:29:33 |
Steve Dee |
bug |
|
|
added subscriber Josh Lee |
