** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Released
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This bug was fixed in the package apparmor - 2.11.0-2ubuntu3
---
apparmor (2.11.0-2ubuntu3) zesty; urgency=medium
* SECURITY UPDATE: Don't unload unknown profiles during package
configuration or when restarting the apparmor init script, upstart job, or
systemd unit as this c
Thanks Tyler!
On Thu, Mar 16, 2017 at 4:16 AM, Tyler Hicks
wrote:
> ** Changed in: apparmor
> Milestone: None => 2.12
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1590561
>
> Title:
> webbrowser-app crashes on startup on fres
** Changed in: apparmor
Milestone: None => 2.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
EGL configs fo
Merged into the upstream tree as r3645:
http://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3645
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Importance: Undecided => High
** Changed in: apparmor
Status: New => Fix Com
** Branch linked: lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
This bug was fixed in the package webbrowser-app -
0.23+17.04.20170310-0ubuntu1
---
webbrowser-app (0.23+17.04.20170310-0ubuntu1) zesty; urgency=medium
[ Alexandre Abreu ]
* Explicitely define Ctrl+R as the refresh shortcut for the browser
(LP: #1593877)
[ Andrew Hayzen ]
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Un
@Olivier, yes I rechecked and found /dev/dri already added there, which I
missed somehow.
So I confirm two apparmor access to be added.
/dev/dri/ r,
/sys/devices/pci[0-9]*/**/config r,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitabl
** Branch linked: lp:~ci-train-bot/webbrowser-app/webbrowser-app-ubuntu-
zesty-2504
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unit
** Branch linked: lp:~osomon/webbrowser-app/apparmor-additional-holes-
unity8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No
** Changed in: webbrowser-app (Ubuntu)
Assignee: Santosh (santoshbit2007) => Olivier Tilloy (osomon)
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: Santosh (santoshbit2007) => Olivier Tilloy (osomon)
** Changed
I just upgraded my laptop to zesty and tested webbrowser-app in the unity8
session.
Santosh’s comment (#47) is incorrect. The first denial that I’m getting is
/dev/dri/, and I’ve had to add it to the webbrowser-app profile to proceed to
get further denials for PCI devices config:
type=AVC msg=a
Considering the current implemention constraints that applications have
to access various device files for GL (eg, /dev/dri/card0) instead of
having something trusted like mir do the direct access (see bug #1197133
for background), I don't think we can avoid this access:
/sys/devices/pci[0-9]*/*
** Branch linked: lp:~osomon/apparmor/newer-nvidia-abstraction-trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
** Branch linked: lp:~osomon/apparmor/newer-nvidia-abstraction
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
EGL
** Branch linked: lp:~osomon/webbrowser-app/apparmor-profile-ibus-nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suit
** Changed in: canonical-devices-system-image
Milestone: None => u8c-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No su
@Daniel
/dev/dri/* is not the cause of any issue here, and I guess access is already
provided.
AFAIR adding /dev/dri/* doesn't fix the issue on unity8.
The question is whether "/sys/devices/pci[0-9]*/**/config r," is being
provided by unity8 to all apps or not, if not then adding that in each
/dev/dri/* is a special case that the shell (or lightdm, whichever runs
as root) needs to handle. Same goes for other desktop devices like
audio, webcams etc.
This makes me think it has already been done by virtue of logging in by
lightdm. So yeah, this would just be an over-confinement problem to
@osomon
actually - i am witnessing this & using this bug specifically for webbrowser as
a deb based install on the rootfs failing on zesty unity8 on top of an Intel
built in gpu.
I'll be happy to collect any logs.
Fwiw, i see the same AA denials (even tho it's not a snap)
Unsure if that effects
There are several separate issues here, and it doesn’t help that they
are being tracked in the same place.
IIUC, the issue with the webbrowser-app snap on unity8 needs to be
addressed in unity8 by relaxing the confinement that will allow apps to
create a QOpenGLContext ("/dev/dri/*"?). It’s unclea
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbr
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No
The issue is happening with egl context creation and I could see the bug(error
logs) with
QOpenGLContext ctx;
ctx.create().
So I am also unsure if [1] practically works. Is there any way to
validates that.
[1]
In theory Unity8 should be automatically assigning these rights to all GUI apps
aut
"/sys/devices/pci[0-9]*/**/config r,"
Doesn't that give the browser access to all PCI devices? :)
It's just a graphics device issue so the right device should be:
/dev/dri/*
In theory Unity8 should be automatically assigning these rights to all
GUI apps automatically. Not sure if it does. Certain
summarising the apparmor fixes for issue.
Issue 1: WebBrowser-app crash on zesty/unity8/[intel, readon]
Fix: Adding apparmor access to
"/sys/devices/pci[0-9]*/**/config r,"
Issue 2: WebBrowser-app crash on xenail/unity7/nvidia
Fix: Adding apparmor access to
For the ib
@Jamie
It works.
The application raises a warning:
** (webbrowser-app:4229): WARNING **: Unable to register app:
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application
ID
The syslog has the following denials:
/usr/share/nvidia-367/nvidia-application-profiles-367.57-rc
/org/g
For the ibus denial you need:
#include
For nvidia, you need:
#include
@{PROC}/driver/nvidia/params r,
/dev/nvidia* rw,
unix (send, receive) type=dgram peer=(addr="@nvidia[0-9a-f]*"),
(the apparmor abstraction needs to be updated for newer nvidia).
What happens if you add the above to
webbrowser-app and all other Qt apps trying to get an EGL handle, via Mir
then.
This means : should the policy be updated to have all Qt apps get this
access level ? or should that stay as a per-app decision ?
On Tue, Feb 21, 2017 at 8:44 PM, Seth Arnold <1590...@bugs.launchpad.net>
wrote:
> If
If webbrowser-app needs access to nvidia hardware (does it?) using the
file is probably easier than figuring out each
access one at a time.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/159056
@Santosh
Still crashing.
The apparmor denial for /dev/nvidiactl is gone but now running
webbrowser-app raises either ibus warning or broker_posix error.
(webbrowser-app:9751): IBUS-WARNING **: Unable to connect to ibus: Could
not connect: Permission denied
or
[0100/00.144346:ERROR:broker_
@ ilija
Thanks for syslog,
I checked log, there is apparmor denail for /dev/nvidiactl
Feb 20 16:28:07 Silver kernel: [ 117.797833] audit: type=1400
audit(1487604487.352:57): apparmor="DENIED" operation="open"
profile="webbrowser-app" name="/dev/nvidiactl" pid=3124 comm="webbrowser-app"
reques
@Santosh
After boot
1. $ webbrowser-app-> crash
2. $ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.webbrowser-app
3. $ webbrowser-app-> works
Attached: /var/log/syslog
** Attachment added: "/var/log/syslog"
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1590561/+at
@ Ilija
Then this also seems to issue with apparmor access, So could you give me
full /var/log/syslog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup
If /etc/apparmor.d/usr.bin.webbrowser-app is related to the
problem/solution then the correct package is 'webbrowser-app'. Re-
confirmed.
** Changed in: webbrowser-app (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
@Santosh
Now it works!
Output:
unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
UCUriHandler: Empty "APP_ID" environment variable, i
@Ilija
Could your try running after disabling apparmor profile for webbrpwser-app
sudo apparmor_parser -R /etc/apparmor.d/usr.bin.webbrowser-app
and let me know the result
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Sure, driver is nvidia-367.57-0ubuntu0.16.04.1
I never had any graphics problems with any other browser, game or video
player. What's so special about webbrower-app?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
@ Ilija
I tried on unity7/16.04/nvidia with nouveau driver and didn't see any crash as
such.
But webbrowser-app crash on 17.04/unity7 which is related to
https://bugs.launchpad.net/bugs/1649262, Here nvidia drivers is not getting
loaded by mesa.
Well, unity8/17.04 is apparmor issue but this(1
Following comment #20 nothing really changed for me on Xenial, the only
difference is with the second part the window takes again a longer time
to be destroyed.
$ webbrowser-app
--desktop_file_hint=/usr/share/applications/webbrowser-app.desktop
Output:
(webbrowser-app:20815): dconf-CRITICAL **:
@jdstrand : apparently this issue would need the policy to be relaxed to
allow for EGL context creation (see comment #20).
Now, I am not sure if that requires more checks as to whether this is a
legit access request, or if drivers and or the stack need changes to
make this a safe operation. WDYT?
Just to add that the dconf errors are harmless, as confirmed by oSoMon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suita
Thanks. Those errors agree with with most of us are seeing; permission
denied (in various places).
Assuming the process hasn't changed userid, then it's a
confinement/apparmor bug. More people need to verify comment #20
maybe...
--
You received this bug notification because you are a member of U
@Gerry Boland (gerboland)
@Daniel van Vugt (vanvugt)
I just want to clarify the confusion you have with nVidia drivers.
When I reported the bug I encountered it on Xenial (without Mir) and the title
changes covering Zesty (Unity8/Mir) where made by Daniel along the way (comment
#3). Thus my grap
Crash is triggred When webbrowwser-app tries to create OpenGLContext. and it
happens with creation of qml window. this context is shared with oxide so oxide
shows error while using context.
I could get same egl error log[1] by triggering this call:
QOpenGLContext ctx;
ctx.create()
So In theory
Interesting, and thanks for proposing a fix.
I guess some further information will still be needed to understand whether
to open the apparmor profile to access those, or if that is wrong from a
confinement perspective.
Can you find which Qt function and/or Oxide calls are made that trigger the
ac
Environment: zesty/unity8/radeongpu
I can see the EGL crash in my radeon gpu from command line
$ webbrowser-app
--desktop_file_hint=/usr/share/applications/webbrowser-app.desktop
The Crash doesn't happen if I unload the webbrowser apparmor profile.
Looking further on apparmor denial I see few
@santosh: can you detail the apparmor denial, if any, that you experience
when the app hangs?
Also, when that happens, what are the function calls made by Oxide that
trigger that ?
Knowing which calls are made would probably help people on this thread to
know where this breaks. (or hangs).
On Wed
Just to clarify actually I didn't see any crash in my
test(unity8/zesty/radeon gpu), App gets launched but keeps spinning,
same result as Pat mentioned above.
After disabling apparmor service webbrowser-app works fine.
--
You received this bug notification because you are a member of Ubuntu
Bug
I don’t have a machine running zesty atm but according to comment #13
from Santosh, disabling apparmor confinement for webbrowser-app allows
the app to launch. Which would confirm that the problem is caused by an
apparmor denial that prevents Qt (and oxide) to find a suitable EGL
config.
>From Kev
Gerry,
We have somewhat commandeered this bug. It's being experienced on Intel
graphics by most people, despite the description mentioning nvidia up
top. There is a separate bug (which I can't find right now) for nvidia
driver failures, but given Mir doesn't actually support the Nvidia
driver yet
re: Gerry's questions
At least for me
1) this an intel gpu, also i see AA denials in syslog upon attempting to launch
this. I just ran it and confirmed that again (and previous syslog excerpt
attached by me above)
2) see attached file
3) this bug has been around a long time, but it's sounding li
I've a bunch of questions. Any time you see EGL complaints, it is often
down to the graphics driver.
1. is this complaint for an NVidia-based system only? The log indicates
it has the proprietary nvidia driver installed, which Mir does not
support (and so Unity8 does not run). How are you testing?
unity8/zesty:
In case browser startup screen and spins. it works and load page after
disabling apparmor service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes o
** Changed in: oxide
Assignee: (unassigned) => Santosh (santoshbit2007)
** Changed in: webbrowser-app (Ubuntu)
Assignee: (unassigned) => Santosh (santoshbit2007)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
On unity7
Browser (from deb) it crashes.
I installed the webbrowser-app snap and it runs perfectly along with the
platform snap.
Unity8
from the scope or drawer the browser just creates a black xmir window. From the
command line it complains it cannot connect to mir.
>From teh scope or drawers
Oxide failing to create a GL context isn't your only issue here, as Qt
also fails to create one (which happens completely independently of
Oxide)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Is there something in syslog ? like apparmor not authorizing access to
certain interfaces?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zes
** Summary changed:
- webbrowser-app crashes on startup on fresh zesty Unity8
+ webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL
configs found
** Package changed: oxide-qt (Ubuntu) => oxide
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Invalid
--
Y
62 matches
Mail list logo
