Re: [gentoo-user] Re: Kernel 4.14.14 has meltdown / spectre info in /sys

2018-01-24 Thread Adam Carter
>
> > $ cat /sys/devices/system/cpu/vulnerabilities/meltdown
> > Not affected
>
> Aha.
>
> matica!1 ~$ cat /sys/devices/system/cpu/vulnerabilities/meltdown
> Not affected
>  matica!2 ~$ uname -r
> 4.9.78
>
> I guess these patches will be trickling down for a long time yet.
>

Good to see.

Seems to me like point versions of 4.9 and 4.14 are often released on the
same date, but fixes that have gone into 4.14 don't make it into 4.9 until
the subsequent release. Could be my imagination.


Re: [gentoo-user] chromium build failure

2018-01-24 Thread Canek Peláez Valdés
On Wed, Jan 24, 2018 at 10:11 PM, allan gottlieb  wrote:
>
> I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the
> build logs are essentially identical.  After about 12 hours compiling and
> 36MB of build.log, the error shown below occurs
>
> I have two laptops with *very* similar gentoo distributions.  The newer
> machine had a successful build first try.  The second older (4 years)
> machine had both failures.  Each machine has profile
> default/linux/amd64/17.0/desktop/gnome/systemd

If the USE flags for chromium on both machines are the same, simply create
a binary package from the machine that already built it.

machine1:

$ quickpkg --include-config=y www-client/chromium

machine2

$ sync --delete -Pvase ssh machine1:/usr/portage/packages/
/usr/portage/packages/
$ emerge --nodeps -1Kv www-client/chromium

I have two powerful desktop computers (home and office) and a laptop. Their
USE flags are identical; I just compile in one of them and generate binary
packages for the other two. It helps (but it's not 100% required) if the
/usr/portage tree is identical (I sync only with one and rsync the others,
followed by emerge --metadata).

Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México


Re: [gentoo-user] Re: Using both Gnome and KDE Plasma?

2018-01-24 Thread Dale
Nikos Chantziaras wrote:
> On 25/01/18 04:34, Dale wrote:
>> This is what I would do.  I would make sure emerge -uDNp world comes
>> back clean, no remerges or updates.  Change profile to generic desktop.
>
> There's no "desktop/systemd" profile. I'm on systemd. If I switch to
> the "systemd" profile, then I lose what's in the "desktop" profile.
>
>
>

When you run emerge -DNp world, any systemd changes should show up and
then you can add them to either make.conf or package.use.  I wouldn't be
surprised if the biggest change is the USE flag systemd itself. 

I guess you could pick whichever is going to be used most, KDE or Gnome,
and then add the other variables in as needed.  Either way, you are
going to have to adjust USE flags and such. 

Dale

:-)  :-) 



[gentoo-user] chromium build failure

2018-01-24 Thread allan gottlieb
I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the
build logs are essentially identical.  After about 12 hours compiling and
36MB of build.log, the error shown below occurs

I have two laptops with *very* similar gentoo distributions.  The newer
machine had a successful build first try.  The second older (4 years)
machine had both failures.  Each machine has profile
default/linux/amd64/17.0/desktop/gnome/systemd

Thanks in advance for any help.

allan



[132/15175] python ../../chrome/browser/resources/optimize_webui.py --host 
history --input ../../chrome/browser/resources/md_history --out_folder 
gen/chrome/browser/resources/md_history --depfile 
gen/chrome/browser/resources/md_history/build.d --html_in_files app.html 
lazy_load.html --html_out_files app.vulcanized.html lazy_load.vulcanized.html 
--js_out_files app.crisper.js lazy_load.crisper.js --exclude 
chrome://resources/html/util.html chrome://history/constants.html
FAILED: gen/chrome/browser/resources/md_history/app.vulcanized.html 
gen/chrome/browser/resources/md_history/lazy_load.vulcanized.html 
gen/chrome/browser/resources/md_history/app.crisper.js 
gen/chrome/browser/resources/md_history/lazy_load.crisper.js 
python ../../chrome/browser/resources/optimize_webui.py --host history --input 
../../chrome/browser/resources/md_history --out_folder 
gen/chrome/browser/resources/md_history --depfile 
gen/chrome/browser/resources/md_history/build.d --html_in_files app.html 
lazy_load.html --html_out_files app.vulcanized.html lazy_load.vulcanized.html 
--js_out_files app.crisper.js lazy_load.crisper.js --exclude 
chrome://resources/html/util.html chrome://history/constants.html
../../third_party/node/linux/node-linux-x64/bin/node 
../../third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler 
--exclude chrome://resources/html/polymer.html --exclude 
chrome://resources/polymer/v1_0/polymer/polymer.html --exclude 
chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude 
chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude 
chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js
 --exclude chrome://resources/css/roboto.css --exclude 
chrome://resources/css/text_defaults.css --exclude 
chrome://resources/css/text_defaults_md.css --exclude 
chrome://resources/js/load_time_data.js --inline-css --inline-scripts 
--rewrite-urls-in-templates --strip-comments --redirect 
"chrome://resources/cr_components/|../../ui/webui/resources/cr_components" 
--redirect 
"chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements" 
--redirect "chrome://resources/css/|../../ui/webui/resources/css" --redirect 
"chrome://resources/html/|../../ui/webui/resources/html" --redirect 
"chrome://resources/js/|../../ui/webui/resources/js" --redirect 
"chrome://resources/polymer/v1_0/|../../third_party/polymer/v1_0/components-chromium"
 --exclude chrome://resources/html/util.html --exclude 
chrome://history/constants.html --exclude strings.js --exclude 
chrome://history/strings.js --manifest-out 
/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/out/Release/gen/chrome/browser/resources/md_history/history_requestlist.txt
 --root 
/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/chrome/browser/resources/md_history
 --redirect 
"chrome://history/|/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/chrome/browser/resources/md_history"
 --out-dir gen/chrome/browser/resources/md_history/bundled --shell app.html 
--in-html app.html --in-html lazy_load.html failed: module.js:471
throw err;
^

Error: Cannot find module 
'/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:383:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:496:3

Traceback (most recent call last):
  File "../../chrome/browser/resources/optimize_webui.py", line 252, in 
main(sys.argv[1:])
  File "../../chrome/browser/resources/optimize_webui.py", line 235, in main
manifest_out_path = _optimize(args.input, args)
  File "../../chrome/browser/resources/optimize_webui.py", line 159, in 
_optimize
] + in_html_args)
  File "../../third_party/node/node.py", line 28, in RunNode
raise
TypeError: exceptions must be old-style classes or derived from BaseException, 
not NoneType
ninja: build stopped: subcommand failed.
 [31;01m*[0m ERROR: www-client/chromium-63.0.3239.132::gentoo failed (compile 
phase):
 [31;01m*[0m   ninja -v -j1 -l0 -C out/Release chrome chromedriver failed
 [31;01m*[0m 
 [31;01m*[0m Call stack:
 [31;01m*[0m ebuild.sh, line  124:  Called src_compile
 [31;01m

[gentoo-user] Firefox, pulseaudio and waiting for rust to build...

2018-01-24 Thread tuxic
Hi,

I switched from firefox-bin to firefox to get rid of the pulseaudio
dependancy ... which seems to imply, that rust is build also.

I only have an AMD Phenom(tm) II X6 1090T Processor...and building
rust takesquite.some.time.

Is it valid to replace rust (from source) by rust-bin?

Is it as easy as

emerge -C rust

and after unmasking the appropiate version of rust-bin

emerge rust-bin 

?

Are there any drawbacks or will it work flawlessly?

Thanks a lot for any help in advance!

Cheers
Meino





[gentoo-user] Re: Using both Gnome and KDE Plasma?

2018-01-24 Thread Nikos Chantziaras

On 25/01/18 04:34, Dale wrote:

This is what I would do.  I would make sure emerge -uDNp world comes
back clean, no remerges or updates.  Change profile to generic desktop.


There's no "desktop/systemd" profile. I'm on systemd. If I switch to the 
"systemd" profile, then I lose what's in the "desktop" profile.





Re: [gentoo-user] Re: Using both Gnome and KDE Plasma?

2018-01-24 Thread Dale
R0b0t1 wrote:
> On Wed, Jan 24, 2018 at 8:34 PM, Dale  wrote:
>> Nikos Chantziaras wrote:
>>> On 25/01/18 02:28, Neil Bothwick wrote:
 On Thu, 25 Jan 2018 01:16:07 +0200, Nikos Chantziaras wrote:

> One user wants Gnome, the other wants Plasma. Is this doable?
>
> Currently, Plasma is installed, and the profile is:
>
> default/linux/amd64/17.0/desktop/plasma/systemd
>
> The profiles seem to be either-or. There's one for plasma, one for
> gnome. But I need both now :-/
 The differences between the profiles are mainly the USE flags set. As
 your system is already built with the plasma profiles, I'd add gnome to
 your USE flags and emerge gnome-base/gnome. Portage will shout at you if
 you need to enable any other USE flags.
>>> Don't know. There's use flags that seem to be set because it's
>>> recommended to set them, not because they're needed.
>>>
>>> It seems to me that I have to choose either-or here in order to have a
>>> well working desktop. Otherwise, if something doesn't seem work right,
>>> I'll never know whether it's because of the profile or because of
>>> something else.
>>>
>>> I suppose I have to switch to the gnome profile and then see if KDE is
>>> still working as before. But it seems I'll have to manually replicate
>>> whatever the plasma profile is setting by hand.
>>>
>>>
>>>
>>
>> This is what I would do.  I would make sure emerge -uDNp world comes
>> back clean, no remerges or updates.  Change profile to generic desktop.
>> Do a emerge -DNp world and look at what changes, especially USE flags.
>> Take those changes and set them in make.conf or package.use if you
>> prefer.  Since both KDE and Gnome has their own desktop profile, using
>> the generic profile I think would be the best bet.  You just may have to
>> set some things in make.conf/package.use to add KDE and Gnome settings
>> to have both installed at the same time.
>>
> Yes, this works and I've done it, which is why I recommended it.
>
> Cheers,
>  R0b0t1
>
>


Yea, I just added the steps to it and some reasoning for each step,
mostly.  Having both should be doable for sure.  One just has to make
sure the USE flags and such are right. 

Of course, one has to watch USE flag changes even when doing regular
updates but I went over mine with a fine tooth comb during the recent
profile update as well.  One has to look for those yellow characters
when doing updates, at any time but some are more important than
others.  Sometimes one USE flag change can make things either not work
right or not work at all.  Of course, it can add some nifty feature
too.  ;-) 

Dale

:-)  :-) 



Re: [gentoo-user] Re: Using both Gnome and KDE Plasma?

2018-01-24 Thread R0b0t1
On Wed, Jan 24, 2018 at 8:34 PM, Dale  wrote:
> Nikos Chantziaras wrote:
>> On 25/01/18 02:28, Neil Bothwick wrote:
>>> On Thu, 25 Jan 2018 01:16:07 +0200, Nikos Chantziaras wrote:
>>>
 One user wants Gnome, the other wants Plasma. Is this doable?

 Currently, Plasma is installed, and the profile is:

 default/linux/amd64/17.0/desktop/plasma/systemd

 The profiles seem to be either-or. There's one for plasma, one for
 gnome. But I need both now :-/
>>>
>>> The differences between the profiles are mainly the USE flags set. As
>>> your system is already built with the plasma profiles, I'd add gnome to
>>> your USE flags and emerge gnome-base/gnome. Portage will shout at you if
>>> you need to enable any other USE flags.
>>
>> Don't know. There's use flags that seem to be set because it's
>> recommended to set them, not because they're needed.
>>
>> It seems to me that I have to choose either-or here in order to have a
>> well working desktop. Otherwise, if something doesn't seem work right,
>> I'll never know whether it's because of the profile or because of
>> something else.
>>
>> I suppose I have to switch to the gnome profile and then see if KDE is
>> still working as before. But it seems I'll have to manually replicate
>> whatever the plasma profile is setting by hand.
>>
>>
>>
>
>
> This is what I would do.  I would make sure emerge -uDNp world comes
> back clean, no remerges or updates.  Change profile to generic desktop.
> Do a emerge -DNp world and look at what changes, especially USE flags.
> Take those changes and set them in make.conf or package.use if you
> prefer.  Since both KDE and Gnome has their own desktop profile, using
> the generic profile I think would be the best bet.  You just may have to
> set some things in make.conf/package.use to add KDE and Gnome settings
> to have both installed at the same time.
>

Yes, this works and I've done it, which is why I recommended it.

Cheers,
 R0b0t1



Re: [gentoo-user] Re: Using both Gnome and KDE Plasma?

2018-01-24 Thread Dale
Nikos Chantziaras wrote:
> On 25/01/18 02:28, Neil Bothwick wrote:
>> On Thu, 25 Jan 2018 01:16:07 +0200, Nikos Chantziaras wrote:
>>
>>> One user wants Gnome, the other wants Plasma. Is this doable?
>>>
>>> Currently, Plasma is installed, and the profile is:
>>>
>>>     default/linux/amd64/17.0/desktop/plasma/systemd
>>>
>>> The profiles seem to be either-or. There's one for plasma, one for
>>> gnome. But I need both now :-/
>>
>> The differences between the profiles are mainly the USE flags set. As
>> your system is already built with the plasma profiles, I'd add gnome to
>> your USE flags and emerge gnome-base/gnome. Portage will shout at you if
>> you need to enable any other USE flags.
>
> Don't know. There's use flags that seem to be set because it's
> recommended to set them, not because they're needed.
>
> It seems to me that I have to choose either-or here in order to have a
> well working desktop. Otherwise, if something doesn't seem work right,
> I'll never know whether it's because of the profile or because of
> something else.
>
> I suppose I have to switch to the gnome profile and then see if KDE is
> still working as before. But it seems I'll have to manually replicate
> whatever the plasma profile is setting by hand.
>
>
>


This is what I would do.  I would make sure emerge -uDNp world comes
back clean, no remerges or updates.  Change profile to generic desktop. 
Do a emerge -DNp world and look at what changes, especially USE flags. 
Take those changes and set them in make.conf or package.use if you
prefer.  Since both KDE and Gnome has their own desktop profile, using
the generic profile I think would be the best bet.  You just may have to
set some things in make.conf/package.use to add KDE and Gnome settings
to have both installed at the same time. 

That's my two cents. 

Dale

:-)  :-) 



[gentoo-user] Re: Using both Gnome and KDE Plasma?

2018-01-24 Thread Nikos Chantziaras

On 25/01/18 02:28, Neil Bothwick wrote:

On Thu, 25 Jan 2018 01:16:07 +0200, Nikos Chantziaras wrote:


One user wants Gnome, the other wants Plasma. Is this doable?

Currently, Plasma is installed, and the profile is:

default/linux/amd64/17.0/desktop/plasma/systemd

The profiles seem to be either-or. There's one for plasma, one for
gnome. But I need both now :-/


The differences between the profiles are mainly the USE flags set. As
your system is already built with the plasma profiles, I'd add gnome to
your USE flags and emerge gnome-base/gnome. Portage will shout at you if
you need to enable any other USE flags.


Don't know. There's use flags that seem to be set because it's 
recommended to set them, not because they're needed.


It seems to me that I have to choose either-or here in order to have a 
well working desktop. Otherwise, if something doesn't seem work right, 
I'll never know whether it's because of the profile or because of 
something else.


I suppose I have to switch to the gnome profile and then see if KDE is 
still working as before. But it seems I'll have to manually replicate 
whatever the plasma profile is setting by hand.





Re: [gentoo-user] Using both Gnome and KDE Plasma?

2018-01-24 Thread Neil Bothwick
On Thu, 25 Jan 2018 01:16:07 +0200, Nikos Chantziaras wrote:

> One user wants Gnome, the other wants Plasma. Is this doable?
> 
> Currently, Plasma is installed, and the profile is:
> 
>default/linux/amd64/17.0/desktop/plasma/systemd
> 
> The profiles seem to be either-or. There's one for plasma, one for 
> gnome. But I need both now :-/

The differences between the profiles are mainly the USE flags set. As
your system is already built with the plasma profiles, I'd add gnome to
your USE flags and emerge gnome-base/gnome. Portage will shout at you if
you need to enable any other USE flags.


-- 
Neil Bothwick

When you finally buy enough memory, you will not have enough disk space.
 -- Murphy's Computer Laws n\xB03


pgpBZUKTOsV7D.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Using both Gnome and KDE Plasma?

2018-01-24 Thread R0b0t1
On Wed, Jan 24, 2018 at 5:16 PM, Nikos Chantziaras  wrote:
> One user wants Gnome, the other wants Plasma. Is this doable?
>
> Currently, Plasma is installed, and the profile is:
>
>   default/linux/amd64/17.0/desktop/plasma/systemd
>
> The profiles seem to be either-or. There's one for plasma, one for gnome.
> But I need both now :-/
>

Pick the desktop profile with no DE. Install kde-plasma/plasma-meta
and gnome-base/gnome. There should be a drop down in your display
manager that will allow you to select which DE to launch. If your
desktop manager is associated with a DE this may be harder to find. I
suggest SDDM.

Beware, sir. The Gnome foot is the left, or sinister, foot.

Cheers,
 R0b0t1



Re: [gentoo-user] Using both Gnome and KDE Plasma?

2018-01-24 Thread Peter Humphrey
On Wednesday, 24 January 2018 23:16:07 GMT Nikos Chantziaras wrote:
> One user wants Gnome, the other wants Plasma. Is this doable?
> 
> Currently, Plasma is installed, and the profile is:
> 
>default/linux/amd64/17.0/desktop/plasma/systemd
> 
> The profiles seem to be either-or. There's one for plasma, one for
> gnome. But I need both now :-/

Choose the desktop profile?

-- 
Regards,
Peter.




Re: [SUSPECTED SPAM] Re: [gentoo-user] Questions about Pale Moon

2018-01-24 Thread Peter Humphrey
On Wednesday, 24 January 2018 21:40:18 GMT Walter Dnes wrote:
> On Wed, Jan 24, 2018 at 11:43:31AM +, Peter Humphrey wrote
> 
> > On Tuesday, 23 January 2018 18:27:21 GMT Walter Dnes wrote:
> > 
> > Yes, I do have them both installed already.
> > 
> > > Is this the official Pale Moon, or an unofficial build?
> > 
> > It's www-client/palemoon-bin-27.7.1::palemoon. I don't know whether
> > that's "official", because when I "layman -a palemoon" I'm told it's
> > not an official overlay. Different officialdoms, I suppose.
> 
> Disclosure... I'm a volunteer for the Pale Moon project (not an official
> spokesman).

Yes, I'd gathered that. Kudos to you :)

> I do a contributed build for Pentium3-class machines.  My idea of
> "official" is obviously "from the Pale Moon website".  Can you do a quick-
> n-dirty install from the official tarball to check if the icon problem
> happens with the official Pale Moon?  This test will install into $HOME/pm
> 
> 1) Go to http://linux.palemoon.org/download/mainline/ and download the
> appropriate (32 or 64 bit) tarball for your system.
> 
> 2) killall palemoon  # Ignore error message if Pale Moon not running.
> 
> 3) rm -rf $HOME/pm && mkdir $HOME/pm  # Start from a known state
> 
> 4) tar -C $HOME/pm -xvjf   # Extract tarball
> 
> 5) $HOME/pm/palemoon/palemoon  # Launch Pale Moon
> 
>   Note; this install is self-contained.  It does not splatter stuff all
> over various library directories.  Does the icon problem still happen
> with the official tarball?

'Fraid so, and I still get those undefined-symbol errors I mentioned.

> > This is with gcc 4.9.4, and I get the same with gcc 6.4.0.
> 
> 6.3.0 builds Pale Moon OK on profile 13.  I'll soon be doing the switch
> over to 17 on my 32-bit desktop.  You might be able to get things working
> with custom flags for the Pale Moon ebuild using package.env as per... 
> https://wiki.gentoo.org/wiki//etc/portage/package.env

Hmm. I'll have to put my thinking-cap on for that. Maybe tomorrow. This is 
what portage wants to do (I'm on profile 17.0):

[ebuild  N#] www-client/palemoon-27.7.1::palemoon  USE="alsa dbus 
devtools gtk2 official-branding optimize -debug -ffmpeg (-gtk3) -jemalloc -
necko-wifi -pulseaudio -shared-js -system-bzip2 -system-libevent -system-
libvpx -system-libwebp -system-sqlite -system-zlib -threads -valgrind -
webrtc" CPU_FLAGS_X86="sse sse2" 0 KiB

-- 
Regards,
Peter.




[gentoo-user] Using both Gnome and KDE Plasma?

2018-01-24 Thread Nikos Chantziaras

One user wants Gnome, the other wants Plasma. Is this doable?

Currently, Plasma is installed, and the profile is:

  default/linux/amd64/17.0/desktop/plasma/systemd

The profiles seem to be either-or. There's one for plasma, one for 
gnome. But I need both now :-/





[gentoo-user] Re: Kernel 4.14.14 has meltdown / spectre info in /sys

2018-01-24 Thread Ian Zimmerman
On 2018-01-19 10:50, Adam Carter wrote:

> > Looking at the kernel source (for 4.9.77), the flag is initially set no
> > matter what in arch/x86/kernel/cpu/common.c @cpu_show_meltdown(), and
> > nothing afterwards clears it ...
> 
> 
> With 4.14.14, pretty much same CPU;
> model   : 4
> model name  : AMD Phenom(tm) II X4 965 Processor
> stepping: 3
> 
> $ cat /sys/devices/system/cpu/vulnerabilities/meltdown
> Not affected

Aha.

matica!1 ~$ cat /sys/devices/system/cpu/vulnerabilities/meltdown 
Not affected
 matica!2 ~$ uname -r
4.9.78

I guess these patches will be trickling down for a long time yet.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.



[SUSPECTED SPAM] Re: [gentoo-user] Questions about Pale Moon

2018-01-24 Thread Walter Dnes
On Wed, Jan 24, 2018 at 11:43:31AM +, Peter Humphrey wrote
> On Tuesday, 23 January 2018 18:27:21 GMT Walter Dnes wrote:
> 
> Yes, I do have them both installed already.
> 
> > Is this the official Pale Moon, or an unofficial build?
> 
> It's www-client/palemoon-bin-27.7.1::palemoon. I don't know whether
> that's "official", because when I "layman -a palemoon" I'm told it's
> not an official overlay. Different officialdoms, I suppose.

  Disclosure... I'm a volunteer for the Pale Moon project (not an
official spokesman).  I do a contributed build for Pentium3-class
machines.  My idea of "official" is obviously "from the Pale Moon
website".  Can you do a quick-n-dirty install from the official tarball
to check if the icon problem happens with the official Pale Moon?  This
test will install into $HOME/pm

1) Go to http://linux.palemoon.org/download/mainline/ and download the
appropriate (32 or 64 bit) tarball for your system.

