*** This bug is a duplicate of bug 1552577 ***

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1552577, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may

** Attachment removed: "CoreDump.gz"

** Attachment removed: "Disassembly.txt"

** Attachment removed: "ProcMaps.txt"

** Attachment removed: "ProcStatus.txt"

** Attachment removed: "Registers.txt"

** Attachment removed: "Stacktrace.txt"

** Attachment removed: "ThreadStacktrace.txt"

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV in 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.

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

Status in apport package in Ubuntu:

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
   -- 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 
   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
   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
   () 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:

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

Reply via email to