Sorry for noise. Disabling btrfs scan did improve boot time, i just had
other (DHCP) issues also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460447
Title:
Boot slow, "scanning for btrfs filesyst
It definitely changed in boot time by me adding a btrfs-formatted block
device to the system (/dev/sdb, without a partition table)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460447
Title:
Boot s
Hold on, removing the scan was not a complete solution. I still have
slow boots, caused by something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460447
Title:
Boot slow, "scanning for btrfs
and then doing update-initramfs -u of course
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460447
Title:
Boot slow, "scanning for btrfs filesystems" takes 100 seconds
To manage notifications about
Editing /usr/share/initramfs-tools/scripts/local-premount/btrfs to
remove the scan speeds up boots for me on 4.0.0-4-generic wily. That'll
stop you from being able to mount a multi-device filesystem as root,
which I do not need.
--
You received this bug notification because you are a member of Ub
For me, it was a matter of creating an empty /etc/dnsmasq.conf so that
lxc-net.service could start, thus creating lxcbr0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452601
Title:
vivid container'
Public bug reported:
Raise volume multimedia key is no longer working after upgrade to
oneiric.
xev gives:
KeyRelease event, serial 32, synthetic NO, window 0x2a1,
root 0xad, subw 0x0, time 718367, (213,264), root:(215,350),
state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVo
*** This bug is a duplicate of bug 808938 ***
https://bugs.launchpad.net/bugs/808938
** This bug has been marked a duplicate of bug 808938
oneiric upgrade regression: personal account not in video group causes
gnome-shell to fail (glx)
--
You received this bug notification because you ar
Public bug reported:
After upgrading to oneiric, GLX stopped working, for example gnome-shell would
not run.
This was because swrast instead of real rendered was used. This in turn had to
do with permissions:
crw-rw 1 root video 226, 0 2011-07-11 17:49 /dev/dri/card0
And my user was previo
Public bug reported:
After upgrading to oneiric, GLX stopped working, for example gnome-shell would
not run.
This was because swrast instead of real rendered was used. This in turn had to
do with permissions:
crw-rw 1 root video 226, 0 2011-07-11 17:49 /dev/dri/card0
And my user was previo
udevd complains about write permissions to /run/udev but even with chmod go+w
it does.
Is udev started before the fs is remounted rw?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807306
Title:
[o
Workaround for me was:
Copy /etc/X11/xorg.conf.failsafe to /etc/X11/xorg.conf
(Replaced gfx driver to mine)
Disabled HAL
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
Added a section for keyboard explicitly (for mouse it was not needed)
Section "InputDevice"
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32944535/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/32944536/XsessionErrors.txt
--
uswsusp configure fails on install
https://bugs.launchpad.net/bugs/441546
You received thi
Public bug reported:
Binary package hint: uswsusp
I have a swapfile on a dmcrypt ext4 root volume:
$ swapon -s
FilenameTypeSizeUsedPriority
/resumefile file6291448 3496-1
/resumefile swapswap
My problem went away by reinstalling jaunty from scratch and then
upgrading to karmic via aptitude. Don't know what triggered this. New
install has the same filesystem setup with crypto disks.
--
upstart/mountall does not boot after mounting crypto disks
https://bugs.launchpad.net/bugs/438962
You
** Tags added: ubuntu-boot
--
upstart/mountall does not boot after mounting crypto disks
https://bugs.launchpad.net/bugs/438962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32725236/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/32725237/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32725238/Dependencies.txt
** A
Public bug reported:
Binary package hint: udev
Upstart fails to finish booting after starting init of crypto disks.
udevd complains about inotify_add_watch(6, (null), 10) failed: Bad
address. When investigating the system by forcing a getty to be spawned
and logging in, I can see that / is read-o
18 matches
Mail list logo
