[Touch-packages] [Bug 1734702] Re: perldoc shows lots of escapes

2018-01-08 Thread Eliah Kagan 
This bug affects my Lubuntu 17.10 (64-bit) system, which has version
5.26.0-8ubuntu1 of the perl and perl-doc packages. I noticed the bug
immediately upon checking for it after Zanna (https://launchpad.net
/~rose-anna-bleasdale / https://askubuntu.com/users/527764/zanna)
reported experiencing it in Ubuntu MATE 17.10. Until this bug is fixed,
I suggest the workaround of setting the PAGER environment variable to
"less" so that the proper configuration for less is used; other full
workarounds are also effective (see below).

The problem does not appear to depend in any way on what sort of
terminal emulator is used. I tried in LXTerminal (TERM=xterm), XTerm
(TERM=xterm), a virtual console (TERM=linux), and via SSH (TERM=xterm).
Zanna tried in MATE Terminal (TERM=xterm), GNOME Terminal (TERM=xterm-
256color), Konsole (TERM=xterm-256color), Tilda (TERM=xterm-256color),
XTerm (TERM=xterm), and a virtual console (TERM=linux). See
https://chat.stackexchange.com/transcript/message/42130009#42130009 and
subsequent messages for details. It occurred for us both no matter what
terminals we used. I believe this is the same bug as reported here.

In case it is helpful, I have attached a file showing the debugging
output produced by running "perldoc -D perlsyn" on my Lubuntu 17.10
system. Note the presence of this line:

About to call Pod::Perldoc::ToTerm->pager_configuration("/usr/bin
/sensible-pager")

I suspect that the problem is that the necessary configuration for less
to permit terminal escape sequences--specifically, that the -R option
either be passed to it or present in the LESS environment variable--is
not satisfied when the pager configuration for sensible-pager is used,
even when sensible-pager runs less, as it does by default in Ubuntu.

I further suspect that many, or perhaps all, 17.10 systems have this bug
in their default configuration (though it would only be noticed if users
install and run perldoc). This strongly resembles
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735134. This bug may
be considered a regression, in that the problem had previously occurred
and was then prevented by the addition of this code in Perldoc.pm, which
is present in 16.04 but removed in 17.10 (see below for details):

# fix visible escape codes in ToTerm output
# https://bugs.debian.org/758689
local $ENV{LESS} = defined $ENV{LESS} ? "$ENV{LESS} -R" : "-R";

The simplest workaround for this bug that I am aware of is to pass the
-t flag to perldoc. As in the workaround described in the bug report
here, the resulting formatting is readable but not as fancy as usual.

A *full* workaround is also possible, and is only slightly more
complicated. Telling perldoc explicitly that you want "less" by defining
the PAGER environment variable works:

PAGER=less perldoc perlsyn

Otherwise, it finds sensible-pager first (see above), and appears not to
place -R in LESS (see below), because it does not know that the
sensible-pager shell script runs less.

The problem may also be avoided by ensuring that an environment variable
with the name LESS and a value that specifies the R option is present.
For example, this works:

LESS=-R perldoc perlsyn

Or this may be preferred, because if you have a LESS environment
variable with other options, they will still be used (and if not, it has
the same effect as above):

LESS="$LESS -R" perldoc perlsyn

Or you can pipe to less and pass -R:

perldoc perlsyn | less -R

If these workarounds do not work for you (i.e., for the original author
of this bug report), then I might be mistaken in my belief that the bug
I am experiencing is the same as yours.

This bug does not appear to affect Ubuntu 16.04 LTS. It does not happen
on my Lubuntu 16.04 LTS (64-bit) system. Ubuntu 16.04 LTS has
"/usr/share/perl/5.22/Pod/Perldoc.pm" which uses this loop to open the
document in a pager:

foreach my $pager (@pagers) {
$self->aside("About to try calling $pager $output\n");
if ($self->is_vms) {
last if system("$pager $output") == 0;
} else {
# fix visible escape codes in ToTerm output
# bugs.debian.org/758689
local $ENV{LESS} = defined $ENV{LESS} ? "$ENV{LESS} -R" : "-R";
last if system("$pager \"$output\"") == 0;
}
}

Ubuntu 17.10 has this corresponding loop, which no longer directly
attempts to modify the LESS environment variable in order to prevent
Debian Bug 758689 from occurring:

foreach my $pager (@pagers) {
$self->aside("About to try calling $pager $output\n");
if ($self->is_vms) {
last if system("$pager $output") == 0;
} elsif($self->is_amigaos) {
last if system($pager, $output) == 0;
} else {
my $formatter = $self->{'formatter_class'};
if ( $formatter->can('pager_configuration') ) {
$self->aside("About to call $formatter" . 
"->pager_configuration(\"$pager\")\n");

[Touch-packages] [Bug 1539995] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

2017-08-01 Thread Eliah Kagan 
This apparently has not gone away; I got it on Artful. There are some
details in duplicate bug 1707854.

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

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Partial Upgrade failed (crash)
  Ubuntu Mate 16 Alpha install testing on different machines.
  This machine Dell Optiplex 960

  linuxpusher@linuxpusher-OptiPlex-960:~$ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  
  linuxpusher@linuxpusher-OptiPlex-960:~$ sudo lshw
  [sudo] password for linuxpusher: 
  linuxpusher-optiplex-960  
  description: Computer
  width: 64 bits
  capabilities: smbios-2.5 vsyscall32
*-core
 description: Motherboard
 physical id: 0
   *-memory
description: System memory
physical id: 0
size: 7819MiB
   *-cpu
product: Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@0
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority
   *-pci
description: Host bridge
product: 4 Series Chipset DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 03
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel
resources: irq:0
  *-display:0
   description: VGA compatible controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:33 memory:fe80-febf 
memory:d000-dfff ioport:ecb0(size=8)
  *-display:1 UNCLAIMED
   description: Display controller
   product: 4 Series Chipset Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2.1
   bus info: pci@:00:02.1
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm bus_master cap_list
   configuration: latency=0
   resources: memory:fe70-fe7f
  *-communication:0
   description: Communication controller
   product: 4 Series Chipset HECI Controller
   vendor: Intel Corporation
   physical id: 3
   bus info: pci@:00:03.0
   version: 03
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list
   configuration: driver=mei_me latency=0
   resources: irq:34 memory:feda6000-feda600f
  *-ide
   description: IDE interface
   product: 4 Series Chipset PT IDER Controller
   vendor: Intel Corporation
   physical id: 3.2
   bus info: pci@:00:03.2
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: ide pm msi bus_master cap_list
   configuration: driver=ata_generic latency=0
   resources: irq:18 ioport:fe80(size=8) ioport:fe90(size=4) 
ioport:fea0(size=8) ioport:feb0(size=4) ioport:fef0(size=16)
  *-communication:1
   description: Serial controller
   product: 4 Series Chipset Serial KT Controller
   vendor: Intel Corporation
   physical id: 3.3
   bus info: pci@:00:03.3
   version: 03
   width: 32 bits
   clock: 66MHz
   capabilities: pm msi 16550 bus_master cap_list
   configuration: driver=serial latency=0
   resources: irq:17 ioport:ecb8(size=8) memory:fe6d8000-fe6d8fff
  *-network
   description: Ethernet interface
   product: 82567LM-3 Gigabit Network Connection
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical

[Touch-packages] [Bug 1707854] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

2017-08-01 Thread Eliah Kagan 
*** This bug is a duplicate of bug 1539995 ***
https://bugs.launchpad.net/bugs/1539995

This bug report is for the bug in apport or GTK+, *not* for the kernel
bug (if any) that triggered it. However, in case the kernel oops that
triggered the apport-gtk instance that crashed is relevant, here's the
output of dmesg.

** Attachment added: "output of dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1707854/+attachment/4925074/+files/dmesg.txt

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

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

Status in apport package in Ubuntu:
  New

Bug description:
  On an Xubuntu Artful amd64 system with linux-generic 4.11.0.12.12,
  libgtk-3-0 3.22.17-0ubuntu1, and apport-gtk 2.20.6-0ubuntu4, I viewed
  the details on a kernel crash report prepared by apport-gtk titled
  "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 24s!
  [kworker/0:0:2661]" but decided not to report that bug. This is a
  VMware Workstation 12.5.7 virtual machine that I believe incurs
  slowdowns from the host from time to time. After I successfully quit
  the Apport dialog box that would allow me to report the bug, an
  unexpected smaller window appeared with no contents and "Ubuntu"
  (without the quotes) as its title. I waited several minutes but no
  window contents appeared.

  This all actually occurred twice at a time -- apparently there were
  two kernel soft locks at different times, and Apport offered to report
  bugs relating to both events. I clicked through to view the details on
  both. I quit both dialog boxes and got two smaller windows with no
  contents; these windows never changed. I did not take a screenshot of
  the windows, but I did use xwininfo to obtain the window ID of one of
  them and then the xprop command to obtain information about it,
  following the technique described at
  https://unix.stackexchange.com/a/84981. The output of "xprop -id
  0x42011b1" is attached as xprop.txt.

  Then I closed the two windows by clicking the X. My window manager
  told me one of them was not responding and asked if I wanted to force
  it to close, which I did. After this, at least one of the two
  instances of apport-gtk apparently segfaulted; another apport window,
  which appeared to work correctly, eventually came up to help me report
  the crash as a bug, which I am doing now. I don't know for sure that
  the crash is actually from when I forced the window to close, or from
  before that; it could even have happened before the two mysterious
  windows were created. Furthermore, I don't know if the window I ran
  xprop to get information about came from the same instance of apport-
  gtk that crashed, or from the other instance.

  I don't know if this bug is in apport or some GTK+ package such as
  libgtk-3-0. It resembles bug 1539995, which is considered to be a GTK+
  bug rather than an apport bug and, as of this writing, appears (along
  with its duplicates) not known to affect any releases except Xenial
  and Yakkety. (Perhaps the forthcoming symbolic retrace will shed light
  on the similarity.)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: apport-gtk 2.20.6-0ubuntu4
  ProcVersionSignature: Ubuntu 4.11.0-12.18-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 02:34:38 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-07-31 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f789c06ea78 : 
mov(%r14),%rax
   PC (0x7f789c06ea78) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   gtk_widget_translate_coordinates () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_event_controller_handle_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1707854] [NEW] apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

2017-08-01 Thread Eliah Kagan 
*** This bug is a duplicate of bug 1539995 ***
https://bugs.launchpad.net/bugs/1539995

Public bug reported:

On an Xubuntu Artful amd64 system with linux-generic 4.11.0.12.12,
libgtk-3-0 3.22.17-0ubuntu1, and apport-gtk 2.20.6-0ubuntu4, I viewed
the details on a kernel crash report prepared by apport-gtk titled "NMI
watchdog: BUG: soft lockup - CPU#0 stuck for 24s! [kworker/0:0:2661]"
but decided not to report that bug. This is a VMware Workstation 12.5.7
virtual machine that I believe incurs slowdowns from the host from time
to time. After I successfully quit the Apport dialog box that would
allow me to report the bug, an unexpected smaller window appeared with
no contents and "Ubuntu" (without the quotes) as its title. I waited
several minutes but no window contents appeared.

This all actually occurred twice at a time -- apparently there were two
kernel soft locks at different times, and Apport offered to report bugs
relating to both events. I clicked through to view the details on both.
I quit both dialog boxes and got two smaller windows with no contents;
these windows never changed. I did not take a screenshot of the windows,
but I did use xwininfo to obtain the window ID of one of them and then
the xprop command to obtain information about it, following the
technique described at https://unix.stackexchange.com/a/84981. The
output of "xprop -id 0x42011b1" is attached as xprop.txt.

Then I closed the two windows by clicking the X. My window manager told
me one of them was not responding and asked if I wanted to force it to
close, which I did. After this, at least one of the two instances of
apport-gtk apparently segfaulted; another apport window, which appeared
to work correctly, eventually came up to help me report the crash as a
bug, which I am doing now. I don't know for sure that the crash is
actually from when I forced the window to close, or from before that; it
could even have happened before the two mysterious windows were created.
Furthermore, I don't know if the window I ran xprop to get information
about came from the same instance of apport-gtk that crashed, or from
the other instance.

I don't know if this bug is in apport or some GTK+ package such as
libgtk-3-0. It resembles bug 1539995, which is considered to be a GTK+
bug rather than an apport bug and, as of this writing, appears (along
with its duplicates) not known to affect any releases except Xenial and
Yakkety. (Perhaps the forthcoming symbolic retrace will shed light on
the similarity.)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: apport-gtk 2.20.6-0ubuntu4
ProcVersionSignature: Ubuntu 4.11.0-12.18-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Tue Aug  1 02:34:38 2017
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2017-07-31 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f789c06ea78 :   
mov(%r14),%rax
 PC (0x7f789c06ea78) ok
 source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 gtk_widget_translate_coordinates () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_event_controller_handle_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful

** Attachment added: "output of "xprop -id 0x42011b1"; 0x42011b1 was the ID of 
one of the mysterious windows"
   https://bugs.launchpad.net/bugs/1707854/+attachment/4925061/+files/xprop.txt

** Information type changed from Private to Public

** Description changed:

- On an Xubuntu Artful amd64 system with libgtk-3-0 3.22.17-0ubuntu1 and
- apport-gtk 2.20.6-0ubuntu4, I viewed the details on a kernel crash
- report prepared by apport-gtk titled "NMI watchdog: BUG: soft lockup -
- CPU#0 stuck for 24s! [kworker/0:0:2661]" but decided not to report that
- bug. This is a VMware Workstation 12.5.7 virtual machine that I believe
- incurs slowdowns from the host from time to time. After I successfully
- quit the Apport dialog box that would allow me to report the bug, an
- unexpected smaller window appeared with no contents and "Ubuntu"
- (without the quotes) as its title. I waited several minutes but no
- window

[Touch-packages] [Bug 1707829] [NEW] systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

2017-07-31 Thread Eliah Kagan 
*** This bug is a duplicate of bug 1605307 ***
https://bugs.launchpad.net/bugs/1605307

Public bug reported:

Apport told me systemd-resolved crashed when I logged in to my fully
updated Xubuntu Artful amd64 system. This is the same virtual machine
for which I reported bug 1707792 earlier today; potentially relevant
details about the system installed on this machine may be found in that
bug report.

I suspect this is still bug 1707792 (which is a duplicate of bug
1705870), but this also resembles bug 1605307, which was originally
reported against Yakkety but has since also been tagged Zesty and
Artful. Are these all really the same bug?

After the symbolic retrace and depending on what it shows, I will likely
mark this as a duplicate of something else, if that is not done
automatically.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Mon Jul 31 22:16:39 2017
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2017-07-31 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdline: /lib/systemd/systemd-resolved
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic 
root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait () from /lib/systemd/libsystemd-shared-234.so
 sd_event_run () from /lib/systemd/libsystemd-shared-234.so
 sd_event_loop () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
Title: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-crash artful package-from-proposed

** Information type changed from Private to Public

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

Title:
  systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  Apport told me systemd-resolved crashed when I logged in to my fully
  updated Xubuntu Artful amd64 system. This is the same virtual machine
  for which I reported bug 1707792 earlier today; potentially relevant
  details about the system installed on this machine may be found in
  that bug report.

  I suspect this is still bug 1707792 (which is a duplicate of bug
  1705870), but this also resembles bug 1605307, which was originally
  reported against Yakkety but has since also been tagged Zesty and
  Artful. Are these all really the same bug?

  After the symbolic retrace and depending on what it shows, I will
  likely mark this as a duplicate of something else, if that is not done
  automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Jul 31 22:16:39 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2017-07-31 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
  Lsusb:
   Bus 001 Device 001: ID

[Touch-packages] [Bug 1707792] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

2017-07-31 Thread Eliah Kagan 
*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870

** Description changed:

  I don't know if this should be considered a bug in systemd or apport.
  
  systemd-udevd appears to crash with this bug on each boot. This is a
  fully updated Xubuntu Artful amd64 system (installed yesterday from the
  daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport
- 2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has no
- swap and runs inside a VMware Workstation 12.5.7 virtual machine (with
- open-vm-tools) on a Windows host. The host system has not approached
- memory exhaustion. I suspect these details may be relevant, because the
- host system sometimes experiences unexplained slowdowns when I/O is
- high. Note that I only suspect, and do not actually know for sure, that
- this bug may have been triggered by the host system's I/O problems.
+ 2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system swaps
+ to a 948 MiB swap file (/swapfile) and runs inside a VMware Workstation
+ 12.5.7 virtual machine (with open-vm-tools) on a Windows host. The host
+ system has not approached memory exhaustion. I suspect these details may
+ be relevant, because the host system sometimes experiences unexplained
+ slowdowns when I/O is high. Note that I only suspect, and do not
+ actually know for sure, that this bug may have been triggered by the
+ host system's I/O problems.
  
  I only know about this crash because Apport notified me. Starting the
  system seems to take longer than it should; specifically, once the non-
  graphical login prompt is shown, it sometimes takes up to a minute for
  LightDM to appear. But I don't know if that is related, and beyond that,
  I have not observed anything going wrong on the system. When I
  originally installed this Ubuntu (guest) system, Apport did not inform
  me of a crash. Since then, the host system engaged in more intensive
  I/O, and also I enabled artful-proposed, and now the crash occurs. I
  don't know if either of these changes are relevant.
  
  This most resembles bug 1705870, which occurred in Artful with some
  slightly earlier package versions. Depending on the results of the
  symbolic retrace, I might mark this as a duplicate of that bug. It also
  resembles bug 1663995, bug 1506798, bug 1433320, and some of its (many)
  duplicates. That bug (i.e., bug 1433320) was considered to affect apport
  rather than systemd (see
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10)
  and is considered fixed. (To a lesser extent, this bug resembles bug
  1437896, which that bug mentions, and which is considered a bug in
  systemd.)
  
  I have made /bin/sh a symlink to bash on this system instead of dash
  (because I am using this system to test
  http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html,
  which expects it). Aside from making startup scripts run a bit slower
  and increasing memory footprint slightly, I suspect this is irrelevant
  to this bug, but it's a significant (and *unusual*) change so I figured
  it is worth mentioning.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Jul 31 17:41:49 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-07-31 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic 
root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x1f82c781c0, argc=1, argv=0x7ffddfff7de8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffddfff7dd8) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias:

[Touch-packages] [Bug 1705870] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

2017-07-31 Thread Eliah Kagan 
I've experienced this bug, also in a virtual machine (though with VMware
rather than QEMU). See bug 1707792 for details.

These bugs have a lot in common with bug 1433320, though that is
considered fixed.

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Sat Jul 22 00:19:41 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-03-25 (849 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x558cc4bc3f20, argc=1, argv=0x7ffe6962b198, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe6962b188) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-yakkety
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-yakkety
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1707792] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

2017-07-31 Thread Eliah Kagan 
*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870

** Attachment removed: "the output of dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707792/+attachment/4924803/+files/dmesg.txt

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know if this should be considered a bug in systemd or apport.

  systemd-udevd appears to crash with this bug on each boot. This is a
  fully updated Xubuntu Artful amd64 system (installed yesterday from
  the daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport
  2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has
  no swap and runs inside a VMware Workstation 12.5.7 virtual machine
  (with open-vm-tools) on a Windows host. The host system has not
  approached memory exhaustion. I suspect these details may be relevant,
  because the host system sometimes experiences unexplained slowdowns
  when I/O is high. Note that I only suspect, and do not actually know
  for sure, that this bug may have been triggered by the host system's
  I/O problems.

  I only know about this crash because Apport notified me. Starting the
  system seems to take longer than it should; specifically, once the
  non-graphical login prompt is shown, it sometimes takes up to a minute
  for LightDM to appear. But I don't know if that is related, and beyond
  that, I have not observed anything going wrong on the system. When I
  originally installed this Ubuntu (guest) system, Apport did not inform
  me of a crash. Since then, the host system engaged in more intensive
  I/O, and also I enabled artful-proposed, and now the crash occurs. I
  don't know if either of these changes are relevant.

  This most resembles bug 1705870, which occurred in Artful with some
  slightly earlier package versions. Depending on the results of the
  symbolic retrace, I might mark this as a duplicate of that bug. It
  also resembles bug 1663995, bug 1506798, bug 1433320, and some of its
  (many) duplicates. That bug (i.e., bug 1433320) was considered to
  affect apport rather than systemd (see
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10)
  and is considered fixed. (To a lesser extent, this bug resembles bug
  1437896, which that bug mentions, and which is considered a bug in
  systemd.)

  I have made /bin/sh a symlink to bash on this system instead of dash
  (because I am using this system to test
  http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html,
  which expects it). Aside from making startup scripts run a bit slower
  and increasing memory footprint slightly, I suspect this is irrelevant
  to this bug, but it's a significant (and *unusual*) change so I
  figured it is worth mentioning.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Jul 31 17:41:49 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-07-31 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic 
root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x1f82c781c0, argc=1, argv=0x7ffddfff7de8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffddfff7dd8) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias:

[Touch-packages] [Bug 1707792] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

2017-07-31 Thread Eliah Kagan 
*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870

Public bug reported:

I don't know if this should be considered a bug in systemd or apport.

systemd-udevd appears to crash with this bug on each boot. This is a
fully updated Xubuntu Artful amd64 system (installed yesterday from the
daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport
2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has no
swap and runs inside a VMware Workstation 12.5.7 virtual machine (with
open-vm-tools) on a Windows host. The host system has not approached
memory exhaustion. I suspect these details may be relevant, because the
host system sometimes experiences unexplained slowdowns when I/O is
high. Note that I only suspect, and do not actually know for sure, that
this bug may have been triggered by the host system's I/O problems.

I only know about this crash because Apport notified me. Starting the
system seems to take longer than it should; specifically, once the non-
graphical login prompt is shown, it sometimes takes up to a minute for
LightDM to appear. But I don't know if that is related, and beyond that,
I have not observed anything going wrong on the system. When I
originally installed this Ubuntu (guest) system, Apport did not inform
me of a crash. Since then, the host system engaged in more intensive
I/O, and also I enabled artful-proposed, and now the crash occurs. I
don't know if either of these changes are relevant.

This most resembles bug 1705870, which occurred in Artful with some
slightly earlier package versions. Depending on the results of the
symbolic retrace, I might mark this as a duplicate of that bug. It also
resembles bug 1663995, bug 1506798, bug 1433320, and some of its (many)
duplicates. That bug (i.e., bug 1433320) was considered to affect apport
rather than systemd (see
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10)
and is considered fixed. (To a lesser extent, this bug resembles bug
1437896, which that bug mentions, and which is considered a bug in
systemd.)

I have made /bin/sh a symlink to bash on this system instead of dash
(because I am using this system to test
http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html,
which expects it). Aside from making startup scripts run a bit slower
and increasing memory footprint slightly, I suspect this is irrelevant
to this bug, but it's a significant (and *unusual*) change so I figured
it is worth mentioning.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: udev 234-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Mon Jul 31 17:41:49 2017
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2017-07-31 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic 
root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x1f82c781c0, argc=1, argv=0x7ffddfff7de8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffddfff7dd8) at ../csu/libc-start.c:291
Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-crash artful package-from-proposed

** Attachment added: "the output of dmesg"
   https://bugs.launchpad.net/bugs/1707792/+attachment/4924803/+files/dmesg.txt

** Information type changed from Private to Public

** Description changed:

  I don't know if this should be considered a bug in systemd or apport.
  
  systemd-udevd