Sometimes when reading a binary file your terminal font may be set to junk values and whatever you type will appear as junk. This may happen when reading a binary file through cat command, opening the raw device files like /dev/random /dev/urandom, or reading /proc/kcore memory file. Below screen shot shows how terminal looks when this happens,
There is an easy way to fix this problem by resetting the terminal. Yes typing reset command in the terminal will reset your terminal back to normal state.
When applications are running in full screen, notifications does not appear in cinnamon desktop. When running applications in full screen like watching a movie in media player, viewing firefox in full screen and if there is any notification bubbles appearing it doesn’t show up. It only appears below the full screen application. Whatever be the criticality of the notification it doesn’t appear. This could lead to many problems like not getting to know when the battery is getting low, when disconnected from a network etc.
Ideally notifications should appear on top of whatever application the user is running, but this is not the case.
This bug could be reproduced by running the command notify-send in terminal as given below,
sleep 10 ; notify-send hi
and run an application in full screen and wait for 10 secs and check whether ‘hi’ appears. If it doesn’t appear, you are affected by this bug.
I have reported this bug in launchpad linux mint page here: https://bugs.launchpad.net/linuxmint/+bug/1162198
If you can reproduce this go and subscribe to this bug by clicking ‘Yes,this bug affect me’ in the bug page.
Power management in Linux mint desktop does not kick in when the system is booted upon, it only starts up when the cinnamon desktop is logged into. This should not be the case because when the system is powered up and left untouched, the brightness settings does not work, battery management settings doesn’t work. When this is the case battery gets drained completely.
By default in power manager settings, system is configured to take critical battery action only when 2 minutes of power is remaining. Thus most people wouldn’t have noticed the seriousness of this problem. I configured my system to take critical battery action when battery is at 25 % by modifying the dconf-editor settings and confirming this is the case.
I have reported a bug to Linux mint in launchpad here https://bugs.launchpad.net/linuxmint/+bug/1155691
If you are facing this bug, please add a comment against this bug.
I’m afraid this is how gnome3 desktop behaves too. This must affect all the linux distributions using cinnamon and gnome3 desktop. At this moment i have no idea what are all the distributions affected. If your version of linux is affected, please report it to your distributions authors at the appropriate place.
I guess this is more of a design error than of a bug
Some scripts that work fine when run manually in a shell environment will just fail when scheduled with cron. This is due to shell environment variables not available to those scripts when cron executes the scripts. You can verify this by running env or printenv commands in both the shell in which you manually execute the script and in cron by schedule it to the nearest minute and writing it to a file.
# m h dom mon dow command
35 * * * * env > /tmp/env.log
By comparing both outputs you can find that the environment variables available in cron are very limited.
Most errors will arise due to commands in your script not available in location set by cron environment PATH variable. You can compare the value of PATH variable in both outputs and tell that the executable paths cron looks in is very limited. You can fix this by giving the full path to commands in your shell script, but you have to look for where the executables are located and modify all those scheduled scripts.
However there is one easy fix to this problem. The important thing to note is cron allows you to set environment variables in the crontab file. So you could just add the variables you wanted to be available to cron at the top of the crontab file as shown below.
# m h dom mon dow command
38 * * * * env > /tmp/env.log
Now schedule the script again and check the output of /tmp/env.log file. You can see that the values you passed were availabe to cron. By this way you can run those scripts just the way it is without any modifications.
Gnome desktop does not allow users to set the values for battery critical state, Power settings will only allow users to set what action is to be taken when the battery is critical. By default it is considered critical when battery backup time is 5 minutes and it will initiate battery critical action when backup time remaining is 2 minutes. This default behavior is questionable because 2 minutes will not be sufficient for all users to find a power source and as most batteries used today are lithium-ion batteries, their life will get significantly reduced by this default behavior when drained so low so often.
Fortunately, this can be changed in configuration editor. systems using older Gnome versions such as Gnome2 desktops had a tool called Gconf-editor to change these configuration settings. Newer Gnome versions such as systems using Gnome3 desktop use a tool called dconf-editor to make changes to these configuration settings.Install this tool by using below command from terminal
sudo apt-get install dconf-editor
After installing open dconf-editor and look for following path in the left pane
In the right pane look for the fields,
and change the time values for the fields according to your preferences.Note that the time is defined in seconds.
Description for the fields and the type of value it accepts will be available at the bottom pane, when you select the fields.
Alternatively, if you want your system to consider the battery percentage instead of remaining time, uncheck the key
and modify the keys
to your preference.Now your system should take the values you defined after the next boot or restart your system for the settings to take effect immediately.
All of a sudden my eclipse IDE started showing empty dialog box after working fine for some days. Most of the solutions found talks about Xulrunner problem that doesn’t work for me. A simple solution would be to just move your workspace folder to a different location or delete it if don’t have any important projects inside it and start eclipse again.Now you are good to go.