[Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
Here is a strace. Couldn't make it hang while stracing though: http://pastebin.com/mQ6Zgja1 Not sure how to produce anything useful with gdb, if you have any suggestions I'm happy to try. I could connect with gdb to the hanging program, would that be of any use? And what kind of information would you like to see from gdb in that case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870874 Title: LDAP user with automounted nfs homedir cannot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/870874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
Probably final comment from me, I found a workaround that "solves" the problem for me. If you don't need QT Accessibility: Edit `/etc/X11/Xsession.d/90qt-a11y', put a `#' in front of all lines: # -*- sh -*- # Xsession.d script to set the QT_ACCESSIBILITY env variable when accessibility # is enabled. # # This file is sourced by Xsession(5), not executed. #if [ -x "/usr/bin/gsettings" ]; then # a11y_enabled=$(gsettings get org.gnome.desktop.interface toolkit-accessibility) # if "$a11y_enabled" = "true" ]; then # export QT_ACCESSIBILITY=1 # fi #fi This work around might break with updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870874 Title: LDAP user with automounted nfs homedir cannot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/870874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
I guess this is not a lightdm issue, so changing the package to Xorg. ** Package changed: lightdm (Ubuntu) => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870874 Title: LDAP user with automounted nfs homedir cannot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/870874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
I can confirm this on two machines. The command in the above post contains a typo, the command below is the one at which the login process hangs: `gsettings get org.gnome.desktop.interface toolkit-accessibility' According to `ps aux' the process is in state `Sl'. When I kill that single process (no need to do a killall like I mentioned in the previous post) the login process continues and the user logs in nicely. Logging in with a local account always works fine. Logging in with LDAP authentication and Autofs mounted homedirs causes always a hang on this process. I tried running the same command from the command line after being logged in with both a local account and an ldap authenticated account. In both cases it returns `false'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870874 Title: LDAP user with automounted nfs homedir cannot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/870874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734398] Re: Ubuntu flash audio delay
I can confirm with Ubuntu 11.10 and Flash player 11 downloaded from Adobe's website. I don't know whether it is a problem with Adobe's plugin or whether the problem is on the Ubuntu side. The problem can be observed very easily in this Flash game: http://www.adamatomic.com/canabalt Just wait until the character jumps through the glass (which happens after a couple of seconds of playing) and notice how the sound of the breaking glass is delayed by about 1 second. Makes that specific flash game unplayable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/734398 Title: Ubuntu flash audio delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/734398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
It seems the system is hanging at: `gsettings get org.gnome.desktop.interface toolkit-accessiblity' Once I did a `killall gsettings' the ldap user logged in properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870874 Title: LDAP user with automounted nfs homedir cannot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/870874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870874 Title: LDAP user with automounted nfs homedir cannot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/870874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870874] [NEW] LDAP user with automounted nfs homedir cannot login
Public bug reported:
After installing Ubuntu (Oneiric, development branch) I followed two
guides to setup LDAP authentication and automounting of home directories
using autofs-ldap. This setup was working properly for older Ubuntu
releases (just to be sure I also tried with a fresh, up to date 11.04
installation).
The following steps were executed to setup LDAP authentication:
https://help.ubuntu.com/11.04/serverguide/C/openldap-server.html (section: LDAP
Authentication)
These steps were executed to setup Autofs-ldap:
https://help.ubuntu.com/community/AutofsLDAP
LDAP users properly login from the terminal (Ctrl-Alt-F1), in that case
they can browse their automounted homedirs etc.
When I try to login using LightDM the user seems to be logged in
properly; the login widget disappears from the screen but other than
that nothing is happening (the login screen background is still visible,
but the login widget is gone). I still can move the mouse pointer but
the user is not logged on. When taking a look at the user's .xsession-
errors file there is not much to see, nothing that seems worrying to me.
I can't find anything that obviously looks like an error in /var/log/*.
I tried several things:
- removed all files/directories starting with a . (dot) in the user's home
directory
- using LightDM and the default Ubuntu window manager
- using LightDM with Gnome
- using GDM with Gnome
In all cases the same behavior was observed.
Logging in with a local user works like a charm.
This is what /var/log/lightdm/lightdm.log says:
[+2.83s] DEBUG: Read 8 bytes from greeter
[+2.83s] DEBUG: Read 15 bytes from greeter
[+2.83s] DEBUG: Greeter start authentication for test_user
[+2.83s] DEBUG: pam_authenticate(0x169e340, 0) -> 10 (User not known to the
underlying authentication module)
[+2.83s] DEBUG: pam_start("lightdm", "test_user") -> (0x7f1ae4011570, 0)
[+2.85s] DEBUG: Prompt greeter with 1 message(s)
[+2.85s] DEBUG: Wrote 45 bytes to greeter
[+16.20s] DEBUG: Read 8 bytes from greeter
[+16.20s] DEBUG: Read 16 bytes from greeter
[+16.20s] DEBUG: Continue authentication
[+16.22s] DEBUG: pam_authenticate(0x7f1ae4011570, 0) -> 0 (Success)
[+16.22s] DEBUG: pam_acct_mgmt(0x7f1ae4011570, 0) -> 0 (Success)
[+16.22s] DEBUG: Authenticate result for user test_user: Success
[+16.22s] DEBUG: User test_user authorized
[+16.22s] DEBUG: Wrote 27 bytes to greeter
[+16.24s] DEBUG: Read 8 bytes from greeter
[+16.24s] DEBUG: Read 15 bytes from greeter
[+16.24s] DEBUG: Greeter requests session gnome-shell
[+16.25s] DEBUG: Stopping greeter
[+16.25s] DEBUG: Dropping privileges to uid 104
[+16.25s] DEBUG: Removing session authority from /var/lib/lightdm/.Xauthority
[+16.28s] DEBUG: Restoring privileges
[+16.28s] DEBUG: Sending signal 15 to process 7950
[+16.28s] DEBUG: Process 7950 exited with return value 0
[+16.28s] DEBUG: pam_close_session(0x167f300) -> 0 (Success)
[+16.28s] DEBUG: pam_setcred(0x167f300, PAM_DELETE_CRED) -> 0 (Success)
[+16.28s] DEBUG: pam_end(0x167f300) -> 0
[+16.28s] DEBUG: Ending ConsoleKit session
6e3a694924188906d4093c6702696be1-1318095483.743254-1770205889
[+16.31s] DEBUG: Greeter quit
[+16.31s] DEBUG: Starting user session
[+16.38s] DEBUG: Dropping privileges to uid 1049
[+16.38s] DEBUG: Writing /srv/home/test_user/.dmrc
[+17.48s] DEBUG: Restoring privileges
[+17.51s] DEBUG: Starting session gnome-shell as user test_user logging to
/srv/home/test_user/.xsession-errors
[+17.51s] DEBUG: Launching session
[+17.51s] DEBUG: pam_set_item(0x7f1ae4011570, 3, ":0") -> 0 (Success)
[+17.55s] DEBUG: pam_open_session(0x7f1ae4011570, 0) -> 0 (Success)
[+17.58s] DEBUG: Opened ConsoleKit session
6e3a694924188906d4093c6702696be1-1318095500.694488-13642418
[+17.58s] DEBUG: Dropping privileges to uid 1049
[+17.58s] DEBUG: Adding session authority to /srv/home/test_user/.Xauthority
[+17.82s] DEBUG: Restoring privileges
[+17.82s] DEBUG: Launching process 8053: /usr/sbin/lightdm-session
'gnome-session --session=gnome'
[+17.82s] DEBUG: Registering session with bus path
/org/freedesktop/DisplayManager/Session0
[+17.92s] DEBUG: pam_setcred(0x7f1ae4011570, PAM_ESTABLISH_CRED) -> 0 (Success)
[+17.92s] DEBUG: PAM returns environment
'GNOME_KEYRING_CONTROL=/tmp/keyring-6wgIZV GNOME_KEYRING_PID=8044
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8'
The user's .xsession_errors:
Running X session wrapper
Loading profile from /etc/profile
Loading resource: /etc/X11/Xresources/x11-common
Loading X session script /etc/X11/Xsession.d/20x11-common_process-args
Loading X session script /etc/X11/Xsession.d/30x11-common_xresources
Loading X session script /etc/X11/Xsession.d/40x11-common_xsessionrc
Loading X session script /etc/X11/Xsession.d/50_check_unity_support
Loading X session script /etc/X11/Xsession.d/50x11-common_determine-startup
Loading X session script
/etc/X11/Xsession.d/52libcanberra-gtk3-module_add-to-gtk-modules
Loading X session script
/etc/X11/Xsession.d/52libcanberra-gtk-module_a
[Bug 495394] Re: autostart almost always fails on boot time host
I changed my upstart script to ensure both the bridge and the md0 device (on which the LVM volume is located) are started before libvirt is started. In my situation this makes sure all my virtual machines can be started. However, different virtual machines can have different dependencies on (possibly slow) hardware being available or not. Perhaps it is a good idea to create separate upstart scripts for each virtual machine? This way it could be ensured that the hardware a specific virtual machine is relying on is brought up. I fixed my problems with the following `start on' line in /etc/init /libvirt-bin.conf: start on runlevel [2345] and net-device-added INTERFACE="br0" and block- device-added DEVNAME="/dev/md0" br0 is the bridge I am using md0 is the raid volume on which the LVM2 volumes are located, it seems (although I'm not 100% sure) that the block-device-added event is always fired after all LVM volumes on the block device are up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/495394 Title: autostart almost always fails on boot time host -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495394] Re: autostart almost always fails on boot time host
It seems there is another problem with my configuration that causes libvirt to have problems with autostarting virtual machines. I am using software RAID 1 with mdadm and my virtual machines are running on an LVM2 partition on md0. It seems the LVM2 volume is not yet available at the point where libvirt tries to start my virtual machines: libvirtd: 20:42:16.345: 1389: error : qemuAutostartDomain:275 : Failed to autostart VM 'ns': unable to set user and group to '114: 125' on '/dev/mapper/storage-st0': No such file or directory libvirtd: 20:42:16.346: 1389: error : virSecurityDACSetOwnership:125 : unable to set user and group to '114:125' on '/dev/mapper/s torage-st1': No such file or directory So it seems at this point it is not the bridge that is causing problems, but it is mdadm in combination with LVM2. According to my /var/log/boot.log the mdadm monitoring daemon is started after libvirt. But I'm not sure if the monitoring application has anything to do with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/495394 Title: autostart almost always fails on boot time host -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495394] Re: autostart almost always fails on boot time host
I can reproduce this on a fresh Ubuntu 11.04 using two 11.04 virtual machines (I had better luck with my previous 10.10 install that did work properly for me). The patch provided by Mika does not seem to work for me, libvirt does not seem to be started properly with it (my domains are not shown in virsh with a `list --all' for example). My boot.log shows two lines with `Stopping Check if bridged network is up. OK' though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/495394 Title: autostart almost always fails on boot time host -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40189] Re: autofs needs to be restarted to pick up some shares
I have this problem as well: Ubuntu 9.10 and reading mount points from an ldap server. The ldap server is running on a guest virtual machine, while the host itself needs autofs. Tried moving autofs from S19 in the init scripts to S30 (after libnss-ldap and after qemu-kvm and libvirt- bin), but that didn't help. I also tried Sebastian Veldhuisen his suggestion, but that didn't work either. -- autofs needs to be restarted to pick up some shares https://bugs.launchpad.net/bugs/40189 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495394] Re: autostart almost always fails on boot time host
Is there anything we can do to help somebody looking into this? I'm happy to provide more information if necessary. Should we look into other related packages that might cause the problem and file bug reports for those? For me this bug is pretty much a show stopper, autostarting domains is something I really need working. -- autostart almost always fails on boot time host https://bugs.launchpad.net/bugs/495394 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495394] Re: autostart almost always fails on boot time host
I tried setting bridge_maxwait=0, I only booted two times thereafter to see what happened. In both occasions some of the VM's with autostart booted, but not all of them (first time 2/5, second time 4/5). So, at best this might have helped a bit, but it is not a solution for the problem. The filesystem check, that only takes a couple of seconds, is still a good solution. When I setup my system so that it checks the filesystem (on which my host OS is installed, not the filesystem on which the VM's are installed), all VM's start consistently. -- autostart almost always fails on boot time host https://bugs.launchpad.net/bugs/495394 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495394] Re: autostart almost always fails on boot time host
I've been able to start up all domains consistently on each boot of the host OS, by changing the parameters of the partition the host OS is installed on. I've forced a check of this filesystem on each system boot, and all domains are running consistently after the host is booted. The filesystem check only takes a couple of seconds, I still don't know whether it is just the extra delay during boot time gives libvirt the necessary time to get the domains up, or whether something else is going on. -- autostart almost always fails on boot time host https://bugs.launchpad.net/bugs/495394 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495394] Re: autostart almost always fails on boot time host
Just rebooted the host, which started checking the file system. Thereafter all domains seemed to be up. Unsure whether this was coincidence (can't remember seeing all domains up after a reboot before), or whether the extra boot time somehow caused the domains to come up as expected. -- autostart almost always fails on boot time host https://bugs.launchpad.net/bugs/495394 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495394] [NEW] autostart almost always fails on boot time host
Public bug reported: host OS: lsb_release -rd: 1. Release of Ubuntu: Description:Ubuntu 9.10 Release:9.10 Linux 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux 2. Version of package: apt-cache policy libvirt-bin libvirt-bin: Installed: 0.7.0-1ubuntu13.1 Candidate: 0.7.0-1ubuntu13.1 Version table: *** 0.7.0-1ubuntu13.1 0 500 http://nl.archive.ubuntu.com karmic-updates/main Packages 100 /var/lib/dpkg/status 0.7.0-1ubuntu13 0 500 http://nl.archive.ubuntu.com karmic/main Packages 3. What I expected to happen: Domains that are marked `autostart' should be running after the host was booted. 4. What happened instead: - auto starting domains mostly fails when booting the host OS (Ubuntu 9.10) - auto starting the same domains does work when using Ubuntu 8.04.3 LTS or Ubuntu 9.04 as host OS - auto starting the same domains does work when invoking `/etc/init.d/libvirt-bin restart' Libvirtd is running. There are symlinks in /etc/libvirt/qemu/autostart. Mostly none of my domains are running, however sometimes a domain succeeds and is booted (say 1 in 10 attempts a domain succeeds to boot during the host boot process). When, after booting the host, I run `/etc/init.d/libvirt-bin restart' all of my domains are coming up as expected. Autostart works for all domains while using Ubuntu 8.04.3 LTS or Ubuntu 9.04 as host OS. I'm using Ubuntu 9.04 and 9.10 guest OS'es. Some of them were created under Ubuntu 9.04 and some of them were created on Ubuntu 9.10. Most of the domains are installed on a LVM, but I also tried creating a file based virtual machine that is located on the boot device of the host OS. There is no difference between these domains, all of them are booted only very sporadicly while booting the host OS. All domains are using a bridge device that I specified myself, and using static IP addresses. I removed the default network created by libvirt, because I don't use it (however: before I deleted that, autostart didn't work either). The bridge device works properly, I can log in my virtual machines via ssh and I use the bridge as well to talk to the internal network. I tried setting the bug logging level in `/etc/libvirt/libvirt.conf' to 1, but I don't see anything in the files in `/var/log' that explains why my domains are not auto-starting during boot time of the host OS (or at least, nothing that I recognize). If there is anything else I could try, or any other information I should provide, please let me know. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- autostart almost always fails on boot time host https://bugs.launchpad.net/bugs/495394 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218230] Re: gtk file dialog blocks on trackerd (via dbus) for 25s for users with NFS homedirs
I experienced the same problem. Opening a file dialog in any application causes a 25 second freeze of the program. Thereafter the dialog appears and can be used. I am using fully updated Ubuntu 8.04.2 (64 bits) clients and server. The problem occurs only with user accounts that have NFS mounted homedirs, when using a program on a client pc. Removing `tracker' from the clients solved the problem for me. I also have seen some programs trying to access `/home/.hidden' like described by somebody above. Allthough I am not sure yet if this causes any problems in my case. -- gtk file dialog blocks on trackerd (via dbus) for 25s for users with NFS homedirs https://bugs.launchpad.net/bugs/218230 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259797] Re: installation of mdadm causes freeze during boot of Hardy
After another fresh installation, without installing mdadm my system also freezes sometimes (allthough not that consequent as when mdadm is installed). I even got a freeze while I was in the system bios, so I guess the real problem is with my hardware. -- installation of mdadm causes freeze during boot of Hardy https://bugs.launchpad.net/bugs/259797 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259797] [NEW] installation of mdadm causes freeze during boot of Hardy
Public bug reported: Binary package hint: mdadm I have a fresh installation of Ubuntu 8.04 which has three harddisks (all ide, pata disks): /dev/sda (contains '/' on /dev/sda1 and swap on /dev/sda2) /dev/sdb /dev/sdc I would like to create a raid 1 array of sdb and sdc. Everything runs fine until I installed mdadm. I tried directly after installing mdadm to create a raid1 (mirror) array with mdadm --create /dev/md0 --raid-devices=2 /dev/sdb /dev/sdc This caused my system to freeze. After I tried to reboot, the system froze during booting. Next thing I tried was installing mdadm on a clean Ubuntu 8.04 installation, and reboot before creating any raid arrays. This also caused a freeze of the system during the boot process. I tried booting with the failsafe option in the ubuntu boot menu, this throws me back to a 'busybox': (initramfs): If I try to execute some commands, the system freezes after a short while. I tried booting the system with the ubuntu live cd so I could edit the mdadm.conf file. I changed the following lines: DEVICE /dev/sdb /dev/sdc # (not sure anymore what the default value was) # (commented this one out, because I didn't specify any arrays yet) # ARRAY /dev/md0 level=raid1 num-devices=2 UUID= After that I wasn't dropped back to the busybox, but the system still froze during the boot process. I am now out of options and I have no clue what is actually going on here or how I could possibly fix this so I can boot my system. It seems the system just freezes when mdadm tries to build an array (while I didn't specify anything), it also freezes when I did specify the right disks. Another thing which I am not sure about: when I boot using the live cd, and I mount /dev/sda1, it lists a lot of md devices in the mounted /dev/md* (ranging from md0 to md31). Is this normal behavoir? Greetings, Heiko ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: hardy initramfs mdadm -- installation of mdadm causes freeze during boot of Hardy https://bugs.launchpad.net/bugs/259797 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
