[Bug 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep
Confirming this on a desktop machine, Intel(R) Core(TM) i5-2500K with built-in Intel graphics and no additional video card at all. Suspend/resume was working just fine on 13.10. After upgrade to 14.04 suspend still works, but upon resume the screen is blank. The only way to get it back is to go to a text console and force-kill X so it respawns. I'm running KDE as my desktop, in case it matters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283938 Title: Ubuntu 14.04 blank screen after wakeup from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1283938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033669] Re: compizconfig causes python to segfault in quantal
Same as dseidel here: In [1]: import compizconfig In [2]: ctx = compizconfig.Context() compizconfig - Info: Backend : ini compizconfig - Info: Integration : true compizconfig - Info: Profile : default Segmentation fault (core dumped) Immediate segfault upon creating the context, before any invalid settings have been passed. This is using XFCE4 on ubuntu 12.10, freshly upgraded from 12.04. Basically this means that now it's impossible to tweak any Compiz settings on 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033669 Title: compizconfig causes python to segfault in quantal To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1033669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871176] Re: KnownFailure should not be registered as a global nose plugin
Many thanks, @jtaylor! Any chance the fix could be backported to 11.10? It's a trivial fix and means that right now, nobody can safely run the ipython test suite on 11.10... And it may also affect other packages that also try to use numpy's KnownFailure plugin. Given how tricky to debug the problem is if you get hit by it (in the ipython case, two expert developers independently wasted several hours each trying to sort it out), it would be great to see it fixed in the current ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871176 Title: KnownFailure should not be registered as a global nose plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/871176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871176] Re: KnownFailure should not be registered as a global nose plugin
Fair enough, I understand such concerns. Thanks again for handling it so promptly! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871176 Title: KnownFailure should not be registered as a global nose plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/871176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871176] [NEW] KnownFailure should not be registered as a global nose plugin
Public bug reported: Currently there's this in the ubuntu oneiric package: amirbar[matplotlib-1.0.1.egg-info] pwd /usr/share/pyshared/matplotlib-1.0.1.egg-info amirbar[matplotlib-1.0.1.egg-info] cat entry_points.txt [nose.plugins] KnownFailure = matplotlib.testing.noseclasses:KnownFailure this causes no end of trouble, such as the IPython test suite failing. Please don't register this as a global nose plugin, it's really meant only for matplotlib use. In fact it was copied from numpy. We'll work in mpl to hide it further and only expose our copy if we can't find the numpy one, but the ubuntu package should NOT expose this as a global nose plugin AT ALL. ** Affects: matplotlib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871176 Title: KnownFailure should not be registered as a global nose plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/871176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 868000] Re: Fix for #821290 broke M-f/M-b behaviour in gnome-terminal without menubar
I suspect (but could be wrong) this is related to the fact that in 11.10, now gtk won't honor the Emacs keybindings theme. Now even if the gtk key theme is set to Emacs, Ctrl A/E/K etc don't work anymore as they used to in any GTK text field (gedit, firefox text areas, etc). I tried to report it as a separate bug but keep getting launchpad server errors that discard my report, so I gave up and found the most similar existing bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/868000 Title: Fix for #821290 broke M-f/M-b behaviour in gnome-terminal without menubar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/868000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 414967] Re: print statements get incorrectly mangled by the autocall feature under Python 2.6
Hi Brian, On Fri, Apr 23, 2010 at 10:19 AM, Brian Murray br...@ubuntu.com wrote: Fernando - So is creating a patch out of revision 1224 the only bit we need to fix this in Ubuntu for Lucid? Yes! I hope to release 0.10.1 in the near future officially, so you can update to that later on. Cheers, f -- print statements get incorrectly mangled by the autocall feature under Python 2.6 https://bugs.launchpad.net/bugs/414967 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384713] Re: print statement does autocall inside interactive indented blocks
*** This bug is a duplicate of bug 414967 *** https://bugs.launchpad.net/bugs/414967 ** This bug has been marked a duplicate of bug 414967 print statements get incorrectly mangled by the autocall feature under Python 2.6 -- print statement does autocall inside interactive indented blocks https://bugs.launchpad.net/bugs/384713 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379135] Re: IPython history is broken. IndentationErrors everywhere.
*** This bug is a duplicate of bug 414967 *** https://bugs.launchpad.net/bugs/414967 ** This bug is no longer a duplicate of bug 384713 print statement does autocall inside interactive indented blocks ** This bug has been marked a duplicate of bug 414967 print statements get incorrectly mangled by the autocall feature under Python 2.6 -- IPython history is broken. IndentationErrors everywhere. https://bugs.launchpad.net/bugs/379135 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379132] Re: IPython history is broken. IndentationErrors everywhere.
*** This bug is a duplicate of bug 414967 *** https://bugs.launchpad.net/bugs/414967 ** This bug is no longer a duplicate of bug 384713 print statement does autocall inside interactive indented blocks ** This bug has been marked a duplicate of bug 414967 print statements get incorrectly mangled by the autocall feature under Python 2.6 -- IPython history is broken. IndentationErrors everywhere. https://bugs.launchpad.net/bugs/379132 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 414967] Re: print statements get incorrectly mangled by the autocall feature under Python 2.6
This is really an annoying bug, but I'm a bit lost on how to approach it. For example, we could hardcode a check on 'print' being on the line to avoid triggering the autocall behavior, but that would break legitimate use of autocall for users of print as a function... Any suggestions welcome. -- print statements get incorrectly mangled by the autocall feature under Python 2.6 https://bugs.launchpad.net/bugs/414967 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379135] Re: IPython history is broken. IndentationErrors everywhere.
*** This bug is a duplicate of bug 414967 *** https://bugs.launchpad.net/bugs/414967 Actually it's a dupe of bug 414967, where we'd like to centralize all ideas on what to do here... -- IPython history is broken. IndentationErrors everywhere. https://bugs.launchpad.net/bugs/379135 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 414967] Re: print statements get incorrectly mangled by the autocall feature under Python 2.6
On Thu, Apr 22, 2010 at 11:46 AM, Robert Kern
robert.kern+launch...@gmail.com wrote:
In LineInfo.ofind(), when ifun is print, check if the compiler has
recorded the from __future__ import print_function:
import __future__
def ofind(self, ip):
...
if self.ifunc == 'print':
if not ip.shell.compile.compiler.flags
__future__.CO_FUTURE_PRINT_FUNCTION:
return {'found': False, 'obj': None, ...}
Aha thanks! I looked around for this flag by reading the compiler
source code, but I failed to find this.
OK, with this info in hand, we can fix this damned bug quickly, which
is awfully irksome.
Cheers,
f
--
print statements get incorrectly mangled by the autocall feature under Python
2.6
https://bugs.launchpad.net/bugs/414967
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 414967] Re: print statements get incorrectly mangled by the autocall feature under Python 2.6
Thanks to Robert's tip, this is now fixed: - For 0.10.1: http://bazaar.launchpad.net/~ipython-dev/ipython/0.10.1/revision/1224 - For trunk: http://bazaar.launchpad.net/~ipython-dev/ipython/trunk/revision/1237 ** Changed in: ipython Status: In Progress = Fix Committed -- print statements get incorrectly mangled by the autocall feature under Python 2.6 https://bugs.launchpad.net/bugs/414967 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 414967] Re: print statements get incorrectly mangled by the autocall feature under Python 2.6
Fixed 2.5 and below incompatibitliy in r1225 for 0.10.1 and r1238 for trunk. -- print statements get incorrectly mangled by the autocall feature under Python 2.6 https://bugs.launchpad.net/bugs/414967 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 470824] Re: spurious trailing space after tab completion
On Sun, Jan 31, 2010 at 2:47 PM, Ludwig Schwardt ludwig.schwa...@gmail.com wrote: One solution to this problem is to install the readline package from PyPI (i.e. easy_install readline). The latest version (2.6.4) includes the fix from the Python maintenance branch mentioned above (r75747). It also works fine on Snow Leopard and Ubuntu. That's great to know, excellent. With a local install, one can keep the fix for now, and then remove it once upstream includes it in a new system python release. Thanks! f -- spurious trailing space after tab completion https://bugs.launchpad.net/bugs/470824 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 470824] Re: spurious trailing space after tab completion
On Sun, Jan 10, 2010 at 1:55 PM, Robert Schroll rschr...@gmail.com wrote: This issue has been fixed in Python's 2.6 maintenance branch with revision 75747. (Here's the patch itself: http://svn.python.org/view/python/branches/release26-maint/Modules/readline.c?r1=75747r2=75746pathrev=75747view=patch) What do I need to do to get this into Ubuntu's versions? I don't know specifically what the ubuntu policy is regarding backports of fixes like this, but I'd start here: http://packages.ubuntu.com/karmic/python/python This is the actual package page, you might have luck either reporting this to their bug tracker, or contacting the team members directly. It would really be great to have this done upstream; all my machines use ubuntu and this stupid backspacing is driving me crazy... Cheers, f -- spurious trailing space after tab completion https://bugs.launchpad.net/bugs/470824 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270856] Re: IPython hangs with PyGTK
Michiel, the problem is that in this case (I just tried) the shell blocks while plot windows are open... For 0.10.1, it would be nice to either have a solid solution here or to remove that warning, because it's not very informative to the users. I tried changing the code to have a single-threaded shell simply calling set_interactive(True/False), but neither worked: the shell just blocks on input. Ultimately in 0.11 we have a much more robust solution to this using PyOS_InputHook, and so far it's looking very solid. So if someone proposes for 0.10.1 a patch that takes proper advantage of the set_interactive call, I'll be happy to apply it, otherwise there's no point in giving that warning (since using the non-threaded shell and gtk just blocks, as best I can see in testing here on Ubuntu Karmic with a current pygtk that has set_interactive). -- IPython hangs with PyGTK https://bugs.launchpad.net/bugs/270856 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 470824] Re: spurious trailing space after tab completion
Closing as invalid, since this isn't really our bug, it's Python's. -- spurious trailing space after tab completion https://bugs.launchpad.net/bugs/470824 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 414967] Re: print statements get incorrectly mangled by the autocall feature under Python 2.6
Mmh: - Beni, I've applied your patch to 0.10.1 and trunk-dev, thanks. - As for the real problem with print, I'm not sure what to do: I've spent some quality time with the Python sources, trying to write some ctypes-based utilities to fish into the compiler state struct (see compiler.c and future.c in the Python tree), but no success yet. It's not the type of code I'm familiar with so it's likely to be slow/hard going, and I don't have the time for more on this now. Ultimately I'm leaning towards suggesting that people simply put in their config file from __future__ import print_function and be done with it! That way they start getting used to print as a function everywhere, in preparation for 3.0, they can learn the syntax of the function, and IPython will happily put the parens in there for them. It seems like a better way to address this than to sink days of work into an obscure tool to spelunk into the compiler internals at runtime to fish a __future__ flag out... Thoughts? If people agree on this, closing the bug will just require adding the text above to the docs/faq. ** Changed in: ipython Importance: Undecided = Low ** Changed in: ipython Status: New = In Progress ** Changed in: ipython Assignee: (unassigned) = Fernando Perez (fdo.perez) ** Changed in: ipython Milestone: None = 0.11 ** Branch linked: lp:~fdo.perez/ipython/trunk-dev ** Branch linked: lp:ipython/0.10 -- print statements get incorrectly mangled by the autocall feature under Python 2.6 https://bugs.launchpad.net/bugs/414967 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 463807] Re: Ipython adds extra space after successful completion
*** This bug is a duplicate of bug 470824 *** https://bugs.launchpad.net/bugs/470824 Not only is this a dupe ipython report, in fact it's ultimately a Python bug: http://bugs.python.org/issue5833 Closing, as there's nothing we can do about it until a new Python release is made with the fix. ** Bug watch added: Python Roundup #5833 http://bugs.python.org/issue5833 ** Changed in: ipython Status: New = Invalid ** Changed in: ipython Assignee: (unassigned) = Fernando Perez (fdo.perez) -- Ipython adds extra space after successful completion https://bugs.launchpad.net/bugs/463807 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381069] Re: Cannot step debugger in IPython 0.9.1/0.10 under Python 2.6.2/2.6.4: Pdb instance has no attribute 'curframe'
It would be great if someone could report this as a Python bug, which is what it really is: the checklines() method in pdb is broken, and this doesn't appear to have been reported. I've had my bugs.python account messed up for a while so I can't report it myself right now, sorry. -- Cannot step debugger in IPython 0.9.1/0.10 under Python 2.6.2/2.6.4: Pdb instance has no attribute 'curframe' https://bugs.launchpad.net/bugs/381069 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381069] Re: Cannot step debugger in IPython 0.9.1/0.10 under Python 2.6.2/2.6.4: Pdb instance has no attribute 'curframe'
Never mind: looking further, the bug is in our end... Stay tuned. -- Cannot step debugger in IPython 0.9.1/0.10 under Python 2.6.2/2.6.4: Pdb instance has no attribute 'curframe' https://bugs.launchpad.net/bugs/381069 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 381069] Re: Cannot step debugger in IPython 0.9.1/0.10 under Python 2.6.2/2.6.4: Pdb instance has no attribute 'curframe'
Fix committed here: http://bazaar.launchpad.net/~ipython- dev/ipython/0.10.1/revision/1214 Will be part of 0.10.1 release, but packagers (ubuntu and others) are welcome to include it now if they want to issue a quicker fix, because I'm not sure when 0.10.1 will be actually released. ** Branch linked: lp:~ipython-dev/ipython/0.10.1 ** Changed in: ipython (Ubuntu) Assignee: (unassigned) = Fernando Perez (fdo.perez) ** Changed in: ipython (Ubuntu) Assignee: Fernando Perez (fdo.perez) = (unassigned) ** Changed in: ipython Assignee: (unassigned) = Fernando Perez (fdo.perez) ** Changed in: ipython Status: New = Confirmed ** Changed in: ipython Importance: Undecided = High ** Changed in: ipython Status: Confirmed = Fix Committed ** Changed in: ipython Milestone: None = 0.10.1 -- Cannot step debugger in IPython 0.9.1/0.10 under Python 2.6.2/2.6.4: Pdb instance has no attribute 'curframe' https://bugs.launchpad.net/bugs/381069 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 406520] Re: libatlas3gf-sse2 zgemv function gives wrong result
This is indeed a really serious problem for numerical use of Ubuntu. Note: I suspect this bug is a dupe of the older: https://bugs.launchpad.net/ubuntu/+source/atlas/+bug/363510 -- libatlas3gf-sse2 zgemv function gives wrong result https://bugs.launchpad.net/bugs/406520 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328942] Re: ipython change char '0xe9' to 4 spaces
OK, I see it now. In fact, I don't even have to change my locale, just the terminal encoding (at least on gnome-terminal). I'm marking it as confirmed but assigned to nobody, because honestly I don't know how to fix it right now, and I have other things on my plate that are more urgent for me. We have others on the team that know much, much more about unicode than I do, so perhaps one of them can help. And if you do find a solution, please send it in, it would be very nice to have this fixed. Sorry not to be able to help more right now. ** Changed in: ipython Importance: Undecided = Medium Assignee: Fernando Perez (fdo.perez) = (unassigned) Status: New = Confirmed -- ipython change char '0xe9' to 4 spaces https://bugs.launchpad.net/bugs/328942 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328942] Re: does not accept input unicode char larger than unichr(0x8fff)
At least on my trunk, it looks fine: uqbar[scratch] python Python 2.5.2 (r252:60911, Oct 5 2008, 19:29:17) [GCC 4.3.2] on linux2 Type help, copyright, credits or license for more information. print unichr(0x9000) 退 uqbar[scratch] ip -nobanner In [1]: print unichr(0x9000) 退 Closing for now, reopen if you have further info using my trunk: https://code.launchpad.net/~fdo.perez/ipython/trunk-dev (this will be soon merged for release, once it's reviewed by others). ** Changed in: ipython Assignee: (unassigned) = Fernando Perez (fdo.perez) Status: New = Fix Committed -- does not accept input unicode char larger than unichr(0x8fff) https://bugs.launchpad.net/bugs/328942 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178509] Re: [hardy] wifi (iwl4965) is slow to return after suspend/resume
I think this bug should be reopened, since the problem persists. I'm running Intrepid on a Dell 1330 with the Intel 3495 card: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) and I get the same 30 second delay before the wireless connection starts up again after suspending. Here's some perhaps useful info from dmesg... After resuming: [167761.512525] Enabling non-boot CPUs ... [167761.512525] SMP alternatives: switching to SMP code [167761.519438] Booting processor 1/1 ip 6000 [167761.507072] Initializing CPU#1 ... About 6 seconds later, the wifi card comes up (and the LED confirms this): [167767.261785] iwl3945 :0c:00.0: enabling device ( - 0002) [167767.261797] iwl3945 :0c:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [167767.261867] iwl3945 :0c:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [167767.261936] iwl3945 :0c:00.0: restoring config space at offset 0x4 (was 0x0, writing 0xf6cff000) [167767.261950] iwl3945 :0c:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [167767.261969] iwl3945 :0c:00.0: restoring config space at offset 0x1 (was 0x12, writing 0x100106) [167767.344091] Registered led device: iwl-phy0:radio [167767.345162] Registered led device: iwl-phy0:assoc [167767.346115] Registered led device: iwl-phy0:RX [167767.347004] Registered led device: iwl-phy0:TX Here, it seems to try to immediately authenticate with some AP: [167767.347661] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.365973] ADDRCONF(NETDEV_UP): eth1: link is not ready [167767.385833] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.584035] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.784085] eth1: authenticate with AP 00:11:0a:e9:a4:e1 [167767.984028] eth1: authentication with AP 00:11:0a:e9:a4:e1 timed out But that didn't work, and next it tries another one, about 30 seconds later: [167795.730581] eth1: authenticate with AP 00:1e:c7:4f:2f:f1 [167795.732466] eth1: authenticated [167795.732481] eth1: associate with AP 00:1e:c7:4f:2f:f1 [167795.735924] eth1: RX AssocResp from 00:1e:c7:4f:2f:f1 (capab=0x431 status=0 aid=4) [167795.735937] eth1: associated [167795.737327] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [167805.893058] eth1: no IPv6 routers present And that worked. Now, I have no idea what the first AP might be, but it's NOT the network I was just on (I did this test by suspending and resuming my laptop at home, without moving or changing networks). I noticed that my EEE PC on which I just yesterday put 8.10, and which ONLY knows about this AP, reconnects instantly on resume. So I'm wondering if the problem is that NetworkManager is by default attempting to connect to some other AP first, instead of to my main one... I'll be happy to provide more details if needed, I'd really like to see this fixed. -- [hardy] wifi (iwl4965) is slow to return after suspend/resume https://bugs.launchpad.net/bugs/178509 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
