[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV

[Tiago Pasqualini da Silva]

** Description changed:

+ [ Impact ]
+ 
  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:
  
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158
  
- The following patch fixes the issue:
- 
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8
  
- I was able simulate it to happen on gdb, by breaking once the manager is
- setup, getting the loopback device and running link_drop_foreign_config
- on the loopback device:
+ This can be fixed by simply null checking link->network before doing anything 
with it. Upstream has fixed it on this commit: 
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8
+ 
+ [ Test Plan ]
+ 
+ Since this issue is hard to reproduce, I was able trigger it on gdb, by
+ adding a breakpoint once the manager is setup, getting the loopback
+ device and running link_drop_foreign_config on the loopback device:
  
  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
  Starting program: /lib/systemd/systemd-networkd
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL
  
  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
  $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000",
  n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
  storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
  type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
  $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772,
    state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
    __u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0,
    flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state = 
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0,
    address_label_messages = 0, route_messages = 0, 
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0, 
enslaving = 0,
    addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0, 
routes_foreign = 0x55796180, addresses_configured = false,
    addresses_ready = false, dhcp_client = 0x0, dhcp_lease = 0x0, lease_file = 
0x5579c620 "/run/systemd/netif/leases/1", original_mtu = 0,
    dhcp4_messages = 0, dhcp4_configured = false, dhcp6_configured = false, 
ndisc_messages = 0, ndisc_configured = false, ipv4ll = 0x0

[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV on bionic

[Tiago Pasqualini da Silva]

** Description changed:

  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:
  
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158
  
  The following patch fixes the issue:
  
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8
  
- 
- I was able simulate it to happen on gdb, by breaking once the manager is 
setup, getting the loopback device and running link_drop_foreign_config on the 
loopback device:
- 
+ I was able simulate it to happen on gdb, by breaking once the manager is
+ setup, getting the loopback device and running link_drop_foreign_config
+ on the loopback device:
  
  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
- Starting program: /lib/systemd/systemd-networkd 
+ Starting program: /lib/systemd/systemd-networkd
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL
  
  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
- $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000", 
- n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
- storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
 
- type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
+ $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000",
+ n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
+ storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
+ type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
- $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772, 
-   state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
-   __u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0, 
-   flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state = 
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0, 
-   address_label_messages = 0, route_messages = 0, 
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0, 
enslaving = 0, 
-   addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0, 
routes_foreign = 0x55796180, addresses_configured = false, 
-   addresses_ready

[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV on bionic

[Tiago Pasqualini da Silva]

** Also affects: ubuntu-pro
   Importance: Undecided
   Status: New

** Also affects: ubuntu-pro/18.04
   Importance: Undecided
   Status: New

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

Title:
  systemd-networkd crashes with SIGSEGV on bionic

Status in systemd:
  New
Status in Ubuntu Pro:
  New
Status in Ubuntu Pro 18.04 series:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158

  The following patch fixes the issue:
  
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8

  
  I was able simulate it to happen on gdb, by breaking once the manager is 
setup, getting the loopback device and running link_drop_foreign_config on the 
loopback device:

  
  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
  Starting program: /lib/systemd/systemd-networkd 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL

  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
  $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000", 
  n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
  storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
 
  type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
  $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772, 
state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0, 
flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state = 
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0, 
address_label_messages = 0, route_messages = 0, 
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0, 
enslaving = 0, 
addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0, 
routes_foreign = 0x55796180, addresses_configured = false, 
addresses_ready = false, dhcp_client = 0x0, dhcp_lease = 0x0, lease_file = 
0x5579c620 "/run/systemd/netif/leases/1", original_mtu = 0, 
dhcp4_messages = 0, dhcp4_configured = false, dhcp6_configured = false,

[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV on bionic

[Tiago Pasqualini da Silva]

** Project changed: netplan => systemd

** Changed in: systemd
 Assignee: (unassigned) => Tiago Pasqualini da Silva (tiago.pasqualini)

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  systemd-networkd crashes with SIGSEGV on bionic

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Customer reported that this issue happens randomly during their
  automated regression runs. It's not consistent and hard to reproduce.
  They have shared a coredump:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  2741 ../src/network/networkd-link.c: No such file or directory.
  (gdb) bt
  #0 0x555962aa1c34 in link_drop_foreign_config 
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
  #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
  #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) 
at ../src/network/networkd-link.c:3698
  #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, 
userdata=) at ../src/network/networkd-manager.c:713
  #4 0x555962a48a16 in process_match (m=0x5559635702c0, 
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
  #5 process_running (ret=0x0, rtnl=0x55596355d990) at 
../src/libsystemd/sd-netlink/sd-netlink.c:418
  #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at 
../src/libsystemd/sd-netlink/sd-netlink.c:452
  #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
  #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at 
../src/libsystemd/sd-event/sd-event.c:2311
  #9 0x555962a4de2a in sd_event_dispatch (e=, 
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
  #10 0x555962a4dfb9 in sd_event_run (e=, 
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2723
  #11 0x555962a4e1fb in sd_event_loop (e=) at 
../src/libsystemd/sd-event/sd-event.c:2744
  #12 0x555962a223d6 in main (argc=, argv=) 
at ../src/network/networkd.c:158

  The following patch fixes the issue:
  
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8

  
  I was able simulate it to happen on gdb, by breaking once the manager is 
setup, getting the loopback device and running link_drop_foreign_config on the 
loopback device:

  
  (gdb) b src/network/networkd.c:150
  Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
  (gdb) r
  Starting program: /lib/systemd/systemd-networkd 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  eth0: IPv6 successfully enabled
  eth0: Gained IPv6LL

  Breakpoint 1, main (argc=, argv=) at 
../src/network/networkd.c:152
  152   log_info("Enumeration completed");
  (gdb) p *m->links
  $1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage 
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000", 
  n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256, 
_pad = "\000\000"}, direct = {
  storage = 
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
 
  type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2, 
from_pool = true}}
  (gdb) set $mylink = (Link **) malloc(sizeof(Link *))
  (gdb) call link_get(m, 1, $mylink)
  $2 = 0
  (gdb) p *$mylink
  $3 = (Link *) 0x557a3f70
  (gdb) p **$mylink
  $4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0, 
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772, 
state_file = 0x5579c670 "/run/systemd/netif/links/1", mac = 
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0, 
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0, 
flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state = 
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0, 
address_label_messages = 0, route_messages = 0, 
routing_policy_rule_messages = 0, routing_policy_rule_remove_messages = 0, 
enslaving = 0, 
addresses = 0x0, addresses_foreign = 0x55796120, routes = 0x0, 
routes_foreign = 0x55796180, addresses_configured = false, 
addresses_ready = false, dhcp_client = 0x0, dhcp_lease = 0x0, lease_file = 
0x5579c620 "/run

[Touch-packages] [Bug 2000173] Re: Xorg freeze

[Tiago Matias]

I would also like to add that this issue also manifests when the display
goes to sleep.

Moving the mouse or touching the keyboard (which should wake the display
up) produces no effect and requires turning the monitor off and on
again.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  I have a persistent issue where my freshly installed Ubuntu sleeps the
  monitor after booting.

  The solution is to turn the monitor off and on again. After turning it
  on the login screen is displayed.

  Note that when the screen is off even the combination CTRL+ALT+F2 to
  switch to a console TTY will not work.

  Rarely the system will boot to the login sleep without the screen
  going to sleep.

  There is the following message on dmesg:

  [   63.052273] amdgpu :0a:00.0: [drm] *ERROR* mstb
  d9e48d98 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed

  System: Ubuntu 22.04.1 LTS
  CPU: AMD Ryzen 5 5600x 6-core processor × 12
  GPU: AMD Radeon rx 6900 xt
  Monitor: DELL Ultrasharp U3415W connected with a Display Port <-> 
mini-Display Port cable.

  Using the default Ubuntu graphical drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 20 18:21:07 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 
6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 6900 XT 
[1002:0e3a]
  InstallationDate: Installed on 2022-12-05 (14 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=UUID=08da7c47-3c82-4be1-8f1e-3546fd436ec5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2423
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B550-I GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2423:bd08/11/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

[Tiago Stürmer Daitx]

@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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

> 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

** 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 1888101] Re: 'unsupported protocol' error when using PyMySQL

[Tiago]

Hi Seth,

In my case its sort of a complicated setup. We have a MariaDB running on an 
Ubuntu 18.04 server with SSL and ed25519. Then, I followed the instructions on 
the Superset documentation for manual installation 
(https://superset.incubator.apache.org/installation.html) and installed the 
software on an Ubuntu 20.04. When using the mysqldb python driver the Superset 
software was giving out an error and I decided to try to change to PyMySQL 
(since superset uses SLQAlchemy should not make a big difference). Then the 
error is shown when trying to connect.
I haven't tried another version of Python or Openssl.

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

Title:
  'unsupported protocol' error when using PyMySQL

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  openssl:
Installiert:   1.1.1f-1ubuntu2
Installationskandidat: 1.1.1f-1ubuntu2
Versionstabelle:
   *** 1.1.1f-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) + 4)
  I am trying to connect to my MariaDB with python package "PyMySQL" and SSL 
