Terminal preferences bug

Have any of you seen or heard of a bug in 10.10.2 affecting the preferences for Terminal.app?
Here's how I got to it. With Terminal.app running, open Preferences, click Profiles, and then make sure that focus is on the TEXT tab. What you should find is that clicking the color boxes turn gray and do not cause the color picker to open. Clicking them twice returns them to their color, but the color picker still doesn't open. It might open if you click the color boxes that are set for Terminal, but when it does the dialog is broken and malformed. The same issue appears in the WINDOW tab for determining the color of the terminal window. Also, none of the pre-set profiles will change the appearance of Terminal even if you select them.
I've tried restarting the application, but nothing more drastic than that. If any of you have seen this and know a solution, please let me know.
Thanks in advance!

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Please take this step regardless of the results of Step 1.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

Similar Messages

[Cinnamon] Terminator preferences help.

Hi there,
I have a little problem with terminator's preferences screen as it's always reset. My settings are well saved and work but if I try to look at them later, it is as if every color I chose for my terminal is black and every option deactivated.
I think it's cinnamon related as friends of mine have also installed it on archlinux but with LXDE installed and it works like a charm.
It's a small issue I know but I like to know the reasons of os bug.
I'd also like to have a hand with transparency this time. You see, on Linux Mint 13 Mate, my terminal would use fake transparency as I could only see my desktop background but not the windows behind it. Now on arch, I have the real transparency which makes characters impossible to read when some other windows are behind.
I've search the web for an answer but every one is asking for how to go from semi-transparent to fully transparent terminal (which I think is dumb).
Hope to find an answer here,
Thanks in advance.

Is System Preferences available under the Apple icon at top left? Does it work?

Mavericks: terminal preferences not transfered to second desktop

I have created my own Terminal settings through preferences, and I have selected them to be used when creating new terminal windows. On the desktop where I first launch Terminal, this works as expected. If I then go to a second desktop, and type "command + N", then the "Basic" terminal settings are used instead. If I look in the preferences, I can still see that the ones I picked are set, however, the "Shell > New Window" is set to Basic. Perhaps obviously, since I am launching a new Terminal on a different desktop, I have changed Mission Control to no switch to the desktop on which the windows are already opened.
I believe this is a software bug and not some preferences I can control. Any ideas?
Regards,
Andre

The full screen action that you are describing is working as Apple have designed it to work.
Whenever you use an application or watch a video in Full Screen mode, it will always open it its own desktop.

Remote app, print preference bug

hello,
we use remote app on a 2008 R2 Server and since last update, the print preference dialog are in front. If you logon direct an terminal server it works fine. If you use a app the dialog can be closed
Chris

Hi,
Do you find the solution ?
I have the same issue, only with W7 client not with XP client.
The "printing option" window doesn't appear foreground the remote application so the user have to use ALT+TAB combinaison to display the window !
Thanks in advance,

Terminal preferences only used for first window

Hello,
Whatever I set in Terminal's Preferences only lasts for the first window I open.
For example, if I set "New window with settings:" to "Pro," the first window is Pro, but any subsequent windows or tabs are just black text on white background. I tried deleted the preferences file, still the same.
Any ideas?
Thank you!

Nevermind. I realized that Command-N opened a new basic window.
Solution was to select File -> Use Settings as Default.
Cheers.

Select Applications (Terminal, Preferences) Freeze On Mouse Hover

This behaviour started happening a couple of days ago. When I hover my mouse over an application (such as Terminal) it freezes with the message 'process Termainl [pid] caught causing excessive wakeups...'
Some applications (such as Google Chrome) work fine. Others (iTerm, Terminal, Hipchat) are susceptible. If the application exhibits the behaviour - without fail, simply hovering the mouse over the application window, without clicking or giving it explicit focus, will cause it to freeze.
Prior to this, my battery had swollen and the suspicion was that it was pressing against the trackpad resulting in a constant stream of interrupts. I took the battery out and am typing this without the battery - the issue persists.
I also tried disconnecting the trackpad. Same issue, even when using an external mouse to navigate. That seems to contradict the idea that it's an issue with the trackpad.

So after spraying the board with a non-conductive, plastic-safe solvent ("Superwash"), I'm seeing the behaviour in less applications.
Annoyingly, iTerm2 and System Preferences are still affected. Terminal now works, Hipchat now works.

Time Machine Terminal Preferences?

I have two issues with Time Machine.
1. 2 hourly backups is too frequent but there is no way to change this in the preferences (10.6.8).
2. Occasionally my back up disc falls off FW and I don't notice. Time Machine waits until 10days have passed before informing me 'It has been 10 days since the last backup'. This is too long, but again there is no means to change this in the preferences.
So, is there a means of setting these parameters in the Terminal?
If so, pointers in the right direction would be helpful.
I'm not a Terminal neophyte but neither am I a power user.

I just thought to check and my system has not been backed up since April 12.

