[Bug 1004243] Re: multipath installs not working
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1004243 Title: multipath installs not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1004243/+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 1386052] [NEW] pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Public bug reported: Hi, Seems pollen fails to log everytime rsyslog packages are upgraded or rsyslog daemon itself is bounced. There's an alert for it, but I don't think it should be set up in such a way that we need to manually bounce the pollen daemon every time rsyslog packages are upgraded. Could you please look into fixing this so pollen itself does something to reconnect to syslog? Thanks, Haw ** Affects: pollen (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, Seems pollen fails to log everytime rsyslog packages are upgraded or rsyslog daemon itself is bounced. There's an alert for it, but I don't think it should be set up in such a way that we need to manually bounce the pollen daemon every time rsyslog packages are upgraded. + Could you please look into fixing this so pollen itself does something + to reconnect to syslog? + Thanks, Haw -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+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 1354114] Re: multipath segmentation Fault (libmultipath: update waiter handling)
This bug was fixed in the package multipath-tools - https://launchpad.net/ubuntu/+source/multipath-tools/0.4.9-3ubuntu7.2 --- multipath-tools (0.4.9-3ubuntu7.2) trusty; urgency=medium * 1002-fix-linking-library.patch: Move $(LIBDEPS) to the end of the link line to fix underlinking with ld --as-needed (LP: #1004243) -- Adam Conrad adcon...@ubuntu.com Mon, 13 Oct 2014 07:47:07 -0600 ** Changed in: multipath-tools (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1354114 Title: multipath segmentation Fault (libmultipath: update waiter handling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+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 1317587] Re: ClamAV 0.98.1 is Outdated
Since clamav is available in trusty-backports, does that mean the Trusty task can be marked Fix Released? Will clamav 0.98.4 move to trusty-updates? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1317587 Title: ClamAV 0.98.1 is Outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1317587/+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 1386052] Re: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pollen (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+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 1385407] Re: juju-quickstart destroys existing AWS environment
** Package changed: juju-quickstart (Ubuntu) = juju-quickstart -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-quickstart in Ubuntu. https://bugs.launchpad.net/bugs/1385407 Title: juju-quickstart destroys existing AWS environment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-quickstart/+bug/1385407/+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 1381768] Re: AttributeError: 'module' object has no attribute 'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4
Reviewed: https://review.openstack.org/129770 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=db291b340e63b74d8d240abfc37d03fb163f33f1 Submitter: Jenkins Branch:stable/juno commit db291b340e63b74d8d240abfc37d03fb163f33f1 Author: Nathan Kinder nkin...@redhat.com Date: Wed Oct 15 15:39:55 2014 -0700 Use newer python-ldap paging control API The API for using the LDAP simple paged results control changed between python-ldap version 2.3 and 2.4. Our current implementation fails with an AttributeError when trying to use paging with version 2.4 of python-ldap. This patch detects the capabilities of the underlying python-ldap version and uses the newer API in versions of python-ldap that have removed the older API. Change-Id: I2986e12daea3edf50f299af5927d2a05278e82f7 Closes-bug: #1381768 (cherry picked from commit 1be4a15454e6917571bc937e3bb3589e8f79bc55) ** Changed in: keystone/juno Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1381768 Title: AttributeError: 'module' object has no attribute 'LDAP_CONTROL_PAGE_OID' with python-ldap 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1381768/+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 1357880] Re: /etc/logcheck/ignore.d.server/dhclient needs updated regex
I am running 14.04.1 ubuntu. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logcheck in Ubuntu. https://bugs.launchpad.net/bugs/1357880 Title: /etc/logcheck/ignore.d.server/dhclient needs updated regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/1357880/+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 1357880] Re: /etc/logcheck/ignore.d.server/dhclient needs updated regex
I am also getting these notifications: Oct 27 05:02:47 test dhclient: DHCPREQUEST of 192.168.0.4 on eth1 to 192.168.0.3 port 67 (xid=0x7f1ffa2b) Oct 27 05:02:47 test dhclient: DHCPNAK from 192.168.0.3 (xid=0x7f1ffa2b) Oct 27 05:02:47 test dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0x3ff27ab2) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logcheck in Ubuntu. https://bugs.launchpad.net/bugs/1357880 Title: /etc/logcheck/ignore.d.server/dhclient needs updated regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/1357880/+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 1382632] Re: Insecure key file permissions
How do we get this on trusty? Or the MAAS PPA perhaps? -- 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/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1382632/+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 1386144] [NEW] juju-core 1.20.11 is not packaged in Ubuntu
Public bug reported: juju-core 1.20.11 is proposed for release upstream. We're now in a position to have this enter trusty-proposed and vivid- proposed, but it should not land in trusty-updates or vivid until upstream passes QA on our proposed binaries, published 1.20.11 tools in their stable simplestream and announces the release for general production use. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. [Development Fix] Full backport of new upstream release. racb will remove the block- proposed tag when verification has passed, and then this update should migrate to vivid. [Stable Fix] Full backport of new upstream release. [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upsteam QA test against Vivid: TODO [sinzui] Upstream QA test against Trusty: TODO [sinzui] Upstream release process complete: TODO Manual tests required: [racb] Test juju-quickstart against vivid-proposed: TODO [racb] Test juju-quickstart against trusty-proposed: TODO The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug. Landscape team QA: TODO ** Affects: juju-core (Ubuntu) Importance: Medium Assignee: Ubuntu Server Team (ubuntu-server) Status: Triaged ** Affects: juju-core (Ubuntu Trusty) Importance: Medium Assignee: Ubuntu Server Team (ubuntu-server) Status: Triaged ** Tags: block-proposed update-software-version ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Status: New = Triaged ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: juju-core (Ubuntu Trusty) Assignee: (unassigned) = Ubuntu Server Team (ubuntu-server) -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/1386144 Title: juju-core 1.20.11 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1386144/+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 1357441] Re: package libapache2-mod-perl2 2.0.8+httpd24-r1449661-6ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libapache2-mod-perl2 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-perl2 in Ubuntu. https://bugs.launchpad.net/bugs/1357441 Title: package libapache2-mod-perl2 2.0.8+httpd24-r1449661-6ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-perl2/+bug/1357441/+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 1386194] [NEW] openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators
Public bug reported: openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators. I have ldap.conf cat /etc/ldap.conf ###DEBCONF### ## ## Configuration of this file will be managed by debconf as long as the ## first line of the file says '###DEBCONF###' ## ## You should use dpkg-reconfigure to configure this file via debconf ## # # @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $ # # This is the configuration file for the LDAP nameservice # switch library and the LDAP PAM module. # # PADL Software # http://www.padl.com # # Your LDAP server. Must be resolvable without using LDAP. # Multiple \hosts may be specified, each separated by a # space. How long nss_ldap takes to failover depends on # whether your LDAP client library supports configurable # network or connect timeouts (see bind_timelimit). #host 127.0.0.1 #host ldap.stuba.sk ldap2.stuba.sk host ldap.stuba.sk # The distinguished name of the search base. base ou=People,dc=stuba,dc=sk pam_template_login_attribute uid # Another way to specify your LDAP server is to provide an #uri ldapi://ldap.stuba.sk ldapi://ldap2.stuba.sk #uri ldaps://ldap.stuba.sk ldaps://ldap2.stuba.sk #TLS_REQCERT allow # Unix Domain Sockets to connect to a local LDAP Server. #uri ldap://127.0.0.1/ #uri ldaps://127.0.0.1/ #uri ldapi://%2fvar%2frun%2fldapi_sock/ # Note: %2f encodes the '/' used as directory separator # The LDAP version to use (defaults to 3 # if supported by client library) ldap_version 3 REFERRALS off TIMEOUT 60 NETWORK_TIMEOUT 60 TIMELIMIT 60 refferrals off timeout 60 network_timeout 60 timelimit 60 persistent-search off # The distinguished name to bind to the server with. # Optional: default is to bind anonymously. #binddn uid=fodrek,ou=People,dc=stuba,dc=sk # The credentials to bind with. # Optional: default is no credential. #bindpw secret # The distinguished name to bind to the server with # if the effective user ID is root. Password is # stored in /etc/ldap.secret (mode 600) #rootbinddn cn=manager,dc=padl,dc=com # The port. # Optional: default is 389. #port 389 # The search scope. #scope sub #scope one scope base # Search timelimit timelimit 1 # Bind/connect timelimit bind_timelimit 12 # Reconnect policy: hard (default) will retry connecting to # the software with exponential backoff, soft will fail # immediately. #bind_policy hard bind_policy soft # Idle timelimit; client will close connections # (nss_ldap only) if the server has not been contacted # for the number of seconds specified below. #idle_timelimit 3600 idle_timelimit 60 debug 99 # Filter to AND with uid=%s #pam_filter objectclass=account #pam_filter objectclass=posixAccount # The user ID attribute (defaults to uid) pam_login_attribute uid # Search the root DSE for the password policy (works # with Netscape Directory Server) #pam_lookup_policy yes # Check the 'host' attribute for access control # Default is no; if set to yes, and user has no # value for the host attribute, and pam_ldap is # configured for account management (authorization) # then the user will not be allowed to login. pam_check_host_attr no # Check the 'authorizedService' attribute for access # control # Default is no; if set to yes, and the user has no # value for the authorizedService attribute, and # pam_ldap is configured for account management # (authorization) then the user will not be allowed # to login. #pam_check_service_attr yes # Group to enforce membership of #pam_groupdn ou=People,dc=stuba,dc=sk # Group member attribute #pam_member_attribute uniquemember #pam_member_attribute uid # Specify a minium or maximum UID number allowed #pam_min_uid 0 #pam_max_uid 0 # Template login attribute, default template user # (can be overriden by value of former attribute # in user's entry) #pam_login_attribute userPrincipalName #pam_template_login_attribute uid #pam_template_login nobody # HEADS UP: the pam_crypt, pam_nds_passwd, # and pam_ad_passwd options are no # longer supported. # # Do not hash the password at all; presume # the directory server will do it, if # necessary. This is the default. pam_password md5 # Hash password locally; required for University of # Michigan LDAP server, and works with Netscape # Directory Server if you're using the UNIX-Crypt # hash mechanism and not using the NT Synchronization # service. #pam_password crypt # Remove old password first, then update in # cleartext. Necessary for use with Novell # Directory Services (NDS) #pam_password clear_remove_old #pam_password nds # RACF is an alias for the above. For use with # IBM RACF #pam_password racf # Update Active Directory password, by # creating Unicode password and updating # unicodePwd attribute. #pam_password ad # Use the OpenLDAP password change # extended operation to update the password. #pam_password exop # Redirect users to a URL or somesuch on password # changes. #pam_password_prohibit_message Please visit http://internal to change
[Bug 1382632] Re: Insecure key file permissions
** Changed in: curtin (Ubuntu) Status: New = Confirmed ** Also affects: horizon (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Vivid) Importance: Undecided Status: Confirmed ** Also affects: curtin (Ubuntu Vivid) Importance: Undecided Status: Confirmed ** Also affects: horizon (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Utopic) Importance: Undecided Status: New ** No longer affects: horizon (Ubuntu Trusty) ** No longer affects: horizon (Ubuntu Utopic) -- 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/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1382632/+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 1382266] Re: maas-proxy fails to start on freshly installed MAAS
** Changed in: maas (Ubuntu) Status: Confirmed = Incomplete ** Changed in: maas Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1382266 Title: maas-proxy fails to start on freshly installed MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382266/+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 1386194] Re: openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators
Hi, Thank you for reporting this and helping to make Ubuntu better. Peter Fodrek wrote: cat /etc/ldap.conf This is the configuration file for libnss-ldap, which is not part of OpenLDAP. If you need assistance with configuring libnss-ldap or libpam- ldap, I suggest contacting the support channels for that software, or asking on answers.ubuntu.com. You might also wish to try libnss-ldapd /libpam-ldapd and see whether they have the same problem. If you are experiencing a bug in OpenLDAP, please try to provide more evidence of such; or if you are experiencing a bug (and are certain it's a bug, not a misconfiguration) in libnss-ldap, please reassign this to the appropriate package. Thanks! ** Changed in: openldap (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1386194 Title: openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1386194/+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 1385851] Re: OpenVPN only supports TLS v1.0
The version that supports negociating TLS 1.1+ (2.3.4) landed in Debian Sid few days ago so it should be picked up by Ubuntu Vivid eventually. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1385851 Title: OpenVPN only supports TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+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 1382632] Re: Insecure key file permissions
** Description changed:
openstack-dashboard 1:2014.2-0ubuntu1~cloud0 from
http://ppa.launchpad.net/ubuntu-cloud-archive/juno-staging/ubuntu/
Got this during installation with the charm:
(...)
2014-10-17 17:17:07 INFO install Setting up openstack-dashboard
(1:2014.2-0ubuntu1~cloud0) ...
2014-10-17 17:17:07 INFO install Collecting and compressing static assets...
2014-10-17 17:17:07 INFO install Traceback (most recent call last):
2014-10-17 17:17:07 INFO install File manage.py, line 25, in module
2014-10-17 17:17:07 INFO install execute_from_command_line(sys.argv)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
399, in execute_from_command_line
2014-10-17 17:17:07 INFO install utility.execute()
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
392, in execute
2014-10-17 17:17:07 INFO install
self.fetch_command(subcommand).run_from_argv(self.argv)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
261, in fetch_command
2014-10-17 17:17:07 INFO install commands = get_commands()
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
107, in get_commands
2014-10-17 17:17:07 INFO install apps = settings.INSTALLED_APPS
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 54, in
__getattr__
2014-10-17 17:17:07 INFO install self._setup(name)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 49, in _setup
2014-10-17 17:17:07 INFO install self._wrapped = Settings(settings_module)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 128, in
__init__
2014-10-17 17:17:07 INFO install mod =
importlib.import_module(self.SETTINGS_MODULE)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40, in
import_module
2014-10-17 17:17:07 INFO install __import__(name)
2014-10-17 17:17:07 INFO install File
/usr/share/openstack-dashboard/openstack_dashboard/settings.py, line 316, in
module
2014-10-17 17:17:07 INFO install from local.local_settings import * #
noqa
2014-10-17 17:17:07 INFO install File
/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py,
line 98, in module
2014-10-17 17:17:07 INFO install SECRET_KEY =
secret_key.generate_or_read_from_file('/var/lib/openstack-dashboard/secret_key')
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/horizon/utils/secret_key.py, line 61, in
generate_or_read_from_file
2014-10-17 17:17:07 INFO install raise FilePermissionError(Insecure key
file permissions!)
2014-10-17 17:17:07 INFO install
horizon.utils.secret_key.FilePermissionError: Insecure key file permissions!
2014-10-17 17:17:07 INFO install dpkg: error processing package
openstack-dashboard (--configure):
2014-10-17 17:17:07 INFO install subprocess installed post-installation
script returned error exit status 1
2014-10-17 17:17:07 INFO install dpkg: dependency problems prevent
configuration of openstack-dashboard-ubuntu-theme:
2014-10-17 17:17:07 INFO install openstack-dashboard-ubuntu-theme depends on
openstack-dashboard (= 1:2014.2-0ubuntu1~cloud0); however:
2014-10-17 17:17:07 INFO install Package openstack-dashboard is not
configured yet.
- 2014-10-17 17:17:07 INFO install
+ 2014-10-17 17:17:07 INFO install
2014-10-17 17:17:07 INFO install dpkg: error processing package
openstack-dashboard-ubuntu-theme (--configure):
2014-10-17 17:17:07 INFO install dependency problems - leaving unconfigured
2014-10-17 17:17:07 INFO install No apport report written because the error
message indicates its a followup error from a previous failure.
2014-10-17 17:17:07 INFO install Errors were encountered while processing:
2014-10-17 17:17:07 INFO install openstack-dashboard
2014-10-17 17:17:07 INFO install openstack-dashboard-ubuntu-theme
2014-10-17 17:17:08 INFO install E: Sub-process /usr/bin/dpkg returned an
error code (1)
Full logs attached.
+
+ Related Bugs:
+ * bug 1382632: horizon insecure key file permissions
+ * bug 1386237: tar strange behavior with --acl
+ * bug 1313550: ping broken (xattrs lost in tar extraction)
--
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/1382632
Title:
Insecure key file permissions
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1382632/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
[Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Description changed: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags - SRU curtin - == - - [Impact] - - As the original bug report description mentions, curtin's extraction - needs to use xattr/acl flags. - - [Test Case] - - To reproduce this bug, use curtin extraction without the extended file - attributes. - - [Regression Potential] - - Since the patch for this bug fix *looks* to see if there are extended - file attributes, it should work in the event that they are there or are - not there or are. More specifically, if tar cmd supports xattrs, curtin - will return the required flags to extract them. This lowers the - probability of introducing a regression. + Related Bugs: + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl + * bug 1313550: ping broken (xattrs lost in tar extraction) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Description changed: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: - * bug 1382632: horizon insecure key file permissions - * bug 1386237: tar strange behavior with --acl - * bug 1313550: ping broken (xattrs lost in tar extraction) + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl and xattr + * bug 1313550: ping broken (xattrs lost in tar extraction) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1382632] Re: Insecure key file permissions
** Changed in: curtin (Ubuntu Utopic) Status: New = Confirmed ** Changed in: curtin (Ubuntu Trusty) Status: New = Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided = High ** Changed in: curtin (Ubuntu Utopic) Importance: Undecided = High ** Changed in: curtin (Ubuntu Vivid) Importance: Undecided = High -- 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/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1382632/+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 1377325] Re: The ppc64/arm versions of Juju should depend on a more recent version of libgo5
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Status: New = Triaged ** Changed in: juju-core (Ubuntu Trusty) Status: New = Triaged ** Changed in: juju-core (Ubuntu) Importance: Undecided = High ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided = High ** Changed in: juju-core (Ubuntu) Assignee: (unassigned) = Robie Basak (racb) ** Changed in: juju-core (Ubuntu Trusty) Assignee: (unassigned) = Robie Basak (racb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1377325 Title: The ppc64/arm versions of Juju should depend on a more recent version of libgo5 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1377325/+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 1333630] Re: screen caught signal 11 core dumped
Any chance the fix will be back ported? broken screen in LTS is kinda bad... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+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 1386275] [NEW] failure with utopic level lsblk. should use --output, not --out.
Public bug reported: $ dpkg-query --show curtin python-curtin util-linux curtin 0.1.0~bzr190-0ubuntu1 python-curtin 0.1.0~bzr190-0ubuntu1 util-linux 2.25.1-3ubuntu4 $ sudo curtin --showtrace install http://cloud- images.ubuntu.com/utopic/current/utopic-server-cloudimg- amd64-root.tar.gz Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/curtin/commands/main.py, line 96, in main sys.exit(args.func(args)) File /usr/lib/python2.7/dist-packages/curtin/commands/block_meta.py, line 53, in block_meta meta_simple(args) File /usr/lib/python2.7/dist-packages/curtin/commands/block_meta.py, line 150, in meta_simple devices = block.get_installable_blockdevs() File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 118, in get_installable_blockdevs unused = get_unused_blockdev_info() File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 81, in get_unused_blockdev_info bdinfo = _lsblock(['--nodeps']) File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 70, in _lsblock (out, _err) = util.subp(basecmd + list(args), capture=True) File /usr/lib/python2.7/dist-packages/curtin/util.py, line 67, in subp cmd=args) ProcessExecutionError: Unexpected error while running command. Command: ['lsblk', '--noheadings', '--bytes', '--pairs', '--out=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-SIZE,SIZE,STATE,TYPE,UUID', '--nodeps'] Exit code: 1 ... is ambiguous; possibilities: \'--output\' \'--output-all\'\n\nUsage:\n lsblk [options] [device ...]\n\nOptions:\n -a, --all basically, util-linux's lsblk gained a '--output-all' argument, which made our use of '--out' ambiguous. Note, back to 12.04 supports --output per http://manpages.ubuntu.com/manpages/precise/en/man8/lsblk.8.html . not sure why I used '--out'. ** Affects: curtin Importance: High Status: Confirmed ** Affects: curtin (Ubuntu) Importance: High Status: Confirmed ** Also affects: curtin Importance: Undecided Status: New ** Changed in: curtin (Ubuntu) Status: New = Confirmed ** Changed in: curtin (Ubuntu) Importance: Undecided = High ** Changed in: curtin Status: New = Confirmed ** Changed in: curtin Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1386275 Title: failure with utopic level lsblk. should use --output, not --out. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1386275/+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 1386275] Re: failure with utopic level lsblk. should use --output, not --out.
** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Vivid) Importance: High Status: Confirmed ** Changed in: curtin (Ubuntu Trusty) Status: New = Confirmed ** Changed in: curtin (Ubuntu Utopic) Status: New = Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided = High ** Changed in: curtin (Ubuntu Utopic) Importance: Undecided = High ** Changed in: curtin (Ubuntu Trusty) Importance: High = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1386275 Title: failure with utopic level lsblk. should use --output, not --out. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1386275/+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 1333630] Re: screen caught signal 11 core dumped
4.2.1 is part of 14.10 Utopic and also available in trusty-backports. ** Changed in: screen (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+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 1378910] Re: Call the install log 'install log' rather than 'curtin log'
** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu) Status: New = Confirmed ** Changed in: curtin (Ubuntu) Importance: Undecided = Medium ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Vivid) Importance: Medium Status: Confirmed ** Also affects: curtin (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Trusty) Status: New = Confirmed ** Changed in: curtin (Ubuntu Utopic) Status: New = Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: curtin (Ubuntu Utopic) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1378910 Title: Call the install log 'install log' rather than 'curtin log' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1378910/+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 1386275] Re: failure with utopic level lsblk. should use --output, not --out.
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/sru-utopic-level -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1386275 Title: failure with utopic level lsblk. should use --output, not --out. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1386275/+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 1378910] Re: Call the install log 'install log' rather than 'curtin log'
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/sru-utopic-level -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1378910 Title: Call the install log 'install log' rather than 'curtin log' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1378910/+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 1382632] Re: Insecure key file permissions
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/sru-utopic-level -- 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/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1382632/+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 1216817] Re: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
** Also affects: nginx (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: nginx (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+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 1216817] Re: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Marking as Fix Released for other releases - this was fixed in Debian as 1.4.7-1, and Utopic and later have 1.6.x. As such, this is fixed in Utopic and later. ** Changed in: nginx (Ubuntu) Status: Triaged = Fix Released ** Changed in: nginx (Ubuntu Precise) Importance: Undecided = Low ** Changed in: nginx (Ubuntu Precise) Status: New = In Progress ** Changed in: nginx (Ubuntu Precise) Assignee: (unassigned) = Thomas Ward (teward) ** Changed in: nginx (Ubuntu Trusty) Importance: Undecided = Low ** Changed in: nginx (Ubuntu Trusty) Status: New = In Progress ** Changed in: nginx (Ubuntu Trusty) Assignee: (unassigned) = Thomas Ward (teward) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Fix works for me too, but it obviously isn't the proper solution. -- 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/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1386275] Re: failure with utopic level lsblk. should use --output, not --out.
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1 --- curtin (0.1.0~bzr195-0ubuntu1) vivid; urgency=medium * New upstream snapshot. * move install log from /var/log/curtin_install.log to /var/log/curtin/install.log (LP: #1378910) * to not use '--acl' when extracting tar files (LP: #1382632) as it inadvertently writes default directory acls. * invoke lsblk with '--output' rather than '--out' to avoid ambiguity in newer versions of lsblk (LP: #1386275) -- Scott Moser smo...@ubuntu.com Mon, 27 Oct 2014 12:25:27 -0400 ** Branch linked: lp:~smoser/ubuntu/utopic/curtin/sru-vivid-level ** Changed in: curtin (Ubuntu Vivid) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1386275 Title: failure with utopic level lsblk. should use --output, not --out. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1386275/+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 1382632] Re: Insecure key file permissions
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1 --- curtin (0.1.0~bzr195-0ubuntu1) vivid; urgency=medium * New upstream snapshot. * move install log from /var/log/curtin_install.log to /var/log/curtin/install.log (LP: #1378910) * to not use '--acl' when extracting tar files (LP: #1382632) as it inadvertently writes default directory acls. * invoke lsblk with '--output' rather than '--out' to avoid ambiguity in newer versions of lsblk (LP: #1386275) -- Scott Moser smo...@ubuntu.com Mon, 27 Oct 2014 12:25:27 -0400 ** Branch linked: lp:~smoser/ubuntu/utopic/curtin/sru-vivid-level ** Changed in: curtin (Ubuntu Vivid) Status: Confirmed = Fix Released -- 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/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1382632/+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 1378910] Re: Call the install log 'install log' rather than 'curtin log'
This bug was fixed in the package curtin - 0.1.0~bzr195-0ubuntu1 --- curtin (0.1.0~bzr195-0ubuntu1) vivid; urgency=medium * New upstream snapshot. * move install log from /var/log/curtin_install.log to /var/log/curtin/install.log (LP: #1378910) * to not use '--acl' when extracting tar files (LP: #1382632) as it inadvertently writes default directory acls. * invoke lsblk with '--output' rather than '--out' to avoid ambiguity in newer versions of lsblk (LP: #1386275) -- Scott Moser smo...@ubuntu.com Mon, 27 Oct 2014 12:25:27 -0400 ** Branch linked: lp:~smoser/ubuntu/utopic/curtin/sru-vivid-level ** Changed in: curtin (Ubuntu Vivid) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1378910 Title: Call the install log 'install log' rather than 'curtin log' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1378910/+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 1216817] Re: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Trusty debdiff for fixing this bug ** Patch added: Trusty Debdiff to fix #1216817 https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1216817/+attachment/4246391/+files/lp1216817-trusty.debdiff ** Changed in: nginx (Ubuntu Precise) Status: In Progress = Triaged ** Changed in: nginx (Ubuntu Precise) Assignee: Thomas Ward (teward) = (unassigned) ** Changed in: nginx (Ubuntu Trusty) Status: In Progress = Triaged ** Changed in: nginx (Ubuntu Trusty) Assignee: Thomas Ward (teward) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+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 1216817] Re: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Upstream diff from the nginx-http-push module developers is located here: https://github.com/slact/nginx_http_push_module/commit/836e8319c93681386fb00e6bd34d9e37612f3334.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+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 1216817] Re: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Precise debdiff for fixing this bug, using the upstream changes. ** Patch added: Precise Debdiff to fix #1216817 https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1216817/+attachment/4246390/+files/lp1216817-precise.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+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 1216817] Re: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
To everyone affected: We need example configurations to use here, so we can test this getting fixed. To the SRU team: I am build-testing this now in a ppa, and will let you know if it builds correctly. ** Description changed: + [Impact] + + * The nginx-http-push module generates errors when using fastcgi_cache + or proxy_cache arguments in the config. + + * This adds extra errors to the error logs, and causes problems with + the cache manager. + + * Caching still works, however, but this causes excessive unnecessary + noise in the error logs and the issue is an incompatibility between the + module and the nginx cache manager. + + [Test Case] + + * Use the nginx-extras package, and use any configuration with either + `fastcgi_cache` or `proxy_cache` arguments. (NOTE: I will attempt to + develop a test configuration that you can use to test this) + + [Regression Potential] + + * This fix originated upstream, and should not introduce any + regressions. + + [Other Info] + + * The debdiffs here are derived from upstream changes, as detailed at https://github.com/slact/nginx_http_push_module/commit/836e8319c93681386fb00e6bd34d9e37612f3334.diff + + * The only changes to this diff were the indentation, to match what was + in the packages. + + + [Original Description] + system : Ubuntu 12.04 LTS package : nginx-extras 1.4.1-1ppa1~precise Hello, if you try to use proxy_cache or fastcgi_cache you got this error in error.log of nginx : 2013/08/26 00:13:10 [info] 15722#0: Using 32KiB of shared memory for push module in /etc/nginx/nginx.conf:137 2013/08/26 00:13:11 [alert] 15756#0: epoll_ctl(1, 0) failed (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15756#0: failed to register channel handler while initializing push module worker (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15757#0: epoll_ctl(1, 0) failed (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15757#0: failed to register channel handler while initializing push module worker (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15737#0: cache manager process 15756 exited with fatal code 2 and cannot be respawned - You can't disable nginx_push_module, to make nginx cache to work. Everything is fine if you use the daemon off; option. I've seen this issue in many forum/mailing list, i think nginx_push_module shouldn't be in the extras package anymore. system : Ubuntu 12.04 LTS package : nginx-extras 1.4.1-1ppa1~precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+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 1382632] Re: Insecure key file permissions
** Description changed:
+ === SRU Information ===
+ [Impact]
+ Systems installed using curtin inadvertantly have a default set of acl applied
+ to the root directory. Those default acl can wreak havoc with seemingly
+ sane expectations of users or packages or administrators.
+
+ For example, the problem that was noticed essentially boiled down to a
+ program doing:
+ ( umask 0066 ; rm -f secret-file; echo passw0rd secret-file )
+ and then later that program checked permissions of the file
+ and found:
+ $ ls -l secret-file
+ -rw-r--r-- 1 smoser smoser 0 Oct 27 12:00 secret-file
+ instead of
+ -rw--- 1 smoser smoser 0 Oct 27 12:00 secret-file
+ And raised exception.
+
+ This is not at all an unreasonable expectation.
+ Essentially, this boils down to all packages not being ready to handle
+ having filesystem ACL in place. Additionally curtin did not intend on
+ installing the target with default ACLs that was a unexpected behavior of
+ tar (raised in bug 1386237)
+
+ [Test Case]
+ * Install system with MAAS and fast path installer (curtin).
+ * mkdir /tmp/mydir
+ * cd /tmp/mydir
+ * ( umask 0066 ; rm -f secret-file; echo passw0rd secret-file )
+ * ls -l secret-file
+
+ Expected output is that file has 600 permissions. Failure case, is 644.
+
+ [Regression Potential]
+ Fairly small chance for regression as the tar files created for consumption
+ are not created with acl information inside. Generally ubuntu installations
+ do not have default ACL in place on /, and thus the change creates less
+ chance for unexpected behavior than is currently present.
+
+ [Other Info]
+ This bug is not actually present in the version of curtin in trusty.
+ However, the fix for this issue is in the code added to fix bug 1313550.
+ The bug is present in utopic's version of curtin.
+
+ === End SRU Information ===
+
openstack-dashboard 1:2014.2-0ubuntu1~cloud0 from
http://ppa.launchpad.net/ubuntu-cloud-archive/juno-staging/ubuntu/
Got this during installation with the charm:
(...)
2014-10-17 17:17:07 INFO install Setting up openstack-dashboard
(1:2014.2-0ubuntu1~cloud0) ...
2014-10-17 17:17:07 INFO install Collecting and compressing static assets...
2014-10-17 17:17:07 INFO install Traceback (most recent call last):
2014-10-17 17:17:07 INFO install File manage.py, line 25, in module
2014-10-17 17:17:07 INFO install execute_from_command_line(sys.argv)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
399, in execute_from_command_line
2014-10-17 17:17:07 INFO install utility.execute()
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
392, in execute
2014-10-17 17:17:07 INFO install
self.fetch_command(subcommand).run_from_argv(self.argv)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
261, in fetch_command
2014-10-17 17:17:07 INFO install commands = get_commands()
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
107, in get_commands
2014-10-17 17:17:07 INFO install apps = settings.INSTALLED_APPS
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 54, in
__getattr__
2014-10-17 17:17:07 INFO install self._setup(name)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 49, in _setup
2014-10-17 17:17:07 INFO install self._wrapped = Settings(settings_module)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 128, in
__init__
2014-10-17 17:17:07 INFO install mod =
importlib.import_module(self.SETTINGS_MODULE)
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40, in
import_module
2014-10-17 17:17:07 INFO install __import__(name)
2014-10-17 17:17:07 INFO install File
/usr/share/openstack-dashboard/openstack_dashboard/settings.py, line 316, in
module
2014-10-17 17:17:07 INFO install from local.local_settings import * #
noqa
2014-10-17 17:17:07 INFO install File
/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py,
line 98, in module
2014-10-17 17:17:07 INFO install SECRET_KEY =
secret_key.generate_or_read_from_file('/var/lib/openstack-dashboard/secret_key')
2014-10-17 17:17:07 INFO install File
/usr/lib/python2.7/dist-packages/horizon/utils/secret_key.py, line 61, in
generate_or_read_from_file
2014-10-17 17:17:07 INFO install raise FilePermissionError(Insecure key
file permissions!)
2014-10-17 17:17:07 INFO install
horizon.utils.secret_key.FilePermissionError: Insecure key file permissions!
2014-10-17 17:17:07 INFO install dpkg: error processing package
openstack-dashboard
[Bug 1386275] Re: failure with utopic level lsblk. should use --output, not --out.
** Description changed:
+ === Begin SRU Information ===
+ [Impact]
+ curtin install if util-linux is at utopic version or later.
+
+ The problem is that curtin's '_lsblock' which is used to get invoke lsblock to
+ get information about the block devices of the system used '--out=' to specify
+ the output format rather than '--output'. In utopic the version of util-linux
+ contains a lsblock with '--output-all' flag, which made '--output' ambiguous
+ and the command would fail.
+
+ The fix is then straight forward and is to just use '--output=' rather than
+ '--out='. I'm not sure where the usage of '--out' came from as versions
+ of util-linux back to 12.04 support '--output'.
+
+ [Test Case]
+ $ sudo apt-get update -qy apt-get install -qy python-curtin
+ $ dpkg-query --show python-curtin util-linux
+ python-curtin 0.1.0~bzr190-0ubuntu1
+ util-linux 2.25.1-3ubuntu4
+ $ python -c 'from curtin import block; import pprint;
pprint.pprint(block._lsblock())'
+
+ Result currently is stack trace on utopic.
+ Success is a pretty printed dictionary of 'lsblk' information like:
+ {
+ 'vdb1': {'ALIGNMENT': '0',
+ 'DISC-ALN': '0',
+ 'DISC-GRAN': '0',
+ ..
+ 'UUID': '',
+ 'device_path': '/dev/vdb1'}}
+ }
+
+ === End SRU Information ===
+
$ dpkg-query --show curtin python-curtin util-linux
curtin 0.1.0~bzr190-0ubuntu1
python-curtin 0.1.0~bzr190-0ubuntu1
util-linux 2.25.1-3ubuntu4
$ sudo curtin --showtrace install http://cloud-
images.ubuntu.com/utopic/current/utopic-server-cloudimg-
amd64-root.tar.gz
Traceback (most recent call last):
- File /usr/lib/python2.7/dist-packages/curtin/commands/main.py, line 96,
in main
- sys.exit(args.func(args))
- File /usr/lib/python2.7/dist-packages/curtin/commands/block_meta.py, line
53, in block_meta
- meta_simple(args)
- File /usr/lib/python2.7/dist-packages/curtin/commands/block_meta.py, line
150, in meta_simple
- devices = block.get_installable_blockdevs()
- File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 118,
in get_installable_blockdevs
- unused = get_unused_blockdev_info()
- File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 81,
in get_unused_blockdev_info
- bdinfo = _lsblock(['--nodeps'])
- File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 70,
in _lsblock
- (out, _err) = util.subp(basecmd + list(args), capture=True)
- File /usr/lib/python2.7/dist-packages/curtin/util.py, line 67, in subp
- cmd=args)
+ File /usr/lib/python2.7/dist-packages/curtin/commands/main.py, line 96,
in main
+ sys.exit(args.func(args))
+ File /usr/lib/python2.7/dist-packages/curtin/commands/block_meta.py, line
53, in block_meta
+ meta_simple(args)
+ File /usr/lib/python2.7/dist-packages/curtin/commands/block_meta.py, line
150, in meta_simple
+ devices = block.get_installable_blockdevs()
+ File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 118,
in get_installable_blockdevs
+ unused = get_unused_blockdev_info()
+ File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 81,
in get_unused_blockdev_info
+ bdinfo = _lsblock(['--nodeps'])
+ File /usr/lib/python2.7/dist-packages/curtin/block/__init__.py, line 70,
in _lsblock
+ (out, _err) = util.subp(basecmd + list(args), capture=True)
+ File /usr/lib/python2.7/dist-packages/curtin/util.py, line 67, in subp
+ cmd=args)
ProcessExecutionError: Unexpected error while running command.
Command: ['lsblk', '--noheadings', '--bytes', '--pairs',
'--out=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-SIZE,SIZE,STATE,TYPE,UUID',
'--nodeps']
Exit code: 1
...
is ambiguous; possibilities: \'--output\' \'--output-all\'\n\nUsage:\n lsblk
[options] [device ...]\n\nOptions:\n -a, --all
-
basically, util-linux's lsblk gained a '--output-all' argument, which made
our use of '--out' ambiguous. Note, back to 12.04 supports --output per
http://manpages.ubuntu.com/manpages/precise/en/man8/lsblk.8.html .
not sure why I used '--out'.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1386275
Title:
failure with utopic level lsblk. should use --output, not --out.
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1386275/+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 1378910] Re: Call the install log 'install log' rather than 'curtin log'
** Description changed: - sabdfl requested the curtin install log on a node's page not surface the - name 'curtin' - it should just be called 'install log'. + === Begin SRU Information === + [Impact] + The impact is for MAAS's UI, from a consistency perspective. In newer + versions of MAAS, certain files from the system during installation are + collected and made available in the UI. One of those was curtin's + log file 'curtin_install.log'. + + The impact is then that in debugging, the user would have to know if a + install used curtin or d-i in order to investigate the correct file name. + + This is arguably of trivial importance, but the change to the code and impact + are also trivial. + + [Test Case] + Install system with curtin in MAAS. + Check the install log on the node's page to see if the file is 'install.log' + or 'curtin_install_log'. + + [Other Information] + The version of curtin in 14.04 did not create any log by itself, so the + user of 14.04 version of curtin will not have any expectation on the file name. + The version of 14.10 in utopic would have created /var/log/install.log. + So, the exposed expectation is in users of 14.10 curtin who were using curtin + outside of MAAS (those using from maas aren't generally going looking for + log files on the ephemeral install system). + === End SRU Information === + + + sabdfl requested the curtin install log on a node's page not surface the name 'curtin' - it should just be called 'install log'. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1378910 Title: Call the install log 'install log' rather than 'curtin log' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1378910/+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 1311724] Re: Macbook Air resumes immidiately after suspend
This seems to work all the time when the computer is unplugged... when plugged in, it seems to work most of the time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1311724 Title: Macbook Air resumes immidiately after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1311724/+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 1378708] [NEW] VNC based installation does not interpret key strokes correctly.
You have been subscribed to a public bug: Problem Description = Ubuntu 14.10 VNC mode installation process does not interpret key strokes correctly. ---uname output--- Ubuntu daily build dated Oct 6th 2014 Machine Type = 8284-22A System Hang == During VNC mode installation, whenever the installer asks for input (for example password for a user) , it does not interpret key inputs properly. One example : When I type Sachin as a user name, the installer screen interprets it as Saachiin or Saccchhiiin. I have observed similar behavior post installation as well (while typing in VNC console) sachin@ubuntu:~$ cd /etcc/ -bash: cd: /etcc/: No such file or directory sachin@ubuntu:~$ lls No command 'lls' found, did you mean: . Steps to Reproduce === 1. define and start the below xml for VNC based installation. [root@lep8a ISO]# qemu-img create -f qcow2 /var/lib/libvirt/images/manu/ubuntu14_10_VNC.qcow2 60G Formatting '/var/lib/libvirt/images/manu/ubuntu14_10_VNC.qcow2', fmt=qcow2 size=64424509440 encryption=off cluster_size=65536 lazy_refcounts=off [root@lep8a new]# virsh dumpxml GMT_ubuntu14_10_VNC domain type='kvm' nameGMT_ubuntu14_10_VNC/name uuidbd45e5dd-9c10-4729-9b9b-da8fe136a45d/uuid memory unit='KiB'4194304/memory currentMemory unit='KiB'4194304/currentMemory vcpu placement='static'2/vcpu resource partition/machine/partition /resource os type arch='ppc64' machine='pseries'hvm/type boot dev='hd'/ boot dev='cdrom'/ /os features acpi/ apic/ pae/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/qemu-system-ppc64/emulator disk type='file' device='disk' driver name='qemu' type='qcow2' cache='none'/ source file='/var/lib/libvirt/images/manu/ubuntu14_10_VNC.qcow2'/ target dev='hda' bus='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /disk disk type='file' device='cdrom' driver name='qemu' type='raw'/ source file='/var/lib/libvirt/images/manu/ISO/utopic-server-ppc64el_oct6.iso'/ target dev='sdb' bus='scsi'/ readonly/ address type='drive' controller='0' bus='0' target='0' unit='1'/ /disk controller type='usb' index='0' address type='pci' domain='0x' bus='0x00' slot='0x02' function='0x0'/ /controller controller type='pci' index='0' model='pci-root'/ controller type='scsi' index='0' address type='spapr-vio' reg='0x2000'/ /controller interface type='bridge' mac address='52:54:c0:a8:7a:68'/ source bridge='brenP6p1s0f0'/ model type='e1000'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x0'/ /interface serial type='pty' target type='isa-serial' port='0'/ address type='spapr-vio' reg='0x3000'/ /serial console type='pty' target type='serial' port='0'/ address type='spapr-vio' reg='0x3000'/ /console input type='keyboard' bus='usb'/ input type='mouse' bus='usb'/ graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' keymap='en-us' listen type='address' address='0.0.0.0'/ /graphics video model type='vga' vram='9216' heads='1'/ address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /video memballoon model='virtio' address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /memballoon /devices seclabel type='dynamic' model='selinux' relabel='yes'/ /domain [root@lep8a new]# virsh start --console GMT_ubuntu14_10_VNC Domain GMT_ubuntu14_10_VNC started Connected to domain GMT_ubuntu14_10_VNC Escape character is ^] SLOF ** QEMU Starting ... 2. verify the VNCport and enable the iptables on pkvm host to use the same. [root@lep8a ISO]# virsh vncdisplay GMT_ubuntu14_10_VNC :1 [root@lep8a ISO]# firewall-cmd --add-port 1/tcp [root@lep8a ISO]# [root@lep8a ISO]# firewall-cmd --add-service=vnc-server Warning: ALREADY_ENABLED 3. using the vncviewer try to connect to the pkVMhostIP:1 the vncviewer connects and the install begins. I have used Vinagre (a remote desktop viewer for the GNOME desktop) Install ISO Information: utopic-server-ppc64el_Oct6.iso ** Affects: qemu (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: architecture-ppc64le bot-comment bugnameltc-117245 severity-high targetmilestone-inin1410 -- VNC based installation does not interpret key strokes correctly. https://bugs.launchpad.net/bugs/1378708 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Bug 1378708] Re: VNC based installation does not interpret key strokes correctly.
This doesn't seem to have anything to do with ubiquity what makes you think this isn't simply your keyboard's auto repeat feature and you're holding down the key for too long? ** Package changed: ubiquity (Ubuntu) = qemu (Ubuntu) ** Changed in: qemu (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1378708 Title: VNC based installation does not interpret key strokes correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1378708/+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 1279000] Re: db migrate script to set charset=utf8 for all tables
** Changed in: openstack-chef Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1279000 Title: db migrate script to set charset=utf8 for all tables To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1279000/+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 1332203] Re: autofs5-ldap regularly crashes after long periods of time
This problem has continued over the past few months. We slogged through
the strace output a few times and just today found this:
[pid 935] sendto(11, 27Sep 22 13:06:30 automount[92..., 90, MSG_NOSIGNAL,
NULL, 0) = -1 ECONNREFUSED (Connection refused)
[pid 935] close(11) = 0
[pid 935] socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
[pid 935] connect(4, {sa_family=AF_FILE, path=/dev/log}, 110) = -1
ECONNREFUSED (Connection refused)
[pid 935] close(4)= 0
[pid 935] ioctl(3, 0xc0189379, 0x7f22fecabb20) = 0
[pid 935] ioctl(3, 0xc0189375, 0x7f22fecabb20) = 0
[pid 935] sched_yield() = 0
[pid 935] umount(/home, 0) = -1 EBUSY (Device or resource busy)
[pid 935] nanosleep({0, 2}, NULL) = 0
[pid 935] umount(/home, 0) = -1 EBUSY (Device or resource busy)
[pid 935] nanosleep({0, 2}, NULL) = 0
Our syslog sends some events to another loghost and the top call to
sendto(), which appears to fail, and automount tries to go down
gracefully. Checking the .crash file again, the backtrace is identical.
The backtrace does seem to support this story since there is a call to
vsyslog() inside of log_error().
So this bug may be filed under the wrong package, depending on whose
responsibility it is to handle this kind of error. Reading the man page
for vsyslog(), I don't see any way the caller can catch an error so this
could in fact be a problem with it.
We are using rsyslog 5.8.6-1ubuntu8.9 currently.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/1332203
Title:
autofs5-ldap regularly crashes after long periods of time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1332203/+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 1373964] Re: write_files should not be curtin_hooks
** Changed in: curtin (Ubuntu) Status: New = Triaged ** Changed in: curtin (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1373964 Title: write_files should not be curtin_hooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1373964/+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 1386394] [NEW] SRU: catch 14.04 up with curtin trunk features
Public bug reported: === Begin SRU Template === [Impact] Newer versions of MAAS require/use some features in newer versions of curtin. This bug tracks and describes new features of curtin that are being brought back to 14.04. The following is a list of the new features that are being SRU'd. * hardware enablement: ppc64 support MAAS install with fast path installer is expected to work both to PowerNV and KVM guests. * hardware enablement: know kernel mapping for utopic (hwe-u = 3.16). When the Utopic level hardware enablement kernel is made available for 14.04, curtin should be able to utilize that kernel when it is booted in an environment with a 3.16 kernel. * feature: support installing disk images including windows. MAAS's windows install should function. * feature: support creating swap file installations by default should have a swap file created (/swap.img). * feature: support reporting logs back to MAAS curtin install logs are available on maas in 1.7 and later for user inspection. * feature: enable logging of installation to /var/log/curtin/install.log (LP: #1378910) curtin install will always write /var/log/curtin/install.log with log/debug information. [Other Info] MAAS's dependency on newer curtin for hardware enablement and features was raised to the technical board at [1]. There was no official response there, so at the current time we're pursuing this under a standard SRU. [1] https://lists.ubuntu.com/archives/technical-board/2014-July/001986.html === End SRU Template === ** Affects: curtin (Ubuntu) Importance: Medium Status: Fix Released ** Affects: curtin (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Trusty) Status: New = Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: curtin (Ubuntu) Status: New = Fix Released ** Changed in: curtin (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1386394 Title: SRU: catch 14.04 up with curtin trunk features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1386394/+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 1386396] [NEW] package mysql-server-5.5 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1
Public bug reported: Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/mysql-server-5.5_5.5.40-0ubuntu0.14.04.1_i386.deb ProblemType: Package DistroRelease: Ubuntu 14.04 Package: mysql-server-5.5 (not installed) ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 AptOrdering: mysql-server-5.5: Install mysql-server-5.5: Configure Architecture: i386 Date: Mon Oct 27 22:47:56 2014 DuplicateSignature: package:mysql-server-5.5:(not installed):le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2014-10-22 (4 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) SourcePackage: mysql-5.5 Title: package mysql-server-5.5 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to trusty on 2014-10-25 (2 days ago) ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- 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/1386396 Title: package mysql-server-5.5 (not installed) failed to install/upgrade: le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1386396/+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 1386394] Re: SRU: catch 14.04 up with curtin trunk features
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/sru-utopic-level -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1386394 Title: SRU: catch 14.04 up with curtin trunk features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1386394/+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 1381537] Re: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix
** Description changed: - The current version of dovecot in Ubuntu 12.04 LTS, Precise Pangolin is - 2.0.19 + SRU Request: + + [Impact] + Dovecot in Precise does not contain the ssl_protocols configuration option that allows disabling SSLv3. Since there are now known weaknesses in SSLv3, it would be preferable to have an option to disable it like on later releases. + + [Test Case] + 1- Configure dovecot + 2- Connect with SSLv3 only + 3- add ssl_protocols = !SSLv3 to dovecot configuration ile + 4- Connect with SSLv3 only + 5- Connect with TLS to make sure it still works + + Alternatively, the security team QRT script has been modified to test + for this. It can be used. + + [Regression Potential] + This touches the config file parsing code, and the SSL code. Any regression could result in the configuration file not being parsed correctly, or for some unknown issue with SSL negotiation. + + + Original description: + The current version of dovecot in Ubuntu 12.04 LTS, Precise Pangolin is 2.0.19 This version is too old to switch off SSLv3 which has been designated insecure as of the recent poodle discovery [1]. In dovecot versions 2.1+ the protocol can be switched off, but for older versions the source code would need to be patched [2,3] I asked the Ubuntu team to either backport a patch to 2.0.19, or package a newer version of dovecot for precise. [1] https://www.openssl.org/~bodo/ssl-poodle.pdf [2] http://askubuntu.com/questions/537196/how-do-i-patch-workaround-sslv3-poodle-vulnerability-cve-2014-3566 [3] http://www.mail-archive.com/dovecot@dovecot.org/msg59945.html - source package in precise security: dovecot 1:2.0.19-0ubuntu2.1 ** Description changed: SRU Request: [Impact] Dovecot in Precise does not contain the ssl_protocols configuration option that allows disabling SSLv3. Since there are now known weaknesses in SSLv3, it would be preferable to have an option to disable it like on later releases. + It may not be appropriate to default to having SSLv3 disabled yet. As + such, this SRU only adds the configuration option, but doesn't enable + it. + [Test Case] 1- Configure dovecot 2- Connect with SSLv3 only - 3- add ssl_protocols = !SSLv3 to dovecot configuration ile + 3- add ssl_protocols = !SSLv3 to dovecot configuration file 4- Connect with SSLv3 only 5- Connect with TLS to make sure it still works Alternatively, the security team QRT script has been modified to test for this. It can be used. [Regression Potential] This touches the config file parsing code, and the SSL code. Any regression could result in the configuration file not being parsed correctly, or for some unknown issue with SSL negotiation. - Original description: The current version of dovecot in Ubuntu 12.04 LTS, Precise Pangolin is 2.0.19 This version is too old to switch off SSLv3 which has been designated insecure as of the recent poodle discovery [1]. In dovecot versions 2.1+ the protocol can be switched off, but for older versions the source code would need to be patched [2,3] I asked the Ubuntu team to either backport a patch to 2.0.19, or package a newer version of dovecot for precise. [1] https://www.openssl.org/~bodo/ssl-poodle.pdf [2] http://askubuntu.com/questions/537196/how-do-i-patch-workaround-sslv3-poodle-vulnerability-cve-2014-3566 [3] http://www.mail-archive.com/dovecot@dovecot.org/msg59945.html source package in precise security: dovecot 1:2.0.19-0ubuntu2.1 ** Changed in: dovecot (Ubuntu Precise) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1381537 Title: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1381537/+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 1296553] Re: samba crashed with SIGABRT in smb_panic()
*** This bug is a duplicate of bug 1281532 *** https://bugs.launchpad.net/bugs/1281532 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New = Confirmed -- 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/1296553 Title: samba crashed with SIGABRT in smb_panic() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1296553/+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 1386429] [NEW] openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-updates/juno fails install (exit status 1)
Public bug reported:
openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-
updates/juno fails install (exit status 1)
full stack trace:
2014-10-27 20:40:42 INFO install Setting up openstack-dashboard
(1:2014.2-0ubuntu1~cloud0) ...
2014-10-27 20:40:43 INFO install Adding system user `horizon' (UID 106) ...
2014-10-27 20:40:43 INFO install Adding new user `horizon' (UID 106) with group
`horizon' ...
2014-10-27 20:40:43 INFO install Not creating home directory
`/usr/share/openstack-dashboard/'.
2014-10-27 20:40:43 INFO install Collecting and compressing static assets...
2014-10-27 20:40:45 INFO install Traceback (most recent call last):
2014-10-27 20:40:45 INFO install File manage.py, line 25, in module
2014-10-27 20:40:45 INFO install execute_from_command_line(sys.argv)
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
399, in execute_from_command_line
2014-10-27 20:40:45 INFO install utility.execute()
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
392, in execute
2014-10-27 20:40:45 INFO install
self.fetch_command(subcommand).run_from_argv(self.argv)
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
261, in fetch_command
2014-10-27 20:40:45 INFO install commands = get_commands()
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/core/management/__init__.py, line
107, in get_commands
2014-10-27 20:40:45 INFO install apps = settings.INSTALLED_APPS
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 54, in
__getattr__
2014-10-27 20:40:45 INFO install self._setup(name)
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 49, in _setup
2014-10-27 20:40:45 INFO install self._wrapped = Settings(settings_module)
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 128, in
__init__
2014-10-27 20:40:45 INFO install mod =
importlib.import_module(self.SETTINGS_MODULE)
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/django/utils/importlib.py, line 40, in
import_module
2014-10-27 20:40:45 INFO install __import__(name)
2014-10-27 20:40:45 INFO install File
/usr/share/openstack-dashboard/openstack_dashboard/settings.py, line 316, in
module
2014-10-27 20:40:45 INFO install from local.local_settings import * # noqa
2014-10-27 20:40:45 INFO install File
/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py,
line 98, in module
2014-10-27 20:40:45 INFO install SECRET_KEY =
secret_key.generate_or_read_from_file('/var/lib/openstack-dashboard/secret_key')
2014-10-27 20:40:45 INFO install File
/usr/lib/python2.7/dist-packages/horizon/utils/secret_key.py, line 61, in
generate_or_read_from_file
2014-10-27 20:40:45 INFO install raise FilePermissionError(Insecure key
file permissions!)
2014-10-27 20:40:45 INFO install horizon.utils.secret_key.FilePermissionError:
Insecure key file permissions!
2014-10-27 20:40:45 INFO install dpkg: error processing package
openstack-dashboard (--configure):
2014-10-27 20:40:45 INFO install subprocess installed post-installation script
returned error exit status 1
Looks like /var/lib/openstack-dashboard/secret_key is created without the
correct permissions
using charm lp:~openstack-charmers/charms/trusty/openstack-dashboard/next to
deploy currently -- doesnt seem as if that charm is writing anything to those
locations before apt-get install, but I could be wrong.
** Affects: horizon (Ubuntu)
Importance: Undecided
Status: New
** Tags: oil
--
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/1386429
Title:
openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-
updates/juno fails install (exit status 1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1386429/+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 1386429] Re: openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-updates/juno fails install (exit status 1)
Looks like it installed fine on a clean trusty lxc with cloud:trusty- updates/juno -- so moving it this bug to the charm. ** Package changed: horizon (Ubuntu) = openstack-dashboard (Juju Charms Collection) ** Summary changed: - openstack-dashboard 2014.2-0ubuntu1~cloud0 from cloud:trusty-updates/juno fails install (exit status 1) + cloud:trusty-updates/juno fails apt-get install openstack-dashboard -- bad /var/lib/openstack-dashboard/secret permissions -- 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/1386429 Title: cloud:trusty-updates/juno fails apt-get install openstack-dashboard -- bad /var/lib/openstack-dashboard/secret permissions To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/openstack-dashboard/+bug/1386429/+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 1386465] [NEW] apparmor profile prevents libvirtd from creating a socket
Public bug reported: I'd like to emphasize that I upgraded from Ubuntu Gnome 14.4 to 14.10 I installed systemd. libvirtd fails to start on the stock upgrade system. Examining the log files it looks like apparmor prevents libvirtd from creating a net socket. Okt 28 00:31:49 rivendell kernel: audit: type=1400 audit(1414452709.808:42): apparmor=DENIED operation=create profile=/usr/sbin/libvirtd pid=15162 comm=libvirtd family=netlink sock_type=raw protocol=9 Okt 28 00:31:49 rivendell kernel: audit: type=1400 audit(1414452709.808:43): apparmor=DENIED operation=create profile=/usr/sbin/libvirtd pid=15162 comm=libvirtd family=netlink sock_type=raw protocol=0 I tried to run aa-logprof in order to have apparmor fix the permissions but that did not work. that is why modified apparmor profiles are attached. Putting apparmor in audit mode aa-audit /usr/sbin/libvirtd enables me to start libvirt systemctl restart libvirtd It looks like the apparmor profile permissions have to be adjusted. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libvirt-bin 1.2.8-0ubuntu11 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 28 01:20:45 2014 InstallationDate: Installed on 2013-01-08 (657 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) KernLog: SourcePackage: libvirt UpgradeStatus: Upgraded to utopic on 2014-10-23 (4 days ago) modified.conffile..etc.apparmor.d.usr.sbin.libvirtd: [modified] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/libvirt/qemu.conf'] mtime.conffile..etc.apparmor.d.usr.sbin.libvirtd: 2014-10-28T00:33:09.824586 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1386465 Title: apparmor profile prevents libvirtd from creating a socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/+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 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
Here's a debdiff for the patch. ** Patch added: lxc.debdiff https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+attachment/4246695/+files/lxc.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+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 1385851] Re: OpenVPN only supports TLS v1.0
** Tags added: trusty utopic ** Patch added: https://github.com/OpenVPN/openvpn/commit/4b67f9849ab3efe89268e01afddc7795f38d0f64; https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+attachment/4246696/+files/4b67f9849ab3efe89268e01afddc7795f38d0f64.patch ** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1385851 Title: OpenVPN only supports TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+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 1323729] Re: Remove Open vSwitch and Linuxbridge plugins from the Neutron tree
Fix proposed to branch: master Review: https://review.openstack.org/131323 ** Changed in: devstack Status: Confirmed = In Progress ** Changed in: devstack Assignee: Armando Migliaccio (armando-migliaccio) = YAMAMOTO Takashi (yamamoto) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1323729 Title: Remove Open vSwitch and Linuxbridge plugins from the Neutron tree To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1323729/+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 1386503] [NEW] openstack snapshot, migration, suspend broken by invtsc
Public bug reported: I believe this commit http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=de0aeafe9ce3eb414c8b5d3aa8995d776a2952de fixes the issue. In OpenStack nova, one gets this error: libvirtError: internal error: unable to execute QEMU command 'migrate': State blocked by non-migratable device 'cpu' when executing 'nova image-create', or 'nova suspend' operations. This in turn is caused by the 'invtsc' being used for 'host-model', preventing a migration. $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 $ apt-cache policy libvirt-bin libvirt-bin: Installed: 1.2.8-0ubuntu11 Candidate: 1.2.8-0ubuntu11 Version table: *** 1.2.8-0ubuntu11 0 500 http://ca.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1386503 Title: openstack snapshot, migration, suspend broken by invtsc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386503/+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 1386514] [NEW] multipathd can't be updated
Public bug reported: During package update on running 12.04 server I got: Preparing to replace multipath-tools 0.4.9-3ubuntu5.1 (using .../multipath-tools_0.4.9-3ubuntu5.3_amd64.deb) ... * Stopping multipath daemon multipathd Oct 28 08:06:13 | mpath1: map in use invoke-rc.d: initscript multipath-tools, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg - trying script from the new package instead ... * Stopping multipath daemon multipathd Oct 28 08:06:13 | mpath1: map in use invoke-rc.d: initscript multipath-tools, action stop failed. dpkg: error processing /var/cache/apt/archives/multipath-tools_0.4.9-3ubuntu5.3_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 * Starting multipath daemon multipathd [ OK ] Errors were encountered while processing: /var/cache/apt/archives/multipath-tools_0.4.9-3ubuntu5.3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is definitely wrong to stop multipathd on running system And update can't be installed. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1386514 Title: multipathd can't be updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1386514/+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 1350491] Re: package cgmanager 0.27-0ubuntu8 failed to install/upgrade
[Expired for cgmanager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cgmanager (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1350491 Title: package cgmanager 0.27-0ubuntu8 failed to install/upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1350491/+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 1350509] Re: package cgmanager 0.27-0ubuntu8 failed to install/upgrade
[Expired for cgmanager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cgmanager (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1350509 Title: package cgmanager 0.27-0ubuntu8 failed to install/upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1350509/+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 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
The attachment lxc.debdiff seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+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 1004243] Re: multipath installs not working
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004243 Title: multipath installs not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1004243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386052] [NEW] pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Public bug reported: Hi, Seems pollen fails to log everytime rsyslog packages are upgraded or rsyslog daemon itself is bounced. There's an alert for it, but I don't think it should be set up in such a way that we need to manually bounce the pollen daemon every time rsyslog packages are upgraded. Could you please look into fixing this so pollen itself does something to reconnect to syslog? Thanks, Haw ** Affects: pollen (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, Seems pollen fails to log everytime rsyslog packages are upgraded or rsyslog daemon itself is bounced. There's an alert for it, but I don't think it should be set up in such a way that we need to manually bounce the pollen daemon every time rsyslog packages are upgraded. + Could you please look into fixing this so pollen itself does something + to reconnect to syslog? + Thanks, Haw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383589] Re: [Dell Vostro 3546] Wireless key does not work on 14.04
patch for upstream has been submitted ** Changed in: linux (Ubuntu) Status: Confirmed = In Progress ** Changed in: hwe-next Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383589 Title: [Dell Vostro 3546] Wireless key does not work on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354114] Re: multipath segmentation Fault (libmultipath: update waiter handling)
This bug was fixed in the package multipath-tools - https://launchpad.net/ubuntu/+source/multipath-tools/0.4.9-3ubuntu7.2 --- multipath-tools (0.4.9-3ubuntu7.2) trusty; urgency=medium * 1002-fix-linking-library.patch: Move $(LIBDEPS) to the end of the link line to fix underlinking with ld --as-needed (LP: #1004243) -- Adam Conrad adcon...@ubuntu.com Mon, 13 Oct 2014 07:47:07 -0600 ** Changed in: multipath-tools (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354114 Title: multipath segmentation Fault (libmultipath: update waiter handling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1354114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317587] Re: ClamAV 0.98.1 is Outdated
Since clamav is available in trusty-backports, does that mean the Trusty task can be marked Fix Released? Will clamav 0.98.4 move to trusty-updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317587 Title: ClamAV 0.98.1 is Outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1317587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385038] Re: Corrupted low memory error on Ubuntu 14.04
memtest from Grub menu returned no errors. Machine is HP Pavilion dv7 Notebook PC Product number WW180AV Bios version F.13 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385038 Title: Corrupted low memory error on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1378690] Re: [Lenovo ThinkPad T60] 82573L Gigabit Ethernet Controller UNCLAIMED on Ubuntu
Guys I don't have that computer to proceed with the test. I gave it back to the client so I can't send the data they want. On 26/10/2014 09:19 μμ, Christopher M. Penalver wrote: Theodotos Andreou, have you e-mailed the appropriate mailing list yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378690 Title: [Lenovo ThinkPad T60] 82573L Gigabit Ethernet Controller UNCLAIMED on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347837] Re: can't install or remove powerd (even when with --force-all)
That looks like a systemd message. I fixed this on my own system by making a systemd config for it. Not sure if I did it right. /etc/systemd/system$ ls -l powerd.service lrwxrwxrwx 1 root root 34 Oct 26 22:26 powerd.service - /lib/systemd/system/powerd.service /etc/systemd/system$ cat powerd.service [Unit] Description=Power daemon to monitor and control system power state [Service] Type=dbus BusName=com.canonical.powerd Restart=always Environment=ANDROID_ROOT=/system ExecStart=/usr/bin/powerd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347837 Title: can't install or remove powerd (even when with --force-all) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1347837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382748] Re: Interface with 16:9 aspect ratio
I can't confirm this problem. To me everything is working correctly. See screenshot. ** Attachment added: tvtime 16:9 https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/1382748/+attachment/4245971/+files/tvtime%20mate.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382748 Title: Interface with 16:9 aspect ratio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/1382748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386057] Re: Merge evince 3.14.1-1 from debian
** Patch added: ubuntu to new https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1386057/+attachment/4245972/+files/ubuntu.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386057 Title: Merge evince 3.14.1-1 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1386057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386057] [NEW] Merge evince 3.14.1-1 from debian
Public bug reported: Merge from debian again to help reduce duplication of work. ** Affects: evince (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/1386057 Title: Merge evince 3.14.1-1 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1386057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386057] Re: Merge evince 3.14.1-1 from debian
** Patch added: debian to new https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1386057/+attachment/4245973/+files/debian.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386057 Title: Merge evince 3.14.1-1 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1386057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385026] Re: Transcriber can open audio, but plays static
I have another laptop computer with the exact same configuration which is opening and playing mp3 files fine through transcriber, so this appears to be a configuration problem with this particular PC. A workaround is that transcriber does open and play wav files, so I will convert to those for now. Suggestions on which packages need to be (re)installed to get mp3 file functionality working again would be welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385026 Title: Transcriber can open audio, but plays static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transcriber/+bug/1385026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373776] Re: internal panel brightness set to 0 when switching back to internal-only mode
This is a simple patch to fix this issue for sna / uxa mode and tested on UMA / discrete card. ** Patch added: fix-no-backlight.patch https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1373776/+attachment/4245974/+files/fix-no-backlight.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373776 Title: internal panel brightness set to 0 when switching back to internal- only mode To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1373776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382748] Re: Interface with 16:9 aspect ratio
OK, I found the problem. This occurs when changing appearance through the following menu path: * Setup * Output configuration * Apply matte * And choose one of the following: 4: 3, 16:10 16: 9, 1.85: 1 or 2.35: 1 Everything is fine when used directly in the menu path: * Setup * Output configuration * 16: 9 output I will investigate this problem and propose a solution (soon). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382748 Title: Interface with 16:9 aspect ratio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/1382748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1356558] Re: BUG: soft lockup - CPU stuck for 22s! [md3_raid1]
Is there anything I should test next? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1356558 Title: BUG: soft lockup - CPU stuck for 22s! [md3_raid1] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921533] Re: vtun server is not accepting client connections because of missing /var/lock/vtund at startup
Here's the fix for another distro: # cat EOF /etc/tmpfiles.d/vtund.conf d /run/lock/vtund 0755 root root - EOF # fix it before the next reboot too # systemd-tmpfiles --create We can debate all day whether it's a packaging bug or a software bug. But that may be the fix here too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921533 Title: vtun server is not accepting client connections because of missing /var/lock/vtund at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/921533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385390] Re: package ack-grep 2.12-1 failed to install/upgrade: trying to overwrite `/usr/bin/ack', which is the diverted version of `/usr/bin/ack-grep'
If you set up a local diversion as instructed in the section Renaming ack-grep on Debian-derived distros on their website, remove it: sudo dpkg-divert --remove /usr/bin/ack-grep -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385390 Title: package ack-grep 2.12-1 failed to install/upgrade: trying to overwrite `/usr/bin/ack', which is the diverted version of `/usr/bin/ack-grep' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ack-grep/+bug/1385390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924686] Re: package libfreerdp1 not installed failed to install/upgrade: попытка перезаписать «/usr/share/freerdp/keymaps/aliases», который уже имеется в пакете libfreerdp0 0.8.2-2build1
too old. ** Changed in: freerdp (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924686 Title: package libfreerdp1 not installed failed to install/upgrade: попытка перезаписать «/usr/share/freerdp/keymaps/aliases», который уже имеется в пакете libfreerdp0 0.8.2-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/924686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310762] Re: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up
I have absolutely the same problem: Nvidia GT630M, Ubuntu 14.10, Nvidia drivers 331.89 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310762 Title: [HP ZBook 15 Mobile Workstation] Ubuntu 14.04 random freeze and lock up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
The same problem Nvidia GT630M, Ubuntu 14.10, nvidia 331.89 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373776] Re: internal panel brightness set to 0 when switching back to internal-only mode
that's the patch that this upload has included :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373776 Title: internal panel brightness set to 0 when switching back to internal- only mode To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1373776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283826] Re: lightdm hangs after updates
Hi I very much appreciate the assistance. Im ok getting into terminal as long as its a copy and paste kinda deal, Im a gui user having moved over from windows but over the last few years I have gotten fairly familiar with what does what when it comes to ubuntu/linux... and have no problem busting out terminal or opening this or that in kate and doing some editing... I do not however have the ability to just buts out a terminal window and know what to type natively. here you go thank you.. took a while to figure out how to get into the log files as root :) thanks again :) * lightdm.conf*** [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu greeter-show-manual-login=true **end **lightdm.log* [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.10.1, UID=0 PID=1296 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-xubuntu.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registered seat module xlocal [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Registered seat module surfaceflinger [+0.00s] DEBUG: Adding default seat [+0.00s] DEBUG: Seat: Starting [+0.00s] DEBUG: Seat: Creating greeter session [+0.00s] DEBUG: Seat: Creating display server of type x [+0.01s] DEBUG: Quitting Plymouth [+0.02s] DEBUG: Using VT 7 [+0.02s] DEBUG: Seat: Starting local X display on VT 7 [+0.02s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log [+0.02s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0 [+0.02s] DEBUG: DisplayServer x-0: Launching X Server [+0.02s] DEBUG: Launching process 1309: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.02s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0 [+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.05s] DEBUG: Loading users from org.freedesktop.Accounts [+0.05s] DEBUG: User /org/freedesktop/Accounts/User1001 added [+0.08s] DEBUG: User /org/freedesktop/Accounts/User1003 added [+0.10s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.11s] DEBUG: User /org/freedesktop/Accounts/User1002 added [+2.09s] DEBUG: Got signal 10 from process 1309 [+2.09s] DEBUG: DisplayServer x-0: Got signal from X server :0 [+2.09s] DEBUG: DisplayServer x-0: Connecting to XServer :0 [+2.09s] DEBUG: Launching process 1499: /sbin/prime-offload [+2.09s] DEBUG: Process 1499 exited with return value 0 [+2.09s] DEBUG: Seat: Exit status of /sbin/prime-offload: 0 [+2.10s] DEBUG: Seat: Display server ready, starting session authentication [+2.10s] DEBUG: Session pid=1505: Started with service 'lightdm-greeter', username 'lightdm' [+2.16s] DEBUG: Session pid=1505: Authentication complete with return value 0: Success [+2.16s] DEBUG: Seat: Session authenticated, running command [+2.16s] DEBUG: Session pid=1505: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter [+2.16s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+2.16s] DEBUG: Session pid=1505: Logging to /var/log/lightdm/x-0-greeter.log [+2.17s] DEBUG: Activating VT 7 [+2.17s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c1 [+2.34s] DEBUG: Session pid=1505: Greeter connected version=1.10.1 [+2.71s] DEBUG: Session pid=1505: Greeter start authentication [+2.71s] DEBUG: Session pid=1748: Started with service 'lightdm', username '(null)' [+2.72s] DEBUG: Session pid=1748: Got 1 message(s) from PAM [+2.72s] DEBUG: Session pid=1505: Prompt greeter with 1 message(s) [+2.76s] DEBUG: User /org/freedesktop/Accounts/User1003 changed [+2.81s] DEBUG: User /org/freedesktop/Accounts/User1000 changed [+6.27s] DEBUG: Session pid=1505: Greeter start authentication
[Bug 1294052] Re: Unlock screen shown twice (violet and black) after resume from sleep
*** This bug is a duplicate of bug 1292451 *** https://bugs.launchpad.net/bugs/1292451 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294052 Title: Unlock screen shown twice (violet and black) after resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1294052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325881] Re: [Asus X550LD] Touchpad not working/detected Ubuntu 14.04
I have the same issue in Asus R513C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325881 Title: [Asus X550LD] Touchpad not working/detected Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1325881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380747] Re: SST on IPv6 fails for xtrabackup-v2
** Also affects: percona-xtradb-cluster/5.5 Importance: Undecided Status: New ** Also affects: percona-xtradb-cluster/5.6 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/1380747 Title: SST on IPv6 fails for xtrabackup-v2 To manage notifications about this bug go to: https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1380747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384297] Re: gpu i915 OOPS on power change intel_display_power_put+0xf9
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384297 Title: gpu i915 OOPS on power change intel_display_power_put+0xf9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1384297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
Ryan, upstream has questions on https://bugreports.qt- project.org/browse/QTBUG-42189 please can you answer them there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381660] Re: Realtek card rtl8723be bluetooth and WiFi
I'm using Utopics default kernel and I also got wifi working with https://github.com/lwfinger/rtlwifi_new. I even got bluetooth to work with lwfinger's rtl8723au_bt. But when bluetooth is enabled, wifi is not working very well (unless the signals is very good, the connection becomes slow and unresponsive at times). I know that bluetooth and wifi use the same antenna for this chipset, but I'm hoping it's a driver issue and could be fixed on the software level. I would be happy to debug if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381660 Title: Realtek card rtl8723be bluetooth and WiFi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384297] Re: gpu i915 OOPS on power change intel_display_power_put+0xf9
I see this during suspend/resume, and sometimes it results in lockup, requiring a restart of lightdm. I think it might be safe to say that this regression happened somewhere between Linux kernel 3.13 and 3.16. I was previously running Ubuntu 14.04 LTS (with the 3.13 kernel) and there were no issues. However, running Ubuntu 14.04 LTS with the upstream 3.16 kernel gave this warning. After upgrading to Ubuntu 14.10 LTS (with the Ubuntu 3.16 kernel), the problem persisted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384297 Title: gpu i915 OOPS on power change intel_display_power_put+0xf9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1384297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386077] [NEW] Dell XPS Touchpad not detected on Ubuntu 14.10
Public bug reported: The touchpad was working properly on Ubuntu 14.04 but it's not recognized as a device after upgrade to 14.10. Version: Ubuntu 3.16.0-23.31-generic 3.16.4 cat /proc/bus/input/devices output: I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name=Lid Switch P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name=Video Bus P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name=HDA Intel HDMI HDMI/DP,pcm=3 P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name=HDA Intel HDMI HDMI/DP,pcm=7 P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name=HDA Intel HDMI HDMI/DP,pcm=8 P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name=HDA Intel PCH Headphone Mic P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product= Version= N: Name=Dell WMI hotkeys P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input12 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=13 B: KEY=1500b 20030 0 0 B: MSC=10 I: Bus=0003 Vendor=06cb Product=0af8 Version=0111 N: Name=SYNAPTICS Synaptics Large Touch Screen P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-3/2-3:1.0/0003:06CB:0AF8.0002/input/input13 U: Uniq= H: Handlers=mouse1 event11 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=2608003 I: Bus=0003 Vendor=0bda Product=5752 Version=3902 N: Name=Integrated_Webcam_HD P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-5/2-5:1.0/input/input15 U: Uniq= H: Handlers=kbd event12 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=046d Product=c00e Version=0110 N: Name=Logitech USB-PS/2 Optical Mouse P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/0003:046D:C00E.0005/input/input843 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 lspci -vnvn lspci-vnvn.log output: 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09) Subsystem: Dell Device [1028:060a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0]
[Bug 1385641] Re: urfkilld use 100% cpu after resume
This also happens on a Dell XPS developer edition laptop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385641 Title: urfkilld use 100% cpu after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1385641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385793] Re: Merge 1.6-4 from debian
** Changed in: gzip (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385793 Title: Merge 1.6-4 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1385793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386078] [NEW] Icon at the wrong place
Public bug reported: The icon of qshutdown is shown in the upper left corner and not at the right like the other icons. (see picture) System: Description:Ubuntu 14.10 Release:14.10 Package Version: 1.6.8-1 This happens since ubuntu 14.10, with 14.04 i have no Problems. ** Affects: shutdown-qapps (Ubuntu) Importance: Undecided Status: New ** Attachment added: qshutdown.png https://bugs.launchpad.net/bugs/1386078/+attachment/4246003/+files/qshutdown.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386078 Title: Icon at the wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shutdown-qapps/+bug/1386078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385903] Re: imagemagick crashes with stack smashing detected
What is the imagemagick version ? What is the image being converted ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385903 Title: imagemagick crashes with stack smashing detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1385903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
