[Bug 592434] Re: ssh -X user@machine hangs when using exit to terminate
This bug is still around 12.10. Openssh client and server version 1:6.0p1-3ubuntu1. Given the duration and progress (or lack thereof :-) of this bug: Anybody looking at this upstream? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/592434 Title: ssh -X user@machine hangs when using exit to terminate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/592434/+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 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)
also present in Ubuntu 13.04 Raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1004606 Title: virsh create-snapshot fails to create external snapshot (blockdev- snapshot-sync fails in json monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1004606/+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 592434] Re: ssh -X user@machine hangs when using exit to terminate
PS: I got the the following when I ran the ssh client with -vvvX and started an X11 application: debug3: channel 0: will not send data after close debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 3 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1) #2 x11 (t4 r4 i0/0 o0/0 fd 8/8 cc -1) #3 x11 (t4 r5 i0/0 o0/0 fd 9/9 cc -1) In contrast to this, ssh with just -vvv produced the following output when logging out of the server: debug3: channel 0: will not send data after close debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/592434 Title: ssh -X user@machine hangs when using exit to terminate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/592434/+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 1015223] Re: cloud-init-nonet main process killed by TERM signal
ading "normal exit SIGTERM" to /etc/init/cloud-init.conf will probably suppress the appearance of normal termination messages in dmesg. What would be slightly better, though probably overkill in this case, would be a signal handler that somehow pacifies upstart by catching SIGTERM and exiting more gracfully with 0 status. -- 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/1015223 Title: cloud-init-nonet main process killed by TERM signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1015223/+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 1050021] Re: autofs failed to mount .hidden
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: autofs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1050021 Title: autofs failed to mount .hidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1050021/+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 1014732] Re: log_error not set in my.cnf, errors not written anywhere
This bug was fixed in the package mysql-5.5 - 5.5.29-0ubuntu0.12.04.2 --- mysql-5.5 (5.5.29-0ubuntu0.12.04.2) precise-proposed; urgency=low [ Robie Basak ] * Update default my.cnf to log errors to /var/log/mysql/error.log instead of not logging errors at all (LP: #1014732). * Add attachment of error log /var/log/mysql/error.log to apport hook. -- Marc DeslauriersWed, 23 Jan 2013 08:43:56 -0500 ** Changed in: mysql-5.5 (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1014732 Title: log_error not set in my.cnf, errors not written anywhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1014732/+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 885758] Re: 'ldap passwd sync = yes' and ldap password not updated
** Description changed: - After upgrading a server (with ubuntu server) to lucid from previous LTS (hardy?), users start complain that, after changing passwords, windows works but other services (imap, ssh, ...) not. - After some hours of test, i've discovered that simply the NT/LM password got updated, the 'POSIX' ldap one not. + After upgrading a server (with ubuntu server) to lucid from previous LTS (hardy?), users start complaining that, after changing passwords, windows works but other services (imap, ssh, ...) don't. + After some hours of testing, I've discovered that simply the NT/LM password got updated, the 'POSIX' ldap one did not. Running 'smbpasswd -D 5 gaio' lead to: - smbldap_check_root_dse: Expected one rootDSE, got 0 + smbldap_check_root_dse: Expected one rootDSE, got 0 some other googling take me to the needs to add another ACL, so i've added: - access to attrs=namingcontexts -by * read + access to attrs=namingcontexts + by * read and now works. Some notes: - 1) i don't know if this is the correct/best ACL to add, and if this is a bug 'per se' or a side effects of the upgrade: i've no other lucid system to test with... - 2) this is probably a 'openldap upgrade bug' - 3) this is mainly a samba bug, i think: if i set 'ldap passwd sync = yes' and ldap password fail, i this it is better to reject the entire password changing operation, not to have ''half-changed'' password. + 1) I don't know if this is the correct/best ACL to add, and if this is a bug 'per se' or a side effects of the upgrade: I have no other lucid system to test with... + 2) This is probably a 'openldap upgrade bug'. + 3) This is mainly a samba bug, I think: if I set 'ldap passwd sync = yes' and ldap password fails. If it is better to reject the entire password changing operation, to not have a ''half-changed'' password. - I've marked also the ''security bug'' check because i think that this is - a security issue: sysadmin could set a dumb password for a first logon, + I've marked also the ''security bug'' check because I think that this is + a security issue: sysadmin could set a dumb password for a first login, then users change immediately but the dumb password remains for all non- windows services. thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/885758 Title: 'ldap passwd sync = yes' and ldap password not updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/885758/+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 1143009] [NEW] Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main)
Public bug reported: Please sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main) Explanation of the Ubuntu delta and why it can be dropped: * Resynchronise with Debian. (LP: #1023931) Remaining changes: - debian/puppetmaster-passenger.postinst: Make sure we error if puppet config print doesn't work - debian/puppetmaster-passenger.postinst: Ensure upgrades from <= 2.7.11-1 fixup passenger apache configuration. * Dropped upstreamed patches: - debian/patches/CVE-2012-1906_CVE-2012-1986_to_CVE-2012-1989.patch - debian/patches/puppet-12844 - debian/patches/2.7.17-Puppet-July-2012-CVE-fixes.patch * Drop Build-Depends on ruby-rspec (in universe): - debian/control: remove ruby-rspec from Build-Depends - debian/patches/no-rspec.patch: make Rakefile work anyway if rspec isn't installed so we can use it in debian/rules. Changelog entries since current raring version 2.7.18-1ubuntu1: puppet (3.0.0~rc2-1) experimental; urgency=low * Imported Upstream version 3.0.0~rc2 * Rename configuration file /etc/apache2/sites-available/puppetmaster to puppetmaster.conf to match apache2 policy change (Closes: #673970) * Check if a2dissite is present for postrm (Closes: #674011) * Workaround apache2 a2* utils API change to stay compatible to both apache 2.2 and 2.4 * Add description to no-rubygems patch * Add lintian override for unit tests having hashbang, and not being executable * Refactor puppetmaster-passenger postinst and postrm scripts -- Stig Sandbeck Mathisen Thu, 24 May 2012 21:58:39 +0200 puppet (3.0.0~rc1-1) experimental; urgency=low * Imported Upstream version 3.0.0~rc1 * Depend on facter 2 or newer * Remove installation of standalone commands and their manpages, they are no longer provided upstream (filebucket, pi, puppetdoc, ralsh, puppetca, puppetd, puppetmasterd, puppetqd, and puppetrun) * Remove backported patch for "runit" * Disable patch for test library path * Use a packaging dependency to check rspec version -- Stig Sandbeck Mathisen Fri, 18 May 2012 18:57:34 +0200 ** Affects: puppet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1143009 Title: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+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
[Blueprint servercloud-r-midonet-deps] Provide support for Midonet with Quantum
Blueprint changed by James Page: Work items changed: Work items: - [james-page] discovery around quantum integration and horizontal scale-out/ha: TODO - [james-page] packaging of midonet-openstack plugin: BLOCKED - [rossella-o] release line-up of midonet/plugin with openstack and Ubuntu: TODO - [james-page] charm support for midonet: BLOCKED - [james-page] review for inclusion in partner: TODO + [james-page] discovery around quantum integration and horizontal scale-out/ha: DONE + [james-page] packaging of midonet-openstack plugin: DONE + [rossella-o] release line-up of midonet/plugin with openstack and Ubuntu: DONE + [james-page] charm support for midonet: TODO + [james-page] review for inclusion in partner: POSTPONED -- Provide support for Midonet with Quantum https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-midonet-deps -- 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 1143009] Re: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main)
** Changed in: puppet (Ubuntu) Status: New => Invalid ** Changed in: puppet (Ubuntu) Status: Invalid => In Progress ** Changed in: puppet (Ubuntu) Assignee: (unassigned) => Benjamin Kerensa (bkerensa) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1143009 Title: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+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 1095181] Re: terrible breakage on git rebase
[Expired for etckeeper (Ubuntu) because there has been no activity for 60 days.] ** Changed in: etckeeper (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1095181 Title: terrible breakage on git rebase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1095181/+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 1143009] Re: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main)
As discussed on ubuntu-devel-discuss, this should really be a released version rather than an RC. It would be great if that happened through Debian. ** Changed in: puppet (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1143009 Title: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+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 1057125] Re: stable/essex horizon installs unusable version of glance
xception, but this bug is linked from the SRU changelog and would require direct verification. Please either complete the bug description with a test case for this bug, or re-upload without a reference in the changelog. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1057125 Title: stable/essex horizon installs unusable version of glance To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1057125/+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 1031291] Re: TypeError when trying to delete an unnamed volume via dashboard
xception, but this bug is linked from the SRU changelog and would require direct verification. Please either complete the bug description with a test case for this bug, or re-upload without a reference in the changelog. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1031291 Title: TypeError when trying to delete an unnamed volume via dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1031291/+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 1020555] Re: Wrong 'Download CSV Summary' link
The horizon SRU is a provisional micro-release exception, but this bug is linked from the SRU changelog and would require direct verification. Please either complete the bug description with a test case for this bug, or re-upload without a reference in the changelog. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1020555 Title: Wrong 'Download CSV Summary' link To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1020555/+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 1143009] Re: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main)
3.1.0 is out and stable. Could that be used? On Mar 3, 2013 10:10 PM, "Micah Gersten" wrote: > As discussed on ubuntu-devel-discuss, this should really be a released > version rather than an RC. It would be great if that happened through > Debian. > > ** Changed in: puppet (Ubuntu) >Status: In Progress => Incomplete > > -- > You received this bug notification because you are subscribed to puppet > in Ubuntu. > Matching subscriptions: puppet ubuntu > https://bugs.launchpad.net/bugs/1143009 > > Title: > Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main) > > Status in “puppet” package in Ubuntu: > Incomplete > > Bug description: > Please sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main) > > Explanation of the Ubuntu delta and why it can be dropped: > * Resynchronise with Debian. (LP: #1023931) Remaining changes: > - debian/puppetmaster-passenger.postinst: Make sure we error if > puppet > config print doesn't work > - debian/puppetmaster-passenger.postinst: Ensure upgrades from > <= 2.7.11-1 fixup passenger apache configuration. > * Dropped upstreamed patches: > - debian/patches/CVE-2012-1906_CVE-2012-1986_to_CVE-2012-1989.patch > - debian/patches/puppet-12844 > - debian/patches/2.7.17-Puppet-July-2012-CVE-fixes.patch > * Drop Build-Depends on ruby-rspec (in universe): > - debian/control: remove ruby-rspec from Build-Depends > - debian/patches/no-rspec.patch: make Rakefile work anyway if rspec > isn't installed so we can use it in debian/rules. > > > Changelog entries since current raring version 2.7.18-1ubuntu1: > > puppet (3.0.0~rc2-1) experimental; urgency=low > > * Imported Upstream version 3.0.0~rc2 > * Rename configuration file /etc/apache2/sites-available/puppetmaster > to > puppetmaster.conf to match apache2 policy change (Closes: #673970) > * Check if a2dissite is present for postrm (Closes: #674011) > * Workaround apache2 a2* utils API change to stay compatible to both > apache 2.2 and 2.4 > * Add description to no-rubygems patch > * Add lintian override for unit tests having hashbang, and not being > executable > * Refactor puppetmaster-passenger postinst and postrm scripts > >-- Stig Sandbeck Mathisen Thu, 24 May 2012 21:58:39 > +0200 > > puppet (3.0.0~rc1-1) experimental; urgency=low > > * Imported Upstream version 3.0.0~rc1 > * Depend on facter 2 or newer > * Remove installation of standalone commands and their manpages, they > are no longer provided upstream (filebucket, pi, puppetdoc, ralsh, > puppetca, puppetd, puppetmasterd, puppetqd, and puppetrun) > * Remove backported patch for "runit" > * Disable patch for test library path > * Use a packaging dependency to check rspec version > >-- Stig Sandbeck Mathisen Fri, 18 May 2012 18:57:34 > +0200 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+subscriptions > ** CVE added: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2012-1906 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2012-1986 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2012-1989 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1143009 Title: Sync puppet 3.0.0~rc2-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+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
