Re: [arch-general] Screen lock stopped working

2016-09-18 Thread David Rosenstrauch 

On 09/18/2016 10:45 AM, Ralf Mardorf wrote:

On Sun, 18 Sep 2016 10:23:41 -0400, David Rosenstrauch wrote:

On 09/18/2016 01:22 AM, Ralf Mardorf wrote:

On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:

I'm running XFCE desktop btw.


On Arch Linux using Xfce not necessarily explains what screen lock /
screensaver you are using.



xflock4/xscreensaver


Ok...

[rocketmouse@archlinux ~]$ pacman -Si xfce4-session | grep lock
  xscreensaver: for locking screen with xflock4
  gnome-screensaver: for locking screen with xflock4
  xlockmore: for locking screen with xflock4
  slock: for locking screen with xflock4

https://wiki.archlinux.org/index.php/xfce#Lock_the_screen

... and from where did you get the information that xscreensaver is
used? Is nothing lese installed?

I don't know how to find out, I'm neither using a screensaver, nor do I
use Xfce4 anymore.

Perhaps

xfconf-query -l
xfconf-query -c xfce4-power-manager -lv

?

Regards,
Ralf




Well I only have xscreensaver installed, not gnome-screensaver, so I'd 
think it must be using that.


Thanks,

DR

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Dutch Ingraham 
On Sun, Sep 18, 2016 at 10:14:35AM -0500, Doug Newgard wrote:
> On Sun, 18 Sep 2016 09:47:57 -0500
> Dutch Ingraham  wrote:
> 
> > On Sun, Sep 18, 2016 at 09:23:01AM -0500, Doug Newgard wrote:
> > > On Sun, 18 Sep 2016 09:11:45 -0500
> > > Dutch Ingraham  wrote:
> > >   
> > > > Hello all:
> > > > 
> > > > TL;DR: One Arch installation will allow redirecting startx's stderr to
> > > > a file, one won't.  What is the difference between systems?
> > > >   
> > > 
> > > Is X running as root or as the user (rootless)? This can change based on
> > > configuration and on drivers used.  
> > 
> > Excellent question - how is this conclusively determined?  Note I have 
> > taken no
> > explicit action either way, i.e., to enable rootlessness or not.
> > 
> > Looking at the xorg wiki, it appears as though 3 conditions are necessary 
> > for
> > running "rootless":
> > 
> > 1. systemd >= 216; OK, I'm at 231 on both machines;
> > 2. start X via xinit; OK, I'm using xinit through startx, not a display 
> > manager;
> > 3. if I can summarize, if using a proprietary display driver, such as 
> > Catalyst
> > or Nvidia, need to take an extra step to run rootless; *this may be the 
> > issue.*
> > 
> > On the machine where redirection works, I am using the nvidia proprietary
> > driver; on the machine where the error occurs, I am using the xf-video-ati
> > driver.
> > 
> > So, unless I have step 3 above backwards (which is entirely possible), the
> > question is how to redirect stderr when running rootless? (If I am in fact
> > misunderstanding, please explain so a moron like me can understand!)
> > 
> > Thanks for your help.
> 
> rooted vs rootless does look like one difference between the systems. Next, I
> would enable rooted X on the problem machine and see if it works. If it does,
> we know we've narrowed down the issue.

Bingo.  Created the Xwrapper.config file with the line "needs_root_rights = yes"
and I can now startx and redirect stderr.

