07.08.2023 23:01, Marc Espie пишет:
> To be fair, most alternates dependencies do conflict, and the bits involved
> work just fine with pkg_add -r.
>
> The *idea* of differing runtime dependencies is actually fairly rare.
It surely is, so quite low priority, albeit still nice-to-have, imho.
; > After one of the recent www/iridum updates, the extension/native host
> > > > now
> > > > works there just like it does with www/chromium.
> > > >
> > > > Is this the right way to depend on either chromium or iridium?
> > >
> > works there just like it does with www/chromium.
> > >
> > > Is this the right way to depend on either chromium or iridium?
> > > The way I understand this: use either iridium-* or chromium-* if
> > > installed,
> > > otherwise install www
t; Is this the right way to depend on either chromium or iridium?
> > The way I understand this: use either iridium-* or chromium-* if installed,
> > otherwise install www/chromium to satisfy the runtime dependency.
>
> Not in practise, as I can't uninstall chromium whe
On Tue, Jul 25, 2023 at 04:42:10PM +, Klemens Nanni wrote:
> After one of the recent www/iridum updates, the extension/native host now
> works there just like it does with www/chromium.
>
> Is this the right way to depend on either chromium or iridium?
> The way I understand th
After one of the recent www/iridum updates, the extension/native host now
works there just like it does with www/chromium.
Is this the right way to depend on either chromium or iridium?
The way I understand this: use either iridium-* or chromium-* if installed,
otherwise install www/chromium to
ncy.
> > >
> > > --
> > > Sent from a phone, apologies for poor formatting.
> > >
> > > On 24 December 2022 20:46:51 "Luke A. Call" wrote:
> > >
> > > > Maybe I should have summarized by saying that inst
hould have summarized by saying that installing totem, of all
things, fixed the error message and the crashes from iridium, chromium, and
LibreOffice. Hopefully that provides some info about the dependencies.
The below (and its attachments included originally) hopefully provide
details as far as nee
sages*) and try running
> > libreoffice after each one, you should be able to figure out the missing
> > dependency.
> >
> > --
> > Sent from a phone, apologies for poor formatting.
> >
> > On 24 December 2022 20:46:51 "Luke A. Call" wrote:
>
t;Luke A. Call" wrote:
>
> > Maybe I should have summarized by saying that installing totem, of all
> > things, fixed the error message and the crashes from iridium, chromium, and
> > LibreOffice. Hopefully that provides some info about the dependencies.
> &
On 24 December 2022 20:46:51 "Luke A. Call" wrote:
Maybe I should have summarized by saying that installing totem, of all
things, fixed the error message and the crashes from iridium, chromium, and
LibreOffice. Hopefully that provides some info about the dependencies.
The below (and
Maybe I should have summarized by saying that installing totem, of all
things, fixed the error message and the crashes from iridium, chromium, and
LibreOffice. Hopefully that provides some info about the dependencies.
The below (and its attachments included originally) hopefully provide
details
There was a significant update to www/Iridium that occurred just after
the ports freeze. www/ungoogled-chromium was also added. Is there any
consideration for providing Iridium as an update? www/googled-chromium
is a newly added package but blurs the criteria for updates as it
patches www
rig
> +++ content/gpu/gpu_sandbox_hook_linux.cc
> -@@ -99,8 +99,9 @@ static const char kLibV4lEncPluginPath[] =
> - "/usr/lib/libv4l/plugins/libv4l-encplugin.so";
> - #endif
> +@@ -101,6 +101,7 @@ static const char kLibV4lEncPluginPath[] =
>
open_flag = RTLD_NOW | RTLD_GLOBAL | RTLD_NODELETE;
-+constexpr int dlopen_flag = RTLD_NOW | RTLD_GLOBAL;
+ constexpr int dlopen_flag = RTLD_NOW | RTLD_GLOBAL | RTLD_NODELETE;
+#if !defined(OS_BSD)
void AddV4L2GpuPermissions(
Index:
On 2020/12/21 11:33, Stuart Cassoff wrote:
> I may have missed a post about this but iridium hasn't been working on
> i386 for a while now. Something seems off.
>
>
> $ iridium
> /usr/local/bin/iridium[57]: /usr/local/iridium/iridium: Cannot allocate
> memory
>
I may have missed a post about this but iridium hasn't been working on
i386 for a while now. Something seems off.
$ iridium
/usr/local/bin/iridium[57]: /usr/local/iridium/iridium: Cannot allocate
memory
$ ldd /usr/local/iridium/ir
use
> > >of that error message.
> > >A good setup for this is run chrome --disable-unveil and set up the
> > >download directory, then run it normally with unveil and be able to
> > >use it.
> > >
> > >Also a big confusion with iridium is
thrown into ~ and I can't move from there because
> >of that error message.
> >A good setup for this is run chrome --disable-unveil and set up the
> >download directory, then run it normally with unveil and be able to
> >use it.
> >
> >Also a big confusion with
sage.
>A good setup for this is run chrome --disable-unveil and set up the
>download directory, then run it normally with unveil and be able to
>use it.
>
>Also a big confusion with iridium is when the downloaded files are not
>accessible / are deleted / are not shown because of s
+1,27 @@
> > +$OpenBSD: README-main,v 1.2 2018/09/04 12:46:25 espie Exp $
> > +
> > ++---
> > +| Running ${PKGSTEM} on OpenBSD
> > ++-------
> > +
> > +Unveil
> > +=====
> > +Iridium has been pa
his is run chrome --disable-unveil and set up the
download directory, then run it normally with unveil and be able to
use it.
Also a big confusion with iridium is when the downloaded files are not
accessible / are deleted / are not shown because of some potential
danger to your computer. Seriously
> +| Running ${PKGSTEM} on OpenBSD
> ++-------
> +
> +Unveil
> +=
> +Iridium has been patched to use pledge and unveil, so it can only
> +display paths allowed in /etc/iridium/unveil.main, this includes
> +the following paths:
> +
> + ~/Docum
On Tue, Feb 12, 2019 at 10:23:53AM +0100, Karel Gardas wrote:
>
> Just iridium user here.
>
> On Tue, 12 Feb 2019 07:02:31 +0100
> Solene Rapenne wrote:
>
> > So, iridium can only display paths allowed in /etc/iridium/, this
>
> This "allowed in /etc/irid
Just iridium user here.
On Tue, 12 Feb 2019 07:02:31 +0100
Solene Rapenne wrote:
> So, iridium can only display paths allowed in /etc/iridium/, this
This "allowed in /etc/iridium/" is quite confusing. Shouldn't this be "allowed
in /etc/iridium/unveil.main" un
Hi
I'm proposing a pkg/README file for iridium and chromium about unveil.
The following is the iridium README, chromium being the same with
s/iridium/chromium
$OpenBSD: README,v 1.2 2018/09/04 12:46:25 espi
It would not read $HOME/Downloads/
I replaced the newly generated ~/.config/iridium directory with one
generated pre Nov/2018 and could then read and save to $HOME/Downlaods.
A thought that others could test by renaming ~/.config/iridium and
generating a new configuration.
On Jan 08, 2019
I updated and still had the message that iridium could not read the
/home/user. This was on a newer install and I went ahead and deleted my
~/.config/iridium and replaced it with the iridium directory from my
stable box. That worked
I have a second -current/amd64 box which also had the same
On January 8, 2019 3:13:08 PM UTC, "Heppler, J. Scott"
wrote:
>I suspect browsers are not the primary means of downloading for
>seasoned
>OpenBSD users and this new bug may go under the radar. Anyone else
>seeing this on iridium? On chromium?
Have you tried download
On Tue, 8 Jan 2019 07:13:08 -0800
"Heppler, J. Scott" wrote:
> I suspect browsers are not the primary means of downloading for seasoned
> OpenBSD users and this new bug may go under the radar. Anyone else
> seeing this on iridium? On chromium?
Tested on yesterday OpenBSD sn
I suspect browsers are not the primary means of downloading for seasoned
OpenBSD users and this new bug may go under the radar. Anyone else
seeing this on iridium? On chromium?
--
J. Scott Heppler
Solene Rapenne, 04 Dec 2018 18:47:
> SpikeHeron on freenode told me about the iridium FAQ:
> https://iridiumbrowser.de/faq
>
> [..] This is also the reason why the extensions panel at chrome://extensions
> does not fully work — dis/enabling (check box) and removing (trash can)
Solene Rapenne wrote:
> Robert Nagy wrote:
> > On 04/12/18 15:38 +, Stuart Henderson wrote:
> > > On 2018/12/04 16:36, Solene Rapenne wrote:
> > > > I can't delete or disable extensions in iridium on latest amd64
> > > > sna
Robert Nagy wrote:
> On 04/12/18 15:38 +, Stuart Henderson wrote:
> > On 2018/12/04 16:36, Solene Rapenne wrote:
> > > I can't delete or disable extensions in iridium on latest amd64 snapshot.
> > > I
> > > don't know if it worked before.
>
On 04/12/18 15:38 +, Stuart Henderson wrote:
> On 2018/12/04 16:36, Solene Rapenne wrote:
> > I can't delete or disable extensions in iridium on latest amd64 snapshot. I
> > don't know if it worked before.
> >
> > In console output, when I dis
On 2018/12/04 16:36, Solene Rapenne wrote:
> I can't delete or disable extensions in iridium on latest amd64 snapshot. I
> don't know if it worked before.
>
> In console output, when I disable an extension, I get this message:
>
> [23086:-552224352:1204/163207.445631:
I can't delete or disable extensions in iridium on latest amd64 snapshot. I
don't know if it worked before.
In console output, when I disable an extension, I get this message:
[23086:-552224352:1204/163207.445631:ERROR:CONSOLE(0)] "Unchecked
runtime.lastError while running manage
landry@ provides a buildbot for mozill-firefox but core development is
focused on privilege separation: pledge(2), unveil(2), Chromium/Iridium
are able to utilize privilege separation while mozilla-firefox does not.
This raises questions about a buildbot for Chromium and/or Iridium.
Would it
following results:
- Chromium: "Aw, Snap!"
- Firefox: Infinite "Loading ProtonMail..."
- Iridium: "Aw, Snap!"
Any idea how to fix this?
At least for Firefox, try setting javascript.options.asmjs to false in
about:config.
Thanks, that worked. At least I can access
hromium: "Aw, Snap!"
> - Firefox: Infinite "Loading ProtonMail..."
> - Iridium: "Aw, Snap!"
>
> Any idea how to fix this?
At least for Firefox, try setting javascript.options.asmjs to false in
about:config.
--
db
Hi,
I have two desktops that run current. After I updated the first desktop
to the latest snapshot I can no longer access ProtonMail
(mail.protonmail.com). When I try, I get the following results:
- Chromium: "Aw, Snap!"
- Firefox: Infinite "Loading ProtonMail..."
- Iridi
Hi,
When I try to access https://mail.protonmail.com with Iridium I get an
"Aw, Snap!" and the following in dmesg:
iridium[19218]: pledge "stdio", syscall 197
iridium[49053]: pledge "rpath", syscall 5
iridium[52712]: pledge "rpath", syscall 5
i
For example, here is my safety diff for cat.
The intrinsic beauty of it's memory handling is beyond words.
You just can't trust a virtual system to do it right; you always
need to check the underlying subsystem isn't messin' with ya.
Index: cat.c
=
> I've just upgraded my workstation to the latest snapshot, including
> newer packages. I use the signal chrome app in iridium and since it
> was complaining about needing an upgrade, I removed the (package
> version iridium-2017.11p0) app and tried to re-install it (iridium has
Hi all,
I've just upgraded my workstation to the latest snapshot, including
newer packages. I use the signal chrome app in iridium and since it
was complaining about needing an upgrade, I removed the (package
version iridium-2017.11p0) app and tried to re-install it (iridium has
a problem
Il 25 apr 2017 14:22, "Caspar Schutijser" ha
scritto:
Hi,
I noticed that the wxallowed check that is in the startup script of
the chromium port is not present in the iridium port. Also, the chromium
port uses ${TRUEPREFIX} in the exec line.
Thanks,
Caspar Schutijser
Index
Hi,
I noticed that the wxallowed check that is in the startup script of
the chromium port is not present in the iridium port. Also, the chromium
port uses ${TRUEPREFIX} in the exec line.
Thanks,
Caspar Schutijser
Index: Makefile
> do i need to install some extra fonts
I've always needed to install fonts for Japanese and Korean to view
them in Firefox: you should be fine after doing that.
i think i remember i had no problems with japanese
fonts on pages like wikipedia before.
do i need to install some extra fonts, or utf-8 takes
care of this (noto font)?
--
"fishing, stranger?" "no, just drowning worms."
On Sun, Oct 16, 2016 at 03:57:11PM +0200, frantisek holop wrote:
> hello fellow iridium users, if any.
>
> recently iridium starts for me only every second time,
> dumping core on the first one. i removed the old
> profile data and still that's the case.
>
> any ide
hello fellow iridium users, if any.
recently iridium starts for me only every second time,
dumping core on the first one. i removed the old
profile data and still that's the case.
any ideas?
OpenBSD 6.0-current (obj) #0: Sat Oct 15 08:45:10 MDT 2016
iridium-51.1p2 Iridium browse
shot. One
> > result is that this diff will make chromium and iridium crash because
> > they do not make "recvfd" promises. Do you see messages like
> >
> > chrome(99124): syscall 27 "recvfd"
> >
> > in your dmesg?
> >
> > If th
I can't tell from your message whether this is the following problem:
There is a diff being discussed that makes pledge "recvfd" stricter. It
is plausible that Theo put this diff into the most recent snapshot. One
result is that this diff will make chromium and iridium crash beca
Hi,
After updating my packages,today, to the latest snapshot, both Chromium
and Iridium
stopped working. When I start them I directly get the "Aw, Snap!
Something went
wrong while displaying this webpage." page.
When I start Chromium from a terminal I get the following messages:
On Fri, Feb 26, 2016 at 11:11:01AM -0500, Michael McConville wrote:
> Seems like the Python module's not working in some context, unless I'm
> doing something wrong. I suspect that rm'ing your /usr/local/bin/python
> symlink (if you have one) will expose this.
This port uses ${WRKDIR}/bin/python w
55 matches
Mail list logo
