Crash is still happening even with the latest changes to the shutdown
sequence in oxide trunk.

I’ve observed that closing a window by sending it a _NET_CLOSE_WINDOW
message (using e.g. wmctrl -c) doesn’t trigger the crash, so it’s really
only the Alt+F4 keyboard shortcut that causes the issue.

** This bug is no longer a duplicate of bug 1448079
   Don't run the event loop after QGuiApplication begins to tear down

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

  Alt+F4 crashes app

Status in webbrowser-app package in Ubuntu:

Bug description:
  was just watching something on Youtube Web App created by unity
  itself. when i pressed alt-f4 Ubuntu said it had an error and if i
  want to submit it.

  that is all folks.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webapp-container 0.23+15.04.20150320.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 19:56:16 2015
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2015-03-22 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  ProcCmdline: webapp-container --app-id=YouTubeyoutubecom 
--webapp=WW91VHViZQ== --enable-back-forward
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x00000000) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: webbrowser-app
   ?? ()
   ?? () from 
   QMetaObject::activate(QObject*, int, int, void**) () from 
   ?? () from 
   ?? () from 
  Title: webapp-container crashed with SIGSEGV in QMetaObject::activate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to