enabled. On my old installation (Kubuntu 19.10) this worked. With the new 
installation (also new PC: Xubuntu 20.04) I get this error message:

  ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
  (_ssl.c:1108)

  Here are my installation details:
  Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 
28 May 2019
  New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 
31 Mar 2020

  When I use python with a different SSL version...:
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX 
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 
  this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 

  
  It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does 
not work together with PyMySQL.

  Some more details I have posted here:
  
https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1f-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Jul 18 15:42:27 2020
  InstallationDate: Installed on 2020-07-13 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1888101/+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 1888101] Re: 'unsupported protocol' error when using PyMySQL

[Tiago]

Hi, I'm having a similar issue. Mariadb server with ssl connection, I'm
trying to connect a software called Superset with PyMySQL driver. Error
message looks identical:

WARNING:superset.views.core:Connection failed (pymysql.err.OperationalError) 
(2003, "Can't connect to MySQL server on '' ([SSL: 
UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1108))")
(Background on this error at: http://sqlalche.me/e/13/e3q8)

Client running on Ubuntu 20.04

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

Title:
  'unsupported protocol' error when using PyMySQL

Status in openssl package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  openssl:
Installiert:   1.1.1f-1ubuntu2
Installationskandidat: 1.1.1f-1ubuntu2
Versionstabelle:
   *** 1.1.1f-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) + 4)
  I am trying to connect to my MariaDB with python package "PyMySQL" and SSL 
