[Bug 604283] Re: network servers do not listen on 127.0.1.1
Any ETA on when this will be fixed in 10.04? I think this problem is likely why I've had problems getting e.g. "mvn jetty:run" to work on my laptop -- but only when a VPN connection (split-tunnel, I think) to my workplace is in place. -- network servers do not listen on 127.0.1.1 https://bugs.launchpad.net/bugs/604283 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 531249] Re: proximity.py crashes on startup with TypeError in ConfigObj.__init__()
Was mistakenly considered to be a duplicate of #284339, a fate that was share to several other Lucid-only bug reports for proximity. I have now cleaned up the erroneous duplicate markers; the other Lucid- only bugs now are duplicates of this one, as this one seems to be the only one that includes a patch. -- proximity.py crashes on startup with TypeError in ConfigObj.__init__() https://bugs.launchpad.net/bugs/531249 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 531256] Re: proximity.py crashed with TypeError in __init__()
*** This bug is a duplicate of bug 531249 *** https://bugs.launchpad.net/bugs/531249 ** This bug is no longer a duplicate of bug 284339 proximity.py crashed with TypeError in __init__() ** This bug has been marked a duplicate of bug 531249 proximity.py crashes on startup with TypeError in ConfigObj.__init__() -- proximity.py crashed with TypeError in __init__() https://bugs.launchpad.net/bugs/531256 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 530294] Re: Blue Proximity will not load in Lucid
*** This bug is a duplicate of bug 531249 *** https://bugs.launchpad.net/bugs/531249 ** This bug is no longer a duplicate of bug 284339 proximity.py crashed with TypeError in __init__() ** This bug has been marked a duplicate of bug 531249 proximity.py crashes on startup with TypeError in ConfigObj.__init__() -- Blue Proximity will not load in Lucid https://bugs.launchpad.net/bugs/530294 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 530666] Re: proximity.py crashed with TypeError in __init__()
*** This bug is a duplicate of bug 531249 *** https://bugs.launchpad.net/bugs/531249 ** This bug is no longer a duplicate of bug 284339 proximity.py crashed with TypeError in __init__() ** This bug has been marked a duplicate of bug 531249 proximity.py crashes on startup with TypeError in ConfigObj.__init__() -- proximity.py crashed with TypeError in __init__() https://bugs.launchpad.net/bugs/530666 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 530875] Re: proximity.py crashed with TypeError in __init__()
*** This bug is a duplicate of bug 531249 *** https://bugs.launchpad.net/bugs/531249 ** This bug is no longer a duplicate of bug 284339 proximity.py crashed with TypeError in __init__() ** This bug has been marked a duplicate of bug 531249 proximity.py crashes on startup with TypeError in ConfigObj.__init__() -- proximity.py crashed with TypeError in __init__() https://bugs.launchpad.net/bugs/530875 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 531249] Re: proximity.py crashes on startup with TypeError in ConfigObj.__init__()
** This bug is no longer a duplicate of bug 284339 proximity.py crashed with TypeError in __init__() -- proximity.py crashes on startup with TypeError in ConfigObj.__init__() https://bugs.launchpad.net/bugs/531249 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 531249] Re: proximity.py crashes on startup with TypeError in ConfigObj.__init__()
** Patch added: "Change ConfigObj() calls so as not to trigger buggy deprecation warning" http://launchpadlibrarian.net/40049115/avoid-configobj-deprecation.patch ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/40049116/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/40049117/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/40049118/ProcStatus.txt ** Attachment added: "Traceback.txt" http://launchpadlibrarian.net/40049119/Traceback.txt ** Visibility changed to: Public -- proximity.py crashes on startup with TypeError in ConfigObj.__init__() https://bugs.launchpad.net/bugs/531249 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 525342] Re: Deprecation warning in ConfigObj.__init__() causes crash
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39479649/Dependencies.txt -- Deprecation warning in ConfigObj.__init__() causes crash https://bugs.launchpad.net/bugs/525342 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 525342] [NEW] Deprecation warning in ConfigObj.__init__() causes crash
Public bug reported:
The current version of python-configobj in lucid (4.7.0-1) contains a
crash-inducing call to warnings.warn() in ConfigObj.__init__():
if options is not None:
import warnings
warnings.warn('Passing in an options dictionary to ConfigObj() is ',
'deprecated. Use **options instead.',
DeprecationWarning, stacklevel=2)
As warnings.warn accepts at most 3 arguments, the first comma should
probably be something else, e.g. a plus sign.
This problem causes applications that use the deprecated options
dictionary to crash:
$ blueproximity
Traceback (most recent call last):
File "/usr/share/blueproximity/proximity.py", line 1274, in
config = ConfigObj(os.path.join(conf_dir, _('standard') +
'.conf'),{'create_empty':True,'file_error':False,'configspec':conf_specs})
File "/usr/lib/pymodules/python2.6/configobj.py", line 1206, in __init__
DeprecationWarning, stacklevel=2)
TypeError: warn() takes at most 3 arguments (4 given)
The release notes for the latest upstream version, 4.7.1, indicates that
this problem has been adressed there:
http://pypi.python.org/pypi/configobj/4.7.1
ProblemType: Bug
Architecture: i386
Date: Sun Feb 21 16:48:59 2010
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: python-configobj 4.7.0-1
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: configobj
Uname: Linux 2.6.32-13-generic i686
** Affects: configobj (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 lucid
--
Deprecation warning in ConfigObj.__init__() causes crash
https://bugs.launchpad.net/bugs/525342
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 72227] Re: should avoid loading modules from working directory
On Thu, Jul 16, 2009 at 2:36 PM, Forest Bond wrote: > Harald, > > I'm afraid what you're saying isn't adding up. I can see from your test > script that the CWD is in your sys.path. That clearly indicates that > modules in your CWD should get imported. The _script directory_ is in my sys.path. When I run my test script as "./test.py", the script directory and the CWD coincide. However, as my bzr typically isn't run as "./bzr" when I'm in danger of triggering this bug, the CWD will not be in my sys.path. What I'm wondering is, does the test.py script, when run on your system, indicate the absolute path to the script directory is in sys.path, or is there an empty-string element in your sys.path? And, if there is any empty-string elements there, is the script directory there, as well? And finally, is the absolute path to the CWD somehow included in your sys.path? > Why don't you tell me what you're doing to reproduce, and I'll see if I > can help you figure out what the problem is. I performed the exact same steps that you indicated: hmel...@octarine:/tmp/,72227$ touch logging.py hmel...@octarine:/tmp/,72227$ bzr stat unknown: logging.py ... and as you can see, I was unable to reproduce the bug in this way, too. My thinking is that if the fix for this issue is as simple as removing any empty-string elements from sys.path (on Python installations that somehow isn't conforming to the sys.path documentation I linked to), then that should be easy to fix. If, on the other hand, your python somehow includes one or more absolute path to directories that we don't really want to import modules from, the fix might have to be more involved (one possible remedy in this case might be to run Python with the -S command-line option). -- Harald -- should avoid loading modules from working directory https://bugs.launchpad.net/bugs/72227 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 72227] Re: should avoid loading modules from working directory
On Thu, Jul 16, 2009 at 12:47 PM, Forest Bond wrote:
> [~]
> 06:45 for...@w038$ touch logging.py
> [~]
> 06:46 for...@w038$ bzr stat
> Traceback (most recent call last):
> File "/usr/bin/bzr", line 125, in
> import bzrlib.trace
> File "/usr/lib/python2.6/dist-packages/bzrlib/trace.py", line 106, in
>
> _bzr_logger = logging.getLogger('bzr')
> AttributeError: 'module' object has no attribute 'getLogger'
I can't reproduce this, either. Forest, what does the output of the
"test.py" script at the end of my first message look like on your
system?
--
Harald
--
should avoid loading modules from working directory
https://bugs.launchpad.net/bugs/72227
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 72227] Re: should avoid loading modules from working directory
I am unable to reproduce this on Ubunty Jaunty, using either the bzr from the official Jaunty repository (1.13.1-1) or the current development version. I've tried the following procedure with both python 2.5.4-1ubuntu4 and 2.6.2-0ubuntu1: hmel...@octarine:~$ mkdir /tmp/,72227/ hmel...@octarine:~$ cd /tmp/,72227/ hmel...@octarine:/tmp/,72227$ /usr/bin/python2.5 /usr/bin/bzr --no-plugins init Created a standalone tree (format: pack-0.92) hmel...@octarine:/tmp/,72227$ mkdir -p foo/codecs hmel...@octarine:/tmp/,72227$ touch foo/codecs/__init__.py hmel...@octarine:/tmp/,72227$ cd foo hmel...@octarine:/tmp/,72227/foo$ /usr/bin/python2.5 /usr/bin/bzr --no-plugins add adding foo adding foo/codecs adding foo/codecs/__init__.py I've also tried a similar procedure using the standalone 1.16.1-3 installer on a virtual Windows XP box. I was unable to reproduce the bug there, too. FWIW, the behaviour I'm seeing (i.e. not being able to reproduce the bug) seems to correspond well with Python's documentation (http://docs.python.org/library/sys.html#sys.path): sys.path[0] should only be an empty string when "the script directory is not available": hmel...@octarine:/tmp/,72227/foo$ cat > test.py #!/usr/bin/env python import sys import pprint pprint.pprint(sys.path) hmel...@octarine:/tmp/,72227/foo$ chmod +x test.py hmel...@octarine:/tmp/,72227/foo$ ./test.py ['/tmp/,72227/foo', '/usr/lib/python2.6', '/usr/lib/python2.6/plat-linux2', '/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old', '/usr/lib/python2.6/lib-dynload', '/usr/lib/python2.6/dist-packages', '/usr/lib/python2.6/dist-packages/Numeric', '/usr/lib/python2.6/dist-packages/PIL', '/usr/lib/python2.6/dist-packages/gst-0.10', '/var/lib/python-support/python2.6', '/usr/lib/python2.6/dist-packages/gtk-2.0', '/var/lib/python-support/python2.6/gtk-2.0', '/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode', '/usr/local/lib/python2.6/dist-packages'] i.e. when I invoke a Python script on my system, there is no empty string element in sys.path. Does anyone know how to reliably reproduce this bug? -- should avoid loading modules from working directory https://bugs.launchpad.net/bugs/72227 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 172601] Re: Dual-head fails with ati driver, appears related to 'crtc'
On 12/12/2007, Tormod Volden <[EMAIL PROTECTED]> wrote: > I'll temporarily just attach the "buggy" version here. Doesn't work well > for me, but might well work for you :) This does indeed work just fine for me. Thanks! -- Harald -- Dual-head fails with ati driver, appears related to 'crtc' https://bugs.launchpad.net/bugs/172601 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172601] Re: Dual-head fails with ati driver, appears related to 'crtc'
It appears that my email attachment didn't make it through, attaching shell script via LP web UI. ** Attachment added: "Shell script for toggling between LVDS and external monitors" http://launchpadlibrarian.net/10835496/toggle-screens -- Dual-head fails with ati driver, appears related to 'crtc' https://bugs.launchpad.net/bugs/172601 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 172601] Re: Dual-head fails with ati driver, appears related to 'crtc'
On 11/12/2007, Anthony Brock <[EMAIL PROTECTED]> wrote: > Harald, > > I suspect that we are discussing related, but not identical issues. > You're able to make CRTC 0 monitors work at the same time as a CRTC 1 > monitor (which I am NOT able to accomplish). While you're situation does > not allow maximum resolution, mines doesn't allow ANY resolution. > > The "nonsense" on LVDS-0 is, in my view, simply the way that monitor > choses to display the signal it is receiving. The Dell FP1905 monitors > chose to display it with the "... Cannot Display This Video Mode" > message. So, in my view, the LVDS and VGA-0 display issues are the same > in my case. Your issue is likely related, but not as severe (since > you're able to see something displayed with a low-enough resolution). > > Does that make sense? To me it does; I think the issues sound likely to be at least very closely related, so for now I'll hold off on filing my issue as a separate bug. Tormod, please let me know if you think otherwise. I should also mention that as my LVDS has a max resolution of 1400x1050 (i.e. lower than the max resolution of the external monitors), I'm doing "xrandr --output LVDS --off" whenever I switch[1] to using the external monitors -- so that might be why I'm not seeing any "nonsense". [1] By using the attached shell script. -- Harald -- Dual-head fails with ati driver, appears related to 'crtc' https://bugs.launchpad.net/bugs/172601 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 172601] Re: Dual-head fails with ati driver, appears related to 'crtc'
On 10/12/2007, Tormod Volden <[EMAIL PROTECTED]> wrote: > Anthony, from Harald's comment it sounds like it might would help for > you to specify: Virtual 2560 1024 I'd guess that might cause the "nonsense" on LVDS to go away, but that's not the real issue I'm hoping to have fixed -- do we have a disconnect on what we consider to be the bug here? To me, the real issue is that I can't make CRTC 0 drive monitors with as high a resolution as CRTC 1 can (even though I could do this using the same hardware under Feisty, so it's not a hardware problem). The way I'm interpreting Anthony's original bug report, he also considers the "trying to use CRTC 0 to drive monitor X on its maximum (preferred) resolution just makes it go black" problem to be the main issue; the fact that he sees some nonsense on LVDS while trying to set up VGA-0 *and* DVI-0 with their preferred resolutions might be a clue to where the problem originates, but isn't the real problem that he wants fixed. Anthony, am I interpreting you correctly? If not, should I create a separate bug report for what I consider to be the main issue? -- Harald -- Dual-head fails with ati driver, appears related to 'crtc' https://bugs.launchpad.net/bugs/172601 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172601] Re: Dual-head fails with ati driver, appears related to 'crtc'
I have a similar setup here: Dell Latitude D610 with ATI Technologies Inc M22 [Mobility Radeon X300] Docking station Two external monitors, each capable of 1600x1200, connected through the DVI and VGA ports of the docking station and I'm seeing a very similar problem: whichever (external) monitor that's currently using CRTC 0 can't display the signal when I attempt using the 1600x1200 mode. CRTC 1 works nicely with this mode, no matter which of the external monitors is using it. Reducing the mode for the CRTC 0-connected monitor to 1200x1024 makes it usable. (I'm not seeing any of the LVDS "nonsense" on startup, though. I did see something like that when I tried a very wide "Virtual" setting in xorg.conf, but as I don't need that much width, I reduced it back to 3200, which doesn't cause any artefacts). The same physical setup was working nicely under feisty (with 2x1600x1200 on Xinerama), so I'm guessing that this is a CRTC 0-specific deficiency in the radeon driver. I've also tried upgrading the X drivers from Tormod Volden's launchpad archive (deb http://ppa.launchpad.net/tormodvolden/ubuntu gutsy main), but that didn't help. Let me know if you would like me to attach any diagnostic data for my case. -- Dual-head fails with ati driver, appears related to 'crtc' https://bugs.launchpad.net/bugs/172601 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
