subject:"Re\: problems with system\-config\-display and crtl\-alt\-backspace"

Paul Allen Newell wrote:
Suvayu Ali wrote:
On Sunday 27 December 2009 11:06 AM, Kevin Fenzi wrote:
On Sun, 27 Dec 2009 00:42:19 -0800
Paul Allen Newellpnew...@cs.cmu.edu wrote:

To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I
could edit my xorg.conf to restore that feature.

How did you discover this? Trying it in a gnome desktop? :)

Searched Fedora f12 web pages and they told me to install
system-config-display to create an xorg.conf that matched the default
that the opSys was using. Worked great and, to use the cliché,
groovy

Don't do that. See:

http://ryanler.wordpress.com/2009/06/11/controlaltbackspace-shortcut-does-not-restart-the-x-server-in-fedora-11/

(with screenshots even! :)

There is no need at all to make an xorg.conf, and as you have seen it
can cause problems moving forward.

kevin

If the OP is interested, the command line way to do this would be to
have one of your login scripts like ~/.bash_profile say,

setxkbmap -option terminate:ctrl_alt_bksp

;)
Suvayu:

Thanks, this is interesting. So it is in .bash_profile and not
.bashrc? Is there a similar way to do in either cshrc or, preferably,
tcshrc?

At this point it would be helpful to read man bash and man tcsh
which will answer your questions about when the various ~/. files are read.

--
Life is a whim of several billion cells to be you for a while. Guess
Who! http://tinyurl.com/mc4xe7

signature.asc
Description: OpenPGP digital signature
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-28 Thread Suvayu Ali


Hi Aaron,

On Monday 28 December 2009 02:11 PM, Aaron Konstam wrote:

On Mon, 2009-12-28 at 03:04 -0800, Suvayu Ali wrote:

~/.bash_profile gets sourced by any well behaved desktop environment
when ever you login. In my experience XFCE and WindowMaker does this. (I
don't use Gnome/KDE as often, so can't comment on them).

~/.bashrc gets sourced when ever you open an interactive shell, maybe by
opening a terminal emulator or login in remotely.

This means whenever you login remotely both ~/.bash_profile  ~/.bashrc
gets sourced. However if you open a terminal emulator like
gnome-terminal or xterm only your ~/.bashrc gets sourced.


It is my impression that.bashrc is souurced whenever any program is run
in a bash environment. I am willing to be corrected.



By bash environment if you mean a terminal emulator then that is exactly 
what I meant in my previous post. However if for example you run 
something using a menu or shortcut on your desktop or maybe Alt-F2 then 
~/.bashrc is _not_ sourced, and environment variables defined there 
won't be available to you. If you want something like that, you need to 
define it in your ~/.bash_profile.


Hope this makes my point clearer. :)
--
Suvayu

Open source is the future. It sets us free.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace


TNWestTex wrote:


Paul Allen Newell wrote:
  

François Patte wrote:


Paul Allen Newell pnew...@cs.cmu.edu a écrit :

  

To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I 
could edit my xorg.conf to restore that feature.


Searched Fedora f12 web pages and they told me to install 
system-config-display to create an xorg.conf that matched the default 
that the opSys was using. Worked great and, to use the cliché, groovy


Reboot system and it immediately hangs after that cute little Fedora 
icon finishes to say that it booted. Just hangs and hangs. To use the 
cliché again, not groovy.


I figure I have no choice but to reinstall

Why don't edit grub boot line to switch to level 3 and see what 
happens using startx? Then examine the log files Xorg.0.log*


  


This message was sent using IMP, the Internet Messaging Program.
  

François:

Thanks for the reply. Given the here it is replies from Eric and 
Kevin, I'm going to take the easy route and use that rather than get 
myself into more trouble with Xorg.


Paul




If you use the advice from François you can make the other changes by using
su - to get to root without having to reinstall.  In textmode you have
control over your system that the graphical boot takes away from you. 
Besides on all the systems I've tried so far it is much faster to login and

type startx than is tis to wait for all the graphics.

Robert McBroom

  

Robert:

Though I certainly agree with the benefits you describe, I have to admit 
that I don't feel secure enough in my skills to venture into such. Just 
trying to run vanilla quite often gets me into trouble. That being said, 
fedora / red hat / linux is one heck of alot easier than Windows as far 
as I am concerned.