To get back the rootless operation, I then backed that file out and appended, to
~/.xserverrc, "vt$XDG_VTNR -keeptty."  This seems to be working at this point.
(Note I had, some days ago, appended the "vt$XDG_VTNR" to the .xserverrc, but
that alone doesn't work.  Need the -keeptty.)

Thanks for your help.

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Doug Newgard 
On Sun, 18 Sep 2016 09:47:57 -0500
Dutch Ingraham  wrote:

> On Sun, Sep 18, 2016 at 09:23:01AM -0500, Doug Newgard wrote:
> > On Sun, 18 Sep 2016 09:11:45 -0500
> > Dutch Ingraham  wrote:
> >   
> > > Hello all:
> > > 
> > > TL;DR: One Arch installation will allow redirecting startx's stderr to
> > > a file, one won't.  What is the difference between systems?
> > >   
> > 
> > Is X running as root or as the user (rootless)? This can change based on
> > configuration and on drivers used.  
> 
> Excellent question - how is this conclusively determined?  Note I have taken 
> no
> explicit action either way, i.e., to enable rootlessness or not.
> 
> Looking at the xorg wiki, it appears as though 3 conditions are necessary for
> running "rootless":
> 
> 1. systemd >= 216; OK, I'm at 231 on both machines;
> 2. start X via xinit; OK, I'm using xinit through startx, not a display 
> manager;
> 3. if I can summarize, if using a proprietary display driver, such as Catalyst
> or Nvidia, need to take an extra step to run rootless; *this may be the 
> issue.*
> 
> On the machine where redirection works, I am using the nvidia proprietary
> driver; on the machine where the error occurs, I am using the xf-video-ati
> driver.
> 
> So, unless I have step 3 above backwards (which is entirely possible), the
> question is how to redirect stderr when running rootless? (If I am in fact
> misunderstanding, please explain so a moron like me can understand!)
> 
> Thanks for your help.

rooted vs rootless does look like one difference between the systems. Next, I
would enable rooted X on the problem machine and see if it works. If it does,
we know we've narrowed down the issue.

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Dutch Ingraham 
On Sun, Sep 18, 2016 at 04:29:47PM +0200, Ralf Mardorf wrote:
> On Sun, 18 Sep 2016 16:24:12 +0200, Ralf Mardorf wrote:
> >On Sun, 18 Sep 2016 09:11:45 -0500, Dutch Ingraham wrote:
> >>TL;DR: One Arch installation will allow redirecting startx's stderr to
> >>a file, one won't.  What is the difference between systems?  
> >
> >Hi,
> >
> >what actually was too long to read?
> >
> >Did you for testing purpose install a display manger, e.g. lightdm?
> >Does lightdm or any other DM also not provide the wanted output? If so,
> >what does the display manager's log file in /var provide?
> 
> Pardon, your mal was TL;DR, my bad, ok, .xsession-errors is used, here
> is output, however, what is mentioned by "Please also check the log file
> at "/home/dutch/.local/share/xorg/Xorg.0.log" for additional
> information"?

Sorry, I should have included information on that; there are no errors at all
noted in the xorg.log.

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Dutch Ingraham 
On Sun, Sep 18, 2016 at 04:24:12PM +0200, Ralf Mardorf wrote:
> On Sun, 18 Sep 2016 09:11:45 -0500, Dutch Ingraham wrote:
> >TL;DR: One Arch installation will allow redirecting startx's stderr to
> >a file, one won't.  What is the difference between systems?
> 
> Hi,
> 
> what actually was too long to read?
> 
> Did you for testing purpose install a display manger, e.g. lightdm?
> Does lightdm or any other DM also not provide the wanted output? If so,
> what does the display manager's log file in /var provide?
> 
> Regards,
> Ralf

Thanks for your response.  I do have sddm installed, as it came along with the
Plasma goo, but it is disabled as I never use a display manager.  I could enable
it for testing purposes, though, if other testing does not pan out (see other
responses in this thread.)

Thanks again.

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Dutch Ingraham 
On Sun, Sep 18, 2016 at 09:23:01AM -0500, Doug Newgard wrote:
> On Sun, 18 Sep 2016 09:11:45 -0500
> Dutch Ingraham  wrote:
> 
> > Hello all:
> > 
> > TL;DR: One Arch installation will allow redirecting startx's stderr to
> > a file, one won't.  What is the difference between systems?
> > 
> 
> Is X running as root or as the user (rootless)? This can change based on
> configuration and on drivers used.

Excellent question - how is this conclusively determined?  Note I have taken no
explicit action either way, i.e., to enable rootlessness or not.

Looking at the xorg wiki, it appears as though 3 conditions are necessary for
running "rootless":

1. systemd >= 216; OK, I'm at 231 on both machines;
2. start X via xinit; OK, I'm using xinit through startx, not a display manager;
3. if I can summarize, if using a proprietary display driver, such as Catalyst
or Nvidia, need to take an extra step to run rootless; *this may be the issue.*

On the machine where redirection works, I am using the nvidia proprietary
driver; on the machine where the error occurs, I am using the xf-video-ati
driver.

So, unless I have step 3 above backwards (which is entirely possible), the
question is how to redirect stderr when running rootless? (If I am in fact
misunderstanding, please explain so a moron like me can understand!)

Thanks for your help.

Re: [arch-general] Screen lock stopped working

2016-09-18 Thread Ralf Mardorf 
On Sun, 18 Sep 2016 10:23:41 -0400, David Rosenstrauch wrote:
>On 09/18/2016 01:22 AM, Ralf Mardorf wrote:
>> On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:  
>>> I'm running XFCE desktop btw.  
>>
>> On Arch Linux using Xfce not necessarily explains what screen lock /
>> screensaver you are using.
>>  
>
>xflock4/xscreensaver

Ok...

[rocketmouse@archlinux ~]$ pacman -Si xfce4-session | grep lock
  xscreensaver: for locking screen with xflock4
  gnome-screensaver: for locking screen with xflock4
  xlockmore: for locking screen with xflock4
  slock: for locking screen with xflock4

https://wiki.archlinux.org/index.php/xfce#Lock_the_screen

... and from where did you get the information that xscreensaver is
used? Is nothing lese installed?

I don't know how to find out, I'm neither using a screensaver, nor do I
use Xfce4 anymore.

Perhaps

xfconf-query -l
xfconf-query -c xfce4-power-manager -lv

?

Regards,
Ralf

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Ralf Mardorf 
On Sun, 18 Sep 2016 16:24:12 +0200, Ralf Mardorf wrote:
>On Sun, 18 Sep 2016 09:11:45 -0500, Dutch Ingraham wrote:
>>TL;DR: One Arch installation will allow redirecting startx's stderr to
>>a file, one won't.  What is the difference between systems?  
>
>Hi,
>
>what actually was too long to read?
>
>Did you for testing purpose install a display manger, e.g. lightdm?
>Does lightdm or any other DM also not provide the wanted output? If so,
>what does the display manager's log file in /var provide?

Pardon, your mal was TL;DR, my bad, ok, .xsession-errors is used, here
is output, however, what is mentioned by "Please also check the log file
at "/home/dutch/.local/share/xorg/Xorg.0.log" for additional
information"?

-- 
Death of ROXTerm
https://sourceforge.net/p/roxterm/discussion/422638/thread/60da6975/

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Ralf Mardorf 
On Sun, 18 Sep 2016 09:11:45 -0500, Dutch Ingraham wrote:
>TL;DR: One Arch installation will allow redirecting startx's stderr to
>a file, one won't.  What is the difference between systems?

Hi,

what actually was too long to read?

Did you for testing purpose install a display manger, e.g. lightdm?
Does lightdm or any other DM also not provide the wanted output? If so,
what does the display manager's log file in /var provide?

Regards,
Ralf

Re: [arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Doug Newgard 
On Sun, 18 Sep 2016 09:11:45 -0500
Dutch Ingraham  wrote:

> Hello all:
> 
> TL;DR: One Arch installation will allow redirecting startx's stderr to
> a file, one won't.  What is the difference between systems?
> 

Is X running as root or as the user (rootless)? This can change based on
configuration and on drivers used.

Re: [arch-general] Screen lock stopped working

2016-09-18 Thread David Rosenstrauch 

On 09/18/2016 01:22 AM, Ralf Mardorf wrote:

On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:

I'm running XFCE desktop btw.


On Arch Linux using Xfce not necessarily explains what screen lock /
screensaver you are using.



xflock4/xscreensaver

[arch-general] .xsession-errors - can't startx with that file

2016-09-18 Thread Dutch Ingraham 
Hello all:

TL;DR: One Arch installation will allow redirecting startx's stderr to
a file, one won't.  What is the difference between systems?

I am having an issue with logging xsession errors.  Specifically, if I
create an .xsession-errors file in /home/user, then startx with
< /home/user/.xsession-errors>>, startx will write to the
file, but otherwise error-out and not actually start X.  The error, in
its entirety, is:

"X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.5.4-1-ARCH x86_64
Current Operating System: Linux archlinux 4.7.4-1-ARCH #1 SMP PREEMPT
Thu Sep 15 15:24:29 CEST 2016 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux
root=UUID=763598c6-08b4-44d9-9b21-d4dbd558b107 rw
Build Date: 19 July 2016  05:54:24PM

Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/dutch/.local/share/xorg/Xorg.0.log", Time: Sat Sep
17 20:01:10 2016
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
(EE)
(EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
(EE) Please also check the log file at
"/home/dutch/.local/share/xorg/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error"

For the correctness of the specific incantation
< /home/user/.xsession-errors>>, see these [1][2] threads.  In
addition, that command works on any number of other distros (Fedora,
Gentoo, etc., and even OpenBSD).

But here is the real kicker - I have another computer with a very
similar Arch installation, i.e., x86_64, fully up-to-date, "full" KDE
and other window managers installed, using identical (actually copied
from machine-to-machine) .xinitrc files.  The above error only happens
on one machine, and happens regardless of whether I am trying to start
Plasma or just DWM, Awesome, i3, or whatever.

Searching for that specific error does return a few hits [3][4], but none of
those issues/remedies are similar to mine.

Any ideas on how I can determine the differences between the two Arch
installations that are causing only one to error-out when redirecting
stderr to a file?

[1] https://bbs.archlinux.org/viewtopic.php?id=143068
[2] https://www.linuxquestions.org/questions/slackware-14/where-is-~-
xsession-errors-log-867498/
[3] https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219
[4] https://bbs.archlinux.org/viewtopic.php?id=192329

Re: [arch-general] [arch-dev-public] i686 and SSE2

2016-09-18 Thread Jayesh Badwaik 
On Sunday, 18 September 2016 07:53:56 CEST Doug Newgard wrote:
> This thread is split between arch-general and arch-dev-public

Ohh, my bad. Did not properly read the headers. Thank You. 
-- 
Cheers
Jayesh Badwaik

signature.asc
Description: This is a digitally signed message part.

Re: [arch-general] [arch-dev-public] i686 and SSE2

2016-09-18 Thread Doug Newgard 
On Sun, 18 Sep 2016 14:50:09 +0200
Jayesh Badwaik  wrote:

> On Saturday, 17 September 2016 15:10:48 CEST LoneVVolf wrote:
> > On Fri, 2016-09-16 at 21:44 +0200, Bartłomiej Piotrowski wrote:  
> >  > Actually, why don't raise the bar higher? SSE2 has been introduced in
> >  > 2001 – that's 15 years to upgrade one's hardware and given my sad
> >  > experiences with computers, I find it hard to believe anyone has that
> >  > old PC that happens to run Arch.
> >  >   
> 
> I did not receive the above Bartlomiej's mail from the Arch Mailing List or 
> even the thread starter. Was it a private mail? I need to know because 
> otherwise it is getting rejected by my mail provider and I need to know what? 
> 

This thread is split between arch-general and arch-dev-public

Re: [arch-general] Screen lock stopped working

2016-09-18 Thread Eric Blau 
On Sun, Sep 18, 2016 at 1:22 AM, Ralf Mardorf 
wrote:

> On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:
> >I'm running XFCE desktop btw.
>
> On Arch Linux using Xfce not necessarily explains what screen lock /
> screensaver you are using.
>

Personally, I noticed that using xscreensaver, the screen locks but never
enters standby, suspend, or off DPMS power saving modes. If I run "xset
dpms force off" the monitor immediately powers off and comes back on when I
hit a key or move the mouse. Also, xautolock is failing to detect
inactivity and suspend my computer as I have it configured to do.

This happened since upgrading from linux 4.6.4 to 4.7.2 and continues to
occur with 4.7.4. I've noticed this on two separate computers, one running
Intel graphics and the other running the nvidia driver.

The version of xscreensaver has been unchanged for me at 5.35 since 1 July.

-Eric

Re: [arch-general] [arch-dev-public] i686 and SSE2

2016-09-18 Thread Jayesh Badwaik 
On Saturday, 17 September 2016 15:10:48 CEST LoneVVolf wrote:
> On Fri, 2016-09-16 at 21:44 +0200, Bartłomiej Piotrowski wrote:
>  > Actually, why don't raise the bar higher? SSE2 has been introduced in
>  > 2001 – that's 15 years to upgrade one's hardware and given my sad
>  > experiences with computers, I find it hard to believe anyone has that
>  > old PC that happens to run Arch.
>  > 

I did not receive the above Bartlomiej's mail from the Arch Mailing List or 
even the thread starter. Was it a private mail? I need to know because 
otherwise it is getting rejected by my mail provider and I need to know what? 

-- 
Cheers
Jayesh Badwaik

signature.asc
Description: This is a digitally signed message part.

Re: [arch-general] [arch-dev-public] i686 and SSE2

2016-09-18 Thread Mauro Santos via arch-general 
I'm not sure enforcing sse3 or later for AMD64 hardware is the best
course of action.

> egrep "^model name|^flags" /proc/cpuinfo
model name  : AMD Athlon(tm) 64 Processor 3000+
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm
3dnowext 3dnow rep_good nopl eagerfpu pni lahf_lm 3dnowprefetch vmmcall

This machine is still able to run Arch just fine, and has saved the day
when the laptop I used day to day broke down. As others have said, AMD
cpus might not have sse4 unless they are quite recent.

Requiring sse2 might be a reasonable cutoff, but I'm sure there will be
people still using older machines that will complain if sse2 is
mandatory, as I can reasonably see late pentium 3 machines still being
usable for office, email or light browsing applications.

-- 
Mauro Santos

Re: [arch-general] pkgstats api

2016-09-18 Thread Pierre Schmitz 

On 18.09.2016 13:14, Chris Stryczynski wrote:

Apologies I sent this through yesterday but without any subject so not
sure if it gets picked up.

I was wondering if there is an API / JSON endpoint for pkgstats?
Saves me having to scrape the page! I'm interested to build a packages
/ aur frontend.


Unfortunately there is no API atm.

--
Pierre Schmitz, https://pierre-schmitz.com

[arch-general] pkgstats api

2016-09-18 Thread Chris Stryczynski 
Apologies I sent this through yesterday but without any subject so not 
sure if it gets picked up.


I was wondering if there is an API / JSON endpoint for pkgstats?
Saves me having to scrape the page! I'm interested to build a packages / 
aur frontend.

Re: [arch-general] [arch-dev-public] i686 and SSE2

2016-09-18 Thread Martin Kühne via arch-general 
It would probably also give more arguments/hardware in need of a
retro-cpu archlinux variant/project which I'd like to see and would
help out with. Which in turn might be a better alternative for my
Geode as well.
Just my 2¢ to this.

cheers!
mar77i

Re: [arch-general] [arch-dev-public] i686 and SSE2

2016-09-18 Thread Martin Kühne via arch-general 
...I'm all for making arch work well for the hardware it runs well on,
and I don't think expecting SSE2 is too bleeding edge wrt hardware
constraints. There are other distros that work well on cpus that
aren't up to par with arch's needs. I started using gentoo on my
pcengines board due to already existing performance concerns for its
amd geode/i[45]86 cpu.

cheers!
mar77i

Re: [arch-general] [arch-dev-public] i686 and SSE2

2016-09-18 Thread Ralf Mardorf 
>On Fri, 2016-09-16 at 21:44 +0200, Bartłomiej Piotrowski wrote:
> > For the same reason I would not complain about requiring SSE4
> > instructions for amd64.

So you recommend to drop good hardware, to pollute our environment, to
waste rare earth elements and things like this?

[rocketmouse@archlinux ~]$ sudo hwinfo --cpu | head -8
01: None 00.0: 10103 CPU
  [Created at cpu.457]
  Unique ID: rdCR.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: X86-64
  Vendor: "AuthenticAMD"
  Model: 15.107.2 "AMD Athlon(tm) X2 Dual Core Processor BE-2350"
  Features: 
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,ht,syscall,nx,mmxext,fxsr_opt,rdtscp,lm,3dnowext,3dnow,rep_good,nopl,extd_apicid,eagerfpu,pni,cx16,lahf_lm,cmp_legacy,svm,extapic,cr8_legacy,3dnowprefetch,vmmcall,lbrv