Systeme preference bug :(

I work on a iBook PowerPc G4, 1.33Ghz, 512ram with OS X Tiger 10.4.11
when I open "systeme preference" then go in "desktop & screen saver" the window open and close by itself and the Apple report bug system open with the message: go there----> http://djinsanity.skyrock.com/article_1375210708.html
please help me
thanks everyone

Click here and follow the instructions.
(26392)

Mail Notification Preferences Bug

Is anybody having a problem with  mail remembering notification preferences on emails? I'm running OS X Yosemite on a MacBook Pro 13 inch (Early 2013) I've gone through the normal steps in preferences to disable the notifications and went to the Genius Bar where they showed me how to do it too. The settings aren't being remembered.

Back up all data before proceeding.
This procedure will unlock all your user files (not system files) and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.
Step 1
If you have more than one user, and the one in question is not an administrator, then go to Step 2.
Triple-click anywhere in the following line on this page to select it:
sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.
Start up in Recovery mode. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open. In that window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Terminal.app bug when minimizing or maximizing window

I am running vi in a 24x80 window. When I maximize the window, terminal replaces the top line in the file with a random line from the body of the file. When I minimize the file, the top line is replaced with another random line. For instance, I have a file with 10 lines as follows ...
I maximize the window and it now contains ...
(the top line has been replaced with line 5)
I minimize and it changes to ...
Now the top line has been replaced with line 4.
Every time I maximize or minimize the window the top line may, or may not, be replaced with a line from the body of the file. This makes writing code interesting to say the least.
Any ideas?

Hi Ahmad,
For your issue, please try the following suggestions:
Update your graphic driver;
Update your Office to the last version;
Disable all
add-ins to determine if it could be caused by the 3rd-party add-ins;
Configure your computer to reboot in
clean boot mode to determine if it could be caused by the 3rd-party services and applications;
Tips:
To have your Office applications update with Windows, go to Control Panel\All Control Panel Items\Windows Update\Change settings
Make sure the options - "Give me updates for other microsoft products when i update windows" is enabled.
Max Meng
TechNet Community Support

Code Editor preferences bugs

Hi,
Please log:
1. The Escape When Pasting In String Literals preference doesn't work: pasting a string containing single quotes inside another doesn't escape anything, resulting in invalid code.
2. The Adjust Indentation When Pasting preference never adjusts anything.
Then there's the Automatically Copy Paste Imports preference, which I have no clue as of what it's supposed to do, and I don't see anything happening that indicates it actually does something. Does anyone know more about this?
Thanks,
K.

en there's the Automatically Copy Paste
Imports preference, which I have no clue as ofwhat it's supposed to do, and I don't see anything
happening that indicates it actually does something.
Does anyone know more about this?
I suspect this is a JDeveloper hangover. Paste in some java code and JDeveloper will automatically add the import statements at the top of the file.
Actually, I suspect the last 3 in the list might all be JDeveloper hangovers and not properly implemented.

Research system preferences bug

Hello everyone, i have a little problem, when i search in the system preferences the panel with the word i'm searching hide the preferences on the right and i'm not in grade to determinate if are spotted or not.
In particular when i try to search "research" when i type the firs letters spotlight is hided by the research pane.
Thanks a lot!
A

Finish typing in the work and hit the return key.

Read Terminated Buffer bug in CVI 5.5 ? (2)

Another thing that make my headache to grow....
When I run the project inside CVI 5.01 IDE, it works but if I create
the .exe file, it stops working.
This is because the .exe file is using the CVI 5.5 RTE ?
If so, there is a way to make the .exe file using the old CVI 5.01 RTE
Ciao
Dimitri

Dimitri
I also fight with different versions of the RTE, but I found no way to use
different version on one machine.
Once you have updatet to 5.5, I found no way to run an .exe file with RTE
5.0
Stephan
Dimitri Ghinis schrieb in im Newsbeitrag:
[email protected]..
> Another thing that make my headache to grow....
>
> When I run the project inside CVI 5.01 IDE, it works but if I create
> the .exe file, it stops working.
>
> This is because the .exe file is using the CVI 5.5 RTE ?
>
> If so, there is a way to make the .exe file using the old CVI 5.01 RTE
> ?
>
> Ciao
> Dimitri

Terminal.app resize bug?

I use the Terminal.app to log into a Linux machine. I usually open up multiple tabs per window, and I run emacs in some of the terminal window. The problem is that when I resize the windows, often the window can not remember what size it's supposed to be, and sometimes switching from one tab to another triggers the window to resize to previous dimensions. It's particularly annoying when I start emacs in a tab that's confused in this way, because the window width that emacs thinks it is is incorrect, so emacs can not format the display properly. If I manually resize the window with emacs running, it snaps into place, but then the other tab gets confused.
I didn't have this problem, or it wasn't as noticeable on OSX 10.6.
Is there something I can do about this? This problem is really annoying, and Apple hasn't fixed the other Terminal.app bug I reported to them yet.

You could try iterm or iterm2
<http://iterm.sourceforge.net/>
<http://www.iterm2.com/>
You can always ssh -Y (or ssh -X) into your Linux system and export xterm's back to your Mac (although I'm not personally a fan of xterm, some people like it).
And of course there is always the gui version of emacs and have it export its X11 windows back to your Mac.
NOTE: I am not an emacs user, so anything I say about emacs is based on things I read on the intertubes :-)
You could VNC to your Linux box (although that generally speaking requires a rather fast network corrected to be anywhere usable for an editing session), also the build-in Mac OS X VNC client (Screen Sharing) does not always play nice outside the Mac family, so you should consider alternative VNC clients, such as Chicken (formally Chicken of the VNC), JollysFastVNC, tightvnc (via MacPorts.org), to name a few.
Finally, if you feel there is a real bug in Terminal that needs to be addressed, please file a bug report with Apple so they will have a chance to see and maybe fix it
BugReporter
<http://bugreporter.apple.com>
Free ADC (Apple Developer Connection) account needed for BugReporter.
Anyone can get a free account at:
<http://developer.apple.com/programs/register/>