Once I have a stable f12 install, I'll read man page / web to learn more 
about startx as your advice indicates it is probably something I could 
find useful.


Thanks for the email,
Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace


Suvayu Ali wrote:

Hi Aaron,

On Monday 28 December 2009 02:11 PM, Aaron Konstam wrote:

On Mon, 2009-12-28 at 03:04 -0800, Suvayu Ali wrote:

~/.bash_profile gets sourced by any well behaved desktop environment
when ever you login. In my experience XFCE and WindowMaker does 
this. (I

don't use Gnome/KDE as often, so can't comment on them).

~/.bashrc gets sourced when ever you open an interactive shell, 
maybe by

opening a terminal emulator or login in remotely.

This means whenever you login remotely both ~/.bash_profile  ~/.bashrc
gets sourced. However if you open a terminal emulator like
gnome-terminal or xterm only your ~/.bashrc gets sourced.


It is my impression that.bashrc is souurced whenever any program is run
in a bash environment. I am willing to be corrected.



By bash environment if you mean a terminal emulator then that is 
exactly what I meant in my previous post. However if for example you 
run something using a menu or shortcut on your desktop or maybe Alt-F2 
then ~/.bashrc is _not_ sourced, and environment variables defined 
there won't be available to you. If you want something like that, you 
need to define it in your ~/.bash_profile.


Hope this makes my point clearer. :)
Naive question  it sounds like if a user has selected bash as 
shell-of-choice, then bash_profile is there for any operation (terminal 
or not) that would involve the use of the shell? I might not be saying 
this right, but I am trying to understand just how global bash_profile 
is and, if not, why it isn't as it seems by your email that for all 
intents and purposes it is global to a user's login process.


Thanks for bearing with the question given that you already know I am 
running tcsh and therefore this is a learning exercise as opposed to a 
real occurrence in my usage of fedora.


Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

Paul Allen Newell wrote:
 Suvayu Ali wrote:
 Hi Aaron,

 On Monday 28 December 2009 02:11 PM, Aaron Konstam wrote:
 On Mon, 2009-12-28 at 03:04 -0800, Suvayu Ali wrote:
 ~/.bash_profile gets sourced by any well behaved desktop environment
 when ever you login. In my experience XFCE and WindowMaker does
 this. (I
 don't use Gnome/KDE as often, so can't comment on them).

 ~/.bashrc gets sourced when ever you open an interactive shell,
 maybe by
 opening a terminal emulator or login in remotely.

 This means whenever you login remotely both ~/.bash_profile 
 ~/.bashrc
 gets sourced. However if you open a terminal emulator like
 gnome-terminal or xterm only your ~/.bashrc gets sourced.

 It is my impression that.bashrc is souurced whenever any program is run
 in a bash environment. I am willing to be corrected.


 By bash environment if you mean a terminal emulator then that is
 exactly what I meant in my previous post. However if for example you
 run something using a menu or shortcut on your desktop or maybe
 Alt-F2 then ~/.bashrc is _not_ sourced, and environment variables
 defined there won't be available to you. If you want something like
 that, you need to define it in your ~/.bash_profile.

 Hope this makes my point clearer. :)
 Naive question  it sounds like if a user has selected bash as
 shell-of-choice, then bash_profile is there for any operation
 (terminal or not) that would involve the use of the shell? I might not
 be saying this right, but I am trying to understand just how global
 bash_profile is and, if not, why it isn't as it seems by your email
 that for all intents and purposes it is global to a user's login process.

 Thanks for bearing with the question given that you already know I am
 running tcsh and therefore this is a learning exercise as opposed to a
 real occurrence in my usage of fedora.

 Paul

Why not just read man bash?

-- 
95% of guys masturbate...the other 5% lie. Guess Who!
http://tinyurl.com/mc4xe7



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace


Ed Greshko wrote:

Paul Allen Newell wrote:
  

Suvayu Ali wrote:


Hi Aaron,

On Monday 28 December 2009 02:11 PM, Aaron Konstam wrote:
  

On Mon, 2009-12-28 at 03:04 -0800, Suvayu Ali wrote:


~/.bash_profile gets sourced by any well behaved desktop environment
when ever you login. In my experience XFCE and WindowMaker does
this. (I
don't use Gnome/KDE as often, so can't comment on them).