2) killall palemoon  # Ignore error message if Pale Moon not running.

3) rm -rf $HOME/pm && mkdir $HOME/pm  # Start from a known state

4) tar -C $HOME/pm -xvjf   # Extract tarball

5) $HOME/pm/palemoon/palemoon  # Launch Pale Moon

  Note; this install is self-contained.  It does not splatter stuff all
over various library directories.  Does the icon problem still happen
with the official tarball?

> This is with gcc 4.9.4, and I get the same with gcc 6.4.0. I've only just 
> noticed that about -fPIC; haven't all those problems been fixed by now?

  6.3.0 builds Pale Moon OK on profile 13.  I'll soon be doing the
switch over to 17 on my 32-bit desktop.  You might be able to get things
working with custom flags for the Pale Moon ebuild using package.env as
per...  https://wiki.gentoo.org/wiki//etc/portage/package.env

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications



Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

2018-01-24 Thread Corbin Bird


On 01/23/2018 11:06 PM, Adam Carter wrote:
>
> FYI, this is from 4.14.15's ChangeLog, doesn't appear to be in 4.9.78
> though.
>
> commit f41b2d7ee791e845147a3e3cafb25493dca6870a
> Author: Josh Poimboeuf mailto:jpoim...@redhat.com>>
> Date:   Mon Jan 15 08:17:07 2018 -0600
>
> objtool: Fix seg fault with gold linker
> 
> commit 2a0098d70640dda192a79966c14d449e7a34d675 upstream.
> 
> Objtool segfaults when the gold linker is used with
> CONFIG_MODVERSIONS=y and CONFIG_UNWINDER_ORC=y.
> 
> With CONFIG_MODVERSIONS=y, the .o file gets passed to the linker before
> being passed to objtool.  The gold linker seems to strip unused ELF
> symbols by default, which confuses objtool and causes the seg fault when
> it's trying to generate ORC metadata.
> 
> Objtool should really be running immediately after GCC anyway, without a
> linker call in between.  Change the makefile ordering so that objtool is
> called before the linker.
.
FYI :
Found the culprit ... ( very late last night )
.
sys-kernel/gentoo-sources has a USE Flag of 'experimental'
The experimental patch enables additional choices for CPU.
The last kernel version with no problem was 4.9.76-r1
The choice that worked before was : AMD Piledriver
That induces the error now.
.
When I compiled with CPU set to :
K-8 --> no problem
Generic x86_64 --> no problem
.
That was the only change made in 'menuconfig' before every test compile.
.
Now I know why all the warnings from the 'objtool', during compile, also
disappeared.
( With CPU set to either : K-8, Generic x86_64 )
> Objtool should really be running immediately after GCC anyway, without a
> linker call in between.  Change the makefile ordering so that objtool is
> called before the linker.
Thinking the 'experimental patch' may be needing some attention.
.
So ... now I am looking at filling a bug report ( if appropriate ) on
Gentoo's bug tracker.
.
Thanks to every one who chipped in with suggestions.
.
Corbin



Re: [gentoo-user] Questions about Pale Moon

2018-01-24 Thread Dale
Peter Humphrey wrote:
> On Wednesday, 24 January 2018 17:09:19 GMT Dale wrote:
>
>> Maybe check and see if you have librsvg installed??
> Thanks Dale. Yes, it is installed - is it even possible to run KDE without 
> it, I wonder?
>


Well, I get this here:


root@fireball / # equery d gnome-base/librsvg
 * These packages depend on gnome-base/librsvg:
kde-apps/kwave-17.12.1 (handbook ? gnome-base/librsvg)
mate-base/mate-control-center-1.18.1 (>=gnome-base/librsvg-2.0:2)
mate-base/mate-panel-1.18.2 (>=gnome-base/librsvg-2.36.2:2)
mate-extra/mate-system-monitor-1.18.0 (>=gnome-base/librsvg-2.35:2)
media-gfx/enblend-4.2.0_p20161007-r1 (doc ? gnome-base/librsvg)
media-gfx/eom-1.18.2 (svg ? >=gnome-base/librsvg-2.36.2:2)
media-gfx/gimp-2.9.8-r1 (>=gnome-base/librsvg-2.40.6:2)
media-gfx/graphviz-2.40.1-r1 (svg ? gnome-base/librsvg)
media-gfx/imagemagick-7.0.7.19 (svg ? gnome-base/librsvg)
media-libs/gegl-0.3.26 (svg ? >=gnome-base/librsvg-2.40.6:2)
media-video/vlc-2.2.8-r1 (svg ? >=gnome-base/librsvg-2.9:2)
sci-chemistry/chemical-mime-data-0.1.94-r3 (gnome-base/librsvg)
x11-libs/gtk+-2.24.31-r1
(gnome-base/librsvg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
x11-libs/gtk+-3.22.19
(gnome-base/librsvg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
x11-themes/adwaita-icon-theme-3.24.0 (gnome-base/librsvg:2)
x11-themes/gnome-icon-theme-symbolic-3.12.0 (gnome-base/librsvg)
x11-wm/openbox-3.6.1 (svg ? gnome-base/librsvg:2)
xfce-base/xfce4-meta-4.12-r1 (svg ? gnome-base/librsvg)
root@fireball / #



There is one kde package in there but I think KDE needs some of the
others too.  It appears that a couple GUIs need that package.  Of
course, I'm sure I could change USE flags and whittle that down but then
I might start missing things too.  ;-) 

Dale

:-)  :-) 



Re: [gentoo-user] Questions about Pale Moon

2018-01-24 Thread Peter Humphrey
On Wednesday, 24 January 2018 17:09:19 GMT Dale wrote:

> Maybe check and see if you have librsvg installed??

Thanks Dale. Yes, it is installed - is it even possible to run KDE without 
it, I wonder?

-- 
Regards,
Peter.




Re: [gentoo-user] Questions about Pale Moon

2018-01-24 Thread Dale
Peter Humphrey wrote:
> On Tuesday, 23 January 2018 12:08:12 GMT Arve Barsnes wrote:
>
>> Maybe check command line output?
> I get eight of these: "undefined symbol: UCNV_TO_U_CALLBACK_STOP". The full 
> list is attached.
>


If it helps any:

root@fireball / # equery b
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
 * Searching for
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so ...
gnome-base/librsvg-2.40.18
(/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so)
root@fireball / #

Maybe check and see if you have librsvg installed??

Dale

:-)  :-) 



Re: [gentoo-user] Questions about Pale Moon

2018-01-24 Thread Peter Humphrey
On Tuesday, 23 January 2018 12:08:12 GMT Arve Barsnes wrote:

> Maybe check command line output?

I get eight of these: "undefined symbol: UCNV_TO_U_CALLBACK_STOP". The full 
list is attached.

-- 
Regards,
Peter.
$ palemoon-bin

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'go-previous' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'go-next' for stock: 
Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'view-refresh' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'process-stop' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'go-home' for stock: 
Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'view-refresh' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'process-stop' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'edit-find' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'list-add' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'window-close' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'view-refresh' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'process-stop' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'go-previous' for 
stock: Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP

