[Touch-packages] [Bug 1823435] [NEW] session-migration ftbfs in disco

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
.session-migration_0.3.3_BUILDING.txt.gz

make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
Scanning dependencies of target check
make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
nosetests3
...FF
==
FAIL: Test that the migration happens as expected
--
Traceback (most recent call last):
  File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
- 10_test.sh;01_test.sh;02_test.sh;
+ 01_test.sh;02_test.sh;10_test.sh;


==
FAIL: Test subsequent runs with a new script
--
Traceback (most recent call last):
  File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
- 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
+ 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;


--
Ran 9 tests in 8.615s

FAILED (failures=2)
make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:167: check] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build] Error 2

** Affects: session-migration (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Changed in: session-migration (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-dd-incoming

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

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  

[Touch-packages] [Bug 1823433] [NEW] pcre3 ftbfs in disco

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417924474/buildlog_ubuntu-disco-
amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz

dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
--- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
+++ dpkg-gensymbolsEKHP_Q   2019-04-06 01:28:56.598135324 +
@@ -80,9 +80,9 @@
  (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
  (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
-#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
+#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  (c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
-#MISSING: 2:8.39-9# (c++|optional=STL)"void std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
+#MISSING: 2:8.39-11# (c++|optional=STL)"void std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  (c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
  (c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
- (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
+#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:116: binary-arch] Error 2

** Affects: pcre3 (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Changed in: pcre3 (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-dd-incoming

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

Title:
  pcre3 ftbfs in disco

Status in pcre3 package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924474/buildlog_ubuntu-disco-
  amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz

  dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
  dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
  --- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
  +++ dpkg-gensymbolsEKHP_Q 2019-04-06 01:28:56.598135324 +
  @@ -80,9 +80,9 @@
(c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
(c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
(c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
  -#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  +#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
(c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
  -#MISSING: 2:8.39-9# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  +#MISSING: 2:8.39-11# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
(c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
(c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
  - (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  +#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:116: binary-arch] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1823433/+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 1823432] [NEW] openexr ftbfs in disco (i386 only)

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

compression 7, x sampling 2, y sampling 2: writing reading comparing
compression 8, x sampling 2, y sampling 2: writing reading comparing
compression 9, x sampling 2, y sampling 2: writing reading comparing
random bits
compression 0, x sampling 1, y sampling 1: writing reading comparingIlmImfTest: 
testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
FAIL IlmImfTest (exit status: 134)


Testsuite summary for OpenEXR 2.2.1

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See IlmImfTest/test-suite.log

make[5]: *** [Makefile:966: test-suite.log] Error 1
make[5]: Leaving directory '/<>/IlmImfTest'
make[4]: *** [Makefile:1074: check-TESTS] Error 2
make[4]: Leaving directory '/<>/IlmImfTest'
make[3]: *** [Makefile:1148: check-am] Error 2
make[3]: Leaving directory '/<>/IlmImfTest'
make[2]: *** [Makefile:498: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:25: build-arch] Error 2

** Affects: openexr (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Changed in: openexr (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-dd-incoming

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1823432/+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 1823426] [NEW] librsvg ftbfs in disco (i386 only)

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

   Compiling phf_generator v0.7.23
 Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
error[E0428]: the name `U1024` is defined multiple times
--> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
 |
2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
 | 
-
 previous definition of the type `U1024` here
2111 | pub type P1024 = PInt; pub type N1024 = NInt;
2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
 | 
^
 `U1024` redefined here
 |
 = note: `U1024` must be defined only once in the type namespace of this 
module

error[E0428]: the name `P1024` is defined multiple times
--> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
 |
2111 | pub type P1024 = PInt; pub type N1024 = NInt;
 | - previous definition of the type 
`P1024` here
2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;
 | ^ `P1024` redefined here
 |
 = note: `P1024` must be defined only once in the type namespace of this 
module

error[E0428]: the name `N1024` is defined multiple times
--> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
 |
2111 | pub type P1024 = PInt; pub type N1024 = NInt;
 |   - previous 
definition of the type `N1024` here
2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
2113 | pub type P1024 = PInt; pub type N1024 = NInt;
 |   ^ `N1024` 
redefined here
 |
 = note: `N1024` must be defined only once in the type namespace of this 
module

   Compiling quote v0.6.8
 Running `rustc --crate-name quote /<>/vendor/quote/src/lib.rs 
--color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C 
debuginfo=2 --cfg 'feature="default"' --cfg 'feature="proc-macro"' --cfg 
'feature="proc-macro2"' -C metadata=7bcb03a3954c3d99 -C 
extra-filename=-7bcb03a3954c3d99 --out-dir /<>/target/release/deps 
-L dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0428`.
error: Could not compile `typenum`.

Caused by:
  process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
warning: build failed, waiting for other jobs to finish...
error: build failed
make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:1457: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:940: all] Error 2

** Affects: librsvg (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Changed in: librsvg (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-dd-incoming

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 

[Touch-packages] [Bug 1823425] [NEW] libdmapsharing ftbfs in disco

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417924367/buildlog_ubuntu-disco-
amd64.libdmapsharing_2.9.39-4_BUILDING.txt.gz

Making all in tests
make[3]: Entering directory '/<>/tests'
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject  
dacplisten.vala vala-dmap-db.vala vala-dmap-container-db.vala -C
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gtk+-2.0 --pkg 
gstreamer-1.0 --pkg libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg 
avahi-gobject dpapview.vala vala-dmap-db.vala vala-dpap-record.vala -C
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapcopy.vala vala-dmap-db.vala vala-dpap-record.vala -C
/usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapserve.vala vala-dmap-db.vala vala-dpap-record.vala 
vala-dmap-container-db.vala -C
vala-dpap-record.vala:120.3-120.42: warning: unhandled error `GLib.FileError'
GLib.FileUtils.get_data (path, out data);

vala-dmap-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'
db.add (((DMAP.Record) record));
^^
vala-dmap-db.vala:27.2-27.46: vala-dmap-db.vala:31.10-31.16: error: The name 
`size' does not exist in the context of `ValaDMAPDb.db'
return db.size;
   ^^^
vala-dmap-db.vala:43.10-43.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
vala-dmap-db.vala:48.19-48.25: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
for (i = 0; i < db.size; i++) {
^^^
error: Cannot convert from 
`Gee.ArrayList'vala-dmap-db.vala:58.10-58.15: error: The name 
`get' does not exist in the context of `ValaDMAPDb.db'
return db.get ((int) id - 1);
   ^^
vala-dmap-container-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
 to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
vala-dmap-container-db.vala:30.10-30.16: error: The name `size' does not exist 
in the context of `ValaDMAPContainerDb.db'
return db.size;
   ^^   ^
^^^vala-dmap-container-db.vala:35.19-35.25: 
^^
vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'error: The name `size' does not exist in the context 
of `ValaDMAPContainerDb.db'
for (i = 0; i < db.size; i++) {
^^^

db.add (((DMAP.Record) record));
dmapserve.vala:34.40-34.43: ^^
vala-dmap-db.vala:31.10-31.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
warning: Argument 2: Cannot pass null to non-null parameter type
vala-dmap-db.vala:43.10-43.16: error: The name  share = new DPAP.Share 
("dmapserve", null, db, container_db, null);
 
dmapserve.vala:34.64-34.67: warning: Argument 5: Cannot pass null to non-null 
parameter type
share = new DPAP.Share ("dmapserve", null, db, container_db, 
null);
 

`size' does not exist in the context of 
`ValaDMAPDb.db'dmapserve.vala:57.6-57.32: 
return db.size;
   ^^^
warning: unhandled error `GLib.Error'
vala-dmap-db.vala:48.19-48.25: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
for (i = 0; i < db.size; i++) {
^^^
var dmapcopy = new DPAPServe ();
^^^vala-dmap-db.vala:58.10-58.15: error: The name `get' does not 
exist in the context of `ValaDMAPDb.db'
return db.get ((int) id - 1);
   ^^

Compilation failed: 9 error(s), 4 warning(s)
vala-dpap-record.vala:120.3-120.42: warning: unhandled error `GLib.FileError'
GLib.FileUtils.get_data (path, out data);

dmapcopy.vala:95.6-95.31: warning: unhandled error `GLib.Error'
var dmapcopy = new DPAPCopy 

[Touch-packages] [Bug 1823423] [NEW] ibus ftbfs in disco

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco-
amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz

multiple vala/glib errors

** Affects: ibus (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Tags added: ftbfs rls-dd-incoming

** Changed in: ibus (Ubuntu)
   Importance: Undecided => High

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

Title:
  ibus ftbfs in disco

Status in ibus package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco-
  amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz

  multiple vala/glib errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1823423/+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 1823422] [NEW] heimdal ftbfs in disco

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco-
amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz

=
   Heimdal 7.5.0: lib/hx509/test-suite.log
=

# TOTAL: 16
# PASS:  15
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test_chain


cert -> root
cert -> root
cert -> root
sub-cert -> root
sub-cert -> sub-ca -> root
sub-cert -> sub-ca
sub-cert -> sub-ca -> root
sub-cert -> sub-ca -> root
sub-cert -> sub-ca -> root
max depth 2 (ok)
max depth 1 (fail)
ocsp non-ca responder
ocsp ca responder
ocsp no-ca responder, missing cert
ocsp no-ca responder, missing cert, in pool
ocsp no-ca responder, keyHash
ocsp revoked cert
ocsp print reply resp1-ocsp-no-cert
ocsp print reply resp1-ca
ocsp print reply resp1-keyhash
ocsp print reply resp2
ocsp verify exists
ocsp verify not exists
ocsp verify revoked
crl non-revoked cert
FAIL test_chain (exit status: 1)


Testsuite summary for Heimdal 7.5.0

# TOTAL: 16
# PASS:  15
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See lib/hx509/test-suite.log
Please report to https://github.com/heimdal/heimdal/issues

** Affects: heimdal (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Changed in: heimdal (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs rls-dd-incoming

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

Title:
  heimdal ftbfs in disco

Status in heimdal package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco-
  amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz

  =
 Heimdal 7.5.0: lib/hx509/test-suite.log
  =

  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: test_chain
  

  cert -> root
  cert -> root
  cert -> root
  sub-cert -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  max depth 2 (ok)
  max depth 1 (fail)
  ocsp non-ca responder
  ocsp ca responder
  ocsp no-ca responder, missing cert
  ocsp no-ca responder, missing cert, in pool
  ocsp no-ca responder, keyHash
  ocsp revoked cert
  ocsp print reply resp1-ocsp-no-cert
  ocsp print reply resp1-ca
  ocsp print reply resp1-keyhash
  ocsp print reply resp2
  ocsp verify exists
  ocsp verify not exists
  ocsp verify revoked
  crl non-revoked cert
  FAIL test_chain (exit status: 1)

  
  Testsuite summary for Heimdal 7.5.0
  
  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See lib/hx509/test-suite.log
  Please report to https://github.com/heimdal/heimdal/issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1823422/+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 1823420] [NEW] audit ftbfs in disco

2019-04-05 Thread Matthias Klose
Public bug reported:

https://launchpadlibrarian.net/417924448/buildlog_ubuntu-
disco-i386.audit_1%3A2.8.3-1ubuntu3_BUILDING.txt.gz

gcc -DHAVE_CONFIG_H -I. -I../../../lib -I..  -I. -I../../.. -I../../../auparse  
'-DTABLE_H="flagtab.h"' -g -O2 -c -o gen_flagtabs_h-gen_tables.o `test -f 
'gen_tables.c' || echo '../../../lib/'`gen_tables.c
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
 #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
 
In file included from ../../../lib/libaudit.h:35,
 from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous 
definition
 #define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
 
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
 #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
 
In file included from ../../../lib/libaudit.h:35,
 from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous 
definition
 #define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
 
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
 #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
 
In file included from ../../../lib/libaudit.h:35,
 from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous 
definition
 #define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
 
In file included from ../../../lib/gen_tables.c:40:
../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
 #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
 
In file included from ../../../lib/libaudit.h:35,
 from ../../../lib/gen_tables.c:40:
/usr/include/linux/audit.h:161: note: this is the location of the previous 
definition
 #define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
 
../../../lib/libaudit.h:292:30: error: ‘AUDIT_FILTER_EXCLUDE’ undeclared here 
(not in a function)
 #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
  ^
../../../lib/gen_tables.c:89:23: note: in definition of macro ‘_S’
 #define _S(VAL, S) { (VAL), (S), 0, 0 },
   ^~~
../../../lib/flagtab.h:26:4: note: in expansion of macro ‘AUDIT_FILTER_EXCLUDE’
 _S(AUDIT_FILTER_EXCLUDE, "exclude"   )
^~~~
make[4]: *** [Makefile:1003: gen_flagtabs_h-gen_tables.o] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/debian/build/lib'
make[3]: *** [Makefile:469: all-recursive] Error 1

** Affects: audit (Ubuntu)
 Importance: High
 Status: New


** Tags: ftbfs rls-dd-incoming

** Tags added: ftbfs

** Tags added: rld-dd-incoming

** Tags removed: rld-dd-incoming
** Tags added: rls-dd-incoming

** Changed in: audit (Ubuntu)
   Importance: Undecided => High

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

Title:
  audit ftbfs in disco

Status in audit package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924448/buildlog_ubuntu-
  disco-i386.audit_1%3A2.8.3-1ubuntu3_BUILDING.txt.gz

  gcc -DHAVE_CONFIG_H -I. -I../../../lib -I..  -I. -I../../.. 
-I../../../auparse  '-DTABLE_H="flagtab.h"' -g -O2 -c -o 
gen_flagtabs_h-gen_tables.o `test -f 'gen_tables.c' || echo 
'../../../lib/'`gen_tables.c
  In file included from ../../../lib/gen_tables.c:40:
  ../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
   #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
   
  In file included from ../../../lib/libaudit.h:35,
   from ../../../lib/gen_tables.c:40:
  /usr/include/linux/audit.h:161: note: this is the location of the previous 
definition
   #define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
   
  In file included from ../../../lib/gen_tables.c:40:
  ../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
   #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
   
  In file included from ../../../lib/libaudit.h:35,
   from ../../../lib/gen_tables.c:40:
  /usr/include/linux/audit.h:161: note: this is the location of the previous 
definition
   #define AUDIT_FILTER_EXCLUDE 0x05 /* Apply rule before record creation */
   
  In file included from ../../../lib/gen_tables.c:40:
  ../../../lib/libaudit.h:292: warning: "AUDIT_FILTER_EXCLUDE" redefined
   #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
   
  In file included from ../../../lib/libaudit.h:35,
   from ../../../lib/gen_tables.c:40:
  /usr/include/linux/audit.h:161: note: this is the location of the previous 
definition
   #define AUDIT_FILTER_EXCLUDE 0x05 /* 

[Touch-packages] [Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain

2019-04-05 Thread Matthias Klose
these were all done already in September 2018.

** Changed in: gcc-7-cross (Ubuntu)
   Status: New => Fix Released

** Changed in: gcc-8-cross (Ubuntu)
   Status: New => Fix Released

** Changed in: gcc-defaults (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Enable arm-linux-gnueabi target on ppc64el toolchain

Status in The Ubuntu-power-systems project:
  Incomplete
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-7-cross package in Ubuntu:
  Fix Released
Status in gcc-8-cross package in Ubuntu:
  Fix Released
Status in gcc-defaults package in Ubuntu:
  Fix Released

Bug description:
  Dear Canonical.

  We would like to have arm-linux-gnueabi target on ppc64el cross
  toolchain. This would enable us to use a ppc64el host to do cross
  compilation for aarch64.

  I talked to Matthias Klose already, and he is aware of this request.

  Thank you,
  Breno

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1786940/+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 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-05 Thread Seth Arnold
Root, aha! We've finally uncovered the root of the problem. (Sorry. I
can't help myself. It's Friday afternoon.)

While Qualys' TLS scanner is a top-notch tool that I use regularly,
their "security scanner" is sadly not. They have built a tool that
checks version numbers. This is not ideal, because the clear majority of
Linux systems do not do wholesale version updates but instead backport
specific security fixes:

https://wiki.ubuntu.com/SecurityTeam/FAQ#Versions
https://www.debian.org/security/faq#version
https://wiki.centos.org/FAQ/General#head-3dad8cb98ac535185e58e882a23ca4b096cbff2f
https://access.redhat.com/security/updates/backporting

These sorts of security scanners would be more useful if everyone built
their entire systems from scratch.

Anyway, please ask Qualys to consider consuming our OVAL data:
https://people.canonical.com/~ubuntu-security/oval/
or parsing our database directly:
https://git.launchpad.net/ubuntu-cve-tracker

Both of these approaches would give better results. (There are tradeoffs
involved. They are welcome to contact us at secur...@ubuntu.com if they
would like to discuss the tradeoffs.)

Thanks

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  Fix Released

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled

2019-04-05 Thread b
If I remove the bluez package there are no issues with suspend.

** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

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

Title:
  Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is
  still enabled

Status in bluez package in Ubuntu:
  New

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2019-04-05 Thread Brian Murray
This is still an issue with gdb version 8.2.90.20190311-0ubuntu1 in
disco.

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in gdb package in Ubuntu:
  New

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+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 1623530] Re: Apport should be disabled by default

2019-04-05 Thread Brian Murray
Bug 1778497 is about having a remember feature in apport which gives the
user a way to say never report crashes or always report crashes. This
feature is available in 18.04 and on. Could you please test it and see
if it helps address your concerns? Thanks!

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1623530/+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 1822370] Re: 19.04 beta openssh-client broken pipe

2019-04-05 Thread Brian Murray
** Also affects: openssh (Ubuntu Disco)
   Importance: Critical
 Assignee: Colin Watson (cjwatson)
   Status: Triaged

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Disco:
  Triaged
Status in openssh package in Debian:
  New

Bug description:
  New versions of openssh (as in Ubuntu 19.04) are reported to trigger a
  connection issue:

 packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  In most of the cases this seems to affect VMWare based environments as
  there is a bug in their implementation in regard to the traffic
  shaping protocols.

  Until resolved by VMWare the workarounds for now are:

  Configure your client to use the old defaults permanently in
  =>  /etc/ssh/ssh_config 
  Host *
  IPQoS lowdelay throughput 
  # You might want to limit to your VMware based systems

  Or per command via:
   $ ssh IPQoS="latency throughput" user@host

  Two values as one is for interactive and one for non-interactive use
  cases.

   original report 

  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-05 Thread Steve Langasek
needs a test case for libnet-ssleay-perl.

** Also affects: libnet-ssleay-perl (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: libnet-ssleay-perl (Ubuntu)

** Changed in: libnet-ssleay-perl (Ubuntu Bionic)
   Status: New => Incomplete

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  Incomplete
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Test cases for the python updates]

  python3.7 is a preview in bionic as a non-supported/non-default
  version of python3. Passing it's own autopkgtests is sufficient
  validation for python3.7. It includes a point release update, with
  OpenSSL 1.1.1 compat and features.

  python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
  also includes a point release update to 3.6.8. It has been part of the
  full-archive rebuild and regression analysis. Autopkgtests were
  triggered for python3.6 and python3-defaults with regressions already
  fixed in the individual packages as appropriate.

  python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
  compat only. It has been part of the full-archive rebuild and
  regression analysis. Autopkgtests were triggered for python2.7 and
  python-defaults with regressions already fixed in the individual
  packages as appropriate.

  The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 
and python point releases as seen in:
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html

  And analyzed in
  
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.

     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.

   * This update bundles python 3.6 and 3.7 point releases

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

  [Autopkgtest Regressions]

  dovecot/armhf - flakey

  libnet-ssleay-perl - awaiting sru accept into proposed of
  libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
  versioned breaks.

  linux* - rebuild testcases passes (for some 

[Touch-packages] [Bug 1823404] [NEW] Memory errors reported by valgrind for gdebi-gtk

2019-04-05 Thread Elias Rudberg
Public bug reported:

This is for gdebi version 0.9.5.7+nmu2.

When running gdebi-gtk through valgrind, for example like this:

valgrind gdebi-gtk -h

that shows lots of memory errors, for example:
- Conditional jump or move depends on uninitialised value(s)
- Use of uninitialised value of size 8
- Invalid read of size 4
- Address 0x4e68020 is 304 bytes inside a block of size 2,208 free'd

and so on. So there are bugs in the code that can cause the program to crash.
One example of a used that got a crash is here:
https://askubuntu.com/questions/1131516/gdebi-gtk-segmentation-fault-core-dumped

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

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

Title:
  Memory errors reported by valgrind for gdebi-gtk

Status in gdebi package in Ubuntu:
  New

Bug description:
  This is for gdebi version 0.9.5.7+nmu2.

  When running gdebi-gtk through valgrind, for example like this:

  valgrind gdebi-gtk -h

  that shows lots of memory errors, for example:
  - Conditional jump or move depends on uninitialised value(s)
  - Use of uninitialised value of size 8
  - Invalid read of size 4
  - Address 0x4e68020 is 304 bytes inside a block of size 2,208 free'd

  and so on. So there are bugs in the code that can cause the program to crash.
  One example of a used that got a crash is here:
  
https://askubuntu.com/questions/1131516/gdebi-gtk-segmentation-fault-core-dumped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1823404/+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 1815509] Re: Shutdown hung by firmware update daemon

2019-04-05 Thread Mario Limonciello
Thanks for the comment. If it's gone with disco I'll close this.

Please anyone who encounters it, turn on fwupd verbose logging so we can
figure out what is happening if it's fwupd.

It's also possible this is the last visible message but it's some other
script running at this time. This will be evidenced in a verbose log.

** Changed in: fwupd (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1823398] [NEW] setvtrgb causes boot delays in clouds

2019-04-05 Thread Steve Langasek
Public bug reported:

systemd-analyze output of cloud images shows that setvtrgb.service can
take a measureable amount of time to complete.  Setting the color
pallete for a graphical console on a cloud instance that we have no
graphical console access to is not something that should be allowed to
slow down boot.

Reproduced with disco on a Google GCE instance of type N1_Standard_2.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  setvtrgb causes boot delays in clouds

Status in console-setup package in Ubuntu:
  New

Bug description:
  systemd-analyze output of cloud images shows that setvtrgb.service can
  take a measureable amount of time to complete.  Setting the color
  pallete for a graphical console on a cloud instance that we have no
  graphical console access to is not something that should be allowed to
  slow down boot.

  Reproduced with disco on a Google GCE instance of type N1_Standard_2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1823398/+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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

2019-04-05 Thread Mike Clark
I have an identical setup and problem.

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+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 1659534] Reminder of SRU verification policy change

2019-04-05 Thread Brian Murray
Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Committed

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659534/+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 1719612] Re: non-us keyboard layout not setup in initramfs

2019-04-05 Thread Steve Langasek
** Changed in: console-setup (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  non-us keyboard layout not setup in initramfs

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Artful:
  Won't Fix

Bug description:
  Description:Ubuntu Artful Aardvark (development branch)
  Release:17.10

  In Artful the /etc/console/cached.kmap.gz file does not exists, in its place, 
it uses some files with more precise names susch as cached_UTF-8_del.kmap.gz. 
However the initramfs scripts still uses cached.kmap.gz . The consequence is 
that the keyboard layout remains US in the initramfs which is a problem for 
full encrypted installation when entering passphrase.
  Proposed solution is to make a symbolic link from  cached_UTF-8_del.kmap.gz 
to cached.kmap.gz. Then the initramfs tools will find the 
/etc/console/cached.kmap.gz file and includes it in the initramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1719612/+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 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]

2019-04-05 Thread Steve Langasek
I don't understand why you are (were) seeing a bug here.  There are
several other units that declare themselves After=plymouth-quit-
wait.service without After=plymouth-quit.service, including getty
itself, and I'm not aware of any reports that getty fails to start for
users because of this race.  This sounds to me like a bug in the
calamares-based ISO and its integration with the existing standard
systemd units in Ubuntu, not a bug in console-setup.

** Changed in: console-setup (Ubuntu)
   Status: New => Incomplete

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

Title:
  setvtrgb.service incorrectly ordered [with patchy]

Status in console-setup package in Ubuntu:
  Incomplete

Bug description:
  setvtrgb is not correctly ordered when used with plymouth. It has an 
After=plymouth-quit-wait.service, but that may not be applicable when 
plymouth-quit.service is queued instead. This ultimately results in semi-random 
setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't 
up/still getting fiddled with with by plymouth. So, depending on the unit tree 
the VT may have the correct custom color, or the default kernel color.
  Since this is entirely dependent on the units being started, and their 
effective order, this is super hard to reproduce reliably. The most reliable 
way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead 
of GDM, which 100% of the time ends up having a unit order where setvtrgb is 
called way too soon (even before getty.target, although I am not sure that 
matters as far as the VT colors are concerned).

  The solution seems excitingly simple though. Adding an After=plymouth-
  quit.service rule correctly orders the unit at least in my test case.
  Since After is only an order hint this should be entirely regression
  free.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+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


Re: [Touch-packages] [Bug 1746585] Re: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all

2019-04-05 Thread Ryan
Hi Daniel,

Thank you for reaching out. I ran

sudo apt remove timidity*

and then rebooted. It did not fix the issue.


Thanks,

-- Ryan Viertel


On Sun, Mar 31, 2019 at 11:40 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Please try uninstalling 'timidity' and all 'timidity' related packages.
> Then reboot.
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746585
>
> Title:
>   [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at
>   all
>
> Status in alsa-driver package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Speakers and HDMI sound work fine, only headphones not working. I went
>   through all of the steps on
>
>   https://help.ubuntu.com/community/SoundTroubleshootingProcedure
>   https://help.ubuntu.com/community/SoundTroubleshooting
>   and
>   https://wiki.ubuntu.com/DebuggingSoundProblems
>
>   and submitted this report with ubuntu-bug -s audio
>
>   Some possibly relevant information: This installation of Ubuntu was
>   originally installed on a Dell Inspiron 15, but I cloned the partition
>   onto an SSD that I installed on the Latitude 6420. It is the Latitude
>   that is affected, the headphones work fine on the Inspiron.
>
>   Let me know if any more information is required.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
>   Uname: Linux 4.13.0-32-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
>/dev/snd/controlC0:  rviertel   2881 F pulseaudio
> rviertel   4589 F alsamixer
>   CurrentDesktop: Unity
>   Date: Wed Jan 31 12:22:17 2018
>   InstallationDate: Installed on 2015-04-27 (1009 days ago)
>   InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150218.1)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Symptom_DevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
>/dev/snd/controlC0:  rviertel   2881 F pulseaudio
> rviertel   4589 F alsamixer
>/dev/snd/seq:timidity   1191 F timidity
>   Symptom_Jack: Black Headphone Out, Left
>   Symptom_Type: No sound at all
>   Title: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No
> sound at all
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/11/2011
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A06
>   dmi.board.name: 0K0DNP
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A02
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Latitude E6420
>   dmi.product.version: 01
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1746585/+subscriptions
>

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

Title:
  [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Speakers and HDMI sound work fine, only headphones not working. I went
  through all of the steps on

  https://help.ubuntu.com/community/SoundTroubleshootingProcedure
  https://help.ubuntu.com/community/SoundTroubleshooting
  and
  https://wiki.ubuntu.com/DebuggingSoundProblems

  and submitted this report with ubuntu-bug -s audio

  Some possibly relevant information: This installation of Ubuntu was
  originally installed on a Dell Inspiron 15, but I cloned the partition
  onto an SSD that I installed on the Latitude 6420. It is the Latitude
  that is affected, the headphones work fine on the Inspiron.

  Let me know if any more information is required.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rviertel   2881 F...m pulseaudio
   /dev/snd/controlC0:  rviertel   2881 F pulseaudio
    rviertel   4589 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Jan 31 

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2019-04-05 Thread Till Kamppeter
The patch got also merged into the 3.24 branch of GTK:

https://gitlab.gnome.org/GNOME/gtk/merge_requests/717

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not 

[Touch-packages] [Bug 1823382] [NEW] backport openssl 1.1.1 fixes to bionic and cosmic

2019-04-05 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * neon27 doesn't work with openssl 1.1.1
 * backport fixes from disco to cosmic and bionic to resolve that

[Test Case]

 * does not FTBFS

[Regression Potential]

 * currently broken in cosmic, and will break once openssl is upgraded
in bionic, so for all practical purposes it's completely busted at the
moment.

[Other Info]
 
 * Fixes already in disco and unstable.

** Affects: neon27 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: neon27 (Ubuntu Bionic)
 Importance: Undecided
 Status: In Progress

** Affects: neon27 (Ubuntu Cosmic)
 Importance: Undecided
 Status: In Progress

** Affects: neon27 (Ubuntu Disco)
 Importance: Undecided
 Status: Fix Released

** Also affects: neon27 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: neon27 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: neon27 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: neon27 (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: neon27 (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: neon27 (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

Status in neon27 package in Ubuntu:
  Fix Released
Status in neon27 source package in Bionic:
  In Progress
Status in neon27 source package in Cosmic:
  In Progress
Status in neon27 source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/1823382/+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 1823354] Re: printer is no longer visable

2019-04-05 Thread Sebastien Bacher
Thank you for your bug report. Could you make a screenshot showing the
issue? What printer do you use and how is it connected to the system?

** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  printer is no longer visable

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  This is what system sais when I click on Printers in system settings for 
Ubuntu
  Sorry! The system printing service doesnt seem to be available

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Apr  5 10:33:13 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0501]
  InstallationDate: Installed on 2019-03-12 (23 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=3e6b4fed-11bf-458e-bda1-131b0681e85c ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-UD3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-UD3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823354/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-05 Thread Derk Willem te Bokkel
just some summary thoughts in addition to point to some anomalies ..

the "failures in lightdm appear to correspond with shorter journal logs .. 
so certain processes are not running as expected .. 

plymouth also does not appear on the screen .. 
as it needs the proper graphics support ..

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More 

[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-05 Thread Dimitri John Ledkov
** Description changed:

  [Impact]
  
   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.
  
   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
  rapidly adopted due to increased set of supported hashes & algoes, as
  well as improved handshake [re-]negotiation.
  
   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
  
   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software
  is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.
  
  [Test Case]
  
   * Rebuild all reverse dependencies
  
   * Execute autopkg tests for all of them
  
   * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g.
  mongodb)
  
   * Backport TLS v1.3 support patches, where applicable
  
  [Test cases for the python updates]
  
  python3.7 is a preview in bionic as a non-supported/non-default
  version of python3. Passing it's own autopkgtests is sufficient
  validation for python3.7. It includes a point release update, with
  OpenSSL 1.1.1 compat and features.
  
  python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
  also includes a point release update to 3.6.8. It has been part of the
  full-archive rebuild and regression analysis. Autopkgtests were
  triggered for python3.6 and python3-defaults with regressions already
  fixed in the individual packages as appropriate.
  
  python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
  compat only. It has been part of the full-archive rebuild and
  regression analysis. Autopkgtests were triggered for python2.7 and
  python-defaults with regressions already fixed in the individual
  packages as appropriate.
+ 
+ The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 
and python point releases as seen in:
+ 
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
+ 
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html
+ 
+ And analyzed in
+ 
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652
  
  [Regression Potential]
  
   * Connectivity interop is the biggest issues which will be unavoidable
  with introducing TLS v1.3. However, tests on cosmic demonstrate that
  curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3
  without issues.
  
   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side software
  or by backporting relevant support fixes
  
   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3
  
   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.
  
     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.
  
   * This update bundles python 3.6 and 3.7 point releases
  
  [Other Info]
  
   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092
  
   * TLS v1.3 support in NSS is expected to make it to 18.04 via security
  updates
  
   * TLS v1.3 support in GnuTLS is expected to be available in 19.04
  
   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473
  
  [Autopkgtest Regressions]
  
  dovecot/armhf - flakey
  
  libnet-ssleay-perl - awaiting sru accept into proposed of
  libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
  versioned breaks.
  
  linux* - rebuild testcases passes (for some edge flavours the build
  fails in non-ssl portions of the build), ubuntu-regression-suite
  testcase fails for a few variants but should have been skipped (in
  progress to be fixed in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056)
  
  openvswitch/i386 - extremely flakey, errors out or fails mostly

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed

[Touch-packages] [Bug 1823380] Re: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2019-04-05 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  was able to boot into ubuntu generic but unable to boot into regular
  mode

  would get flip_done time out if I attempted to boot normally

  Computer is dual booted with Windows 7

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: policykit-1 0.105-14.1ubuntu0.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Apr  5 13:08:57 2019
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2019-01-15 (80 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: policykit-1
  Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1823380/+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 1823380] [NEW] package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2019-04-05 Thread bryan
Public bug reported:

was able to boot into ubuntu generic but unable to boot into regular
mode

would get flip_done time out if I attempted to boot normally

Computer is dual booted with Windows 7

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: policykit-1 0.105-14.1ubuntu0.4
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Apr  5 13:08:57 2019
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2019-01-15 (80 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: policykit-1
Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  was able to boot into ubuntu generic but unable to boot into regular
  mode

  would get flip_done time out if I attempted to boot normally

  Computer is dual booted with Windows 7

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: policykit-1 0.105-14.1ubuntu0.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Apr  5 13:08:57 2019
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2019-01-15 (80 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: policykit-1
  Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1823380/+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 1697959] Re: late package version collection can cause confusion

2019-04-05 Thread Brian Murray
When looking at bug 1822395 it occurred to me that this could also be an
issue if an application were to crash during the release upgrade process
and the data collection were done after the upgrade.

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

Title:
  late package version collection can cause confusion

Status in apport package in Ubuntu:
  New

Bug description:
  The following OOPS contains some misinformation:

  https://errors.ubuntu.com/oops/3680877e-5046-11e7-89b7-fa163e54c21f

  The Date field is from before the package version in the report was
  accepted into -proposed. This likely happened because the .crash file
  was created and data collection, including adding the Package key, was
  done after systemd had been upgraded. This is alluded to in the
  UnreportableReason of the OOPS.

  UnreportableReason:
  Неполадка произошла с программой /lib/systemd/systemd-resolved, в которую 
были внесены изменения с момента её аварийного завершения работы.

  It says that systemd-resolved was modified since the error occurred.

  As we can see in bug 1621396 this ended up confusing the developer and
  they were concerned about their fix not working. It seems like apport
  or whoopsie should do something better here.

  Ideas include not putting a package version in the Package field if
  the binary has been modified, or not uploading the crash to the Error
  Tracker if the binary has changed.  The latter would require some
  additional work because the UnreportableReason is translated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697959/+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 1823376] [NEW] Please add ${distro_id}ESM:${distro_codename}-security to allowed origins (on Ubuntu)

2019-04-05 Thread Balint Reczey
Public bug reported:

.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823376/+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 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install

2019-04-05 Thread Balint Reczey
The error is still not seen in Xenial's 1.1ubuntu1.18.04.7~16.04.2:

https://errors.ubuntu.com/?package=unattended-
upgrades=year=1.1ubuntu1.18.04.7~16.04.2

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-
  upgrade@1927:main:do_install

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades can be crashing when packages are marked for removal 
after collecting upgradable packages.
   * The fix clear the cache when it may be in an invalid state to lose 
markings.

  [Test Case]

   * Observe
  https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2
  not occurring in fixed versions.

  [Regression Potential]

   * The extra cache.clear() can take extra CPU time when invoked
  needlessly or can cause skipping updates when invoked at the wrong
  time. However the fix received extensive testing in newer releases
  making unnoticed regressions unlikely to surface.

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1782, in main
  logfile_dpkg)
    File "/usr/bin/unattended-upgrade", line 1057, in do_install
  "removal:%s" % "".join([pkg.name for pkg in marked_delete]))
  AssertionError: Internal error. The following packages are marked for 
removal:linux-headers-4.15.0-20-generic

  Also seen as:
  https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1775292] Re: Unattended-upgrades stopped adjusting candidates in 1.1

2019-04-05 Thread Balint Reczey
1.1ubuntu1.18.04.7~16.04.2 passes, too:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190228_150449_11313@/log.gz

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  Unattended-upgrades stopped adjusting candidates in 1.1

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades may fail to install an update when the highest
  version of a package to be updated exists in an origin u-u is not
  allowed to pull packages from.

  [Test Case]

   * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
   * Observe no line with "adjusting candidate version: " with buggy u-u version
   * Install fixed u-u version
   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting candidate version: "

  [Regression Potential]

   * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775292/+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 1781446] Re: Autopkgtest upgrade-all-security is failing due to apt printing to stderr in Bionic

2019-04-05 Thread Balint Reczey
Really:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190228_150449_11313@/log.gz

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

Title:
  Autopkgtest upgrade-all-security is failing due to apt printing to
  stderr in Bionic

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact] 
   * The following error can be seen in autopkgtest, holding back u-u from 
migration:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180712_151033_c44d8@/log.gz
 :
  ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ...
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  Reading package lists...
  ...
  autopkgtest [14:17:33]: test upgrade-all-security:  - - - - - - - - - - 
results - - - - - - - - - -
  upgrade-all-security FAIL stderr: W: APT had planned for dpkg to do more than 
it reported back (2370 vs 2372).
  autopkgtest [14:17:34]: test upgrade-all-security:  - - - - - - - - - - 
stderr - - - - - - - - - -
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  autopkgtest [14:17:34]: test upgrade-between-snapshots: preparing testbed
  ...

  [Test Case]

   * upgrade-all-security autopkgtest

  [Regression Potential]

   * Valid errors manifesting themselves only as output from stderr may
  not fail the autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781446/+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 1773033] Re: unattended upgrade no longer actions on shutdown (when started on battery)

2019-04-05 Thread Balint Reczey
** Summary changed:

- unattended upgrade no longer actions on shutdown
+ unattended upgrade no longer actions on shutdown (when started on battery)

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

Title:
  unattended upgrade no longer actions on shutdown (when started on
  battery)

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades does not install upgrades when it is configured
  to install updates on shutdown and when it the system is started on
  battery, but installs updates on battery in other cases.

   * This behaviour is unintended and confuses users, moreover
  installing updates on battery risks the system to be shut down in the
  middle of an upgrade due to depleting the battery.

   * This upload changes u-u to skip updates or gracefully stop when the
  system is switching to batter-powered state by default minimizing the
  risk of breaking the system.

  [Test Case]

   * Run "unattended-upgrade --dry-run --verbose" on battery and on AC
  power

   * With default configuration u-u should stop with the following message on 
battery:
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  System is on battery power, stopping

   * On AC power it should continue:
  $ sudo ./unattended-upgrade --dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

   * Add the following configuration file and check u-u continuing even on 
battery:
  $ cat /etc/apt/apt.conf.d/51unattended-upgrades-on-battery 
  Unattended-Upgrade::OnlyOnACPower "false";
  rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo ./unattended-upgrade 
--dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

  
  [Regression Potential] 

   * Unattended-upgrades may fail to install updates even on AC power,
  but this is unlikely to happen due to the code changed being fairly
  simple. on_ac_power may return 255 (false) Power status could not be
  determined, but this is mapped to being on AC power and installing the
  updates, only subprocess.call("on_ac_power") == 1 makes u-u skip
  updates.

  [Original Bug Text]

  Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
  flag set.

  post-install script on 14.04 and 16.04 would set options in
  /etc/apt/apt.conf.d/50unattended-upgrades and
  /etc/apt/apt.conf.d/10periodic to install updates on shutdown of
  ubuntu desktop. This worked on 17.10 also, until an update before the
  release of 18.04. After a fresh install of 18.04, ran the post install
  script. Below is the contents of the two files, updates do not run,
  even if performing an apt update and leaving the machine up for a few
  hours to download packages in the back ground. Both the unattended-
  upgrades and unattended-upgrades-shutdown log files are empty.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ii  unattended-upgrades1.1ubuntu1
  all  automatic installation of security upgrades

  
--/etc/apt/apt.conf.d/50unattended-upgrades
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESM:${distro_codename}";
  "${distro_id}:${distro_codename}-updates";
  //  "${distro_id}:${distro_codename}-proposed";
  //  "${distro_id}:${distro_codename}-backports";
  "LP-PPA-libreoffice:${distro_codename}";
  "Canonical:${distro_codename}";
  };

  Unattended-Upgrade::Package-Blacklist {
  //  "vim";
  //  "libc6";
  //  "libc6-dev";
  //  "libc6-i686";
  };

  Unattended-Upgrade::DevRelease "false";
  Unattended-Upgrade::InstallOnShutdown "true";
  Unattended-Upgrade::Remove-Unused-Dependencies "true";

  

[Touch-packages] [Bug 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades

2019-04-05 Thread Balint Reczey
Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial:


root@x-uu-verify:~# grep -B1 please 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
msg = _("Unattended-upgrade in progress during shutdown, "
"please don't turn off the computer")
--
_("To enable monitoring the PrepareForShutdown() signal "
  "instead of polling please install the python3-gi package"))
root@x-uu-verify:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all  automatic 
installation of security upgrades


** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  Wrong/confuse text on shutdown at unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The confusing text on shutdown is, well, can confuse users.
   * This fix itself is minor and would not warrant a backport but it is 
backported as part of fully backporting Bionic's u-u version to Xenial.

  [Test Case]

   * Check that the status text is less confusing than it was previously
  either by configuring unattended-upgrades to run at shutdown and
  waiting for the text to appear or check that the text is changed in
  unattended-upgrades-shutdown:

  $ grep -B1 please /usr/share/unattended-upgrades/unattended-upgrade-shutdown 
  msg = _("Unattended-upgrade in progress during shutdown, "
  "please don't turn off the computer")

* The former way or the verification may not be easy since with the fix for 
LP: #1803137 the shutdown screen does not show up when u-u-shutdown starts 
running, see the bug for the details.
* Also checking unatttended-upgrades-shutdown for the changed text does not 
ensure that the translation is ready, too.

  [Regression Potential]

   * The updated text should not cause major issues, but until it is
  translated to each language it is shown in English, possibly confusing
  users in a different way.

  [Original Bug Text]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades-0.90ubuntu0.9
  Uname: 4.4.0-104-generic #127-Ubuntu SMP
  Architecture: amd64

  I've german systems, so when updates will be installed at shutdown
  this text will be displayed at the screen.

  German:
  "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf 
Sekunden lange gewartet"

  English:
  "unattended upgrade runs during the shutdown, it waits for five seconds"

  This sentence make absolutly no sence for me. Maybe it is an 
translationproblem? Don't know text on the english ubuntuversion.
  The problem is that some customer turned of some computers, because the 
updates need more time then 5 seconds ;)

  A better message will that was Windows10 displays at shutdown ...don't
  turn off the computer, updates will be installed...

  Thanks and best Reagards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1741579/+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 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

2019-04-05 Thread Balint Reczey
Verified with 1.1ubuntu1.18.04.7~16.04.2 on Xenial:

...
2019-04-05 16:17:32,704 INFO Initial blacklisted packages: ebtables
2019-04-05 16:17:32,705 INFO Initial whitelisted packages: 
2019-04-05 16:17:32,705 INFO Starting unattended upgrades script
2019-04-05 16:17:32,705 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial
...
2019-04-05 16:17:33,813 DEBUG Checking: busybox-static ([, ])
2019-04-05 16:17:33,960 DEBUG Checking: ebtables ([])
2019-04-05 16:17:33,962 DEBUG adjusting candidate version: 
ebtables=2.0.10.4-3.4ubuntu1
2019-04-05 16:17:34,660 DEBUG pkgs that look like they should be upgraded: 
busybox-static
2019-04-05 16:17:34,712 DEBUG fetch.run() result: 0
...
2019-04-05 16:17:37,879 INFO All upgrades installed


>From r...@x-uu-verify.lxd Fri Apr 05 16:17:38 2019
Return-path: 
Envelope-to: r...@x-uu-verify.lxd
Delivery-date: Fri, 05 Apr 2019 16:17:38 +
Received: from root by x-uu-verify.lxd with local (Exim 4.86_2)
(envelope-from )
id 1hCRX8-0004lu-Pd
for r...@x-uu-verify.lxd; Fri, 05 Apr 2019 16:17:38 +
Subject: [reboot required] unattended-upgrades result for x-uu-verify: True
To: r...@x-uu-verify.lxd
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: root 
Message-Id: 
Date: Fri, 05 Apr 2019 16:17:38 +

Unattended upgrade returned: True

Warning: A reboot is required to complete this upgrade.

Packages that were upgraded:
 busybox-static=20


Package installation log:
Log started: 2019-04-05  16:17:35
Preparing to unpack .../busybox-static_1%3a1.22.0-15ubuntu1.4_amd64.deb ...
Unpacking busybox-static (1:1.22.0-15ubuntu1.4) over (1:1.22.0-15ubuntu1) .=
..
Processing triggers for man-db (2.7.5-1) ...
Setting up busybox-static (1:1.22.0-15ubuntu1.4) ...
Log ended: 2019-04-05  16:17:37


Unattended-upgrades log:
...

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

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

Status in unattended-upgrades:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * Listing the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
    apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
    liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
    python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
    unattended-upgrades update-manager-core update-notifier-common
  27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 24.1 MB of archives.
  After this operation, 1454 kB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.

  * blacklist ebtables, set up emails from u-u, then run u-u again:
  $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
  $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: ebtables
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Packages that will be upgraded:

  * Observe ebtables listed as being kept back and having upgradable origin 
with buggy u-u:
  $ sudo cat /var/mail/mail
  ...
  Packages with upgradable origin but kept back:
   

[Touch-packages] [Bug 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

2019-04-05 Thread Balint Reczey
The build-time test also passed:

https://launchpadlibrarian.net/413160112/buildlog_ubuntu-xenial-amd64.unattended-upgrades_1.1ubuntu1.18.04.7~16.04.2_BUILDING.txt.gz
 :
...
Running ./test_blacklisted_wrong_origin.py with python3
DEBUG:root:Checking: postgresql ([])
.
--
Ran 1 test in 0.002s

OK
...

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

Status in unattended-upgrades:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * Listing the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
    apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
    liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
    python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
    unattended-upgrades update-manager-core update-notifier-common
  27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 24.1 MB of archives.
  After this operation, 1454 kB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.

  * blacklist ebtables, set up emails from u-u, then run u-u again:
  $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
  $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: ebtables
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Packages that will be upgraded:

  * Observe ebtables listed as being kept back and having upgradable origin 
with buggy u-u:
  $ sudo cat /var/mail/mail
  ...
  Packages with upgradable origin but kept back:
   ebtables=20
  ...

  * Upgrade u-u to a fixed version and run it, observing ebtables to be
  not listed as having upgradable origin

  [Regression Potential]

   * Regressions may make packages incorrectly missing from u-u's
  report, but the autopkgtests also cover that to some extent.

  [Other Info]

   * Original report: https://github.com/mvo5/unattended-
  upgrades/issues/116

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+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 1607845] Re: List of versioned kernels is not right for Ubuntu

2019-04-05 Thread Manfred Hampl
What about packages like

linux-modules-extra-3.13.0-168-generic

Two versions ago (starting with 3.13.0-166) the former linux-image-
extra-* packages have been renamed to linux-modules-extra-*

I do not see any provision for these in /etc/apt/apt.conf.d/01autoremove
and 01autoremove-kernels on my trusty system (apt 1.0.1ubuntu2.23), and
indeed "apt autoremove" deleted the linux-image-extra package belonging
to the "running kernel minus one" kernel version.

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1607845/+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 1607845] Re: List of versioned kernels is not right for Ubuntu

2019-04-05 Thread Julian Andres Klode
Added this to my list of things so I don't forget about it; might look
into it next week.

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

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1607845/+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 1823327] Re: booting cloud images on a Multipass Windows hosted enviroment is slow in the initramfs stage due to font setup / framebuffer issues

2019-04-05 Thread Steve Langasek
/etc/default/console-setup has:
ACTIVE_CONSOLES="/dev/tty[1-6]"
and /usr/share/initramfs-tools/scripts/init-top/console_setup iterates over 
these active consoles.

This is not work that should be done in the initramfs (and I actually
don't see an equivalent setup from the rootfs, which implies we
currently don't get the font setup at all on an initramfsless-booted
system).  In the initramfs we should be initializing at most one VT.

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

Title:
  booting cloud images on a Multipass Windows hosted enviroment is slow
  in the initramfs stage due to font setup / framebuffer issues

Status in cloud-images:
  New
Status in console-setup package in Ubuntu:
  New

Bug description:
  Booting an azure kernel Cosmic cloud image with multipass on Windows
  10 pro takes a long time. Using systemd-analyze 25 seconds in kernel
  boot time is reported. Digging into this, the kernel boot time is
  actually ~5 seconds, the other 20 seconds before systemd init is
  exec'd is actually in the initramfs. I've instrumented the kernel to
  record the exec and exit times of each process in the kernel and the
  top offending processes in initramfs during boot are:

  Duration PID process
  14.86832 262 /scripts/init-top/console_setup
  2.48749 263 /bin/setfont
  2.45357 268 /bin/setfont
  2.44657 291 /bin/setfont
  2.44392 286 /bin/setfont
  2.43545 279 /bin/setfont
  2.43161 274 /bin/setfont
  1.19233 255 /scripts/init-top/framebuffer

  console_setup is calling setfont 7 times and each time setfint is
  taking more than 2.4 seconds to complete. Also the framebuffer program
  is taking over a second to run.

  For Disco with azure kernel:

  Duration PID process
  14.19028 275 console_setup
  2.39020 276 setfont
  2.34020 281 setfont
  2.32915 293 setfont
  2.32389 289 setfont
  2.32319 285 setfont
  2.32178 297 setfont
  1.11417 268 framebuffer

  For Xenial with generic kernel:

  Duration PID process
  15.01832 232 console_setup
  2.52273 233 setfont
  2.50960 238 setfont
  2.48476 250 setfont
  2.46333 256 setfont
  2.46289 262 setfont
  2.44667 268 setfont
  1.07674 225 framebuffer

  For Xenial with azure kernel:
  15.00529 260 console_setup
  2.49699 261 setfont
  2.47591 292 setfont
  2.47443 266 setfont
  2.47131 286 setfont
  2.46812 280 setfont
  2.45780 274 setfont
  1.07095 253 framebuffer

  so it seems to occur across releases with generic and azure kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1823327/+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 1781446] Re: Autopkgtest upgrade-all-security is failing due to apt printing to stderr in Bionic

2019-04-05 Thread Balint Reczey
Tested with 1.1ubuntu1.18.04.7~16.04.2:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190314_133620_f98b4@/log.gz

Still passing.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  Autopkgtest upgrade-all-security is failing due to apt printing to
  stderr in Bionic

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact] 
   * The following error can be seen in autopkgtest, holding back u-u from 
migration:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180712_151033_c44d8@/log.gz
 :
  ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ...
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  Reading package lists...
  ...
  autopkgtest [14:17:33]: test upgrade-all-security:  - - - - - - - - - - 
results - - - - - - - - - -
  upgrade-all-security FAIL stderr: W: APT had planned for dpkg to do more than 
it reported back (2370 vs 2372).
  autopkgtest [14:17:34]: test upgrade-all-security:  - - - - - - - - - - 
stderr - - - - - - - - - -
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  autopkgtest [14:17:34]: test upgrade-between-snapshots: preparing testbed
  ...

  [Test Case]

   * upgrade-all-security autopkgtest

  [Regression Potential]

   * Valid errors manifesting themselves only as output from stderr may
  not fail the autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781446/+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 1823327] Re: booting cloud images on a Multipass Windows hosted enviroment is slow in the initramfs stage due to font setup / framebuffer issues

2019-04-05 Thread Steve Langasek
** Also affects: console-setup (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  booting cloud images on a Multipass Windows hosted enviroment is slow
  in the initramfs stage due to font setup / framebuffer issues

Status in cloud-images:
  New
Status in console-setup package in Ubuntu:
  New

Bug description:
  Booting an azure kernel Cosmic cloud image with multipass on Windows
  10 pro takes a long time. Using systemd-analyze 25 seconds in kernel
  boot time is reported. Digging into this, the kernel boot time is
  actually ~5 seconds, the other 20 seconds before systemd init is
  exec'd is actually in the initramfs. I've instrumented the kernel to
  record the exec and exit times of each process in the kernel and the
  top offending processes in initramfs during boot are:

  Duration PID process
  14.86832 262 /scripts/init-top/console_setup
  2.48749 263 /bin/setfont
  2.45357 268 /bin/setfont
  2.44657 291 /bin/setfont
  2.44392 286 /bin/setfont
  2.43545 279 /bin/setfont
  2.43161 274 /bin/setfont
  1.19233 255 /scripts/init-top/framebuffer

  console_setup is calling setfont 7 times and each time setfint is
  taking more than 2.4 seconds to complete. Also the framebuffer program
  is taking over a second to run.

  For Disco with azure kernel:

  Duration PID process
  14.19028 275 console_setup
  2.39020 276 setfont
  2.34020 281 setfont
  2.32915 293 setfont
  2.32389 289 setfont
  2.32319 285 setfont
  2.32178 297 setfont
  1.11417 268 framebuffer

  For Xenial with generic kernel:

  Duration PID process
  15.01832 232 console_setup
  2.52273 233 setfont
  2.50960 238 setfont
  2.48476 250 setfont
  2.46333 256 setfont
  2.46289 262 setfont
  2.44667 268 setfont
  1.07674 225 framebuffer

  For Xenial with azure kernel:
  15.00529 260 console_setup
  2.49699 261 setfont
  2.47591 292 setfont
  2.47443 266 setfont
  2.47131 286 setfont
  2.46812 280 setfont
  2.45780 274 setfont
  1.07095 253 framebuffer

  so it seems to occur across releases with generic and azure kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1823327/+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 1737637] Re: Replacing configuration file directory with file breaks unattended-upgrades

2019-04-05 Thread Balint Reczey
Verified 1.1ubuntu1.18.04.7~16.04.2 in Xenial:

root@x-uu-verify:~# apt update -qq
21 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@x-uu-verify:~#  apt install git=1:2.7.4-0ubuntu1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
Suggested packages:
  git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk 
gitweb git-arch git-cvs git-mediawiki git-svn
The following packages will be DOWNGRADED:
  git
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 21 not upgraded.
Need to get 3,006 kB of archives.
After this operation, 73.7 kB disk space will be freed.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 git amd64 
1:2.7.4-0ubuntu1 [3,006 kB]
Fetched 3,006 kB in 0s (13.0 MB/s)
dpkg: warning: downgrading git from 1:2.7.4-0ubuntu1.6 to 1:2.7.4-0ubuntu1
(Reading database ... 25724 files and directories currently installed.)
Preparing to unpack .../git_1%3a2.7.4-0ubuntu1_amd64.deb ...
Unpacking git (1:2.7.4-0ubuntu1) over (1:2.7.4-0ubuntu1.6) ...
Setting up git (1:2.7.4-0ubuntu1) ...
root@x-uu-verify:~# mv /etc/bash_completion.d/git-prompt 
/etc/bash_completion.d/git-prompt.bak
root@x-uu-verify:~# mkdir /etc/bash_completion.d/git-prompt
root@x-uu-verify:~# unattended-upgrade --verbose --dry-run
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=UbuntuESM,a=xenial']
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1485, in 
main(options)
  File "/usr/bin/unattended-upgrade", line 1275, in main
if conffile_prompt(item.destfile):
  File "/usr/bin/unattended-upgrade", line 671, in conffile_prompt
with open(prefix + conf_file, 'rb') as fb:
IsADirectoryError: [Errno 21] Is a directory: 
'/etc/bash_completion.d/git-prompt'
root@x-uu-verify:~# vi /etc/apt/sources.list
root@x-uu-verify:~# apt update -qq
30 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@x-uu-verify:~# apt install -y -qq unattended-upgrades 
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
Suggested packages:
  bsd-mailx default-mta | mail-transport-agent needrestart
The following packages will be upgraded:
  unattended-upgrades
1 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Need to get 40.1 kB of archives.
After this operation, 69.6 kB of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 25723 files and directories currently installed.)
Preparing to unpack .../unattended-upgrades_1.1ubuntu1.18.04.7~16.04.2_all.deb 
...
Unpacking unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) over 
(0.90ubuntu0.10) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu21.17) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) ...
Installing new version of config file 
/etc/kernel/postinst.d/unattended-upgrades ...
Installing new version of config file 
/etc/pm/sleep.d/10_unattended-upgrades-hibernate ...
root@x-uu-verify:~# unattended-upgrade --verbose --dry-run
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: busybox-initramfs busybox-static git 
libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 ntfs-3g 
policykit-1 snapd ubuntu-core-launcher
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 
/var/cache/apt/archives/git_1%3a2.7.4-0ubuntu1.6_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure git:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 
/var/cache/apt/archives/libpolkit-backend-1-0_0.105-14.1ubuntu0.5_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libpolkit-backend-1-0:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 
/var/cache/apt/archives/busybox-initramfs_1%3a1.22.0-15ubuntu1.4_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure busybox-initramfs:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 
/var/cache/apt/archives/libpolkit-agent-1-0_0.105-14.1ubuntu0.5_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libpolkit-agent-1-0:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending 
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 

[Touch-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

2019-04-05 Thread Mohammad Kazemi
** Also affects: upower (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  New
Status in gnome-shell source package in Bionic:
  Triaged
Status in upower source package in Bionic:
  New
Status in gnome-shell source package in Cosmic:
  Triaged
Status in upower source package in Cosmic:
  New
Status in gnome-shell source package in Disco:
  Fix Released
Status in upower source package in Disco:
  New

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1823175/+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 1823306] Re: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover

2019-04-05 Thread Hans P Möller
** Changed in: software-properties (Ubuntu Disco)
 Assignee: (unassigned) => Hans P Möller (hmollercl)

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

Title:
  lxqt-sudo added to Exec line of software-properties-qt.desktop breaks
  use in KDE Plasma Discover

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Disco:
  Confirmed

Bug description:
  In the upload: https://launchpad.net/ubuntu/+source/software-
  properties/0.97.8

  there is a change in the software-properties-qt.desktop files which is
  (a) not documented in the changelog, and (b) not communicated to other
  flavour users of this application (Kubuntu in this case).

  -Exec=software-properties-qt
  +Exec=lxqt-sudo software-properties-qt

  This results in Plasma Discover not being able to launch software-
  properties-qt, as it uses privilege elevation via kdesu of whatever is
  in the Exec line, and lxqt-sudo added there makes this fail.

  Context to this is:

  For Cosmic release Lubuntu developers requested agreement from Kubuntu
  to the porting of the software-properties-kde package to pure Qt, so
  that it could be used in both Kubuntu and Lubuntu (lxqt) without
  pulling a lot of KDE dependencies into Lubuntu's lqxt images/installs.
  This was on the condition that despite being renamed to -qt, it
  remained completely as a tool for joint usage between the two
  flavours.

  The original sofware-properties-kde was meant to be launched by
  applications and was set not to show in DE menus by default.

  It seems that Lubuntu wishes to now have it useable directly from a
  'start'/'search' menu, hence making it visible and adding the lxqt-
  sudo in the Exec line to facilitate launch with privilege escalation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823306/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-05 Thread Dimitri John Ledkov
** No longer affects: salt (Ubuntu)

** No longer affects: salt (Ubuntu Bionic)

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Test cases for the python updates]

  python3.7 is a preview in bionic as a non-supported/non-default
  version of python3. Passing it's own autopkgtests is sufficient
  validation for python3.7. It includes a point release update, with
  OpenSSL 1.1.1 compat and features.

  python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
  also includes a point release update to 3.6.8. It has been part of the
  full-archive rebuild and regression analysis. Autopkgtests were
  triggered for python3.6 and python3-defaults with regressions already
  fixed in the individual packages as appropriate.

  python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
  compat only. It has been part of the full-archive rebuild and
  regression analysis. Autopkgtests were triggered for python2.7 and
  python-defaults with regressions already fixed in the individual
  packages as appropriate.

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.

     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.

   * This update bundles python 3.6 and 3.7 point releases

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

  [Autopkgtest Regressions]

  dovecot/armhf - flakey

  libnet-ssleay-perl - awaiting sru accept into proposed of
  libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
  versioned breaks.

  linux* - rebuild testcases passes (for some edge flavours the build
  fails in non-ssl portions of the build), ubuntu-regression-suite
  testcase fails for a few variants but should have been skipped (in
  progress to be fixed in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056)

  openvswitch/i386 - extremely flakey, errors out or fails mostly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   

[Touch-packages] [Bug 1822966] Re: apport-bug locks up when selecting "Cancel"

2019-04-05 Thread Brian Murray
I was unable to recreate this with apport version 2.20.10-0ubuntu25 from
disco on an Ubuntu mate desktop, using the apport-gtk frontend. When I
click "Other problem" I receive a dialog indicating that I need to
specify a package or PID and apport quits. Subsequently, I think this is
specific to the kubuntu frontend.

** Project changed: apport => apport (Ubuntu)

** Tags added: disco

** Tags added: kubuntu

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

Title:
  apport-bug locks up when selecting "Cancel"

Status in apport package in Ubuntu:
  New

Bug description:
  To reproduce:

  * Run "apport-bug" from the command line
  * Select "Other problem" from the "What kind of problem do you want to 
report?", then click OK.
  * The "What display problem do you observe?" dialogue pops up, I realise that 
doesn't match anything that I want to report and click Cancel.
  * Apport becomes completely unresponsive.

  Traceback after Ctrl-C suggests that there is a problem with a thread
  lock:

  Exception ignored in: 
  Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
  t.join()
File "/usr/lib/python3.7/threading.py", line 1032, in join
  self._wait_for_tstate_lock()
File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
  elif lock.acquire(block, timeout):
  KeyboardInterrupt

  This is on Kubuntu 19.04, apport 2.20.10-0ubuntu23

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1822966/+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 1823354] [NEW] printer is no longer visable

2019-04-05 Thread Michael Hendrick
Public bug reported:

This is what system sais when I click on Printers in system settings for Ubuntu
Sorry! The system printing service doesnt seem to be available

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CompositorRunning: None
Date: Fri Apr  5 10:33:13 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0501]
InstallationDate: Installed on 2019-03-12 (23 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=3e6b4fed-11bf-458e-bda1-131b0681e85c ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: EP45-UD3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-UD3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic ubuntu

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

Title:
  printer is no longer visable

Status in xorg package in Ubuntu:
  New

Bug description:
  This is what system sais when I click on Printers in system settings for 
Ubuntu
  Sorry! The system printing service doesnt seem to be available

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Apr  5 10:33:13 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0501]
  InstallationDate: Installed on 2019-03-12 (23 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3L
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=3e6b4fed-11bf-458e-bda1-131b0681e85c ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-UD3L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-UD3L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  

[Touch-packages] [Bug 1822966] [NEW] apport-bug locks up when selecting "Cancel"

2019-04-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

To reproduce:

* Run "apport-bug" from the command line
* Select "Other problem" from the "What kind of problem do you want to 
report?", then click OK.
* The "What display problem do you observe?" dialogue pops up, I realise that 
doesn't match anything that I want to report and click Cancel.
* Apport becomes completely unresponsive.

Traceback after Ctrl-C suggests that there is a problem with a thread
lock:

Exception ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
t.join()
  File "/usr/lib/python3.7/threading.py", line 1032, in join
self._wait_for_tstate_lock()
  File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
elif lock.acquire(block, timeout):
KeyboardInterrupt

This is on Kubuntu 19.04, apport 2.20.10-0ubuntu23

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

-- 
apport-bug locks up when selecting "Cancel"
https://bugs.launchpad.net/bugs/1822966
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport in Ubuntu.

-- 
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 1778800] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

2019-04-05 Thread Stephane Bakhos
This actually caused downtime for me today because of the apache update.
The process stops apache, tries to stop u-u then exits, leaving apache
down.

When can we expect the fix to be released for xenial?

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Upgrading unattended-upgrades during shutdown fails due to postinst
  trying to start the unattended-upgrades service. This can break
  installation of other security-fixes, too.

   * Unattended-upgrades is regularly SRU-d and this bug can break
  installing other important updates.

   * The fix is not starting/stopping the init.d script in postinst
  which is not useful during package installation anyway.

  [Test Case]

   * Check prerm that invoke-rc.d is not called:
  --- prerm.old 2018-06-07 01:30:55.0 +0200
  +++ /var/lib/dpkg/info/unattended-upgrades.prerm  2018-07-12 
14:04:12.294677476 +0200
  @@ -40,11 +40,6 @@
   # dh_installdeb will replace this with shell code automatically
   # generated by other debhelper scripts.
   
  -# Automatically added by dh_installinit/11.1.6ubuntu2
  -if [ -x "/etc/init.d/unattended-upgrades" ] && [ "$1" = remove ]; then
  - invoke-rc.d unattended-upgrades stop || exit 1
  -fi
  -# End automatically added section
   
   
   exit 0

  
   * Check postinst that invoke-rc.d is not called:
  --- postinst.old  2018-06-07 01:30:55.0 +0200
  +++ /var/lib/dpkg/info/unattended-upgrades.postinst   2018-07-12 
14:04:12.242676369 +0200
  @@ -108,8 +108,7 @@
   # Automatically added by dh_installinit/11.1.6ubuntu2
   if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -x "/etc/init.d/unattended-upgrades" ]; then
  - update-rc.d unattended-upgrades defaults >/dev/null
  - invoke-rc.d unattended-upgrades start || exit 1
  + update-rc.d unattended-upgrades defaults >/dev/null || exit 1
fi
   fi
   # End automatically added section

  
  [Regression Potential] 

  * Unattended-upgrades.service may fail to start upon first
  installation. This is not an issue in default configuration since apt
  starts u-u based on timers and stops it gracefully upon shutdown.

  [Original Bug Text]

  update did not install.
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778800/+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 1782709] Re: Updating systemd kills network on bionic

2019-04-05 Thread rjr162
I'd like to also confirm this bug, which we've been experiencing for the
past few months since we first setup an 18.04 image for our deployment
portal.

Initially I thought the cause MAY have been from us using ifupdown (we
have to as our vCenter instance hasn't been upgraded to 6.5.x or 6.7
where Ubuntu 18.04 with NetPlan is officially supported).

I've checked logs and it seems that *every time* apt upgrade is ran and
one of the systemd components are upgraded, the network dies.

You can do "ip addr" and see the interface has no addresses assigned.
A simple restart of networking and the IPs come back. This literally just 
happened this morning to two of our 18.04 LTS systems and the systemd packages 
that were updated were:

libsystemd0
systemd-sysv
libpam-systemd
systemd
libnss-systemd

The rest of the packages that were updated:
grub-common
grub2-common
udev
grub-pc
apache2-data
libudev1
grub-pc-bin
apache2-bin
libunistring2
apache2
apache2-utils


I also had another report on Feb 20th, and it also involved the following 
updates:
Start-Date: 2019-02-20  04:41:09
Commandline: /usr/bin/apt-get -o quiet=1 upgrade -y -o 
APT::Get::Show-Upgraded=true
Upgrade: libsystemd0:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), udev:amd64 
(237-3ubuntu10.12, 237-3ubuntu10.13), libudev1:amd64 (237-3ubuntu10.12, 
237-3ubuntu10.13), systemd-sysv:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), 
libpam-systemd:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), systemd:amd64 
(237-3ubuntu10.12, 237-3ubuntu10.13), libnss-systemd:amd64 (237-3ubuntu10.12, 
237-3ubuntu10.13), pciutils:amd64 (1:3.5.2-1ubuntu1, 1:3.5.2-1ubuntu1.1), 
libpci3:amd64 (1:3.5.2-1ubuntu1, 1:3.5.2-1ubuntu1.1)
End-Date: 2019-02-20  04:42:19

