[Bug 1811641] Re: Wodim permissions error: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
Yes, this looks like the same thing. The root of the problem is that /usr/bin/wodim is lacking the u+s (where user=root) permission. Fixing it might just be a matter of changing the permissions of this file in the .deb package. However, if upstream expects wodim to be installed in the home directory, that would complicate things somewhat. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811641 Title: Wodim permissions error: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1811641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811641] Re: Wodim permissions error: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
@Chris Guiver Thank-you for taking the time to respond to this bug report! I've done some upgrades, since I posted the original report, but after uninstalling and reinstalling K3B and Wodim, the symptoms are the same (partial log output, with error, below). The "chmod +r /usr/bin/wodim" trick still functions effectively as a workaround. Please let me know if you need anything else. K3B package info: Package: k3b Architecture: amd64 Version: 17.12.3-0ubuntu3 Priority: optional Section: universe/otherosfs Origin: Ubuntu Maintainer: Kubuntu Developers Original-Maintainer: Debian KDE Extras Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 2485 Depends: cdparanoia, cdrdao, cdrskin, genisoimage, k3b-data (= 17.12.3-0ubuntu3), libk3b7 (= 17.12.3-0ubuntu3), udisks2, wodim, kio, libc6 (>= 2.14), libkf5archive5 (>= 4.96.0), libkf5bookmarks5 (>= 4.96.0), libkf5cddb5, libkf5completion5 (>= 4.97.0), libkf5configcore5 (>= 4.98.0), libkf5configwidgets5 (>= 4.96.0), libkf5coreaddons5 (>= 5.16.0), libkf5i18n5 (>= 4.97.0), libkf5iconthemes5 (>= 5.25.0), libkf5jobwidgets5 (>= 4.96.0), libkf5kcmutils5 (>= 4.96.0), libkf5kiocore5 (>= 4.96.0), libkf5kiofilewidgets5 (>= 4.96.0), libkf5kiowidgets5 (>= 5.33.0), libkf5newstuff5 (>= 4.95.0), libkf5notifications5 (>= 4.96.0), libkf5notifyconfig5 (>= 4.96.0), libkf5service-bin, libkf5service5 (>= 4.99.0), libkf5solid5 (>= 4.97.0), libkf5widgetsaddons5 (>= 4.96.0), libkf5xmlgui-bin, libkf5xmlgui5 (>= 4.98.0), libqt5core5a (>= 5.9.0~beta), libqt5dbus5 (>= 5.0.2), libqt5gui5 (>= 5.7.0), libqt5widgets5 (>= 5.6.0~beta), libqt5xml5 (>= 5.0.2), libstdc++6 (>= 4.1.1) Recommends: dvd+rw-tools, growisofs, libk3b7-extracodecs, transcode, vcdimager Suggests: k3b-extrathemes, k3b-i18n, kde-config-cddb, normalize-audio, sox Filename: pool/universe/k/k3b/k3b_17.12.3-0ubuntu3_amd64.deb Size: 618988 MD5sum: fc4221e6962a5c39fa96ae8a47ca5c49 SHA1: 986164bd69f910e2cf8975b8abccafd7c2775aef SHA256: 6f0115c85b2b3f57d78b78327e6ee14106293c3868e22a7a9b7f22df106df183 Homepage: http://www.k3b.org Description-en: Sophisticated CD/DVD burning application K3b provides a comfortable user interface to perform most CD/DVD burning tasks. While the experienced user can take influence in all steps of the burning process the beginner may find comfort in the automatic settings and the reasonable k3b defaults which allow a quick start. Description-md5: c76b0e46810cfd0637ba2d7954169eff Task: kubuntu-desktop, kubuntu-full Supported: 3y Wodim package info: Package: wodim Architecture: amd64 Version: 9:1.1.11-3ubuntu2 Priority: optional Section: universe/otherosfs Source: cdrkit Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Joerg Jaspert Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 926 Provides: cdrecord Depends: libc6 (>= 2.14), libcap2 (>= 1:2.10) Recommends: genisoimage Suggests: cdrkit-doc Conflicts: xcdroast (<< 0.98+0alpha15-11) Replaces: cdrecord, cdrtools-doc Filename: pool/universe/c/cdrkit/wodim_1.1.11-3ubuntu2_amd64.deb Size: 266590 MD5sum: ff0102baedca59b01c83254e8220daff SHA1: 3fa3eedce885d900858c2dcf6ad6186613b6085f SHA256: c6bfb7e5ac40f130d2eb8adde74f771d7b2dd5f65e9b8b3c5c06c8f299580d42 Description-en: command line CD/DVD writing tool wodim allows you to create CDs or DVDs on a CD/DVD recorder. It supports writing data, audio, mixed, multi-session, and CD+ disc and DVD data and video disks on DVD capable devices, on just about every type of CD/DVD recorder out there. . Please install cdrkit-doc if you want most of the documentation and README files. Description-md5: 430a6da0f7f8a42f965bb87ea62dcc74 Task: kubuntu-desktop, kubuntu-full, ubuntustudio-video, ubuntukylin-desktop, ubuntu-mate-desktop Supported: 3y Partial log with error: Devices --- HL-DT-ST BD-RE BH16NS40 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] [%7] System --- K3b Version: 17.12.3 KDE Version: 5.44.0 Qt Version: 5.9.5 Kernel: 4.15.0-58-generic Used versions --- cdrecord: 1.1.11 cdrecord --- /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. /usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero. TOC Type: 1 = CD-ROM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811641 Title: Wodim permissions error:
[Bug 1353013] Re: Popping/Crackling sound when playing audio in Ubuntu 14.04
I'm seeing this bug in Linux Mint 19.1 (Ubuntu 18.04 base). The audio devices do not appear and disappear in the "Sounds" GUI. The workaround I've found is to do this in a terminal: pulseaudio -k && sleep 5 ; pulseaudio -D Sometimes this works for hours, and sometimes it works for minutes, after killing/restarting the PulseAudio daemon, as above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353013 Title: Popping/Crackling sound when playing audio in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-hdmi-pulseaudio/+bug/1353013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353013] Re: Popping/Crackling sound when playing audio in Ubuntu 14.04
I'm seeing this bug in Linux Mint 19.1 (Ubuntu 18.04 base). The audio devices do not appear and disappear in the "Sounds" GUI. The workaround I've found is to do this in a terminal: pulseaudio -k && sleep 5 ; pulseaudio -D Sometimes this works for hours, and sometimes it works for minutes, after killing/restarting the PulseAudio daemon, as above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353013 Title: Popping/Crackling sound when playing audio in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-hdmi-pulseaudio/+bug/1353013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811641] [NEW] Wodim permissions error: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
Public bug reported: Tested on Linux Mint 19.1 AMD64 Cinnamon (Ubuntu 18.04 LTS base). When copying an audio CD (didn't test with other media), this error causes the writing process to abort before beginning: /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. /usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero. A workaround is to enable the sticky bit on /usr/bin/wodim, like so: sudo chmod +s /usr/bin/wodim My user was already in the cdrom group, so permissions should not have been an issue: groups $USER myuser : myuser adm cdrom sudo dip plugdev lpadmin sambashare I'm guessing this can be fixed with a simple change in the package files, assuming the use of the sticky bit is not a security risk. Below are logs from two audio CD copying attempts. The first one is trying to burn a simulation without the workaround, which fails. The second one is a simulation with the workaround, which succeeds. I also did a real burn and tested the resulting audio CD, but forgot to save the log file (sorry). Suffice to say that it worked. SIMULATION WITHOUT WORKAROUND Devices --- HL-DT-ST BD-RE BH16NS40 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] [%7] System --- K3b Version: 17.12.3 KDE Version: 5.44.0 Qt Version: 5.9.5 Kernel: 4.15.0-43-generic Used versions --- cdrecord: 1.1.11 cdrecord --- /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. /usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero. TOC Type: 0 = CD-DA cdrecord command: --- /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=48 -raw96r -dummy driveropts=burnfree -text -useinfo -audio -shorttrack /tmp/k3bCdCopy0/Track01.wav /tmp/k3bCdCopy0/Track02.wav /tmp/k3bCdCopy0/Track03.wav /tmp/k3bCdCopy0/Track04.wav /tmp/k3bCdCopy0/Track05.wav SIMULATION WITH WORKAROUND Devices --- HL-DT-ST BD-RE BH16NS40 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] [%7] System --- K3b Version: 17.12.3 KDE Version: 5.44.0 Qt Version: 5.9.5 Kernel: 4.15.0-43-generic Used versions --- cdrecord: 1.1.11 cdrecord --- scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 SCSI buffer size: 64512 Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. TOC Type: 0 = CD-DA Driveropts: 'burnfree' Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identification : 'BD-RE BH16NS40 ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0009 (CD-R) Profile: 0x0043 (BD-RE) Profile: 0x0042 (BD-R random recording) Profile: 0x0041 (BD-R sequential recording) Profile: 0x0040 (BD-ROM) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0012 (DVD-RAM) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) (current) Profile: 0x0008 (CD-ROM) Profile: 0x0002 (Removable disk) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 3013120 = 2942 KB FIFO size : 12582912 = 12288 KB Encoding speed : 1000x (75000 sectors/s) for libedc from Heiko Ei�feldt Speed set to 8468 KB/s pregap1: -1 Track 01: audio 31 MB (03:08.00) no preemp Track 02: audio 40 MB (03:58.00) no preemp pregapsize:
[Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)
I've also been having this problem since 16.04. Dell XPS 13" 2015, model L321X. The issue persists in Ubuntu 18.04 LTS, as well as Ubuntu Mint 18.04 LTS. Dell's support page indicates that this issue existed in 14.04, but disappeared in 15.04. This may be a regression. https://www.dell.com/community/Linux-General/UPDATE-Ubuntu-14-04 -Touchpad-Freezing-Fix-XPS-13-2015/td-p/4587485 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576844 Title: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313539] Re: [DisplayPort] monitor shows black screen and "no input signal" after turning the monitor off and on manually
Issue persists in 18.04. All OS upgrades installed as of June 25, 2018. Dell XPS 13" L321X Mini Displayport -> HDMI adapter -> HDMI cable -> LG 43lx570h television. Interestingly, I was able to get this setup to work on a different model of television, just a few days earlier. I don't currently have access to that TV, but when I get back to where it is, I'll do another test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313539 Title: [DisplayPort] monitor shows black screen and "no input signal" after turning the monitor off and on manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1313539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463120] Re: Failure to boot if fstab disk mounts fail
Could fstab default mount options be changed so that, unless otherwise specified, failed mount attempts would skip that filesystem and keep booting (logging an error), instead of dropping to an inaccessible recovery console? This would let the fstab be fixed with minimal hassle in a headless environment, so long as the broken mount isn't /boot or /. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686157] [NEW] External Displays Turn Off After Only A Few Seconds Of Inactivity
Public bug reported: OS VERSION DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.04 DISTRIB_CODENAME=zesty DISTRIB_DESCRIPTION="Ubuntu 17.04" UPOWER VERSION upower: Installed: 0.99.4-4 Candidate: 0.99.4-4 Version table: *** 0.99.4-4 500 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status EXPECTED BEHAVIOR Expected displays to stay on while idle, for at least a few minutes (per Power Settings). WHAT HAPPENED INSTEAD (and hardware information) I just upgraded from a fully-updated Ubuntu 16.10 64-bit Desktop installation to 17.04, using the update manager. In 16.10 and 16.04 LTS, this issue did not exist for me. I'm using a MacBook Pro with Ubuntu installed in a dual-boot configuration. I have two attached monitors: one via the mini DisplayPort and one via HDMI. I normally keep the laptop lid closed while working. Since the upgrade (persisting through several reboots), whenever I have the notebook lid closed, if I don't touch the keyboard or mouse for about 5 seconds, both external displays go into power- saving mode. When I touch the keyboard/mouse, again, they instantly come back up (no delay), indicating that the computer had probably not been suspended. If I then don't touch the keyboard/mouse for another 5 seconds, they immediately go back into power saving mode. (Repeat...) Going into Display Settings and changing "Built-in Display" to on or off doesn't seem to have any effect. When I close the lid, it changes itself back to "OFF"; and when I open the lid, it changes itself back to "ON". (This seems like a sensible behavior.) Notably, the on/off switch doesn't seem to move unless I exit and re-enter Display Settings. I found a workaround to this problem on a forum post: In "/etc/UPower/UPower.conf", change "IgnoreLid=false" to "IgnoreLid=true". After doing this, the Built-in Display switch stays on whatever I set it to, regardless of whether the laptop lid is open or closed (which probably isn't ideal); but more importantly, the external displays no longer turn off when idle for a few seconds. They now obey the settings I explicitly define in Power Settings. ** Affects: upower (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/1686157 Title: External Displays Turn Off After Only A Few Seconds Of Inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1686157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463120] Re: Failure to boot if fstab disk mounts fail
I've tested this with kernel 4.10-rc3 in a local VirtualBox VM (Ubuntu
Server 16.04), with the same fstab error as above, and am able to
confirm most of the symptoms described by the reporter.
When attempting to 'mount -a', it presents the expected "wrong
filesystem type" error, but doesn't render the system unresponsive.
Upon reboot, however, it drops into a maintenance console without
presenting an error about a failed mount attempt. Consequently, the
server would be unreachable for maintenance via SSH.
'journalctl -xb' provides a log that contains an error about the failed
mount attempt, but doesn't point to it as the reason for dropping into a
maintenance terminal, and it isn't the last thing logged.
After fixing fstab (which requires physical access) and rebooting
('reboot' from the maintenance console), GRUB does still have a
countdown, but it starts around 10 seconds, instead of 3 seconds (~3
seconds is the default for Ubuntu Server). Otherwise, at this point,
the system is able to boot up automatically, without issue.
After rebooting a second time (from the normal BASH prompt), the GRUB
countdown is back to ~3 seconds, and the system boots normally
(automatically), from there.
Thanks, again, for helping to resolve this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463120
Title:
Failure to boot if fstab disk mounts fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463120] Re: Failure to boot if fstab disk mounts fail
(New kernel is still compiling...) I just did a test with a fully-patched, newly spun-up Ubuntu Server 14.04 AWS instance, and the behavior seems to be present with kernel 3.13.0-107. I can't verify all of the symptoms described by the reporter, because I don't have physical access; but I get "connection refused" when trying to SSH into it, after making an intentionally-bad edit to /etc/fstab. For completeness, this is the bad edit I made: /home/ubuntu/test.img /mnt ext4 defaults 0 0 The file referenced was created with: dd if=/dev/zero of=/home/ubuntu/test.img bs=1M count=20 When attempting to mount this file from the command-line, it produces a "wrong filesystem type" error, as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463120] Re: Failure to boot if fstab disk mounts fail
Thanks for your attention on this bug, Joseph. I'm compiling the new kernel, now, and will let you know as soon as I have a test result. As far as I know, all 16.04 kernel versions exhibit this problem; but I haven't done any testing on Ubuntu 15.X. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