~/.bashrc gets sourced when ever you open an interactive shell,
maybe by
opening a terminal emulator or login in remotely.

This means whenever you login remotely both ~/.bash_profile 
~/.bashrc

gets sourced. However if you open a terminal emulator like
gnome-terminal or xterm only your ~/.bashrc gets sourced.
  

It is my impression that.bashrc is souurced whenever any program is run
in a bash environment. I am willing to be corrected.



By bash environment if you mean a terminal emulator then that is
exactly what I meant in my previous post. However if for example you
run something using a menu or shortcut on your desktop or maybe
Alt-F2 then ~/.bashrc is _not_ sourced, and environment variables
defined there won't be available to you. If you want something like
that, you need to define it in your ~/.bash_profile.

Hope this makes my point clearer. :)
  

Naive question  it sounds like if a user has selected bash as
shell-of-choice, then bash_profile is there for any operation
(terminal or not) that would involve the use of the shell? I might not
be saying this right, but I am trying to understand just how global
bash_profile is and, if not, why it isn't as it seems by your email
that for all intents and purposes it is global to a user's login process.

Thanks for bearing with the question given that you already know I am
running tcsh and therefore this is a learning exercise as opposed to a
real occurrence in my usage of fedora.

Paul



Why not just read man bash?

  
Because bring up the man bash pages and searching for profile gives 
me info about what happens with a shell or a non-interactive --login 
shell and doesn't give me any meta information that either answers my 
question or makes it clear that I am asking the wrong question.


http://www.gnu.org/software/bash/manual/bashref.html

One of the reasons to watch/read this forum is to get answers to 
questions that man pages don't supply. In my experience, if you want to 
know exactly how to do something with a given command/whatever, they are 
great. If you want to get an understanding of the overall picture of the 
command/whatever, they aren't very good as they assume you have already 
commit to this is what I am using so how do I do this particular 
operation.


To ask what is the scope of .bash_profile outside of sourcing order in 
particular occurrences, I don't see it in the man pages.


I am more than happy to be told that I am totally incorrect in my 
interpretation of this.


Thanks (and that includes making me double-check the man pages to prove 
to myself that I am not seeing the answer I am looking for!),

Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

Paul Allen Newell wrote:
 Ed Greshko wrote:
 Paul Allen Newell wrote:
  
 Suvayu Ali wrote:

 Hi Aaron,

 On Monday 28 December 2009 02:11 PM, Aaron Konstam wrote:
  
 On Mon, 2009-12-28 at 03:04 -0800, Suvayu Ali wrote:

 ~/.bash_profile gets sourced by any well behaved desktop
 environment
 when ever you login. In my experience XFCE and WindowMaker does
 this. (I
 don't use Gnome/KDE as often, so can't comment on them).

 ~/.bashrc gets sourced when ever you open an interactive shell,
 maybe by
 opening a terminal emulator or login in remotely.

 This means whenever you login remotely both ~/.bash_profile
 ~/.bashrc
 gets sourced. However if you open a terminal emulator like
 gnome-terminal or xterm only your ~/.bashrc gets sourced.
   
 It is my impression that.bashrc is souurced whenever any program
 is run
 in a bash environment. I am willing to be corrected.

 
 By bash environment if you mean a terminal emulator then that is
 exactly what I meant in my previous post. However if for example you
 run something using a menu or shortcut on your desktop or maybe
 Alt-F2 then ~/.bashrc is _not_ sourced, and environment variables
 defined there won't be available to you. If you want something like
 that, you need to define it in your ~/.bash_profile.

 Hope this makes my point clearer. :)
   
 Naive question  it sounds like if a user has selected bash as
 shell-of-choice, then bash_profile is there for any operation
 (terminal or not) that would involve the use of the shell? I might not
 be saying this right, but I am trying to understand just how global
 bash_profile is and, if not, why it isn't as it seems by your email
 that for all intents and purposes it is global to a user's login
 process.

 Thanks for bearing with the question given that you already know I am
 running tcsh and therefore this is a learning exercise as opposed to a
 real occurrence in my usage of fedora.

 Paul

 
 Why not just read man bash?

   
 Because bring up the man bash pages and searching for profile
 gives me info about what happens with a shell or a non-interactive
 --login shell and doesn't give me any meta information that either
 answers my question or makes it clear that I am asking the wrong
 question.

 http://www.gnu.org/software/bash/manual/bashref.html

 One of the reasons to watch/read this forum is to get answers to
 questions that man pages don't supply. In my experience, if you want
 to know exactly how to do something with a given command/whatever,
 they are great. If you want to get an understanding of the overall
 picture of the command/whatever, they aren't very good as they assume
 you have already commit to this is what I am using so how do I do
 this particular operation.

 To ask what is the scope of .bash_profile outside of sourcing order
 in particular occurrences, I don't see it in the man pages.

 I am more than happy to be told that I am totally incorrect in my
 interpretation of this.

 Thanks (and that includes making me double-check the man pages to
 prove to myself that I am not seeing the answer I am looking for!),
 Paul

