[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
@sergiodj many thanks for the help here
It was a dwz man page somewhere that made me think we might be misusing
.gnu_debugaltlink somehow (didn't even know about dh_dwz), but on a
quick search I couldn't understand how the path was supposed to look
like so I could test that idea with my replace-altlink-section-hack.
And if GDB can support looking for .dwz on the debug-file-drectory even
with hardcoded paths, all the better.
Many, many thanks for taking the time to look at this and come up with
these 2 solutions. We really appreciate it.
--
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/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
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/apport/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
So the issue is: if there is a .gnu_debugaltlink GDB will try to load
that file and throw an error if it can't. That path is absolute and GDB
does _not_ look for that path/file anywhere else, not even inside
'debug-file-directory'.
GDB seems to only look at section .gnu_debugaltlink in debug/.build-
id/nn/nn.debug, it does not seem to use that section from the binary
at all.
Due to that, another workaround is to modify that section to point to
the 'right' place:
1) use objcopy to dump .gnu_debugaltlink from debug/.build-id/nn/nn.debug
into a file
2) use sed to modify the path in the dump file
3) use objcopy to update .gnu_debugaltlink section in
debug/.build-id/nn/nn.debug
As in:
$ objcopy --dump-section .gnu_debugaltlink=altlink
/tmp/dbgsym/usr/lib/debug/.build-id/76/e9f820204912084fd156c593b2c92f1a4b51f1.debug
$ sed -i 's:^:/tmp/dbgsym:' altlink
$ objcopy --update-section .gnu_debugaltlink=altlink
/tmp/dbgsym/usr/lib/debug/.build-id/76/e9f820204912084fd156c593b2c92f1a4b51f1.debug
--
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/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
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/apport/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
I was able to reproduce what Brian is reporting here.
If the -dbgsym for the package is installed, gdb works and reports that it is
reading from the /tmp/dbgsym path. When -dbgsym package is not installed then
it fails with the
'could not find '.gnu_debugaltlink' file for ...' message
--
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/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
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/apport/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
I tried the testcase from comment #12 in Focal and Hirsute and it worked
just fine:
$ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
Type "apropos word" to search for commands related to "word".
Reading symbols from /bin/cat...
Reading symbols from
/tmp/dbgsym/usr/lib/debug/.build-id/b3/57ed53c8c9cb1a312f83b28982304effae0135.debug...
[New LWP 2094475]
Core was generated by `/bin/cat'.
Program terminated with signal SIGTSTP, Stopped (user).
#0 0x77eb6142 in __GI___libc_read (fd=fd@entry=0,
buf=buf@entry=0x77faa000, nbytes=nbytes@entry=131072) at
../sysdeps/unix/sysv/linux/read.c:26
# hirsute
$ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
Reading symbols from /bin/cat...
Reading symbols from
/tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug...
[New LWP 14651]
Core was generated by `/usr/bin/cat'.
Program terminated with signal SIGTSTP, Stopped (user).
#0 0x77edccb2 in __GI___libc_read (fd=fd@entry=0,
buf=buf@entry=0x7791e000, nbytes=nbytes@entry=131072) at
../sysdeps/unix/sysv/linux/read.c:26
26 ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
If the dbgsym is installed and I use (with intentional typo):
set debug-file-directory /tmp/dbgsym/usr/lib/debugnot:/usr/lib/debug
it then loads symbols correctly from /usr/lib/debug
Note, this was tested under Focal (host) and Hirsute (lxd container).
--
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/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
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/apport/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
> 7) Execute "gdb --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
--ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug'"
Try setting the debug-file-directory first, it should work.
gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
Still, this does not seem to invalidate the original bug report or the
one in comment #4, as they are setting 'file' and 'core' last. It is
just that comment #12 does not seem to indicate a valid reproducer.
--
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/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
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/apport/+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 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
** Branch linked: lp:~tdaitx/ubuntu/groovy/apport/ubuntu
--
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/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
Status in apport package in Ubuntu:
Confirmed
Bug description:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Problem in coreutils
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third
party package and try again.
A simpler recreate is:
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import
apport;print(apport.packaging.is_distro_package("coreutils"))'
True
Desired result:
The message should instruct the user to run 'apt update' as root if
they think this is in error. That would improve usability and avoid
false reports about apport incorrectly flagging a package as
unsupported.
Additionally, if the user is root (and optionally if the set of
package candidates only contains a 'now' component)
self._cache.update(); self._cache.open() could be called to download
lists.
Alternatively it could just check to see if lists have been
downloaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+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 1870088] Re: xz-utils ftbfs in focal
** Tags removed: block-proposed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Fix Committed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1870088] Re: xz-utils ftbfs in focal
** Changed in: xz-utils (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Fix Committed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1870088] Re: xz-utils ftbfs in focal
Installed xz-utils 5.2.4-1ubuntu1 on Focal from focal-proposed, works fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Confirmed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1870088] Re: xz-utils ftbfs in focal
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Confirmed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1850608] Re: Segfaults trying to send crash report
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1850608 Title: Segfaults trying to send crash report Status in whoopsie package in Ubuntu: Fix Released Bug description: After this morning's upgrade to "whoopsie 0.2.62ubuntu0.2" plus "libwhoopsie0 0.2.62ubuntu0.2"(fix to bug #1830865), whoopsie repeatedly crashes with a segfault (in what seems to be libc?). An excerpt from /var/log/syslog (slightly redacted): Oct 30 08:33:06 [REDACTED] systemd[1]: Started crash report submission daemon. Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Using lock path: /var/lock/whoopsie/lock Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Parsing /var/crash/_usr_bin_kdeinit5.1000.crash. Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Uploading /var/crash/_usr_bin_kdeinit5.1000.crash. Oct 30 08:33:10 [REDACTED] kernel: [ 2129.099314] whoopsie[22414]: segfault at 7f4f878a4000 ip 7f4f866fe5e1 sp 7ffe348bed78 error 4 in libc-2.27.so[7f4f86591000+1e7000] Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Main process exited, code=dumped, status=11/SEGV Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Failed with result 'core-dump'. Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Service hold-off time over, scheduling restart. Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Scheduled restart job, restart counter is at 133. Oct 30 08:33:11 [REDACTED] systemd[1]: Stopped crash report submission daemon. The above sequence of logged events repeats endlessly, with only(?) the times and whoospie PID changing. The problem can be (temporarily) stopped by `service whoopsie stop'; using `service whoopsie start' resumes the above behaviour. Rebooting does not "fix". Manually running whoopsie shows the same behaviour: $ sudo /bin/sh -c 'export CRASH_DB_URL=https://daisy.ubuntu.com; exec whoopsie -f' [09:45:14] Using lock path: /var/lock/whoopsie/lock [09:45:14] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 [09:45:14] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 [09:45:14] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 [09:45:14] Parsing /var/crash/_usr_bin_kdeinit5.1000.crash. [09:45:14] Uploading /var/crash/_usr_bin_kdeinit5.1000.crash. Segmentation fault $ $ ls -la /var/crash/ total 33340 drwxrwsrwt 2 root whoopsie 4096 Oct 30 08:52 . drwxr-xr-x 16 root root 4096 Sep 14 2018 .. -rw-r--r-- 1 root whoopsie 281 Oct 30 08:55 kexec_cmd -rwxrwxrwx 1 root whoopsie0 Oct 30 08:22 .lock -rw-r- 1 blf whoopsie 17624101 Oct 30 08:53 _usr_bin_kdeinit5.1000.crash -rw-rw-r-- 1 blf whoopsie0 Oct 30 08:22 _usr_bin_kdeinit5.1000.upload -rw-r- 1 root whoopsie 398157 Oct 24 11:49 _usr_bin_sddm.0.crash -rw-r- 1 whoopsie whoopsie 15996866 Oct 30 08:22 _usr_bin_whoopsie.108.crash -rw-r- 1 root whoopsie99379 Oct 22 15:07 _usr_sbin_inetd.0.crash $ Because (as far as I know) the various `.crash' files MAY contain sensitive information, I have not attached them to this (public) bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: whoopsie 0.2.62ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 Date: Wed Oct 30 09:28:01 2019 InstallationDate: Installed on 2016-10-07 (1118 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to bionic on 2018-08-18 (438 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1850608/+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 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour
I tested the initramfs-tools in xenial-proposed, bionic-proposed, and
disco-proposed with all 3 testcases (panic=-1, panic=10, and no panic),
everything worked as expected:
- panic=-1 rebooted instantly after the root partition is not found
- panic=10 rebooted after 10 seconds
- no "panic" entry caused to drop into a basic shell
ii initramfs-tools 0.122ubuntu8.16 all generic modular initramfs generator
(automation)
ii initramfs-tools 0.130ubuntu3.9 all generic modular initramfs generator
(automation)
ii initramfs-tools 0.131ubuntu19.2 all generic modular initramfs generator
(automation)
multipass@xenial:~$ apt-cache policy initramfs-tools
initramfs-tools:
Installed: 0.122ubuntu8.16
Candidate: 0.122ubuntu8.16
Version table:
*** 0.122ubuntu8.16 400
400 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
0.122ubuntu8.15 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
0.122ubuntu8.14 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
0.122ubuntu8 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
multipass@bionic:~$ apt-cache policy initramfs-tools
initramfs-tools:
Installed: 0.130ubuntu3.9
Candidate: 0.130ubuntu3.9
Version table:
*** 0.130ubuntu3.9 400
400 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
0.130ubuntu3.8 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
0.130ubuntu3.6 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
0.130ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
multipass@disco:~$ apt-cache policy initramfs-tools
initramfs-tools:
Installed: 0.131ubuntu19.2
Candidate: 0.131ubuntu19.2
Version table:
*** 0.131ubuntu19.2 400
400 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages
100 /var/lib/dpkg/status
0.131ubuntu19.1 500
500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
0.131ubuntu19 500
500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco verification-needed-xenial
** Tags added: verification-done-bionic verification-done-disco
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1831252
Title:
panic=-1 is completely ignored by the initrd causing unexpected
behaviour
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Fix Committed
Status in initramfs-tools source package in Bionic:
Fix Committed
Status in initramfs-tools source package in Disco:
Fix Committed
Status in initramfs-tools source package in Eoan:
Fix Released
Bug description:
[Impact]
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a
kernel level this works just fine and the system reboots immediately ...
when in the initramfs during boot and a panic occurs, no reboot
happens at all, the initrd spawns a shell regardless of the panic=
value ...
[Test case]
Before booting change root=$foo to root=x$foo - this will make it
panic. Then test that
1) "panic=-1" causes an immediate reboot
2) "panic=5" waits 5 seconds
3) no "panic" drops you to a shell
[Regression potential]
This adds some very specific checks for -1 in places that use ${panic}, as
such the regression potential is somewhat limited. If there were a regression,
it could be a syntax error (causing boot to fail) or a sleep not working
correctly (causing sleep to, well, not sleep) - but that's unrealistic.
[Other info]
this is caused by a filter in /usr/share/initramfs-tools/init
panic=*)
panic="${x#panic=}"
case ${panic} in
*[![:digit:].]*)
panic=
;;
esac
;;
this function only lets positive values through, else panic= simply
gets unset
the panic() function itself is also not capable of handling negative
values, it has a sleep call that interprets negative values as
commandline options instead of simply ignoring a negative sleep time
[2] (line 11).
the filter in the init script should allow the -1 value (to comply
with the kernel documentation and behaviour) and the panic() function
should properly skip the sleep call when a negative value for panic=
is set.
[1]
[Touch-packages] [Bug 1823125] Re: tomcat9 fails to install in 18.04
** Changed in: tomcat9 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1823125 Title: tomcat9 fails to install in 18.04 Status in systemd package in Ubuntu: Fix Released Status in tomcat9 package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in tomcat9 source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Status in tomcat9 source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Status in tomcat9 source package in Disco: Fix Released Bug description: # apt install tomcat9 ... Setting up tomcat9 (9.0.16-3~18.04) ... [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage. Creating config file /etc/tomcat9/tomcat-users.xml with new version chown: invalid group: ‘root:tomcat’ dpkg: error processing package tomcat9 (--configure): installed tomcat9 package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.15) ... Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. done. Processing triggers for rsyslog (8.32.0-1ubuntu4) ... Errors were encountered while processing: tomcat9 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823125/+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 1821768] Re: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed
Could you please take a look at bug #1770278 and look if the screenshot with the artifacts is the same/similar to what you are seeing here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1821768 Title: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed Status in ubuntu-themes package in Ubuntu: New Bug description: Openjdk-11 is now in bionic-proposed, and apparently it has switched to gtk3. The gtk3-java theming in Ambiance theme is very incomplete in Bionic. I can see a lot of theming artefacts in scilab (default look) and jabref (after switching to gtk look) from bionic-proposed. Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance on Bionic: A. For java-gtk2: 1. Don't update to openjdk-11 in bionic-proposed 2. Install jabref 3.8.2+ds-3 3. Change the look in Preferences to Gtk 4. Notice that the app is properly themed B. For java-gtk3: 5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed 6. Change the look in Preferences to Gtk 5. Notice that the theming has many artefacts compared to the previous version The same steps can be followed to compare scilab before and after. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 16:17:52 2019 InstallationDate: Installed on 2018-11-29 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1821768/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3 that are waiting for security team review. Copy only after OK is received. PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 Please copy them in the following order/grouping. Group 1: * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07) Group 2: * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago) * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20) * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20) * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20) * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19) * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19) * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20) Packages from stage 4 and later are not yet reviewed and should not be uploaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activemq/+bug/1814133/+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 1814133]
: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3 that are waiting for security team review. Copy only after OK is received. PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 Please copy them in the following order/grouping. Group 1: * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07) Group 2: * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago) * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20) * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20) * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20) * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19) * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19) * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20) Packages from stage 4 and later are not yet reviewed and should not be uploaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activemq/+bug/1814133/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jabref (Ubuntu) Importance: Undecided Status: New ** Also affects: octave (Ubuntu) Importance: Undecided Status: New ** Also affects: pdfsam (Ubuntu) Importance: Undecided Status: New ** Also affects: scilab (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in pdfsam package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in scilab package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer
[Touch-packages] [Bug 1814133]
affects Ubuntu/jabref affects Ubuntu/scilab affects Ubuntu/scilab affects Ubuntu/pdfsam -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in pdfsam package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in scilab package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3
Re: [Touch-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
> > Just a question, is this update going to affect these packages: > > jabref > > scilab > > octave > > pdfsam > > ? > > > > Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding > > OpenJdk-11 and its dependant packages to facilitate the maintenance > > burden. > > Yes, we are planning to update java apps that are affected by this transition. To be more specific, any package that fails to run correctly with openjdk-11 will be investigated and is a candidate for a update. The update does not necessarily imply we will use the latest version: we might simply apply or backport changes that allow them to work under openjdk-11. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle
Re: [Touch-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
> Just a question, is this update going to affect these packages: > jabref > scilab > octave > pdfsam > ? > > Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding > OpenJdk-11 and its dependant packages to facilitate the maintenance > burden. Yes, we are planning to update java apps that are affected by this transition. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: libhibernate-validator-java (Ubuntu) Importance: Undecided Status: New ** Also affects: jasperreports (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-bundle-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-enforcer (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-jaxb2-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-plugin-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: logback (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-javadoc-plugin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3 that are waiting for security team review. Copy only after OK is received. PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 Please copy them in the following order/grouping. Group 1: * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic- security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. - [2018-02-21] + [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) - Packages from stage 3 and later are not yet reviewed and should not be + + [2019-02-22] + Packages in stage 3 that are waiting for security team review. Copy only after OK is received. + + PPAs: + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 + + Please copy them in the following order/grouping. + Group 1: + * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) + * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07) + + Group 2: + * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago) + * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20) + * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19) + * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19) + * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20) + + Packages from stage 4 and later are not yet reviewed and should not be uploaded. ** Also affects: java-common (Ubuntu) Importance: Undecided Status: New ** Also affects: javatools (Ubuntu) Importance: Undecided Status: New ** Also affects: insubstantial (Ubuntu) Importance: Undecided Status: New ** No longer affects: saaj-ri (Ubuntu) ** Also affects: libgpars-groovy-java (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in metro-policy package in Ubuntu
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. - This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - - openjdk-lts 11 needs newer build dependencies - - various packages have runtime failures when run with openjdk-11 + This transition is a security update of openjdk-lts from openjdk-10 to + openjdk-11. This introduces runtime and FTBFS issues which requires + backports of multiple packages into the security pocket as well. - A few packages *must* be updated/patched before openjdk-11 itself is uploaded: - TBD + The packages are being build on PPAs under the + https://launchpad.net/~openjdk-11-transition team. The PPAs depend + solely on the security pocket and are separated in stages. + + The agreed process among foundations and the security team is that + packages in the PPAs will be binary copied into bionic-proposed, checked + for migration issues, and - no issues pending - copied into bionic- + security. + + A few packages might also need to be updated in Cosmic, but as an + exception that will be done after the Bionic transition is worked out. + + + [2018-02-21] + Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. + + Notes: + - jtreg and testng are new versions required as build dependencies of openjdk-11 + - all other packages are backports that must be build/bootstrapped with openjdk-10 + + PPAs: + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 + + + Please copy them in the following order/grouping. + + Group 1: + * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 2: + * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) + * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) + + Please upload libcommons-lang3-java from stage 2 (ignore the version in + stage 1). + + Group 3: + * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) + * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 4: + * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 5: + * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + + Packages from stage 3 and later are not yet reviewed and should not be uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. A few packages
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: - update to openjdk 11 in 18.04 LTS + Transition OpenJDK 11 to 18.04 LTS. + + This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: + - openjdk-lts 11 needs newer build dependencies + - various packages have runtime failures when run with openjdk-11 + + A few packages *must* be updated/patched before openjdk-11 itself is uploaded: + TBD -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - openjdk-lts 11 needs newer build dependencies - various packages have runtime failures when run with openjdk-11 A few packages *must* be updated/patched before openjdk-11 itself is uploaded: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jtreg (Ubuntu) Importance: Undecided Status: New ** Also affects: libcommons-lang3-java (Ubuntu) Importance: Undecided Status: New ** Also affects: testng (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: clojure1.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: dd-plist (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-compiler-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: plexus-languages (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj (Ubuntu) Importance: Undecided Status: New ** Also affects: surefire (Ubuntu) Importance: Undecided Status: New ** Also affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Also affects: groovy (Ubuntu) Importance: Undecided Status: New ** Also affects: jaxws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: jws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: metro-policy (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj-ri (Ubuntu) Importance: Undecided Status: New ** Also affects: junit4 (Ubuntu) Importance: Undecided Status: New ** Also affects: gettext (Ubuntu) Importance: Undecided Status: New ** Also affects: scala (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
** Also affects: freetype (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: freetype (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: openjdk-lts (Ubuntu) Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: Confirmed Status in freetype source package in Bionic: New Status in openjdk-lts source package in Bionic: New Status in freetype source package in Cosmic: New Status in openjdk-lts source package in Cosmic: New Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
Did the testcase verification again for the new 0.130ubuntu3.5 bionic- proposed upload and I confirm again that it works as expected. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
Verified that initramfs-tools 0.130ubuntu3.5 in bionic-proposed now works as expected after following through the testcase. As expected orphaned old-dkms files are properly removed and no other files are affected. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
I have prepared a new merge proposal that includes the right version check in the postinst for Bionic. This has been uploaded to the Bionic queue as 0.130ubuntu3.5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
Verification done in Xenial and Bionic as per the test case. It works fine and will prevent update-initramfs from being stuck in the described scenarios. ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
Verification failed on Bionic when following the test case, the postinst script has a bad check for the previous version of initramfs-tools it expected - it is testing against a version from Xenial, not the Bionic version. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
Verification done on Xenial by following the test case. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1792189] Re: linux-firmware does not depend on initramfs-tools
** Changed in: initramfs-tools (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1792189 Title: linux-firmware does not depend on initramfs-tools Status in initramfs-tools package in Ubuntu: Confirmed Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
** Merge proposal unlinked: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355188 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
SRU as a merge proposal for both this and bug 1667512 available at Bionic: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 Xenial: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 ** No longer affects: dkms (Ubuntu) ** No longer affects: dkms (Ubuntu Xenial) ** No longer affects: dkms (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+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 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
SRU as a merge proposal for both this and bug 1791959 available at Bionic: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 Xenial: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic
[Touch-packages] [Bug 1667512] Re: [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system
** Summary changed: - update-initramfs hangs on upgrade, dpkg unusable, unbootable system + [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system ** Summary changed: - [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system + [SRU] update-initramfs should sync only the filesystem containing the initramfs image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at
[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
** Description changed: - At least four users, including myself, are having an issue with update- - initramfs hanging while updating ubuntu 16.04. The bug has been - documented while attempting an update to multiple kernel versions ( - 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or - install to fail, and may also lead to an unbootable system. + [Impact] + If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. + + [Test Case] + One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. + + 1. Setup a nfs server and export a directory with write permissions for + the client + + 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) + $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress + Note: adjust the "count" accordingly to how fast/slow your system is. + + 3. Call sync and verify that it only finished after "dd" is done. + + 4. Repeat step #2 and now call "sync -f /boot/". + Verify that it finished immediatly. + + [Regression Potential] + Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. + + [Other] + If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). + + The 'sync' and 'syncfs' specifications are pretty much similar and + syncfs is expected to work the same as a normal sync regarding data + integrity. Also altought the patch introduces the initrd file as an + extra argument which would cause 'sync -f' to fail if the file does not + exist, the update-initramfs script would fail earlier than that because + that file is created by the 'mv' call a few lines above. Thus no + regressions are expected. + + [References] + [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 + [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html + + [Original bug report] + At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade - Fetched 1,571 MB in 2min 9s (12.2 MB/s) + Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic - (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. + (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic - (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
attaching cosmic patch ** Patch added: "initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187984/+files/initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
attaching bionic sru patch ** Patch added: "initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187983/+files/initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
attaching xenial sru patch ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. - This assumes a new Xenial/Bionic/Cosmic schroot. + This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) - sudo touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms + touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: - sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 + apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: - TBD - * cosmic: - TBD + apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: - sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic + apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: - TBD - * cosmic: - TBD + apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel - ls /boot/*.old-dkms + ls -1 /boot/*.old-dkms - 5) install the initramfs-tools that contains this fix - sudo apt-get install -y initramfs-tools + 5) install the initramfs-tools from proposed that contains this fix + apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms - 7) autoremove the older kernel - sudo apt-get autoremove -y + 7) mark kernel images and headers as automatically installed + apt-mark auto linux-image-4*-generic linux-headers-4*-generic - 8) verify that there are now only 2 old-dkms, one for each installed kernel - ls /boot/*.old-dkms + 8) autoremove the older kernel + apt-get autoremove -y + + 9) verify that there are now only 2 old-dkms, one for each installed kernel + ls -1 /boot/*.old-dkms + + + These steps guarantees that: + - orphaned old-dkms are correctly removed from /boot + - non-orphaned old-dkms are kept + - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ** Patch added: "initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187982/+files/initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic:
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
** Summary changed: - remove /boot/initrd.img-*.old-dkms files left behind + [SRU] remove orphaned initrd old-dkms files in /boot ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. - bug 1515513 dealt with removing initrd.img-.old-dkms files - using the kernel's prerm hook, but that is only executed for the kernel - version being removed: any other old-dkms file generated prior to that - would not be removed by the hook, taking space in the /boot directory. + bug 1515513 dealt with removing old-dkms initrd files using the kernel's + prerm hook, but that is only executed for the kernel version being + removed: any other old-dkms file generated prior to that would not be + removed by the hook, taking space in the /boot directory and being + carried forward with every upgrade. - Note: Filling up the /boot partition causes updates to fail. + Note: Filling up the /boot partition causes updates and upgrades to + fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. - This assumes a new Xenial/Bionic schroot. + This assumes a new Xenial/Bionic/Cosmic schroot. - 1) create a file to work as a placeholder for the initrd.img old dkms file - sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms + 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) + sudo touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: + TBD + * cosmic: TBD 3) install the headers for the old kernels (forces dkms to run) * xenial: sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: TBD + * cosmic: + TBD - 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel + 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools - 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel + 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ** Patch removed: "initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187601/+files/initramfs-tools_0.122ubuntu8.12_debdiff_0.122ubuntu8.13.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to
[Touch-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu Xenial) Status: New => Invalid ** Changed in: dkms (Ubuntu Bionic) Status: New => Invalid ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] - As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. + As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. - This assumes a new Xenial schroot. + This assumes a new Xenial/Bionic schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools + * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 + * bionic: + TBD 3) install the headers for the old kernels (forces dkms to run) + * xenial: sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic + * bionic: + TBD 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Invalid Status in initramfs-tools source package in Xenial: New Status in dkms source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: TBD 3) install the headers for the old kernels
[Touch-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu) Importance: Undecided => Medium ** Changed in: dkms (Ubuntu) Status: New => Confirmed ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind
** Changed in: dkms (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing initrd.img-.old-dkms files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory. Note: Filling up the /boot partition causes updates to fail. [Test Case] As the fix for bug 1515513 is available on Xenial it is no longer possible to reproduce this by simply installing and updating kernels (dkms 2.2.0.3-2ubuntu11.3 would be required for that). In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial schroot. 1) create a file to work as a placeholder for the initrd.img old dkms file sudo touch /boot/initrd.img-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools sudo apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 3) install the headers for the old kernels (forces dkms to run) sudo apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic 4) verify that there are 4 old-dkms, the manually created and one for each installed kernel ls /boot/*.old-dkms 5) install the initramfs-tools that contains this fix sudo apt-get install -y initramfs-tools 6) verify that the manually created old-dkms file was removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) autoremove the older kernel sudo apt-get autoremove -y 8) verify that there are now only 2 old-dkms, one for each installed kernel ls /boot/*.old-dkms [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+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 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
** Tags added: bionic xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: update-initramfs hangs on upgrade, dpkg unusable, unbootable system Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic ^CFailed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-63-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-4.4.0-63-generic: linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic (= 4.4.0-63.84); however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-generic: linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; however: Package linux-signed-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-63-generic: linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-extra-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (=
[Touch-packages] [Bug 1679865] Re: coreutils FTBFS during zesty test rebuild
This is caused by a change in the new TZ as reported at [1]. A fix is provided in [2] but required a small change for the first chunk to apply cleanly - see attached debdiff. Other option is to sync the newest version, 8.28-1 [3,4], which includes the fix upstream and builds cleanly. [1] http://lists.gnu.org/archive/html/coreutils/2017-03/msg00026.html [2] http://lists.gnu.org/archive/html/coreutils/2017-03/msg00031.html [3] http://snapshot.debian.org/package/coreutils/8.28-1/ [4] https://tracker.debian.org/pkg/coreutils ** Patch added: "coreutils_8.26-3ubuntu3_8.26-3ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1679865/+attachment/4963059/+files/coreutils_8.26-3ubuntu3_8.26-3ubuntu3.debdiff ** Changed in: coreutils (Ubuntu) Assignee: Matthias Klose (doko) => (unassigned) ** Changed in: coreutils (Ubuntu) Status: New => Confirmed ** Tags added: patch ** Tags added: artful ** Summary changed: - coreutils FTBFS during zesty test rebuild + coreutils FTBFS during zesty/artful test rebuild -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1679865 Title: coreutils FTBFS during zesty/artful test rebuild Status in coreutils package in Ubuntu: Confirmed Bug description: coreutils version 8.26-3ubuntu3 in zesty failed to build on all arches during a test rebuild of the archive. The build log can be found here: https://launchpadlibrarian.net/312365438/buildlog_ubuntu-zesty- amd64.coreutils_8.26-3ubuntu3_BUILDING.txt.gz The failure seems to be: FAIL: tests/misc/date-debug === --- exp3 2017-03-25 05:27:00.477874098 + +++ out3 2017-03-25 05:27:00.481874118 + @@ -4,4 +4,4 @@ date: final: 1.0 (epoch-seconds) date: final: (Y-M-D) 1970-01-01 00:00:01 (UTC0) date: final: (Y-M-D) 1969-12-31 19:00:01 (output timezone TZ=-05:00) -Wed Dec 31 19:00:01 PET 1969 +Wed Dec 31 19:00:01 -05 1969 FAIL tests/misc/date-debug.sh (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1679865/+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 1711449] Re: [FTBFS] lxc build fails due to gcc-7
** Patch added: "lxc_2.0.8-0ubuntu4_2.0.8-0ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1711449/+attachment/4934433/+files/lxc_2.0.8-0ubuntu4_2.0.8-0ubuntu5.debdiff ** Tags added: artful ftbfs patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1711449 Title: [FTBFS] lxc build fails due to gcc-7 Status in lxc package in Ubuntu: New Status in lxc package in Debian: Unknown Bug description: Currently lxc FTBFS due to a GCC-7 bug. There's a upstream report for gcc-7 [1], but meanwhile lxc upstream has applied a workaround that fixes the build [1]. cgroups/cgfsng.c: In function ‘cgfsng_create’: cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be truncated before the last format character [-Werror=format-truncation=] snprintf(offset, 5, "-%d", idx); ^ In file included from /usr/include/stdio.h:938:0, from cgroups/cgfsng.c:44: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of size 5 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, ^~~~ __bos (__s), __fmt, __va_arg_pack ()); ~ cc1: all warnings being treated as errors [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1711449/+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 1711449] [NEW] [FTBFS] lxc build fails due to gcc-7
Public bug reported: Currently lxc FTBFS due to a GCC-7 bug. There's a upstream report for gcc-7 [1], but meanwhile lxc upstream has applied a workaround that fixes the build [1]. cgroups/cgfsng.c: In function ‘cgfsng_create’: cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be truncated before the last format character [-Werror=format-truncation=] snprintf(offset, 5, "-%d", idx); ^ In file included from /usr/include/stdio.h:938:0, from cgroups/cgfsng.c:44: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of size 5 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, ^~~~ __bos (__s), __fmt, __va_arg_pack ()); ~ cc1: all warnings being treated as errors [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #853531 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853531 ** Also affects: lxc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853531 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1711449 Title: [FTBFS] lxc build fails due to gcc-7 Status in lxc package in Ubuntu: New Status in lxc package in Debian: Unknown Bug description: Currently lxc FTBFS due to a GCC-7 bug. There's a upstream report for gcc-7 [1], but meanwhile lxc upstream has applied a workaround that fixes the build [1]. cgroups/cgfsng.c: In function ‘cgfsng_create’: cgroups/cgfsng.c:1381:23: error: ‘__builtin___snprintf_chk’ output may be truncated before the last format character [-Werror=format-truncation=] snprintf(offset, 5, "-%d", idx); ^ In file included from /usr/include/stdio.h:938:0, from cgroups/cgfsng.c:44: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 3 and 6 bytes into a destination of size 5 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, ^~~~ __bos (__s), __fmt, __va_arg_pack ()); ~ cc1: all warnings being treated as errors [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 [2] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1711449/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Import notes about running the testcase in Xenial and Zesty:
1. OpenJDK 8 has not yet been released with the apport hook on Xenial and
Zesty; I copied the source_openjdk-8.py hook file from the apport package-hooks
directory from OpenJDK 8 in artful to the right place in order to test it in
Xenial and Zesty.
2. The HotspotError key was present in all cases when viewing the report with
the apport-cli tool, as expected, and whoopsie *without* the fix ignored the
key and didn't upload it, also as expected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1696814
Title:
add openjdk hs log to list of acceptable_fields in whoopsie
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie source package in Xenial:
Fix Committed
Status in whoopsie source package in Zesty:
Fix Committed
Bug description:
[Impact]
By default OpenJDK 8 generates an hs_err file when it crashes, this file
contains the stacktrace generated by OpenJDK (thus it contains different data
compared to a gdb stacktrace) plus information on the running threads, classes,
and memory usage (OpenJDK's regions). This file is usually required by the
OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case
of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate
from OpenJDK crashes.
OpenJDK 8 now includes a new apport hook to collect additional data
from crash reports as well as the hs_err log file (in the new
HotspotError key).
A new release is soon reaching Zesty and Xenial with the hook included
and without SRU'ing this fix the hs_err file won't be uploaded to the
error tracker.
[Test Case]
Make sure that you are using OpenJDK 8 and to stop whoopsie service before
continuing. If any popup about submitting a crash report shows up at any time,
ignore/cancel it - we are going to manually submit the report to the staging
error tracker (instead of the official one).
# SleepTest.java
public class SleepTest {
public static void main(String[] args) throws Exception {
Thread.sleep(5000);
}
}
1. Run whoopsie:
$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
2. Run the SleepTest and SIGKILL it in another terminal:
$ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest"
3. View the crash report and submit it:
$ apport-cli -c report
/var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash
3a) View the report
3b) [Optional] Search for the "HotspotError" key
3c) Send the report
4. Verify that the report was saved, including the hs_err content:
4a) In whoopsie terminal, check the OOPS ID code
4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID
4c) Confirm that the HotspotError was added to the report
[Regression Potential]
If the new key is added to acceptable_fields whoopsie will upload the entries
in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to
it could allow bigger files with in turn cause an overhead in the error tracker
infrastructure.
[Original bug report]
OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a
Crash report under the HotspotError key. The hook is currently limited to
attaching files under 100 KB.
Please add HotspotError key to the whitelist in order for it to be
available in error tracker.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Results from the testcase in Zesty:
- current whoopsie 0.2.55: no HotspotError (as expected)
https://errors.staging.ubuntu.com/oops/90d56bae-6e50-11e7-8a18-fa163eaf9b83
- proposed whoopsie 0.2.55.1: HotspotError is present (as expected)
https://errors.staging.ubuntu.com/oops/3e464710-6e4f-11e7-8a18-fa163eaf9b83
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1696814
Title:
add openjdk hs log to list of acceptable_fields in whoopsie
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie source package in Xenial:
Fix Committed
Status in whoopsie source package in Zesty:
Fix Committed
Bug description:
[Impact]
By default OpenJDK 8 generates an hs_err file when it crashes, this file
contains the stacktrace generated by OpenJDK (thus it contains different data
compared to a gdb stacktrace) plus information on the running threads, classes,
and memory usage (OpenJDK's regions). This file is usually required by the
OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case
of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate
from OpenJDK crashes.
OpenJDK 8 now includes a new apport hook to collect additional data
from crash reports as well as the hs_err log file (in the new
HotspotError key).
A new release is soon reaching Zesty and Xenial with the hook included
and without SRU'ing this fix the hs_err file won't be uploaded to the
error tracker.
[Test Case]
Make sure that you are using OpenJDK 8 and to stop whoopsie service before
continuing. If any popup about submitting a crash report shows up at any time,
ignore/cancel it - we are going to manually submit the report to the staging
error tracker (instead of the official one).
# SleepTest.java
public class SleepTest {
public static void main(String[] args) throws Exception {
Thread.sleep(5000);
}
}
1. Run whoopsie:
$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
2. Run the SleepTest and SIGKILL it in another terminal:
$ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest"
3. View the crash report and submit it:
$ apport-cli -c report
/var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash
3a) View the report
3b) [Optional] Search for the "HotspotError" key
3c) Send the report
4. Verify that the report was saved, including the hs_err content:
4a) In whoopsie terminal, check the OOPS ID code
4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID
4c) Confirm that the HotspotError was added to the report
[Regression Potential]
If the new key is added to acceptable_fields whoopsie will upload the entries
in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to
it could allow bigger files with in turn cause an overhead in the error tracker
infrastructure.
[Original bug report]
OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a
Crash report under the HotspotError key. The hook is currently limited to
attaching files under 100 KB.
Please add HotspotError key to the whitelist in order for it to be
available in error tracker.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Results from tests on Xenial:
- current whoopsie 0.2.52.3: no HotspotError (as expected)
https://errors.staging.ubuntu.com/oops/5e77a89e-6e4a-11e7-8a18-fa163eaf9b83
- proposed whoopsie 0.2.52.4: HotspotError is present (as expected)
https://errors.staging.ubuntu.com/oops/cfa0113c-6e4a-11e7-8a18-fa163eaf9b83
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1696814
Title:
add openjdk hs log to list of acceptable_fields in whoopsie
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie source package in Xenial:
Fix Committed
Status in whoopsie source package in Zesty:
Fix Committed
Bug description:
[Impact]
By default OpenJDK 8 generates an hs_err file when it crashes, this file
contains the stacktrace generated by OpenJDK (thus it contains different data
compared to a gdb stacktrace) plus information on the running threads, classes,
and memory usage (OpenJDK's regions). This file is usually required by the
OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case
of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate
from OpenJDK crashes.
OpenJDK 8 now includes a new apport hook to collect additional data
from crash reports as well as the hs_err log file (in the new
HotspotError key).
A new release is soon reaching Zesty and Xenial with the hook included
and without SRU'ing this fix the hs_err file won't be uploaded to the
error tracker.
[Test Case]
Make sure that you are using OpenJDK 8 and to stop whoopsie service before
continuing. If any popup about submitting a crash report shows up at any time,
ignore/cancel it - we are going to manually submit the report to the staging
error tracker (instead of the official one).
# SleepTest.java
public class SleepTest {
public static void main(String[] args) throws Exception {
Thread.sleep(5000);
}
}
1. Run whoopsie:
$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
2. Run the SleepTest and SIGKILL it in another terminal:
$ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest"
3. View the crash report and submit it:
$ apport-cli -c report
/var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash
3a) View the report
3b) [Optional] Search for the "HotspotError" key
3c) Send the report
4. Verify that the report was saved, including the hs_err content:
4a) In whoopsie terminal, check the OOPS ID code
4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID
4c) Confirm that the HotspotError was added to the report
[Regression Potential]
If the new key is added to acceptable_fields whoopsie will upload the entries
in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to
it could allow bigger files with in turn cause an overhead in the error tracker
infrastructure.
[Original bug report]
OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a
Crash report under the HotspotError key. The hook is currently limited to
attaching files under 100 KB.
Please add HotspotError key to the whitelist in order for it to be
available in error tracker.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
** Description changed:
- [Impact]
+ [Impact]
By default OpenJDK 8 generates an hs_err file when it crashes, this file
contains the stacktrace generated by OpenJDK (thus it contains different data
compared to a gdb stacktrace) plus information on the running threads, classes,
and memory usage (OpenJDK's regions). This file is usually required by the
OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case
of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate
from OpenJDK crashes.
OpenJDK 8 now includes a new apport hook to collect additional data from
crash reports as well as the hs_err log file (in the new HotspotError
key).
A new release is soon reaching Zesty and Xenial with the hook included
and without SRU'ing this fix the hs_err file won't be uploaded to the
error tracker.
[Test Case]
- 1. Start any java program using OpenJDK 8
- 2. Kill it with SIGILL
- 3. Check that the created report contains the hs_err file
+ Make sure that you are using OpenJDK 8 and to stop whoopsie service before
continuing. If any popup about submitting a crash report shows up at any time,
ignore/cancel it - we are going to manually submit the report to the staging
error tracker (instead of the official one).
- [Regression Potential]
+ # SleepTest.java
+ public class SleepTest {
+ public static void main(String[] args) throws Exception {
+ Thread.sleep(5000);
+ }
+ }
+
+ 1. Run whoopsie:
+ $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
+
+ 2. Run the SleepTest and SIGKILL it in another terminal:
+ $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest"
+
+ 3. View the crash report and submit it:
+ $ apport-cli -c report
/var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash
+ 3a) View the report
+ 3b) [Optional] Search for the "HotspotError" key
+ 3c) Send the report
+
+ 4. Verify that the report was saved, including the hs_err content:
+ 4a) In whoopsie terminal, check the OOPS ID code
+ 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID
+ 4c) Confirm that the HotspotError was added to the report
+
+ [Regression Potential]
If the new key is added to acceptable_fields whoopsie will upload the entries
in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to
it could allow bigger files with in turn cause an overhead in the error tracker
infrastructure.
[Original bug report]
OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a
Crash report under the HotspotError key. The hook is currently limited to
attaching files under 100 KB.
Please add HotspotError key to the whitelist in order for it to be
available in error tracker.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1696814
Title:
add openjdk hs log to list of acceptable_fields in whoopsie
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie source package in Xenial:
Fix Committed
Status in whoopsie source package in Zesty:
Fix Committed
Bug description:
[Impact]
By default OpenJDK 8 generates an hs_err file when it crashes, this file
contains the stacktrace generated by OpenJDK (thus it contains different data
compared to a gdb stacktrace) plus information on the running threads, classes,
and memory usage (OpenJDK's regions). This file is usually required by the
OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case
of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate
from OpenJDK crashes.
OpenJDK 8 now includes a new apport hook to collect additional data
from crash reports as well as the hs_err log file (in the new
HotspotError key).
A new release is soon reaching Zesty and Xenial with the hook included
and without SRU'ing this fix the hs_err file won't be uploaded to the
error tracker.
[Test Case]
Make sure that you are using OpenJDK 8 and to stop whoopsie service before
continuing. If any popup about submitting a crash report shows up at any time,
ignore/cancel it - we are going to manually submit the report to the staging
error tracker (instead of the official one).
# SleepTest.java
public class SleepTest {
public static void main(String[] args) throws Exception {
Thread.sleep(5000);
}
}
1. Run whoopsie:
$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
2. Run the SleepTest and SIGKILL it in another terminal:
$ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest"
3. View the crash report and submit it:
$ apport-cli -c report
/var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash
3a) View the report
3b) [Optional] Search for the "HotspotError" key
3c) Send the report
4. Verify that the report was saved, including the hs_err content:
4a) In whoopsie terminal,
[Touch-packages] [Bug 1705320] [NEW] [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix
Public bug reported: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1705320 Title: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix Status in whoopsie package in Ubuntu: New Bug description: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+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 1705320] Re: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix
** Patch added: "whoopsie_0.2.55_0.2.55.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+attachment/4917749/+files/whoopsie_0.2.55_0.2.55.1.debdiff ** Description changed: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. - The first fix is #1696814 and was added to whoopsie 0.2.56/artful. It - adds the new HotspotError key into the acceptable_fields so that the new - apport hook from OpenJDK 8 can upload the hs_err file generated by - OpenJDK crashes. The file is limited to 100 KB by the hook. + The first fix is tracked by bug #1696814 and was added to whoopsie + 0.2.56/artful. It adds the new HotspotError key into the + acceptable_fields so that the new apport hook from OpenJDK 8 can upload + the hs_err file generated by OpenJDK crashes. The file is limited to 100 + KB by the hook. - The second fix is #1697375 and was added to whoopsie 0.2.57/artful. It - fixes whoopsie queries for NetworkManager state. + The second fix is tracked by bug #1697375 and was added to whoopsie + 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. - The impact, testcase and regression potential are discussed directly on + The impact, testcase and regression potential are discussed directly in the bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1705320 Title: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix Status in whoopsie package in Ubuntu: New Bug description: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+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 1705320] Re: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix
** Patch added: "whoopsie_0.2.52.3_0.2.52.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+attachment/4917748/+files/whoopsie_0.2.52.3_0.2.52.4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1705320 Title: [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix Status in whoopsie package in Ubuntu: New Bug description: whoopsie needs a SRU with 2 recent fixes for both Xenial and Zesty. The first fix is tracked by bug #1696814 and was added to whoopsie 0.2.56/artful. It adds the new HotspotError key into the acceptable_fields so that the new apport hook from OpenJDK 8 can upload the hs_err file generated by OpenJDK crashes. The file is limited to 100 KB by the hook. The second fix is tracked by bug #1697375 and was added to whoopsie 0.2.57/artful. It fixes whoopsie queries for NetworkManager state. The impact, testcase and regression potential are discussed directly in the bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1705320/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
** Description changed: - OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to - a Crash report under the HotspotError key. The hook is currently limited - to attaching files under 100 KB. + [Impact] + By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. + + OpenJDK 8 now includes a new apport hook to collect additional data from + crash reports as well as the hs_err log file (in the new HotspotError + key). + + A new release is soon reaching Zesty and Xenial with the hook included + and without SRU'ing this fix the hs_err file won't be uploaded to the + error tracker. + + [Test Case] + 1. Start any java program using OpenJDK 8 + 2. Kill it with SIGILL + 3. Check that the created report contains the hs_err file + + [Regression Potential] + If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. + + [Original bug report] + OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Triaged Status in whoopsie source package in Zesty: Triaged Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] 1. Start any java program using OpenJDK 8 2. Kill it with SIGILL 3. Check that the created report contains the hs_err file [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1704174] [NEW] update apparmor rules to include wicd's dhclient.conf file
Public bug reported: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "sbin.dhclient-wicd.patch" https://bugs.launchpad.net/bugs/1704174/+attachment/4914177/+files/sbin.dhclient-wicd.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1704174 Title: update apparmor rules to include wicd's dhclient.conf file Status in isc-dhcp package in Ubuntu: New Bug description: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1704174/+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 1647638] Re: W: APT had planned for dpkg to do more than it reported back
Small correction to get the right zz-fail file (needs to escape $), please run: $ sudo tee /etc/kernel/postinst.d/zz-fail
[Touch-packages] [Bug 1647638] Re: W: APT had planned for dpkg to do more than it reported back
I could replicate it on my system, I got the following message on the tests: W: APT had planned for dpkg to do more than it reported back (0 vs 4). Affected packages: linux-image-4.10.0-22-generic:amd64 == Reproducer == $ sudo tee /etc/kernel/postinst.d/zz-fail
[Touch-packages] [Bug 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
** Attachment removed: "source-openjdk-8.py" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892544/+files/source-openjdk-8.py ** Attachment added: "source-openjdk-8.py" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892554/+files/source-openjdk-8.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: New Bug description: OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
This is the proposed openjdk-8 hook. ** Description changed: - This is for Tiago's openjdk apport package hook. + OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to + a Crash report under the HotspotError key. The hook is currently limited + to attaching files under 100 KB. + + Please add HotspotError key to the whitelist in order for it to be + available in error tracker. ** Attachment added: "source-openjdk-8.py" https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892544/+files/source-openjdk-8.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: New Bug description: OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1640320] Re: FTBFS in zesty
I believe that the failed builds were re-run since the first report by Dimitri and then failed due to googletest. After fixing the googletest issues then we end up with another FTBFS caused by missing 'vector' includes. I have added a merge proposal with the fixes in place. ** Branch linked: lp:~tdaitx/location-service/lp-1640320-ftbfs-fix ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty Status in location-service package in Ubuntu: Confirmed Bug description: FTBFS in zesty during a no change rebuild against new boost Please see build logs at: https://launchpad.net/ubuntu/+source /location-service/3.0.0+16.10.20160912-0ubuntu2 Please help fix this [ 10%] Building CXX object src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o cd /<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location && /usr/bin/g++ -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS -Dubuntu_location_service_connectivity_EXPORTS -I/<>/location-service-3.0.0+16.10.20160912/3rd-party -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/json-c -I/<>/location-service-3.0.0+16.10.20160912/include/location_service -I/<>/location-service-3.0.0+16.10.20160912/src/location_service -I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service -I/usr/include/ubuntu -g -O2 -fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra -fPIC -Wno-error=unused-local-typedefs -fPIC -o CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o -c /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp In file included from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0, from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19: /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14: error: ‘vector’ in namespace ‘std’ does not name a template type std::vector xtra_hosts ^~ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10: warning: extra ‘;’ [-Wpedantic] }; ^ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18: error: ‘vector’ in namespace ‘std’ does not name a template type virtual std::vector download_xtra_data(const Configuration& config) = 0; ^~ make -f po/CMakeFiles/pofiles_70.dir/build.make po/CMakeFiles/pofiles_70.dir/depend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+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 1637239] Re: Please merge ncurses 6.0+20160917-1 (main) from Debian unstable (main)
Patch to merge latest debian version (6.0+20161126-1) into to Ubuntu (last merge was 6.0+20160625-1ubuntu1). Remaining changes: - Add a simple autopkgtest to the package. - Build x32 packages. - Build lib32 packages on s390x. The changes have been forwarded to Debian: - http://bugs.debian.org/857000 (autopkgtest) - http://bugs.debian.org/857001 (lib32 packages on s390x) - http://bugs.debian.org/857003 (x32 packages) Thanks to Steve Langasek for the info bellow: The x32 multilib packages (libx32ncurses5) makes as much sense to include in the package as lib32ncurses5 and lib64ncurses5 which are being shipped, and for the same rationale. It's also relevant that there is no official x32 port in either Debian or Ubuntu from which to install the multiarch binaries. Still it might be controversial on Debian because https://bugs.debian.org/848163 requests the removal of the multilib binaries for other arche; has also not been acted on but might be after Debian stretch is released. For now we will be keeping the x32 multilib as it is and going forward with the merge. ** Bug watch added: Debian Bug tracker #857000 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857000 ** Bug watch added: Debian Bug tracker #857001 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857001 ** Bug watch added: Debian Bug tracker #857003 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857003 ** Bug watch added: Debian Bug tracker #848163 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848163 ** Patch added: "ncurses_6.0+20161126-1_ncurses_6.0+20161126-1ubuntu1.diff" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1637239/+attachment/4833150/+files/ncurses_6.0+20161126-1_ncurses_6.0+20161126-1ubuntu1.diff ** Changed in: ncurses (Ubuntu) Assignee: Tiago Stürmer Daitx (tdaitx) => (unassigned) ** Changed in: ncurses (Ubuntu) Status: In Progress => Confirmed ** Description changed: Ubuntu version: 6.0+20160625-1ubuntu1 - Debian verison: 6.0+20160917-1 + Debian verison: 6.0+20161126-1 Details: https://merges.ubuntu.com/n/ncurses/REPORT ** Summary changed: - Please merge ncurses 6.0+20160917-1 (main) from Debian unstable (main) + Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1637239 Title: Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: Confirmed Bug description: Ubuntu version: 6.0+20160625-1ubuntu1 Debian verison: 6.0+20161126-1 Details: https://merges.ubuntu.com/n/ncurses/REPORT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1637239/+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 1637239] [NEW] Please merge ncurses 6.0+20160917-1 (main) from Debian unstable (main)
Public bug reported: Ubuntu version: 6.0+20160625-1ubuntu1 Debian verison: 6.0+20160917-1 Details: https://merges.ubuntu.com/n/ncurses/REPORT ** Affects: ncurses (Ubuntu) Importance: Undecided Assignee: Tiago Stürmer Daitx (tdaitx) Status: In Progress ** Changed in: ncurses (Ubuntu) Status: New => In Progress ** Changed in: ncurses (Ubuntu) Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1637239 Title: Please merge ncurses 6.0+20160917-1 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: In Progress Bug description: Ubuntu version: 6.0+20160625-1ubuntu1 Debian verison: 6.0+20160917-1 Details: https://merges.ubuntu.com/n/ncurses/REPORT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1637239/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
This bug was not related to lcms, but to OpenJDK. Invalidating it for LCMS. ** Changed in: lcms2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Unknown Status in lcms2 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Fix Released Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
IcedTea #1896 tracks the LCMS 2.7 update. The fix for this bug was tracked under IcedTea #3020. ** Bug watch added: Iced Tea Bugzilla #3020 http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3020 ** Changed in: openjdk Importance: Medium => Unknown ** Changed in: openjdk Status: Fix Released => Unknown ** Changed in: openjdk Remote watch: Iced Tea Bugzilla #1896 => Iced Tea Bugzilla #3020 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Unknown Status in lcms2 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Fix Released Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 1598850] Re: [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main)
** Patch added: "debdiff between latest ubuntu version and the merged package (debian directory only, ignore upstream changes)" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+attachment/4697108/+files/ncurses_6.0+20160319-1ubuntu1-ncurses_6.0+20160625-1ubuntu1_debian-dir-only.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1598850 Title: [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: New Bug description: Old Ubuntu version: 6.0+20160319-1ubuntu1 Details: https://merges.ubuntu.com/n/ncurses/REPORT (from https://merges.ubuntu.com/main.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+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 1598850] Re: [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main)
** Patch added: "debdiff between debian and the new merge" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+attachment/4697106/+files/ncurses_6.0+20160625-1-ncurses_6.0+20160625-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1598850 Title: [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: New Bug description: Old Ubuntu version: 6.0+20160319-1ubuntu1 Details: https://merges.ubuntu.com/n/ncurses/REPORT (from https://merges.ubuntu.com/main.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+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 1598850] Re: [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main)
** Patch added: "debdiff between latest ubuntu version and the merged package" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+attachment/4697107/+files/ncurses_6.0+20160319-1ubuntu1-ncurses_6.0+20160625-1ubuntu1.debdiff ** Patch removed: "debdiff between debian and the new merge" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+attachment/4695259/+files/ncurses_6.0+20160319-2_ncurses_6.0+20160319-2ubuntu1.debdiff ** Patch removed: "debdiff between latest ubuntu version and the merged package" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+attachment/4695260/+files/ncurses_6.0+20160319-1ubuntu1_ncurses_6.0+20160319-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1598850 Title: [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: New Bug description: Old Ubuntu version: 6.0+20160319-1ubuntu1 Details: https://merges.ubuntu.com/n/ncurses/REPORT (from https://merges.ubuntu.com/main.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+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 1598850] Re: Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main)
** Patch added: "debdiff between latest ubuntu version and the merged package" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+attachment/4695260/+files/ncurses_6.0+20160319-1ubuntu1_ncurses_6.0+20160319-2ubuntu1.debdiff ** Changed in: ncurses (Ubuntu) Assignee: Tiago Stürmer Daitx (tdaitx) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1598850 Title: Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: In Progress Bug description: Old Ubuntu version: 6.0+20160319-1ubuntu1 Details: https://merges.ubuntu.com/n/ncurses/REPORT (from https://merges.ubuntu.com/main.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+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 1598850] Re: Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main)
** Patch added: "debdiff between debian and the new merge" https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+attachment/4695259/+files/ncurses_6.0+20160319-2_ncurses_6.0+20160319-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1598850 Title: Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: In Progress Bug description: Old Ubuntu version: 6.0+20160319-1ubuntu1 Details: https://merges.ubuntu.com/n/ncurses/REPORT (from https://merges.ubuntu.com/main.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+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 1598850] [NEW] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main)
Public bug reported: Old Ubuntu version: 6.0+20160319-1ubuntu1 Details: https://merges.ubuntu.com/n/ncurses/REPORT (from https://merges.ubuntu.com/main.html) ** Affects: ncurses (Ubuntu) Importance: Undecided Assignee: Tiago Stürmer Daitx (tdaitx) Status: In Progress ** Changed in: ncurses (Ubuntu) Status: New => In Progress ** Changed in: ncurses (Ubuntu) Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1598850 Title: Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: In Progress Bug description: Old Ubuntu version: 6.0+20160319-1ubuntu1 Details: https://merges.ubuntu.com/n/ncurses/REPORT (from https://merges.ubuntu.com/main.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1598850/+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 913434]
Created attachment 1529 testcase to reproduce it Provide jpeg files (at least 128 of them) in a ./jpg directory Run using something like: $ while ! timeout --preserve-status 10 java Lp9133434Imageio; do echo " done."; done as the bug doesn't happen on every run (seem to depend on the jpeg files under test, I can get it once about every 5 runs). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Confirmed Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434]
I was able to reproduce this issue on Ubuntu's IcedTea 2.6.6 running: - the integrated lcms library (disable-system-lcms) - lcms 2.5 and 2.6 system library (enable-system-lcms) For some reason that I haven't been able to track down yet it does depend on the JPEG file under test - a initial sample I grabbed from the internet ran just fine, only when I tested it against bunch grabbed from `locate .jpg` was I able to reproduce it. I haven't tested it against 3.x, but OpenJDK 8u91 runs just fine when using the same lcms 2.6 so I would expect similar results. Let me know if hs_err and/or core files would be of any help, as well as running it against an upstream IcedTea build (Ubuntu does not patch anything related to lcms). Started a few testes after an Ubuntu user reported running into this issue (https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/913434). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Confirmed Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434]
Got together a bunch of images from the various hs_err I had at hand. I was unable to keep the file under 1 MB for upload, thus I uploaded it here: https://drive.google.com/open?id=0Bw-FF32TRkU3MFdFOXF4dlZ0c2s -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Confirmed Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
I was unable to reproduce it yesterday, but it was due to the jpeg files I was using. I repeated it today with different jpeg files and reproduced it. Got a crash on OpenJDK 7u101 with both LCMS 2.5 (Trusty) and 2.6 (Wily), also reproduced when using the LCMS lib that comes with OpenJDK (by default Ubuntu uses the lib from lcms2-2 package). OpenJDK 8 on Wily uses the same LCMS and does not crash. I will report this upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 1582692] Re: OOM using CRON but not using SHELL under 16.04
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Can you reproduce it with other java programs?
* Can you reproduce it with a smaller -Xmx?
* What specific steps should we take to recreate this bug?
Please provide:
* How much RAM your system has (so I can try to simulate the % of used and
available RAM)
* Your crontab and under which user it is being run
* (If at all possible) a sample of the program you are trying to run (or the
program + settings)
This will help us to find and resolve the problem, as I have been so far
unable to reproduce it.
** Changed in: cron (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1582692
Title:
OOM using CRON but not using SHELL under 16.04
Status in cron package in Ubuntu:
Incomplete
Bug description:
When I start a java program with high memory usage ("-Xmx52g") by
shell, everything is working well. However if I start the same program
with the same command and same user by CRON, I get a
java.lang.OutOfMemoryError just after a few seconds.
Additionally CRON isn't able to do anything as long as I don't kill
the blocked java program. No matter which cronjob should be started,
it always ends up with "(CRON) error (can't fork)" in syslog. After
killing the java program all new cronjobs are working fine again.
The problem only occurs with Ubuntu 16.04, all older versions worked
very well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1582692/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
Mauro, Thanks for the additional information. Your and IcedTea's reports seem to indicate that LCMS 2.5 is the culprit for not being thread safe. I will try to reproduce it later on so I can test if a newer version does indeed fix this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 913434] Re: ImageIO crashes (core dumped) while reading many image files
Mauro, Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? * Does it affect OpenJDK 6 as well? Please post or attach the error output so we can verify it is actually the same bug. This will help us to find and resolve the problem. ** Changed in: lcms2 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: openjdk-7 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+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 1503450] [NEW] mesa FTBFS due to missing Requires in mirclient
Public bug reported:
mesa currently FTBFS due to a missing mirclient dependency during build
time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"Mesa\"
-DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=1
-DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../src/
gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal error:
mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in mesa package in Ubuntu:
New
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main
[Touch-packages] [Bug 1503450] Re: mesa FTBFS due to missing Requires in mirclient
This patch forces autoconf to use mirclient in addition to mir-client-
platform-mesa-dev
** Also affects: mir
Importance: Undecided
Status: New
** Patch added: "force mirclient dependency"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1503450/+attachment/4486549/+files/mesa_11.0.2-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in Mir:
New
Status in mesa package in Ubuntu:
New
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../sr
c/gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal
error: mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1503450/+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 1503450] Re: mesa FTBFS due to missing Requires in mirclient
This patch adds "Requires: mirclient = @MIR_VERSION@" in
src/platforms/mesa/mir-client-platform-mesa-dev.pc.in
** Patch added: "mir patch: add "Requires: mirclient"
mir-client-platform-mesa-dev.pc.in"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1503450/+attachment/4486550/+files/add-mirclient-requires.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in Mir:
New
Status in mesa package in Ubuntu:
New
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../sr
c/gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal
error: mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1503450/+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 115475] Re: tproxy support (iptables & squid)
** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/115475 Title: tproxy support (iptables & squid) Status in Squid: Fix Released Status in iptables package in Ubuntu: Fix Released Status in squid3 package in Ubuntu: Fix Released Status in squid package in Debian: Fix Released Bug description: tproxy is a module which makes building squid as an invisible acceleration proxy possible. Currently you have to alter your network topology to plug squid in like that, but with this module the squid box becomes an invisible bridge (not even traceroute can find it). It is available in patch-o-matic and would be very handy. To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/115475/+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
