LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-14-2014, 10:22 PM   #1
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
xlock -mode nose gives sigsev 11 under fvwm2


I find a consistent error running: xlock -mode nose
under the fvwm2 windows manager.

I starts up ok and the little guy with the nose walks around, but then
it returns to X with a signal 11 error...

Under OpenBSD, the little guy walks around and then a box with a fortune is displayed. Since the fortune is never displayed under Slackware, I suspect that this is the area of the problem.

Does anyone else have this problem?
 
Old 02-15-2014, 09:44 AM   #2
jmccue
Member
 
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 800
Blog Entries: 1

Rep: Reputation: 400Reputation: 400Reputation: 400Reputation: 400Reputation: 400
No issues here under fvwm2. Try this command as a test to see what happens
Code:
/usr/libexec/xscreensaver/noseguy
For a shot in the dark, rename ~/.xscreensaver to something and test. Doubt it will help with xlock but you never know.

BTW, noseguy (nose) is cool

EDIT -- do you have package bsd-games installed ? xscreensaver needs fortune for noseguy and I suspect the same is true for xlock

Last edited by jmccue; 02-15-2014 at 09:48 AM. Reason: ask about fortune
 
1 members found this post helpful.
Old 02-15-2014, 10:00 AM   #3
lems
Member
 
Registered: May 2004
Distribution: BSD
Posts: 269

Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by comet.berkeley View Post
Does anyone else have this problem?
Yes, same problem using ctwm. I noticed that when I compiled xlockmore with the options of OpenBSD[1], it still exited, but did not print
Code:
Access control list restored.
xlock: caught signal 11 while running nose mode (uid 1000).
anymore.

I also get
Code:
Could not create FontSet -*-fixed-medium-r-*-*-14-*-*-*-*-*-*,-*-*-medium-r-normal--14-*
but I had no luck using the various -*font* switches.

Sorry for not being of much help.

[1]: http://www.openbsd.org/cgi-bin/cvswe...e=text%2Fplain

Last edited by lems; 02-15-2014 at 01:14 PM. Reason: typo
 
1 members found this post helpful.
Old 02-15-2014, 02:31 PM   #4
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by jmccue View Post
No issues here under fvwm2. Try this command as a test to see what happens
Code:
/usr/libexec/xscreensaver/noseguy
For a shot in the dark, rename ~/.xscreensaver to something and test. Doubt it will help with xlock but you never know.

BTW, noseguy (nose) is cool

EDIT -- do you have package bsd-games installed ? xscreensaver needs fortune for noseguy and I suspect the same is true for xlock

I tried the command

$/usr/libexec/xscreensaver/noseguy

and it displays a window but instead of a fortune it displays an error message:

xscreensaver-text: /usr/share/doc/libX11-1.6.0/COPYING: No such file or directory

This is the same error I get when simply running

$xscreensaver-text

I can make it work under fvwm2 by giving the fortune command as a parameter:

Code:
/usr/libexec/xscreensaver/noseguy -program 'fortune'
 
Old 02-15-2014, 03:04 PM   #5
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by lems View Post
Yes, same problem using ctwm. I noticed that when I compiled xlockmore with the options of OpenBSD[1], it still exited, but did not print
Code:
Access control list restored.
xlock: caught signal 11 while running nose mode (uid 1000).
anymore.

I also get
Code:
Could not create FontSet -*-fixed-medium-r-*-*-14-*-*-*-*-*-*,-*-*-medium-r-normal--14-*
but I had no luck using the various -*font* switches.

[1]: http://www.openbsd.org/cgi-bin/cvswe...e=text%2Fplain
Thank you. This looks identical to the errors that I am getting under Slackware current with fvwm2.

I tried using the trick of the "-program" option which worked for xscreensaver/noseguy in the last posting but it still gets the same error:

xlock: caught signal 11 while running nose mode ...

The error definitely happens at the time a fortune is supposed to be displayed which is a random time after the program starts.

I found a source of more information about the settings of xlock by using the "-resources" option to create a file with listing all the default settings:

Code:
$ xlock -resources | sort | tee xlock-resources.txt
And here are some of the relevant settings found:

Code:
...
XLock.message:
XLock.messagefile:
XLock.messagefont: -*-times-*-*-*-*-18-*-*-*-*-*-*-*
XLock.messagesfile:
...
XLock.nose.bitmap:
XLock.nose.count: 1
XLock.nose.cycles: 1
XLock.nose.delay: 100000
XLock.nose.ncolors: 64
XLock.nose.saturation: 1
XLock.nose.size: 1
...
XLock.planfontset: -*-fixed-medium-r-*-*-14-*-*-*-*-*-*,-*-*-medium-r-normal--14-*
...
XLock.program: fortune -s
 
Old 02-15-2014, 06:34 PM   #6
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Original Poster
Rep: Reputation: Disabled
This seems to be something unique to my current installation.

I could not repeat the bug on a clean install of 14.1-stable.
Nor could I repeat the bug in a clean install of current.
"xlock -mode nose" works fine on clean installs.

I will try to figure out what I changed on my current system and report back.

Needless to say, "signal 11" is not a very helpful error message...
 
Old 02-15-2014, 10:29 PM   #7
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Original Poster
Rep: Reputation: Disabled
This is finally solved.

The root problem was the setting of the LANG environment variable.

In Slackware the /etc/profile.d/lang.sh script normally sets the LANG variable:

Code:
export LANG=en_US
But recently I was messing around with UTF-8 and had this in the lang.sh script:

Code:
export LANG=en_US.utf8
LANG=en_US.utf8 causes xlock -mode nose to fail with signal 11
and it causes this error message to emit from xlock:

Could not create FontSet -*-fixed-medium-r-*-*-14-*-*-*-*-*-*,-*-*-medium-r-normal--14-*

Last edited by aaazen; 02-15-2014 at 10:34 PM. Reason: use bold font
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
php (interpreter): SIGSEV on ZEND_MM_IS_FREE_BLOCK(next_block) eantoranz Programming 4 08-03-2012 05:23 PM
Multiple KDE application crashes (signal 11, SIGSEV) in MEPIS and Kubuntu adasiak Linux - Newbie 1 07-18-2008 07:20 AM
Kopete-Strange sigsev issue sumguy231 Linux - Software 0 12-28-2004 04:43 PM
Xlock / Xlock more with enterprise authentication yasir15 Linux - Software 0 04-20-2004 12:47 PM
xlock does not run in fullscreen mode anymore after updating qtvision (KDE 3.1.1) Physitux Linux - Software 0 02-09-2004 03:59 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:46 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration