On 09/21/2016 09:54 PM, meino.cra...@gmx.de wrote:
> Hi,
>
> Got this this morning:
>
https://bugs.gentoo.org/show_bug.cgi?id=594732
Hi,
Got this this morning:
>>> Emerging (1 of 1) www-client/firefox-49.0::gentoo
* Fetching files in the background.
* To view fetch progress, run in another terminal:
* tail -f /var/log/emerge-fetch.log
* firefox-49.0.source.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...
>> >> I haven't mentioned it yet, but several times I've seen the website
>> >> perform fine all day until I browse to it myself and then all of a
>> >> sudden it's super slow for me and my third-party monitor. WTF???
>> >
>> > I had a similar problems once when routing through a IPsec VPN tunnnel
On Wednesday, September 21, 2016 01:47:28 PM Grant wrote:
> >> I haven't mentioned it yet, but several times I've seen the website
> >> perform fine all day until I browse to it myself and then all of a
> >> sudden it's super slow for me and my third-party monitor. WTF???
> >
> > I had a similar
>> I haven't mentioned it yet, but several times I've seen the website
>> perform fine all day until I browse to it myself and then all of a
>> sudden it's super slow for me and my third-party monitor. WTF???
>
> I had a similar problems once when routing through a IPsec VPN tunnnel.
> I needed to
Am Wed, 21 Sep 2016 22:06:37 +0200
schrieb Kai Krakow :
> Am Wed, 21 Sep 2016 12:37:51 -0700
> schrieb Grant :
>
> > [...]
> > [...]
> [...]
> > >
> > > You may want to set the default congestion control to fq-codel
> > > (it's in the kernel) if you're using DSL links. This may help yo
Am Wed, 21 Sep 2016 12:53:17 -0700
schrieb Grant :
> [...]
> [...]
> >>
> >> You may want to set the default congestion control to fq-codel
> >> (it's in the kernel) if you're using DSL links. This may help your
> >> problem a little bit. It is most effective if you deploy traffic
> >> shapi
Am Wed, 21 Sep 2016 12:32:48 -0700
schrieb Grant :
> [...]
> [...]
> >>
> >>
> >> I'm seeing the issue again as usual but ping response times come
> >> back normal at about 50ms. I'll keep trying.
> >
> > Not sure if this came after or before switching your router to modem
> > mode... But
Am Wed, 21 Sep 2016 12:37:51 -0700
schrieb Grant :
> [...]
> [...]
> >>
> >>
> >> Hi Kai, yesterday I switched my Gentoo router over to handling
> >> PPPoE and pings seem to be working properly now. The AT&T device
> >> is now functioning as a modem only and passing everything
> >> through.
>> > > If that device behaves badly in router mode by blocking just all
>> > > icmp traffic instead of only icmp-echo-req, this is a good idea.
>> > > You may want to bug AT&T about this problem then. It should really
>> > > not block related icmp traffic.
>> >
>> >
>> > Hi Kai, yesterday I switche
Am Wed, 21 Sep 2016 21:29:13 +0200
schrieb Kai Krakow :
> Am Wed, 21 Sep 2016 07:30:40 -0700
> schrieb Grant :
>
> > [...]
> > [...]
> [...]
> > >
> > > If that device behaves badly in router mode by blocking just all
> > > icmp traffic instead of only icmp-echo-req, this is a good ide
>> >> I just remembered that our AT&T modem/router does not respond to
>> >> pings. My solution is to move PPPoE off of that device and onto my
>> >> Gentoo router so that pings pass through the AT&T device to the
>> >> Gentoo router but I haven't done that yet as I want to be on-site
>> >> for it
>> >> Maybe run a ping to a destination which you are having problems
>> >> with, then reproduce the problem (with the network idle
>> >> otherwise). You should see ping packets dropped only then.
>> >>
>> >> You can also ping with increasing packet sizes (see ping --help)
>> >> and see when the pa
Am Wed, 21 Sep 2016 07:30:40 -0700
schrieb Grant :
> [...]
> [...]
> >>
> >>
> >> I just remembered that our AT&T modem/router does not respond to
> >> pings. My solution is to move PPPoE off of that device and onto my
> >> Gentoo router so that pings pass through the AT&T device to the
> >
Am Wed, 21 Sep 2016 10:43:39 -0700
schrieb Grant :
> >> Maybe run a ping to a destination which you are having problems
> >> with, then reproduce the problem (with the network idle
> >> otherwise). You should see ping packets dropped only then.
> >>
> >> You can also ping with increasing packet si
Am Wed, 21 Sep 2016 10:08:31 +0100
schrieb Peter Humphrey :
> On Wednesday 21 Sep 2016 06:08:38 Kai Krakow wrote:
>
> > I upgraded xorg to 1.18 and during that process also enabled
> > USE=wayland. However, I don't run a wayland session (this actually
> > doesn't seem to work with nvidia). I use
>> Maybe run a ping to a destination which you are having problems with,
>> then reproduce the problem (with the network idle otherwise). You should
>> see ping packets dropped only then.
>>
>> You can also ping with increasing packet sizes (see ping --help) and
>> see when the packet becomes too b
I just started using PPPoE on Gentoo for the first time. Could my
config be improved?
config_net0="4.3.2.1/24"
config_net1="1.2.3.4/24"
config_ppp0="ppp"
link_ppp0="net0"
plugins_ppp0="pppoe"
username_ppp0="user"
password_ppp0="pass"
pppd_ppp0="
defaultroute
child-timeout 60
"
Starting n
On Tuesday 20 September 2016, konsolebox wrote:
> On Sun, Sep 18, 2016 at 10:55 PM, Robin Atwood wrote:
> >
> > Anybody got any idea what the problem with kde-sunset is?
>
> Custom repositories listed in /etc/portage/repos.conf/ are
> synchronized with `emerge --sync`. `kde-sunset` is not in la
>> >> A while back I was having networking issues. I eventually tried
>> >> drastically lowering the MTU of all the systems onsite and the
>> >> issues disappeared. I always thought the issue was due to the MTU
>> >> on our modem/router. Today I read that AT&T DSL requires a 1492
>> >> MTU so I
>> >> It looks like the TCP Queuing spike itself was due to imapproxy
>> >> which I've now disabled. I'll post more info as I gather it.
>> >
>> >
>> > imapproxy was clearly affecting the TCP Queuing graph in munin but I
>> > still ended up with a massive TCP Queuing spike today and
>> > correspon
Today's upgrade introduces vim 8.0; since the upgrade affects two
packages (vim and vim-core) and in my case they where many packages
apart in the list of upgrades, for some time vim behaved unexpectedly
("E484: Can't open file /usr/share/vim/syntax/syntax.vim" and no syntax
highlighting). Just
On Wed, Sep 21, 2016 at 5:16 AM, Raymond Jennings wrote:
> Probably should clarify that I wasn't talking about patches. I just
> remember the big git migration and was wondering if the syncing process
> itself would be moved under anongit.gentoo.org at some point so that we
> could avoid relying
On Wednesday 21 Sep 2016 10:57:11 Neil Bothwick wrote:
> On Wed, 21 Sep 2016 09:43:58 +, Franz Fellner wrote:
> > > Good suggestion, thanks. notification-deamon wants the upgrade, I'll
> > > try with some more masking or USE change.
> >
> > --verbose --tree (short: -vt) should really be used b
Also it appears that #gentoo-infra is invite only.
On Wed, Sep 21, 2016 at 2:16 AM, Raymond Jennings
wrote:
> Probably should clarify that I wasn't talking about patches. I just
> remember the big git migration and was wondering if the syncing process
> itself would be moved under anongit.gento
On Wed, 21 Sep 2016 09:43:58 +, Franz Fellner wrote:
> > Good suggestion, thanks. notification-deamon wants the upgrade, I'll
> > try with some more masking or USE change.
>
> --verbose --tree (short: -vt) should really be used by default ;) It
> doesn't hurt but it is a great help.
I disa
> Good suggestion, thanks. notification-deamon wants the upgrade, I'll try
> with some more masking or USE change.
--verbose --tree (short: -vt) should really be used by default ;) It doesn't
hurt
but it is a great help.
> Do you have a reference regarding the meld issue so I can track it?
Not
Probably should clarify that I wasn't talking about patches. I just
remember the big git migration and was wondering if the syncing process
itself would be moved under anongit.gentoo.org at some point so that we
could avoid relying on github (per social contact thingy)
On Tue, Sep 20, 2016 at 12:
Franz Fellner wrote:
> Adding "--verbose --tree" to your emerge options probably reveals the
> offending package.
> It is likely this is caused by a dependency you have not yet masked.
>
> Meld master already contains fixes for those issues, so hopefully they
> release a fixed
> version soon...
>
On Wednesday 21 Sep 2016 06:08:38 Kai Krakow wrote:
> I upgraded xorg to 1.18 and during that process also enabled
> USE=wayland. However, I don't run a wayland session (this actually
> doesn't seem to work with nvidia). I use sddm as the login manager, and
> I'm running latest plasma 5.7. The sys
Adding "--verbose --tree" to your emerge options probably reveals the offending
package.
It is likely this is caused by a dependency you have not yet masked.
Meld master already contains fixes for those issues, so hopefully they release
a fixed
version soon...
On Wed, 21 Sep 2016 10:30:21 +0200
I have masked >gtk+-3.18.9 due to issues with meld on my system [1],[2].
Today's update wants me to unmask it [3]. Checking the ebuilds, none of
the packages emerge lists should need a gtk+ higher than gtk+-3.18.9;
for example the most probable candidate, gcr-3.20.,0 depends only on:
COMMON_DEPEN
32 matches
Mail list logo