The interesting thing is, looking at my notes, in my case it MAY BE from
the ifupdown which should "just work", as this 2nd VM also has that
setup. I looked and it updated this morning the same as the first
machine but I didn't have a report of it being offline. Now on this 2nd
machine, I did also do an "apt remove netplan.io" as a "hope this solves
the issue and it's some conflict or issue between netplan.io and
ifupdown OR a conflict between systemd and netplan.io and since there's
no report of it being down and I just verified networking is fine is
it something between systemd and netplan?

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

Title:
  Updating systemd kills network on bionic

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I do have an ubuntu bionic server installation without a graphical interface. 
The server
  has two active network adapters, both connected to the internet. One is used 
for outgoing
  internet traffic, the other for incoming. The incoming adapter lives on a 
public network segment
  (something like 88.236.133.104/29). I do have multiple servers within this 
segment.

  Typically, I update the server regularly, meaning:

  * ssh to the incoming adapter: ssh 88.236.133.108
  * apt-get update
  * apt-get upgrade
  * apt-get dist-upgrade
  * apt-get clean
  * reboot

  It used to work ok.

  BUT: Today, "apt-get upgrade" seem to take really long when updating systemd.
  After a could of minutes, I realized that the ssh session became inactive. I 
couldn't type
  into it, I had to abort it via ~. .

  * ssh from the internet to the incoming adapter was not working anymore - ssh 
