[Bug 525552] Re: Byobu overwrites shell prompt setting
I also see this behavior with byobu 5.60-0ubuntu1 on Ubuntu 13.10. I can run byobu manually or automatically at login (using byobu-enable) but the aliases and functions I have in a /etc/profile.d/lxc-helpers.sh script aren't available to me. Interestingly, when I run tmux it does have my profile (aliases and funtions) available. As a workaround for byobu I just append the following to my ~/.bashrc file to re-source the profile which gets everything working as expected. . /etc/profile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/525552 Title: Byobu overwrites shell prompt setting To manage notifications about this bug go to: https://bugs.launchpad.net/byobu/+bug/525552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1270961] [NEW] Install failed due to missing /etc/lxc when using Jan 20 Saucy daily build
Public bug reported: I tried multiple times to install the 1.0.0~beta2+master~20140120-1600-0ubuntu1~ppa1~saucy1 daily build in Saucy and the preinstall script failed each time because the /etc/lxc directory is missing. ** Affects: lxc (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/1270961 Title: Install failed due to missing /etc/lxc when using Jan 20 Saucy daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1270961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016695] Re: add console=tty1 to cloud-image kernel boot parameters
That's great! Thanks for working this in. Will it make it into 12.04 at all or will it only be in 12.10 and beyond? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty1 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016695] Re: add console=tty0 to cloud-image kernel boot parameters
Thanks Clint. I understand that we can't lose any messages going to the serial console. So I experimented and I have a different solution that I think would satisfy. My main goal is to *by default* be able to see in the VMware console the kernel messages as well as the first few messages from cloud-init that show cloud-init is searching for the EC2 datasource by default and is timing out. Sending this info only to the serial port means anyone unfamiliar with running a cloud-image in VMware (or other hypervisor) may not understand that cloud-init is behind the scenes searching for the EC2 datasource and timing out. They would sit there wondering why it's taking so long to boot. *Maybe* they'd figure out they can add console=tty1 to their kernel boot parameters so they can see what is going on. I personally think Ubuntu server is great but this could be frustrating to others and potentially lead them to believe something just ain't right with Ubuntu servers. My new solution is to add console=tty1 *before* console=ttyS0. Note that it's tty1 and not tty0. This produces the same results as expected for the serial port. All messages are output to serial as usual. This also outputs all kernel messages and just enough of the cloud-init messages to tty1 which makes it visible in VMware's vSphere console where you can watch it search for the EC2 datasource and timeout. The remainder of the cloud-init messages (including the cloud-init final message) are not visible in the console so you'd have to log in and check the cloud-init log in /var/log to see it's status but that's much better than nothing at all. When the server is done booting the VMware console displays the tty1 as expected which is why I used tty1 instead of tty0. I tested all this by using VMware's ability to output serial port to a file. I have attached a file for the serial port output for each of the following grub kernel parameter entries: linux /boot/vmliuz-3.2.0-24-virtual root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 linux /boot/vmliuz-3.2.0-24-virtual root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 ds=nocloud The first shows cloud-init searching for EC2 datasource and timing out. The second shows the results when cloud-init is configured with ds=nocloud. Do you think this sounds reasonable? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016695] Re: add console=tty0 to cloud-image kernel boot parameters
** Attachment added: "console=tty1 console=ttyS0" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+attachment/3212313/+files/serial_output_tty1_ttyS0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016695] Re: add console=tty0 to cloud-image kernel boot parameters
** Attachment added: "console=tty1 console=ttyS0 ds=nocloud" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+attachment/3212314/+files/serial_output_tty1_ttyS0_nocloud.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016695] Re: add console=tty1 to cloud-image kernel boot parameters
Thanks Ben. I'm not familiar with how these changes actually make it into new releases. If this change actually gets made would it make it into 12.04.1 in August? ** Summary changed: - add console=tty0 to cloud-image kernel boot parameters + add console=tty1 to cloud-image kernel boot parameters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty1 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016695] [NEW] add console=tty0 to cloud-image kernel boot parameters
Public bug reported: I use VMware vSphere Client's to manage my Ubuntu 12.04 cloud-image based vm's. vSphere is able to display the console of the vm as it boots but because the default kernel boot parameter is set to use console=ttyS0 I can't see anything until booting is done unless I manually add console=tty0 first. Can you add console=tty0 after console=ttyS0 so boot process will display automatically? I would really appreciate it. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: cloud-images ec2-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016695] Re: add console=tty0 to cloud-image kernel boot parameters
Scott, I think the following info is relevant to your comment. http://www.kernel.org/doc/Documentation/serial-console.txt "You can specify multiple console= options on the kernel command line. Output will appear on all of them. The last device will be used when you open /dev/console. So, for example: console=ttyS1,9600 console=tty0 defines that opening /dev/console will get you the current foreground virtual console, and kernel messages will appear on both the VGA console and the 2nd serial port (ttyS1 or COM2) at 9600 baud." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861137] Re: Openssl TLS errors while connecting to SSLv3 sites
I have the same problem. My 10.04 Apache server reverse proxied my Tomcat 6.0.24 OpenJDK server just fine. I just swapped out the 10.04 Apache server with a 12.04 Apache server and the proxy failed until I used the solution mentioned in comment #6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861137 Title: Openssl TLS errors while connecting to SSLv3 sites To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861137] Re: Openssl TLS errors while connecting to SSLv3 sites
I just found that instead of restricting the available ciphers on the Tomcat server as per comment #6 I am also able to workaround the problem by just restricting the available ciphers that the Apache proxy uses by adding "SSLProxyCipherSuite RC4-SHA" to my Apache VirtualHost config. This makes more sense to me to since the problem is with the new server rather than with the old Tomcat server. (At least that's my understanding.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861137 Title: Openssl TLS errors while connecting to SSLv3 sites To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925023] Re: Likewise win domain user user cannot access audio
I'm having exactly the same problem. I've reinstalled Ubuntu 11.10 a few times now and local user's audio works fine. When I login with a domain user the audio hardware isn't listed under "Sound settings". I can't change volume or anything and normal system sounds don't work. Strange thing is that I can hear web videos and skype calls. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925023 Title: Likewise win domain user user cannot access audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/925023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
