[Bug 1769397] [NEW] Xorg crashes, possibly easystroke related
Public bug reported: Hi, Giving ubuntu-mate 18.04 a try, fresh install. I'm getting a lot of Xorg crashes which seem to be easystroke related: Easiest way to reproduce so far seems browsing around in chromium, at some point when using mouse wheel for scrolling everything suddenly freezes, Xorg session crashes and i'm back at login manager. I suspect this is easystroke related: - syslog shows easystroke crashing right at that time: 17:26:12 bionic mate-appearance[2034]: ../../../../../gdk/x11/gdkwindow-x11.c:5579 drawable is not a native X11 window 17:34:02 bionic kernel: [ 2489.359116] easystroke[1860]: segfault at 0 ip b7bf2e9d sp bfef9640 error 4 in libgtkmm-3.0.so.1.1.0[b79c5000+3c3000] 17:26:12 bionic mate-appearance[2034]: message repeated 5 times: [ ../../../../../gdk/x11/gdkwindow-x11.c:5579 drawable is not a native X11 window] 17:34:02 mate-appearance[2034]: mate-appearance-properties: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. - I can't seem to get it to crash when easystroke is not running. easystroke works fine otherwise, imported settings from previous install and it does well. Might be mate-related, i'll report it there as well. ** Affects: easystroke (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/1769397 Title: Xorg crashes, possibly easystroke related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1769397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769397] Re: Xorg crashes, possibly easystroke related
Ubuntu-MATE bug report: https://bugs.launchpad.net/ubuntu-mate/+bug/1769399 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769397 Title: Xorg crashes, possibly easystroke related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1769397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769401] [NEW] 18.04: Getting emacs-style markkeys to work again ?
Public bug reported: Hi, I'm giving ubuntu-mate 18.04 a try, Some fixes needed to get my .screenrc to work again, but so far so good. One thing i can't get to work is the markkeys setting to get emacs-style bindings in copy mode: # emacs-style binding in copy mode # this is to make pgup (^[[5~) and pgdn (^[[6~) work: markkeys h=^B:l=^F:$=^E:^b=5:^f=6:@=ESC=[=~ This used to work fine in 14.04, but in 18.04 this breaks pgup / pgdn (moves back/forward one character instead of one page). I've tried a few things but no luck so far. Any way to get this back in 18.04 ? ** Affects: screen (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/1769401 Title: 18.04: Getting emacs-style markkeys to work again ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1769401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631851] [NEW] Chromium taking 150% cpu after page load
Public bug reported: - Open https://www.facebook.com/U2 - Chromium continues to take 150% cpu after page finishes loading. Running Ubuntu 14.04 Mate desktop here. This happens with latest Chromium 53.0.2785 package and earlier versions as well. I can replicate the issue in Ubuntu Mate 14.04 and 16.04 LiveCDs: Just boot, apt-get update and apt-get install chromium-browser from it. Also happens in Lubuntu 16.04 but *not* in regular 14.04 / 16.04 Ubuntu LiveCDs, so could be Gnome / Unity related. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Description changed: - Open https://www.facebook.com/U2 - Chromium continues to take 150% cpu after page finishes loading. Running Ubuntu 14.04 Mate desktop here. This happens with latest Chromium 53.0.2785 package and earlier versions as well. I can replicate the issue in Ubuntu Mate 14.04 and 16.04 LiveCDs: Just boot, apt-get update and apt-get install chromium-browser from it. - Also happens in Lubuntu 16.04 but not in regular 14.04 / 16.04 Ubuntu LiveCDs, - so could be Gnome / Unity related. + Also happens in Lubuntu 16.04 but *not* in regular 14.04 / 16.04 Ubuntu + LiveCDs, so could be Gnome / Unity related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631851 Title: Chromium taking 150% cpu after page load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631851] Re: Chromium taking 150% cpu after page load
Xubuntu 16.04 is affected 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/1631851 Title: Chromium taking 150% cpu after page load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631851] Re: Chromium taking 150% cpu after page load
Can replicate in regular Ubuntu 16.04.1 LiveCD if Unity is not running: Boot LiveCD, kill Unity and switch to minimal desktop as in: http://askubuntu.com/questions/833868/way-to-run-ubuntu-livecd-without-unity/833962#833962 Start Chromium from there and open facebook page, takes 150% cpu after page load. Looks like it needs something from Unity or it's not happy... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631851 Title: Chromium taking 150% cpu after page load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631851] Re: Chromium taking 150% cpu after page load
Moved to bugs.chromium.org, can close this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631851 Title: Chromium taking 150% cpu after page load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1631851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085457] [NEW] cnee broken in lucid
Public bug reported: cnee version: 3.02-2ubuntu2 Ubuntu version: Ubuntu 10.04.3 LTS Current cnee in lucid is broken: $ cnee --record --events-to-record 1 --mouse --keyboard -o out -e log -v --> xnee_prepare ---> xnee_open_files --- xnee_open_files: handling err --- xnee_open_files: opening err: log Error received: error type 0 (0x0) error code 144 (0x90) error code major 135 (0x87) error code minor 5 (0x5) display 161871632 (0x9a5f710) XRecordBadContext This error can be ignored Error number: 35 Error: Record memory failure Solution: Xnee failed due to bad data received from RECORD extension Unlike https://bugs.launchpad.net/ubuntu/+source/xnee/+bug/378648 it doesn't crash, but doesn't work. Had to compile xnee-3.13 from source package, works like a charm. ** Affects: xnee (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/1085457 Title: cnee broken in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xnee/+bug/1085457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085457] Re: cnee broken in lucid
In case someone has the same issue, xnee-3.13 build for lucid is in my ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085457 Title: cnee broken in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xnee/+bug/1085457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087351] Re: tcpstat's output hangs when no packets arrive
This bug is known and documented in the man page. Came up with a patch (not ready for prod yet) and contacted upstream about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087351 Title: tcpstat's output hangs when no packets arrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpstat/+bug/1087351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087351] Re: tcpstat's output hangs when no packets arrive
** Patch added: "main_loop.patch" https://bugs.launchpad.net/ubuntu/+source/tcpstat/+bug/1087351/+attachment/3453202/+files/main_loop.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087351 Title: tcpstat's output hangs when no packets arrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpstat/+bug/1087351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087351] [NEW] tcpstat's output hangs when no packets arrive
Public bug reported: When running tcpstat in capture mode, output hangs while no packets arrive. For example $ tcpstat -i eth0 1 should print output every second, but instead hangs while there's no network traffic. Missing output comes up all at once once a packet arrives. Tested under Ubuntu Lucid (Precise affected as well - same code) tcpstat package version 1.5-3. ** Affects: tcpstat (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/1087351 Title: tcpstat's output hangs when no packets arrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpstat/+bug/1087351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580437] Re: wvdial returns with Huawei E160E error NO CARRIER
I was having a similar issue with a Huawei E1762. It seems the modem was getting confused when wvdial starts talking to it before it's finished registering. -> using a script to wait until the device is registered before running wvdial solved it ! details here: http://superuser.com/questions/527543/randomly-getting-no-carrier-from-huawei-3g-modem-under-linux/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580437 Title: wvdial returns with Huawei E160E error NO CARRIER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wvdial/+bug/580437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085457] Re: cnee broken in lucid
** Tags added: lucid ** Tags added: i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085457 Title: cnee broken in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xnee/+bug/1085457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087351] Re: tcpstat's output hangs when no packets arrive
** Tags added: i386 precise ** 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/1087351 Title: tcpstat's output hangs when no packets arrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpstat/+bug/1087351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087351] Re: tcpstat's output hangs when no packets arrive
Forwarded proper patch to debian (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697367) so should reach ubuntu at some point. In the meantime fixed version of tcpstat for lucid and precise is available in my ppa. ** Bug watch added: Debian Bug tracker #697367 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697367 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087351 Title: tcpstat's output hangs when no packets arrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpstat/+bug/1087351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087351] Re: tcpstat's output hangs when no packets arrive
** Changed in: tcpstat (Ubuntu) Status: New => Fix Committed ** Changed in: tcpstat (Ubuntu) Assignee: (unassigned) => lemonsqueeze (lemonsqueeze) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1087351 Title: tcpstat's output hangs when no packets arrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpstat/+bug/1087351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085457] Re: cnee broken in lucid
[Impact] * cnee and gnee packages are unuseable. [Test case] * see above [Regression Potential] * updating xnee to 3.13 will rebuild cnee xnee libxnee0 and xnee-doc packages. I couldn't find any other packages depending on these, so risk of regression is low. * successfully built and tested xnee 3.13-1 under lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085457 Title: cnee broken in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xnee/+bug/1085457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085457] Re: cnee broken in lucid
btw, cnee works under precise. so 3.11-1 is ok as far as this bug is concerned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085457 Title: cnee broken in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xnee/+bug/1085457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] [NEW] by default ext3 is mounted without barrier=1 in lucid
Public bug reported: On my system, a default ext3 mount (no fstab entry) results in: $ cat /proc/mounts /dev/sda6 /media/space ext3 rw,nosuid,nodev,relatime,errors=continue,user_xattr,acl,data=ordered 0 0 We can see the "barrier=1" option is missing by default, which can cause severe filesystem corruption in case of power failure (i've been hit recently). Quoting mount(1): "barrier=0 / barrier=1 This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance penalty. The ext3 filesystem does not enable write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure." the issue is fixed in later kernels (precise 3.2.0-35 is not affected), but lucid users are left to suffer the consequences of this horrifying default. $ uname -a Linux netbook 2.6.32-45-generic #101-Ubuntu SMP Mon Dec 3 15:41:13 UTC 2012 i686 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: i386 lucid ** Attachment added: "lsb_release.txt" https://bugs.launchpad.net/bugs/1097042/+attachment/3476349/+files/lsb_release.txt ** Information type changed from Private Security to Public ** Description changed: On my system, a default ext3 mount (no fstab entry) results in: $ cat /proc/mounts /dev/sda6 /media/space ext3 rw,nosuid,nodev,relatime,errors=continue,user_xattr,acl,data=ordered 0 0 We can see the "barrier=1" option is missing by default, which can cause severe filesystem corruption in case of power failure (i've been hit recently). Quoting mount(1): "barrier=0 / barrier=1 - This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper - on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance - penalty. The ext3 filesystem does not enable write barriers by default. Be sure to enable barriers unless - your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power - failure." + This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance + penalty. The ext3 filesystem does not enable write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure." the issue is fixed in later kernels (precise 3.2.0-35 is not affected), but lucid users are left to suffer the consequences of this horrifying default. $ uname -a Linux netbook 2.6.32-45-generic #101-Ubuntu SMP Mon Dec 3 15:41:13 UTC 2012 i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: by default ext3 is mounted without barrier=1 in lucid
/etc/fstab can be used as temporary workaround to force barrier=1 : $ sudo umount /media/space $ sudo mkdir /media/space and add an entry to /etc/fstab like: /dev/sda6 /media/spaceext3 barrier=1,rw,nosuid,nodev,uhelper=udisks 0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: by default ext3 is mounted without barrier=1 in lucid
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+attachment/3476429/+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/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: by default ext3 is mounted without barrier=1 in lucid
** Attachment added: "apport.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+attachment/3476428/+files/apport.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: by default ext3 is mounted without barrier=1 in lucid
** Attachment added: "Uname.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+attachment/3476430/+files/Uname.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: by default ext3 is mounted without barrier=1 in lucid
** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+attachment/3476431/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: by default ext3 is mounted without barrier=1 in lucid
attached log files manually, apport-collect isn't working for some reason... ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: On my system, a default ext3 mount (no fstab entry) results in: $ cat /proc/mounts /dev/sda6 /media/space ext3 rw,nosuid,nodev,relatime,errors=continue,user_xattr,acl,data=ordered 0 0 We can see the "barrier=1" option is missing by default, which can cause severe filesystem corruption in case of power failure (i've been hit recently). Quoting mount(1): "barrier=0 / barrier=1 - This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance - penalty. The ext3 filesystem does not enable write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure." + This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance penalty. The ext3 filesystem does not enable write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure." the issue is fixed in later kernels (precise 3.2.0-35 is not affected), but lucid users are left to suffer the consequences of this horrifying default. $ uname -a Linux netbook 2.6.32-45-generic #101-Ubuntu SMP Mon Dec 3 15:41:13 UTC 2012 i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: by default ext3 is mounted without barrier=1 in lucid
Discussion and some background info in Question #218447. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: by default ext3 is mounted without barrier=1 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097042] Re: Risk of filesystem corruption with ext3 in lucid
** Summary changed: - by default ext3 is mounted without barrier=1 in lucid + Risk of filesystem corruption with ext3 in lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097042 Title: Risk of filesystem corruption with ext3 in lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
