desktop-packages team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

There is an issue here with apport and how it launches apport if the pid
does not equal the global pid.

# Check if we received a valid global PID (kernel >= 3.12). If we do,
# then compare it with the local PID. If they don't match, it's an
# indication that the crash originated from another PID namespace. In that
# case, attempt to forward the crash to apport in that namespace. If
# apport can't be found, then simply log an entry in the host error log
# and exit 0.
if len(sys.argv) == 5 and sys.argv[4].isdigit() and sys.argv[4] != sys.argv[1]:
    if os.path.exists('/proc/%s/root/%s' % (sys.argv[4], __file__)):
        error_log('pid %s (host pid %s) crashed in a container with apport '
                  'support, forwarding' % (sys.argv[1], sys.argv[4]))
        sys.stderr.flush()
        os.execv('/usr/sbin/chroot', ('chroot', '/proc/%s/root/' % sys.argv[4],
                                      __file__, sys.argv[1], sys.argv[2],
                                      sys.argv[3]))

In the last line if we change the arguments to os.execv from sys.argv[1]
to sys.argv[4] one will receive a crash report about chromium-browser
and not init.

** Description changed:

+ Test Case
+ ---------
+ 1) Set your default browser to Chromium.
+ 2) Launch synaptic
+ 3) Click on the home page url for a package.
+ 4) Observe chromium-browser not launch
+ 5) Receive apport crash dialog
+ 5) Also notice the apport crash dialog refers to upstart / systemd
+ 
  none
  
- ProblemType: Crash
- DistroRelease: Ubuntu 14.04
+ ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: => 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
+  TERM=linux
+  PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
-  Segfault happened at: 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
-  PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)!
-  Stack pointer not within stack segment
+  Segfault happened at: 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
+  PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)!
+  Stack pointer not within stack segment
  SegvReason: executing unknown VMA
- Signal: 11
- SourcePackage: upstart
+ Signal: 11SourcePackage: upstart
  StacktraceTop:
-  ?? ()
-  ?? ()
-  ?? ()
+  ?? ()
+  ?? ()
+  ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:
-  
+ 
  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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

** Changed in: apport (Ubuntu)
       Status: New => Triaged

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1300235

Title:
  init (chromium-browser) crashed with SIGSEGV

Status in apport package in Ubuntu:
  Triaged
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Test Case
  ---------
  1) Set your default browser to Chromium.
  2) Launch synaptic
  3) Click on the home page url for a package.
  4) Observe chromium-browser not launch
  5) Receive apport crash dialog
  5) Also notice the apport crash dialog refers to upstart / systemd

  none

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: => 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:	Cannot access memory at address 0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:

  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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