I suppose I don't understand your question or what makes you think the
man page doesn't answer it.

The man page tells you under what conditions the various files
(/etc/profile, ~/.bash_profile ~/.bash_login etc) are read depending on
what type of shell (interactive, login). 

Are you saying there is a situation not covered?

Remember, everything that is executed is executed under a shell.

-- 
When the going gets weird, the weird turn pro... -- Hunter S. Thompson
Guess Who! http://tinyurl.com/mc4xe7



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace


Ed Greshko wrote:

Paul Allen Newell wrote:
  

Ed Greshko wrote:


Paul Allen Newell wrote:
 
  

Suvayu Ali wrote:
   


Hi Aaron,

On Monday 28 December 2009 02:11 PM, Aaron Konstam wrote:
 
  

On Mon, 2009-12-28 at 03:04 -0800, Suvayu Ali wrote:
   


~/.bash_profile gets sourced by any well behaved desktop
environment
when ever you login. In my experience XFCE and WindowMaker does
this. (I
don't use Gnome/KDE as often, so can't comment on them).

~/.bashrc gets sourced when ever you open an interactive shell,
maybe by
opening a terminal emulator or login in remotely.

This means whenever you login remotely both ~/.bash_profile
~/.bashrc
gets sourced. However if you open a terminal emulator like
gnome-terminal or xterm only your ~/.bashrc gets sourced.
  
  

It is my impression that.bashrc is souurced whenever any program
is run
in a bash environment. I am willing to be corrected.




By bash environment if you mean a terminal emulator then that is
exactly what I meant in my previous post. However if for example you
run something using a menu or shortcut on your desktop or maybe
Alt-F2 then ~/.bashrc is _not_ sourced, and environment variables
defined there won't be available to you. If you want something like
that, you need to define it in your ~/.bash_profile.

Hope this makes my point clearer. :)
  
  

Naive question  it sounds like if a user has selected bash as
shell-of-choice, then bash_profile is there for any operation
(terminal or not) that would involve the use of the shell? I might not
be saying this right, but I am trying to understand just how global
bash_profile is and, if not, why it isn't as it seems by your email
that for all intents and purposes it is global to a user's login
process.

Thanks for bearing with the question given that you already know I am
running tcsh and therefore this is a learning exercise as opposed to a
real occurrence in my usage of fedora.

Paul




Why not just read man bash?

  
  

Because bring up the man bash pages and searching for profile
gives me info about what happens with a shell or a non-interactive
--login shell and doesn't give me any meta information that either
answers my question or makes it clear that I am asking the wrong
question.

http://www.gnu.org/software/bash/manual/bashref.html

One of the reasons to watch/read this forum is to get answers to
questions that man pages don't supply. In my experience, if you want
to know exactly how to do something with a given command/whatever,
they are great. If you want to get an understanding of the overall
picture of the command/whatever, they aren't very good as they assume
you have already commit to this is what I am using so how do I do
this particular operation.

To ask what is the scope of .bash_profile outside of sourcing order
in particular occurrences, I don't see it in the man pages.

I am more than happy to be told that I am totally incorrect in my
interpretation of this.

Thanks (and that includes making me double-check the man pages to
prove to myself that I am not seeing the answer I am looking for!),
Paul



I suppose I don't understand your question or what makes you think the
man page doesn't answer it.

The man page tells you under what conditions the various files
(/etc/profile, ~/.bash_profile ~/.bash_login etc) are read depending on
what type of shell (interactive, login). 


