[ Note added 2013-05-13: I now have a scrot-based shell script that does this better IMHO than does Imagemagick. See http://martesmartes.blogspot.com/2013/05/screenshots-in-lxde-mate-etc.html ]
The Gnome screenshot tool has always fallen a bit short in the usability department. How do I change the default directory for storing screen shots? How do I make it default to "select area to grab"? I've always just lived with it, but tonight decided to do a little legwork to learn how to make it default to what I wanted, and I found something better.
I've long used ImageMagick for image editing. In some respects Mirage is easier to use, but Mirage doesn't handle as many image formats. I suppose the GIMP is more popular, but it's a usability nightmare.
Google led me to a wonderful page at the Webmaster Tips Blog.
Assuming one has ImageMagick installed, taking a screenshot of a selected area on the screen is as simple as typing
import filename.imagetype
and then selecting the area of the screen to copy.
As a concrete example, suppose I want to capture some text from above in file selectArea.png:
import selectArea.png
The result is this, in a file called selectArea.png:
I like it.
Showing posts with label Gnome. Show all posts
Showing posts with label Gnome. Show all posts
Thursday, October 25, 2012
Sunday, June 3, 2012
Zeitgeist Spyware Framework Installed by Default in Linux Mint 13
I thought I would take a moment to pull together information on the Zeitgeist monitoring system which has become a part of Gnome and is inexplicably included within Linux Mint. First, Zeitgeist is not itself spyware, but it collects much information about a user that would be one-stop shopping for any spyware that finds its way onto a system. It provides no discernible benefit, and is dangerous to keep around, so get rid of it. More information:
- My take on what Zeitgeist is.
- Zeitgeist was dropped as a component for Gnome 2.32 but the Ubuntu folks decided life wouldn't be complete without a spyware framework.
- Removing Zeitgeist.
Labels:
Gnome,
Linux Mint 13,
privacy,
spyware,
zeitgeist
Thursday, May 31, 2012
Why I'm Not Using Cinnamon
I was using Cinnamon on my desktops, and went back to Gnome classic no effects. This with Linux Mint 12.
I installed Linux Mint 13 RC on my laptop, and switched to Mate.
Mate works fine on my laptop. Mate keyboard shortcuts for volume up/down and play/pause do not work on my desktops.
So, why is switching to Cinnamon a bad idea, IMHO?
I installed Linux Mint 13 RC on my laptop, and switched to Mate.
Mate works fine on my laptop. Mate keyboard shortcuts for volume up/down and play/pause do not work on my desktops.
So, why is switching to Cinnamon a bad idea, IMHO?
- Cinnamon has no no grouping of menu items on the panel.
- Bumping a window being dragged against the top panel causes it to maximize--a most annoying bug.
- Nautilus 3.2.1 under Cinnamon shows selected files as pink with no text, or perhaps pink text on a pink background. Sometimes I like to be able to see the name of and related info for a selected file. Really. This is with the list view, which is my preferred default.
- Under Cinnamon, ImageMagick's pan icon is missing window controls (e.g., close) which should be in the upper right.
- [ Added 2012-06-02: Cinnamon removes the ability to move the save file dialog within a web browser. ]
I do like the hot corner, but it doesn't outweigh just the lack of grouping of menu items let alone the other problems I'm seeing with Cinnamon.
Saturday, May 19, 2012
Starting out in Cinnamon (w/Linux Mint 12)
[ Note added 2012-05-31: I no longer use Cinnamon. Here's why: http://martesmartes.blogspot.com/2012/05/why-im-not-using-cinnamon.html ]
I've been using Linux Mint 12 for awhile, and 11 briefly before that, ever since I got fed up with Gnome's decision that the user interface is unimportant.
Thursday a grad student asked me if I'd tried Cinnamon, which apparently he has liked on a few different platforms. This left me with a choice: work on the finals I would be delivering, or mess with Cinnamon. I chose Cinnamon, though I now must admit that my IS 247 exam suffered from insufficient proofreading.
I like Cinnamon, and recommended it to a friend, who didn't see much difference between it and what he had been running (probably Gnome Classic or Mate) on a Mint system. I responded with a summary of my experiences with Cinnamon to date:
First, switching to Cinnamon on my recommendation should be worth some placebo effect. If not:
The panels are configurable, and it's okay to have just one.
TFM: the wrench & screwdriver in the main menu leads to a different place from System Tools|System Settings wrench & screwdriver. If you select Menu|Wrench & Screwdriver, one of the options is Hot Corner. Make it visible, place it in a corner not otherwise critically used (it's translucent) and play with it.
I was using Gnome Classic with no effects, because with effects keyboard shortcuts didn't work. With Mate my volume controls (alt-up, alt-down) didn't work. This does everything Mate does without breaking keyboard shortcuts (big deal) and also allowing effects (not a big deal).
I really like Hot Corner.
Cinnamon has more themes than Gnome Classic, but still not one I really like. A little googling, though, led me to a page on creating themes, and it does look simple, except I'll be editing CSS and am unclear regarding what some of the tags are. I'll either find docs or experiment.
What I really want are larger fonts in the panel and top bars on windows that change colors noticeably between selected and not selected.
There is one clear-cut bug that I've seen: Under Cinnamon, Gnome Terminal 3.0.1 doesn't consistently switch its cursor to solid block (from outline) when the window has focus. A minor aggravation.
I have an old (ca. 12/2005) Dell laptop running Ubuntu 10.4 LTS. Ubuntu's LTS is rather short, and has expired, so I think I'll blow that away in favor of the Mint13 RC, Cinnamon, and Mate. If Mate is less buggy in the Mint 13 environment than Mint 12 (they use the word mature to describe it, but I have yet to see evidence of that) it might be a good choice. Anyhow, the new Mint 13, Cinnamon, and Mate on modest hardware seems worth learning about.
I've been using Linux Mint 12 for awhile, and 11 briefly before that, ever since I got fed up with Gnome's decision that the user interface is unimportant.
Thursday a grad student asked me if I'd tried Cinnamon, which apparently he has liked on a few different platforms. This left me with a choice: work on the finals I would be delivering, or mess with Cinnamon. I chose Cinnamon, though I now must admit that my IS 247 exam suffered from insufficient proofreading.
I like Cinnamon, and recommended it to a friend, who didn't see much difference between it and what he had been running (probably Gnome Classic or Mate) on a Mint system. I responded with a summary of my experiences with Cinnamon to date:
First, switching to Cinnamon on my recommendation should be worth some placebo effect. If not:
The panels are configurable, and it's okay to have just one.
TFM: the wrench & screwdriver in the main menu leads to a different place from System Tools|System Settings wrench & screwdriver. If you select Menu|Wrench & Screwdriver, one of the options is Hot Corner. Make it visible, place it in a corner not otherwise critically used (it's translucent) and play with it.
I was using Gnome Classic with no effects, because with effects keyboard shortcuts didn't work. With Mate my volume controls (alt-up, alt-down) didn't work. This does everything Mate does without breaking keyboard shortcuts (big deal) and also allowing effects (not a big deal).
I really like Hot Corner.
Cinnamon has more themes than Gnome Classic, but still not one I really like. A little googling, though, led me to a page on creating themes, and it does look simple, except I'll be editing CSS and am unclear regarding what some of the tags are. I'll either find docs or experiment.
What I really want are larger fonts in the panel and top bars on windows that change colors noticeably between selected and not selected.
There is one clear-cut bug that I've seen: Under Cinnamon, Gnome Terminal 3.0.1 doesn't consistently switch its cursor to solid block (from outline) when the window has focus. A minor aggravation.
I have an old (ca. 12/2005) Dell laptop running Ubuntu 10.4 LTS. Ubuntu's LTS is rather short, and has expired, so I think I'll blow that away in favor of the Mint13 RC, Cinnamon, and Mate. If Mate is less buggy in the Mint 13 environment than Mint 12 (they use the word mature to describe it, but I have yet to see evidence of that) it might be a good choice. Anyhow, the new Mint 13, Cinnamon, and Mate on modest hardware seems worth learning about.
Labels:
Cinnamon,
Gnome,
Linux Mint 11,
Linux Mint 12,
Linux Mint 13,
Mate,
ubuntu,
usability
Monday, January 9, 2012
Wikipedia Can't Spell Mate, No, Wait, the Gnome Project Can't Spell Mate
All along I've been spelling mate as mate, which is the spelling that seems to prevail within the Linux Mint 12 Documentation. I was annoyed that Wikipedia spells it maté, an example of hypercorrection. Mate is an herb or a tea made from the herb. This is what the project is named after, and is the correct spelling. Someone decided that Americans would be more likely to pronounce correctly if it is misspelled as maté. The problem here is threefold:
- the misspelling maté puts the emphasis on the wrong syllable,
- the misspelling maté is a different word, and
- maté is first person preterit form, I killed. Okay, two and three are arguably the same objection.
The discussion at the Wikipedia maté page saved me from making a change to the page that someone would have to back out of later. Someone pointed out that the spelling is incorrect, but someone else pointed out that the spelling is the one used by the gnome project, and it's not Wikipedia's place to correct the spelling of a project name, but rather to use it as-is. I agree, but I will not be using the misspelling.
Thursday, September 22, 2011
Ubuntu Unity: a Guide for the Perplexed
After a little time with Unity, I've decided it really is simple to work with. If you can figure out how to get to the command line (I had to Google it), start with the following two commands:
sudo apt-get install gnome // kde is fine too
sudo apt-get remove unity
Log out, and then back in, and you should find a much more usable system.
sudo apt-get install gnome // kde is fine too
sudo apt-get remove unity
Log out, and then back in, and you should find a much more usable system.
Tuesday, September 6, 2011
Gnome 2.32.1 Missing Scrollbars
Gnome 2.32.1, as delivered in Ubuntu 11.04, is missing full scrollbar functionality in some applications. Instead of a scrollbar, on the right edge of the window is a small target that, when the mouse is over it, creates a dragging tool for scrolling up and down. This is okay so far as it goes, and does save some screen real estate, which is great. However, the ability to click within the scrollbar to move up or down a screenfull is gone.
I see nothing in the options to return full scrollbar functionality, and it is vexing that many applications do have regular scrollbars, and some, or at least Nautilus 2.32.2.1, do not. So how do we fix it. There was a brief discussion at superuser.com in which one person totally missed the point regarding why this is a problem and a couple suggestions were given, neither of which seemed complete. This is how I restored scrollbar functionality, based on the guidance at superuser:
sudo apt-get remove overlay-scrollbar
sudo apt-get autoremove --purge liboverlay-scrollbar-*
sudo su
echo "export LIBOVERLAY_SCROLLBAR=0" > /etc/X11/Xsession.d/80overlayscrollbars
I see nothing in the options to return full scrollbar functionality, and it is vexing that many applications do have regular scrollbars, and some, or at least Nautilus 2.32.2.1, do not. So how do we fix it. There was a brief discussion at superuser.com in which one person totally missed the point regarding why this is a problem and a couple suggestions were given, neither of which seemed complete. This is how I restored scrollbar functionality, based on the guidance at superuser:
sudo apt-get remove overlay-scrollbar
sudo apt-get autoremove --purge liboverlay-scrollbar-*
sudo su
echo "export LIBOVERLAY_SCROLLBAR=0" > /etc/X11/Xsession.d/80overlayscrollbars
People trying to do this will likely want to escape the asterisk in the second line. It is not clear to me whether one really needs the first line given the second, but this worked.
My remaining question is why would the Gnome team reduce the scrollbar functionality without providing users with a clear-cut way to revert to full scrollbar functionality? If some prefer this behavior, which seems reasonable, then there should be an option somewhere within Gnome or within individual applications.
Thursday, May 6, 2010
Back to Gnome
I had been using Xfce on one of my desktops for a few months. I like it better than Gnome in some respects, largely because it's less bloated. However, I was repeatedly frustrated by its inability to follow the mouse with the focus. I'm a "focus follows mouse" person, and multiple times a day I would move the mouse from one window to another, passing over an intermediate window, and the focus would stay with the intermediate window. So I'd start typing, thinking the input would go to the window under the mouse. But, alas, no, the focus had remained with a window the mouse had passed over. This sometimes had deleterious effects, and so I've returned to Gnome.
Sunday, February 14, 2010
Xfce Focus Stealing
I configure the window manager for "focus follows mouse" rather than the Windows-like "click to focus." If the mouse pointer indicates where my attention is, why force an extra click? Ok, the real reason is that this is what I'm used to from SunOS and Solaris in the late '80s through the mid '90s. What I say below may not apply to the click to focus crowd--I just don't know.
Under the focus tab in Xfce 4.6.1's Window Manager Tweaks is an undocumented checkbox labeled "Honor standard ICCCM focus hint." At Xfce.org, the most recent documentation is for version 4.2, and 4.2 did not have this "feature." The ICCCM is a large document, and perhaps by investing considerable time one could figure out what ICCCM focus hints are, but I don't have that time. What I have noticed is that if I select both that and "activate focus stealing prevention," applications steal focus willy-nilly. I think most users who do a lot of typing, like, say, programmers, people who create documents, people who send e-mail, etc., will not want Xfce to honor ICCCM focus hints.
The other thing I noticed recently, being new to Xfce, is that the desktop is very, very sluggish compared to Gnome. This alone was bad enough that I considered going back to Gnome. However, last week, being forced to stay at home because of the snow, I noticed another window manager option, "Delay before window receives focus." I set this to zero, or as close to zero as it would let me, and all of a sudden the performance was fairly snappy. So the Xfce default is to give the illusion of poor performance, but eliminating that delay is a huge improvement.
I like Xfce as a window manager, but the documentation is in such bad shape that I cannot recommend it to others.
Under the focus tab in Xfce 4.6.1's Window Manager Tweaks is an undocumented checkbox labeled "Honor standard ICCCM focus hint." At Xfce.org, the most recent documentation is for version 4.2, and 4.2 did not have this "feature." The ICCCM is a large document, and perhaps by investing considerable time one could figure out what ICCCM focus hints are, but I don't have that time. What I have noticed is that if I select both that and "activate focus stealing prevention," applications steal focus willy-nilly. I think most users who do a lot of typing, like, say, programmers, people who create documents, people who send e-mail, etc., will not want Xfce to honor ICCCM focus hints.
The other thing I noticed recently, being new to Xfce, is that the desktop is very, very sluggish compared to Gnome. This alone was bad enough that I considered going back to Gnome. However, last week, being forced to stay at home because of the snow, I noticed another window manager option, "Delay before window receives focus." I set this to zero, or as close to zero as it would let me, and all of a sudden the performance was fairly snappy. So the Xfce default is to give the illusion of poor performance, but eliminating that delay is a huge improvement.
I like Xfce as a window manager, but the documentation is in such bad shape that I cannot recommend it to others.
Saturday, July 11, 2009
gFTP Much Nicer than Nautilus for sftp
Gnome ships with GUI sftp support built into nautilus, but it's not ideal. I was living with it, and do prefer it over the command line version (I'm getting lazy in my old age) but recently have been evaluating xfce as an environment. This is a whole different story, but I'd like to find a less bloated, less buggy environment than Gnome. Xfce doesn't seem to ship with a GUI sftp client, which is totally fine--why ship software that many users won't use?
Looking around, I found gFTP. So far, it seems gFTP is as good as nautilus in every respect. A major difference, however, is that when transferring files to and fro, gFTP maintains modification times. This way, if I have two copies of the same file in two (or more) places, they all have the same modification time. Seems pretty basic and pretty obvious--and very important--but nautilus gets it wrong.
Is my preference for a GUI sftp client really a sign of laziness? I don't think so. In many cases command line tools are quicker and easier, but when maintaining web directory trees it's nice to be able to quickly glance at two directories and see if their contents match. gFTP does have one quirk that's inconvenient in this regard, however, in that it sorts files and directories differently. IMHO, this is another sign of Linux developers not understanding Unix: a directory is, like a file, a link in a directory, darn it, so sort it like other links.
Looking around, I found gFTP. So far, it seems gFTP is as good as nautilus in every respect. A major difference, however, is that when transferring files to and fro, gFTP maintains modification times. This way, if I have two copies of the same file in two (or more) places, they all have the same modification time. Seems pretty basic and pretty obvious--and very important--but nautilus gets it wrong.
Is my preference for a GUI sftp client really a sign of laziness? I don't think so. In many cases command line tools are quicker and easier, but when maintaining web directory trees it's nice to be able to quickly glance at two directories and see if their contents match. gFTP does have one quirk that's inconvenient in this regard, however, in that it sorts files and directories differently. IMHO, this is another sign of Linux developers not understanding Unix: a directory is, like a file, a link in a directory, darn it, so sort it like other links.
Thursday, August 14, 2008
Gnome Caps Lock, Insert Keys
Some time back I discussed disabling the caps lock and insert keys in gnome. In Hardy Heron (Ubuntu 8.04) the caps lock suggestion I made stopped functioning. Here's the new fix:
#! /bin/sh
# Kills the stoopid caps lock and insert keys.
file=/tmp/capsLockDisabled
if test ! -e $file ; then
/usr/bin/xmodmap -e "keycode 66 = "
/usr/bin/xmodmap -e "keycode 106 = "
/bin/date >$file
fi
I'm still amazed every time a new release of Gnome comes out and they still don't give the user a way of getting rid of these. As a system staffer in the Ohio State CIS department (Frank Adelstein? Frodo?) once said: "The caps lock key shouldn't be right next to keys that are used all the time. It should be somewhere off in the next room." Ok, that was a paraphrase, not really a quote, and I don't remember who I'm paraphrasing.
Anyhow, the above script does it. I call the script from my .cshrc. Those of you who use bash (yuck) would put it in your .profile.
Labels:
caps lock,
Gnome,
insert key,
ubuntu
Evince Bug Workaround
Evince has been a continuous battle for me ever since I switched from KDE to Gnome. Ok, more of an occasional annoyance than a continuous battle, and the various problems I've had with Evince convinced me to install and primarily use kpdf for awhile. Well, I've got a fresh Ubuntu install, and didn't want to litter it with all the junk that comes along with kpdf, so I've been using evince. However, evince wants to print everything in A4 format. Yes, my printer defaults are letter. Yes, the PDF documents are letter size. Yes, /etc/papersize contains one line, letter.
I remember wasting an afternoon on this sometime back, so the question became tell evince to use letter every single time I print, go back to kpdf, or waste another afternoon with no guarantee of better results than last time.
First tried the obvious thing:
Totally useless. Instead of placing everything in one place, the evince folks have decided to scatter documentation all over the place at their web site. But, unlike last time, Google found me a solution, a recent blog entry by Dominique Cimafranca at UbuntuLiving. He apparently uses bash, and so suggests a change to the user's .profile. I use tcsh, and so added this line to my .cshrc:
UbuntuLiving suggests that after making this change, one log out and then back in. Not necessary. Any new xterm opened from that point will have the correct setting, or one can just type
in an existing xterm (or gnome-terminal, or konsole, or whatever) and LC_PAPER is set. Then the next time you type the evince command, it'll actually print correctly with no gyrations by the user. Imagine that.
Is this a bug within evince? The evince folks may think not, but Google is unable to find any mention of LC_PAPER at site:www.gnome.org/projects/evince/ and the man page is useless, so the documentation is woefully lacking. Yeah, I'm using an undocumented feature. It'll probably break with the next release.
I remember wasting an afternoon on this sometime back, so the question became tell evince to use letter every single time I print, go back to kpdf, or waste another afternoon with no guarantee of better results than last time.
First tried the obvious thing:
man evince
Totally useless. Instead of placing everything in one place, the evince folks have decided to scatter documentation all over the place at their web site. But, unlike last time, Google found me a solution, a recent blog entry by Dominique Cimafranca at UbuntuLiving. He apparently uses bash, and so suggests a change to the user's .profile. I use tcsh, and so added this line to my .cshrc:
setenv LC_PAPER en_US.UTF-8@letter
UbuntuLiving suggests that after making this change, one log out and then back in. Not necessary. Any new xterm opened from that point will have the correct setting, or one can just type
source ~/.cshrc
in an existing xterm (or gnome-terminal, or konsole, or whatever) and LC_PAPER is set. Then the next time you type the evince command, it'll actually print correctly with no gyrations by the user. Imagine that.
Is this a bug within evince? The evince folks may think not, but Google is unable to find any mention of LC_PAPER at site:www.gnome.org/projects/evince/ and the man page is useless, so the documentation is woefully lacking. Yeah, I'm using an undocumented feature. It'll probably break with the next release.
Saturday, July 26, 2008
Gnome's Messed-Up GLSlideshow
For some inexplicable reason, in Ubuntu 8.04, the screen saver GLSlideshow has no configuration options. There's a long discussion of this issue in the Ubuntu Forums, suggesting that a lot of people have found this perplexing. I think the best how-to on managing GLSlideshow is provided by Bits 'n Pieces.
Labels:
GLSlideshow,
Gnome,
screensaver,
ubuntu
Tuesday, February 5, 2008
Gnome Deficiencies
Two things that should be much more obvious in Gnome, if not actually defaults:
xmodmap -e "remove lock = Caps_Lock"
xmodmap -e "keycode 106 = "
In other words, disable caps lock, and disable the insert key. Why these aren't even offered as choices in the keyboard configuration menu is simply befuddling, not to mention the time wasted by many, many people if Google search results are any indication.
Labels:
caps lock,
Gnome,
insert key,
shift lock,
xmodmap
Saturday, January 5, 2008
Gnome and Caps Lock
Gnome still (as of Gutsy Gibbon) doesn't have an option under "Keyboard Preferences | Layout Options | CapsLock key behavior" to simply disable the caps lock altogether. This is a common enough need that a number of people have provided solutions for a variety of environments. Some are collected here. KDE provides this feature, as opposed to the esoteric options provided by Gnome.
A related issue is that of disabling the insert key in emacs. Emacs is sufficiently powerful that the insert key is unnecessary--this isn't Microsoft Word--and so there should be an easy way to disable that.
A related issue is that of disabling the insert key in emacs. Emacs is sufficiently powerful that the insert key is unnecessary--this isn't Microsoft Word--and so there should be an easy way to disable that.
Labels:
caps lock,
Gnome,
insert key,
KDE
Subscribe to:
Posts (Atom)