Terminal input wrong behaviour

Basically, I have a very strange problem - when I ssh into the machine running CentOS and I open some file in nano to edit it my terminal behaves like crazy.
When I delete something it can put either a simicolon or a closing parathesis or actually delete the thing I want.
Also, the cursor can jump from one place to the other when pressing left/right key. This jumping is only along the line.
Finally, when I press left/right some characters may be overwritten by the characters from the other parts on that line where the cursor happened to be.
It almost seems like the wrong commands are being sent.
Last thing – which is not related to the terminal – if I put mission control to be triggered by Ctrl+Right I can trigger it ALSO by pressing FN. It seems to me that something is very wrong with how character input is being interpreted... Although I do not have ANY problems when typing in other apps.

The problem is a combination of the older version of nano + xterm-256color + Terminal.
The older version of nano does some odd things when moving the cursor left and right: if the cursor is one column to the left of a tab stop, moving the cursor one column to the right sends a tab (Control-I) character, and if it's one column to the right of a tab stop, moving the cursor one column to the left sends a "back tab" (ESC [ Z) sequence. I say "odd" because it's odd that it bothers using these sequences when next to tab stops instead of moving the cursor left/right in the same manner as it does when it's farther away from a tab stop.
The reason this is a problem is that Terminal doesn't support the "back tab" escape sequence. So, nano thinks it moved the cursor to the left one column, but Terminal hasn't moved it, and further editing and cursor movement on that line is out of synch with what's displayed in the terminal and it gets progressively more confusing looking. And since it only occurs when moving one character to the left to a tab stop, the user-observable behavior can seem even more surprising and unpredictable.
Now, it only uses "back tab" if the terminfo file says that the terminal supports it. It does this with a "cbt" entry. You can see this with the "infocmp xterm-256color" command, which shows "cbt=\E[Z". This code is supported by modern Xterm and is found in several variations of the xterm terminfo entry, but xterm-color represents an older branch of Xterm and does not include "cbt". So, switching to xterm-color gives you something roughly similar to xterm and xterm-256color, except without "cbt" (and some important behaviors like Background Color Erase and 256 colors) and so this older version of nano behaves better in combination with xterm-color and Terminal.
So, you can work around the problem by setting the TERM environment variable to xterm-color (or, really, any terminfo value that doesn't include "cbt" and is reasonably compatible with Terminal), or by upgrading the older nano on the remote host to a newer version that doesn't have this somewhat odd cursor movement behavior. You could also create a custom terminfo file that's a copy of xterm-256color with cbt removed (assuming you're comfortable creating and editing custom terminfo files).
The easiest way for users to set the TERM value is with the popup menu in Terminal > Preferences > Settings > [profile] > Advanced > Declare terminal as. However, that sets it for every program used with that profile. I recommend one of two approaches:
1. Duplicate (in the "action" menu below the profiles list) the profile you want to use with the remote host and set the "Declare terminal as" value (which just sets the TERM environment variable), then always use that profile for terminals that you use to ssh to CentOS machines. In fact, if you only have one or two remote hosts for which this is a problem, you could customize "… > Settings > Shell > Startup > Run command" to include the "ssh …" command, which will connect to the remote host automatically when you create a new terminal with that profile. Then create a similar custom profile for each remote host.
2. Invoke nano with something like "TERM=xterm-color nano" to set the terminfo value only when running the older version of nano. You could even turn this into an alias, e.g., "alias nano='TERM=xterm-color nano'". If you only have one remote host (or you don't mind doing this on mulitple hosts), customise the appropriate shell startup script to do this so it only does this when invoking nano on that host. Or just remember to "export TERM=xterm-color" after you login to the remote host.
As always, this forum is not an official means to provide feedback to Apple. If this issue is important to you, please file a bug report either at <http://www.apple.com/feedback/macosx.html> (set Feedback Area to Applications/Utilities) or <http://developer.apple.com/bugreporter/> (requires registering for a free developer account). Apple uses reports like these to prioritize work and to decide what's important to put in system updates.

Terminal preferences bug

Similar Messages

Maybe you are looking for