(pale moon:2395): Gtk-WARNING **: Error loading theme icon 'go-next' for stock: 
Unable to load image-loading module: 
/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: 
/usr/lib64/libxml2.so.2: undefined symbol: UCNV_TO_U_CALLBACK_STOP


[gentoo-user] net-fs/samba: USE-flags for domain member server

2018-01-24 Thread Stefan G. Weichinger

I am running a gentoo server with net-fs/samba-4.6.12 as domain member
server in an Active Directory domain with 2 Debian 9.3 servers running
samba-4.6.12 as well.

We see issues like all the smbd-sessions stopping to work and I am
trying to find the reason.

What USE-flags do you gentoo-users use for domain member servers?

I wonder if this is still OK:

# from "equery u":
acl ads gnutls ldap pam python_targets_python2_7 system-mitkrb5  systemd
winbind

# cat package.use.samba
net-fs/samba ads ldap winbind gnutls



Re: [gentoo-user] Questions about Pale Moon

2018-01-24 Thread Peter Humphrey
On Tuesday, 23 January 2018 18:27:21 GMT Walter Dnes wrote:
> On Tue, Jan 23, 2018 at 11:58:52AM +, Peter Humphrey wrote
> 
> > Q 1:  I've asked this before, but I can't find the reply. How can I
> > arrange for  to step through the open tabs, one at a time,
> > from left to right. Or is there another key combination to do that?
> 
>   From the Pale Moon FAQ...
> https://www.palemoon.org/faq.shtml#Preference:_I_prefer_the_old_Ctrl-Tab

Oops! I should have thought to check there.

> > If you don't like the graphical preview pane for switching between
> > browser tabs, you can restore the method as also found in Firefox:
> > In the address bar, type about:config and press enter. This
> > opens the advanced configuration editor.  Find the parameter
> > browser.ctrlTab.previews and set it to false

Works like a charm. Thanks Walter.

> > Q 2:  What other package do I need installed to give me the navigation
> > symbols? I've attached a section of the window to show what I mean.
> 
>   First try x11-themes/hicolor-icon-theme and if that doesn't suffice
> try adwaita-icon-theme (which pulls in x11-themes/hicolor-icon-theme).
> Actually, you should already have them installed if you have gtk+(2 or
> 3).

Yes, I do have them both installed already.

> Is this the official Pale Moon, or an unofficial build?

It's www-client/palemoon-bin-27.7.1::palemoon. I don't know whether that's 
"official", because when I "layman -a palemoon" I'm told it's not an 
official overlay. Different officialdoms, I suppose.

I can't compile from source because of this (from the build log):

8 9:45.12 ../../build/unix/gold/ld: error: /var/tmp/portage/www-client/
palemoon-27.7.1/work/palemoon-27.7.1/o/toolkit/library/../../media/
libstagefright/Unified_cpp_media_libstagefright0.o: requires dynamic 
R_X86_64_PC32 reloc against '_Z13GetDemuxerLogv' which may overflow at 
runtime; recompile with -fPIC
8 9:45.12 ../../build/unix/gold/ld: error: read-only segment has dynamic 
relocations
8 9:45.12 /var/tmp/portage/www-client/palemoon-27.7.1/work/palemoon-27.7.1/
media/libstagefright/binding/MoofParser.cpp:728: error: undefined reference 
to 'GetDemuxerLog()'
8 9:45.12 /var/tmp/portage/www-client/palemoon-27.7.1/work/palemoon-27.7.1/
media/libstagefright/binding/MoofParser.cpp:735: error: undefined reference 
to 'GetDemuxerLog()'
8 9:45.12 /var/tmp/portage/www-client/palemoon-27.7.1/work/palemoon-27.7.1/
media/libstagefright/binding/MoofParser.cpp:591: error: undefined reference 
to 'GetDemuxerLog()'
8 9:45.12 /var/tmp/portage/www-client/palemoon-27.7.1/work/palemoon-27.7.1/
media/libstagefright/binding/MoofParser.cpp:599: error: undefined reference 
to 'GetDemuxerLog()'
8 9:45.12 collect2: error: ld returned 1 exit status

This is with gcc 4.9.4, and I get the same with gcc 6.4.0. I've only just 
noticed that about -fPIC; haven't all those problems been fixed by now?

-- 
Regards,
Peter.