from:"Vasya Pupkin"

[Touch-packages] [Bug 2082625] Re: Let's Encrypt Root CA is missing

2024-09-26 Thread Vasya Pupkin

It seems like this is a Let's Encrypt bug, because I ended up with wrong
intermediate certificate in the fullchain.pem file. Please close this
bug.

** Changed in: ca-certificates (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/2082625

Title:
  Let's Encrypt Root CA is missing

Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  Some Let's Encrypt Root CA is missing from ca-certificates package.
  It's easy to confirm:

  $ curl -svo /dev/null https://natashamoroz.com
  * Host natashamoroz.com:443 was resolved.
  * IPv6: (none)
  * IPv4: 188.242.141.254
  *   Trying 188.242.141.254:443...
  * Connected to natashamoroz.com (188.242.141.254) port 443
  * ALPN: curl offers h2,http/1.1
  } [5 bytes data]
  * TLSv1.3 (OUT), TLS handshake, Client hello (1):
  } [512 bytes data]
  *  CAfile: /etc/ssl/certs/ca-certificates.crt
  *  CApath: /etc/ssl/certs
  { [5 bytes data]
  * TLSv1.3 (IN), TLS handshake, Server hello (2):
  { [122 bytes data]
  * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  { [21 bytes data]
  * TLSv1.3 (IN), TLS handshake, Certificate (11):
  { [2056 bytes data]
  * TLSv1.3 (OUT), TLS alert, unknown CA (560):
  } [2 bytes data]
  * SSL certificate problem: unable to get local issuer certificate
  * Closing connection

  $ openssl s_client -connect natashamoroz.com:443 -showcerts
  CONNECTED(0003)
  depth=0 CN = natashamoroz.com
  verify error:num=20:unable to get local issuer certificate
  verify return:1
  depth=0 CN = natashamoroz.com
  verify error:num=21:unable to verify the first certificate
  verify return:1
  depth=0 CN = natashamoroz.com
  verify return:1
  ---
  Certificate chain
   0 s:CN = natashamoroz.com
     i:C = US, O = Let's Encrypt, CN = E5
     a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384
     v:NotBefore: Aug  9 12:48:02 2024 GMT; NotAfter: Nov  7 12:48:01 2024 GMT
  -BEGIN CERTIFICATE-
  MIIDlzCCAx2gAwIBAgISBHHFUn5199cYVg5s4AbDFGiMMAoGCCqGSM49BAMDMDIx
  CzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQDEwJF
  NTAeFw0yNDA4MDkxMjQ4MDJaFw0yNDExMDcxMjQ4MDFaMBsxGTAXBgNVBAMTEG5h
  dGFzaGFtb3Jvei5jb20wWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAATQWyHUiZx/
  QlngiDCEFqa4MUCaX63vTIeMpq/pd3eH1WWNu3n6esazgKE6dyy2AVxJCiWQA7WU
  a++caH3C0xUvo4ICKDCCAiQwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsG
  AQUFBwMBBggrBgEFBQcDAjAMBgNVHRMBAf8EAjAAMB0GA1UdDgQWBBTDqKJxFz10
  63UDZBA6bg9d1ATHNjAfBgNVHSMEGDAWgBSfK1/PPCFPnQS37SssxMZwi9LXDTBV
  BggrBgEFBQcBAQRJMEcwIQYIKwYBBQUHMAGGFWh0dHA6Ly9lNS5vLmxlbmNyLm9y
  ZzAiBggrBgEFBQcwAoYWaHR0cDovL2U1LmkubGVuY3Iub3JnLzAxBgNVHREEKjAo
  ghBuYXRhc2hhbW9yb3ouY29tghR3d3cubmF0YXNoYW1vcm96LmNvbTATBgNVHSAE
  DDAKMAgGBmeBDAECATCCAQQGCisGAQQB1nkCBAIEgfUEgfIA8AB2AO7N0GTV2xrO
  xVy3nbTNE6Iyh0Z8vOzew1FIWUZxH7WbAAABkTdkGywAAAQDAEcwRQIgMUjSGkuN
  +vx6PNq9jzGJbP5dKgfs5K7/wxVAWWIQcmgCIQC3EVMlI0TzMAkKyZEJ6K7cfFp0
  aQ5FatPnW4j8egNqjwB2AN/hVuuqBa+1nA+GcY2owDJOrlbZbqf1pWoB0cE7vlJc
  AAABkTdkG+gAAAQDAEcwRQIhAL7ZuYjCN/QfLb5PvmmEQ/+34Xjw5nsCOZk+t8XC
  SPYJAiAH+ZVke25hv/jCO4jmGwZHVLmnOq0VCbNOVqMc6JvvTzAKBggqhkjOPQQD
  AwNoADBlAjARhAZ9+bKg0oGS9Sr0704OB4CiauuM5WTtdU2wGRRG5M/5NsQjxgRF
  s3CkoL937ngCMQCMzai0sFnQ7cioVZEk62n2U/9zIMFHWJ5IVui0PEdPp6J8yo18
  TU5JS3IYQyDeJTM=
  -END CERTIFICATE-
   1 s:C = US, O = Let's Encrypt, CN = E6
     i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
     a:PKEY: id-ecPublicKey, 384 (bit); sigalg: RSA-SHA256
     v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
  -BEGIN CERTIFICATE-
  MIIEVzCCAj+gAwIBAgIRALBXPpFzlydw27SHyzpFKzgwDQYJKoZIhvcNAQELBQAw
  TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
  cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjQwMzEzMDAwMDAw
  WhcNMjcwMzEyMjM1OTU5WjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
  RW5jcnlwdDELMAkGA1UEAxMCRTYwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAATZ8Z5G
  h/ghcWCoJuuj+rnq2h25EqfUJtlRFLFhfHWWvyILOR/VvtEKRqotPEoJhC6+QJVV
  6RlAN2Z17TJOdwRJ+HB7wxjnzvdxEP6sdNgA1O1tHHMWMxCcOrLqbGL0vbijgfgw
  gfUwDgYDVR0PAQH/BAQDAgGGMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcD
  ATASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSTJ0aYA6lRaI6Y1sRCSNsj
  v1iU0jAfBgNVHSMEGDAWgBR5tFnme7bl5AFzgAiIyBpY9umbbjAyBggrBgEFBQcB
  AQQmMCQwIgYIKwYBBQUHMAKGFmh0dHA6Ly94MS5pLmxlbmNyLm9yZy8wEwYDVR0g
  BAwwCjAIBgZngQwBAgEwJwYDVR0fBCAwHjAcoBqgGIYWaHR0cDovL3gxLmMubGVu
  Y3Iub3JnLzANBgkqhkiG9w0BAQsFAAOCAgEAfYt7SiA1sgWGCIpunk46r4AExIRc
  MxkKgUhNlrrv1B21hOaXN/5miE+LOTbrcmU/M9yvC6MVY730GNFoL8IhJ8j8vrOL
  pMY22OP6baS1k9YMrtDTlwJHoGby04ThTUeBDksS9RiuHvicZqBedQdIF65pZuhp
  eDcGBcLiYasQr/EO5gxxtLyTmgsHSOVSBcFOn9lgv7LECPq9i7mfH3mpxgrRKSxH
  pOoZ0KXMcB+hHuvlklHntvcI0mMMQ0mhYj6qtMFStkF1RpCG3IPdIwpVCQqu8GV7
  s8ubknRzs+3C/Bm19RFOoiPpDkwvyNfvmQ14XkyqqKK5oZ8zhD32kFRQkxa8uZSu
  h4aTImFxknu39waBxIRXE4jKxlAmQc4QjFZoq1KmQqQg0J/1JF8RlFvJas1VcjLv
  YlvUB2t6npO6oQjB3l+PNf0DpQH7iUx3Wz5AjQC

[Touch-packages] [Bug 2082625] [NEW] Let's Encrypt Root CA is missing

2024-09-26 Thread Vasya Pupkin

Public bug reported:

Some Let's Encrypt Root CA (ISRG Root X1) is missing from ca-
certificates package. It's easy to confirm:

$ curl -svo /dev/null https://natashamoroz.com
* Host natashamoroz.com:443 was resolved.
* IPv6: (none)
* IPv4: 188.242.141.254
*   Trying 188.242.141.254:443...
* Connected to natashamoroz.com (188.242.141.254) port 443
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [21 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2056 bytes data]
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
} [2 bytes data]
* SSL certificate problem: unable to get local issuer certificate
* Closing connection


$ openssl s_client -connect natashamoroz.com:443 -showcerts
CONNECTED(0003)
depth=0 CN = natashamoroz.com
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN = natashamoroz.com
verify error:num=21:unable to verify the first certificate
verify return:1
depth=0 CN = natashamoroz.com
verify return:1
---
Certificate chain
 0 s:CN = natashamoroz.com
   i:C = US, O = Let's Encrypt, CN = E5
   a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384
   v:NotBefore: Aug  9 12:48:02 2024 GMT; NotAfter: Nov  7 12:48:01 2024 GMT
-BEGIN CERTIFICATE-
MIIDlzCCAx2gAwIBAgISBHHFUn5199cYVg5s4AbDFGiMMAoGCCqGSM49BAMDMDIx
CzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQDEwJF
NTAeFw0yNDA4MDkxMjQ4MDJaFw0yNDExMDcxMjQ4MDFaMBsxGTAXBgNVBAMTEG5h
dGFzaGFtb3Jvei5jb20wWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAATQWyHUiZx/
QlngiDCEFqa4MUCaX63vTIeMpq/pd3eH1WWNu3n6esazgKE6dyy2AVxJCiWQA7WU
a++caH3C0xUvo4ICKDCCAiQwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsG
AQUFBwMBBggrBgEFBQcDAjAMBgNVHRMBAf8EAjAAMB0GA1UdDgQWBBTDqKJxFz10
63UDZBA6bg9d1ATHNjAfBgNVHSMEGDAWgBSfK1/PPCFPnQS37SssxMZwi9LXDTBV
BggrBgEFBQcBAQRJMEcwIQYIKwYBBQUHMAGGFWh0dHA6Ly9lNS5vLmxlbmNyLm9y
ZzAiBggrBgEFBQcwAoYWaHR0cDovL2U1LmkubGVuY3Iub3JnLzAxBgNVHREEKjAo
ghBuYXRhc2hhbW9yb3ouY29tghR3d3cubmF0YXNoYW1vcm96LmNvbTATBgNVHSAE
DDAKMAgGBmeBDAECATCCAQQGCisGAQQB1nkCBAIEgfUEgfIA8AB2AO7N0GTV2xrO
xVy3nbTNE6Iyh0Z8vOzew1FIWUZxH7WbAAABkTdkGywAAAQDAEcwRQIgMUjSGkuN
+vx6PNq9jzGJbP5dKgfs5K7/wxVAWWIQcmgCIQC3EVMlI0TzMAkKyZEJ6K7cfFp0
aQ5FatPnW4j8egNqjwB2AN/hVuuqBa+1nA+GcY2owDJOrlbZbqf1pWoB0cE7vlJc
AAABkTdkG+gAAAQDAEcwRQIhAL7ZuYjCN/QfLb5PvmmEQ/+34Xjw5nsCOZk+t8XC
SPYJAiAH+ZVke25hv/jCO4jmGwZHVLmnOq0VCbNOVqMc6JvvTzAKBggqhkjOPQQD
AwNoADBlAjARhAZ9+bKg0oGS9Sr0704OB4CiauuM5WTtdU2wGRRG5M/5NsQjxgRF
s3CkoL937ngCMQCMzai0sFnQ7cioVZEk62n2U/9zIMFHWJ5IVui0PEdPp6J8yo18
TU5JS3IYQyDeJTM=
-END CERTIFICATE-
 1 s:C = US, O = Let's Encrypt, CN = E6
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
   a:PKEY: id-ecPublicKey, 384 (bit); sigalg: RSA-SHA256
   v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
-BEGIN CERTIFICATE-
MIIEVzCCAj+gAwIBAgIRALBXPpFzlydw27SHyzpFKzgwDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjQwMzEzMDAwMDAw
WhcNMjcwMzEyMjM1OTU5WjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
RW5jcnlwdDELMAkGA1UEAxMCRTYwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAATZ8Z5G
h/ghcWCoJuuj+rnq2h25EqfUJtlRFLFhfHWWvyILOR/VvtEKRqotPEoJhC6+QJVV
6RlAN2Z17TJOdwRJ+HB7wxjnzvdxEP6sdNgA1O1tHHMWMxCcOrLqbGL0vbijgfgw
gfUwDgYDVR0PAQH/BAQDAgGGMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcD
ATASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSTJ0aYA6lRaI6Y1sRCSNsj
v1iU0jAfBgNVHSMEGDAWgBR5tFnme7bl5AFzgAiIyBpY9umbbjAyBggrBgEFBQcB
AQQmMCQwIgYIKwYBBQUHMAKGFmh0dHA6Ly94MS5pLmxlbmNyLm9yZy8wEwYDVR0g
BAwwCjAIBgZngQwBAgEwJwYDVR0fBCAwHjAcoBqgGIYWaHR0cDovL3gxLmMubGVu
Y3Iub3JnLzANBgkqhkiG9w0BAQsFAAOCAgEAfYt7SiA1sgWGCIpunk46r4AExIRc
MxkKgUhNlrrv1B21hOaXN/5miE+LOTbrcmU/M9yvC6MVY730GNFoL8IhJ8j8vrOL
pMY22OP6baS1k9YMrtDTlwJHoGby04ThTUeBDksS9RiuHvicZqBedQdIF65pZuhp
eDcGBcLiYasQr/EO5gxxtLyTmgsHSOVSBcFOn9lgv7LECPq9i7mfH3mpxgrRKSxH
pOoZ0KXMcB+hHuvlklHntvcI0mMMQ0mhYj6qtMFStkF1RpCG3IPdIwpVCQqu8GV7
s8ubknRzs+3C/Bm19RFOoiPpDkwvyNfvmQ14XkyqqKK5oZ8zhD32kFRQkxa8uZSu
h4aTImFxknu39waBxIRXE4jKxlAmQc4QjFZoq1KmQqQg0J/1JF8RlFvJas1VcjLv
YlvUB2t6npO6oQjB3l+PNf0DpQH7iUx3Wz5AjQCi6L25FjyE06q6BZ/QlmtYdl/8
ZYao4SRqPEs/6cAiF+Qf5zg2UkaWtDphl1LKMuTNLotvsX99HP69V2faNyegodQ0
LyTApr/vT01YPE46vNsDLgK+4cL6TrzC/a4WcmF5SRJ938zrv/duJHLXQIku5v0+
EwOy59Hdm0PT/Er/84dDV0CSjdR/2XuZM3kpysSKLgD1cKiDA+IRguODCxfO9cyY
Ig46v9mFmBvyH04=
-END CERTIFICATE-
---
Server certificate
subject=CN = natashamoroz.com
issuer=C = US, O = Let's Encrypt, CN = E5
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ECDSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2415 bytes and written 398 bytes
Verification error: unable to verify the first certificate


$ sudo grep -i -r 'ISRG Root X1' /etc/ssl/certs/ | w

[Touch-packages] [Bug 2082625] Re: Let's Encrypt Root CA is missing

2024-09-26 Thread Vasya Pupkin

** Description changed:

- Some Let's Encrypt Root CA (ISRG Root X1) is missing from ca-
- certificates package. It's easy to confirm:
+ Some Let's Encrypt Root CA is missing from ca-certificates package. It's
+ easy to confirm:
  
  $ curl -svo /dev/null https://natashamoroz.com
  * Host natashamoroz.com:443 was resolved.
  * IPv6: (none)
  * IPv4: 188.242.141.254
  *   Trying 188.242.141.254:443...
  * Connected to natashamoroz.com (188.242.141.254) port 443
  * ALPN: curl offers h2,http/1.1
  } [5 bytes data]
  * TLSv1.3 (OUT), TLS handshake, Client hello (1):
  } [512 bytes data]
  *  CAfile: /etc/ssl/certs/ca-certificates.crt
  *  CApath: /etc/ssl/certs
  { [5 bytes data]
  * TLSv1.3 (IN), TLS handshake, Server hello (2):
  { [122 bytes data]
  * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  { [21 bytes data]
  * TLSv1.3 (IN), TLS handshake, Certificate (11):
  { [2056 bytes data]
  * TLSv1.3 (OUT), TLS alert, unknown CA (560):
  } [2 bytes data]
  * SSL certificate problem: unable to get local issuer certificate
  * Closing connection
  
- 
  $ openssl s_client -connect natashamoroz.com:443 -showcerts
  CONNECTED(0003)
  depth=0 CN = natashamoroz.com
  verify error:num=20:unable to get local issuer certificate
  verify return:1
  depth=0 CN = natashamoroz.com
  verify error:num=21:unable to verify the first certificate
  verify return:1
  depth=0 CN = natashamoroz.com
  verify return:1
  ---
  Certificate chain
-  0 s:CN = natashamoroz.com
-i:C = US, O = Let's Encrypt, CN = E5
-a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384
-v:NotBefore: Aug  9 12:48:02 2024 GMT; NotAfter: Nov  7 12:48:01 2024 GMT
+  0 s:CN = natashamoroz.com
+    i:C = US, O = Let's Encrypt, CN = E5
+    a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384
+    v:NotBefore: Aug  9 12:48:02 2024 GMT; NotAfter: Nov  7 12:48:01 2024 GMT
  -BEGIN CERTIFICATE-
  MIIDlzCCAx2gAwIBAgISBHHFUn5199cYVg5s4AbDFGiMMAoGCCqGSM49BAMDMDIx
  CzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQDEwJF
  NTAeFw0yNDA4MDkxMjQ4MDJaFw0yNDExMDcxMjQ4MDFaMBsxGTAXBgNVBAMTEG5h
  dGFzaGFtb3Jvei5jb20wWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAATQWyHUiZx/
  QlngiDCEFqa4MUCaX63vTIeMpq/pd3eH1WWNu3n6esazgKE6dyy2AVxJCiWQA7WU
  a++caH3C0xUvo4ICKDCCAiQwDgYDVR0PAQH/BAQDAgeAMB0GA1UdJQQWMBQGCCsG
  AQUFBwMBBggrBgEFBQcDAjAMBgNVHRMBAf8EAjAAMB0GA1UdDgQWBBTDqKJxFz10
  63UDZBA6bg9d1ATHNjAfBgNVHSMEGDAWgBSfK1/PPCFPnQS37SssxMZwi9LXDTBV
  BggrBgEFBQcBAQRJMEcwIQYIKwYBBQUHMAGGFWh0dHA6Ly9lNS5vLmxlbmNyLm9y
  ZzAiBggrBgEFBQcwAoYWaHR0cDovL2U1LmkubGVuY3Iub3JnLzAxBgNVHREEKjAo
  ghBuYXRhc2hhbW9yb3ouY29tghR3d3cubmF0YXNoYW1vcm96LmNvbTATBgNVHSAE
  DDAKMAgGBmeBDAECATCCAQQGCisGAQQB1nkCBAIEgfUEgfIA8AB2AO7N0GTV2xrO
  xVy3nbTNE6Iyh0Z8vOzew1FIWUZxH7WbAAABkTdkGywAAAQDAEcwRQIgMUjSGkuN
  +vx6PNq9jzGJbP5dKgfs5K7/wxVAWWIQcmgCIQC3EVMlI0TzMAkKyZEJ6K7cfFp0
  aQ5FatPnW4j8egNqjwB2AN/hVuuqBa+1nA+GcY2owDJOrlbZbqf1pWoB0cE7vlJc
  AAABkTdkG+gAAAQDAEcwRQIhAL7ZuYjCN/QfLb5PvmmEQ/+34Xjw5nsCOZk+t8XC
  SPYJAiAH+ZVke25hv/jCO4jmGwZHVLmnOq0VCbNOVqMc6JvvTzAKBggqhkjOPQQD
  AwNoADBlAjARhAZ9+bKg0oGS9Sr0704OB4CiauuM5WTtdU2wGRRG5M/5NsQjxgRF
  s3CkoL937ngCMQCMzai0sFnQ7cioVZEk62n2U/9zIMFHWJ5IVui0PEdPp6J8yo18
  TU5JS3IYQyDeJTM=
  -END CERTIFICATE-
-  1 s:C = US, O = Let's Encrypt, CN = E6
-i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
-a:PKEY: id-ecPublicKey, 384 (bit); sigalg: RSA-SHA256
-v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
+  1 s:C = US, O = Let's Encrypt, CN = E6
+    i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
+    a:PKEY: id-ecPublicKey, 384 (bit); sigalg: RSA-SHA256
+    v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
  -BEGIN CERTIFICATE-
  MIIEVzCCAj+gAwIBAgIRALBXPpFzlydw27SHyzpFKzgwDQYJKoZIhvcNAQELBQAw
  TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
  cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjQwMzEzMDAwMDAw
  WhcNMjcwMzEyMjM1OTU5WjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
  RW5jcnlwdDELMAkGA1UEAxMCRTYwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAATZ8Z5G
  h/ghcWCoJuuj+rnq2h25EqfUJtlRFLFhfHWWvyILOR/VvtEKRqotPEoJhC6+QJVV
  6RlAN2Z17TJOdwRJ+HB7wxjnzvdxEP6sdNgA1O1tHHMWMxCcOrLqbGL0vbijgfgw
  gfUwDgYDVR0PAQH/BAQDAgGGMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcD
  ATASBgNVHRMBAf8ECDAGAQH/AgEAMB0GA1UdDgQWBBSTJ0aYA6lRaI6Y1sRCSNsj
  v1iU0jAfBgNVHSMEGDAWgBR5tFnme7bl5AFzgAiIyBpY9umbbjAyBggrBgEFBQcB
  AQQmMCQwIgYIKwYBBQUHMAKGFmh0dHA6Ly94MS5pLmxlbmNyLm9yZy8wEwYDVR0g
  BAwwCjAIBgZngQwBAgEwJwYDVR0fBCAwHjAcoBqgGIYWaHR0cDovL3gxLmMubGVu
  Y3Iub3JnLzANBgkqhkiG9w0BAQsFAAOCAgEAfYt7SiA1sgWGCIpunk46r4AExIRc
  MxkKgUhNlrrv1B21hOaXN/5miE+LOTbrcmU/M9yvC6MVY730GNFoL8IhJ8j8vrOL
  pMY22OP6baS1k9YMrtDTlwJHoGby04ThTUeBDksS9RiuHvicZqBedQdIF65pZuhp
  eDcGBcLiYasQr/EO5gxxtLyTmgsHSOVSBcFOn9lgv7LECPq9i7mfH3mpxgrRKSxH
  pOoZ0KXMcB+hHuvlklHntvcI0mMMQ0mhYj6qtMFStkF1RpCG3IPdIwpVCQqu8GV7
  s8ubknRzs+3C/Bm19RFOoiPpDkwvyNfvmQ14XkyqqKK5oZ8zhD32kFRQkxa8uZSu
  h4aTImFxknu39waBxIRXE

[Touch-packages] [Bug 2080216] Re: sshd cannot bind to IPv4 interfaces

2024-09-13 Thread Vasya Pupkin

Some more details. Here's a part of my sslh config:

listen:
(
{ host: "0.0.0.0"; port: "443"; },
{ host: "::"; port: "443"; }
);

And here's how it's working:

# ss -tlnp | grep sslh
LISTEN 0  50   0.0.0.0:4430.0.0.0:*
users:(("sslh-fork",pid=2557,fd=3),("sslh-fork",pid=2556,fd=3),("sslh-fork",pid=2551,fd=3))
LISTEN 0  50  [::]:443   [::]:*
users:(("sslh-fork",pid=2557,fd=4),("sslh-fork",pid=2556,fd=4),("sslh-fork",pid=2551,fd=4))

You can see that it's listening on both 0.0.0.0 and [::] interfaces.

Now here's a piece of my sshd_config:

AddressFamily any
ListenAddress 0.0.0.0
ListenAddress ::

And here's how it's working:

# ss -tlnp | grep sshd
LISTEN 0  8192[::]:22[::]:*
users:(("sshd",pid=843,fd=3),("systemd",pid=1,fd=69))


As you can see, it doesn't listen on IPv4 interface at all.

This is clearly a packaging bug because only precompiled binaries are
affected. My sslh binary compiled under Ubuntu 22.04 was doing the same
and was fixed once I compiled it under Ubuntu 24.04.

-- 
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/2080216

Title:
  sshd cannot bind to IPv4 interfaces

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 22.04 to 24.04 I noticed that my sshd only
  listening on IPv6 interface (::), while previously it was listening
  both IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify
  ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after
  restart sshd was still listening on IPv6 only.

  This problem affects other packages as well, for example, openvpn.

  Rebuilding applications from sources seems to fix the issue.

  Setting net.ipv6.bindv6only=0 also helps, but that's not a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu13.5
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Sep 10 16:45:54 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=screen.xterm-256color
  SourcePackage: openssh
  UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2080216/+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 2080216] Re: sshd cannot bind to IPv4 interfaces

2024-09-10 Thread Vasya Pupkin

I first noticed that I could not ssh to my host, was getting connection
refused error. Then I tried to connect over IPv6 address and it worked.
I checked with `ss -tlnp | grep 22` and found out that sshd was only
listening on [::]:22. Then I tried almost everything to bind it to
0.0.0.0 without any luck. Even when I only specified 0.0.0.0 as bind
interface, it was still binding to [::] instead.

I also noticed that my manually compiled sslh behaved the same way. Last
time it was compiled on Ubuntu 22.04, so I decided to rebuild it on
24.04 and it started to work properly.

I believe, there was some change in libc which either requires all
network related software recompiled from source. Because like I said,
almost every network related software behaves the same.

While net.ipv6.bindv6only=0 is the default, it doesn't explain why
net.ipv6.bindv6only=1 works incorrectly. It is not supposed to replace
0.0.0.0 with [::], it is supposed to stop applications to bind to IPv4
interfaces when they are configured to bind to [::] only explicitly.
Also, it doesn't explain why recompiling applications from source fixes
the issue.

-- 
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/2080216

Title:
  sshd cannot bind to IPv4 interfaces

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 22.04 to 24.04 I noticed that my sshd only
  listening on IPv6 interface (::), while previously it was listening
  both IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify
  ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after
  restart sshd was still listening on IPv6 only.

  This problem affects other packages as well, for example, openvpn.

  Rebuilding applications from sources seems to fix the issue.

  Setting net.ipv6.bindv6only=0 also helps, but that's not a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu13.5
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Sep 10 16:45:54 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=screen.xterm-256color
  SourcePackage: openssh
  UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2080216/+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 2080216] [NEW] sshd cannot bind to IPv4 interfaces

2024-09-10 Thread Vasya Pupkin

Public bug reported:

After upgrading from 22.04 to 24.04 I noticed that my sshd only
listening on IPv6 interface (::), while previously it was listening both
IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify
ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after
restart sshd was still listening on IPv6 only.

This problem affects other packages as well, for example, openvpn.

Rebuilding applications from sources seems to fix the issue.

Setting net.ipv6.bindv6only=0 also helps, but that's not a solution.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: openssh-server 1:9.6p1-3ubuntu13.5
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Sep 10 16:45:54 2024
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=screen.xterm-256color
SourcePackage: openssh
UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

-- 
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/2080216

Title:
  sshd cannot bind to IPv4 interfaces

Status in openssh package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 24.04 I noticed that my sshd only
  listening on IPv6 interface (::), while previously it was listening
  both IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify
  ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after
  restart sshd was still listening on IPv6 only.

  This problem affects other packages as well, for example, openvpn.

  Rebuilding applications from sources seems to fix the issue.

  Setting net.ipv6.bindv6only=0 also helps, but that's not a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu13.5
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Sep 10 16:45:54 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=screen.xterm-256color
  SourcePackage: openssh
  UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2080216/+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 1928594] [NEW] Setting up encrypted swap causes ordering cycle

