[Bug 1340219] Re: s3ql post-installation script fails with syntax error in "yield from"
Where did you get this package version from? The most-recent s3ql package in the official precise repository is 1.9-1 (see http://packages.ubuntu.com/precise/s3ql). The most recent s3ql package for precise in the ppa is 1.18.1-1~precise1 (not 1.18-1~precise1, see https://launchpad.net/~nikratio/+archive/ubuntu/s3ql/+packages). Either of these packages should work fine. ** Changed in: s3ql (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340219 Title: s3ql post-installation script fails with syntax error in "yield from" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1340219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
spamistrash, try to install a vanilla upstream kernel without Ubuntu patches. This makes things work reliably for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272375] Re: tests fail with python3.4 as default version
Martin, why should the package build extensions for all supported python3 versions? It is an application, not a Python module. So isn't it sufficient if it works with the default python version? At least in Debian, this seems to be the officially blessed way to package Python apps (see eg. https://wiki.debian.org/Python/Packaging, Example 2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272375 Title: tests fail with python3.4 as default version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1272375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272375] Re: tests fail with python3.4 as default version
In other words, this bug will resolve itself automatically, and there is nothing that needs to be fixed in the s3ql package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272375 Title: tests fail with python3.4 as default version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1272375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272375] Re: tests fail with python3.4 as default version
After another update && dist-upgrade, the testcases now fail because s3ql itself has not been rebuilt with the new default python (as a Python app rather than Python module, the package is build only with the default interpreter). Is there some missing metadata that ought to have triggered a rebuilt? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272375 Title: tests fail with python3.4 as default version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1272375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272375] Re: tests fail with python3.4 as default version
I've added the ppa and upgraded the system. Now all the s3ql unit tests fail because none of the dependencies are available for Python 3.4 (e.g. no python-apsw), not really surprising and (as far as I understand) not a bug in S3QL. I'd like to debug this problem, but I'll need some instruction to replicate whatever environment you used to run the tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272375 Title: tests fail with python3.4 as default version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1272375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272375] Re: tests fail with python3.4 as default version
The subprocess related bug is fixed in https://bitbucket.org/nikratio/s3ql/commits/8772e4b7548d09dbf77bf8b126bd084a1f338a36 Is there a way to reproduce the problems with python3.4 as default python? I'm running a chroot with trusty-proposed, but it still seems to use python3.3 as default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272375 Title: tests fail with python3.4 as default version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1272375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272375] Re: tests fail with python3.4 as default version
I found a problem that causes the unit tests after (and including) t4_adm.py to fail. The problem is that when forking subprocesses, the subprocesses try to load the modules from the source package rather than the installed package. This is, however, unrelated to Python 3.4 being installed or not. Do you have an example of a test run from trusty where these tests actually pass? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272375 Title: tests fail with python3.4 as default version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1272375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272375] Re: tests fail with python3.4 as default version
The log on https://jenkins.qa.ubuntu.com/job/trusty-adt- s3ql/36/ARCH=i386,label=adt/console says that the tests were run under Python 3.3. Did you built with python3.4, but then ran the self tests with python 3.3? This mustfail, because then the C extension (deltadump.so) is not available for python 3.3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272375 Title: tests fail with python3.4 as default version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1272375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
I just performed the BIOS update. It still does not work with the Ubuntu kernel, and it still works with the mainline kernel. $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for nikratio: G6ETA1WW (2.61 ) 12/13/2013 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
I can probably give the BIOS update a shot. However, could you elaborate why we're going this avenue? The DisplayLink is a USB device, and it works with the mainline kernel. So wouldn't the correct course of action be to bisect the differences between Ubuntu and mainline to determine which ubuntu-specific patch is causing the breakage? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
I tested with the amd64 precise desktop image, and I can confirm that the problem is reproducible there as well. I do have a /dev/dri/card1 device, but X11 fails to open it with "Resource temporarily unavailable". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Apologies, the Ubuntu kernel naming/versioning scheme is completely opaque to me. I have no idea why 3.11.0-031100-generic needs to be mainline while 3.11.0-11-generic is not (and I read through many of the Ubuntu kernel wiki packages). So, I'm still happy to test other packages or perform a bisection, but I need either git commits / tags or URLs to .deb's. Version numbers do not help me at all. Do I understand correctly that you do *not* want me to do the git bisection anymore, and instead test the http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.11.3-saucy/ packages? I already tried the http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.11-saucy/ packages, and they do *not* exhibit the problem. As far as I can tell, *none* of the mainline kernels that I have tested are affected by the problem and *all* Ubuntu kernels that I have tested are affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
I'm afraid I still don't get the mapping. There's no 3.11.0-031100 in the "Ubuntu Kernel Version" column on http://kernel.ubuntu.com/~kernel- ppa/info/kernel-version-map.html. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
I cloned the git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git repository, but I'm having trouble identifying the commits that correspond to 3.11.0-031100-generic and 3.11.0-11-generic. There does not seem to be a Ubuntu-3.11.0-11 tag: $ git log --oneline Ubuntu-3.11.0-031100..Ubuntu-3.11.0-11 fatal: ambiguous argument 'Ubuntu-3.11.0-031100..Ubuntu-3.11.0-11': unknown revision or path not in the working tree. Could you tell me the start and stop commits for the bisect? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: 17e9:0378 [Lenovo ThinkPad X1 Carbon] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Bug is *not present* in http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.11.10-saucy/, i.e. the external display is working with that kernel. ** Tags added: kernel-fixed-upstream-3.11.10 ** Tags removed: needs-kernel-logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Just tested latest Trusty live CD. Bug is still present. ** Changed in: linux (Ubuntu Saucy) Status: Incomplete => Confirmed ** Changed in: linux (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/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922166/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922165/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922171/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922168/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922170/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922175/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922173/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922172/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922169/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922163/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922167/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922164/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922162/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922174/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
apport information ** Tags added: apport-collected trusty ** Description changed: My Plugable UGA-2K-A USB 2.0 to DVI adapter (using chipset DisplayLink DL-195, USB ID 17e9:4302) works fine with 3.11.0-031100-generic. However, when upgrading to 3.11.0-11-generic, X11 fails to open the DRI device with [ 8.868] (EE) open /dev/dri/card1: Resource temporarily unavailable Reverting to 3.11.0-031100-generic fixes the problem. Upgrading to current mainline (3.12.0-999.201310030405) also fixes the problem (but causes lots of kernel BUG messages). In both cases, the kernel correctly creates the /dev/fb1 and /dev/dri/card1 devices. There are no error messages in the kernel log. - I can bisect this if someone tells me where to find the intermediate - versions. + I can bisect this if someone tells me where to find the intermediate versions. + --- + ApportVersion: 2.12.7-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2883 F pulseaudio + CasperVersion: 1.336ubuntu1 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131203) + MachineType: LENOVO 3444F8U + MarkForUpload: True + Package: linux (not installed) + ProcFB: + 0 inteldrmfb + 1 udldrmfb + ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity + ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 + RelatedPackageVersions: + linux-restricted-modules-3.12.0-5-generic N/A + linux-backports-modules-3.12.0-5-generic N/A + linux-firmware1.117 + Tags: trusty + Uname: Linux 3.12.0-5-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + WifiSyslog: + + dmi.bios.date: 02/04/2013 + dmi.bios.vendor: LENOVO + dmi.bios.version: G6ET93WW (2.53 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 3444F8U + dmi.board.vendor: LENOVO + dmi.board.version: Win8 Pro DPK TPG + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvrG6ET93WW(2.53):bd02/04/2013:svnLENOVO:pn3444F8U:pvrThinkPadX1Carbon:rvnLENOVO:rn3444F8U:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 3444F8U + dmi.product.version: ThinkPad X1 Carbon + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1234818/+attachment/3922161/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Tags added: kernel-fixed-upstream ** Tags added: kernel-fixed-upstream-3.11.0-031100-generic ** Changed in: linux (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/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
On 10/21/2013 05:46 AM, Frank Lazzarini wrote: > I just upgraded my Ubuntu installation from 13.04 (kernel > 3.10.0-031000rc7-generic) with a USB Displaylink working just fine to > 13.10 after loading the new kernel the usb displaylink stopped working. > After reading this thread I tried 3.11.0-031100-generic as well which > didn't work for me. > > Here a summary of my settings > > $ cat /etc/modprobe.d/blacklist-framebuffer | grep udl You won an useless use of cat award :-). http://partmaps.org/era/unix/award.html > #blacklist udl > blacklist udlfb Same settings here. > > $ cat /etc/modprobe.d/udlfb.conf > options udlfb fb_defio=1 This file doesn't exist on my system, but since udlfb is blacklisted, it shouldn't matter. Do you have a /dev/fbX device for the DisplayLink? Does /var/log/Xorg.log.0 give any information about what goes wrong? Best, Nikolaus -- Encrypted emails preferred. PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C »Time flies like an arrow, fruit flies like a Banana.« -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
When reporting this bug, I called it a regression because an older kernel package worked, but a more recent one did not. I did not realize that the older one was mainline, and the later one with Ubuntu patches. The system runs Ubuntu raring. Since raring comes with a 3.8, which I believe does not fully support the DL-195, I installed a 3.11 kernel from Saucy (but nothing else). When at some later point I updated to a more recent Saucy kernel (apparently this time including Ubuntu patches), things stopped working. So yes, I would say it's possible that this has never worked in Ubuntu but only in mainline. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Bug is also present in Linux version 3.9.0-0-generic (buildd@panlong) (gcc version 4.8.0 (Ubuntu 4.8.0-4ubuntu1) ) #1-Ubuntu SMP Fri Apr 26 15:36:25 UTC 2013 That seems to be the earliest saucy kernel available. Which version(s) should I try next? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Bug is also present in Linux version 3.10.0-0-generic (buildd@roseapple) (gcc version 4.8.1 (Ubuntu 4.8.1-4ubuntu2) ) #6-Ubuntu SMP Mon Jun 24 19:38:38 UTC 2013 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Bug is also present in Linux version 3.10.0-5-generic (buildd@panlong) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-7ubuntu1) ) #14-Ubuntu SMP Mon Jul 22 15:23:30 UTC 2013 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
There doesn't seem to be anything available for download on https://launchpad.net/ubuntu/+source/linux/3.10.0-3.12. I randomly tried https://launchpad.net/ubuntu/+source/linux/3.10.0-5.14 but couldn't find any .debs there either. Are you sure these links are working? I believe there were some important upstream fixes for the udl driver in (upstream) 3.11, so I would not expect any Ubuntu kernels to work that were based on upstream < 3.11. So maybe things got broken right away on the rebase? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Bug is present in Linux version 3.11.0-1-generic (buildd@roseapple) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-8ubuntu1) ) #4-Ubuntu SMP Fri Aug 9 02:29:21 UTC 2013 Is it possible that this never worked with the Ubuntu kernels but only with the mainline kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Bug found in: Linux version 3.11.0-12-generic (buildd@allspice) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7) ) #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Bug found in: Linux version 3.11.0-9-generic (buildd@allspice) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu3) ) #16-Ubuntu SMP Fri Sep 27 15:08:11 UTC 2013 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Well, from my comments above the only version buggy kernel is the current saucy release (3.11.0-11-generic). Everything else I tested is good (3.11.0-031100-generic, 3.11.1-031101-generic, 3.11.2-031102-generic). I'm mightily confused by the version numbering though. Shouldn't the 3.11.1-0xx versions be more recent than the 3.11.0-11 kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
This is quite confusing, the 3.11.0-11-generic kernel trat I tried first did not come with an -extra package. In any case, installing the -extra package did not make a difference, the problem still occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
This version does not fix the bug. [0] nikratio@thinkpad:~$ uname -a Linux thinkpad 3.11.0-11-generic #17~lp1234818Commitcd6e935Reverted SMP Mon Oct 7 21:09:34 UTC 20 x86_64 x86_64 x86_64 GNU/Linux [0] nikratio@thinkpad:~$ grep EE /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 9.043] Initializing built-in extension MIT-SCREEN-SAVER [ 9.047] (EE) open /dev/dri/card1: Resource temporarily unavailable (I only installed -image, not -headers, -tools, or -image-extra. I assume this wouldn't make a difference?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
3.11.1-031101-generic is still working (my X11 looks really weird with it, but that's probably a separate issue) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
The first link seems to point to the kernel where I originally found the problem (at least the .deb file name is identical), so I'll just test the other two kernels and report back. Is that what what you wanted me to do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
3.11.2-031102-generic is still working too (and here my X11 is looking good again as well). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
..and 3.11.0-11-generic is still failing with "Resource not available" (just to reconfirm). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
These were all the results. Please let me know if you want me to do other tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234827] [NEW] Incorrectly claims that mainline kernel is running
Public bug reported: I'm trying to report a bug against an Ubuntu kernel, but apport won't let me do it and keeps claiming that I'm running a mainline kernel. I have indeed *installed* a mainline kernel to test if the problem exists there as well, but I'm definitely not running it at the moment. $ cat /proc/version Linux version 3.11.0-031100-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201309021735 SMP Mon Sep 2 21:36:21 UTC 2013 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: apport 2.9.2-0ubuntu8.3 Uname: Linux 3.11.0-031100-generic x86_64 ApportLog: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashReports: 644:0:110:0:2013-10-01 10:41:20.456300504 -0700:2013-10-01 10:41:20.456300504 -0700:/var/crash/_usr_bin_Xorg.0.upload 640:0:110:10433306:2013-10-01 10:41:13.452197790 -0700:2013-10-01 10:41:14.452197790 -0700:/var/crash/_usr_bin_Xorg.0.crash Date: Thu Oct 3 09:51:17 2013 InstallationDate: Installed on 2013-08-02 (62 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234827 Title: Incorrectly claims that mainline kernel is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1234827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "working-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857779/+files/working-dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "broken-dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857791/+files/broken-dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "working-lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857780/+files/working-lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "broken-version.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857794/+files/broken-version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] [NEW] Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
Public bug reported: My Plugable UGA-2K-A USB 2.0 to DVI adapter (using chipset DisplayLink DL-195, USB ID 17e9:4302) works fine with 3.11.0-031100-generic. However, when upgrading to 3.11.0-11-generic, X11 fails to open the DRI device with [ 8.868] (EE) open /dev/dri/card1: Resource temporarily unavailable Reverting to 3.11.0-031100-generic fixes the problem. Upgrading to current mainline (3.12.0-999.201310030405) also fixes the problem (but causes lots of kernel BUG messages). In both cases, the kernel correctly creates the /dev/fb1 and /dev/dri/card1 devices. There are no error messages in the kernel log. I can bisect this if someone tells me where to find the intermediate versions. ** Affects: linux-meta (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/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "working-version.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857782/+files/working-version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "broken-uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857793/+files/broken-uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "working-uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857781/+files/working-uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
** Attachment added: "broken-lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857792/+files/broken-lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234818 Title: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575156] Re: fuser output is scattered between stderr and stdout
It might be deliberate, but is there any good reason for it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/575156 Title: fuser output is scattered between stderr and stdout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/575156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213338] Re: Displaylink slow graphic performance on Ubuntu 13
FWIW, you can work around the problem by using e.g. XFCE instead of unity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213338 Title: Displaylink slow graphic performance on Ubuntu 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1213338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223514] Re: autopkgtest failure: Tests fails to import s3ql python modules
Fixed in Debian. Thanks for the report! ** Changed in: s3ql (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223514 Title: autopkgtest failure: Tests fails to import s3ql python modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1223514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215882] Re: Emails are silently discarded on 554 reply to STARTTLS
** Bug watch added: Mozilla Bugzilla #909438 https://bugzilla.mozilla.org/show_bug.cgi?id=909438 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=909438 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215882 Title: Emails are silently discarded on 554 reply to STARTTLS To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1215882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215882] [NEW] Emails are silently discarded on 554 reply to STARTTLS
Public bug reported:
It seems that emails are silently discarded when the remote SMTP server
replies with an error on STARTTLS. Here is an example smtp log created
with NSPR_LOG_MODULES='smtp:5,timestamp':
2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to:
mail.trialphaenergy.com
2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013
04:10:25 -0700
2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state: 14
2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO
[10.11.206.9]
2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response:
250-mail.trialphaenergy.com Hello [10.11.10.19]
2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response: 250-SIZE
2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response:
250-PIPELINING
2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response: 250-DSN
2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response:
250-ENHANCEDSTATUSCODES
2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response:
250-STARTTLS
2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response:
250-AUTH NTLM
2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response:
250-8BITMIME
2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response:
250-BINARYMIME
2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250
CHUNKING
2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state: 4
2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state: 21
2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state: 19
2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state: 21
2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
The UI, however, gives no indication of failure and closes the compose window
after the apparent successful submission to the smtp server.
If the user has not configured a Sent folder this results in data loss. Even if
the user has configured a sent folder, he receives no indication that the email
has not been sent.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikratio 2425 F pulseaudio
BuildID: 20130803220711
Channel: Unavailable
Date: Fri Aug 23 13:05:30 2013
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-07-30 (23 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PrefSources:
prefs.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
Prefs:
extensions.lastAppVersion: "17.0.8" (prefs.js)
network.cookie.prefsMigrated: true (prefs.js)
places.database.lastMaintenance: 1377252192 (prefs.js)
places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
privacy.donottrackheader.enabled: true (prefs.js)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion
Re: [Bug 1177094] Re: transport endpoint not connected when using s3ql with metadata-upload-interval 0
On 05/28/2013 01:04 PM, Sarah Angelini wrote:
> We are indeed using the PPA as the source of the S3QL package. Upon
> installation of version 1.15, I encountered this error message:
>
> SyntaxError: ('invalid syntax',
> ('/usr/lib/pymodules/python2.6/s3ql/mount.py', 251, 50, 'with
> tempfile.NamedTemporaryFile() as tmp, \\\n'))
>
> I suspect there's a typo, but I'm not clear on what needs fixing.
No, that's because Lucid only comes with Python 2.6. Getting S3QL to run
on such an old Python isn't officially supported and requires some
compatibility workarounds.
I just uploaded a new version (1.15-1~lucid2) to the PPA, hopefully this
will fix the remaining issues.
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1177094
Title:
transport endpoint not connected when using s3ql with metadata-upload-
interval 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1177094/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177094] Re: transport endpoint not connected when using s3ql with metadata-upload-interval 0
Ubuntu Lucid doesn't ship with an s3ql package, so the used package probably comes from the S3QL PPA (https://launchpad.net/~nikratio/+archive/s3ql). The PPA has just been updated to the new 1.15 upstream release which fixes the problem reported above. This bug can thus be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177094 Title: transport endpoint not connected when using s3ql with metadata-upload- interval 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1177094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179281] Re: Data corruption with eglibc 2.17
Tested s3ql_1.12-1ubuntu0.1 on amd64 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179281 Title: Data corruption with eglibc 2.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179281] Re: Data corruption with eglibc 2.17
Thanks Julian! Relevant upstream bug is http://code.google.com/p/s3ql/issues/detail?id=399 ** Bug watch added: code.google.com/p/s3ql/issues #399 http://code.google.com/p/s3ql/issues/detail?id=399 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179281 Title: Data corruption with eglibc 2.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179281] Re: Data corruption with eglibc 2.17
** Description changed: [Impact] + + The S3QL package in raring destroys user data. There is a bug in src/s3ql/_deltadump.pyx, which repositions a file descriptor associated with a FILE* stream without first calling fflush(). When using eglibc 2.17, this means that s3ql will store malformed metadata that cannot be loaded again (with prior eglibc versions the bug does not appear, which is probably why it hasn't been found until now). The problem is made worse because this affects only the metadata uploaded to the remote server, but not the locally cached copy. So unless the user explicitly tests reloading the metadata from the server, the corruption will not show up until it's too late. The attached patch fixes the problem by adding the missing fflush() call. [Test Case] * The bug is detected by S3QL unit tests, so running "setup.py test" will fail with $ ./setup.py test [...] == ERROR: test_1_vals_1 (__main__.DumpTests) -- Traceback (most recent call last): File "t1_dump.py", line 36, in test_1_vals_1 self.compare_tables(self.src, self.dst) File "t1_dump.py", line 155, in compare_tables (id2, buf2) = i2.next() File "/usr/lib/s3ql/s3ql/database.py", line 250, in next for col in self.cur.next() ] StopIteration + The unit tests are run automatically by debian/rules. This bug only made + it into the release because (presumably) S3QL was build before eglibc + was updated to 2.17. + [Regression Potential] * The patch effects the writing and reading of data from a binary dump file into an SQLite database. Any regression would thus be restricted to the initial reading, or final dumping of the data. While this makes testing easier, it also means that any regressions will probably make the entire program unusable. [Other Info] * The same patch has already been applied to the S3QL 1.11 debian package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179281 Title: Data corruption with eglibc 2.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179281] Re: Data corruption with eglibc 2.17
** Attachment added: "debdiff2.txt" https://bugs.launchpad.net/debian/+source/s3ql/+bug/1179281/+attachment/3674778/+files/debdiff2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179281 Title: Data corruption with eglibc 2.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179281] Re: Data corruption with eglibc 2.17
** Description changed: + [Impact] + There is a bug in src/s3ql/_deltadump.pyx, which repositions a file descriptor associated with a FILE* stream without first calling - fflush(). When using eglibc 2.17, this means that s3ql will store malformed metadata that cannot be loaded again. The problem is made worse because this affects only the metadata uploaded to the remote server, but not the locally cached copy. So unless the user explicitly tests reloading the metadata from the server, the corruption will not show up until it's too late. + fflush(). When using eglibc 2.17, this means that s3ql will store malformed metadata that cannot be loaded again (with prior eglibc versions the bug does not appear, which is probably why it hasn't been found until now). + + The problem is made worse because this affects only the metadata + uploaded to the remote server, but not the locally cached copy. So + unless the user explicitly tests reloading the metadata from the server, + the corruption will not show up until it's too late. + + The attached patch fixes the problem by adding the missing fflush() + call. + + + [Test Case] + + * The bug is detected by S3QL unit tests, so running "setup.py test" + will fail with + + $ ./setup.py test + [...] + == + ERROR: test_1_vals_1 (__main__.DumpTests) + -- + Traceback (most recent call last): + File "t1_dump.py", line 36, in test_1_vals_1 + self.compare_tables(self.src, self.dst) + File "t1_dump.py", line 155, in compare_tables + (id2, buf2) = i2.next() + File "/usr/lib/s3ql/s3ql/database.py", line 250, in next + for col in self.cur.next() ] + StopIteration + + + [Regression Potential] + + * The patch effects the writing and reading of data from a binary dump + file into an SQLite database. Any regression would thus be restricted to + the initial reading, or final dumping of the data. While this makes + testing easier, it also means that any regressions will probably make + the entire program unusable. + + [Other Info] + + * The same patch has already been applied to the S3QL 1.12 debian package. ** Description changed: [Impact] There is a bug in src/s3ql/_deltadump.pyx, which repositions a file descriptor associated with a FILE* stream without first calling fflush(). When using eglibc 2.17, this means that s3ql will store malformed metadata that cannot be loaded again (with prior eglibc versions the bug does not appear, which is probably why it hasn't been found until now). The problem is made worse because this affects only the metadata uploaded to the remote server, but not the locally cached copy. So unless the user explicitly tests reloading the metadata from the server, the corruption will not show up until it's too late. The attached patch fixes the problem by adding the missing fflush() call. - [Test Case] - * The bug is detected by S3QL unit tests, so running "setup.py test" + * The bug is detected by S3QL unit tests, so running "setup.py test" will fail with $ ./setup.py test [...] == ERROR: test_1_vals_1 (__main__.DumpTests) -- Traceback (most recent call last): - File "t1_dump.py", line 36, in test_1_vals_1 - self.compare_tables(self.src, self.dst) - File "t1_dump.py", line 155, in compare_tables - (id2, buf2) = i2.next() - File "/usr/lib/s3ql/s3ql/database.py", line 250, in next - for col in self.cur.next() ] + File "t1_dump.py", line 36, in test_1_vals_1 + self.compare_tables(self.src, self.dst) + File "t1_dump.py", line 155, in compare_tables + (id2, buf2) = i2.next() + File "/usr/lib/s3ql/s3ql/database.py", line 250, in next + for col in self.cur.next() ] StopIteration + [Regression Potential] - [Regression Potential] - - * The patch effects the writing and reading of data from a binary dump + * The patch effects the writing and reading of data from a binary dump file into an SQLite database. Any regression would thus be restricted to the initial reading, or final dumping of the data. While this makes testing easier, it also means that any regressions will probably make the entire program unusable. [Other Info] - - * The same patch has already been applied to the S3QL 1.12 debian package. + + * The same patch has already been applied to the S3QL 1.11 debian + package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179281 Title: Data corruption with eglibc 2.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@list
[Bug 1179281] [NEW] Data corruption with eglibc 2.17
Public bug reported: There is a bug in src/s3ql/_deltadump.pyx, which repositions a file descriptor associated with a FILE* stream without first calling fflush(). When using eglibc 2.17, this means that s3ql will store malformed metadata that cannot be loaded again. The problem is made worse because this affects only the metadata uploaded to the remote server, but not the locally cached copy. So unless the user explicitly tests reloading the metadata from the server, the corruption will not show up until it's too late. ** Affects: s3ql (Ubuntu) Importance: Undecided Status: New ** Affects: s3ql (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #701350 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701350 ** Also affects: s3ql (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701350 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179281 Title: Data corruption with eglibc 2.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
** Patch added: "Patch against debian package" https://bugs.launchpad.net/qemu/+bug/1033727/+attachment/3482404/+files/qemu-debian.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Thanks a lot Peter! I can confirm that this patch fixes the problems when added on top of Debian's qemu-kvm 1.1.2+dfsg-4 package. I have attached a patch against the Debian git tree. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 814777] Re: Occassional mouse cursor corruption on primary display
Bryce, why did you set this to "Fix Released"? The problem is still experienced by multiple users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/814777 Title: Occassional mouse cursor corruption on primary display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/814777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037192] Re: NFS shares are mounted with wrong clientaddr or not at all
Ah, so if we manually emit a net-device-up event after the ifconfig call (or better, call the hooks in if-up.d), everything should integrate well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037192 Title: NFS shares are mounted with wrong clientaddr or not at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037192] Re: NFS shares are mounted with wrong clientaddr or not at all
How would tinc need to behave for compatibility? I was assuming that udev would automatically generate a net-dev up event when the tun interface comes up, and that nothing else would be necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037192 Title: NFS shares are mounted with wrong clientaddr or not at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037192] Re: NFS shares are mounted with wrong clientaddr or not at all
No, tinc has a separate initscript in /etc/init.d. During startup, tinc executes "ifconfig $INTERFACE $IP netmask 255.255.255.0", where $INTERFACE is a tun interface created by tinc. Will gather the debugging logs as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037192 Title: NFS shares are mounted with wrong clientaddr or not at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037192] [NEW] NFS shares are mounted with wrong clientaddr or not at all
Public bug reported: With the following fstab: proc /proc proc nodev,noexec,nosuid 0 0 /dev/mapper/vg0-fat_client / ext4 relatime,errors=remount-ro 0 1 /dev/mapper/vg0-swap none swap sw 0 0 spitzer:/opt /opt nfs4 auto 0 0 spitzer:/home /home nfs4 auto 0 0 The /opt and /home are sometimes not mounted at all, and sometimes with the wrong clientaddr: $ mount | grep nfs rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) spitzer:/home on /home type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2) spitzer:/opt on /opt type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2) Since this happens on all clients (they all get same clientaddr), this results in a frozen mount (cf http://thread.gmane.org/gmane.linux.nfs/47780) The "spitzer" host is only reachable via a tinc VPN, and mounting (or remounting) manually after boot always works and results in the correct clientaddr, so I believe that mountall is attempting to mount this too early. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mountall 2.15.3 ProcVersionSignature: Ubuntu 3.0.0-23.39~lucid1-server 3.0.36 Uname: Linux 3.0.0-23-server x86_64 Architecture: amd64 Date: Wed Aug 15 12:16:17 2012 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mountall ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037192 Title: NFS shares are mounted with wrong clientaddr or not at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037192] Re: NFS shares are mounted with wrong clientaddr or not at all
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037192 Title: NFS shares are mounted with wrong clientaddr or not at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1037192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Dependency loops due to ANDed start conditions leave system unbootable
Update: sometimes, /opt and /home are also not mounted at all with the above configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Dependency loops due to ANDed start conditions leave system unbootable
fstab looks like this: proc/proc procnodev,noexec,nosuid 0 0 /dev/mapper/vg0-fat_client / ext4 relatime,errors=remount-ro 0 1 /dev/mapper/vg0-swapnoneswapsw 0 0 spitzer:/opt /optnfs4auto 0 0 spitzer:/home /home nfs4auto 0 0 With this setup, /opt and /home are mounted by mountall, however, they are mounted with the wrong clientaddr: $ mount | grep nfs rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) spitzer:/home on /home type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2) spitzer:/opt on /opt type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2) Since this happens on all clients (they all get same clientaddr), this results in a frozen mount (cf http://thread.gmane.org/gmane.linux.nfs/47780) If I remount manually, the clientaddr is correct, so I believe mountall is attempting to mount this too early. Should I report this as a separate bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Dependency loops due to ANDed start conditions leave system unbootable
Things aren't quite that simple. /home is an NFS mount transported over VPN, and mountall generally dosn't mount it (presumably because the VPN isn't up quickly enough). It nevertheless happily emits the "filesystem" event. We tried solving the problem by adding the explicit "mounted" event and starting a third mountall run. So is the real problem here that mountall emits "filesystem" even if it didn't mount all of them? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Dependency loops due to ANDed start conditions leave system unbootable
I think this bug can be considered triaged. It would be great if someone with the necessary permissions could update the status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot
Ok, here's my theory of what happens: I noticed that if you have a very simple upstart job: # cat /etc/init/test.conf start on niko-a and niko-b script sleep 10 end script and then emit niko-a without --no-wait: # initctl emit niko-a then this call blocks until niko-b is emitted as well. Now if mountall tries to emit the mounted event without --no-wait as well, this would block, because GDM is still waiting for other events before it can start (e.g. dbus or drm-device-added). However, these events cannot be emitted until mountall has finished, which it can't, because it's waiting for GDM to start. I don't know if this is a bug in upstart (that should somehow accomodate such chains caused by ANDed starting conditions) or mountall, because it should not wait for the events to be processed. (Tested on Ubuntu 10.04) ** Summary changed: - Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot + Dependency loops due to ANDed start conditions leave system unbootable ** Also affects: mountall (Ubuntu) Importance: Undecided Status: New ** Changed in: mountall (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1027122] Re: JNI applications fail because shared libraries cannot be found
Hi Steve, I can give you a shell account on a server affected by the problem. Would that help? If so, please send me an ssh key. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027122 Title: JNI applications fail because shared libraries cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027122] Re: JNI applications fail because shared libraries cannot be found
I tried running NativeTest.java from bug 737603 with the same environment variables that are used for the jScope invocation (exept the classtpath): Before the upgrade: $ LD_LIBRARY_PATH=:/opt/hbt/valen/lib/i686/:/opt/mdsplus//lib SHLIB_PATH=:/opt/mdsplus//lib DYLD_LIBRARY_PATH=:/opt/mdsplus//lib /usr/bin/java -Xmx128M NativeTest JavaMds java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk/jre/../lib/amd64::/opt/hbt/valen/lib/i686/:/opt/mdsplus//lib:/usr/java/packages/lib/amd64:/usr/lib/jni:/lib:/usr/lib sun.boot.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/amd64 System.mapLibraryName(): libJavaMds.so After the upgrade: $ LD_LIBRARY_PATH=:/opt/hbt/valen/lib/i686/:/opt/mdsplus//lib SHLIB_PATH=:/opt/mdsplus//lib DYLD_LIBRARY_PATH=:/opt/mdsplus//lib /usr/bin/java -Xmx128M NativeTest JavaMds java.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk/jre/../lib/amd64::/opt/hbt/valen/lib/i686/:/opt/mdsplus//lib:/usr/java/packages/lib/amd64:/usr/lib/jni:/lib:/usr/lib sun.boot.library.path: /usr/lib/jvm/java-6-openjdk/jre/lib/amd64 System.mapLibraryName(): libJavaMds.so Exception in thread "main" java.lang.UnsatisfiedLinkError: /opt/mdsplus/lib/libJavaMds.so: libhpi.so: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1750) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1675) at java.lang.Runtime.loadLibrary0(Runtime.java:840) at java.lang.System.loadLibrary(System.java:1047) at NativeTest.main(NativeTest.java:6) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027122 Title: JNI applications fail because shared libraries cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027122] Re: JNI applications fail because shared libraries cannot be found
** Attachment added: "jScope stdout&stderr with -verbose:jni" https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+attachment/3235343/+files/jScope.out ** Changed in: openjdk-6 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027122 Title: JNI applications fail because shared libraries cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027122] Re: JNI applications fail because shared libraries cannot be found
Hi Steve, Thanks for your efforts! Our MDSplus installation has been compiled from source. I have attached the strace output as well as the debugging output. ** Attachment added: "strace output" https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+attachment/3235341/+files/jScope.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027122 Title: JNI applications fail because shared libraries cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614747] Re: JDowloader is closed suddenly
*** This bug is a duplicate of bug 612385 *** https://bugs.launchpad.net/bugs/612385 ** This bug has been marked a duplicate of bug 612385 jdownloader crashes regularily because of insufficient memory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/614747 Title: JDowloader is closed suddenly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/614747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027122] Re: JNI applications fail because shared libraries cannot be found
** Description changed: - One of the last updates to openjdk in Lucid broke JNI applications. - Attempts to run a JNI application now crash with: + The update from OpenJDK 6b20-1.9.13-0ubuntu1~10.04.1 to + 6b21.2-2ubuntu0.10.04.1 in Lucid broke JNI applications. Attempts to run + a JNI application now crash with: $ jScope Load library java.lang.UnsatisfiedLinkError: /opt/mdsplus/lib/libJavaMds.so: libhpi.so: cannot open shared object file: No such file or directory java.lang.UnsatisfiedLinkError: /opt/mdsplus/lib/libJavaMds.so: libhpi.so: cannot open shared object file: No such file or directory - at java.lang.ClassLoader$NativeLibrary.load(Native Method) - at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1750) - at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1675) - at java.lang.Runtime.loadLibrary0(Runtime.java:840) - at java.lang.System.loadLibrary(System.java:1047) - at jScope.LocalDataProvider.(LocalDataProvider.java:192) - at java.lang.Class.forName0(Native Method)/ - at java.lang.Class.forName(Class.java:186) - at jScope.jScopeWaveContainer.SetDataServer(jScopeWaveContainer.java:1360) + at java.lang.ClassLoader$NativeLibrary.load(Native Method) + at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1750) + at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1675) + at java.lang.Runtime.loadLibrary0(Runtime.java:840) + at java.lang.System.loadLibrary(System.java:1047) + at jScope.LocalDataProvider.(LocalDataProvider.java:192) + at java.lang.Class.forName0(Native Method)/ + at java.lang.Class.forName(Class.java:186) + at jScope.jScopeWaveContainer.SetDataServer(jScopeWaveContainer.java:1360) + + Downgrading all packages created by the OpenJDK source package to + 6b20-1.9.13-0ubuntu1~10.04.1 fixes the problem. libhpi.so is located in /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads/libhpi.so, so the problem can be temporarily fixed by setting LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads/. However, this path is of course very dependent on the used JRE, so it needs to be set by java itself. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openjdk-6-jre-headless 6b24-1.11.3-1ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 3.0.0-23.38~lucid1-server 3.0.36 Uname: Linux 3.0.0-23-server x86_64 Architecture: amd64 Date: Fri Jul 20 11:11:48 2012 ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: openjdk-6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027122 Title: JNI applications fail because shared libraries cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027122] Re: JNI applications fail because shared libraries cannot be found
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027122 Title: JNI applications fail because shared libraries cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027122] [NEW] JNI applications fail because shared libraries cannot be found
Public bug reported: One of the last updates to openjdk in Lucid broke JNI applications. Attempts to run a JNI application now crash with: $ jScope Load library java.lang.UnsatisfiedLinkError: /opt/mdsplus/lib/libJavaMds.so: libhpi.so: cannot open shared object file: No such file or directory java.lang.UnsatisfiedLinkError: /opt/mdsplus/lib/libJavaMds.so: libhpi.so: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1750) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1675) at java.lang.Runtime.loadLibrary0(Runtime.java:840) at java.lang.System.loadLibrary(System.java:1047) at jScope.LocalDataProvider.(LocalDataProvider.java:192) at java.lang.Class.forName0(Native Method)/ at java.lang.Class.forName(Class.java:186) at jScope.jScopeWaveContainer.SetDataServer(jScopeWaveContainer.java:1360) libhpi.so is located in /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads/libhpi.so, so the problem can be temporarily fixed by setting LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads/. However, this path is of course very dependent on the used JRE, so it needs to be set by java itself. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openjdk-6-jre-headless 6b24-1.11.3-1ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 3.0.0-23.38~lucid1-server 3.0.36 Uname: Linux 3.0.0-23-server x86_64 Architecture: amd64 Date: Fri Jul 20 11:11:48 2012 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openjdk-6 ** Affects: openjdk-6 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027122 Title: JNI applications fail because shared libraries cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1027122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Hanging mountall stops boot process
Since this is triggered by changing an upstart job unrelated to mountall, I'm reassigning this to upstart. ** Description changed: - One of my Lucid systems stopped booting. If I interpret the "initctl - list" output correctly (attached) the system is waiting for mountall to - complete. + If /home is mounted on a separate partition, and the gdm start condition + in /etc/init/gdm.conf is modified to include "mounted MOUNTPOINT=/home" + as follows: - mountall, however, seems just stuck doing nothing. I added --verbose to - /etc/init/mountall.conf and redirected the output into a file (attached - as well). + start on (filesystem + and mounted MOUNTPOINT=/home + and started dbus + and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 +or stopped udevtrigger)) - If I execute another "mountall --verbose", this one seems to complete - and the system continues booting. I have attached the output of this - second run as well. + then a lucid system will no longer boot. It seems that in this case the + mountall process is waiting for input from upstart, but upstart is not + sending anything. Thus, the required muntall events are not emitted and + the system refuses to boot. + + The problem can be worked around by manually starting another mountall + instance while the first instance is hanging. + + I have attached the --verbose output of the first and second mountall, as + well as an strace output. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mountall 2.15.3 ProcVersionSignature: Ubuntu 3.0.0-17.30~lucid1-server 3.0.22 Uname: Linux 3.0.0-17-server x86_64 Architecture: amd64 Date: Sat Mar 24 18:45:46 2012 ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: mountall ** Package changed: mountall (Ubuntu) => upstart (Ubuntu) ** Summary changed: - Hanging mountall stops boot process + Waiting for mounted MOUNTPOINT=/home in gdm.conf breaks system boot ** Summary changed: - Waiting for mounted MOUNTPOINT=/home in gdm.conf breaks system boot + Waiting for "mounted MOUNTPOINT=/home in gdm.conf" breaks system boot ** Summary changed: - Waiting for "mounted MOUNTPOINT=/home in gdm.conf" breaks system boot + Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 642119] Re: mountall not actually mounting and blocking boot
*** This bug is a duplicate of bug 964207 *** https://bugs.launchpad.net/bugs/964207 ** This bug has been marked a duplicate of bug 964207 Hanging mountall stops boot process -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/642119 Title: mountall not actually mounting and blocking boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/642119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Hanging mountall stops boot process
I added an additional strace -f to mountall.conf as well, this is the output. ** Attachment added: "strace -f output for upstarted started mountall" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+attachment/2931546/+files/strace.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Hanging mountall stops boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Hanging mountall stops boot process
** Attachment added: "Output of second, manually started mountall" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+attachment/2931399/+files/mountall2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Hanging mountall stops boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Hanging mountall stops boot process
** Attachment added: "Output of upstart started mountall" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+attachment/2931398/+files/mountall.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Hanging mountall stops boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964207] Re: Hanging mountall stops boot process
** Attachment added: "initctl list output for hanging system" https://bugs.launchpad.net/bugs/964207/+attachment/2931396/+files/initctl-list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Hanging mountall stops boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
