Re: Running KDE apps under GNOME
On May 29 2010 22:53 +0200, from luca.mercia...@student.ulg.ac.be (Merciadri Luca): I have noticed that running KDE apps under GNOME takes a lot of time once I have not launched any such apps since the beginning of the session. I believe this is normal. If you run the KDE application from within a terminal, you should see a lot of support services being started before the application actually launches. -- Michael Kjörling .. mich...@kjorling.se .. http://michael.kjorling.se * . No bird soars too high if he soars with his own wings . * * ENCRYPTED email preferred -- OpenPGP keys: 0x32D6B8C6, 0xBDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments * signature.asc Description: Digital signature
Re: RAW photo images
On May 21 2010 20:24 -0700, from jerjoz.for...@gmail.com (jeremy jozwik): do you have any access to .cr2 files to see if ufraw works with those? .CR2 is not a single format, but UFRaw works with those produced by the 50D, along with a large number of other cameras' raw formats. There is a camera compatibility list at http://ufraw.sourceforge.net/Cameras.html. -- Michael Kjörling .. mich...@kjorling.se .. http://michael.kjorling.se * . No bird soars too high if he soars with his own wings . * * ENCRYPTED email preferred -- OpenPGP keys: 0x32D6B8C6, 0xBDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments * signature.asc Description: Digital signature
Re: RAW photo images
On May 21 2010 15:03 -0400, from ckro...@frankensteinface.com (Charles Kroeger): Does anyone running Debian, (not Umbuto) use 'raw-therapee' or know of a good raw image processor that does well with 'our' distro? I use F-Spot for photo management and UFRaw for raw conversion; these work well for me with my Canon EOS 50D. -- Michael Kjörling .. mich...@kjorling.se .. http://michael.kjorling.se * . No bird soars too high if he soars with his own wings . * * ENCRYPTED email preferred -- OpenPGP keys: 0x32D6B8C6, 0xBDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments * signature.asc Description: Digital signature
Remapping mouse button 8 of 9 - parameter out of range, says xmodmap on Squeeze
I have been trying to get the thumb button of my mouse to act as a middle button (paste, in most applications). So far I haven't had much luck in Squeeze (it was much easier in Lenny), but earlier today I had a flash of inspiration and tried clicking the wheel, which worked. However, it's pretty hard to click (high physical resistance), and the thumb button is really convenient for this purpose, so I started looking. xev to the rescue; the mouse wheel click (first) is button 2, and the thumb button (second) is button 8: ButtonPress event, serial 31, synthetic NO, window 0x1c1, root 0x124, subw 0x1c2, time 763702, (47,35), root:(918,556), state 0x10, button 2, same_screen YES ButtonPress event, serial 31, synthetic NO, window 0x1c1, root 0x124, subw 0x1c2, time 784661, (34,30), root:(905,551), state 0x10, button 8, same_screen YES (Obviously, there's a lot more messages there, but I believe these are the most interesting.) So, the natural next step is to try to use xmodmap to remap physical button 8 to logical button 2. However, xmodmap doesn't quite like that, or maybe I'm getting the syntax wrong (saying 1 8 3 ... 7 8 9 gives the same output): $ xmodmap -e pointer = 1 2 3 4 5 6 7 2 9 Warning: Only changing the first 9 of 13 buttons. X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 116 (X_SetPointerMapping) Value in failed request: 0x2 Serial number of failed request: 9 Current serial number in output stream: 9 $ ...and the buttons still show up as a straight 1:1 mapping in the xmodmap -pp output, with 13 pointer buttons defined. The funny thing is, if I list all 13 supposed buttons in sequential order, xmodmap has no complaints. (If I list 9, it warns me that I didn't list all of them, but otherwise has no complaints.) I put the following into the pointer section of my xorg.conf for a short while (inspired by the Xorg.0.log snippet below), but it didn't seem to make any difference: Option Buttons 9 The weird thing is in /var/log/Xorg.0.log; it is current, and grep -i buttons gives me: $ grep -i buttons /var/log/Xorg.0.log (II) ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons (**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5 (II) Macintosh mouse button emulation: Found 3 mouse buttons (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5 $ I have a Wacom tablet hooked up over USB but it seems to be unrelated to this, as I get the same log entries with it disconnected through a reboot. So what's up with this Macintosh mouse button emulation, and could it be related to my difficulties? If so, how do I disable it to test that hypothesis? I tried Googling but didn't come across anything that looked particularly helpful, mostly people posting their own Xorg logs that happen to include the same lines. Any suggestions for what to try would be greatly appreciated, as this is starting to bug me somewhat. -- Michael Kjörling .. mich...@kjorling.se .. http://michael.kjorling.se * . No bird soars too high if he soars with his own wings . * * ENCRYPTED email preferred -- OpenPGP keys: 0x32D6B8C6, 0xBDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments * signature.asc Description: Digital signature
Re: Moving a drive to another computer
On May 19 2010 12:46 -0400, from v...@michvhf.com (Vince Vielhaber): What problems (and solutions) should I be expecting when she installs the drive in her computer? I'm assuming the network setup will be one problem. If you use a generic kernel binary and install most variations of hardware-specific packages (thinking xserver-xorg-video-*, for example), my experience is that the issues should be minimal. The default Debian installation does this. My background is mainly in FreeBSD. If a drive is set up as being /dev/ad0 and the other machine sees it as /dev/ad4 it won't complete the boot, it'll complain with a cannot mount root error. Will that be an issue with Debian? You can use UUIDs instead of physical devices, and the kernel will find the partition in question regardless of where it is physically hooked up. The main downside is that UUIDs are rather opaque, but unless your friend is planning on having a lot of drives in her PC or mess around with /etc/fstab and the boot loader configuration, this should be a non-issue. If it is, look up labels - they work largely the same but are human-assigned and human-readable. As far as I have gathered, whenever Linux expects a physical device node such as /dev/hda2 or /dev/sdb1, you can instead pass a string on the format UUID=long-hexstring-with-dashes. So an example fstab entry might look like this: UUID=1e7c6b1a-5c25-4efa-866c-9a6a086b0292 / ext3 errors=remount-ro 0 1 In the boot loader configuration, you'd pass the same kind of string to the kernel through the root parameter, like so: kernel /kernel-binary root=UUID=1e7c6b1a-5c... ro ... The contents of /dev/disk/by-uuid Co will be very helpful. -- Michael Kjörling .. mich...@kjorling.se .. http://michael.kjorling.se * . No bird soars too high if he soars with his own wings . * * ENCRYPTED email preferred -- OpenPGP keys: 0x32D6B8C6, 0xBDE9ADA6 * * ASCII Ribbon Campaign: Against HTML mail, proprietary attachments * signature.asc Description: Digital signature