88.236.133.108
  * ssh via another server within the public network segment worked
  * ssh 88.236.133.106 -> ssh 88.236.133.108
  * After running "netplan apply" everything was fine again

  Here my netplan configuration (I changed the ip addresses):

  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes
  eno2:
dhcp4: no
addresses: [88.236.133.108/29]
#gateway4: 88.236.133.105
routes:
 - to: 0.0.0.0/0
   via: 88.236.133.105
   table: 120
routing-policy:
 - from: 88.236.133.108/32
   table: 120
 - to: 88.236.133.108/32
   table: 120

  Unfortunately, I don't have the console output avalable anymore.
  Shall I provide additional info?

  Best regards, Uli
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 20 08:10 seq
   crw-rw 1 root audio 116, 33 Jul 20 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-14 (5 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - 

[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-05 Thread EOLE team
Thank @xnox, I just made the test and I have the same issue with rebuilt
python3.6.

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in salt package in Ubuntu:
  New
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New
Status in salt source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Test cases for the python updates]

  python3.7 is a preview in bionic as a non-supported/non-default
  version of python3. Passing it's own autopkgtests is sufficient
  validation for python3.7. It includes a point release update, with
  OpenSSL 1.1.1 compat and features.

  python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
  also includes a point release update to 3.6.8. It has been part of the
  full-archive rebuild and regression analysis. Autopkgtests were
  triggered for python3.6 and python3-defaults with regressions already
  fixed in the individual packages as appropriate.

  python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
  compat only. It has been part of the full-archive rebuild and
  regression analysis. Autopkgtests were triggered for python2.7 and
  python-defaults with regressions already fixed in the individual
  packages as appropriate.

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.

     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.

   * This update bundles python 3.6 and 3.7 point releases

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

  [Autopkgtest Regressions]

  dovecot/armhf - flakey

  libnet-ssleay-perl - awaiting sru accept into proposed of
  libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
  versioned breaks.

  linux* - rebuild testcases passes (for some edge flavours the build
  fails in non-ssl portions of the build), ubuntu-regression-suite
  testcase fails for a few variants but should have been skipped (in
  progress to be fixed in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056)

  openvswitch/i386 - extremely flakey, errors out or fails mostly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

2019-04-05 Thread Dean Henrichsmeyer
It's the last thing seen on the console when it happens. The machine in
question has been updated to disco and I haven't seen the behavior.

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

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-05 Thread Dimitri John Ledkov
@eole-team

hm, that shouldn't happen. python3.6, rebuilt against openssl1.1.1, has
not been accepted yet into bionic-proposed. And even, when I upgrade to
python3.6 from the staging ppa, salt still fails.

To get the pending python3.6, you can use the below PPA:
$ sudo add-apt-repository ppa:ci-train-ppa-service/3662
$ sudo apt full-upgrade

I'm now opening a new bug report about salt at 
https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1823332
As I believe it is reproducible in cosmic too.
Further salt discussion / fixing should move to that bug report.

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in salt package in Ubuntu:
  New
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New
Status in salt source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Test cases for the python updates]

  python3.7 is a preview in bionic as a non-supported/non-default
  version of python3. Passing it's own autopkgtests is sufficient
  validation for python3.7. It includes a point release update, with
  OpenSSL 1.1.1 compat and features.

  python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
  also includes a point release update to 3.6.8. It has been part of the
  full-archive rebuild and regression analysis. Autopkgtests were
  triggered for python3.6 and python3-defaults with regressions already
  fixed in the individual packages as appropriate.

  python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
  compat only. It has been part of the full-archive rebuild and
  regression analysis. Autopkgtests were triggered for python2.7 and
  python-defaults with regressions already fixed in the individual
  packages as appropriate.

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.

     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.

   * This update bundles python 3.6 and 3.7 point releases

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

  [Autopkgtest Regressions]

  dovecot/armhf - flakey

  libnet-ssleay-perl - awaiting sru accept into proposed of
  libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
  versioned breaks.

  linux* - rebuild testcases passes (for some edge flavours the build
  fails in 

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-05 Thread Vital Koshalew
@root (mysky),

Qualys is slow to fix their detection algorithm. You just need to provide them 
with False Positive report citing the vendor documentation 
(https://usn.ubuntu.com/3809-1/). 
Faking software version is the last thing someone should do to be PCI DSS 
compliant.

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  Fix Released

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-05 Thread Derk Willem te Bokkel
I've been merrily switching between OS's without this kind of issue for more 
than 10 years .. 
the behaviour changed recently in the last 30 days .. 
it was fine prior to that .. 
This is a regression bug and will annoy anyone working with multiple instances 
of disco xubuntu for testing..

yes it is particular to intel graphics.. i915 based

I have another older laptop amd/ati based which does not react this was
way

no it is not a show stopper except when the power button refuses to
work..

I'm trying to figure it out .. thus the questions.. sorry if that is
inappropriate.

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Touch-packages] [Bug 1823307] [NEW] package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-05 Thread Shambhu Nayek
Public bug reported:

always a pop up coming to report a bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.133-1ubuntu10
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Apr  5 14:31:13 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-05-05 (700 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: lvm2
Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  always a pop up coming to report a bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu10
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  5 14:31:13 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-05 (700 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lvm2
  Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1823307/+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 1823307] Re: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-05 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  always a pop up coming to report a bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.133-1ubuntu10
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Apr  5 14:31:13 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-05 (700 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lvm2
  Title: package lvm2 2.02.133-1ubuntu10 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1823307/+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 1823306] [NEW] lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover

2019-04-05 Thread Rik Mills
Public bug reported:

In the upload: https://launchpad.net/ubuntu/+source/software-
properties/0.97.8

there is a change in the software-properties-qt.desktop files which is
(a) not documented in the changelog, and (b) not communicated to other
flavour users of this application (Kubuntu in this case).

-Exec=software-properties-qt
+Exec=lxqt-sudo software-properties-qt

This results in Plasma Discover not being able to launch software-
properties-qt, as it uses privilege elevation via kdesu of whatever is
in the Exec line, and lxqt-sudo added there makes this fail.

Context to this is:

For Cosmic release Lubuntu developers requested agreement from Kubuntu
to the porting of the software-properties-kde package to pure Qt, so
that it could be used in both Kubuntu and Lubuntu (lxqt) without pulling
a lot of KDE dependencies into Lubuntu's lqxt images/installs. This was
on the condition that despite being renamed to -qt, it remained
completely as a tool for joint usage between the two flavours.

The original sofware-properties-kde was meant to be launched by
applications and was set not to show in DE menus by default.

It seems that Lubuntu wishes to now have it useable directly from a
'start'/'search' menu, hence making it visible and adding the lxqt-sudo
in the Exec line to facilitate launch with privilege escalation.

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: software-properties (Ubuntu Disco)
 Importance: High
 Status: Confirmed

** Also affects: software-properties (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu Disco)
   Status: New => Confirmed

** Changed in: software-properties (Ubuntu Disco)
   Importance: Undecided => High

** Description changed:

  In the upload: https://launchpad.net/ubuntu/+source/software-
  properties/0.97.8
  
  there is a change in the software-properties-qt.desktop files which is
  (a) not documented in the changelog, and (b) not communicated to other
  flavour users of this application (Kubuntu in this case).
  
  -Exec=software-properties-qt
  +Exec=lxqt-sudo software-properties-qt
  
  This results in Plasma Discover not being able to launch software-
  properties-qt, as it uses privilege elevation via kdesu of whatever is
  in the Exec line, and lxqt-sudo added there makes this fail.
  
  Context to this is:
  
  For Cosmic release Lubuntu developers requested agreement from Kubuntu
  to the porting of the software-properties-kde package to pure Qt, so
  that it could be used in both Kubuntu and Lubuntu (lxqt) without pulling
  a lot of KDE dependencies into Lubuntu's lqxt images/installs. This was
- informally on the condition that despite being renamed to -qt, it
- remained completely as a toold for joint usage between the two flavours.
+ on the condition that despite being renamed to -qt, it remained
+ completely as a tool for joint usage between the two flavours.
  
  The original sofware-properties-kde was meant to be launched by
  applications and was set not to show in DE menus by default.
  
  It seems that Lubuntu wishes to now have it useable directly from a
  'start'/'search' menu, hence making it visible and adding the lxqt-sudo
  in the Exec line to facilitate launch with privilege escalation.

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

Title:
  lxqt-sudo added to Exec line of software-properties-qt.desktop breaks
  use in KDE Plasma Discover

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Disco:
  Confirmed

Bug description:
  In the upload: https://launchpad.net/ubuntu/+source/software-
  properties/0.97.8

  there is a change in the software-properties-qt.desktop files which is
  (a) not documented in the changelog, and (b) not communicated to other
  flavour users of this application (Kubuntu in this case).

  -Exec=software-properties-qt
  +Exec=lxqt-sudo software-properties-qt

  This results in Plasma Discover not being able to launch software-
  properties-qt, as it uses privilege elevation via kdesu of whatever is
  in the Exec line, and lxqt-sudo added there makes this fail.

  Context to this is:

  For Cosmic release Lubuntu developers requested agreement from Kubuntu
  to the porting of the software-properties-kde package to pure Qt, so
  that it could be used in both Kubuntu and Lubuntu (lxqt) without
  pulling a lot of KDE dependencies into Lubuntu's lqxt images/installs.
  This was on the condition that despite being renamed to -qt, it
  remained completely as a tool for joint usage between the two
  flavours.

  The original sofware-properties-kde was meant to be launched by
  applications and was set not to show in DE menus by default.

  It seems that Lubuntu wishes to now have it useable directly 

[Touch-packages] [Bug 1640544] Re: "indicator-power" says "estimating" when plugged to power.

2019-04-05 Thread Matthew Paul Thomas
** Changed in: indicator-power (Ubuntu)
   Status: Won't Fix => New

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

Title:
  "indicator-power" says "estimating" when plugged to power.

Status in indicator-power package in Ubuntu:
  New

Bug description:
  There seem to be a couple of bug reports from 4 - 5 years ago,
  complaining the same thing. Looks like the bug is back in 16.10.

  ---

  >1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  16.10 (yakkety)

  >2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 12.10.6+16.10.20160708-0ubuntu1
  Candidate: 12.10.6+16.10.20160708-0ubuntu1

  >3) What you expected to happen

  The indicator should say the remaining time to be fully charged, and
  display an icon of either a charging battery, or a "power plug" (In
  case the battery is fully charged, and the machine is running on
  direct power.).

  >4) What happened instead

  The indicator just says "estimating". It doesn't display whether it is
  being charged, or running on direct power.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1640544/+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 1822984] Re: revert tls security level back to 1