Are you saying there is a situation not covered?

Remember, everything that is executed is executed under a shell.

  

Ed,

Thanks for bearing with me on this.

I think part of my confusion is that I am not understanding whether a 
login shell covers everything that is done once I have logged in via 
splash screen or if it is confined to logining into a shell. If the 
former, then I would assume bash_profiles is hit once and everything 
done thereafter would be under its command. If the latter, then I am 
probably unclear about whether launching a terminal is a login act 
(hence under bash_profile only within that shell).


As I said on my initial reply to this thread, Naive question. I may be 
missing a fundamental understanding of shells and logins and all that 
sort of stuff.


Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

Paul Allen Newell wrote:

 I think part of my confusion is that I am not understanding whether a
 login shell covers everything that is done once I have logged in via
 splash screen or if it is confined to logining into a shell. If the
 former, then I would assume bash_profiles is hit once and everything
 done thereafter would be under its command. If the latter, then I am
 probably unclear about whether launching a terminal is a login act
 (hence under bash_profile only within that shell).

 As I said on my initial reply to this thread, Naive question. I may
 be missing a fundamental understanding of shells and logins and all
 that sort of stuff.

A login shell is what it says it is.  A shell created as a consequence
of logging in.  That could be a console login in run level 3, the GUI
login screen in run level 5, an ssh login from a remote system, etc. 
Starting, for example, gnome-terminal, does not constitute a login shell.

One thing you can do to learn when .bashrc and .bash_profile are sourced
is to add something like

touch /tmp/bashrc.time   to the end of your .bashrc file and a similar
line to your .bash_profile.  Then you can
ls -l --time-style=full-iso  (to display the seconds).

I also think you may want to learn about PID's and PPID's  (Process ID,
and Parent Process ID).




-- 
How to make a million dollars: First, get a million dollars. -- Steve
Martin Guess Who! http://tinyurl.com/mc4xe7



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-28 Thread Suvayu Ali


Hi Paul,

On Monday 28 December 2009 09:21 PM, Paul Allen Newell wrote:

Ed Greshko wrote:


The man page tells you under what conditions the various files
(/etc/profile, ~/.bash_profile ~/.bash_login etc) are read depending on
what type of shell (interactive, login).
Are you saying there is a situation not covered?

Remember, everything that is executed is executed under a shell.


I think part of my confusion is that I am not understanding whether a
login shell covers everything that is done once I have logged in via
splash screen or if it is confined to logining into a shell. If the
former, then I would assume bash_profiles is hit once and everything
done thereafter would be under its command. If the latter, then I am
probably unclear about whether launching a terminal is a login act
(hence under bash_profile only within that shell).



I think a small experiment is in order. Open up any terminal emulator of 
your choice, go fullscreen (well just stretching it to be really big 
should be enough for the experiment ;) )


Now run the following,

$ ps uf -u `whoami`

The output might be a little truncated on the right depending on the 
size of your monitor, but that is not too important. As you can see, the 
command to start your desktop is initiated by a shell. So if you setup 
your environment variables appropriately, then all those should be 
available to the shell starting your desktop. This allows you to have a 
consistent environment for your applications no matter how you launch 
them, from a terminal or from the gui of your desktop.


The lesson to learn here are the differences between shells/apps 
inheriting the environment of its parent shell/process depending on how 
you set the environment.


If you are interested, you can try another small experiment to see for 
yourself what I mean. Try putting this in your ~/.bash_profile,


export PATH=$PATH:${HOME}/bin

And then put a symbolic link to some small application of your choice in 
your ${HOME}/bin.


For example I did this, (I chose thunar as I use XFCE)

$ ln -s -T `which thunar` ${HOME}/bin/fakethunar