enabled. On my old installation (Kubuntu 19.10) this worked. With the new 
installation (also new PC: Xubuntu 20.04) I get this error message:

  ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
  (_ssl.c:1108)

  Here are my installation details:
  Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 
28 May 2019
  New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 
31 Mar 2020

  When I use python with a different SSL version...:
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX 
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 
  this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 

  
  It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does 
not work together with PyMySQL.

  Some more details I have posted here:
  
https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1f-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Jul 18 15:42:27 2020
  InstallationDate: Installed on 2020-07-13 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

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] 
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2

[Touch-packages] [Bug 1449250] Re: Keyboard Layout "Portuguese (Brazil, nativo for US keyboards)" doesn't respect US keyboard layout.

[Tiago Quadra]

Ubuntu 18.04.2 LTS and the problem still persist.

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

Title:
  Keyboard Layout "Portuguese (Brazil, nativo for US keyboards)" doesn't
  respect US keyboard layout.

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  When setting up the keyboard layout to my bluetooth keyboard on my machine I 
saw the option to add a layout specific to Portuguese with the promise it would 
work with USA keyboards.
  But many letters are assigned to the wrong codes.

  1. I'm using Ubuntu 14.04
  2. I don't know the package responsible for this behaviour
  3. I expected a behaviour similar to English USA International layout, but 
with cedilla when you press ' + C instead of the "ć" it currently generates.

  Pressing all characters keys on a USA keyboard should give the following 
