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
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
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
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
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
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
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.
*** 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
*** 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
*** 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
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.
*** 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
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
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
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
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
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:
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
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
= 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
.
** 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
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
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,
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
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
= 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
, 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
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
28 matches
Mail list logo