Now logout and log back in. Try running `fakethunar' with the Alt-F2 
dialogue. It will open up thunar. Now comment out those lines, logout, 
login again and repeat that. You will get an error message. You can do 
many different variations of this to explore some more subtleties. But I 
think this paints a clearer picture now. :)




Paul



Have fun hacking.

PS: This kind of info is usually in the FILES or INVOCATION section of 
the man pages.

--
Suvayu

Open source is the future. It sets us free.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

Ed Greshko wrote:
 Paul Allen Newell wrote:
   
 I think part of my confusion is that I am not understanding whether a
 login shell covers everything that is done once I have logged in via
 splash screen or if it is confined to logining into a shell. If the
 former, then I would assume bash_profiles is hit once and everything
 done thereafter would be under its command. If the latter, then I am
 probably unclear about whether launching a terminal is a login act
 (hence under bash_profile only within that shell).

 As I said on my initial reply to this thread, Naive question. I may
 be missing a fundamental understanding of shells and logins and all
 that sort of stuff.

 
 A login shell is what it says it is.  A shell created as a consequence
 of logging in.  That could be a console login in run level 3, the GUI
 login screen in run level 5, an ssh login from a remote system, etc. 
 Starting, for example, gnome-terminal, does not constitute a login shell.
   
I also forgot to mention the -i and -l parameters on the #!/bin/bash
line of a shell script that would also affect the type of shell.
 One thing you can do to learn when .bashrc and .bash_profile are sourced
 is to add something like

 touch /tmp/bashrc.time   to the end of your .bashrc file and a similar
 line to your .bash_profile.  Then you can
 ls -l --time-style=full-iso  (to display the seconds).

 I also think you may want to learn about PID's and PPID's  (Process ID,
 and Parent Process ID).




   


-- 
There's an old proverb that says just about whatever you want it to.
Guess Who! http://tinyurl.com/mc4xe7



signature.asc
Description: OpenPGP digital signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-27 Thread Eric Tanguy


Le 27/12/2009 09:42, Paul Allen Newell a écrit :

To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I could 
edit my xorg.conf to restore that feature.


Searched Fedora f12 web pages and they told me to install 
system-config-display to create an xorg.conf that matched the default 
that the opSys was using. Worked great and, to use the cliché, groovy


Reboot system and it immediately hangs after that cute little Fedora 
icon finishes to say that it booted. Just hangs and hangs. To use the 
cliché again, not groovy.


I figure I have no choice but to reinstall (what's a few hours between 
friends (grumble)) ... but would like to know the proper (which may be 
not documented) way to restore crtl-alt-backspace to kick the X.


I have three computer on a KVM and I often need to kick one of them if 
it boots up and the KVM isn't directed at it cause its on one of the 
others.. I've never understood why X has to actually connect to the 
monitor to be correct, but X is pretty near a black box as far as I am 
concerned (sigh).


Thanks in advance,
Paul

Thanks,
Paul

In gnome, go to system, preferences, keyboard, after that i don't know 
the exact translation in english.
So go to the 2nd tab,  at the bottom right you find something like 
options ... and you find key sequence to kill the  server ...


Eric

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-27 Thread François Patte


Paul Allen Newell pnew...@cs.cmu.edu a écrit :


To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I  
could edit my xorg.conf to restore that feature.


Searched Fedora f12 web pages and they told me to install  
system-config-display to create an xorg.conf that matched the  
default that the opSys was using. Worked great and, to use the  
cliché, groovy


Reboot system and it immediately hangs after that cute little Fedora  
icon finishes to say that it booted. Just hangs and hangs. To use  
the cliché again, not groovy.


I figure I have no choice but to reinstall


Why don't edit grub boot line to switch to level 3 and see what  
happens using startx? Then examine the log files Xorg.0.log*




--
François Patte
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 4286 2145
http://www.math-info.univ-paris5.fr/~patte



This message was sent using IMP, the Internet Messaging Program.


pgpHiygQErYHe.pgp
Description: Signature numérique PGP
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-27 Thread Karl-Olov Serrander


On Sun, 27 Dec 2009, Eric Tanguy wrote:


Le 27/12/2009 09:42, Paul Allen Newell a écrit :

...
I figure I have no choice but to reinstall (what's a few hours between 
friends (grumble)) ... but would like to know the proper (which may be not 
documented) way to restore crtl-alt-backspace to kick the X.

...
In gnome, go to system, preferences, keyboard, after that i don't know the 
exact translation in english.
So go to the 2nd tab,  at the bottom right you find something like options 
... and you find key sequence to kill the  server ...


Eric


How to set this systemwide ?

Regards
--
Karl-Olov Serrander m11172.abc.se-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-27 Thread Craig White

On Sun, 2009-12-27 at 00:42 -0800, Paul Allen Newell wrote:
 To all:
 
 Installed f12 without any problems.
 
 Discovered that crtl-alt-backspace was disabled in f12 and how I could 
 edit my xorg.conf to restore that feature.
 
 Searched Fedora f12 web pages and they told me to install 
 system-config-display to create an xorg.conf that matched the default 
 that the opSys was using. Worked great and, to use the cliché, groovy
 
 Reboot system and it immediately hangs after that cute little Fedora 
 icon finishes to say that it booted. Just hangs and hangs. To use the 
 cliché again, not groovy.
 
 I figure I have no choice but to reinstall (what's a few hours between 
 friends (grumble)) ... but would like to know the proper (which may be 
 not documented) way to restore crtl-alt-backspace to kick the X.
 
 I have three computer on a KVM and I often need to kick one of them if 
 it boots up and the KVM isn't directed at it cause its on one of the 
 others.. I've never understood why X has to actually connect to the 
 monitor to be correct, but X is pretty near a black box as far as I am 
 concerned (sigh).

put into /etc/X11/xorg.conf

Section ServerFlags
Option  DontZap false  
EndSection 

then you can kill X with ControlAltBackspace as before (after you
restart X of course.

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-27 Thread Kevin Fenzi

On Sun, 27 Dec 2009 00:42:19 -0800
Paul Allen Newell pnew...@cs.cmu.edu wrote:

 To all:
 
 Installed f12 without any problems.
 
 Discovered that crtl-alt-backspace was disabled in f12 and how I
 could edit my xorg.conf to restore that feature.

How did you discover this? Trying it in a gnome desktop? :) 

 Searched Fedora f12 web pages and they told me to install 
 system-config-display to create an xorg.conf that matched the default 
 that the opSys was using. Worked great and, to use the cliché,
 groovy

Don't do that. See: 

http://ryanler.wordpress.com/2009/06/11/controlaltbackspace-shortcut-does-not-restart-the-x-server-in-fedora-11/

(with screenshots even! :) 

There is no need at all to make an xorg.conf, and as you have seen it
can cause problems moving forward. 

kevin


signature.asc
Description: PGP signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace


Eric Tanguy wrote:

Le 27/12/2009 09:42, Paul Allen Newell a écrit :

To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I 
could edit my xorg.conf to restore that feature.


Searched Fedora f12 web pages and they told me to install 
system-config-display to create an xorg.conf that matched the default 
that the opSys was using. Worked great and, to use the cliché, groovy


Reboot system and it immediately hangs after that cute little Fedora 
icon finishes to say that it booted. Just hangs and hangs. To use the 
cliché again, not groovy.


I figure I have no choice but to reinstall (what's a few hours 
between friends (grumble)) ... but would like to know the proper 
(which may be not documented) way to restore crtl-alt-backspace to 
kick the X.


I have three computer on a KVM and I often need to kick one of them 
if it boots up and the KVM isn't directed at it cause its on one of 
the others.. I've never understood why X has to actually connect to 
the monitor to be correct, but X is pretty near a black box as far as 
I am concerned (sigh).


Thanks in advance,
Paul

Thanks,
Paul

In gnome, go to system, preferences, keyboard, after that i don't know 
the exact translation in english.
So go to the 2nd tab,  at the bottom right you find something like 
options ... and you find key sequence to kill the  server ...


Eric


Eric:

Thank you for reply, later email from Kevin Fenzi had like to website to 
show this as well. Once I've reinstalled f12, will give it a try.


Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace


François Patte wrote:

Paul Allen Newell pnew...@cs.cmu.edu a écrit :


To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I 
could edit my xorg.conf to restore that feature.


Searched Fedora f12 web pages and they told me to install 
system-config-display to create an xorg.conf that matched the default 
that the opSys was using. Worked great and, to use the cliché, groovy


Reboot system and it immediately hangs after that cute little Fedora 
icon finishes to say that it booted. Just hangs and hangs. To use the 
cliché again, not groovy.


I figure I have no choice but to reinstall


Why don't edit grub boot line to switch to level 3 and see what 
happens using startx? Then examine the log files Xorg.0.log*




--
François Patte
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 4286 2145
http://www.math-info.univ-paris5.fr/~patte



This message was sent using IMP, the Internet Messaging Program.

François:

Thanks for the reply. Given the here it is replies from Eric and 
Kevin, I'm going to take the easy route and use that rather than get 
myself into more trouble with Xorg.


Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace


Craig White wrote:

On Sun, 2009-12-27 at 00:42 -0800, Paul Allen Newell wrote:
  

To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I could 
edit my xorg.conf to restore that feature.


Searched Fedora f12 web pages and they told me to install 
system-config-display to create an xorg.conf that matched the default 
that the opSys was using. Worked great and, to use the cliché, groovy


Reboot system and it immediately hangs after that cute little Fedora 
icon finishes to say that it booted. Just hangs and hangs. To use the 
cliché again, not groovy.


I figure I have no choice but to reinstall (what's a few hours between 
friends (grumble)) ... but would like to know the proper (which may be 
not documented) way to restore crtl-alt-backspace to kick the X.


I have three computer on a KVM and I often need to kick one of them if 
it boots up and the KVM isn't directed at it cause its on one of the 
others.. I've never understood why X has to actually connect to the 
monitor to be correct, but X is pretty near a black box as far as I am 
concerned (sigh).



put into /etc/X11/xorg.conf

Section ServerFlags
Option  DontZap false  
EndSection 


then you can kill X with ControlAltBackspace as before (after you
restart X of course.

Craig


  

Craig:

The plan originally was to use the DontZap once I proved that using 
system-config-display to create Xorg would work. Never made it far 
enough and, given the posting from Eric and especially Kevin, I think I 
am better off with a reinstall and using the Keyboard Layout.


Thanks for the reply,
Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

Kevin Fenzi wrote:

On Sun, 27 Dec 2009 00:42:19 -0800
Paul Allen Newell pnew...@cs.cmu.edu wrote:

To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I
could edit my xorg.conf to restore that feature.

How did you discover this? Trying it in a gnome desktop? :)

Of course (smile)

Searched Fedora f12 web pages and they told me to install
system-config-display to create an xorg.conf that matched the default
that the opSys was using. Worked great and, to use the cliché,

groovy

Don't do that. See:

http://ryanler.wordpress.com/2009/06/11/controlaltbackspace-shortcut-does-not-restart-the-x-server-in-fedora-11/

(with screenshots even! :)

There is no need at all to make an xorg.conf, and as you have seen it
can cause problems moving forward.

kevin

Kevin:

Many thanks for the link (gotta love when screen-shots are included!).
When I went hunting on the web, I got stuck on the system-config-display
thread which gives me an Xorg to put in DontZap info. I think I ended up
on an F11 thread instead of an F12 as a look afterword shows me that my
searches were Fedoraguide.info ... bad on my part for remembering prior
forum discusssions about DontZap and jumping to wrong conclusion.

I wish my Goggling had hit this article first and/or instead ... another
lesson learned by hitting thumb with hammer instead of hitting nail.

I am quite happy to not mess with Xorg, I remember it making my life
miserable on fc5 and I wasn't exactly looking forward to having to mess
with it again.

Once again, my thanks ... now I just have to reinstall to try it out,
Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace

2009-12-27 Thread Suvayu Ali


On Sunday 27 December 2009 11:06 AM, Kevin Fenzi wrote:

On Sun, 27 Dec 2009 00:42:19 -0800
Paul Allen Newellpnew...@cs.cmu.edu  wrote:


To all:

Installed f12 without any problems.

Discovered that crtl-alt-backspace was disabled in f12 and how I
could edit my xorg.conf to restore that feature.


How did you discover this? Trying it in a gnome desktop? :)


Searched Fedora f12 web pages and they told me to install
system-config-display to create an xorg.conf that matched the default
that the opSys was using. Worked great and, to use the cliché,
groovy


Don't do that. See:

http://ryanler.wordpress.com/2009/06/11/controlaltbackspace-shortcut-does-not-restart-the-x-server-in-fedora-11/

(with screenshots even! :)

There is no need at all to make an xorg.conf, and as you have seen it
can cause problems moving forward.

kevin



If the OP is interested, the command line way to do this would be to 
have one of your login scripts like ~/.bash_profile say,


setxkbmap -option terminate:ctrl_alt_bksp

;)
--
Suvayu

Open source is the future. It sets us free.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: problems with system-config-display and crtl-alt-backspace