I have an image I wish to colorize using a picked color. What is the handiest/easiest way to do this in GIMP?
I’ve tried my best by checking the palette for my picked color’s HSV, then using it as starting point to find corresponding HSL values for the Colorize window. But this seems absurdly difficult and imprecise. I don’t do much image processing, but I repeatedly come across this specific problem, so there must be a better way that I just don’t know about.
Hi Gary. I now tested this in a VM running up-to-date Precise and am happy to report the problem no longer occurs. I’m thus marking this as being fixed.
Apparently this is now supported; at least the following seems to work under 12.04:
$ qdbus org.gnome.Nautilus /org/gnome/Nautilus org.gnome.Nautilus.FileOperations.CopyFile "file:///source/directory" "*" "file:///destination/directory" ""
where /source/directory is the absolute path to your source directory, * is the glob for file[s] to copy,/destination/directory is your destination directory and the last ”” is for destination file name. Note that you need to have the last one there even if it’s empty as in here, to fulfill the method signature. Also, if you specify a target name and have multiple source files, they’ll all get copied to that one destination file, giving an overwrite prompt for each file after the first one (which may or may not be what you want).
Sorry, the GM965 Express is the chipset, that one has a Mobile Intel GMA X3100 display adapter.
Confirming this on another G31 (MSI MS-7525). Haven’t seen similar on 5 other Precise setups I have, including laptops with Intel 855GM and GM965 Express on the graphics (the G31 has GMA 3100).
Here’s why this is broken: logging out != shutting down. Why does the sync block logout instead of continuing in the background, and just blocking any attempts to *actually* shut down? The way it currently is makes it impractical to use U1 to sync my users’ config, because they’re blocked from fast user switching by the wait on every logout.
I’d love to, if only a) I knew how to bake bread b) I didn’t suck at baking in general and c) had the time.
Is it different from rye bread root?
Here’s a patch that worked for me. It adds some lines to what becomes /usr/share/pyshared/blueman/plugins/applet/NMPANSupport.py during installation, to set up variables that are otherwise left initialized to ’None’, hence the error when they’re used later on.
Note that I don’t know anything about DBus, have barely glimpsed at Python prior to this, and in particular have no knowledge of how Blueman’s developer intended for things to work, so apply at your own risk.
You make your own bread? That’s so cool!
Steps to reproduce:
1. Select a tag (with photos attached to it)
2. Select the associated photos (Ctrl-A)
3. From the Events menu, select ”New Event…”
4. Repeat steps 1. & 2. for another tag
5. Try to create a new event as in step 3.
What I expect to happen:
To be able to create a new event just as before.
What happens instead:
The ”New Event…” menu item is ghosted and won’t become enabled again unless I shut down Shotwell and restart it.