[Bug 1519545] Re: gpsbabel has usb problems
Thanks so much for the provided workaround. On Ubuntu 20.04, /etc/default/tlp no longer exists. Instead, I created a file /etc/tlp.d/50-usb-blacklist.conf containing only this line: USB_BLACKLIST="091e:0003" After "systemctl restart tlp", gpsbabel worked fine with my Garmin eTrex Vista HCx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519545 Title: gpsbabel has usb problems To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1519545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807244] Re: mediathekview does not find com.jidesoft.utils.ThreadCheckingRepaintManager
This seems to be a duplicate of #1798683 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807244 Title: mediathekview does not find com.jidesoft.utils.ThreadCheckingRepaintManager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediathekview/+bug/1807244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409280] Re: Graphviz's sfdp is seriuosly crippled without a triangulation library
This issue no longer occurs in Cosmic. Installing graphviz now pulls in a 'libgts-0.7-5' package, so I assume that the fix that was made in the Debian package has found its way to Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409280 Title: Graphviz's sfdp is seriuosly crippled without a triangulation library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/1409280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203568] Re: dosfsck slow repairing thousands of identically named files
Great to hear! I'm happy that at least someone is using it. Perhaps Daniel (the maintainer) is now willing to take a second look at the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203568 Title: dosfsck slow repairing thousands of identically named files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1203568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203568] Re: dosfsck slow repairing thousands of identically named files
Any news on this? It's a one-line patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203568 Title: dosfsck slow repairing thousands of identically named files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1203568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298831] [NEW] pyvenv environments not usable without activation
Public bug reported: Virtual environments created with pyvenv are supposed to be usable without 'activation', according to Python's docs. With Ubuntu's Python 3.3 packages, however, the sys.path is incomplete unless the environment variable VIRTUAL_ENV is set. $ cd /tmp $ pyvenv-3.3 venv $ venv/bin/python -c 'import sys;print(sys.path)' ['', '/usr/lib/python3.3', '/usr/lib/python3.3/plat-x86_64-linux-gnu', '/usr/lib/python3.3/lib-dynload'] When I create a test module, I cannot import it: $ echo 'print(Hello)' venv/lib/python3.3/site-packages/hello.py $ venv/bin/python -c 'import hello' Traceback (most recent call last): File string, line 1, in module ImportError: No module named 'hello' When I set VIRTUAL_ENV (simulating activation), the sys.path is complete and it works: $ VIRTUAL_ENV=/tmp/venv venv/bin/python -c 'import sys;print(sys.path)' ['', '/usr/lib/python3.3', '/usr/lib/python3.3/plat-x86_64-linux-gnu', '/usr/lib/python3.3/lib-dynload', '/tmp/venv/lib/python3.3/site-packages'] $ VIRTUAL_ENV=/tmp/venv venv/bin/python -c 'import hello' Hello The latter output is what I also get with a Python manually compiled from sources, but even without the VIRTUAL_ENV variable being set. This may be related: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695758 - https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1093193 Versions: Ubuntu 13.10 Python 3.3.2-7ubuntu3.1 ** Affects: python3.3 (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/1298831 Title: pyvenv environments not usable without activation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1298831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298831] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1298831/+attachment/404/+files/ProcEnviron.txt ** Changed in: python3.3 (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298831 Title: pyvenv environments not usable without activation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1298831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298831] Re: pyvenv environments not usable without activation
apport information ** Tags added: apport-collected saucy ** Description changed: Virtual environments created with pyvenv are supposed to be usable without 'activation', according to Python's docs. With Ubuntu's Python 3.3 packages, however, the sys.path is incomplete unless the environment variable VIRTUAL_ENV is set. $ cd /tmp $ pyvenv-3.3 venv $ venv/bin/python -c 'import sys;print(sys.path)' ['', '/usr/lib/python3.3', '/usr/lib/python3.3/plat-x86_64-linux-gnu', '/usr/lib/python3.3/lib-dynload'] When I create a test module, I cannot import it: $ echo 'print(Hello)' venv/lib/python3.3/site-packages/hello.py $ venv/bin/python -c 'import hello' Traceback (most recent call last): File string, line 1, in module ImportError: No module named 'hello' When I set VIRTUAL_ENV (simulating activation), the sys.path is complete and it works: $ VIRTUAL_ENV=/tmp/venv venv/bin/python -c 'import sys;print(sys.path)' ['', '/usr/lib/python3.3', '/usr/lib/python3.3/plat-x86_64-linux-gnu', '/usr/lib/python3.3/lib-dynload', '/tmp/venv/lib/python3.3/site-packages'] $ VIRTUAL_ENV=/tmp/venv venv/bin/python -c 'import hello' Hello The latter output is what I also get with a Python manually compiled from sources, but even without the VIRTUAL_ENV variable being set. This may be related: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695758 - https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1093193 Versions: Ubuntu 13.10 Python 3.3.2-7ubuntu3.1 + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2012-04-14 (713 days ago) + InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427) + MarkForUpload: True + Package: python3.3 3.3.2-7ubuntu3.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 + Tags: saucy + Uname: Linux 3.8.0-22-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-10-18 (161 days ago) + UserGroups: ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1298831/+attachment/4048887/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298831 Title: pyvenv environments not usable without activation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1298831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203568] [NEW] dosfsck slow repairing thousands of identically named files
Public bug reported: I have an image of a broken FAT file system that contains approx. 3 identically named files. These were created by a GPS logger, which usually writes its track into a single file, but somehow managed to create a new file each second due to a broken SD card. To salvage the files, I use dosfsck -aw file.img. That is initially quite fast, renaming hundreds of files per second, but gets slower and slower until renaming a single file takes multiple seconds. The problem seems to be that the function auto_rename in in src/check.c uses a loop to find an unused file name, starting with FSCK.000 and incrementing to FSCK.001 and so on if the file name is already in use. This is slow because, for each file, all the previous file names are checked again (quadratic time). I have solved the problem for me by using a random file name instead: --- a/src/check.c +++ b/src/check.c @@ -384,7 +384,7 @@ static void auto_rename(DOS_FILE * file) -number = 0; +number = random() % 1000; @@ -403,7 +403,7 @@ static void auto_rename(DOS_FILE * file) - number++; + number = random() % 1000; I cancelled my first attempt of repairing the image after 12 hours. With this patch, dosfsck was finished within 2 minutes. ** Affects: dosfstools (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/1203568 Title: dosfsck slow repairing thousands of identically named files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosfstools/+bug/1203568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075173] Re: Kile won't open files outside the home directory
The bug seems to have been fixed for more recent kile versions: https://bugs.kde.org/show_bug.cgi?id=301808 ** Bug watch added: KDE Bug Tracking System #301808 https://bugs.kde.org/show_bug.cgi?id=301808 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kile in Ubuntu. https://bugs.launchpad.net/bugs/1075173 Title: Kile won't open files outside the home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kile/+bug/1075173/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 701262] Re: OpenJDK Java running eclipse crashes with error in libc
This blog post possibly describes the same problem: http://www.siafoo.net/user/stou/blog/2010/12/06/Only-free-if-your-time-is In short: Try to unset the environment variable MALLOC_CHECK_ and see if it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701262 Title: OpenJDK Java running eclipse crashes with error in libc -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