2019-04-05 Thread Timo Aaltonen
Hello Dimitri, or anyone else affected,

Accepted openssl into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: openssl (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  revert tls security level back to 1

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Cosmic:
  Fix Committed
Status in openssl source package in Disco:
  Fix Released

Bug description:
  [Impact]
  * increase minimum default tls security level from 0 to 1, as is the default 
upstream

  [Test Case]

  * generate 80bits TLS certificate and attempt to use it

  * with prior openssl it should work, but with this update it should
  fail

  [Regression Potential]

  * This increases the minimum required certificate/keys sizes and
  algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also
  now will match upstream default. It is still lower than Debian's
  default that raises it to 2 by default.

  * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any
  weak keys were accepted. With this change keys lower than 112 will be
  rejected, which are considered to be too weak to be useful by most CAs
  out there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+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 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i

2019-04-05 Thread Timo Aaltonen
Hello Dimitri, or anyone else affected,

Accepted openssl into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: openssl (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Cosmic:
  Fix Committed
Status in openssl source package in Disco:
  Fix Released
Status in openssl package in Debian:
  New

Bug description:
  [Impact]
   * fetch-url cannot use https protocol (no https preseeds)

  [Test case]
   * in d-i, mini.iso, tty try
 wget https://geoip.ubuntu.com/lookup

   it should succeed.

  [Solution]
  The required openssl.cnf configuration file is missing, needs to simply 
exists, even if it is empty.

  [Regression Potential]
  well, if one cannot download over https / init ssl library in d-i, it's hard 
to get openssl busted more than that. No code changes on the .deb side of things

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+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 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

2019-04-05 Thread Timo Aaltonen
Hello Balint, or anyone else affected,

Accepted ubuntu-meta into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
meta/1.425.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-meta (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: ubuntu-meta (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1822341] Please test proposed package

2019-04-05 Thread Timo Aaltonen
Hello Balint, or anyone else affected,

Accepted ubuntu-meta into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
meta/1.417.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-05 Thread Christian Ehrhardt 
See lightdm and gpu-manager services in
http://paste.ubuntu.com/p/5QyzgMKhmr/ for an example how that looks like
from a guests POV.

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-05 Thread Christian Ehrhardt 
Thanks cascardo for testing power8 already.

This came up in bug 1823152 as well and made me aware of this.
If qemu is not run in commandline most frontends set something else than "-vga 
std" therefore I wasn't aware. But I can confirm seeing the issue.

I think I can test x86 quite easily, is there a PPA to test this?
Actually everyone can:
1. sudo qemu-img create /var/lib/libvirt/images/xubuntu18_04.qcow2 15G
2. sudo qemu-system-x86_64-spice -enable-kvm -cpu host -boot d -cdrom 
~/Downloads/xubuntu-18.04.2-desktop-amd64.iso 
/var/lib/libvirt/images/xubuntu18_04.qcow2 -m 8G
3. sudo qemu-system-x86_64-spice -enable-kvm -cpu host 
/var/lib/libvirt/images/xubuntu18_04.qcow2 -m 8G

#3 fails with the default, set "-vga qxl" and you have a working guest.
For mass testing you can do the install in #2 once and then just copy around 
the image file to boot e.g. under different Hosts versions.


OTOH - I'm not sure I can speak for all potential implications as the kmod 
header reads like:
"# Framebuffer drivers are generally buggy and poorly-supported, and cause
# suspend failures, kernel panics and general mayhem.  For this reason we
# never load them automatically."
I won't test e.g. suspend on all of them and/or might it be an issue on bare 
metal or on real Bochs?

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1822341] Please test proposed package

2019-04-05 Thread Timo Aaltonen
Hello Balint, or anyone else affected,

Accepted ubuntu-meta into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
meta/1.361.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: kmod (Ubuntu)
   Status: New => Confirmed

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-05 Thread EOLE team
The libssl1.1 version 1.1.1-1ubuntu2.1~18.04.1 breaks salt package
version 2017.7.4+dfsg1-1:

root@server:~# salt-key -L
Error: unknown error (_ssl.c:2788)

root@server:~# salt --versions-report
Traceback (most recent call last):
  File "/usr/bin/salt", line 10, in 
salt_main()
  File "/usr/lib/python3/dist-packages/salt/scripts.py", line 476, in salt_main
client.run()
  File "/usr/lib/python3/dist-packages/salt/cli/salt.py", line 33, in run
import salt.client
  File "/usr/lib/python3/dist-packages/salt/client/__init__.py", line 31, in 

import salt.cache
  File "/usr/lib/python3/dist-packages/salt/cache/__init__.py", line 18, in 

import salt.loader
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 26, in 
import salt.utils.event
  File "/usr/lib/python3/dist-packages/salt/utils/event.py", line 70, in 

import tornado.iostream
  File "/usr/lib/python3/dist-packages/tornado/iostream.py", line 40, in 

from tornado.netutil import ssl_wrap_socket, ssl_match_hostname, 
SSLCertificateError, _client_ssl_defaults, _server_ssl_defaults
  File "/usr/lib/python3/dist-packages/tornado/netutil.py", line 57, in 
ssl.Purpose.SERVER_AUTH)
  File "/usr/lib/python3.6/ssl.py", line 502, in create_default_context
context = SSLContext(PROTOCOL_TLS)
  File "/usr/lib/python3.6/ssl.py", line 391, in __new__
self = _SSLContext.__new__(cls, protocol)
ssl.SSLError: unknown error (_ssl.c:2788)

Seems to be python3.6 which is impacted.

Regards.

** Also affects: salt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in salt package in Ubuntu:
  New
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New
Status in salt source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Test cases for the python updates]

  python3.7 is a preview in bionic as a non-supported/non-default
  version of python3. Passing it's own autopkgtests is sufficient
  validation for python3.7. It includes a point release update, with
  OpenSSL 1.1.1 compat and features.

  python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
  also includes a point release update to 3.6.8. It has been part of the
  full-archive rebuild and regression analysis. Autopkgtests were
  triggered for python3.6 and python3-defaults with regressions already
  fixed in the individual packages as appropriate.

  python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
  compat only. It has been part of the full-archive rebuild and
  regression analysis. Autopkgtests were triggered for python2.7 and
  python-defaults with regressions already fixed in the individual
  packages as appropriate.

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set 

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-05 Thread root
@set, That's fine, but scanned Qualys report suggests to install openssh
>7.8 to fix this bug!, not sure where is the issue, PFA for sample
qualys report, do you know how to change the openssh version and hide OS
version without compiling?, any SSHD_options? let me know.


