[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Super, I was just looking for a way to build kernels in a Docker container. Maybe the Docker image could be modified to build dwarves for itself at some point. I think you can request more space for a PPA from launchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Still seeing this spurious libc 2.33 dependency (I *assume* it's not the kernel people who decide to change their libc policy in the middle of a release series -- so it's spurious) in 5.10.35. Are the Ubuntu / Canonical people notified? I'm not sure who takes care of this "Mainline PPA" (which doesn't seem to have a Launchpad presence, but just a website with build products). Is there anyone to CC on Launchpad, so that we may get some more or less official answer? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
It would be unfortunate for the "LTS" kernel version to not be installable on LTS Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631088] Re: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable
Aha, it's Teh Apparmor. Edit /etc/apparmor.d/usr.bin.evince and add /**.[tT][tT][fF] rw, after the other supported formats (bmp, djvu etc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631088 Title: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/631088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631088] Re: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable
Still not working in 14.04. Strangely, using "strace -eopen evince" I can see that an open() system call returns EACCES, even though from the shell I can access the symlink (and its target) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631088 Title: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/631088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396048] Re: Evince misses font and only displays squares in menus
For me it seems to happen with symlinks from /usr/share/fonts to a different partition -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396048 Title: Evince misses font and only displays squares in menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443213] Re: Data corruption with msgpack <= 0.4.5, >= 0.4.2 -- upgrade to 0.4.6
Also, https://github.com/msgpack/msgpack-python/issues/97 and apparently https://github.com/msgpack/msgpack-python/issues/101 The original report refers to 124, which only affects the pure python implementation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443213 Title: Data corruption with msgpack <= 0.4.5, >= 0.4.2 -- upgrade to 0.4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msgpack-python/+bug/1443213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443213] Re: Data corruption with msgpack <= 0.4.5, >= 0.4.2 -- upgrade to 0.4.6
Also, https://github.com/msgpack/msgpack-python/issues/114 (fixed in 0.4.3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443213 Title: Data corruption with msgpack <= 0.4.5, >= 0.4.2 -- upgrade to 0.4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msgpack-python/+bug/1443213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443213] [NEW] Data corruption with msgpack <= 0.4.5, >= 0.4.2 -- upgrade to 0.4.6
Public bug reported: Please upgrade to 0.4.6 to avoid data corruption: https://github.com/msgpack/msgpack-python/issues/124 Utopic also needs the upgrade. ** Affects: msgpack-python (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443213 Title: Data corruption with msgpack <= 0.4.5, >= 0.4.2 -- upgrade to 0.4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msgpack-python/+bug/1443213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411757] Re: update to latest msgpack-python release
Update to 0.4.6, because 0.4.2 (the current Vivid version) to 0.4.5 have DATA CORRUPION bugs: https://github.com/msgpack/msgpack- python/issues/124 ** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411757 Title: update to latest msgpack-python release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msgpack-python/+bug/1411757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245474] Re: [regression] on login screen, monitor stays on forever
This seems to have been fixed in unity-greeter, but not lightdm-gtk- greeter. And in any case, how can the unity-greeter inactivity timeout be tuned? gsettings under the lightdm account? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245474 Title: [regression] on login screen, monitor stays on forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1245474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
I'm seeing this with linux-lowlatency-lts-utopic... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
Sorry, this is on Trusty amd64, with linux-lowlatency-lts-utopic 3.16.0.31.24 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
The vivd package *still* doesn't provide opencl-icd, so after installing fglrx, python-pyopencl tries to pull in beignet... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Trusty was affected too by the Conflicts: thing; I've been running manually-patched fglrx drivers for a while now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
This is... nightmarish. @nukedathlonman, why don't you state clearly which package needs to be compiled and what needs to be modified in debian/control? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 682604] Re: Plymouth hangs after successful resume from from hibernation with uswsusp
With encrypted resume it's even worse, because you can't enter the passphrase since plymouth hogs the screen and keyboard. 'plymouth quit' as in #11 indeed solves the problem. CAN SOMEONE PATH uswsusp PLEASE? Also, it seems uswsusp is really old and unsupported; is it possible to get compressed, encrypted hibernation without uswsusp (i.e. with pm- utils using the kernel method)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682604 Title: Plymouth hangs after successful resume from from hibernation with uswsusp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/682604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574773] Re: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart)
Still a problem on Trusty (!), fixed with /etc/init.d/screen-cleanup start. screen == 4.1.0~20120320gitdb59704-9 It seems screen-cleanup is not activated by default in rc.d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574773 Title: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/574773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315898] Re: Light-Locker not working in Lubuntu 14.04
I can't get light-locker to do anything at all. No matter how long my laptop sits unused, there is no blanking of the screen and no locking. This is on a vanilla Lubuntu 14.04 install (and ps confirms light-locker is running) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315898 Title: Light-Locker not working in Lubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1315898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513644] Re: Does not log fsck invocations in /var/log/fsck/
Even on MS Windows you can dig out fsck messages with the eventviewer. This is stupid, lazy and arrogant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/513644 Title: Does not log fsck invocations in /var/log/fsck/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/513644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992068] Re: [needs-packaging] broken in 12.04 and 12.10: libtorsocks: many symbols not found
I've backported a 1.3-3 from saucy (!) in my PPA (https://launchpad.net/~danmbox/+archive/ppa). I still get a bunch of junk: 13:31:17 libtorsocks(28806): WARNING: The symbol res_query() was not found in any shared library with the reported error: Not Found! Also, we failed to find the symbol __res_query() with the reported error: Not Found 13:31:17 libtorsocks(28806): WARNING: The symbol res_search() was not found in any shared library with the reported error: Not Found! Also, we failed to find the symbol __res_search() with the reported error: Not Found 13:31:17 libtorsocks(28806): WARNING: The symbol res_send() was not found in any shared library with the reported error: Not Found! Also, we failed to find the symbol __res_send() with the reported error: Not Found 13:31:17 libtorsocks(28806): WARNING: The symbol res_querydomain() was not found in any shared library with the reported error: Not Found! Also, we failed to find the symbol __res_querydomain() with the reported error: Not Found that makes stderr unreadable. This is kind of important, because the only way to get rid of the junk is to redirect stderr, but in that case you lose all errors. Is this the same bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992068 Title: [needs-packaging] broken in 12.04 and 12.10: libtorsocks: many symbols not found To manage notifications about this bug go to: https://bugs.launchpad.net/torsocks/+bug/992068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244023] [NEW] pycuda 2012.1-1ubuntu2~ubuntu12.04.1 depends on nvidia-current
Public bug reported: You don't have to depend on nvidia-current just to ensure nvidia. Some people have nvidia-319, nvidia-319-updates etc. ** Affects: pycuda (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/1244023 Title: pycuda 2012.1-1ubuntu2~ubuntu12.04.1 depends on nvidia-current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycuda/+bug/1244023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243690] [NEW] Build-depend on xserver-xorg-dev-lts-raring and similar
Public bug reported: Since I installed xserver-xorg-dev-lts-raring, I can't build some packages that insist on depending on xserver-xorg-dev. And due to a separate bug I can't change the Build-Depends: line, because debuild -S reverts my changes. I don't know how you accomplished that. But you should build-depend on xserver-xorg-dev (>= 2:1.4) | xserver-xorg-dev- lts-raring (>= 2:1.4) | xserver-xorg-dev-lts-quantal (>= 2:1.4), ** Affects: nvidia-graphics-drivers-319-updates (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/1243690 Title: Build-depend on xserver-xorg-dev-lts-raring and similar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1243690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243683] [NEW] can't change Build-Depends: line (debuild -S reverts changes)
Public bug reported: When modifying the build-depends line in debian/control for http://packages.ubuntu.com/saucy/nvidia-319-updates, any changes are reverted by debuild -S. How did you manage to accomplish this amazingly useful effect? ** Affects: nvidia-graphics-drivers-319-updates (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/1243683 Title: can't change Build-Depends: line (debuild -S reverts changes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1243683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 763457] Re: please provide opencl-icd virtual package
In my PPA (https://launchpad.net/~danmbox/+archive/ppa) I've tried backporting ocl-icd_2.0.2-1ubuntu1 (after backporting khronos-opencl- headers), but it's not compilable (weird warnings-turned-into-errors) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763457 Title: please provide opencl-icd virtual package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/763457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186786] Re: nvidia-173 kernel module fails to build on kernels >= 3.10.x [error: implicit declaration of function ‘create_proc_entry’]
Is anybody backporting (or at least THINKING about backporting) all these wonderful changes for us plebs on 12.04 LTS using the OFFICIAL linux-generic-lts-raring series, or do we no longer count as real users, despite LTS promises from Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186786 Title: nvidia-173 kernel module fails to build on kernels >= 3.10.x [error: implicit declaration of function ‘create_proc_entry’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1186786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
That was absolute bull. Ubuntu obviously ships with /etc/profile, which is a "version" of bash_profile, so #8 was a specious argument. And placing "profiley" stuff into bashrc slows down the shell (as if it's not slow enough already!) Some .xsessionrc file (or whatever is read by the *dm's) must make sure to read /etc/profile. If that is not done at the system level it must be recommended to users as the preferred workaround for this utter nonsense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17962 Title: newly opened gnome-terminal windows don't have .bash_profile sourced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/17962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
Brad, can you comment on the problems I've shown for 3.2 and 3.8 on precise -lts kernels? Do you want to push through those kernels and then have to deal with separate bugs. I know there's a lot of noise in this thread, but there were some relevant tests and errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
With linux-image-3.5.0-41-generic = 3.5.0-41.64~precise1 there are no Buffer I/O errors, either with mkswap or mkfs.ext2 With linux-image-3.2.0-54-generic = 3.2.0-54.82 the errors are the same as in linux-image-3.8.0-31-generic = 3.8.0-31.46~precise1 So the lts-quantal image is good, the others are not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
I've tested 3.8.0-31-generic (linux-image-3.8.0-31-generic = 3.8.0-31.46~precise1). To the admins: when asking us to test "the latest in -proposed", please tell us which package and which version. It makes it easier to interpret the record in the future, when the "latest in proposed" may be different (or when your proposed solution has been removed / replaced) I'm using the following test now: echo '4096 * 4096' | bc -l > /sys/block/zram0/disksize mkfs.ext2 /dev/zram0 And I get this with dmesg -T: [Sun Sep 22 23:05:40 2013] Buffer I/O error on device zram0, logical block 4095 [Sun Sep 22 23:05:40 2013] lost page write due to I/O error on zram0 [Sun Sep 22 23:05:40 2013] Buffer I/O error on device zram0, logical block 4095 I don't think this is a good kernel. In the terminology of https://lkml.org/lkml/2013/8/13/22, both [1] and [2] should be in the kernel, so that both bug A and bug B are fixed. I'll check how to find the changelog for a kernel and whether the other -proposed (3.2, 3.5) kernels also have the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228882] Re: nvidactl (misspelled) in /etc/apparmor.d/abstractions/ubuntu-browsers.d/multimedia all Ubuntu versions
@dino99, do you also have problems with flash or firefox? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228882 Title: nvidactl (misspelled) in /etc/apparmor.d/abstractions/ubuntu- browsers.d/multimedia all Ubuntu versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1228882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893056] Re: on livecd xdg-open failed with: /usr/bin/xdg-open: 364: /usr/bin/xdg-open: gnome-open: not found
Bug #893835 was incorrectly (in my opinion) marked as a duplicate of this. The problem in that case is that ubuntu-bug fails if the system- wide $BROWSER no longer exists. People in that situation cannot report bugs anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893056 Title: on livecd xdg-open failed with: /usr/bin/xdg-open: 364: /usr/bin/xdg- open: gnome-open: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/893056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 893835] Re: ubuntu-bug fails with "/usr/bin/xdg-open: 364: /usr/bin/xdg-open: gnome-open: not found"
*** This bug is a duplicate of bug 893056 *** https://bugs.launchpad.net/bugs/893056 This fails whenever $BROWSER can't be opened (e.g. when you set up the system-wide BROWSER to chromium-browser then uninstall chromium). This is not a good thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/893835 Title: ubuntu-bug fails with "/usr/bin/xdg-open: 364: /usr/bin/xdg-open: gnome-open: not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/893835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228882] [NEW] nvidactl (misspelled) in /etc/apparmor.d/abstractions/ubuntu-browsers.d/multimedia all Ubuntu versions
Public bug reported: /etc/apparmor.d/abstractions/ubuntu-browsers.d/multimedia mis-spells an nvidia device: # If we allow the above, nvidia based systems will also need these /dev/nvidactl rw, /dev/nvidia0 rw, (should of course be nvidiactl). This seems to be the case in all apparmor versions. I don't know if this affects anything. I can't watch Youtube videos in Firefox, and my fix doesn't improve the situation (there are probably other bugs) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apparmor 2.7.102-0ubuntu3.9 ProcVersionSignature: Ubuntu 3.8.0-31.23-lowlatency 3.8.13.8 Uname: Linux 3.8.0-31-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Sun Sep 22 18:37:58 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-lowlatency root=UUID=a7047dd8-61aa-4cbe-b36d-697a5e7ee64b ro SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apparmor.d.abstractions.ubuntu.browsers.d.multimedia: 2013-09-22T18:16:06.208483 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228882 Title: nvidactl (misspelled) in /etc/apparmor.d/abstractions/ubuntu- browsers.d/multimedia all Ubuntu versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1228882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
@Kenneth Parker: if your problem is that zram shows up EVEN AFTER dpkg --purge zram-config, please **file a separate bug**. Note that "service zram-config stop" stops zram after the system is up, which means it has already potentially damaged your system. What you want is for the zram module to never be modprobe'd at all. There is a blacklist solution in Bug #1217189, comment 45 that seems to work for me. [ On an unrelated note, thank you for sharing so much relevant information about your job, your skills and so on with us. ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
With 3.8.0-31-lowlatency, try this if you're willing to reboot: rmmod zram; modprobe zram; echo -n 6710 > /sys/block/zram0/disksize; mkswap /dev/zram0; dmesg -T | tail It will bring you into a state where you can't rmmod zram (!). # rmmod zram ERROR: Removing 'zram': Device or resource busy I see in dmesg: BUG: unable to handle kernel paging request at 6364652d I tried 6710 (16k+) after determining that with 67108864 I still get "Buffer I/O error on device zram0" at exactly the last zram0 block. This is a pretty serious problem. It looks like zram-related code is quite unstable. I'm not even sure if it's been fixed on the kernel mainline. A simple backport will probably not solve issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
Kenneth, zram-config is a red herring. Even if you purge it completely and set up zram manually, modprobe zram echo -n 67108864 > /sys/block/zram/size mkswap /dev/zram0 swapon /dev/zram0 You still get the error messages and eventually the lock-ups. This is not a script problem, it's a kernel problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
Since several bugs with much more details were merged into this one, the most likely early warning of zram problems are messages like Buffer I/O error on device zram0, logical block 257912 [repeated X times] You get those right after modprobing / formatting zram. If you don't see those with the new kernel, either things are in good shape or the bugfix didn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215513] Re: System locks up, requires hard reset
A week seems like an extremely short time, especially for ALL releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215513 Title: System locks up, requires hard reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218278] Re: When creating a swap device using zram I get Buffer I/O errors
*** This bug is a duplicate of bug 1217189 *** https://bugs.launchpad.net/bugs/1217189 I'm marking this as a duplicate of bug #1217189. I don't find @timg- tpi's comment very reassuring. This is a critical bug for the LTS release. ** This bug has been marked a duplicate of bug 1217189 Buffer I/O error on device zram0 (possibly causing complete machine lockup) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218278 Title: When creating a swap device using zram I get Buffer I/O errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
This bug also occurs on linux-lts-quantal, I think (I remember booting to a lts-quantal kernel after seeing the raring bug). There was a backport to zram on both branches that is causing this. Note that in Bug #1218278, Tim Gardner (timg-tpi) wrote at #19: "There will be a linux-lts-saucy shortly after 13.10 is released."; anyway, I'm marking that one as a duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3813003/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812997/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812998/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3813004/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3813000/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3813002/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812999/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3813001/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Card1.Amixer.values.txt
apport information ** Attachment added: "Card1.Amixer.values.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812995/+files/Card1.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
apport information ** Tags added: apport-collected staging ** Description changed: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. "Correlation does not imply causation, but it does waggle its eyebrows suggestively" and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [] __schedule_bug+0x52/0x5e [20931.796653] [] __schedule+0x575/0x5f0 [20931.796660] [] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [] ? release_pages+0x18d/0x1c0 [20931.796669] [] schedule+0x23/0x60 [20931.796673] [] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [] rwsem_down_write_failed+0x12/0x20 [20931.796681] [] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [] ? down_write+0x24/0x30 [20931.796689] [] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [] swap_entry_free+0xdc/0x170 [20931.796703] [] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [] swap_free+0x28/0x40 [20931.796712] [] do_swap_page+0x390/0x6f0 [20931.796717] [] ? sched_clock+0x8/0x10 [20931.796721] [] handle_pte_fault+0x21a/0x2b0 [20931.796726] [] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [] __do_page_fault+0x190/0x4f0 [20931.796740] [] ? sprintf+0x1c/0x20 [20931.796744] [] ? print_time.part.4+0x82/0xc0 [20931.796748] [] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [] do_page_fault+0xd/0x10 [20931.796756] [] error_code+0x67/0x6c [20931.796759] [] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [] copy_to_user+0x40/0x60 [20931.796767] [] syslog_print+0xc8/0x210 [20931.796770] [] do_syslog+0x206/0x390 [20931.796775] [] ? add_wait_queue+0x50/0x50 [20931.796780] [] ? kmsg_poll+0x50/0x50 [20931.796784] [] kmsg_read+0x50/0x60 [20931.796788] [] proc_reg_read+0x64/0xa0 [20931.796793] [] vfs_read+0x8c/0x160 [20931.796797] [] ? sys_futex+0xed/0x130 [20931.796801] [] ? proc_reg_write+0xa0/0xa0 [20931.796805] [] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this "Buffer I/O error on device zram0", please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. + ApportVersion: 2.0.1-0ubuntu17.4 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: muresan 29305 F pulseaudio + /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio + /dev/snd/controlC1: muresan 29305 F pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + Card0.Amixer.info: + Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 44' +Mixer name : 'SigmaTel STAC9205' +Components : 'HDA:838476a0,102801f1,00100204 HDA:14f12c06,14f1000f,0010' +Controls : 26 +Simple ctrls : 12 + Card1.Amixer.info: + Card hw:1 'USB'/'E-MU Systems, Inc. E-MU 0202 | USB at usb-:00:1d.0-2, full speed' +Mixer name : 'USB Mixer' +Components : 'USB041e:3f02' +Controls : 4 +Simple ctrls : 2 + DistroRelease: Ubuntu 12.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=88836c66-16ea-407f-8753-3190c09ca82f + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + MachineType: Dell Inc. Inspiron 1520 + MarkForUpload: True
[Bug 1217189] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812996/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812992/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812990/+files/ArecordDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812993/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812989/+files/AplayDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Card0.Codecs.codec.1.txt
apport information ** Attachment added: "Card0.Codecs.codec.1.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812994/+files/Card0.Codecs.codec.1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812988/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1217189/+attachment/3812991/+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/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218278] Re: When creating a swap device using zram I get Buffer I/O errors
@timg-tpi: Have you seen bug #1217189, involving machine lock-ups due to this error, probably triggered after heavy swapping? Do you have any suggestions as to why regular raring users seem unaffected by this bug (or at least they're not complaining)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218278 Title: When creating a swap device using zram I get Buffer I/O errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218278] Re: When creating a swap device using zram I get Buffer I/O errors
This might explain the reasons https://lkml.org/lkml/2013/8/13/22 (assuming this was a change backported to 3.8 and 3.5 by Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218278 Title: When creating a swap device using zram I get Buffer I/O errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
@damian-sawicki: yes, but once such memory errors DO occur, I think your system is basically compromised; you don't know when it will crash (*) and you don't know what else gets corrupted before the lock-up (why not filesystem errors, security etc?). That's why I would cut this at the root. (*) In practice, of course, the system seems to actually crash when under heavy swapping the erroneous block gets used (possibly when the page is swapped back into memory?) But this is like overclocking, you never know what parts of the system might break. We need to figure out why there aren't more people affected by this issue and how to get developers involved. Perhaps we should mark this as a security problem (because memory errors usually DO lead to security problems, even if writing an exploit could be hard) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
The way to list your swaps is swapon -s. If zram0 is listed, something still enables it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218278] Re: When creating a swap device using zram I get Buffer I/O errors
might be related to bug #1217189 which raises the possibility of hard machine LOCK-UPS due to zram errors. I've had several such lock-ups on precise after the most recent linux-lts-raring updates (and none before that) that seemed to go away after disabling zram. ** 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/1218278 Title: When creating a swap device using zram I get Buffer I/O errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218278] Re: When creating a swap device using zram I get Buffer I/O errors
Changed to Confirmed as per @jsalisbury's instructions, since @konrad.hofer forgot to. In any case, I doubt raring (and thus linux- lts-raring on precise) will upgrade to 3.11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218278 Title: When creating a swap device using zram I get Buffer I/O errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
Bug #1218278 might be a duplicate (though it doesn't talk about lock- ups). Apparently this is fixed in 3.11, though I don't see how this helps with raring and linux-lts-raring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
@damian-sawicki: a lot of people have zram due to the zram-config package, which you must remove with dpkg --purge zram-config (otherwise it won't go away completely). But in my case zram *still* starts up, and I can't track what sets it up. I think the easy solution is to break the zram modules (e.g. rename zram.ko to zram.ko.save in the appropriate /lib/modules directory) Of course, it would be great to get working zram again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
@damian-sawicki: do you also get lock-ups? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
@variona So, no lock-ups after downgrading? You should also test the NEWER kernel WITHOUT enabling zram and see if the crashes still occur. I've run 3.8.0-29 WITHOUT zram for almost a day (not quite enough to give it a clean pass) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217189] [NEW] Buffer I/O error on device zram0 (possibly causing complete machine lockup)
Public bug reported: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. "Correlation does not imply causation, but it does waggle its eyebrows suggestively" and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [] __schedule_bug+0x52/0x5e [20931.796653] [] __schedule+0x575/0x5f0 [20931.796660] [] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [] ? release_pages+0x18d/0x1c0 [20931.796669] [] schedule+0x23/0x60 [20931.796673] [] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [] rwsem_down_write_failed+0x12/0x20 [20931.796681] [] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [] ? down_write+0x24/0x30 [20931.796689] [] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [] swap_entry_free+0xdc/0x170 [20931.796703] [] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [] swap_free+0x28/0x40 [20931.796712] [] do_swap_page+0x390/0x6f0 [20931.796717] [] ? sched_clock+0x8/0x10 [20931.796721] [] handle_pte_fault+0x21a/0x2b0 [20931.796726] [] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [] __do_page_fault+0x190/0x4f0 [20931.796740] [] ? sprintf+0x1c/0x20 [20931.796744] [] ? print_time.part.4+0x82/0xc0 [20931.796748] [] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [] do_page_fault+0xd/0x10 [20931.796756] [] error_code+0x67/0x6c [20931.796759] [] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [] copy_to_user+0x40/0x60 [20931.796767] [] syslog_print+0xc8/0x210 [20931.796770] [] do_syslog+0x206/0x390 [20931.796775] [] ? add_wait_queue+0x50/0x50 [20931.796780] [] ? kmsg_poll+0x50/0x50 [20931.796784] [] kmsg_read+0x50/0x60 [20931.796788] [] proc_reg_read+0x64/0xa0 [20931.796793] [] vfs_read+0x8c/0x160 [20931.796797] [] ? sys_futex+0xed/0x130 [20931.796801] [] ? proc_reg_write+0xa0/0xa0 [20931.796805] [] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this "Buffer I/O error on device zram0", please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-raring (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087915] Re: Can't combine -o permissions with -o uid=UUU, gid=GGG
"id; touch newfile; stat newfile" OK, you are right "-o permissions" alone accurately preserves owners and permissions, which is sort of what I needed. I was confused by some experiments I did with memory sticks accessed from Windows. "Yes, that should be expected. You cannot both define the owner of a file both as the current user and a forced user. See http://www.tuxera.com/community/ntfs-3g-advanced/ownership-and- permissions/#options" Ownership and permission are orthogonal settings. You could force ownership while leaving permissions alone. This would be useful when working with memory sticks that are accessed both in Windows and Linux (because sometimes directories created in Windows will appear owned by root and unwritable). The permissions/conditions table is actually quite confusing. It's trying to represent a decision tree. I don't have better suggestions though, other than switching the column order, i.e. Condition first, Results second. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087915 Title: Can't combine -o permissions with -o uid=UUU,gid=GGG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1087915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087915] Re: Can't combine -o permissions with -o uid=UUU, gid=GGG
Note, my shell log shows the behavior with mount -o uid=500,gid=500,umask=000. The same behavior (chmod has no effect) occurs when using mount -o permissions,uid=500,gid=500,umask=000 (as if -o permissions is being silently ignored). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087915 Title: Can't combine -o permissions with -o uid=UUU,gid=GGG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1087915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087915] [NEW] Can't combine -o permissions with -o uid=UUU, gid=GGG
Public bug reported: At the moment, it seems that mount.ntfs-3g disables -o permissions if -o uid=UUU and/or uid=GGG are also specified. This (combined with Ubuntu's compilation options disallowing user mounts for NTFS-3g) prevents unprivileged users from easily accessing NTFS systems while preserving standard Unix permissions. root# mount -o uid=500,gid=500,umask=000 /dev/sdb1 /vol/exthd/ root# touch /vol/exthd/x root# ls -al /vol/exthd/x -rwxrwxrwx 1 muresan muresan 0 Dec 8 00:29 /vol/exthd/x root# chmod u-x /vol/exthd/x root# ls -al /vol/exthd/x -rwxrwxrwx 1 muresan muresan 0 Dec 8 00:29 /vol/exthd/x So chmod is ignored and all permissions are fixed to rwx. With "mount -o permissions", permissions ARE preserved, but all files are owned by root: root# mount -o permissions /dev/sdb1 /vol/exthd Using default user mapping root# touch /vol/exthd/x root# ls -al /vol/exthd/x -rw--w--w- 1 root root 0 Dec 8 00:29 /vol/exthd/x root# chmod u+x /vol/exthd/x root# ls -al /vol/exthd/x -rwx-w--w- 1 root root 0 Dec 8 00:29 /vol/exthd/x root# rm /vol/exthd/x root# ls -al /bin/bash -rwxr-xr-x 1 root root 920788 Apr 3 2012 /bin/bash root# cp -a /bin/bash /vol/exthd/ root# ls -al /vol/exthd/bash -rwxr-xr-x 1 root root 920788 Apr 3 2012 /vol/exthd/bash root# umount /vol/exthd Trying to mount the filesystem as an unprivileged user results in: Either mount the volume as root, or rebuild NTFS-3G with integrated FUSE support and make it setuid root. Please see more information at http://tuxera.com/community/ntfs-3g-faq/#unprivileged ** Affects: ntfs-3g (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/1087915 Title: Can't combine -o permissions with -o uid=UUU,gid=GGG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1087915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515915] Re: evince hangs on start-up
The only way I can get out of this bug, when it bites, is to exit my X (and presumably dbus) session and log back in. Really annoying. evince prints all sorts of useless console clutter, but fails to print any useful diagnostics in this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/515915 Title: evince hangs on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/515915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
Run uname -a on the command line and post the results. You're probably not running a real-time kernel, because those stopped at around 2.6.33. But log the results here anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/367671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
@David (#36): are you running a RT kernel though? PA tends to get killed for many other reasons, being the stable piece of software that it is... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/367671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726471] Re: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session
... which is only a dream at this point :) I guess I should request a backport to my installed version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726471 Title: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
Then please ignore my previous comment and file a separate bug. This bug is about unclean shutdowns, while yours sounds like the machine hangs on shutdown -- a different symptom. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
There are other bugs in Ubuntu that can cause shutdown problems, for example Bug #665195 and bug #665176. I fixed my problems by creating a /etc/init.d/sysshutdown as attached (and adding it to the various runlevels). This at least gives you a chance to examine the situation (in Virtual Console 9) and do a Alt + Sysrq + RSEIUB if need be. This, or something similar, should be included in distributions, since improper shutdown is dangerous. Sysrq can be simulated by writing to /proc/sysrq-trigger. Ubuntu should at least force-remount read-only (via sysrq) before doing its customary improper shutdowns. ** Attachment added: "sysshutdown script" https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/2130969/+files/sysshutdown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726471] Re: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session
Thanks, I missed the second status line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726471 Title: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726471] Re: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session
I wonder why this bug is marked as Fix Released? Upstream has indeed fixed the problem, but on a different branch (dbus 1.4.8). Ubuntu has 1.4.6 and AFAICT the fix hasn't been backported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726471 Title: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
It's an interrupted syscall -- there is no result... And the for loop only repeats on EINTR. I take it that no support, or at least help, will be forthcoming from the Ubuntu side? Even though the lead PA developer seems like a smart guy who understands real-time quite well, I'm sorry to say that PA is a stability and usability nightmare, and it has always been so. See the myriad of guides on removing PA from Ubuntu installs. I think the problem is that PA developers put a low priority on making the software "just work" for the user. They are, however, quite happy to explain what the "right thing" is, how to contact the non-responsive ALSA developers, how to invest hours upon hours debugging Pulse etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
Thanks David. I am streaming from qmmp, and I have completely removed gstreamer0.10-pulseaudio (and, yes, as per comment #25, I have a backported natty pulseaudio). I have performed the steps I planned in #28 and have obtained several backtraces. They all look the same. Strangely, the kernel sends SIGXCPU (due to real-time CPU usage reaching the soft RLIMIT_RTTIME) in a write() call. The setrlimit(2) man page says that blocking calls reset the RTTIME count. #0 0x0012d422 in ?? () #1 0x00475edb in write () at ../sysdeps/unix/syscall-template.S:82 #2 0x00153a55 in pa_fdsem_post (f=0x806e178) at pulsecore/fdsem.c:205 #3 0x0013cb0f in push (l=0x8071bc8, p=0x8, wait_op=false) at pulsecore/asyncq.c:161 #4 0x0013d291 in pa_asyncq_post (l=0x8071bc8, p=0x807a620) at pulsecore/asyncq.c:203 #5 0x0013c1ee in pa_asyncmsgq_post (a=0x8071a90, object=0x80b3ac8, code=7, userdata=0x0, offset=0, chunk=0xb570, free_cb=0) at pulsecore/asyncmsgq.c:139 #6 0x009811d7 in pstream_memblock_callback (p=0x80864d8, channel=0, offset=0, seek=PA_SEEK_RELATIVE, chunk=0xb570, userdata=0x8092228) at pulsecore/protocol-native.c:4445 #7 0x001dd20b in ?? () from /usr/lib/libpulsecommon-0.9.22.so #8 0x001c823e in ?? () from /usr/lib/libpulsecommon-0.9.22.so #9 0x0021b5fb in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0 #10 0x0021bb11 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #11 0x0021bbd4 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #12 0x08052e85 in main (argc=1, argv=0xb834) at daemon/main.c:974 Patch attached. ** Patch added: "soft RLIMIT_RTTIME lower than hard limit" https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/367671/+attachment/2090565/+files/0230-rlimit-rttime-soft-limit.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
>From setrlimit(2): setrlimit allows the user to specify two limits -- a soft one and a hard one. For RLIMIT_RTTIME, upon exceeding the soft limit, the kernel sends a SIGXCPU every second, then a SIGKILL. Unfortunately, pulseaudio sets the soft limit equal to the hard limit, so no warning is possible. I'm going to change the code to make the soft limit smaller, then run pulse under gdb and get a backtrace when it receives SIGXCPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
Doesn't the log-level = debug take care of that, Daniel? I didn't attach a full log because minutes pass between the last printed message and the SIGKILL. Is there a way to see how much "rttime" a task has been using (with ps or something else)? And (less likely) is there a way to configure the kernel to send something like SIGUSR1 instead of SIGKILL and/or log the action and its cause? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
This is hard to diagnose. I built 0.9.22 packages from natty, then installed pulseaudio-dbg_0.9.22+stable-queue-24-g67d18-0ubuntu3_i386.deb In ~/.pulse/daemon.conf, I enabled log-level = debug log-meta = yes log-time = yes log-backtrace = 1 then ran pulseaudio under gdb with $ killall pulseaudio; rm ~/.pulse-cookie; gdb --args pulseaudio --log- target=stderr [...] (1533.966| 36.781) D: [modules/alsa/alsa-sink.c:1496 thread_func()] Wakeup from ALSA! (libpulsecommon-0.9.22.so(pa_log_levelv_meta+0x5e9) [0x1cda59]) (1572.048| 38.082) D: [modules/alsa/alsa-sink.c:1496 thread_func()] Wakeup from ALSA! (libpulsecommon-0.9.22.so(pa_log_levelv_meta+0x5e9) [0x1cda59]) [Thread 0xb7355b70 (LWP 24417) exited] [Thread 0xb7b68b70 (LWP 24416) exited] Program terminated with signal SIGKILL, Killed. So, it's impossible to tell what's happening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367671] Re: PulseAudio gets killed mysteriously on RT kernels
Bug #496616 is marked as a duplicate of bug #644644... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/367671 Title: PulseAudio gets killed mysteriously on RT kernels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762929] Re: wmdrawer hangs when killed, segfaults when killed again
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762929 Title: wmdrawer hangs when killed, segfaults when killed again -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762929] [NEW] wmdrawer hangs when killed, segfaults when killed again
Public bug reported: Binary package hint: wmdrawer $ wmdrawer & $ killall wmdrawer # wmdrawer doesn't go away, but doesn't bring up the drawer either anymore $ killall wmdrawer Bye bye, thx to use wmdrawer [1]+ Segmentation fault wmdrawer ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: wmdrawer 0.10.5-1.1 ProcVersionSignature: Ubuntu 2.6.31-11.154-rt Uname: Linux 2.6.31-11-rt i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Apr 16 20:19:10 2011 ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wmdrawer ** Affects: wmdrawer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762929 Title: wmdrawer hangs when killed, segfaults when killed again -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730506] Re: patchage missing build-depend on dbus-glib
Trivial patch added, since there seems to be no response to the original report. Please apply or at least comment on the issue. ** Patch added: "depend on libdbus-glib-1-dev (debdiff)" https://bugs.launchpad.net/ubuntu/+source/patchage/+bug/730506/+attachment/2025152/+files/patchage-depend-on-libdus-glib-1-dev.debdiff.diff ** Tags added: maverick natty patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730506 Title: patchage missing build-depend on dbus-glib -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482533] Re: acroread does not become the default PDF handler for email even after answering "Yes" to the debconf question
** Summary changed: - Karmic acroread does not become the default PDF handler for email even after answering "Yes" to the debconf question + acroread does not become the default PDF handler for email even after answering "Yes" to the debconf question ** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/482533 Title: acroread does not become the default PDF handler for email even after answering "Yes" to the debconf question -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270479] Re: Debian/Ubuntu netpbm is many years out-of-date with upstream
As the comments in the Debian bug report show, Fedora 14 is packaging netpbm-10.47.17, so presumably the license problems invoked by Debian aren't that bad. The Debian maintainer has quite clearly decided to kill this package. He hasn't posted updates in the bug report for almost 4 years. Is there something we can do about inactive Debian maintainers? Alternatively, who's in charge of the Ubuntu package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/270479 Title: Debian/Ubuntu netpbm is many years out-of-date with upstream -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673119] Re: dash "set -e" breaks "trap action INT"
I have reported this bug upstream and it has been confirmed. http://www.mail-archive.com/dash@vger.kernel.org/msg00401.html Apparently dash 0.5.6 fixes it, but releases up to Natty still use 0.5.5 ** Tags added: maverick natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673119 Title: dash "set -e" breaks "trap action INT" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665176] Re: svscan (the upstart job) doesn't stop on shutdown
If you're seeing data corruption due to shutdown, see also this bug: https://bugs.launchpad.net/ubuntu/maverick/+source/sysvinit/+bug/665185 (again there is a fixed version in my PPA, and Ubuntu will also soon provide a Lucid update) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665176 Title: svscan (the upstart job) doesn't stop on shutdown -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665176] Re: svscan (the upstart job) doesn't stop on shutdown
I have a fixed version in my PPA, https://launchpad.net/~danmbox/+archive/ppa/ Attaching debdiff against that version. This is a trivial change, but from what I can see Ubuntu is very selectively maintained, and providing a patch makes it slightly more likely that a maintainer will act. Again, please note that this bug breaks shutdown, leading to unclean filesystems, fsck and thus possibly an increased chance of data corruption. ** Patch added: "debdiff - fix svscan.conf" https://bugs.launchpad.net/ubuntu/+source/daemontools/+bug/665176/+attachment/2006563/+files/daemontools-svscan.conf-debdiff.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665176 Title: svscan (the upstart job) doesn't stop on shutdown -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726471] Re: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session
The bug obviously affects Maverick and Natty as well. It has been fixed in GIT and will be in 1.4.8: https://bugs.freedesktop.org/show_bug.cgi?id=35569 I hope this fix will be backported to 1.4.6 (on freedesktop.org and/or here), because it would be quite annoying to have to deal with buggy Ubuntus for years to come now. ** Bug watch added: freedesktop.org Bugzilla #35569 http://bugs.freedesktop.org/show_bug.cgi?id=35569 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726471 Title: dbus de-prioritizes XDG_DATA_HOME -- can't customize user session -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
Great, thanks. Now what do I have to do to get this fix into Lucid, where it actually *is* a problem (killall5 doesn't overflow on Natty, because it's been fixed, but it does on Lucid)? The LTS release still has years left of support, but I'm really getting the all-around feeling that it is shunned, ignored, and being treated as legacy software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665185] Re: /etc/init.d/sendsigs fails to kill some processes
Steve, note that while this issue has been masked in Maverick & Natty by making killall5 accept any number of OMITPIDs, it is still a problem in Lucid for those who have upstart jobs that won't shut down. The symptom is a journal replay (or heaven forbid worse) after every single reboot (because killall5 crashes and doesn't kill what it's supposed to kill). It depends on how many buggy upstart jobs one has installed... For Maverick and Natty: it may seem that PID reusal is unlikely, but it's not quite so: at boot time, a long-running upstart job gets a low PID (e.g. 425). The system stays up for a day or two. In that interval, PIDs wrap around 32767 several times. At shutdown, it's very possible for a new process to hit PID 425 and get inappropriate immunity. You may have thought that reuse only occurred if PIDs made a full wrap-around in the 10 seconds of so worth of shutdown -- but it's not so. In any case, as I said, why even run this risk? There's no need to accumulate PIDs that once belonged to now-dead upstart jobs (I think you agreed with my analysis of the code, but I'm not quite sure, given your phrasing.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742964] Re: shift-click & ctrl-click not working
** Tags removed: lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742964 Title: shift-click & ctrl-click not working -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742964] [NEW] shift-click & ctrl-click not working
Public bug reported: In xtightvncviewer shift-click and ctrl-click behave as normal clicks, making it impossible to select multiple items. Server is tightvnc, and can be on a windows or on a linux host with the same result. Easiest to reproduce by running a tightvncserver, then connecting to it with 'xtightvncviewer localhost:1' Maverick and Natty seem to have the same tightvnc version so presumably both are affected ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xtightvncviewer 1.3.9-6 ProcVersionSignature: Ubuntu 2.6.31-11.154-rt Uname: Linux 2.6.31-11-rt i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Mar 26 08:34:04 2011 ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: tightvnc ** Affects: tightvnc (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742964 Title: shift-click & ctrl-click not working -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
