[Bug 1726548] Re: Windows resized after resume
I was also having this problem on a System 76 laptop using Wayland with a hidpi screen (3200x1800) and scaling set to 150%. I was able to fix it by doing: gsettings set org.gnome.desktop.interface scaling-factor 1 https://askubuntu.com/questions/1073568/preventing-window-resizing- after-resume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422994] Re: sata_via hard resetting link / freeze: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6
I took the default Lucid kernel, applied this patch http://www.spinics.net/lists/linux-ide/msg37898.html, built it and this fixed this problem for me. -- sata_via hard resetting link / freeze: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 https://bugs.launchpad.net/bugs/422994 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 573482] Re: Java plugin is not working in 64 -ubuntu 10.4
Java is working in both chrome and firefox for me after installing the updates. Here's the output from Firefox 'about:plugins' in case you are still interested: IcedTea NPR Web Browser Plugin (using IcedTea6 1.8 (6b18-1.8-4ubuntu3)) File: IcedTeaPlugin.so Version: The IcedTea NPR Web Browser Plugin (using IcedTea6 1.8 (6b18-1.8-4ubuntu3)) executes Java applets. MIME Type Description SuffixesEnabled application/x-java-vm IcedTea class,jar Yes application/x-java-applet IcedTea class,jar Yes application/x-java-applet;version=1.1 IcedTea class,jar Yes application/x-java-applet;version=1.1.1 IcedTea class,jar Yes application/x-java-applet;version=1.1.2 IcedTea class,jar Yes application/x-java-applet;version=1.1.3 IcedTea class,jar Yes application/x-java-applet;version=1.2 IcedTea class,jar Yes application/x-java-applet;version=1.2.1 IcedTea class,jar Yes application/x-java-applet;version=1.2.2 IcedTea class,jar Yes application/x-java-applet;version=1.3 IcedTea class,jar Yes application/x-java-applet;version=1.3.1 IcedTea class,jar Yes application/x-java-applet;version=1.4 IcedTea class,jar Yes application/x-java-applet;version=1.4.1 IcedTea class,jar Yes application/x-java-applet;version=1.4.2 IcedTea class,jar Yes application/x-java-applet;version=1.5 IcedTea class,jar Yes application/x-java-applet;version=1.6 IcedTea class,jar Yes application/x-java-applet;jpi-version=1.6.0_18 IcedTea class,jar Yes application/x-java-bean IcedTea class,jar Yes application/x-java-bean;version=1.1 IcedTea class,jar Yes application/x-java-bean;version=1.1.1 IcedTea class,jar Yes application/x-java-bean;version=1.1.2 IcedTea class,jar Yes application/x-java-bean;version=1.1.3 IcedTea class,jar Yes application/x-java-bean;version=1.2 IcedTea class,jar Yes application/x-java-bean;version=1.2.1 IcedTea class,jar Yes application/x-java-bean;version=1.2.2 IcedTea class,jar Yes application/x-java-bean;version=1.3 IcedTea class,jar Yes application/x-java-bean;version=1.3.1 IcedTea class,jar Yes application/x-java-bean;version=1.4 IcedTea class,jar Yes application/x-java-bean;version=1.4.1 IcedTea class,jar Yes application/x-java-bean;version=1.4.2 IcedTea class,jar Yes application/x-java-bean;version=1.5 IcedTea class,jar Yes application/x-java-bean;version=1.6 IcedTea class,jar Yes application/x-java-bean;jpi-version=1.6.0_18IcedTea class,jar Yes -- Java plugin is not working in 64 -ubuntu 10.4 https://bugs.launchpad.net/bugs/573482 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 573482] Re: Java plugin is not working in 64 -ubuntu 10.4
I tried this PPA, but it still isn't working for me. It does look like this PPA installs /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/IcedTeaPlugin.so. The default one only installed the i386 version. I'm attaching a strace log of chrome starting up. You can see it finding the plugin, but it won't load any java applets I've tried (http://nitro.ucsc.edu/). ** Attachment added: strace.log http://launchpadlibrarian.net/52192627/strace.log -- Java plugin is not working in 64 -ubuntu 10.4 https://bugs.launchpad.net/bugs/573482 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
Here's dmesg from 2.6.33-rc8 without the pci=use_crs option. ** Attachment added: 2.6.33-rc8 dmesg without pci=use_crs http://launchpadlibrarian.net/39379719/dmesg-2.6.33-rc8-no-use_crs.txt -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
Here's dmesg from 2.6.33-rc8 with the pci=use_crs ** Attachment added: 2.6.33-rc8 dmesg with pci=use_crs http://launchpadlibrarian.net/39379731/dmesg-2.6.33-rc8.txt -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
This fixed it for me as well. You rock, man. -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
On the off chance anyone is paying attention who knows anything about this stuff, here's some more data. I'm uploading 6 files. Three each for my laptop with 2GB main memory installed and 4GB installed. One is cat /proc/mtrr, one is lspci -v, and the last is a copy of Xorg.log. Also I found a program that prints mtrrs in Windows XP 32-bit (where the video works with 4GB installed) and I ran that on my laptop with 4GB installed: Address StartAddress End Memory Type Fixed Ranges 0x 0x0009 WriteBack 0x000a 0x000b Uncacheable 0x000c 0x000f WriteProtected ** Attachment added: lspci -v with 2GB in machine http://launchpadlibrarian.net/35337045/2g-lspci.log -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
** Attachment added: cat /proc/mtrr on 2gb http://launchpadlibrarian.net/35337053/2g-mtrr.log -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
** Attachment added: 2g-xorg.log http://launchpadlibrarian.net/35337092/2g-xorg.log -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
** Attachment added: cat /proc/mtrr with 4GB http://launchpadlibrarian.net/35337132/4g-mtrr.log -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
** Attachment added: lspci -v with 4GB http://launchpadlibrarian.net/35337163/4g-lspci.log -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
** Attachment added: X.org.log with 4g http://launchpadlibrarian.net/35337185/4g-xorg.log -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 341681] Re: [HD 3650] Startup failure Idle timed out, resetting engine...
One thing I forgot to mention is that these attempts to launch X are with the ATI proprietary driver. It exhibits nearly the same behavior as the radeon driver. The only difference is that if I use the ATI proprietary driver, it doesn't sit at a blank screen forever when I have 4GB in the machine, instead it exits with an error. Just like the radeon driver, though, if I take out 2GB, everything works fine. All those files were from the 64bit kernel. The results are the same with the 32bit kernel. I kinda feel like this is some sort of MTRR problem, but I'm not really up on MTRRs and while I have tried fiddling with them a bunch in an effort to get it to work, I've had no luck. -- [HD 3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 343390] Re: [i855] When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats.
I tried it with the Karmic Alpha 2 CD and that seems to have fixed the problem. -- [i855] When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats. https://bugs.launchpad.net/bugs/343390 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 341681] Re: [HD3650] Startup failure Idle timed out, resetting engine...
I've got the same problem. Tried all the solutions mentioned, but the only thing that works is taking out 2GB of the 4GB of main memory. I'm game for trying any patches or tests if anyone has any ideas. -- [HD3650] Startup failure Idle timed out, resetting engine... https://bugs.launchpad.net/bugs/341681 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 343390] Re: When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats.
Of course the VESA driver kept producing a flickering screen at 1024x768, so I downloaded the 2.4.2 version of the intel driver (2.4.1 is the version that was installed on there through the package system), built, and installed it. That seems to have fixed the problem. -- When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats. https://bugs.launchpad.net/bugs/343390 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 343390] [NEW] When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats.
Public bug reported: This is XUbuntu 8.10. The graphics card is an Intel 855GM. The screen was working fine from the original 8.10 install disk until I let it update (some 170 updates). After the update, when X would come up it would come up black and then sort of fade to white in blobs then parts of the screen would fade back to black. Very weird. This is an industrial computer with a built in touch screen (penmount). I haven't installed the touch screen drivers yet on this one. I have two of them. The other one I haven't updated so it is working fine along with the touch screen. I managed to work around it by forcing it to use the VESA driver. I'm attaching the relevant logs and config files. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats. https://bugs.launchpad.net/bugs/343390 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 343390] Re: When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats.
** Attachment added: lspci -vvnn output http://launchpadlibrarian.net/23892933/lspci.txt -- When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats. https://bugs.launchpad.net/bugs/343390 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 343390] Re: When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats.
** Attachment added: Xorg log. http://launchpadlibrarian.net/23892946/Xorg.0.log -- When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats. https://bugs.launchpad.net/bugs/343390 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 343390] Re: When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats.
** Attachment added: xorg.conf http://launchpadlibrarian.net/23892979/xorg.conf ** Description changed: This is XUbuntu 8.10. + + The graphics card is an Intel 855GM. The screen was working fine from the original 8.10 install disk until I let it update (some 170 updates). After the update, when X would come up it would come up black and then sort of fade to white in blobs then parts of the screen would fade back to black. Very weird. This is an industrial computer with a built in touch screen (penmount). I haven't installed the touch screen drivers yet on this one. I have two of them. The other one I haven't updated so it is working fine along with the touch screen. I managed to work around it by forcing it to use the VESA driver. I'm attaching the relevant logs and config files. -- When X starts, screen starts black, fades in sort of organic fashion to white, then fades to black. Repeats. https://bugs.launchpad.net/bugs/343390 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 159106] Re: network-manager not able to set default route if netmask is 255.255.255.255
I have a similar problem when I directly attach my machine to my ATT DSL. It works fine on Windows, but here's what I get in 'daemon.log': Jun 30 15:49:26 safir NetworkManager: info Retrieved the following IP4 configuration from the DHCP daemon: Jun 30 15:49:26 safir NetworkManager: infoaddress 99.165.93.98 Jun 30 15:49:26 safir NetworkManager: infonetmask 255.255.0.0 Jun 30 15:49:26 safir NetworkManager: infobroadcast 255.255.255.255 Jun 30 15:49:26 safir NetworkManager: infogateway 151.164.184.123 Jun 30 15:49:26 safir NetworkManager: infonameserver 192.168.1.254 Jun 30 15:49:27 safir NetworkManager: WARN nm_system_device_set_ip4_route(): Failed to set IPv4 default route on 'eth1': No such process Notice that it is saying the netmask is 255.255.0.0 and assigning me the IP address 99.165.93.98. Then it says the gateway is at 151.164.184.123. I don't see how that is supposed to work. I booted into Windows and did a 'netstat -rn' and Windows makes the default route to the gateway (151.164.184.123) on interface (99.165.93.98), so I guess this would be the equivalent on Ubuntu: route add -host 151.164.184.123 dev eth1 route add default gw 151.164.184.123 This is pretty much what Jens Georg suggested in his original description, but John V's suggestion of checking if the mask is /32 won't work in my case. I took a look at John V's patch, though, and it doesn't check the netmask, so it'll probably work for my case as well. So, probably didn't need to add this comment after all. Well, it is a case to keep in mind. -- network-manager not able to set default route if netmask is 255.255.255.255 https://bugs.launchpad.net/bugs/159106 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 195630] [NEW] Can't change permissions on a folder with nautilus.
Public bug reported: 1. Places - Home folder. 2. File - Create folder. 3. Type 'foo' for the name of the folder and hit enter. 4. Right click on folder named 'foo' and choose Properties. 5. Click on 'Permissions' tab. 6. Change 'File Permissions' for 'Others' to 'Read/Write'. 7. Click on 'Close'. 8. Right click on folder named 'foo' and choose Properties. 9. Click on 'Permisions' tab. Look at 'File Permissions' for 'Others'. It is set back to '---'. It should be 'Read/Write'. Tried the same thing as root using 'gksudo nautilus'. Same problem. System Information: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION=Ubuntu 7.10 ii nautilus 1:2.20.0-0ubuntu7 file manager and graphical shell for GNOME ** Affects: ubuntu Importance: Undecided Status: New -- Can't change permissions on a folder with nautilus. https://bugs.launchpad.net/bugs/195630 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 195630] Re: Can't change permissions on a folder with nautilus.
Normally I never use Nautilus, but I was talking someone through creating permissions on a folder over the phone and we kept getting stuck because I kept telling him to give read/write permissions to the folder, when really what I should have been saying is 'create and delete' which is what it says for the folder permissions in Nautilus. After Matt confirmed the bug it hit me that this is really a UI design bug. What I would do is take away the 'file permission' drop downs on that properties window and have a button which says 'change permissions on enclosed files'. Then when you click that button, it asks for the three permission drop downs. That would say to me that these permissions are not 'properties' of the folder which is the way it seems now. -- Can't change permissions on a folder with nautilus. https://bugs.launchpad.net/bugs/195630 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 120375] Re: cannot boot raid1 with only one disk
Did you wait 3 minutes on the test with one disc detached? I think that by default, there is a three minute timeout before it gets to the place where Ken's patch is. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I haven't messed around with the problem in Gutsy, but what Daniel said above about the difference between Fiesty and Gusty is not correct. Fiesty was also launching mdadm as devices were discovered from udev and that is exactly the problem. Both are pretty much the same, just the code has moved around some. Unfortunately the box I fixed this on is now in production and I haven't had the chance to setup another test one to port my fix to Gutsy, so I'll explain what's going on, and maybe someone else can fix it. The version of mdadm doesn't have anything to do with this problem. This problem is entirely due to the Ubuntu startup scripts. What Ubuntu is doing is as each device gets discovered by udev it runs: mdadm --assemble --scan --no-degraded If your RAID is made up of say sda1 and sdb1, then when 'sda1' is discovered by Linux, udev runs 'mdadm --assemble --scan --no-degraded'. Mdadm tries to build a RAID device using just 'sda1' because that's the only drive discovered so far. It fails because of the '--no-degraded' flag which tells it to not assemble the RAID unless all of the devices are present. If it didn't include the '--no-degraded' flag, it would assemble the RAID in degraded mode. This would be bad because at this point we don't know if 'sdb1' is missing or it just hasn't been discovered by udev yet. So, then Linux chugs along and finds 'sdb1', so it calls 'mdadm --assemble --scan --no-degraded' again. This time both parts of the RAID (sda1 and sdb1) are available, so the command succeeds and the RAID device gets assembled. This all works great if all the RAID devices are working, but since it allways runs mdadm with the '--no-degraded' option, it won't assemble the RAID device if say 'sda1' is broken or missing. My solution was to wait until mounting root failed due to a timeout and then try 'mdadm --assemble --scan' without '--no-degraded' to see if we can assemble a degraded RAID device. Hopefully by the time the root mount has timed out, Linux has discovered all of the disks that it can. This works on my Fiesty box, but as I said above, stuff got moved around for Gutsy and I haven't had a chance to build another box to try it out and fix Gutsy. Also I think my script didn't take into account the scenario where the RAID device isn't root. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I've forgotten about how this works exactly, but if you take a look in:
/usr/share/initramfs-tools/scripts/local
If you look for the comment
# We've given up, but we'll let the user fix matters if they canomment:
The bit inside the while loop with the panic is the part that gets
executed if there is a timeout trying to mount root. Here's what I put
in my Fiesty version right before that comment.
if [ ! -e ${ROOT} ]; then
# Try mdadm in degraded mode in case some drive has failed.
/scripts/local-top/mdadm
fi
This doesn't work anymore because of the changes to Gutsy. You could
just try putting 'mdadm --assemble --scan' there, but that probably
won't work. Everything is a little tricky in these scripts because they
run before root is mounted, so stuff doesn't always work as you would
expect.
Also, you can't just modify these scripts. After you change them, you
have to use 'mkinitramfs' to generate the image that contains these
scripts that is used during the boot up. I'd put in instructions, but
I've forgotten how to do it myself.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I've only tried it on fiesty. I don't have a gutsy machine handy. You have the 'mdadm' package installed, right? If so, then they must have moved stuff around. You could try this: find / -type f -print0 | xargs -0 grep MD_DEGRADED_ARGS That will search the whole file system for the a file with MD_DEGRADED_ARGS in it, but if they've moved stuff around, the patch probably won't work anyway. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
There is a problem with the solution outlined by Scott James Remnant above. (https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/75681/comments/84) What happens when one of the raid devices has failed and it isn't getting detected? Take Scott's example a raid with (sda1 and sdb1): This should work as follows: * an underlying block device, sda1, is detected * udev (through vol_id) detects that this is a RAID member * udev invokes mdadm, which fails to assemble because the RAID-1 is not complete * the creation of a new raid, md0, is detected * udev fails to detect this device, because it is not yet complete At this point, mdadm should assemble the RAID with just sda1 because sdb1 is down, but in the current scheme mdadm only assembles the RAID if all drives are available. This sort of defeats the point of using any of the mirrored RAID schemes. So because the only case that I know of where this is an issue is a case with drive failure, how about trying to run mdadm again after the root mount timeout, but this time without the --no-degraded arg so that if we can assemble some of the RAID arrays without the missing drives, we do it. I'll attach some patches to some /usr/share/initramfs-tools scripts which fix this problem for me. So then the question is how do we know that sdb1 is down and should go ahead with assembling the RAID array? I'm not sure exactly what kind of information we have this early in the bootup process, but how about something like this ** Attachment added: A patch to handle the case where there is a failed RAID drive. http://launchpadlibrarian.net/8884018/failed-raid.patch -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/75681 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I've got a different way to fix this. After reading Bug #75681, it became clear why they have MD_DEGRADED_ARGS in there. They have that because /scripts/local-top/mdadm gets called every time a device marked raid gets called, but they only want mdadm to build the array once all the devices have come up. So I've stuck a line in the startup script that tries to mount root and if mounting root times out, then we try to run mdadm again, but this time we let it try and run with degraded disks. This way it will still startup automatically in the presence of RAID failures. ** Attachment added: Patch to boot after timeout using degraded RAID drives. http://launchpadlibrarian.net/8884059/failed-raid.patch -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
So, there is something wrong with that patch. Actually it seems to be working great, but when I disconnect a drive to fail it, it boots up immediately instead of trying mdadm after the timeout. So I'm guessing that the mdadm script is getting called without the from-udev parameter somewhere else. But it is working in some sense because the machine boots nicely with one of the RAID drives disconnected, or with both of them properly setup. So there might be some race problem with this patch. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
So, there is something wrong with that patch. Actually it seems to be working great, but when I disconnect a drive to fail it, it boots up immediately instead of trying mdadm after the timeout. So I'm guessing that the mdadm script is getting called without the from-udev parameter somewhere else.But it is working in some sense because the machine boots nicely with one of the RAID drives disconnected, or with both of them properly setup. So there might be some race problem with this patch. -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/75681 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 123888] Re: boot hangs with missing RAID device
*** This bug is a duplicate of bug 120375 *** https://bugs.launchpad.net/bugs/120375 ** This bug has been marked a duplicate of bug 120375 cannot boot raid1 with only one disk -- boot hangs with missing RAID device https://bugs.launchpad.net/bugs/123888 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68916] Files do not display when connected to FTP server run in a Japanese environment.
Public bug reported: 1. Start an ftp server in a Japanese language environment: LANGUAGE=ja_JP:ja:en_GB:en LANG=ja_JP.UTF-8 wu-ftpd -s 2. Choose 'Connect to Server from the Places menu. Create a connection to your ftp server using FTP with LOGIN. 3. Double click on the newly created folder on the desktop. No files will display. I went onto the ftp server and got rid of the two language environment variables and then started the server again. Now when I double click on the ftp folder, it works fine. This may also be a bug with wu-ftpd, but if I just use the command-line ftp to connect with ftpd, it looks ok to me. I watched the protocol interaction using tcpdump and gnome-vfs is requesting and receiving a directory listing, so part of the problem is that gnome-vfs isn't parsing the output from wu-ftpd correctly. Even if there is some bug in wu-ftpd, it would seem wise to correct the parsing problem in gnome-vfs to make it more compatible even with a (possibly)[ badly behaving ftp server. ** Affects: gnome-vfs (Ubuntu) Importance: Undecided Status: Unconfirmed -- Files do not display when connected to FTP server run in a Japanese environment. https://launchpad.net/bugs/68916 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