Thanks

** Attachment added: "recent qualys report on a server with openssh 7.6p1"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+attachment/5253000/+files/qualys_scan_report_2019.png

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  Fix Released

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-05 Thread Timo Aaltonen
Your setup is anything but a typical one, and bugs should not be used to
"ask" how something works the way it does. You mentioned that the
"original" disco install always works fine, so I don't think there's a
valid bug here at all?

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+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 1821091] Re: [FFe] Qt 5.12.2 update

2019-04-05 Thread Rik Mills
** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [FFe] Qt 5.12.2 update

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Dear Release Team,

  I would like to update Qt in disco from 5.11.3 to 5.12.2.

  The reasons are the following:

  1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
  branch is LTS and will be supported for three years.

  2) New versions of Plasma are going to require Qt 5.12, and the
  Kubuntu team would like to be able to package them in their backports
  PPA for disco.

  3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to
  30 %.

  4) Finally we will be able to sync all packages from Debian. I have
  managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

  Why we haven’t packaged it early: we did not want to package 5.12.1
  because it had some known bugs. And 5.12.2 was released upstream later
  than it was originally planned.

  Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

  The packages are being prepared in https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced
  with syncs from Debian when qtbase and qtdeclarative get accepted from
  Debian’s NEW queue.

  This transition will require syncs of all Qt packages, and no-change
  rebuilds of packages that build-depend on qtbase5-private-dev or
  qtdeclarative5-private-dev.

  All Qt modules are in universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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