result(with spaces between them and enter after each row of keys):
  ` 1 2 3 4 5 6 7 8 9 0 - =
  q w e r t y u i o p [ ] \
  a s d f g h j k l ; '
  z x c v b n m , . /

  4. While using "Portuguese (Brazil, nativo for USA keyboards)" layout it gives
  = 1 2 3 4 5 6 7 8 9 0 [ ]
  / , . h x w l t c p ~ - '
  i e a o u m d s r n '
  y ; j b k q v g f z

  If you look at the keyboard layout chart, you'll see it has nothing to
  do with USA keyboards and specially nothing like to what is sold here
  in Brazil.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1449250/+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 1823125] Re: tomcat9 fails to install in 18.04

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

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&feel) 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&feel 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&feel 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

[Tiago Stürmer Daitx]

-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]

[Tiago Stürmer Daitx]

:
  * 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

[Tiago Stürmer Daitx]

** 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]

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

> 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Tiago Maurício]

I am running Ubuntu 16.04 with plasma. I was experiencing this issue and
downgraded the network-manager package to 1.2.2-0ubuntu0.16.04.4. Since
the downgrade I haven't had any trouble. Waiting for fix in the latest
version :)

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

[Tiago Stürmer Daitx]

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.
  vmlinuz(/boot/vmlinuz-

[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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
   (/boot/vmlinuz-4.4.0-6

[Touch-packages] [Bug 1667512] Re: [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg unusable, unbootable system

[Tiago Stürmer Daitx]

** 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 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.post

[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system

[Tiago Stürmer Daitx]

** 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 491.

[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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:
  Invali

[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

[Tiago Stürmer Daitx]

** 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 t

[Touch-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind

[Tiago Stürmer Daitx]

** 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 (f

[Touch-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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 (= 4.4.0.6

[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

[Tiago]

Ubuntu 18 is still with the same bug

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1679865] Re: coreutils FTBFS during zesty test rebuild

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

** 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, ch

[Touch-packages] [Bug 1705320] [NEW] [SRU] update whoopsie to include openjdk's hotspoterror key and network manager state fix

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

** 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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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)

[Tiago Stürmer Daitx]

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 1662868] [NEW] Changes to organizationName management break qt-labs-settings

[Tiago Salem Herrmann]

Public bug reported:

Recent changes to the way ubuntu-ui-toolkit handles the organizationName
break the qml Settings component. It cannot access the right
configuration files as organizationName is used to build the
configuration file paths.

I added more details to this comment on the MR that introduced the regression:
https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/organizedWindow/+merge/314631/comments/820497

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Assignee: Christian Dywan (kalikiana)
 Status: New

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

Title:
  Changes to organizationName management break qt-labs-settings

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Recent changes to the way ubuntu-ui-toolkit handles the
  organizationName break the qml Settings component. It cannot access
  the right configuration files as organizationName is used to build the
  configuration file paths.

  I added more details to this comment on the MR that introduced the regression:
  
https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/organizedWindow/+merge/314631/comments/820497

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1662868/+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 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Tiago Carrondo]

rm .config/connectivity-service/config.ini.lock

solved my problem instantly!

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

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

  -

  Per the comments the .config/connectivity-service/config.ini file
  seems to hold bad or outdated info and needs to be manually deleted
  and then recreated by the service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+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 1655022] Re: Image preview no longer works

[Tiago Salem Herrmann]

** Branch linked: lp:~phablet-team/messaging-app/fix-attachments-preview

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

Title:
  Image preview no longer works

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  rc-proposed
  Tap on an image attachment and nothing happens.
  Works fine on OTA 14.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1655022/+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)

[Tiago Stürmer Daitx]

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 1516696] Re: SMS notifications are received only when the phone is unlocked

[Tiago Salem Herrmann]

So, while debugging this issue I found the following:

The delay seems to be bigger if wifi is disabled. If wifi is enabled,
after 1:30 at most the device wakes up, and if no wifi, device seems to
remain off indefinitely (I waited only for 10 minutes then gave up). In
my case, it's krillin and I have only one sim in the second slot. At
first I thought that could be lack of entropy and the system would be
stuck trying to read from /dev/urandom, but turns out this is what I
found:

1) oFono delivers the message to telepathy-ofono right away.
2) telepathy-ofono informs telepathy about the new message.
3) telephony-service-indicator gets the message, sets a timer 
(QTimer::singleShot()) of 1.5 seconds before displaying the message (that's to 
avoid displaying notifications for messages that were already displayed in 
messaging-app.

4) Then I noticed that the triggered() signal is never emitted, until I
manually force the device to wake up.

5) running an strace on telephony-service-indicator and (leaving the
device stuck for about 1 minute) I get this:

[pid  2231] 1474573884.069934 clock_gettime(CLOCK_MONOTONIC, {1265, 272122461}) 
= 0
[pid  2231] 1474573884.070193 clock_gettime(CLOCK_MONOTONIC, {1265, 272383307}) 
= 0
[pid  2231] 1474573884.070407 poll([{fd=3, events=POLLIN}, {fd=6, 
events=POLLIN}, {fd=7, events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, 
events=POLLIN}], 5, 1571) = 0 (Timeout)
[pid  2231] 1474573951.500698 read(3, 0xbed2817c, 16) = -1 EAGAIN (Resource 
temporarily unavailable)
[pid  2231] 1474573951.500977 clock_gettime(CLOCK_MONOTONIC, {1266, 845932613}) 
= 0
[pid  2231] 1474573951.501380 clock_gettime(CLOCK_MONOTONIC, {1266, 846369074}) 
= 0


Someone please correct me if I am missing something, but from my understanding 
qt is stuck in the event loop waiting for the timer event, which only happens 
after I press the power button.

What worries me here is that the call to poll() explicitly sets the
timeout for 1571 (1.5 seconds), and -apparently- it only timed out after
67 seconds, which is when the next call to read() is executed.

An additional information is that on dbus I always see indicator-
datetime emitting a signal (Changed()) as soon as telephony-service-
indicator also gets unblocked, which is a strong indication that
indicator-datetime is also getting affected by this.

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

Title:
  SMS notifications are received only when the phone is unlocked

Status in Canonical System Image:
  Confirmed
Status in powerd:
  New
Status in Unity System Compositor:
  New
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  WHAT HAPPENED:
  The phone stays quiet while locked but once the power button is pressed 
(unlocked), SMS notification are received with vibration, notification bubble 
and sound alert. The message received shows that it was actually received 10 
minutes ago.
  This happened multiple times already but I think I ignored them and this 
seems to have started after OTA-7 was released.

  
  EXPECTED:
  The phone should have the vibration, notification bubble/indicator and sound 
alert even if the phone is locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516696/+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 1516696] Re: SMS notifications are received only when the phone is unlocked

[Tiago Salem Herrmann]

The flow is ofono -> telepathy-ofono -> telephony-service-indicator ->
Notification

My guess is that telephony-service-indicator could be stuck for some
reason (waiting on some dbus call to finish or something like that).

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

Title:
  SMS notifications are received only when the phone is unlocked

Status in Canonical System Image:
  Confirmed
Status in powerd:
  New
Status in Unity System Compositor:
  New
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  WHAT HAPPENED:
  The phone stays quiet while locked but once the power button is pressed 
(unlocked), SMS notification are received with vibration, notification bubble 
and sound alert. The message received shows that it was actually received 10 
minutes ago.
  This happened multiple times already but I think I ignored them and this 
seems to have started after OTA-7 was released.

  
  EXPECTED:
  The phone should have the vibration, notification bubble/indicator and sound 
alert even if the phone is locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516696/+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 1613471] Re: [MIR] telepathy-ofono

[Tiago Salem Herrmann]

Yes, maybe use XDG_SESSION_DESKTOP could be a good solution, but we
decided to remove the dependency of telepathy-ofono from telephony-
service, so I believe once we land that change this MIR won't be needed
anymore.

https://requests.ci-train.ubuntu.com/#/ticket/1902

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

Title:
  [MIR] telepathy-ofono

Status in telepathy-ofono package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by nuntium and telephony-service.

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   * This package depends on ofono, ofono-qt, libphonenumber7 and 
telepathy-qt5. (none of them are currently in main)

  [Standards compliance]
   * This package uses cmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1613471/+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 1613469] Re: [MIR] ofono-qt

[Tiago Salem Herrmann]

- libqofono did not exist by the time telepathy-ofono was created, and
ofono-qt was the only alternative. libqofono started as a fork of ofono-
qt IIRC.

- The tests work with ofono-phonesim (actually phonesim is required).

- Some tests require manual interaction:
http://paste.ubuntu.com/23085781/

- We don't have a roadmap AFAIK.

- It will be a lot of effort to move tp-ofono to link against libqofono.
We have patches in ofono-qt that change some internal logic and add
custom features that are probably not part of libqofono yet. Even the
telepathy-ofono tests are based on ofono-qt. There is a mock to simulate
a real modem using ofono-qt as base.

- If moving ofono-qt to main is really a blocker, as a short term
solution I would say we could move ofono-qt into telepathy-ofono (since
we already have part of the code there for tests), and than come up with
a roadmap to finally move telepathy-ofono to link against libqofono.

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

Title:
  [MIR] ofono-qt

Status in ofono-qt package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by telepathy-ofono

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests, but not executed during build because they 
require ofono to be running.

  [Dependencies]
   * This package depends only on qt5 which is already in main.

  [Standards compliance]
   * This package uses qmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1613469/+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 1613471] Re: [MIR] telepathy-ofono

[Tiago Salem Herrmann]

- I believe telepathy-ofono-ril-mc-plugin is disabled on most archs
because it depends on libhybris-utils, and that is not available on all
architectures.

- telepathy-ofono uses libpulse to change the system audio routes when
there is an incoming call and other call events. That affects the entire
system, so by the time we created the package (3 years ago) that was the
only way to make sure it wasn't going to break audio of desktops. This
audio management should be done outside of telepathy-ofono. We had a
discussion some time ago and decided to create a pulse module to take
care of that, but it is still not done.

- Those crashes are mostly related to pulse audio. I believe some of
them are actually fixed by now.

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

Title:
  [MIR] telepathy-ofono

Status in telepathy-ofono package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by nuntium and telephony-service.

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   * This package depends on ofono, ofono-qt, libphonenumber7 and 
telepathy-qt5. (none of them are currently in main)

  [Standards compliance]
   * This package uses cmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1613471/+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 1613469] Re: [MIR] ofono-qt

[Tiago Salem Herrmann]

Tests are not executed because they rely on ofonod running with some
modem enabled, which is not doable on test environments.

Yes, it was abandoned upstream because ofono-qt was mostly replaced by 
libqofono.
This is the main reason why it has no bugs open.

There was some discussion to move telepathy-ofono to use libqofono
(currently telepathy-ofono is the only package linking against it), but
it would require a lot of effort and would risk introducing new bugs to
the telephony stack, which is not an option at the moment.

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

Title:
  [MIR] ofono-qt

Status in ofono-qt package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by telepathy-ofono

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests, but not executed during build because they 
require ofono to be running.

  [Dependencies]
   * This package depends only on qt5 which is already in main.

  [Standards compliance]
   * This package uses qmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1613469/+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 1616028] [NEW] does not detect bluetooth mouse Thinkpad X1

[Tiago Policarpo]

Public bug reported:


does not list the device.
some help to debug.

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

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

Title:
  does not detect bluetooth mouse Thinkpad X1

Status in bluez package in Ubuntu:
  New

Bug description:
  
  does not list the device.
  some help to debug.

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

[Tiago Stürmer Daitx]

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

[Tiago Stürmer Daitx]

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 1613474] [NEW] [MIR] telepathy-qt5

[Tiago Salem Herrmann]

Public bug reported:

[Availability]
 * Available in universe

[Rationale]
 * This package is required by telephony-service, history-service, 
telepathy-ofono and media-hub.

[Security]
 * No known security issues at this time.

[Quality assurance]
 * This package has unit tests, but not executed during build time.

[Dependencies]
 * This package depends on libtelepathy-farstream3.

[Standards compliance]
 * This package uses cmake and does not require translation.

[Maintenance]
 * Actively developed upstream: 
https://cgit.freedesktop.org/telepathy/telepathy-qt/
 * Packaging maintained in bzr by the phablet team and actively in use on the 
phone and tablet images. Additional patch has been added to fix building with 
gstreamer support on ubuntu.

** Affects: telepathy-qt5 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [MIR] telepathy-qt5

Status in telepathy-qt5 package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by telephony-service, history-service, 
telepathy-ofono and media-hub.

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests, but not executed during build time.

  [Dependencies]
   * This package depends on libtelepathy-farstream3.

  [Standards compliance]
   * This package uses cmake and does not require translation.

  [Maintenance]
   * Actively developed upstream: 
https://cgit.freedesktop.org/telepathy/telepathy-qt/
   * Packaging maintained in bzr by the phablet team and actively in use on the 
phone and tablet images. Additional patch has been added to fix building with 
gstreamer support on ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-qt5/+bug/1613474/+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 1613469] [NEW] [MIR] ofono-qt

[Tiago Salem Herrmann]

Public bug reported:

[Availability]
 * Available in universe

[Rationale]
 * This package is required by telepathy-ofono

[Security]
 * No known security issues at this time.

[Quality assurance]
 * This package has unit tests, but not executed during build because they 
require ofono to be running.

[Dependencies]
 * This package depends only on qt5 which is already in main.

[Standards compliance]
 * This package uses qmake and requires no translation.

[Maintenance]
 * This package is maintained by Canonical and actively in use on the phone and 
tablet images

** Affects: ofono-qt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [MIR] ofono-qt

Status in ofono-qt package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by telepathy-ofono

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests, but not executed during build because they 
require ofono to be running.

  [Dependencies]
   * This package depends only on qt5 which is already in main.

  [Standards compliance]
   * This package uses qmake and requires no translation.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono-qt/+bug/1613469/+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 1612277] [NEW] Tapping the green bar during calls does not bring dialer-app to foreground.

[Tiago Salem Herrmann]

Public bug reported:

This seems to be xenial only.

I flashed the device with channel ubuntu-touch/staging/bq-aquaris.en and
installed silo 11 (with new qt 5.6).

I noticed that tapping the green top bar during calls does not bring
dialer-app to foreground anymore. I'm still not sure if this was
introduced on xenial or only after installing silo 11.

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

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

Title:
  Tapping the green bar during calls does not bring dialer-app to
  foreground.

Status in unity8 package in Ubuntu:
  New

Bug description:
  This seems to be xenial only.

  I flashed the device with channel ubuntu-touch/staging/bq-aquaris.en
  and installed silo 11 (with new qt 5.6).

  I noticed that tapping the green top bar during calls does not bring
  dialer-app to foreground anymore. I'm still not sure if this was
  introduced on xenial or only after installing silo 11.

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

[Tiago Stürmer Daitx]

** 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)

[Tiago Stürmer Daitx]

** 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)

[Tiago Stürmer Daitx]

** 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)

[Tiago Stürmer Daitx]

** 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)

[Tiago Stürmer Daitx]

** 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)

[Tiago Stürmer Daitx]

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 1461873] Re: [messaging] Ability to forward SMS without copy 'n past approach

[Tiago Salem Herrmann]

** Branch linked: lp:~tiagosh/messaging-app/forward-support

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

Title:
  [messaging] Ability to forward SMS without copy 'n past approach

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if the SMS app swipe left context had the ability to forward 
the SMS to other receivers.
  The existing approah where one can swipe left and copy the content and then 
paste into a new SMS seems less intuitive.

  **

  This feature is in the new designs but has yet to be implemented.
  https://docs.google.com/presentation/d/1hkrF2g-
  ad7fhJ0UVLKmu_5ZXSFK1EkcWS129JxmAAI4/edit#slide=id.p97

  **

  This is a certification requirement

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461873/+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 1588127] Re: Phone abandons incoming call

[Tiago Salem Herrmann]

I am seeing timeout from the approver while trying to create an instance
of media-hub in the dbus.log file.

Media-hub is a telepathy observer (it watches telepathy to stop music
when there is an incoming call), and telepathy by design won't forward
the incoming call to the approver (to display the snap decision) until
all observers confirm receiving the incoming channel first.

If media-hub is really stuck for some reason, that would explain the
issue, since after a dbus timeout trying to deliver the channel to
media-hub, telepathy would still try to deliver the channel to the
approver, which would make the snap decision appear, and quickly
disappear (since the incoming call is already gone).

This is a guess, but seems to match what Matthew described, and what I
see in the logs:

-

virtual QMediaService* AalServicePlugin::create(const QString&)
"org.qt-project.qt.mediaplayer"
Failed to start a new media-hub player session:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
Failed to create a new media player backend. Video playback will not function.

Could not finish contructing new AalMediaPlayerService instance since
m_hubPlayerSession is NULL



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

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+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 1588127] Re: Phone abandons incoming call

[Tiago Salem Herrmann]

Thanks for the logs,
could you also grab the dbus logs using the steps I provided on comment #6 
using adb?

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

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+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