Re: [Bug 889117] Re: new version of mediathekview -needs packaging
Hi, Am 13.10.2012 11:41, schrieb Linuxexperte: there are foten new packages of mediathekview out on sourceforge and other download-sites. Will there be a ppa-repository, to keep mediathekveiw updated with the new updated versions in future?? Because: development on this app never stopps and continues and will continue in future. A debian version of mediathekview was uploaded to Debian unstable on oct 3rd. Please try this version. Christoph -- Christoph Martin, Zentrum für Datenverarbeitung, Uni-Mainz, Germany Instant-Messaging: Jabber: mar...@uni-mainz.de (Siehe http://www.zdv.uni-mainz.de/4010.php) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889117 Title: new version of mediathekview -needs packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediathekview/+bug/889117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838968] Re: static-network-up event does not wait for interfaces to have an address
I don't think this bug is really fixed. At least not in the versions which are in precise: isc-hdcp-client=4.1.ESV-R4-0ubuntu5.2, ifupdown=0.7~beta2ubuntu8. The problem occurs, if a dhcp server is not availlable for some time. Then dhclient will send one DHCP-REQUEST on ifup or lease renewal and might never get an answer inside the timeout interval because this one DHCP-REQUEST package might get lost. Then dhclient will terminate and the interface will get never configured, thus making the host unavaillable from the network. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/838968 Title: static-network-up event does not wait for interfaces to have an address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/838968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 838968] Re: static-network-up event does not wait for interfaces to have an address
I don't think this bug is really fixed. At least not in the versions which are in precise: isc-hdcp-client=4.1.ESV-R4-0ubuntu5.2, ifupdown=0.7~beta2ubuntu8. The problem occurs, if a dhcp server is not availlable for some time. Then dhclient will send one DHCP-REQUEST on ifup or lease renewal and might never get an answer inside the timeout interval because this one DHCP-REQUEST package might get lost. Then dhclient will terminate and the interface will get never configured, thus making the host unavaillable from the network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838968 Title: static-network-up event does not wait for interfaces to have an address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/838968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 747084] [NEW] announces cc and sc to wrong network
Public bug reported: I installed eucalyptus clc and walrus on a host with public network and then cc and sc on a host with both public and private network. The installation asked wether I want to use eth1 as private network to connect to the nc's and I answerd yes. But now cc and nc get published via avahi with their public IP address and not with the private IP address. The consequense is that the node controller installed on the private network will try to connect the cc and sc with the wrong IP and will fail. The problem is, that /etc/eucalyptus/eucalyptus-ipaddr.conf tries to find out the IP address by checking the default route. But in this setup the default route is via the public interface. It should take the value of VNET_PRIVINTERFACE in /etc/eucalyptus/eucalyptus.conf to find out the correct interface and ip address. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-cc 2.0+bzr1241-0ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.35-27.48-server 2.6.35.11 Uname: Linux 2.6.35-27-server x86_64 NonfreeKernelModules: mptspi mptscsih mptbase e1000 floppy megaraid_mbox megaraid_mm .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=cluster1 Architecture: amd64 Date: Fri Apr 1 10:37:23 2011 InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/747084 Title: announces cc and sc to wrong network -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 747084] Re: announces cc and sc to wrong network
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/747084 Title: announces cc and sc to wrong network -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 747084] [NEW] announces cc and sc to wrong network
Public bug reported: I installed eucalyptus clc and walrus on a host with public network and then cc and sc on a host with both public and private network. The installation asked wether I want to use eth1 as private network to connect to the nc's and I answerd yes. But now cc and nc get published via avahi with their public IP address and not with the private IP address. The consequense is that the node controller installed on the private network will try to connect the cc and sc with the wrong IP and will fail. The problem is, that /etc/eucalyptus/eucalyptus-ipaddr.conf tries to find out the IP address by checking the default route. But in this setup the default route is via the public interface. It should take the value of VNET_PRIVINTERFACE in /etc/eucalyptus/eucalyptus.conf to find out the correct interface and ip address. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-cc 2.0+bzr1241-0ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.35-27.48-server 2.6.35.11 Uname: Linux 2.6.35-27-server x86_64 NonfreeKernelModules: mptspi mptscsih mptbase e1000 floppy megaraid_mbox megaraid_mm .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=cluster1 Architecture: amd64 Date: Fri Apr 1 10:37:23 2011 InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/747084 Title: announces cc and sc to wrong network -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 747084] Re: announces cc and sc to wrong network
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/747084 Title: announces cc and sc to wrong network -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742443] [NEW] cc looses database information after restart
Public bug reported: When doing restart eucalyptus-cc (not 'restart eucalyptus-cc CLEAN=1') the cc database information are lost. iptables-save does not show anymore the forwarding/nat rules for the vm's also the file //var/run/eucalyptus/net/euca-dhcp.conf does not anymore include the dhcp information for the vm's I know that there existed an old bug, but it was reported as fixed some time ago. I tried version 2.0+bzr1241-0ubuntu4.1 from maverick and 2.0.1+bzr1256-0ubuntu2 from natty. The problem persists in both versions. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-cc 2.0.1+bzr1256-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-27.48-server 2.6.35.11 Uname: Linux 2.6.35-27-server x86_64 .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=cluster1 Architecture: amd64 Date: Fri Mar 25 14:10:45 2011 InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/742443 Title: cc looses database information after restart -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 742443] Re: cc looses database information after restart
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/742443 Title: cc looses database information after restart -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 742443] [NEW] cc looses database information after restart
Public bug reported: When doing restart eucalyptus-cc (not 'restart eucalyptus-cc CLEAN=1') the cc database information are lost. iptables-save does not show anymore the forwarding/nat rules for the vm's also the file //var/run/eucalyptus/net/euca-dhcp.conf does not anymore include the dhcp information for the vm's I know that there existed an old bug, but it was reported as fixed some time ago. I tried version 2.0+bzr1241-0ubuntu4.1 from maverick and 2.0.1+bzr1256-0ubuntu2 from natty. The problem persists in both versions. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: eucalyptus-cc 2.0.1+bzr1256-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-27.48-server 2.6.35.11 Uname: Linux 2.6.35-27-server x86_64 .etc.eucalyptus.eucalyptus.cc.conf: CC_NAME=cluster1 Architecture: amd64 Date: Fri Mar 25 14:10:45 2011 InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eucalyptus ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742443 Title: cc looses database information after restart -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742443] Re: cc looses database information after restart
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742443 Title: cc looses database information after restart -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737796] [NEW] switching users and logging out logs both users out
Public bug reported: Binary package hint: gdm On Ubuntu Natty (development branch). What happens: 1) Fresh reboot, log in as user A. 2) Switch to user B. 3) User A is on tty8, user B on tty9 (Confirmed by switching with CTRL-ALT-F[7-9], you switch either to the desktop or the unlock dialogue.) 4) User B logs out. 5) You drop to the gdm login screen on tty8. User A isn't logged in any more. What should happen: User A should stay logged in. Displaying the gdm login screen makes sense, but it shouldn't kill user A's session. ** Affects: gdm (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/737796 Title: switching users and logging out logs both users out -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
