[Bug 1754877] Re: either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying

Péter Prőhle 1754877 at bugs.launchpad.net
Sat Mar 10 21:59:08 UTC 2018


*** This bug is a duplicate of bug 1552577 ***
    https://bugs.launchpad.net/bugs/1552577

Half of this bug is the duplicate of https://bugs.launchpad.net/bugs/1754885
and NOT of https://bugs.launchpad.net/bugs/1552577 SINCE in 1552577 and 1754885 the situations what caus the problems are different, only the resulting signal is the same.

The other half of this bug is the duplicate of
https://bugs.launchpad.net/bugs/1754887

During the creation of this error report it was not clear, which report
of the three parallel reports remained alive.  But later experiments
made me clear the situation, and therefore later I allowed the apport-
gtk produce the SEPARATE much more precise reports 1754885 and 1754887.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1754877

Title:
  either apport-gtk crashed with SIGSEGV or x-server crashed because of
  xzgv magnifying

Status in apport package in Ubuntu:
  New

Bug description:
  It happens time to time, when I try to magnify a scanned text-picture
  in XZGV, suddenly the whole graphical session terminates, I see the
  monitor in framebuffer character mode, and then I can log in for an
  other graphical session.  Usually I reboot just after this login, and
  after this reboot I get the crash report possibility, ... this time
  three in parallel, but only the "apport-gtk crashed with SIGSEGV" out
  of these was successful to submit a crash report.

  This is the reason why the summary is a bit unsure: "either apport-gtk
  crashed with SIGSEGV or x-server crashed because of xzgv magnifying".
  I am not sure whether there is any problem with apport-gtk, because it
  might happen, that only the reboot disturbed it (I make the reboots
  before any crash report opportunity window shows up).

  I think the real problem is, that magnifying a larger picture in XZGV
  can kill the graphical session, regadless what other jobs wanted to
  remain alive in it.

  (this is 18.04 development branch, and xzgv 0.9.1-4, everything
  (evrypackage) are fresh up to date)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.8-0ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Mar 10 19:30:33 2018
  ExecutablePath: /usr/share/apport/apport-gtk
  ExecutableTimestamp: 1518540671
  InstallationDate: Installed on 2017-07-13 (240 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.6
  JournalErrors:
   -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 19:35:01 CET. --
   Mar 10 19:32:21 pc56 spice-vdagent[1670]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
   Mar 10 19:32:21 pc56 pulseaudio[1703]: [pulseaudio] pid.c: Daemon already running.
   Mar 10 19:32:46 pc56 pulseaudio[1499]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcCwd: /home/prohlep
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  SegvAnalysis:
   Segfault happened at: 0x7f43f443e5a9:	mov    (%rbx),%rdi
   PC (0x7f43f443e5a9) ok
   source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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



More information about the foundations-bugs mailing list