Firefox build broken

2017-02-09 Thread Domagoj Stolfa
Hello,

It would seem that the firefox build is broken on 12.0-CURRENT. I've been
getting the same error as seem on [1]. Has anyone else experienced this?

[1] 
https://lists.freebsd.org/pipermail/freebsd-pkg-fallout/Week-of-Mon-20170206/408053.html

--
Best regards,
Domagoj Stolfa


signature.asc
Description: PGP signature


Re: pkg upgrade deletes firefox?

2017-02-09 Thread Domagoj Stolfa
This is due to the DTRACE option breaking the Firefox build currently. You can
compile it from ports by disabling the DTRACE option.

--
Best regards,
Domagoj Stolfa

On Thu, Feb 09, 2017 at 09:21:18PM +0100, Ronald Klop wrote:
> Interesting:
>
> # 21:12:51 root@sjakie [~]
> pkg install firefox
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up-to-date.
> All repositories are up-to-date.
> pkg: No packages available to install matching 'firefox' have been found
> in the repositories
>
> I guess this is a temporary hickup.
>
> Ronald.
>
>
>
> On Thu, 09 Feb 2017 21:12:28 +0100, Ronald Klop 
> wrote:
>
> > Hi,
> >
> > Today I get this...
> >
> > # 21:08:42 root@sjakie [~]
> > pkg upgrade
> > Updating FreeBSD repository catalogue...
> > Fetching meta.txz: 100%944 B   0.9kB/s00:01
> > Fetching packagesite.txz: 100%6 MiB   3.0MB/s00:02
> > Processing entries: 100%
> > FreeBSD repository update completed. 25950 packages processed.
> > Checking for upgrades (13 candidates): 100%
> > Processing candidates (13 candidates): 100%
> > The following 13 package(s) will be affected (of 0 checked):
> >
> > Installed packages to be REMOVED:
> > firefox-51.0.1,1
> >
> > Installed packages to be UPGRADED:
> > xkeyboard-config: 2.19 -> 2.20
> > xconsole: 1.0.6_1 -> 1.0.7
> > xauth: 1.0.9_1 -> 1.0.10
> > vim-lite: 8.0.0252 -> 8.0.0301
> > tmux: 2.3 -> 2.3_1
> > opencollada: 1.6.25 -> 1.6.37
> > mplayer: 1.3.0.20161228_2 -> 1.3.0.20161228_3
> > libevent2: 2.0.22_1 -> 2.1.8
> > libass: 0.13.5 -> 0.13.6
> > gstreamer1: 1.8.0 -> 1.8.0_1
> > gstreamer: 0.10.36_5 -> 0.10.36_6
> > ffmpeg: 3.2.2_5,1 -> 3.2.2_6,1
> >
> > Number of packages to be removed: 1
> > Number of packages to be upgraded: 12
> >
> > The operation will free 124 MiB.
> > 25 MiB to be downloaded.
> >
> > Proceed with this action? [y/N]:
> >
> >
> > Why would upgrade want to remove firefox?
> >
> > Regards,
> > Ronald.
> > ___
> > freebsd-sta...@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


signature.asc
Description: PGP signature


Re: Crashing chromium/iridium

2017-10-06 Thread Domagoj Stolfa
I’ve found this to be an issue as well. None of the things that I’ve seen 
suggested online could fix it, and unfortunately do not have time to look at it 
myself. I’d be interested to hear if anyone has any more details regarding this 
issue.

—
Domagoj

> On 6 Oct 2017, at 20:39, Grzegorz Junka  wrote:
> 
> Just wanted to check if anybody else observed this annoying behaviour in 
> Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab 
> hangs loading for 30-60 seconds, after which time the browser shows a dialog 
> that the webpage doesn't load and I can either kill or wait.
> 
> There is no pattern, sometimes I can open 10 tabs with no issues, but 
> sometimes 10 tabs hang in a row and need to be killed. Very often when I kill 
> the page reloading the page doesn't help, it still hangs, but when I open the 
> same URL in a new tab it works. Sometimes, however, reloading the page also 
> works.
> 
> I compiled and installed Iridium hoping that it will be free from this bug 
> but it seems that the behaviour is exactly the same as in Chromium. It has 
> been happening for the past year at least. Maybe some of the options I 
> checked for Chromium/Iridium don't work well or maybe some of its 
> dependencies are compiled with options that don't work well. How would I 
> investigate it?
> 
> I didn't try to install precompiled versions. Also, the issue doesn't happen 
> with other browsers (Firefox, any other I could compile on FreeBSD are also 
> fine). I tried to open in safe mode, without extensions, but all without any 
> difference in this behaviour.
> 
> Thanks
> 
> GrzegorzJ
> 
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



signature.asc
Description: Message signed with OpenPGP