Re: [gentoo-user] Failed builds of kbuild and cdrdao with "undefined reference to `__alloca'"

[tuxic]

On 02/12 11:31, Joerg Schilling wrote:
>  wrote:
> 
> > On 02/09 10:02, Andreas K. Huettel wrote:
> > > Am Sonntag, 4. Februar 2018, 15:03:28 CET schrieb tu...@posteo.de:
> > > > Hi,
> > > > 
> > > > I still have the problem of failed builds due to an
> > > > 'undefined reference to `__alloca''. I recompiled
> > > > gcc/glibc and I am using linux-4.15.1 (from kernel.org)
> > > > with linux-headers 4.15. .
> > > > 
> > > > Affected are (at least) cdrdao and kbuild.
> > > > 
> > > 
> > > What's your sys-libs/glibc ?!
> 
> alloca() is usually handled by the compiler, so if there is sucvh a problem, 
> this may be a result of incorrect include files that do not match the 
> compiler.
> 
> BTW: cdrdao is unmaintained since aprox. 10 years and did not get any change 
> since 8.5 years.
> 
> Jörg
> 
> -- 
>  EMail:jo...@schily.net(home) Jörg Schilling D-13353 
> Berlin
> joerg.schill...@fokus.fraunhofer.de (work) Blog: 
> http://schily.blogspot.com/
>  URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
> 

Hi Jörg,

what do you recommend to replace cdrdao?

Meino

[gentoo-user] Re: Vulnerability info in /sys

[Ian Zimmerman]

On 2018-02-12 19:24, Daniel Frey wrote:

> I've read online that there should be vulnerability info (Meltdown,
> Spectre) in /sys under /sys/devices/system/cpu/vulnerabilities but this
> doesn't exist on my PC.

> I've updated to gentoo-sources-4.9.76-r1, shouldn't this info be present?
> 
> $ uname -a
> Linux zatpc 4.9.76-gentoo-r1 #1 SMP Mon Feb 12 09:20:32 PST 2018 x86_64
> Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz GenuineIntel GNU/Linux

See the other threads: you need at least 4.9.79 for the /sys bits.

If you've enabled PTI at build time it's enabled, no need to do anything
else.

Later 4.9 kernels also contain patches for spectre (PTI is not relevant
there).

-- 
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.

[gentoo-user] Vulnerability info in /sys

[Daniel Frey]

I've read online that there should be vulnerability info (Meltdown,
Spectre) in /sys under /sys/devices/system/cpu/vulnerabilities but this
doesn't exist on my PC.

Another place is in /proc/cpuinfo, no info on meltdown/spectre in there
either.

Yet another place is in dmesg, (grep 'page tables isolation') nothing
there either.

I've updated to gentoo-sources-4.9.76-r1, shouldn't this info be present?

$ uname -a
Linux zatpc 4.9.76-gentoo-r1 #1 SMP Mon Feb 12 09:20:32 PST 2018 x86_64
Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz GenuineIntel GNU/Linux

$ zgrep PAGE_TABLE_ISO /proc/config.gz
CONFIG_PAGE_TABLE_ISOLATION=y

Or does the page table isolation need to be explicitly turned on?

Dan

Re: [gentoo-user] Re: Unlocking Plasma desktop in Gentoo without systemd

[Daniel Frey]

On 09/12/17 05:13, Michael Palimaka wrote:
> On 09/12/2017 05:04 AM, Daniel Frey wrote:
>> According to a comment in the bug, you can try to figure out which
>> session it is (ck-list-sessions) and look for the X11 display property
>> set. This will not work (or could be difficult) if you have several
>> users using KDE at the same time and can't tell the sessions apart.
>>
>> Once you figure that out, remember the session name and:
>>
>> # su -c 'dbus-send --system --print-reply \
>> --dest="org.freedesktop.ConsoleKit" \
>>  /org/freedesktop/ConsoleKit/ \
>> org.freedesktop.ConsoleKit.Session.Unlock'
>>
> 
> If there a nice way to wrap this up in a script I'd be interesting in
> shipping this for non-logind systems.
> 
> Another option is sys-auth/elogind, which provides the logind interface
> and tools (like loginctl) for non-systemd systems. This is what I've
> been testing with OpenRC for some time.
> 
> I read that ConsoleKit is also supporting the logind dbus interface now.
> This would in theory make it easy to create a tool to unlock the
> session, but I haven't had a chance to test it yet.
> 

Well, I forgot to disable my screen locker during an update and got bit
by this again. It's a pain typing it manually (especially when you run a
monitor in portrait mode.)

I had some time and put together a general-purpose bash script. A note
of warning, I'm not an expert at bash by any means, but I was able to
test this several ways as I haven't restarted my computer yet.

I'll attach it if someone else wants to try it out. It's simply called
ck-unlock-session.

Dan
#!/bin/sh

# This script is to make unlocking using OpenRC/Consolekit easier when the KDE 
Screenlocker breaks.
#
# Version: 0.1
# Date written: February 2, 2018
#
# Copyright (C) 2018 Daniel Frey
#
# This script is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This script is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
#
# Some notes:
#   -The switch processing/argument handling is very basic.
#   -This script assumes session names start with "Session" when listing
#sessions. This is settable via a variable.
#
# Possible actions:
#   -h : Show help screen
#   -l : List current consolekit sessions
#   -u : Unlock specified session (one parameter required - the session name)
#   -a : Attempt to unlock all sessions

# Return code documentation
#
#  0: Script executed normally
#  1: Root access is not present for script
#  2: No arguments passed
#  3: Multiple actions requested, can only do one at a time
#  4: Argument passed was not recognized
#  5: Multiple arguments passed for unlock single session, only one needed
#  6: The argument required for unlocksession() is missing (internal error)

# Return code constants
readonly ERR_NORMAL_OPERATION=0
readonly ERR_NO_ROOT=1
readonly ERR_NO_ARGS=2
readonly ERR_TOO_MANY_ACTIONS=3
readonly ERR_INVALID_ARGUMENTS=4
readonly ERR_TOO_MANY_ARGS=5
readonly ERR_INTERNAL_ARG_MISSING=6

# Action parameter constants
readonly ACTION_NONE=0
readonly ACTION_HELP=1
readonly ACTION_LIST=2
readonly ACTION_UNLOCKALL=3
readonly ACTION_UNLOCK=4

# This is what's used to look for a session via consolekit.
# By default, assume it is prefixed with "Session".
SESSION_SEARCH_PREFIX=Session

# Check to make sure script has root access, if not... abort now!
if [ $EUID -ne 0 ]; then
echo "This script must be run as root."
exit $ERR_NO_ROOT
fi

function showhelp () {
echo "`basename $0`: a script that helps unlock consolekit sessions

Usage: `basename $0` [action] [parameters]

Actions:
-l : list current sessions available for unlocking 

-u : unlock session specified as a parameter

-a : attempt to unlock all current sessions

-h : this screen

Parameters:
The -u parameter requires a session name to unlock, use -l to list
sessions.

Example:

To unlock a single session, use:
  `basename $0` -u Session1

No arguments will show this screen."
}

function listsessions() {
# Get a list of all sessions, and remove the full colon from the 
session name
ALLSESSIONS=`ck-list-sessions | grep -i ^$SESSION_SEARCH_PREFIX | rev | 
cut -c 2- | rev`

echo
echo "Sessions present on this machine, space-delineated:"
echo
echo $ALLSESSIONS
echo
echo
echo "Session detail (to help locate a specific session:"
ck-list-sessions | grep -A 2 -i ^$SESSION_SEARCH_PREFIX
}

function unlocksession () {
# This function expects one parameter set (the session to unlock.
# Make sure the parameter exists before continuing.
if 

[gentoo-user] Re: some spectre v1 code in 4.15.2

[Nikos Chantziaras]

On 13/02/18 03:31, Ian Zimmerman wrote:

On 2018-02-13 03:13, Nikos Chantziaras wrote:


Apparently, and contrary to what people (me included) wrote here in
the past, BPF JIT is the secure option, and the interpreter is the
insecure one.


Do you have a reference for this?  It sounds strange indeed.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=290af86629b25ffd1ed6232c4e9107da031705cb

"The BPF interpreter has been used as part of the spectre 2 attack 
CVE-2017-5715.

[...]
To make attacker job harder introduce BPF_JIT_ALWAYS_ON config
option that removes interpreter from the kernel in favor of JIT-only mode."

[gentoo-user] Re: some spectre v1 code in 4.15.2

[Ian Zimmerman]

On 2018-02-13 03:13, Nikos Chantziaras wrote:

> Apparently, and contrary to what people (me included) wrote here in
> the past, BPF JIT is the secure option, and the interpreter is the
> insecure one.

Do you have a reference for this?  It sounds strange indeed.

-- 
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.

[gentoo-user] Re: some spectre v1 code in 4.15.2

[Nikos Chantziaras]

On 12/02/18 11:51, Adam Carter wrote:

$ grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user 
pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full 
generic retpoline


One other thing that's landed, is an option to completely disable the 
BPF interpreter in the kernel and force BPF JIT. Apparently, and 
contrary to what people (me included) wrote here in the past, BPF JIT is 
the secure option, and the interpreter is the insecure one.


The option is CONFIG_BPF_JIT_ALWAYS_ON. The prompt for it only becomes 
available after enabling CONFIG_BPF_JIT.

Re: [gentoo-user] DRM error: couldn't read SADs

[Jack]

On 2018.02.12 19:57, Peter Humphrey wrote:

On Sunday, 11 February 2018 05:41:28 GMT 80x24 wrote:
> On Sun, Feb 11, 2018 at 12:47 AM,
> Peter Humphrey  wrote:
> > [drm:dce_v11_0_afmt_setmode] *ERROR* Couldn't read SADs: 0
> > [...]
> > traps: plugin-containe[6833] general protection ip:7f0a2e1711b1
> > sp:7fff6f64dc30 error:0 in ld-2.25.so[7f0a2e15c000+23000]
> >
> > What is a SAD (other than a seasonal affective disorder)? That  
library
> > comes from glibc, of which I've had 5 versions or revisions in  
that time

> /**
>  * drm_edid_to_sad - extracts SADs from EDID
>  * @edid: EDID to parse
>  * @sads: pointer that will be set to the extracted SADs
>  *
>  * Looks for CEA EDID block and extracts SADs (Short Audio  
Descriptors)

> fr$
> *
>  * Note: The returned pointer needs to be freed using kfree().
>  *
>  * Return: The number of found SADs or negative number on error.
>  */
>
> Considering the term ``EDID'' and some audio related words, I think
> it's reading some info from your monitor.

Hmm. Interesting. Looks like I'll have to revise my screen setup.  
It's a
Samsung LED device with HDMI input. This box outputs HDMI too, but  
the other
boxes I use it on output DVI, so by piecemeal development I've ended  
up with

a four-port DVI switch, all connected with adapter cables.

It seems likely that EDID is getting lost, and I may now also have a  
reason
for the washed-out appearance of the screen. Modern websites with  
their pale
colours are hard to read. Even the green of KMail's quoted text is  
hard.


The other boxes I mentioned can also output VGA, and the screen can  
accept
VGA too and switch between inputs. So I just need a two-port VGA  
switch and
some cables. I've not long since thrown out all the old VGA stuff -  
damn! I

knew I should never throw anything away.


It's been a long time since I've needed to do it, and it was also due  
to a (cheap?) KVM switch, but I think there are two things that might  
help.  First, if you boot the PC with that monitor connected, it might  
actually read the EDID data.  Even if not, if you can capture it (one  
time use of a straigt DVI or VGA cable?) you can save it tp a file  
using x11-misc/read-edid, and then there is a way to get kernel/X to  
read that EDID file at startup instead of trying and failing to get it  
directly from the monitor.  If you can't find a reference, I'll dig and  
try to figure out if it's kernel paramater or xorg.conf that you need  
to mess with.


Jack

Re: [gentoo-user] DRM error: couldn't read SADs

[Peter Humphrey]

On Sunday, 11 February 2018 05:41:28 GMT 80x24 wrote:
> On Sun, Feb 11, 2018 at 12:47 AM,
> Peter Humphrey  wrote:
> > [drm:dce_v11_0_afmt_setmode] *ERROR* Couldn't read SADs: 0
> > [...]
> > traps: plugin-containe[6833] general protection ip:7f0a2e1711b1
> > sp:7fff6f64dc30 error:0 in ld-2.25.so[7f0a2e15c000+23000]
> > 
> > What is a SAD (other than a seasonal affective disorder)? That library
> > comes from glibc, of which I've had 5 versions or revisions in that time
> /**
>  * drm_edid_to_sad - extracts SADs from EDID
>  * @edid: EDID to parse
>  * @sads: pointer that will be set to the extracted SADs
>  *
>  * Looks for CEA EDID block and extracts SADs (Short Audio Descriptors)
> fr$
> *
>  * Note: The returned pointer needs to be freed using kfree().
>  *
>  * Return: The number of found SADs or negative number on error.
>  */
> 
> Considering the term ``EDID'' and some audio related words, I think
> it's reading some info from your monitor.

Hmm. Interesting. Looks like I'll have to revise my screen setup. It's a  
Samsung LED device with HDMI input. This box outputs HDMI too, but the other 
boxes I use it on output DVI, so by piecemeal development I've ended up with 
a four-port DVI switch, all connected with adapter cables.

It seems likely that EDID is getting lost, and I may now also have a reason 
for the washed-out appearance of the screen. Modern websites with their pale 
colours are hard to read. Even the green of KMail's quoted text is hard.

The other boxes I mentioned can also output VGA, and the screen can accept 
VGA too and switch between inputs. So I just need a two-port VGA switch and 
some cables. I've not long since thrown out all the old VGA stuff - damn! I 
knew I should never throw anything away.

Thanks for your help.

-- 
Regards,
Peter.

Re: [gentoo-user] Grub2 boot problem

[mad.scientist.at.large]

you need to include the punctuation, specifically the ":"s, which usually are a 
"-", mac addresses use the ":" but unless the syntax has changed/broadened you 
have to have the "-" for seperating the fields in a uuid.  The punctuation is  
part of the syntax (besides breaking the uuid into sections which makes it 
easier to copy/verify).   for data overload see 
 and the 
associated links.


mad.scientist.at.large (a good madscientist)
--
God bless the rich, the greedy and the corrupt politicians they have put into 
office.   God bless them for helping me do the right thing by giving the rich 
my little pile of cash.  After all, the rich know what to do with money.


12. Feb 2018 16:16 by gen...@rnd.se:
>snip

> I've got a fresh Gentoo installation that does not boot. I just end up in
> the Grub2 shell.
>
> Almost, mdadm says 46488b25:9685a3b9:c52b7449:d592dc80
>
>> Does "set" in the grub shell display
>> "prefix=(mduuid/46488b259685a3b9c52b7449d592dc80)/grub" and
>> "root=(mduuid/46488b259685a3b9c52b7449d592dc80)"?
>
> Yes, I messed up the prefix=-line when retyping it.
>
>> Does "grub-probe -t drive -d /dev/md0" output "(mduuid/...)" or
>> "(md/0)" or "(md0)"?
>
> It ouputs "(mduuid/46488b259685a3b9c52b7449d592dc80)"

Re: [gentoo-user] Grub2 boot problem

[Magnus Johansson]

 I've got a fresh Gentoo installation that does not boot. I just end up in
 the Grub2 shell.

 However when there if I do 'set root=(md/0)' and 'configfile 
 /grub/grub.cfg'
 I do get to the Grub2 menu where Gentoo boots just fine.

 /boot and / are both on mdadm devices.

 I've tried re-running grub-mkconfig and grub-install several times without
 luck.

 I've added domdadm to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

 Drives sda/sdb use GPT disklabels and have 20M BIOS boot partitions first.
>>>
>>> To which device are you installing grub?
>>>
>>> Check what "core.img" prefix and modules grub-install is using with
>>>
>>> grub-install --debug $your_device 2>&1 | grep grub-mkimage
>>>
>>> [I hit a similar problem with mdadm 6 or 7 years ago and had to create
>>> a custom "core.img" to boot normally. You might have to do the same
>>> but i would've thought that this problem's been solved. I haven't
>>> encountered it since.]
>>
>> I install grub to devices sda and sdb in the hope I can boot from both/either
>>
>> m / # grub-install --debug /dev/sda 2>&1 | grep grub-mkimage
>> grub-install: info: grub-mkimage --directory '/usr/lib/grub/i386-pc'
>> --prefix '(mduuid/46488b259685a3b9c52b7449d592dc80)/grub' --output
>> '/boot/grub/i386-pc/core.img' --format 'i386-pc' --compression 'auto'
>> 'ext2' 'part_gpt' 'part_gpt' 'diskfilter' 'mdraid1x' 'biosdisk'
>> m / #
>
> [ I assume that "46488b259685a3b9c52b7449d592dc80" is the UUID that's
> displayed as "UUID" or "Array UUID" when you use "mdadm -D ..." or
> "mdadm -E ..." respectively ]

Almost, mdadm says 46488b25:9685a3b9:c52b7449:d592dc80

> Does "set" in the grub shell display
> "prefix=(mduuid/46488b259685a3b9c52b7449d592dc80)/grub" and
> "root=(mduuid/46488b259685a3b9c52b7449d592dc80)"?

Yes, I messed up the prefix=-line when retyping it.

> Does "grub-probe -t drive -d /dev/md0" output "(mduuid/...)" or
> "(md/0)" or "(md0)"?

It ouputs "(mduuid/46488b259685a3b9c52b7449d592dc80)"

Re: [gentoo-user] Multi monitor in KDE - remember window placement as default for all windows?

[Daniel Frey]

On 02/12/18 01:20, Neil Bothwick wrote:
> On Sun, 11 Feb 2018 20:04:27 -0800, Daniel Frey wrote:
> 
>> After a little bit of fiddling around, I found out you can get an 
>> application window to remember its size and position (which is great,
>> at least the option is there.)
>>
>> Not so nice is that I have to tell every new window I open (well, the 
>> ones that open all over the place) to remember their settings.
>>
>> Is there a way to make this a global change for all windows? This is 
>> getting irritating.
> 
> In System Settings -> Display and Monitor you can set the primary
> display. Windows without a saved preference should be opened on this
> display. Is that what you need?
> 
> 

Yes, that's better. I think it was looking random before as it was
trying to open new windows on the portrait monitor and not fitting... so
it would spread across both.

Dan

Re: [gentoo-user] Grub2 boot problem

[Tom H]

On Sat, Feb 10, 2018 at 10:28 AM, Magnus Johansson  wrote:
> 2018-02-07 18:50 GMT+01:00 Steven Lembark :
>> On Mon, 5 Feb 2018 22:00:39 +0100
>> Magnus Johansson  wrote:
>>
>> From my grub.cfg:
>>
>> insmod gzio
>> insmod part_msdos
>> insmod diskfilter
>> insmod mdraid1x
>> insmod raid5rec
>> insmod lvm
>> insmod xfs
>>
>> Sanity check that you have all of the necessary modules installed
>> (e.g., "mdraid*" "raid5rec").
>
> How do you mean? Since 'set root' and 'configfile' makes it boot I'd
> assume the modules are there?
>
> I ran 'set' from grub2 shell and
>
> cmdpath=(hd0)
> prefix=(mduuid/)/root=grub
> root=mduuid/
>
> Where  is the correct UUID.
>
> Which looks ok?

The "prefix=" line isn't OK, unless you've mistyped it.

Re: [gentoo-user] Grub2 boot problem

[Tom H]

On Mon, Feb 5, 2018 at 4:00 PM, Magnus Johansson  wrote:
>>>
>>> I've got a fresh Gentoo installation that does not boot. I just end up in
>>> the Grub2 shell.
>>>
>>> However when there if I do 'set root=(md/0)' and 'configfile /grub/grub.cfg'
>>> I do get to the Grub2 menu where Gentoo boots just fine.
>>>
>>> /boot and / are both on mdadm devices.
>>>
>>> I've tried re-running grub-mkconfig and grub-install several times without
>>> luck.
>>>
>>> I've added domdadm to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.
>>>
>>> Drives sda/sdb use GPT disklabels and have 20M BIOS boot partitions first.
>>
>> To which device are you installing grub?
>>
>> Check what "core.img" prefix and modules grub-install is using with
>>
>> grub-install --debug $your_device 2>&1 | grep grub-mkimage
>>
>> [I hit a similar problem with mdadm 6 or 7 years ago and had to create
>> a custom "core.img" to boot normally. You might have to do the same
>> but i would've thought that this problem's been solved. I haven't
>> encountered it since.]
>
> I install grub to devices sda and sdb in the hope I can boot from both/either
>
> m / # grub-install --debug /dev/sda 2>&1 | grep grub-mkimage
> grub-install: info: grub-mkimage --directory '/usr/lib/grub/i386-pc'
> --prefix '(mduuid/46488b259685a3b9c52b7449d592dc80)/grub' --output
> '/boot/grub/i386-pc/core.img' --format 'i386-pc' --compression 'auto'
> 'ext2' 'part_gpt' 'part_gpt' 'diskfilter' 'mdraid1x' 'biosdisk'
> m / #

[ I assume that "46488b259685a3b9c52b7449d592dc80" is the UUID that's
displayed as "UUID" or "Array UUID" when you use "mdadm -D ..." or
"mdadm -E ..." respectively ]

Does "set" in the grub shell display
"prefix=(mduuid/46488b259685a3b9c52b7449d592dc80)/grub" and
"root=(mduuid/46488b259685a3b9c52b7449d592dc80)"?

Does "grub-probe -t drive -d /dev/md0" output "(mduuid/...)" or
"(md/0)" or "(md0)"?

Re: [gentoo-user] Failed builds of kbuild and cdrdao with "undefined reference to `__alloca'"

[Joerg Schilling]

 wrote:

> On 02/09 10:02, Andreas K. Huettel wrote:
> > Am Sonntag, 4. Februar 2018, 15:03:28 CET schrieb tu...@posteo.de:
> > > Hi,
> > > 
> > > I still have the problem of failed builds due to an
> > > 'undefined reference to `__alloca''. I recompiled
> > > gcc/glibc and I am using linux-4.15.1 (from kernel.org)
> > > with linux-headers 4.15. .
> > > 
> > > Affected are (at least) cdrdao and kbuild.
> > > 
> > 
> > What's your sys-libs/glibc ?!

alloca() is usually handled by the compiler, so if there is sucvh a problem, 
this may be a result of incorrect include files that do not match the compiler.

BTW: cdrdao is unmaintained since aprox. 10 years and did not get any change 
since 8.5 years.

Jörg

-- 
 EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin
joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'

[gentoo-user] some spectre v1 code in 4.15.2

[Adam Carter]

$ grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic
retpoline

Re: [gentoo-user] Multi monitor in KDE - remember window placement as default for all windows?

[Neil Bothwick]

On Sun, 11 Feb 2018 20:04:27 -0800, Daniel Frey wrote:

> After a little bit of fiddling around, I found out you can get an 
> application window to remember its size and position (which is great,
> at least the option is there.)
> 
> Not so nice is that I have to tell every new window I open (well, the 
> ones that open all over the place) to remember their settings.
> 
> Is there a way to make this a global change for all windows? This is 
> getting irritating.

In System Settings -> Display and Monitor you can set the primary
display. Windows without a saved preference should be opened on this
display. Is that what you need?


-- 
Neil Bothwick

Sometimes too much to drink is not enough.


pgpEffa2X7073.pgp
Description: OpenPGP digital signature