2021-05-16 Thread Vasya Pupkin

Public bug reported:

root@home:~# cat /etc/crypttab
# 
cswap /dev/disk/by-partuuid/95605326-e210-4e13-9f93-50cc3d556aca /dev/urandom 
cipher=aes-xts-plain64,size=256,hash=sha1,swap

root@home:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic
cryptsetup: WARNING: Resume target cswap uses a key file

After reboot:

root@home:~# systemctl status systemd-random-seed.service
● systemd-random-seed.service - Load/Save Random Seed
 Loaded: loaded (/lib/systemd/system/systemd-random-seed.service; static; 
vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-random-seed.service(8)
 man:random(4)

May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
ordering cycle on systemd-random-seed.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-mount.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import.target/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import-cache.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.6
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
Date: Sun May 16 18:40:45 2021
InstallationDate: Installed on 2021-01-21 (115 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
 /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 6: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: System manufacturer System Product Name
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=screen.xterm-256color
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=7c964d4b-ef4d-40df-b297-631e4233f297 ro bootdegraded=true 
transparent_hugepage=never
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3801
dmi.board.asset.tag: Default string
dmi.board.name: Z170-E
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.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
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/1928594

Title:
  Setting up encrypted swap causes ordering cycle

Status in systemd package in Ubuntu:
  New

Bug description:
  root@home:~# cat /etc/crypttab
  # 
  cswap /dev/disk/by-partuuid/95605326-e210-4e13-9f93-50cc3d556aca /dev/urandom 
cipher=aes-xts-plain64,size=256,ha

[Touch-packages] [Bug 1779657] Re: apt autoremove not removing old kernels

2021-01-20 Thread Vasya Pupkin

No manually installed kernels. And these were not meta packages. But
since I am on 20.04 now, this is not affecting me anymore.

-- 
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/1779657

Title:
  apt autoremove not removing old kernels

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  I noticed that apt autoremove stopped removing old kernels recently.
  Currently I have 6 installed and apt autoremove does not try to remove
  old ones:

  $ sudo apt autoremove --purge 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  In /etc/apt/apt.conf.d/01autoremove-kernels it is said to only keep
  last three versions:

  # list of different kernel versions:
  4.15.0-24.26~16.04.1
  4.15.0-23.25~16.04.1
  4.15.0-22.24~16.04.1
  4.15.0-15.16~16.04.1
  4.13.0-45.50~16.04.1
  4.13.0-43.48~16.04.1
  # Installing kernel: 4.13.0-45.50~16.04.1 (4.13.0-45-generic)
  # Running kernel: 4.15.0-23.25~16.04.1 (4.15.0-23-generic)
  # Last kernel: 4.15.0-24.26~16.04.1
  # Previous kernel: 4.15.0-23.25~16.04.1
  # Kernel versions list to keep:
  4.13.0-45.50~16.04.1
  4.15.0-23.25~16.04.1
  4.15.0-24.26~16.04.1
  # Kernel packages (version part) to protect:
  4\.13\.0-45-generic
  4\.15\.0-23-generic
  4\.15\.0-24-generic

  It was working fine previously and I didn't change anything that could
  break this functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul  2 14:12:03 2018
  InstallationDate: Installed on 2018-01-19 (164 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1779657/+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 1881582] [NEW] ca-certificates missing some root CA

2020-06-01 Thread Vasya Pupkin

Public bug reported:

I started seeing certificate errors in curl recently on Ubuntu 16.04.
Here's an example:

$ curl -svo /dev/null --resolve ngrok.com:443:34.211.12.31 https://ngrok.com/
* Added ngrok.com:443:34.211.12.31 to DNS cache
* Hostname ngrok.com was found in DNS cache
*   Trying 34.211.12.31...
* Connected to ngrok.com (34.211.12.31) port 443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 596 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
* server certificate verification failed. CAfile: 
/etc/ssl/certs/ca-certificates.crt CRLfile: none
* Closing connection 0

I have latest version of ca-certificates installed. On Ubuntu 20.04
everything works fine:

$ curl -svo /dev/null --resolve ngrok.com:443:34.211.12.31 https://ngrok.com/
* Added ngrok.com:443:34.211.12.31 to DNS cache
* Hostname ngrok.com was found in DNS cache
*   Trying 34.211.12.31:443...
* TCP_NODELAY set
* Connected to ngrok.com (34.211.12.31) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [106 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4439 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.ngrok.com
*  start date: Mar 10 00:00:00 2020 GMT
*  expire date: Mar 10 23:59:59 2021 GMT
*  subjectAltName: host "ngrok.com" matched cert's "ngrok.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; 
CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20170717~16.04.2
ProcVersionSignature: Ubuntu 4.15.0-101.102~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
Date: Mon Jun  1 13:51:14 2020
InstallationDate: Installed on 2011-04-14 (3336 days ago)
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
PackageArchitecture: all
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ca-certificates
UpgradeStatus: Upgraded to xenial on 2016-07-30 (1401 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1881582

Title:
  ca-certificates missing some root CA

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I started seeing certificate errors in curl recently on Ubuntu 16.04.
  Here's an example:

  $ curl -svo /dev/null --resolve ngrok.com:443:34.211.12.31 https://ngrok.com/
  * Added ngrok.com:443:34.211.12.31 to DNS cache
  * Hostname ngrok.com was found in DNS cache
  *   Trying 34.211.12.31...
  * Connected to ngrok.com (34.211.12.31) port 443 (#0)
  * found 148 certificates in /etc/ssl/certs/ca-certificates.crt
  * found 596 certificates in /etc/ssl/certs
  * ALPN, offering http/1.1
  * SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
  * server certificate verification failed. CAfile: 
/etc/ssl/certs/ca-certificates.crt CRLfile: none
  * Closing connection 0

  I have latest version of ca-certificates installed. On Ubuntu 20.04
  everything works fine:

  $ curl -svo /dev/null --resolve ngrok.com:443:34.211.12.31 https://ngrok.com/
  * Added ngrok.com:443:34.211.12.31 to DNS cache
  * Hostname ngrok.com was found in DNS cache
  *   Trying 34.211.12.31:443...
  * TCP_NODELAY set
  * Connected to ngrok.com (34.211.12.31) port 443 (#0)
  * ALPN, offering h2
  * ALPN, offering http/1.1
  * successfully set certificate verify locations:
  *   CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
  } [5 bytes data]
  * TLSv1.3 (OUT), TLS handshake, Client hello (1):
  } [512 bytes data]
  * TLSv1.3 (IN), TLS handshake, Server hello (2):
  { [106 bytes data]
  * TLSv1.2 (IN), TLS handshake, Certificate (11):
  { [4439 bytes data]
  * TLSv1.2 (IN), TLS handshake, Server key exchange (12):
  { [300 bytes data]
  * TLSv1.2 (IN), TLS handshake, Server finished

[Touch-packages] [Bug 175316] Re: no IDN in nslookup and host

2018-08-02 Thread Vasya Pupkin

Any chances the fix will arrive in xenial?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/175316

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/175316/+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 1779657] [NEW] apt autoremove not removing old kernels

2018-07-02 Thread Vasya Pupkin

Public bug reported:

I noticed that apt autoremove stopped removing old kernels recently.
Currently I have 6 installed and apt autoremove does not try to remove
old ones:

$ sudo apt autoremove --purge 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

In /etc/apt/apt.conf.d/01autoremove-kernels it is said to only keep last
three versions:

# list of different kernel versions:
4.15.0-24.26~16.04.1
4.15.0-23.25~16.04.1
4.15.0-22.24~16.04.1
4.15.0-15.16~16.04.1
4.13.0-45.50~16.04.1
4.13.0-43.48~16.04.1
# Installing kernel: 4.13.0-45.50~16.04.1 (4.13.0-45-generic)
# Running kernel: 4.15.0-23.25~16.04.1 (4.15.0-23-generic)
# Last kernel: 4.15.0-24.26~16.04.1
# Previous kernel: 4.15.0-23.25~16.04.1
# Kernel versions list to keep:
4.13.0-45.50~16.04.1
4.15.0-23.25~16.04.1
4.15.0-24.26~16.04.1
# Kernel packages (version part) to protect:
4\.13\.0-45-generic
4\.15\.0-23-generic
4\.15\.0-24-generic

It was working fine previously and I didn't change anything that could
break this functionality.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.26
ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jul  2 14:12:03 2018
InstallationDate: Installed on 2018-01-19 (164 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Summary changed:

- apt autoremove not removing old 4.15 kernels
+ apt autoremove not removing old kernels

-- 
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/1779657

Title:
  apt autoremove not removing old kernels

Status in apt package in Ubuntu:
  New

Bug description:
  I noticed that apt autoremove stopped removing old kernels recently.
  Currently I have 6 installed and apt autoremove does not try to remove
  old ones:

  $ sudo apt autoremove --purge 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  In /etc/apt/apt.conf.d/01autoremove-kernels it is said to only keep
  last three versions:

  # list of different kernel versions:
  4.15.0-24.26~16.04.1
  4.15.0-23.25~16.04.1
  4.15.0-22.24~16.04.1
  4.15.0-15.16~16.04.1
  4.13.0-45.50~16.04.1
  4.13.0-43.48~16.04.1
  # Installing kernel: 4.13.0-45.50~16.04.1 (4.13.0-45-generic)
  # Running kernel: 4.15.0-23.25~16.04.1 (4.15.0-23-generic)
  # Last kernel: 4.15.0-24.26~16.04.1
  # Previous kernel: 4.15.0-23.25~16.04.1
  # Kernel versions list to keep:
  4.13.0-45.50~16.04.1
  4.15.0-23.25~16.04.1
  4.15.0-24.26~16.04.1
  # Kernel packages (version part) to protect:
  4\.13\.0-45-generic
  4\.15\.0-23-generic
  4\.15\.0-24-generic

  It was working fine previously and I didn't change anything that could
  break this functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul  2 14:12:03 2018
  InstallationDate: Installed on 2018-01-19 (164 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1779657/+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 1426362] Re: logind session files fill up /run space

2018-03-29 Thread Vasya Pupkin

All sessions appear in closing state, here's another one:

$ loginctl show-session 77
Id=77
User=1004
Name=raccess
Timestamp=Чт 2018-03-29 20:30:02 MSK
TimestampMonotonic=2363185101
VTNr=0
Remote=yes
RemoteHost=216.126.59.227
Service=sshd
Scope=session-77.scope
Leader=3389
Audit=77
Type=tty
Class=user
Active=yes
State=closing
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1426362

Title:
  logind session files fill up /run space

Status in systemd-shim package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory 
with files.
  The files are 240-260 bytes, but there are many
   As per default install, /run is on tmpfs with 50 MB size. After a couple of 
days, /run/ runs out of free space, which can cause not so funny errors, like 
failed kernel update (kernel postinst tries to create files here, then fails)

  As I see, thesefiles are releated to ssh sesssions, and yes there are
  plenty SSH connection to this host. Shouldn't systemd remove these old
  session files?

  # lsb_release -rd
  Description:Ubuntu 14.10
  Release:14.10

  # apt-cache policy systemd
  systemd:
Installed: 208-8ubuntu8.2
Candidate: 208-8ubuntu8.2
Version table:
   *** 208-8ubuntu8.2 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   208-8ubuntu8 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1426362/+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 1426362] Re: logind session files fill up /run space

2018-03-29 Thread Vasya Pupkin

I am having the same issue on Ubuntu 16.04 now. All sessions appear to
be for one user that is used for incoming ssh connections for rsync.
Here's an example:

$ loginctl show-session 59
Id=59
User=1004
Name=raccess
Timestamp=Чт 2018-03-29 20:20:03 MSK
TimestampMonotonic=1763641802
VTNr=0
Remote=yes
RemoteHost=216.126.59.227
Service=sshd
Scope=session-59.scope
Leader=2814
Audit=59
Type=tty
Class=user
Active=yes
State=closing
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0

I don't see any processes running under user raccess apart from system
ones:

$ ps aux | grep raccess | grep -v grep
raccess   2822  0.0  1.6   6384  4132 ?Ss   20:20   0:00 
/lib/systemd/systemd --user
raccess   2823  0.0  0.4   7316  1096 ?S20:20   0:00 (sd-pam)

And here's an output of lsof -u raccess: https://pbin.cf/444b2d29

This is happening on two servers.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1426362

Title:
  logind session files fill up /run space

Status in systemd-shim package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory 
with files.
  The files are 240-260 bytes, but there are many
   As per default install, /run is on tmpfs with 50 MB size. After a couple of 
days, /run/ runs out of free space, which can cause not so funny errors, like 
failed kernel update (kernel postinst tries to create files here, then fails)

  As I see, thesefiles are releated to ssh sesssions, and yes there are
  plenty SSH connection to this host. Shouldn't systemd remove these old
  session files?

  # lsb_release -rd
  Description:Ubuntu 14.10
  Release:14.10

  # apt-cache policy systemd
  systemd:
Installed: 208-8ubuntu8.2
Candidate: 208-8ubuntu8.2
Version table:
   *** 208-8ubuntu8.2 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   208-8ubuntu8 0
  500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1426362/+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 175316] Re: no IDN in nslookup and host

2018-03-29 Thread Vasya Pupkin

By the way, for all who need a workaround, here's a simple script that
uses idn tool (apt install idn) to translate any non-ascii parameters to
punycode and pass them to supplied executable.

Example:
$ type host
host is aliased to `idnwrapper.sh host'
$ host почта.рф
xn--80a1acny.xn--p1ai has address 91.215.36.43
xn--80a1acny.xn--p1ai mail is handled by 20 78.108.81.1.


** Attachment added: "idn wrapper"
   
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/175316/+attachment/5094800/+files/idnwrapper.sh

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/175316

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Confirmed
Status in iputils package in Ubuntu:
  Fix Released
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/175316/+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 175316] Re: no IDN in nslookup and host

2018-03-29 Thread Vasya Pupkin

And what about other tools like dig and host? How many more years will
they lack IDN support?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/175316

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Confirmed
Status in iputils package in Ubuntu:
  Fix Released
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/175316/+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 175316] Re: no IDN in nslookup and host

2017-09-27 Thread Vasya Pupkin

Seriously, what's the problem? IDN support was added long time ago to
BIND9 and it's tools. Whether someone likes it or not, IDN is a standard
(bad one, but still) and should be supported. Right now I have to use
wrapper to make these tools IDN-aware.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/175316

Title:
  no IDN in nslookup and host

Status in BIND:
  New
Status in bind9 package in Ubuntu:
  Confirmed
Status in iputils package in Ubuntu:
  Confirmed
Status in bind9 package in Debian:
  New

Bug description:
  Binary package hint: bind9

  Neither nslookup or host supports IDN. If you try , for example, to
  get the IP for "registrera-domän.se" it fails every time. As the use
  of IDN is increasing I think it would be a good thing if these tools
  supported this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/175316/+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 1714701] [NEW] vim: syntax highlighting bug with NSIS scripts

2017-09-02 Thread Vasya Pupkin

Public bug reported:

NSIS scripts allow escaping single quotes, like this:

BrandingText 'Vasya V\' Pupkin'

Currently vim considers second single quote as closing and third as
opening, which break syntax highlighting in big scripts completely after
such lines.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: vim 2:8.0.0095-1ubuntu3
Uname: Linux 4.12.10-041210-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sat Sep  2 19:08:10 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-11 (52 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: vim (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1714701

Title:
  vim: syntax highlighting bug with NSIS scripts

Status in vim package in Ubuntu:
  New

Bug description:
  NSIS scripts allow escaping single quotes, like this:

  BrandingText 'Vasya V\' Pupkin'

  Currently vim considers second single quote as closing and third as
  opening, which break syntax highlighting in big scripts completely
  after such lines.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim 2:8.0.0095-1ubuntu3
  Uname: Linux 4.12.10-041210-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Sep  2 19:08:10 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-11 (52 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1714701/+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 1611168] Re: lightdm crashes when trying to switch keyboard layout

2016-08-08 Thread Vasya Pupkin

** Description changed:

  Steps to reproduce:
  
  1. Have at least two keyboard layouts configured (i.e. English and Russian)
  2. Configure hotkey to switch layouts (Settings -> Text Entry -> Switch to 
next source using:)
  3. Lock desktop (Ctrl+Alt+L)
  4. Press layout switch hotkey
  
  After few seconds lightdm will crash, you will see desktop unlocked for
- a moment and then it be locked again. After unlocking desktop an error
- report will show up.
+ a moment and then it will be locked again. After unlocking desktop an
+ error report will show up.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu2
  Uname: Linux 4.7.0-040700-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  9 04:29:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-01 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1611168

Title:
  lightdm crashes when trying to switch keyboard layout

Status in lightdm package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have at least two keyboard layouts configured (i.e. English and Russian)
  2. Configure hotkey to switch layouts (Settings -> Text Entry -> Switch to 
next source using:)
  3. Lock desktop (Ctrl+Alt+L)
  4. Press layout switch hotkey

  After few seconds lightdm will crash, you will see desktop unlocked
  for a moment and then it will be locked again. After unlocking desktop
  an error report will show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu2
  Uname: Linux 4.7.0-040700-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  9 04:29:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-01 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1611168/+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 1611168] [NEW] lightdm crashes when trying to switch keyboard layout

2016-08-08 Thread Vasya Pupkin

Public bug reported:

Steps to reproduce:

1. Have at least two keyboard layouts configured (i.e. English and Russian)
2. Configure hotkey to switch layouts (Settings -> Text Entry -> Switch to next 
source using:)
3. Lock desktop (Ctrl+Alt+L)
4. Press layout switch hotkey

After few seconds lightdm will crash, you will see desktop unlocked for
a moment and then it be locked again. After unlocking desktop an error
report will show up.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.2-0ubuntu2
Uname: Linux 4.7.0-040700-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug  9 04:29:49 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-01 (100 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug package-from-proposed xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1611168

Title:
  lightdm crashes when trying to switch keyboard layout

Status in lightdm package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have at least two keyboard layouts configured (i.e. English and Russian)
  2. Configure hotkey to switch layouts (Settings -> Text Entry -> Switch to 
next source using:)
  3. Lock desktop (Ctrl+Alt+L)
  4. Press layout switch hotkey

  After few seconds lightdm will crash, you will see desktop unlocked
  for a moment and then it be locked again. After unlocking desktop an
  error report will show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu2
  Uname: Linux 4.7.0-040700-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  9 04:29:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-01 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1611168/+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 1586539] Re: Major screen flickering in Chromium and Google Chrome

2016-06-21 Thread Vasya Pupkin

joakimk...@gmail.com posted a real workaround on chromium bug tracker:

===
sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf 

Paste this:

Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "AccelMethod" "uxa"
EndSection

Save and reboot.
===

This works for me.

-- 
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/1586539

Title:
  Major screen flickering in Chromium and Google Chrome

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

  Update: this indeed happens only when browser window is maximized.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586539/+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 1586539] Re: Major screen flickering in Chromium and Google Chrome

2016-06-02 Thread Vasya Pupkin

** Description changed:

  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated in
  16.04. I came across some discussions where different people suggested
  that it is related to new X.Org version.
  
  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s
  
  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.
  
+ Update: this indeed happens only when browser window is maximized.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
-  vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
+  vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
+  vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5126 
-  vendor SHP
+  product id5126
+  vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

-- 
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/1586539

Title:
  Major screen flickering in Chromium and Google Chrome

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is cause

[Touch-packages] [Bug 1586539] [NEW] Major screen flickering in Chromium and Google Chrome

2016-05-27 Thread Vasya Pupkin

Public bug reported:

On a fresh installation of Ubuntu 16.04 I noticed major screen
flickering issues in Chromium and Google Chrome browsers. Since this
never happened in Ubuntu 15.10 with exactly the same Google Chrome
binary, I believe, bug is caused by something that was added/updated in
16.04. I came across some discussions where different people suggested
that it is related to new X.Org version.

Here's a video to show what is happening:
https://youtu.be/l21WsKz3fZc?t=45s

I could fix this flickering with --disable-gpu-compositing switch, but
this slows down page drawing significantly so it can't be considered a
workaround. There is also a Chromium bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
don't think they will fix an Ubuntu-specific bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.6.0-040600-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat May 28 00:01:20 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
 vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller 
[1043:13bd]
InstallationDate: Installed on 2016-05-01 (26 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. UX301LAA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX301LAA.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX301LAA
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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX301LAA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun May 22 23:28:15 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5126 
 vendor SHP
xserver.version: 2:1.18.3-1ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
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/1586539

Title:
  Major screen flickering in Chromium and Google Chrome

Status in xorg package in Ubuntu:
  New

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

[Touch-packages] [Bug 1483437] Re: Mouse cursor disappears permanently after watching full screen videos

2016-03-01 Thread Vasya Pupkin

To test this I will have to install this image and use it extensively
for at least a week. Do you really offer me to do that or you missed
part about "it wasn't happening every day, it's an annoying random bug"?

-- 
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/1483437

Title:
  Mouse cursor disappears permanently after watching full screen videos

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes after watching a YouTube video in Google Chrome in full
  screen mode, my mouse pointer disappears. I can move mouse, scroll
  using mouse wheel, click everywhere, but I can't see a cursor. I can
  only guess where it is. This drives me mad because the only solution
  is to restart PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug 11 02:36:08 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13bd]
  InstallationDate: Installed on 2015-05-06 (96 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=b9c815db-e4fe-4e08-8d62-0c68991fa8be ro quiet splash rootfstype=ext4 
pcie_aspm=force acpi_osi= vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  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.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Tue Aug 11 02:34:47 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1483437/+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 1483437] Re: Mouse cursor disappears permanently after watching full screen videos

2016-02-29 Thread Vasya Pupkin

Yes, it was happening on Ubuntu 15.10 as well with latest BIOS (version
211) installed. But since I upgraded kernel to 4.5, it never happened.
Which doesn't mean anything because it wasn't happening every day, it's
an annoying random bug.

-- 
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/1483437

Title:
  Mouse cursor disappears permanently after watching full screen videos

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes after watching a YouTube video in Google Chrome in full
  screen mode, my mouse pointer disappears. I can move mouse, scroll
  using mouse wheel, click everywhere, but I can't see a cursor. I can
  only guess where it is. This drives me mad because the only solution
  is to restart PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug 11 02:36:08 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13bd]
  InstallationDate: Installed on 2015-05-06 (96 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=b9c815db-e4fe-4e08-8d62-0c68991fa8be ro quiet splash rootfstype=ext4 
pcie_aspm=force acpi_osi= vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  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.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Tue Aug 11 02:34:47 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1483437/+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 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

2015-11-13 Thread Vasya Pupkin

Well, the only problem is with Shift-PrtScr. I remmeber, Alt-PrtScr
never worked for me before, so it's not related.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1512290

Title:
  gnome-screenshot produces very low quality blurry screenshots

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 source package in Wily:
  Triaged

Bug description:
  I believe, this is because I am using a HiDPI display. Every time I
  take a screenshot, I get a blurry image. This is not what I want when
  making a screenshot. Everywhere else when I make a screenshot, I get a
  100% copy of my screen, pixel-perfect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screenshot 3.16.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 13:11:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-22 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1512290/+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 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

2015-11-12 Thread Vasya Pupkin

Well, quality is good now but Shift-PrtScr (copy selection) doesn't work
as expected anymore. The screenshot I am getting is not what I am
selecting. And Alt-PrtScr causes a crash instantly.

Anyway, it is better than it was even with these problems. I can always
crop what I need from a full screenshot which is perfect now.

** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1512290

Title:
  gnome-screenshot produces very low quality blurry screenshots

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Wily:
  Fix Committed

Bug description:
  I believe, this is because I am using a HiDPI display. Every time I
  take a screenshot, I get a blurry image. This is not what I want when
  making a screenshot. Everywhere else when I make a screenshot, I get a
  100% copy of my screen, pixel-perfect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screenshot 3.16.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 13:11:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-22 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1512290/+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 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

2015-11-06 Thread Vasya Pupkin

I am on wily-proposed but still haven't got the fix. What am I doing
wrong?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1512290

Title:
  gnome-screenshot produces very low quality blurry screenshots

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  I believe, this is because I am using a HiDPI display. Every time I
  take a screenshot, I get a blurry image. This is not what I want when
  making a screenshot. Everywhere else when I make a screenshot, I get a
  100% copy of my screen, pixel-perfect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screenshot 3.16.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 13:11:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-22 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1512290/+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 1488587] [NEW] NetworkManager ignores setting "Automatically connect to this network when available"

2015-08-25 Thread Vasya Pupkin

Public bug reported:

I have two Wi-Fi networks available, one is slow and one is fast. I
unchecked option "Automatically connect to this network when available"
for slow network, but NetworkManager keeps connecting to slow network
automatically. I have to manually disconnect and connect to fast network
manually.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.1
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 25 19:42:35 2015
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-05-06 (110 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static  metric 1024 
 192.168.0.0/23 dev wlan0  proto kernel  scope link  src 192.168.0.177 
 192.168.10.0/24 via 192.168.0.2 dev wlan0  proto dhcp  metric 10
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH

 wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
VK_Main_5mhz  983d2cae-70de-47fe-8fcb-199ec5c0958a  
/org/freedesktop/NetworkManager/ActiveConnection/14 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  -- 
   ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
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/1488587

Title:
  NetworkManager ignores setting "Automatically connect to this network
  when available"

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have two Wi-Fi networks available, one is slow and one is fast. I
  unchecked option "Automatically connect to this network when
  available" for slow network, but NetworkManager keeps connecting to
  slow network automatically. I have to manually disconnect and connect
  to fast network manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 25 19:42:35 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-06 (110 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 1024 
   192.168.0.0/23 dev wlan0  proto kernel  scope link  src 192.168.0.177 
   192.168.10.0/24 via 192.168.0.2 dev wlan0  proto dhcp  metric 10
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH

   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
VK_Main_5mhz  983d2cae-70de-47fe-8fcb-199ec5c0958a  
/org/freedesktop/NetworkManager/ActiveConnection/14 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1488587/+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 1483437] [NEW] Mouse cursor disappears permanently after watching full screen videos

2015-08-10 Thread Vasya Pupkin

Public bug reported:

Sometimes after watching a YouTube video in Google Chrome in full screen
mode, my mouse pointer disappears. I can move mouse, scroll using mouse
wheel, click everywhere, but I can't see a cursor. I can only guess
where it is. This drives me mad because the only solution is to restart
PC.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xserver-xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Aug 11 02:36:08 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:13bd]
InstallationDate: Installed on 2015-05-06 (96 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: ASUSTeK COMPUTER INC. UX301LAA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=b9c815db-e4fe-4e08-8d62-0c68991fa8be ro quiet splash rootfstype=ext4 
pcie_aspm=force acpi_osi= vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX301LAA.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX301LAA
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.:bvrUX301LAA.209:bd05/08/2014:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX301LAA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Aug 11 02:34:47 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5126 
 vendor SHP
xserver.version: 2:1.17.1-0ubuntu3

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid

** Summary changed:

- Mouse cursor dissapears permanently after watching fullscreen videos
+ Mouse cursor disappears permanently after watching full screen videos

-- 
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/1483437

Title:
  Mouse cursor disappears permanently after watching full screen videos

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes after watching a YouTube video in Google Chrome in full
  screen mode, my mouse pointer disappears. I can move mouse, scroll
  using mouse wheel, click everywhere, but I can't see a cursor. I can
  only guess where it is. This drives me mad because the only solution
  is to restart PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug 11 02:36:08 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUST

[Touch-packages] [Bug 2082625] Re: Let's Encrypt Root CA is missing

[Touch-packages] [Bug 2082625] [NEW] Let's Encrypt Root CA is missing

[Touch-packages] [Bug 2082625] Re: Let's Encrypt Root CA is missing

[Touch-packages] [Bug 2080216] Re: sshd cannot bind to IPv4 interfaces

[Touch-packages] [Bug 2080216] Re: sshd cannot bind to IPv4 interfaces

[Touch-packages] [Bug 2080216] [NEW] sshd cannot bind to IPv4 interfaces

[Touch-packages] [Bug 1928594] [NEW] Setting up encrypted swap causes ordering cycle

[Touch-packages] [Bug 1779657] Re: apt autoremove not removing old kernels

[Touch-packages] [Bug 1881582] [NEW] ca-certificates missing some root CA

[Touch-packages] [Bug 175316] Re: no IDN in nslookup and host

[Touch-packages] [Bug 1779657] [NEW] apt autoremove not removing old kernels

[Touch-packages] [Bug 1426362] Re: logind session files fill up /run space

[Touch-packages] [Bug 1426362] Re: logind session files fill up /run space

[Touch-packages] [Bug 175316] Re: no IDN in nslookup and host

[Touch-packages] [Bug 175316] Re: no IDN in nslookup and host

[Touch-packages] [Bug 175316] Re: no IDN in nslookup and host

[Touch-packages] [Bug 1714701] [NEW] vim: syntax highlighting bug with NSIS scripts

[Touch-packages] [Bug 1611168] Re: lightdm crashes when trying to switch keyboard layout

[Touch-packages] [Bug 1611168] [NEW] lightdm crashes when trying to switch keyboard layout

[Touch-packages] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

[Touch-packages] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

[Touch-packages] [Bug 1586539] [NEW] Major screen flickering in Chromium and Google Chrome

[Touch-packages] [Bug 1483437] Re: Mouse cursor disappears permanently after watching full screen videos

[Touch-packages] [Bug 1483437] Re: Mouse cursor disappears permanently after watching full screen videos

[Touch-packages] [Bug 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

[Touch-packages] [Bug 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

[Touch-packages] [Bug 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

[Touch-packages] [Bug 1488587] [NEW] NetworkManager ignores setting "Automatically connect to this network when available"

[Touch-packages] [Bug 1483437] [NEW] Mouse cursor disappears permanently after watching full screen videos

29 matches

Site Navigation

Mail list logo

Footer information