[Touch-packages] [Bug 1770195] Re: OpenSSL missing ciphers
[Expired for openssl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssl (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1770195 Title: OpenSSL missing ciphers Status in openssl package in Ubuntu: Expired Bug description: In OpenSSL 1.1.0 several ciphers were simply removed. They can be re- enabled by using "enable-weak-ssl-ciphers" option when building. This should be done to increase compatibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1770195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error
** Description changed:
Impact
--
- Users willing to use the slapd rwm overlay will face a slapd segmentation
fault
- when trying to rewrite some rules. Backporting this fix will allow users using
- stable releases to take advantage of this feature without crashing slapd. This
- issue was fixed by upstream not freeing the rwm overlay filter memory without
- prior checking.
+ Users willing to use the slapd rwm overlay will face a slapd
+ segmentation fault when trying to rewrite some rules. Backporting this
+ fix will allow users using stable releases to take advantage of this
+ feature without crashing slapd. This issue was fixed by upstream not
+ freeing the rwm overlay filter memory without prior checking.
Test Case
-
- In this test case, the rwm overlay will be used and a rule will be created to
- deny any search request for uid=root, then the 'ldapsearch' will be invoked to
- trigger the failure. It is important to mention that the 'ldapsearch' command
- should fail regardless the presence of the bug in the package, the target here
- is the slapd crash. To reproduce this bug one can follow the procedure below
in
- Ubuntu xenial, bionic or disco:
+ In this test case, the rwm overlay will be used and a rule will be
+ created to deny any search request for uid=root, then the 'ldapsearch'
+ will be invoked to trigger the failure. It is important to mention that
+ the 'ldapsearch' command should fail regardless the presence of the bug
+ in the package, the target here is the slapd crash. To reproduce this
+ bug one can follow the procedure below in Ubuntu xenial, bionic or
+ disco:
$ sudo apt-get update
$ sudo apt-get install slapd ldap-utils -y
Reconfigure the slapd package. When asked about a domain, use "example.com".
Choose a password you want (or just leave it blank), and accept defaults for
everything else:
$ sudo dpkg-reconfigure slapd
Create a file called 'add-rwm.ldif' with the following content:
$ cat add-rwm.ldif
dn: cn=module{0},cn=config
changetype: modify
add: olcModuleLoad
olcModuleLoad: rwm
dn: olcOverlay=rwm,olcDatabase={1}mdb,cn=config
changetype: add
objectClass: olcOverlayConfig
objectClass: olcRwmConfig
olcOverlay: rwm
olcRwmRewrite: {0} rwm-rewriteEngine "on"
olcRwmRewrite: {1} rwm-rewriteContext "searchFilter"
olcRwmRewrite: {2} rwm-rewriteRule "(.*)(uid=root)(.*)" "$1$2$3" "#"
-
With this file in place, run:
$ sudo ldapadd -Q -Y EXTERNAL -H ldapi:/// -f add-rwm.ldif
Now, to trigger the crash:
$ ldapsearch -x -h localhost -b dc=example,dc=com -LLL uid=root
Server is unwilling to perform (53)
Additional information: searchFilter/searchFilterAttrDN massage error
-
slapd process will die, and /var/crash will have a crash file for slapd. You
can run the following command to confirm the error:
$ cat /var/log/syslog | grep filter_free
Aug 9 19:51:05 popular-gorilla slapd[1479]: filter_free: unknown filter
type=28530
-
Regression Potential
- Since the fix is a patch provided by upstream (reviewed by maintainers and us)
- simple mistakes like typos are not expected. The patch impacts only the rwm
- module which is not loaded by default. So any regression would affect only the
- users that make use of this overlay. If an user is not using rwm overlay and
is
- facing any issue, it should be related to other problems related to LDAP
- directory services.
-
-
+ Since the fix is a patch provided by upstream (reviewed by maintainers
+ and us) simple mistakes like typos are not expected. The patch impacts
+ only the rwm module which is not loaded by default. So any regression
+ would affect only the users that make use of this overlay. If an user is
+ not using rwm overlay and is facing any issue, it should be related to
+ other problems related to LDAP directory services.
[Original message]
Hello!
We have faced slapd crash, seems an attacker was trying to brute force one
of our services and uid parsing failures caused slapd crash:
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH
base="ou=test,dc=test,dc=com" scope=2 deref=0
filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid
userPassword uidNumber gidNumber gecos homeDirectory loginShell
krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp
shadowLastChange shadowMin shadow
Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange
krbPasswordExpiration pwdAttribute authorizedService accountExpires
userAccountControl nsAccountLock host loginDisabled loginExpirationTime
loginAllowedTimeMap sshPublic
Key
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0
nentries=0 text=massaged filter parse error
Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip
[Touch-packages] [Bug 1839598] Re: tcp_wrappers does not whitelisting of domains, vs IPs
Hello Federico, Wietse is correct. You will not get security benefits from your proposed changes. Public key authentication, combined with a 2FA mechanism such as TOTP for interactive users, is the current best practice. IP filtering is a useful tool; you can already have good benefits from allowing the /16 or /24 or whatever address ranges your contractors are expected to be using. That will drastically reduce the number of compromised hosts on the internet that can contact your server and perform password brute-force authentication attempts. The single best security improvement you can make is disable password authentication in openssh-server and require authorized_keys to log in. We will not make drastic changes to the design and implementation of tcp-wrappers. Thanks for your interest in making Ubuntu more secure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tcp-wrappers in Ubuntu. https://bugs.launchpad.net/bugs/1839598 Title: tcp_wrappers does not whitelisting of domains, vs IPs Status in tcp-wrappers package in Ubuntu: New Bug description: TCP Wrappers (also known as tcp_wrappers) is a host-based networking ACL system, used to filter network access to Internet Protocol servers. It allows host or subnetwork IP addresses, names and/or ident query replies, to be used as tokens on which to filter for access control purposes. The original code was written by Wietse Venema in 1990 He maintained it until 1995, and on June 1, 2001, released it under its own BSD-style license. The tarball includes a library named Libwrap that implements the actual functionality. I had an email conversation with him that lead to nowhere. He does not agree with my request for a redesign. Very concisely, there is no way as of now to whitelist a domain, vs an IP address. You need to know the IP address to which the domain resolves to beforehand, which makes domain updates impossible to process. This causes tremendous operational problems when the person you need to give access to has an IP address that changes often. But I need to digress. Every foreign worker is a potential hacker, for there is no way to perform a security check on her/him. Many companies use them nevertheless because of the low cost. I know a company that hires North Korean engineers working out of mainland China. They log in for legitimate purposes to American corporate servers. They actually live in North Korea and are forced to back home every 3 weeks. They only have access to dynamic IP addresses, where a PTR record does not exist, thus, no reverse-hostname is possible. As a fact: no dynamic IP address has a corresponding PTR record. The question is how to whitelist a remote worker’s IP automatically. This issue cannot be easily solved since commercial VPNs do not guarantee that the same IP will be offered on the next connection. Many small companies that hire foreign workers end up creating fence servers, but that is exponentially more insecure since now you have a potential hacker sitting comfortably inside your firewall, behind your line of defense. Your network may have access to other companies networks, all the way up to a power station or a government facility, maybe a nuclear facility. A very somber scenario. Since Libwrap is the ultimate defense to keep hackers from controlling your servers, it should ONLY verify if an incoming connection resolves to a domain listed in /etc/hosts.allow. It does not. Prior, it performs a hostname check that invariably fails unless the pair IP address/ domain exists in /etc/hosts, but of course that information changes sometimes hourly. As a result of this problem, you cannot use it as a gatekeeper for remote access from dynamic IP addresses, increasing your level of insecurity. As I said, I explained all these ideas to the author, Wietse, without success. He insisted that using a public key was how you protect servers. I disagree. Without Libwrap, which means IP whitelisting, a simple public key mechanism is suicidal. It is very easy to see why. In a first step, a hacker steals the pair public-private key from a box which has legitimate access to your network. Then he uses the pair in another box located in his country, from which he will access your network as if he were the legitimate client or worker. It happened to me already. Libwrap applied to a domain plus public key will perform infinitely better than a public key alone. In fact, public key alone should not be used at all. This is obvious since by using it, you are delegating your security to the box you are allowing to connect, so your entire network is now as secure as your client or worker’s home network, which you don’t control. You just opened the doors of your company wide-open. What I suggest is to modify Libwrap so a domain listed in /etc/hosts.allow would work for real, just performing a simple DNS
[Touch-packages] [Bug 1839598] Re: tcp_wrappers does not whitelisting of domains, vs IPs
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tcp-wrappers in Ubuntu. https://bugs.launchpad.net/bugs/1839598 Title: tcp_wrappers does not whitelisting of domains, vs IPs Status in tcp-wrappers package in Ubuntu: New Bug description: TCP Wrappers (also known as tcp_wrappers) is a host-based networking ACL system, used to filter network access to Internet Protocol servers. It allows host or subnetwork IP addresses, names and/or ident query replies, to be used as tokens on which to filter for access control purposes. The original code was written by Wietse Venema in 1990 He maintained it until 1995, and on June 1, 2001, released it under its own BSD-style license. The tarball includes a library named Libwrap that implements the actual functionality. I had an email conversation with him that lead to nowhere. He does not agree with my request for a redesign. Very concisely, there is no way as of now to whitelist a domain, vs an IP address. You need to know the IP address to which the domain resolves to beforehand, which makes domain updates impossible to process. This causes tremendous operational problems when the person you need to give access to has an IP address that changes often. But I need to digress. Every foreign worker is a potential hacker, for there is no way to perform a security check on her/him. Many companies use them nevertheless because of the low cost. I know a company that hires North Korean engineers working out of mainland China. They log in for legitimate purposes to American corporate servers. They actually live in North Korea and are forced to back home every 3 weeks. They only have access to dynamic IP addresses, where a PTR record does not exist, thus, no reverse-hostname is possible. As a fact: no dynamic IP address has a corresponding PTR record. The question is how to whitelist a remote worker’s IP automatically. This issue cannot be easily solved since commercial VPNs do not guarantee that the same IP will be offered on the next connection. Many small companies that hire foreign workers end up creating fence servers, but that is exponentially more insecure since now you have a potential hacker sitting comfortably inside your firewall, behind your line of defense. Your network may have access to other companies networks, all the way up to a power station or a government facility, maybe a nuclear facility. A very somber scenario. Since Libwrap is the ultimate defense to keep hackers from controlling your servers, it should ONLY verify if an incoming connection resolves to a domain listed in /etc/hosts.allow. It does not. Prior, it performs a hostname check that invariably fails unless the pair IP address/ domain exists in /etc/hosts, but of course that information changes sometimes hourly. As a result of this problem, you cannot use it as a gatekeeper for remote access from dynamic IP addresses, increasing your level of insecurity. As I said, I explained all these ideas to the author, Wietse, without success. He insisted that using a public key was how you protect servers. I disagree. Without Libwrap, which means IP whitelisting, a simple public key mechanism is suicidal. It is very easy to see why. In a first step, a hacker steals the pair public-private key from a box which has legitimate access to your network. Then he uses the pair in another box located in his country, from which he will access your network as if he were the legitimate client or worker. It happened to me already. Libwrap applied to a domain plus public key will perform infinitely better than a public key alone. In fact, public key alone should not be used at all. This is obvious since by using it, you are delegating your security to the box you are allowing to connect, so your entire network is now as secure as your client or worker’s home network, which you don’t control. You just opened the doors of your company wide-open. What I suggest is to modify Libwrap so a domain listed in /etc/hosts.allow would work for real, just performing a simple DNS lookup to will match the IP address to the domain. Right now, this is impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcp-wrappers/+bug/1839598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openldap/+git/openldap/+merge/371148
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openldap/+git/openldap/+merge/371149
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1838370
Title:
slapd segfault on filter parse error
Status in openldap:
Fix Released
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Disco:
Confirmed
Bug description:
Impact
--
Users willing to use the slapd rwm overlay will face a slapd segmentation
fault
when trying to rewrite some rules. Backporting this fix will allow users using
stable releases to take advantage of this feature without crashing slapd. This
issue was fixed by upstream not freeing the rwm overlay filter memory without
prior checking.
Test Case
-
In this test case, the rwm overlay will be used and a rule will be created to
deny any search request for uid=root, then the 'ldapsearch' will be invoked to
trigger the failure. It is important to mention that the 'ldapsearch' command
should fail regardless the presence of the bug in the package, the target here
is the slapd crash. To reproduce this bug one can follow the procedure below
in
Ubuntu xenial, bionic or disco:
$ sudo apt-get update
$ sudo apt-get install slapd ldap-utils -y
Reconfigure the slapd package. When asked about a domain, use "example.com".
Choose a password you want (or just leave it blank), and accept defaults for
everything else:
$ sudo dpkg-reconfigure slapd
Create a file called 'add-rwm.ldif' with the following content:
$ cat add-rwm.ldif
dn: cn=module{0},cn=config
changetype: modify
add: olcModuleLoad
olcModuleLoad: rwm
dn: olcOverlay=rwm,olcDatabase={1}mdb,cn=config
changetype: add
objectClass: olcOverlayConfig
objectClass: olcRwmConfig
olcOverlay: rwm
olcRwmRewrite: {0} rwm-rewriteEngine "on"
olcRwmRewrite: {1} rwm-rewriteContext "searchFilter"
olcRwmRewrite: {2} rwm-rewriteRule "(.*)(uid=root)(.*)" "$1$2$3" "#"
With this file in place, run:
$ sudo ldapadd -Q -Y EXTERNAL -H ldapi:/// -f add-rwm.ldif
Now, to trigger the crash:
$ ldapsearch -x -h localhost -b dc=example,dc=com -LLL uid=root
Server is unwilling to perform (53)
Additional information: searchFilter/searchFilterAttrDN massage error
slapd process will die, and /var/crash will have a crash file for slapd. You
can run the following command to confirm the error:
$ cat /var/log/syslog | grep filter_free
Aug 9 19:51:05 popular-gorilla slapd[1479]: filter_free: unknown filter
type=28530
Regression Potential
Since the fix is a patch provided by upstream (reviewed by maintainers and us)
simple mistakes like typos are not expected. The patch impacts only the rwm
module which is not loaded by default. So any regression would affect only the
users that make use of this overlay. If an user is not using rwm overlay and
is
facing any issue, it should be related to other problems related to LDAP
directory services.
[Original message]
Hello!
We have faced slapd crash, seems an attacker was trying to brute force one
of our services and uid parsing failures caused slapd crash:
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH
base="ou=test,dc=test,dc=com" scope=2 deref=0
filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid
userPassword uidNumber gidNumber gecos homeDirectory loginShell
krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp
shadowLastChange shadowMin shadow
Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange
krbPasswordExpiration pwdAttribute authorizedService accountExpires
userAccountControl nsAccountLock host loginDisabled loginExpirationTime
loginAllowedTimeMap sshPublic
Key
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0
nentries=0 text=massaged filter parse error
Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip
7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so
[7fc8d1868000+1c]
Another faulty filter example:
filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0"
filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
$ lsb_release -rd
Description: Ubuntu 16.04.5 LTS
Release: 16.04
$ slapd -VVV
@(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $
buildd@lcy01-amd64-019
[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openldap/+git/openldap/+merge/371147
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1838370
Title:
slapd segfault on filter parse error
Status in openldap:
Fix Released
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Disco:
Confirmed
Bug description:
Impact
--
Users willing to use the slapd rwm overlay will face a slapd segmentation
fault
when trying to rewrite some rules. Backporting this fix will allow users using
stable releases to take advantage of this feature without crashing slapd. This
issue was fixed by upstream not freeing the rwm overlay filter memory without
prior checking.
Test Case
-
In this test case, the rwm overlay will be used and a rule will be created to
deny any search request for uid=root, then the 'ldapsearch' will be invoked to
trigger the failure. It is important to mention that the 'ldapsearch' command
should fail regardless the presence of the bug in the package, the target here
is the slapd crash. To reproduce this bug one can follow the procedure below
in
Ubuntu xenial, bionic or disco:
$ sudo apt-get update
$ sudo apt-get install slapd ldap-utils -y
Reconfigure the slapd package. When asked about a domain, use "example.com".
Choose a password you want (or just leave it blank), and accept defaults for
everything else:
$ sudo dpkg-reconfigure slapd
Create a file called 'add-rwm.ldif' with the following content:
$ cat add-rwm.ldif
dn: cn=module{0},cn=config
changetype: modify
add: olcModuleLoad
olcModuleLoad: rwm
dn: olcOverlay=rwm,olcDatabase={1}mdb,cn=config
changetype: add
objectClass: olcOverlayConfig
objectClass: olcRwmConfig
olcOverlay: rwm
olcRwmRewrite: {0} rwm-rewriteEngine "on"
olcRwmRewrite: {1} rwm-rewriteContext "searchFilter"
olcRwmRewrite: {2} rwm-rewriteRule "(.*)(uid=root)(.*)" "$1$2$3" "#"
With this file in place, run:
$ sudo ldapadd -Q -Y EXTERNAL -H ldapi:/// -f add-rwm.ldif
Now, to trigger the crash:
$ ldapsearch -x -h localhost -b dc=example,dc=com -LLL uid=root
Server is unwilling to perform (53)
Additional information: searchFilter/searchFilterAttrDN massage error
slapd process will die, and /var/crash will have a crash file for slapd. You
can run the following command to confirm the error:
$ cat /var/log/syslog | grep filter_free
Aug 9 19:51:05 popular-gorilla slapd[1479]: filter_free: unknown filter
type=28530
Regression Potential
Since the fix is a patch provided by upstream (reviewed by maintainers and us)
simple mistakes like typos are not expected. The patch impacts only the rwm
module which is not loaded by default. So any regression would affect only the
users that make use of this overlay. If an user is not using rwm overlay and
is
facing any issue, it should be related to other problems related to LDAP
directory services.
[Original message]
Hello!
We have faced slapd crash, seems an attacker was trying to brute force one
of our services and uid parsing failures caused slapd crash:
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH
base="ou=test,dc=test,dc=com" scope=2 deref=0
filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid
userPassword uidNumber gidNumber gecos homeDirectory loginShell
krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp
shadowLastChange shadowMin shadow
Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange
krbPasswordExpiration pwdAttribute authorizedService accountExpires
userAccountControl nsAccountLock host loginDisabled loginExpirationTime
loginAllowedTimeMap sshPublic
Key
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0
nentries=0 text=massaged filter parse error
Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip
7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so
[7fc8d1868000+1c]
Another faulty filter example:
filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0"
filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
$ lsb_release -rd
Description: Ubuntu 16.04.5 LTS
Release: 16.04
$ slapd -VVV
@(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $
buildd@lcy01-amd64-019
:/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd
Included static backends:
config
ldif
$ apt-cache policy slapd
slapd:
[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error
** Description changed:
+ Impact
+ --
+
+ Users willing to use the slapd rwm overlay will face a slapd segmentation
fault
+ when trying to rewrite some rules. Backporting this fix will allow users using
+ stable releases to take advantage of this feature without crashing slapd. This
+ issue was fixed by upstream not freeing the rwm overlay filter memory without
+ prior checking.
+
+ Test Case
+ -
+
+ In this test case, the rwm overlay will be used and a rule will be created to
+ deny any search request for uid=root, then the 'ldapsearch' will be invoked to
+ trigger the failure. It is important to mention that the 'ldapsearch' command
+ should fail regardless the presence of the bug in the package, the target here
+ is the slapd crash. To reproduce this bug one can follow the procedure below
in
+ Ubuntu xenial, bionic or disco:
+
+ $ sudo apt-get update
+ $ sudo apt-get install slapd ldap-utils -y
+
+ Reconfigure the slapd package. When asked about a domain, use "example.com".
+ Choose a password you want (or just leave it blank), and accept defaults for
+ everything else:
+
+ $ sudo dpkg-reconfigure slapd
+
+ Create a file called 'add-rwm.ldif' with the following content:
+
+ $ cat add-rwm.ldif
+ dn: cn=module{0},cn=config
+ changetype: modify
+ add: olcModuleLoad
+ olcModuleLoad: rwm
+
+ dn: olcOverlay=rwm,olcDatabase={1}mdb,cn=config
+ changetype: add
+ objectClass: olcOverlayConfig
+ objectClass: olcRwmConfig
+ olcOverlay: rwm
+ olcRwmRewrite: {0} rwm-rewriteEngine "on"
+ olcRwmRewrite: {1} rwm-rewriteContext "searchFilter"
+ olcRwmRewrite: {2} rwm-rewriteRule "(.*)(uid=root)(.*)" "$1$2$3" "#"
+
+
+ With this file in place, run:
+
+ $ sudo ldapadd -Q -Y EXTERNAL -H ldapi:/// -f add-rwm.ldif
+
+ Now, to trigger the crash:
+
+ $ ldapsearch -x -h localhost -b dc=example,dc=com -LLL uid=root
+ Server is unwilling to perform (53)
+ Additional information: searchFilter/searchFilterAttrDN massage error
+
+
+ slapd process will die, and /var/crash will have a crash file for slapd. You
+ can run the following command to confirm the error:
+
+ $ cat /var/log/syslog | grep filter_free
+ Aug 9 19:51:05 popular-gorilla slapd[1479]: filter_free: unknown filter
type=28530
+
+
+ Regression Potential
+
+
+ Since the fix is a patch provided by upstream (reviewed by maintainers and us)
+ simple mistakes like typos are not expected. The patch impacts only the rwm
+ module which is not loaded by default. So any regression would affect only the
+ users that make use of this overlay. If an user is not using rwm overlay and
is
+ facing any issue, it should be related to other problems related to LDAP
+ directory services.
+
+
+
+ [Original message]
+
Hello!
We have faced slapd crash, seems an attacker was trying to brute force one
of our services and uid parsing failures caused slapd crash:
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH
base="ou=test,dc=test,dc=com" scope=2 deref=0
filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid
userPassword uidNumber gidNumber gecos homeDirectory loginShell
krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp
shadowLastChange shadowMin shadow
Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange
krbPasswordExpiration pwdAttribute authorizedService accountExpires
userAccountControl nsAccountLock host loginDisabled loginExpirationTime
loginAllowedTimeMap sshPublic
Key
Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0
nentries=0 text=massaged filter parse error
Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip
7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so
[7fc8d1868000+1c]
Another faulty filter example:
filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0"
filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
$ lsb_release -rd
Description: Ubuntu 16.04.5 LTS
Release: 16.04
$ slapd -VVV
@(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $
buildd@lcy01-amd64-019
:/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd
Included static backends:
- config
- ldif
+ config
+ ldif
$ apt-cache policy slapd
slapd:
- Installed: 2.4.42+dfsg-2ubuntu3.3
- Candidate: 2.4.42+dfsg-2ubuntu3.5
- Version table:
- 2.4.42+dfsg-2ubuntu3.5 500
- 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
+ Installed: 2.4.42+dfsg-2ubuntu3.3
+ Candidate: 2.4.42+dfsg-2ubuntu3.5
+ Version table:
+ 2.4.42+dfsg-2ubuntu3.5 500
+ 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
- *** 2.4.42+dfsg-2ubuntu3.3 100
- 100 /var/lib/dpkg/status
- 2.4.42+dfsg-2ubuntu3.2 500
- 500
[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath
[VERIFICATION DISCO] I have installed the disco-proposed 'procps' package and was able to conclude that it fixes the situation based on the reproducer suggested upstream: $ vi $(seq 1 1250| paste -s -d'_')_foo.txt # Creating a process containing > 4096 chars, to be precise 5158 chars) $ pgrep -af 'foo.txt' 1148 vi
[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath
[VERIFICATION BIONIC] I have installed the bionic-proposed 'procps' package and was able to conclude that it fixes the situation based on the reproducer suggested upstream: $ vi $(seq 1 1250| paste -s -d'_')_foo.txt # Creating a process containing > 4096 chars, to be precise 5158 chars) $ pgrep -af 'foo.txt' 1148 vi
[Touch-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
** Changed in: openssh (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian machines Status in seahorse: Fix Released Status in gnome-keyring package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Bug description: on hardy (preserved home folder from feisty) i get the following when i try to ssh Agent admitted failure to sign using the key. Permission denied (publickey). or with verbose on sam@titania:~$ ssh -v oberon OpenSSH_4.7p1 Debian-4ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/sam/.ssh/config debug1: Applying options for oberon debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ## [##] port ##. debug1: Connection established. debug1: identity file /home/sam/.ssh/identity type -1 debug1: identity file /home/sam/.ssh/id_rsa type 1 debug1: identity file /home/sam/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6p1 Debian-5ubuntu0.1 debug1: match: OpenSSH_4.6p1 Debian-5ubuntu0.1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-4ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: using hostkeyalias: oberon debug1: Host 'oberon' is known and matches the RSA host key. debug1: Found key in /home/sam/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/sam/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 Agent admitted failure to sign using the key. debug1: Trying private key: /home/sam/.ssh/identity debug1: Trying private key: /home/sam/.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey). I tried generating a new key. this worked for a few logons, but then i get back to this error. I think it is to do with the local key agent. i found that SSH_AUTH_SOCK=0 ssh oberon works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath
Hello Pedro, or anyone else affected, Accepted procps into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/procps/2:3.3.12-3ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: procps (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1839329 Title: pgrep: allows long command lines to be searched e.g. java process with long classpath Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: In Progress Status in procps source package in Bionic: Fix Committed Status in procps source package in Disco: Fix Committed Bug description: [Impact] The pgrep -f and pkill -f commands are unable to find processes strings in processes which are beyond the 4096th character. This often happens with Java command lines with long classpaths on the command line. [Test Case] A quick test to reproduce this is to vi a file using a filename over 4k $ vi $(seq 1 1250| paste -s -d'_')_foo.txt) and leave vi running then run from another terminal $ pgrep -af 'foo.txt' to find it. Without the fix, one will only see the first 4096 chars, while the expected behaviour would be: $ pgrep -af 'foo.txt' 27667 vi
[Touch-packages] [Bug 1839329] Please test proposed package
Hello Pedro, or anyone else affected, Accepted procps into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/procps/2:3.3.15-2ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1839329 Title: pgrep: allows long command lines to be searched e.g. java process with long classpath Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: In Progress Status in procps source package in Bionic: Fix Committed Status in procps source package in Disco: Fix Committed Bug description: [Impact] The pgrep -f and pkill -f commands are unable to find processes strings in processes which are beyond the 4096th character. This often happens with Java command lines with long classpaths on the command line. [Test Case] A quick test to reproduce this is to vi a file using a filename over 4k $ vi $(seq 1 1250| paste -s -d'_')_foo.txt) and leave vi running then run from another terminal $ pgrep -af 'foo.txt' to find it. Without the fix, one will only see the first 4096 chars, while the expected behaviour would be: $ pgrep -af 'foo.txt' 27667 vi
[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath
Ok, change seems to be trivial enough to accept even without getting this merged upstream (most important is that there was no disagreement so far from the maintainers). I also don't expect anything to go bad since the constant bump is not too big anyway. ** Changed in: procps (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1839329 Title: pgrep: allows long command lines to be searched e.g. java process with long classpath Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: In Progress Status in procps source package in Bionic: Fix Committed Status in procps source package in Disco: Fix Committed Bug description: [Impact] The pgrep -f and pkill -f commands are unable to find processes strings in processes which are beyond the 4096th character. This often happens with Java command lines with long classpaths on the command line. [Test Case] A quick test to reproduce this is to vi a file using a filename over 4k $ vi $(seq 1 1250| paste -s -d'_')_foo.txt) and leave vi running then run from another terminal $ pgrep -af 'foo.txt' to find it. Without the fix, one will only see the first 4096 chars, while the expected behaviour would be: $ pgrep -af 'foo.txt' 27667 vi
[Touch-packages] [Bug 1839637] [NEW] Display driver missing
Public bug reported: After system update and reboot, system stay on the purple screen for long time.Then after going to advanced mode and from recovery option, I run check for broken packages. After completion system was restarted on normal mode and found the display driver missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 20:58:18 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2019-08-05 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G41M-Combo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1839637 Title: Display driver missing Status in xorg package in Ubuntu: New Bug description: After system update and reboot, system stay on the purple screen for long time.Then after going to advanced mode and from recovery option, I run check for broken packages. After completion system was restarted on normal mode and found the display driver missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 20:58:18 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2019-08-05 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G41M-Combo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A
[Touch-packages] [Bug 1839329] Re: pgrep: allows long command lines to be searched e.g. java process with long classpath
This bug was fixed in the package procps - 2:3.3.15-2ubuntu3 --- procps (2:3.3.15-2ubuntu3) eoan; urgency=medium * d/p/pgrep-increase-CMDSTRSIZE.patch: - Allows long command lines to be searched. eg: Java process with a long classpath. (LP: #1839329) -- Eric Desrochers Thu, 08 Aug 2019 16:46:48 + ** Changed in: procps (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1839329 Title: pgrep: allows long command lines to be searched e.g. java process with long classpath Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: In Progress Status in procps source package in Bionic: In Progress Status in procps source package in Disco: In Progress Bug description: [Impact] The pgrep -f and pkill -f commands are unable to find processes strings in processes which are beyond the 4096th character. This often happens with Java command lines with long classpaths on the command line. [Test Case] A quick test to reproduce this is to vi a file using a filename over 4k $ vi $(seq 1 1250| paste -s -d'_')_foo.txt) and leave vi running then run from another terminal $ pgrep -af 'foo.txt' to find it. Without the fix, one will only see the first 4096 chars, while the expected behaviour would be: $ pgrep -af 'foo.txt' 27667 vi
[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
@Hui Wang Thanks, here is my new alsa-info.txt. Unfortunately, my internal mic still doesn't work. ** Attachment added: "alsa-info.txt.69pNmVM83Q" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5281774/+files/alsa-info.txt.69pNmVM83Q -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839603] Re: Wifi breaks and needs restart after Laptop's wake up
You say "But I'm getting tired of this after years of doing it.". Does this mean that you are suffering this bug already with older versions of Ubuntu? Yes, that is correct. It is happening for 2 years now, if I'm not mistaken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1839603 Title: Wifi breaks and needs restart after Laptop's wake up Status in network-manager package in Ubuntu: Incomplete Bug description: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. What works: It seems a simple Wifi turn off and turn on is sufficient, for the bug to go away. But I'm getting tired of this after years of doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839603] Re: Wifi breaks and needs restart after Laptop's wake up
/var/log/syslog seems to contain debug information of network-manager, although I was not successful: With this command: sudo /usr/lib/NetworkManager/debug-helper.py --nm debug I followed these instructions: https://wiki.ubuntu.com/DebuggingNetworkManager#Getting_NetworkManager_debug_logs debug-helper.py seems to not exist on my system: vaidas@vaidas-SATELLITE-L855:/$ sudo /usr/lib/NetworkManager/debug-helper.py --nm debug sudo: /usr/lib/NetworkManager/debug-helper.py: command not found Here can be seen that debug-helper.py does not exist: vaidas@vaidas-SATELLITE-L855:/usr/lib/NetworkManager$ ls conf.d nm-initrd-generatornm-pptp-auth-dialog nm-dhcp-helper nm-openvpn-auth-dialog nm-pptp-service nm-dispatchernm-openvpn-service VPN nm-iface-helper nm-openvpn-service-openvpn-helper ** Attachment added: "NetworkManager debug logs (/var/log/syslog)" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+attachment/5281773/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1839603 Title: Wifi breaks and needs restart after Laptop's wake up Status in network-manager package in Ubuntu: Incomplete Bug description: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. What works: It seems a simple Wifi turn off and turn on is sufficient, for the bug to go away. But I'm getting tired of this after years of doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839603] Re: Wifi breaks and needs restart after Laptop's wake up
Please have a look at https://wiki.ubuntu.com/DebuggingNetworkManager and supply us with debug logs of NetworkManager and wpasupplicant, You say "But I'm getting tired of this after years of doing it.". Does this mean that you are suffering this bug already with older versions of Ubuntu? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1839603 Title: Wifi breaks and needs restart after Laptop's wake up Status in network-manager package in Ubuntu: Incomplete Bug description: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. What works: It seems a simple Wifi turn off and turn on is sufficient, for the bug to go away. But I'm getting tired of this after years of doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839603] Re: Wifi breaks and needs restart after Laptop's wake up
** Description changed: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. - - Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. + Breaking of Wifi after computer wake up starts to appear, on average, + after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. + + What works: It seems a simple Wifi turn off and turn on is sufficient, + for the bug to go away. But I'm getting tired of this after years of + doing it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1839603 Title: Wifi breaks and needs restart after Laptop's wake up Status in network-manager package in Ubuntu: New Bug description: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. What works: It seems a simple Wifi turn off and turn on is sufficient, for the bug to go away. But I'm getting tired of this after years of doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577347] Re: [Inspiron 13-7359, Conexant CX20722, Black Headphone Out, Left] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1577347 Title: [Inspiron 13-7359, Conexant CX20722, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: headset output not working audio device not properly detected have not tested input ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dj 1665 F pulseaudio CurrentDesktop: GNOME Date: Mon May 2 11:50:40 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-17 (136 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dj 1665 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Inspiron 13-7359, Conexant CX20722, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0TDTV6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0TDTV6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1577347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569760] Re: bacground noise from headphones
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1569760 Title: bacground noise from headphones Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have an annoying quiet noise in my headphones. It is low, so one hears it only when there is no sound. The noise is significantly decreased after applying with the HDA Analyzer the following patch: iff for codec 0/0 (0x10ec0280): --- +++ @@ -92,17 +92,17 @@ Control: name="Beep Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=1, idx=4, ofs=0 Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 5 0x18 0x19 0x1a 0x1b 0x1d Node 0x0c [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 - Amp-In vals: [0x00 0x00] [0x00 0x00] + Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x02 0x0b Node 0x0d [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] Connection: 2 0x03 0x0b Node 0x0e [Vendor Defined Widget] wcaps 0xf0: Mon I still can hear very low noise. In order to get rid of this one, I have to apply: Diff for codec 0/0 (0x10ec0280): --- +++ @@ -147,17 +147,17 @@ Unsolicited: tag=0x00, enabled=0 Power: setting=D3, actual=D3 Connection: 2 0x0c 0x0d* Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name="Headphone Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=1, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 - Amp-Out vals: [0x00 0x00] + Amp-Out vals: [0x80 0x80] Pincap 0x0001001c: OUT HP EAPD Detect EAPD 0x2: EAPD Pin Default 0x0421101f: [Jack] HP Out at Ext Right Conn = 1/8, Color = Black DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP Unsolicited: tag=0x01, enabled=1 Power: setting=D0, actual=D But then I don't have sound at all. I presume, with the last patch I basically switch of the headphones output completely. I think, it would be a good idea to add the 'HP ZBook' model to the SND-HDA-INTEL driver so it could automatically apply the above settings. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: openafs fglrx ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: afiergol 2766 F pulseaudio afiergol 3717 F alsamixer /dev/snd/controlC1: afiergol 2766 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 13 10:24:44 2016 InstallationDate: Installed on 2015-04-02 (376 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.14 dmi.board.name: 2253 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.14:bd01/26/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1569760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan
** Tags added: sru-20190722 ubuntu-qrt-apparmor ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1834192 Title: apparmor mult_mount regression test fails in eoan Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: Confirmed Bug description: In running adt testing on 5.2-based kernels for eoan, I'm seeing failures from the apparmor mult_mount regression test. Running the test case manually with -x yields: + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20 + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3 ++ error_handler ++ fatalerror 'Unexpected shell error. Run with -x to debug' Running the following manually in a shell also fails in eoan with the 5.0 kernel copied forward from disco, while it passes in disco: $ uname -a Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dd if=/dev/zero of=test.img bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s $ mkfs.ext2 -F -m 0 -N 10 test.img mke2fs 1.45.2 (27-May-2019) test.img: Not enough space to build proposed filesystem while setting up superblock So this seems likely to be due to some change with mke2fs; not sure if this is a regression there or if the test was getting away with doing something invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839603] [NEW] Wifi breaks and needs restart after Laptop's wake up
Public bug reported: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. What works: It seems a simple Wifi turn off and turn on is sufficient, for the bug to go away. But I'm getting tired of this after years of doing it. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1839603 Title: Wifi breaks and needs restart after Laptop's wake up Status in network-manager package in Ubuntu: New Bug description: This is constant struggle for me, it seems that in the initial days after installation of Ubuntu 19.10 this problem of Wifi stopping to work after wake up does not happen. I'm sure, I reinstalled Ubuntu many times, the issue still persist. Breaking of Wifi after computer wake up starts to appear, on average, after a week of computer usage. On my laptop, this Wifi problem existed in the previous Ubuntu versions as well. What works: It seems a simple Wifi turn off and turn on is sufficient, for the bug to go away. But I'm getting tired of this after years of doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568827] Re: [Q551LN, Realtek ALC3236, Mic, Internal] becomes noise after resume
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1568827 Title: [Q551LN, Realtek ALC3236, Mic, Internal] becomes noise after resume Status in alsa-driver package in Ubuntu: Won't Fix Bug description: After I resume my Asus Q551LN laptop the internal microphone becomes terribly noisy. Killing pulseaudio doesn't help. Only return to normal after reboot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abarto 1673 F pulseaudio /dev/snd/controlC0: abarto 1673 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 11 09:08:44 2016 InstallationDate: Installed on 2016-04-09 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [Q551LN, Realtek ALC3236, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q551LN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q551LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ551LN.204:bd07/31/2014:svnASUSTeKCOMPUTERINC.:pnQ551LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ551LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: Q551LN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605388] Re: [USB-Audio - USB Audio DAC, playback] Crackling sound with no original audio from playback in Chrome
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1605388 Title: [USB-Audio - USB Audio DAC, playback] Crackling sound with no original audio from playback in Chrome Status in alsa-driver package in Ubuntu: Won't Fix Bug description: When I begin playback in Chrome while using Pulseaudio, I get only cracking noises in my headphones, no original audio. Playback works correctly with e.g. aplay, mplayer, Firefox's plugin-container for Flash. If I unplug and replug the device several times, it will start working. If I disable Pulseaudio and use the ALSA hardware device directly (set the default in ~/.asoundrc; stop pulseaudio from starting; restart Chrome) then I do not experience this bug. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Thu Jul 21 16:15:32 2016 InstallationDate: Installed on 2014-03-12 (862 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DAC successful Symptom_Card: PCM2706 Audio Codec - USB Audio DAC Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - USB Audio DAC, playback] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to wily on 2016-02-19 (152 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.06 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.06:bd10/25/2013:svnHewlett-Packard:pnHPZBook15:pvrA3009DC10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.47:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DC10203 dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-04-21T14:56:58.460438 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1605388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577654] Re: PCI/internal sound card not detected E7470
** Tags removed: wily ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1577654 Title: PCI/internal sound card not detected E7470 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound card not detected with Dell E7470. Tried all different tips found on ubuntu doc and various forums without any success. Regards ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.4.6-040406-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue May 3 15:14:14 2016 InstallationDate: Installed on 2016-04-14 (18 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0VNKRJ dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0VNKRJ:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1577654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666216] Re: [VGN-CS25GN_B, Realtek ALC262, Speaker, Internal] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1666216 Title: [VGN-CS25GN_B, Realtek ALC262, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I am using Xubuntu 15.10, it was playing sound before. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xfreeuser 1058 F pulseaudio CurrentDesktop: XFCE Date: Mon Feb 20 21:20:09 2017 InstallationDate: Installed on 2016-06-09 (255 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xfreeuser 1058 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [VGN-CS25GN_B, Realtek ALC262, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2008 dmi.bios.vendor: INSYDE dmi.bios.version: R1080Q2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR1080Q2:bd11/17/2008:svnSonyCorporation:pnVGN-CS25GN_B:pvrC1031B8C:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-CS25GN_B dmi.product.version: C1031B8C dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577349] Re: [Inspiron 13-7359, Conexant CX20722, Black Headphone Out, Left] No automute
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1577349 Title: [Inspiron 13-7359, Conexant CX20722, Black Headphone Out, Left] No automute Status in alsa-driver package in Ubuntu: Won't Fix Bug description: this was after switching headphones with microphone in hdajackretask. before it did nothing. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dj 1665 F pulseaudio CurrentDesktop: GNOME Date: Mon May 2 11:56:10 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-17 (136 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: No auto-mute between outputs Title: [Inspiron 13-7359, Conexant CX20722, Black Headphone Out, Left] No automute UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0TDTV6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0TDTV6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1577349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508092] Re: [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from speakers, only headphones
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1508092 Title: [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from speakers, only headphones Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Sound comes out of the headphones when I insert the jack, but does NOT come out of the speakers when I unplug it. This includes sound from any source, including aplay. This is a newly installed Lubuntu daily build (Lubuntu 15.10 "Wily Werewolf" - Alpha i386 20151017.1). If I go back to running from the Live USB install media, the sound works fine from the speakers OR the headphones, as expected. As suggested by https://help.ubuntu.com/community/SoundTroubleshootingProcedure I have tried: * killing and reloading pulseaudio and alsa-mixer * purging (.config/) .pulse/ then killing/reloading and rebooting * installing and reinstalling pavucontrol linux-sound-base alsa-base alsa-utils libasound2 In the installed version I notice that in Volume Control (pavucontrol) the output switches automatically between headphones and speaker when the jack is plugged and unplugged - as one would expect - and in alsamixer I can see the inactive device being muted automatically. However the speaker never issues any sound :( On the contrary in the live usb I notice that alsamixer leaves both outputs active (unmuted) and simply relies on the microswitch in the headphone jack to control whether the speaker can be heard or not. For reference I past the output of the FAILING test case's alsa- info.sh below and attach the output of the WORKING test case's alsa- info.sh ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: elda 1480 F...m pulseaudio /dev/snd/pcmC0D0p: elda 1480 F...m pulseaudio /dev/snd/controlC0: elda 1480 F pulseaudio CurrentDesktop: LXDE Date: Tue Oct 20 16:36:58 2015 InstallationDate: Installed on 2015-10-19 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20151017.1) JournalErrors: No journal files were found. -- No entries -- PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1011PX:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1011PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491999] Re: [P750ZM-G, Realtek ALC892, Black SPDIF Out, Rear] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1491999 Title: [P750ZM-G, Realtek ALC892, Black SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I had sound before I upgraded from 15.04 to 15.10. It detects that the headphones are plugged in, but no sound at all. Speaker works. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mariogrip 25319 F pulseaudio /dev/snd/controlC0: mariogrip 25319 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 21:02:13 2015 InstallationDate: Installed on 2015-09-03 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mariogrip 25319 F pulseaudio /dev/snd/controlC0: mariogrip 25319 F pulseaudio Symptom_Jack: Black SPDIF Out, Rear Symptom_Type: No sound at all Title: [P750ZM-G, Realtek ALC892, Black SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to wily on 2015-09-03 (0 days ago) dmi.bios.date: 03/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.02 dmi.board.asset.tag: Tag 12345 dmi.board.name: P750ZM-G dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.02:bd03/31/2015:svnNotebook:pnP750ZM-G:pvrNotApplicable:rvnNotebook:rnP750ZM-G:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: P750ZM-G dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1491999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 707540] Re: Destroying pkgCacheFile releases system lock
*** This bug is a duplicate of bug 1794053 *** https://bugs.launchpad.net/bugs/1794053 I fixed this in 1.7.0, but forgot about this bug and tracked it in bug 1794053, so marking this as a duplicate. ** Changed in: apt (Ubuntu) Status: Triaged => Fix Released ** This bug has been marked a duplicate of bug 1794053 pkgCacheFile unlocks in destructor even if it did not acquire lock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/707540 Title: Destroying pkgCacheFile releases system lock Status in apt package in Ubuntu: Fix Released Bug description: Binary package hint: python-apt This code should work, but doesn't: >>> import apt_pkg >>> apt_pkg.init() >>> with apt_pkg.SystemLock(): ... x = apt_pkg.Cache() ... del x Reading package lists... Done Building dependency tree Reading state information... Done Traceback (most recent call last): File "", line 3, in SystemError: E:Not locked (lines beginning with ... should be indented, but Launchpad collapses multiple spaces into one when not at the beginning of the line) Architecture: amd64 apt 0.8.10ubuntu1 python-apt 0.7.100.1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/707540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509703] Re: [Latitude E5440, Realtek ALC3226] Loud, single crackle sound when the login screen appears or resuming from suspend
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1509703 Title: [Latitude E5440, Realtek ALC3226] Loud, single crackle sound when the login screen appears or resuming from suspend Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I hear a loud crackling sound whenever the login screen appears. There is also a crackling sound when the notebook wakes from suspend and an attempt is made to play any sort of audio. This system was upgrade from 15.04 to 15.10 using the system updater. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriel2192 F pulseaudio /dev/snd/controlC1: gabriel2192 F pulseaudio CurrentDesktop: Unity Date: Sat Oct 24 21:06:40 2015 InstallationDate: Installed on 2014-09-19 (400 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E5440, Realtek ALC3226, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to wily on 2015-10-24 (0 days ago) dmi.bios.date: 09/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0WV8K7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd09/02/2015:svnDellInc.:pnLatitudeE5440:pvr00:rvnDellInc.:rn0WV8K7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1509703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504421] Re: seeking in VLC causes sound to become stuttered for a second
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1504421 Title: seeking in VLC causes sound to become stuttered for a second Status in alsa-driver package in Ubuntu: Won't Fix Bug description: The following appears in dmesg when VLC is seeked: [ 42.513156] nouveau E[ VBIOS][:01:00.0] 0x6331[0]: script needs connector type [ 47.863625] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95) [ 47.863737] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM [ 47.863741] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95) [ 211.826483] nouveau E[ VBIOS][:01:00.0] 0x6331[0]: script needs connector type [ 217.275250] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95) [ 217.275467] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM [ 217.275476] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95) [ 4915.101490] nouveau E[ VBIOS][:01:00.0] 0x6331[0]: script needs connector type [ 4920.244628] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95) [ 4920.244841] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM [ 4920.244850] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vyzivus2451 F...m pulseaudio /dev/snd/controlC0: vyzivus2451 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 9 09:32:07 2015 InstallationDate: Installed on 2014-03-07 (580 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to wily on 2015-10-08 (0 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 029M77 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1504421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516361] Re: [N551JK, Realtek ALC668, Speaker, Internal] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1516361 Title: [N551JK, Realtek ALC668, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: After updating to ubuntu gnome 15.10 I cound't hear any sound. I solved editing speech-dispatcher file: sudo gedit /etc/default/speech-dispatcher changing RUN=yes to RUN=no ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: stefano1614 F...m pulseaudio /dev/snd/controlC1: stefano1614 F pulseaudio /dev/snd/controlC0: stefano1614 F pulseaudio CurrentDesktop: GNOME Date: Sun Nov 15 11:13:56 2015 InstallationDate: Installed on 2015-06-13 (154 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [N551JK, Realtek ALC668, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to wily on 2015-11-14 (0 days ago) dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N551JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1516361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1527205] Re: no sound card detected on Dell Latitude e6400 and Ubuntu 15.10
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1527205 Title: no sound card detected on Dell Latitude e6400 and Ubuntu 15.10 Status in alsa-driver package in Ubuntu: Won't Fix Bug description: When I installed Ubuntu 15.04 the sound was working OK. Then, it was working at a set sound level but I could not mute or turn it up/down. Then, no sound at all and no sound card detected. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Dec 17 12:36:11 2015 InstallationDate: Installed on 2015-08-04 (134 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to wily on 2015-12-17 (0 days ago) dmi.bios.date: 05/06/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 0U695R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd05/06/2010:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-10-06T23:14:05.224786 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1527205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1524215] Re: Lenovo B50-70 inverted internal microphone
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete ** Tags removed: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1524215 Title: Lenovo B50-70 inverted internal microphone Status in alsa-driver package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 Attached the alsa-info txt to this bug --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marian 1981 F pulseaudio /dev/snd/pcmC1D0c: marian 1981 F...m pulseaudio /dev/snd/pcmC1D0p: marian 1981 F...m pulseaudio /dev/snd/controlC1: marian 1981 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63 InstallationDate: Installed on 2015-09-10 (90 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20384 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9DCN34WW(V3.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo B50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B50-70 dmi.modalias: dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70: dmi.product.name: 20384 dmi.product.version: Lenovo B50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1524215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1533343] Re: No sound from internal speakers after boot with connected headphones
** Tags removed: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1533343 Title: No sound from internal speakers after boot with connected headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: On Lenovo L450 laptop, when I boot the PC with headphones attached, then the sound via headphones will work, but there will be no sound from internal speakers when headphones are detached. I tested this couple of times and the problem is always reproduced. This is the procedure A: 1. When the problem is not present, sound is present in laptop's speakers, connect the headphones 2. initiate reboot 3. once booted, initiate playing of some audio and check the sound from headphones - it will work OK 4. disconnect the headphones - there is no sound from internal speakers Procedure B: 1. turn off the laptop (power off) 2. connect the headphones to the laptop 3. power on the laptop and boot into Ubuntu 15.10 4. once booted, initiate playing of some audio and check the sound from headphones - it will work OK 5. disconnect the headphones - there is no sound from internal speakers ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ygzo 2125 F pulseaudio /dev/snd/controlC0: ygzo 2125 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 12 20:44:49 2016 InstallationDate: Installed on 2015-10-05 (99 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [20DT0003XS, Realtek ALC3232, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to wily on 2015-11-03 (70 days ago) dmi.bios.date: 08/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JDET54WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DT0003XS dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1533343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540952] Re: speech-dispatcher causes audio corruption (maybe overdrive?) to [Nvidia GPU 40 HDMI/DP, Digital Out, HDMI]
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1540952 Title: speech-dispatcher causes audio corruption (maybe overdrive?) to [Nvidia GPU 40 HDMI/DP, Digital Out, HDMI] Status in alsa-driver package in Ubuntu: Won't Fix Bug description: On first session launch, audio will be corrupt and anything played will result in garbage. If I however remove all 4 speech-dispatcher processes which appear in sound preferences, audio returns to normal and is fine for the remaining session. Brand new upgrade to Ubuntu 15.10, no custom packages, but this was happening in 15.04 as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2063 F pulseaudio /dev/snd/controlC2: john 2063 F pulseaudio /dev/snd/controlC0: john 2063 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity Date: Tue Feb 2 14:42:23 2016 InstallationDate: Installed on 2015-06-05 (241 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia successful Symptom_Card: GK104 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To Be Filled By O.E.M., Nvidia GPU 40 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: Upgraded to wily on 2016-02-02 (0 days ago) dmi.bios.date: 04/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A76ML-K 30 dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd04/02/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnA76ML-K30:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1540952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526569] Re: [USB-Audio - USBStreamer, playback] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1526569 Title: [USB-Audio - USBStreamer, playback] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: USBStreamer worked fine the first time I connected it to my Bodhi Linux computer 8 channels in, 8 channels out connected to a Yamaha 03d with the adat expansion card. Next day I tried again and nothing no input, no output. Alsamixer only recognize TWO controls: master playback and master capture, unmute master and check on capture did nothing. I decided to test with a windows computer and USBStreamer B works perfect so I did a fresh Ubuntu Mate 15.10 installation to my computer. Once I finished to install everything (JACK, etc) I plugged the USBStreamer B to the computer and It worked perfect 8 channels IN 8 channels OUT.. But next day the same thing NO SOUND IN-NO SOUND OUT. But now I unmuted alsamixer Master PLAY and checked CAPTURE and only got CAPTURE, NO PLAY. If I plug the USBStreamer B for the first time it works perfect, but after that It doesn't.. Description: Ubuntu 15.10 Release: 15.10 alsa-base : 1.0.25+dfsg-0ubuntu5 (wily) alsa-utils : 1.0.29-0ubuntu1 (wily) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-19.23-lowlatency 4.2.6 Uname: Linux 4.2.0-19-lowlatency x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vonsai 1754 F pulseaudio /dev/snd/controlC0: vonsai 1754 F pulseaudio CurrentDesktop: MATE Date: Tue Dec 15 17:31:04 2015 InstallationDate: Installed on 2015-12-14 (1 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USBStreamer failed Symptom_Card: USB-Audio - USB2.0-MIDI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vonsai 1754 F pulseaudio /dev/snd/controlC0: vonsai 1754 F pulseaudio Symptom_Type: No sound at all Title: [USB-Audio - USBStreamer, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XI AC (MS-7913) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.6:bd12/12/2014:svnMSI:pnMS-7913:pvr1.0:rvnMSI:rnA88XIAC(MS-7913):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7913 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1526569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1534434] Re: [20BVCTO1WW, Realtek ALC3232, Black Headphone Out, Right] Underruns, dropouts or crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1534434 Title: [20BVCTO1WW, Realtek ALC3232, Black Headphone Out, Right] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Hello, i'm currently having the same issue on a Thinkpad T450, with Ubuntu 15.10 and 15.04 I connect my headphones to the headphone jack, when i connect the headphone jack in the headphone port, i get the same cracking, popping sound as startup and shutdown/reboot. So, when i boot, i get a cracking, popping sound that overpowers the headphones, it still occurs when i shutdown the laptop or reboot. The output of alsa-info.sh gives me a different codec instead of the proposed fix information 0x10ec0292 0x17aa5036 0 i have 0x10ec0292 0x17aa5034 0 I tried the fix with both 0x17aa5036 and 0x17aa5034, on Ubuntu 15.10 and 15.04 without luck, the symptom stays, the cracking sound appears at startup and shutdown. I tried fedora 23 and i still have the issue. Probably caused by the same issue, i get a static noise in the both headphones if i mute it goes away Thanks for your help. Almost similar issue as specified here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502155 Detailed info : Description: Ubuntu 15.10 Release: 15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: madmantm 1370 F pulseaudio madmantm 1916 F alsamixer /dev/snd/controlC0: madmantm 1370 F pulseaudio CurrentDesktop: GNOME Date: Thu Jan 14 22:18:30 2016 InstallationDate: Installed on 2016-01-15 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [20BVCTO1WW, Realtek ALC3232, Black Headphone Out, Right] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET55WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET55WW(1.20):bd12/23/2015:svnLENOVO:pn20BVCTO1WW:pvrThinkPadT450:rvnLENOVO:rn20BVCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BVCTO1WW dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1534434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549872] Re: [E6232, Realtek ALC269VC, Speaker, Internal] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1549872 Title: [E6232, Realtek ALC269VC, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: After the latest kernel update no sound in Ubuntu 15.10 ben@ben-E6232:~$ aplay -l Lijst van PLAYBACK hardware-apparaten kaart 0: PCH [HDA Intel PCH], apparaat 0: ALC269VC Analog [ALC269VC Analog] Sub-apparaten: 1/1 Sub-apparaat #0: subdevice #0 kaart 0: PCH [HDA Intel PCH], apparaat 1: ALC269VC Digital [ALC269VC Digital] Sub-apparaten: 1/1 Sub-apparaat #0: subdevice #0 kaart 0: PCH [HDA Intel PCH], apparaat 3: HDMI 0 [HDMI 0] Sub-apparaten: 1/1 Sub-apparaat #0: subdevice #0 ben@ben-E6232:~$ ubuntu-bug Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. 1641 Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ben1641 F...m pulseaudio /dev/snd/controlC0: ben1641 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 25 16:54:45 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-19 (68 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Intern geluid - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ben1641 F...m pulseaudio /dev/snd/controlC0: ben1641 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [E6232, Realtek ALC269VC, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0.26 dmi.board.asset.tag: No Asset Tag dmi.board.name: E6232 dmi.board.vendor: MEDION dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0.26:bd08/20/2012:svnMEDION:pnE6232:pvrTobefilledbyO.E.M.:rvnMEDION:rnE6232:rvrTobefilledbyO.E.M.:cvnMEDION:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: E6232 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1549872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543724] Re: Audio stuttering. Only tried earphones. [HP Pavilion dv6 Notebook PC, IDT 92HD81B1X5, Black Headphone Out, Front] Underruns, dropouts or crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1543724 Title: Audio stuttering. Only tried earphones. [HP Pavilion dv6 Notebook PC, IDT 92HD81B1X5, Black Headphone Out, Front] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Running Ubuntu 15.10. I'm not sure if the bug is due to the alsa-driver or something else. At times audio stutters and jitters regardless if its being reproduced by media player or browser. I had to reinstall Ubuntu a few weeks ago because of a video driver problem and after that re-installation I started having this problem, but I might as well haven't noticed it at the time. I surely didn't have this problem with Linux Mint 17.3. I hope I didn't miss any useful information. Thank you for your attention and for your dedication. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thedoc97 1860 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 19:20:59 2016 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion dv6 Notebook PC, IDT 92HD81B1X5, Black Headphone Out, Front] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1C dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17FD dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1C:bd01/23/2013:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr06912120461620100:rvnHewlett-Packard:rn17FD:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 06912120461620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1543724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542717] Re: [OEM, Realtek ALC892, Green Line Out, Rear] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1542717 Title: [OEM, Realtek ALC892, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I'm unable to play any sounds. I've tried a few sound methods. - The builtin realtek ALC892 on the motherboard (used for filing this bug) via both the rear port and the front headphone port - Buying a cheap usb stick with some internet reviews that it works on linux (http://www.amazon.com/gp/product/B001MSS6CS?psc=1=true_=oh_aui_search_detailpage) - A displayport monitor with a sound out. All three methods work on a Windows install on the same machine. alsamixer sees all the cards and lets me adjust volumes, but I can't get any sound to actually play. From the sound configuration interface within Gnome I do get a weird bug. See the screencast; I try to switch to line out and test the speakers but the popup window title reflects another card. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steve 2234 F pulseaudio /dev/snd/controlC1: steve 2234 F pulseaudio /dev/snd/controlC0: steve 2234 F pulseaudio CurrentDesktop: GNOME Date: Sat Feb 6 15:40:04 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-07 (152 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_AlsaPlaybackTestStderr: A L S A l i b p c m _ h w . c : 1 6 9 3 : ( _ s n d _ p c m _ h w _ o p e n ) I n v a l i d v a l u e f o r c a r d Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steve 2234 F pulseaudio /dev/snd/controlC1: steve 2234 F pulseaudio /dev/snd/controlC0: steve 2234 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r a t t a c h h w : I n t e l e r r o r : N o s u c h d e v i c e Title: [OEM, Realtek ALC892, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to wily on 2015-11-26 (72 days ago) dmi.bios.date: 06/30/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 131-GT-E767 dmi.board.vendor: EVGA dmi.board.version: Tylersburg dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/30/2010:svnOEM:pnOEM:pvrOEM:rvnEVGA:rn131-GT-E767:rvrTylersburg:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-18T15:45:09.729397 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1542717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542641] Re: PCI/internal sound card not detected
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1542641 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Won't Fix Bug description: When I type alsa force-reload several times in terminal, it fixes. but when I reboot, problem persists again. this is my alsa info before force-reload http://www.alsa-project.org/db/?f=a6b8288b69c6fcaeb108200dc39df954d76b99e7 this is alsa info after force-reload several times until sound arrives. http://www.alsa-project.org/db/?f=45f0c322bcbd6d63c0040080baa5fbb63d797aa0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Feb 6 17:46:56 2016 InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2015 dmi.bios.vendor: HP dmi.bios.version: N78 Ver. 01.03 dmi.board.name: 8100 dmi.board.vendor: HP dmi.board.version: KBC Version 16.1F dmi.chassis.asset.tag: 5CD547351Q dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN78Ver.01.03:bd10/15/2015:svnHP:pnHPProBook440G3:pvr:rvnHP:rn8100:rvrKBCVersion16.1F:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1542641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554539] Re: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1554539 Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Audio in the front panel headphone jack(green) is muted. When jack is inserted it is recognized as headphone but there is no sound at all. Tried many different solutions but nothing works. Badly Stuck! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rafif 1649 F pulseaudio /dev/snd/controlC0: rafif 1649 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 8 20:10:01 2016 InstallationDate: Installed on 2016-03-04 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rafif 1649 F pulseaudio /dev/snd/controlC0: rafif 1649 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC1150, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0508 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0508:bd08/10/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1554539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1559228] Re: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1559228 Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have a Lenovo P50 with the docking station. When the laptop is plugged into the docking station sound will not play out the external port. An lspci -n gives me: 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) I have updated the bios. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgoodman 1698 F pulseaudio /dev/snd/pcmC0D0p: bgoodman 1698 F...m pulseaudio /dev/snd/controlC0: bgoodman 1698 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 18 12:08:52 2016 InstallationDate: Installed on 2016-03-17 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgoodman 1698 F pulseaudio /dev/snd/pcmC0D0p: bgoodman 1698 F...m pulseaudio /dev/snd/controlC0: bgoodman 1698 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET45W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET45W(1.19):bd02/22/2016:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-03-18T12:01:21.161389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1559228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555568] Re: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant cracking sound, even when idel (no media playback). Muting and unmuting the sound seems to help
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/168 Title: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant cracking sound, even when idel (no media playback). Muting and unmuting the sound seems to help for around half a minute... Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Sound constantly cracking, even when not playing any media. Muting and unmuting solves the problem for less than a minute. Running kernel 4.4.4, but the problem was still present on the factory Ubuntu 15.10 installation. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.4.4-040404-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arseny 1639 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 10 13:22:09 2016 InstallationDate: Installed on 2016-03-04 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0P96YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/13/2015:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn0P96YG:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 11 - 3147 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563112] Re: [bcm2835 - bcm2835 ALSA, playback] Underruns, dropouts or crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Tags removed: wily ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563112 Title: [bcm2835 - bcm2835 ALSA, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Confirmed Bug description: This bug can be reproduced by using the Speaker Testing for bcm2835 ALSA window from the Sound Preferences > Hardware > Test Speakers button. Clicking the Front Left or the Front Right Test buttons causes the bug to be demonstrated. The bug prevents apps that produce sound from working correctly. This bug has been mentioned recently on Google+ by David Johnson although probably not reported through the Ubuntu bug reporting system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.1.18-v7+ armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 895 F pulseaudio CurrentDesktop: MATE Date: Tue Mar 29 00:16:18 2016 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ALSA successful Symptom_Card: bcm2835 ALSA - bcm2835 ALSA Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [bcm2835 - bcm2835 ALSA, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1563112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564091] Re: USB sound card not detected Razer Megalon headset
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1564091 Title: USB sound card not detected Razer Megalon headset Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Razer Megalon headset this device is not working on Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tonmanayo 1617 F pulseaudio /dev/snd/controlC1: tonmanayo 1617 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 30 23:13:10 2016 InstallationDate: Installed on 2016-03-13 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10J dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10J:bd09/24/2013:svnMicro-StarInternationalCo.,Ltd.:pnGE402OL:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: GE40 2OL dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1564091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1834192 Title: apparmor mult_mount regression test fails in eoan Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: Confirmed Bug description: In running adt testing on 5.2-based kernels for eoan, I'm seeing failures from the apparmor mult_mount regression test. Running the test case manually with -x yields: + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20 + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3 ++ error_handler ++ fatalerror 'Unexpected shell error. Run with -x to debug' Running the following manually in a shell also fails in eoan with the 5.0 kernel copied forward from disco, while it passes in disco: $ uname -a Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dd if=/dev/zero of=test.img bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s $ mkfs.ext2 -F -m 0 -N 10 test.img mke2fs 1.45.2 (27-May-2019) test.img: Not enough space to build proposed filesystem while setting up superblock So this seems likely to be due to some change with mke2fs; not sure if this is a regression there or if the test was getting away with doing something invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509950] Re: DELL XPS M1210 STAC9221 Dual Headphone jacks not working
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1509950 Title: DELL XPS M1210 STAC9221 Dual Headphone jacks not working Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Ubuntu 15.10 after latest update headphones stopped working. When I ran alsamixer in the terminal, I saw they were muted. after unmuting them I pressed F6 and saw the soundcard id, then pressed esc and esc to exit alsamixer then entered sudo alsactl store Intel After rebooting they worked! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1272 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 02:15:01 2015 InstallationDate: Installed on 2015-10-20 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151019) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/11/2008:svnDellInc.:pnMXC062:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXC062 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1509950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] no master playback volume
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: virtualbox (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1487168 Title: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] no master playback volume Status in Virtualbox: New Status in alsa-driver package in Ubuntu: Won't Fix Status in virtualbox package in Ubuntu: Won't Fix Bug description: Volume Slider is only controlling PCM channel and is not controlling Master. In effect, Master is restricting the audio level to the default of approximately 45 Percent. In order to raise the Master Volume Level, alsamixer is capable of changing Master. Without manually raising Master to Max Volume, Volume Slider can only control volume from 0-45% which is the default level of Master. Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gene 1330 F pulseaudio gene 1922 F alsamixer CurrentDesktop: Unity Date: Thu Aug 20 13:00:57 2015 InstallationDate: Installed on 2015-08-19 (1 days ago) InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - Intel 82801AA-ICH Symptom_Type: Volume slider, or mixer problems Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1487168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508826] Re: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all when headset plugged in
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1508826 Title: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all when headset plugged in Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Sounds works fine through the internal speakers, but once I plug a headset or headphones (I tried two things, in case one was broken) in to the audio out, I get nothing. Looking in alsamixer, plugging the headset in mutes the 'Speaker' output and unmutes the 'Headphone' output, and restores the Master volume to its previous headset-in value. Unplugging the headset does the opposite (mutes 'Headphone'; unmutes 'Speaker'), as I would expect. This was working on vivid, so a definite regression, I think. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 5155 F pulseaudio /dev/snd/controlC0: daniel 5155 F pulseaudio Date: Thu Oct 22 09:37:39 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-04 (412 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to wily on 2015-10-21 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET70WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513107] Re: [20BFS05L00, Realtek ALC3232, Black Headphone Out, Left] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1513107 Title: [20BFS05L00, Realtek ALC3232, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I am on a Lenovo T540p, kernel is 4.2.0-16-generic, release is 15.10 wily. Fairly certain this bug started with/around wily's release. Sound works from internal speakers, but does not work when plugging in anything (in this case, also speakers) into the headphone jack. Those speakers work fine when connected to a different device. The jack worked fine up until recently. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: j-frost2395 F...m pulseaudio /dev/snd/pcmC1D0p: j-frost2395 F...m pulseaudio /dev/snd/controlC1: j-frost2395 F pulseaudio /dev/snd/controlC0: j-frost2395 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 4 16:01:39 2015 InstallationDate: Installed on 2015-08-25 (71 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: j-frost2395 F...m pulseaudio /dev/snd/pcmC1D0p: j-frost2395 F...m pulseaudio /dev/snd/controlC1: j-frost2395 F pulseaudio /dev/snd/controlC0: j-frost2395 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [20BFS05L00, Realtek ALC3232, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to wily on 2015-10-28 (7 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GMET68WW (2.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BFS05L00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGMET68WW(2.16):bd11/07/2014:svnLENOVO:pn20BFS05L00:pvrThinkPadT540p:rvnLENOVO:rn20BFS05L00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20BFS05L00 dmi.product.version: ThinkPad T540p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1513107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
** Tags removed: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks
** Description changed: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] - ... + Some other locking races or something? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Disco: In Progress Bug description: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] Some other locking races or something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839292] Re: systemd 243 now defaults to the "unified" cgroup hierarchy setup, so Docker don't start anymore
Was fixed by release 243~rc1-0ubuntu2 of systemd. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1839292 Title: systemd 243 now defaults to the "unified" cgroup hierarchy setup, so Docker don't start anymore Status in systemd package in Ubuntu: Fix Released Bug description: Hi, like mentioned in systemd NEWS (https://github.com/systemd/systemd/blob/master/NEWS#L56) it's compiled with -Ddefault-hierarchy=unified from now. After updating to the proposed version 243~rc1-0ubuntu1 Docker doesn't come up because of the unsupported cgroup v2. "dockerd[1968]: Error starting daemon: Devices cgroup isn't mounted" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829861] Re: handle TLS session renegotiation
** Description changed: [Impact] TLS sessions can renegotiate keys, but APT does not support it; meaning their HTTPS connections stop working. [Test case] - ... + We don't really have a reproducer. You'd need a server that re-negotiates by path; e.g. because it requires a a certain client certificate for a certain path. + + We know it does not break other use cases, and the patch was tested by + the patch submitter @ Akamai (see + https://github.com/Debian/apt/pull/93). [Regression potential] - Could we get stuck on renegotiation? ** Description changed: [Impact] TLS sessions can renegotiate keys, but APT does not support it; meaning their HTTPS connections stop working. [Test case] We don't really have a reproducer. You'd need a server that re-negotiates by path; e.g. because it requires a a certain client certificate for a certain path. - We know it does not break other use cases, and the patch was tested by - the patch submitter @ Akamai (see - https://github.com/Debian/apt/pull/93). + We know it does not break other use cases, having run that for quite + some time in eoan and Debian stretch, and the patch was tested by the + patch submitter @ Akamai (see https://github.com/Debian/apt/pull/93). [Regression potential] - Could we get stuck on renegotiation? ** No longer affects: apt (Ubuntu Cosmic) ** Changed in: apt (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1829861 Title: handle TLS session renegotiation Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Disco: In Progress Status in apt source package in Eoan: Fix Released Bug description: [Impact] TLS sessions can renegotiate keys, but APT does not support it; meaning their HTTPS connections stop working. [Test case] We don't really have a reproducer. You'd need a server that re-negotiates by path; e.g. because it requires a a certain client certificate for a certain path. We know it does not break other use cases, having run that for quite some time in eoan and Debian stretch, and the patch was tested by the patch submitter @ Akamai (see https://github.com/Debian/apt/pull/93). [Regression potential] - Could we get stuck on renegotiation? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks
** Description changed: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] - ... + Watch lock release with strace and see that it unlocks the right way. [Regression potential] ... ** Changed in: apt (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Disco: In Progress Bug description: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] Some other locking races or something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838771] Re: http:Fix Host header in proxied https connections
Uploaded apt 1.8.3 to disco (this is a sync (*) from Debian unstable, and also includes some other bug fixes from 1.8.2 which I forgot to sync earlier) (*) uploaded with --no-lp so we get a diff for sru-review ** Description changed: [Impact] Currently CONNECT requests use the name of the proxy as Host value, instead of the origin server's name. According to RFC 2616 "The Host field value MUST represent the naming authority of the origin server or gateway given by the original URL." The current implementation causes problems with some proxy vendors. This commit[0] fixes this. [0] - https://salsa.debian.org/apt- team/apt/commit/86d4d98060f36c7e71c34af20a1193a75496ef72#54d3193c5d10a0032c80c3a6d3f069507265547f [Test Case] Here's one reproducer an impacted user brought to my attention: - # /etc/environment - http_proxy="http://internal:8080; - https_proxy="http://interal:8080; + # /etc/environment + http_proxy="http://internal:8080; + https_proxy="http://interal:8080; To support application development activities in-house, I had to configure Azure CLI APT repository following the instructions from "https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view =azure-cli-latest": - $ sudo apt-get update - $ sudo apt-get install curl apt-transport-https lsb-release gnupg - $ curl -sL https://packages.microsoft.com/keys/microsoft.asc | \ - $ gpg --dearmor | \ - $ sudo tee /etc/apt/trusted.gpg.d/microsoft.asc.gpg > /dev/null - $ AZ_REPO=$(lsb_release -cs) - $ echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $ $ AZ_REPO main" | \ - $ sudo tee /etc/apt/sources.list.d/azure-cli.list - $ sudo apt update + $ sudo apt-get update + $ sudo apt-get install curl apt-transport-https lsb-release gnupg + $ curl -sL https://packages.microsoft.com/keys/microsoft.asc | \ + $ gpg --dearmor | \ + $ sudo tee /etc/apt/trusted.gpg.d/microsoft.asc.gpg > /dev/null + $ AZ_REPO=$(lsb_release -cs) + $ echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $ $ AZ_REPO main" | \ + $ sudo tee /etc/apt/sources.list.d/azure-cli.list + $ sudo apt update In the final "apt update" command, APT respects system-wide network proxy variables and successfully fetched Canonical repository data over HTTP. However, it was unable to fetch the newly added Microsoft packages repository served via HTTPS. By using Wireshark to examine the HTTPS request made by APT, the request body reveals as: - CONNECT packages.microsoft.com:443 HTTP/1.1\r\n - Host: internal:8080\r\n - User-Agent: Debian APT-HTTP/1.3 (1.6.11)\r\n - ... - ... + CONNECT packages.microsoft.com:443 HTTP/1.1\r\n + Host: internal:8080\r\n + User-Agent: Debian APT-HTTP/1.3 (1.6.11)\r\n + ... + ... + There also is an automated test case in the package that runs as part of + autopkgtest that tests a scenario like this, see the commit. [Regression Potential] * Fix already in debian, and Eoan * Has been reviewed/approved by juliank * A test package (pre-sru) has been provided to an impacted user, and he confirms it solves the situation. [Other Info] # salsa $ git describe --contains 86d4d98060f36c7e71c34af20a1193a75496ef72 1.9.0~8 # rmadison apt => apt | 1.6.11 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x => apt | 1.8.1 | disco-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.9.1 | eoan | source, amd64, arm64, armhf, i386, ppc64el, s390x -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1838771 Title: http:Fix Host header in proxied https connections Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Disco: In Progress Bug description: [Impact] Currently CONNECT requests use the name of the proxy as Host value, instead of the origin server's name. According to RFC 2616 "The Host field value MUST represent the naming authority of the origin server or gateway given by the original URL." The current implementation causes problems with some proxy vendors. This commit[0] fixes this. [0] - https://salsa.debian.org/apt- team/apt/commit/86d4d98060f36c7e71c34af20a1193a75496ef72#54d3193c5d10a0032c80c3a6d3f069507265547f [Test Case] Here's one reproducer an impacted user brought to my attention: # /etc/environment http_proxy="http://internal:8080; https_proxy="http://interal:8080; To support application development activities in-house, I had to configure Azure CLI APT repository following the instructions from "https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view =azure-cli-latest": $ sudo apt-get update $ sudo apt-get install curl apt-transport-https lsb-release gnupg $ curl -sL
[Touch-packages] [Bug 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]
Maybe this is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916504 ? ** Bug watch added: Debian Bug tracker #916504 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916504 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test] Status in pulseaudio package in Ubuntu: Confirmed Bug description: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4
Confirmed, it's a test failure: FAIL: cpu-volume-test ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed ** Summary changed: - pulseaudio FTBFS on eoan 12.2-2ubuntu4 + pulseaudio FTBFS on eoan 12.2-2ubuntu4: FAIL: cpu-volume-test ** Summary changed: - pulseaudio FTBFS on eoan 12.2-2ubuntu4: FAIL: cpu-volume-test + pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test] Status in pulseaudio package in Ubuntu: Confirmed Bug description: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 Status in pulseaudio package in Ubuntu: New Bug description: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839589] [NEW] pulseaudio FTBFS on eoan 12.2-2ubuntu4
Public bug reported: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 Status in pulseaudio package in Ubuntu: New Bug description: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839586] Re: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839586 Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cups package in Ubuntu: New Bug description: error at the start of the pc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 AptOrdering: cups-filters:amd64: Install NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Wed Aug 7 06:58:27 2019 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-07-30 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_400_M401dn_817E04_: ipp://ZXDSL83C1II.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3050 Papersize: letter PpdFiles: HP_LaserJet_400_M401dn_817E04_: LaserJet 400 M401dn ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0W0CHX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd05/08/2017:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0W0CHX:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839586] [NEW] package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: error at the start of the pc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 AptOrdering: cups-filters:amd64: Install NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Wed Aug 7 06:58:27 2019 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-07-30 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_400_M401dn_817E04_: ipp://ZXDSL83C1II.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3050 Papersize: letter PpdFiles: HP_LaserJet_400_M401dn_817E04_: LaserJet 400 M401dn ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0W0CHX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd05/08/2017:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0W0CHX:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839586 Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cups package in Ubuntu: New Bug description: error at the start of the pc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 AptOrdering: cups-filters:amd64: Install NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Wed Aug 7 06:58:27 2019 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-07-30 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_400_M401dn_817E04_: ipp://ZXDSL83C1II.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3050 Papersize: letter PpdFiles: HP_LaserJet_400_M401dn_817E04_: LaserJet 400 M401dn ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0W0CHX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd05/08/2017:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0W0CHX:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839586/+subscriptions -- Mailing list:
