[SOLVED] ssh-passphrase not recognized by ssh-agent

After an upgrade yesterday, I cannot enter my system anymore. It boots with some (rapidly passing) error messages (related to AF_UNIX) and shows me the login prompt. But fontsize isn't the one I had before, and customized keymappings of my keyboard are missing. Thus my configurations for the console have not been read.
Then I can successfully enter my login and password - but not the ssh-passphrase asked for by ssh-agent. I typed it many times, it must be correct, but is not recognized anymore. So at this point I'm stuck. I rebooted and tried fallback Arch - with the same result.
Then I chose the grub> shell during boot, and tab gave me a list of available commands. But I don't know what to do now.
So my question is:
how can I enter my system besides the ssh-passphrase problem? And if I managed to get into the system again - what might be the cause of this problem?
EDIT:
Ok, I tried to enter my pass-phrase as if I had an US keyboard (I have a German keyboard) and that worked. Now I can enter my system again, so I close this question. Maybe I will open another question soon, related to the root-cause of the problem (why my configuration isn't loaded on startup).
Last edited by 4on6 (2012-11-29 11:35:01)

After an upgrade yesterday, I cannot enter my system anymore. It boots with some (rapidly passing) error messages (related to AF_UNIX) and shows me the login prompt. But fontsize isn't the one I had before, and customized keymappings of my keyboard are missing. Thus my configurations for the console have not been read.
Then I can successfully enter my login and password - but not the ssh-passphrase asked for by ssh-agent. I typed it many times, it must be correct, but is not recognized anymore. So at this point I'm stuck. I rebooted and tried fallback Arch - with the same result.
Then I chose the grub> shell during boot, and tab gave me a list of available commands. But I don't know what to do now.
So my question is:
how can I enter my system besides the ssh-passphrase problem? And if I managed to get into the system again - what might be the cause of this problem?
EDIT:
Ok, I tried to enter my pass-phrase as if I had an US keyboard (I have a German keyboard) and that worked. Now I can enter my system again, so I close this question. Maybe I will open another question soon, related to the root-cause of the problem (why my configuration isn't loaded on startup).
Last edited by 4on6 (2012-11-29 11:35:01)

Similar Messages

  • [solved] Digital Camera not recognized in device-manager

    My digital camera "Canon Powershot SX120 is" is not recognized by the devicemanager. I have read Digital Cameras.
    $ groups
    wheel storage users printadmin
    The "camera"-Group isn't needed anymore and this group doesn't exist on my system.
    The Powershot SX 120 has a  MTP/PTP connection mode (as the manual says). But:
    # mtp-detect
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
    Listing raw device(s)
    No raw devices found.
    gphoto succeed:
    $ gphoto2 --auto-detect
    Modell Port
    Canon PowerShot SX120 IS usb:002,019
    A gphoto --summary could be found here
    There is no udev-rule for this camera. If i create one while copying a rule from a similar camera from /etc/udev/rules.d/69-libmtp.rules, and store it into /etc/udev/rules.d/69-canon.rules, the device-manager shows up. My udev-rule:
    # Canon PowerShot SX120AX (PTP/MTP mode)
    ATTR{idVendor}=="04a9", ATTR{idProduct}=="31e0", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
    The device-manager shows me only the option to open with a file-manager. Doing so will result in an error:
    The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8/ do not exist.
    With my udev-rule:
    solid-hardware listen
    Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
    Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
    Listening to add/remove events:
    Device Added:
    udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8'
    Without the active udev-rule, "solid-hardware listen" produces nothing, but
    udevadm monitor
    monitor will print the received events for:
    UDEV - the event which udev sends out after rule processing
    KERNEL - the kernel uevent
    KERNEL[5077.662572] add /devices/pci0000:00/0000:00:02.1/usb2/2-8 (usb)
    KERNEL[5077.662655] add /devices/pci0000:00/0000:00:02.1/usb2/2-8/2-8:1.0 (usb)
    UDEV [5077.681178] add /devices/pci0000:00/0000:00:02.1/usb2/2-8 (usb)
    UDEV [5077.693035] add /devices/pci0000:00/0000:00:02.1/usb2/2-8/2-8:1.0 (usb)
    Don't know what to do ... is a udev-rule necessary to bring up the message from device-manger? Or is the Camera not recognized as a mtp-device (the Camera has no such settings)? How could i figure it out?
    With Digikam i could import Fotos, but i would do so with gwenview. I've tried to check it out with gwenview_importer:
    $ gwenview_importer --udi '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb2/2-8'
    QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    gwenview_importer: Missing required source folder argument.
      (don't care about the different udi, i took this example from a former try) but i don't know, how to find out where the "source folder" is ...
    Last edited by quiqueck (2014-02-26 20:10:25)

    I have solved this by making an extra udev-rule for my camera. See my adventure on forum.kde.org for details

  • -bash: ssh: command not found = no ssh?

    Hi all,
    Sorry if this isn't the right category - this seemed to be the best fit.
    I'm having trouble with SSH.
    I've used ssh in the past (back when I was running Leopard) but I've never had all that much use for it. Today, however, I opened up terminal to SSH to an iMac on my local network, and got the following back:
    -bash: ssh: command not found
    Having a look around on the internet, somebody else said that they got this message but was still able to see the SSH manual by typing ssh man. However, when I tried this I just got "command not found" again.
    Any ideas?
    Thanks in advance,
    BrutalSpoon.

    Do you remember if you modified .profile or .bash_profile when you installed mysql?
    I guess you could search for the file that has the modification
    /usr/bin/grep /usr/local/mysql/bin $HOME/.[a-z]*
    Once you find the file, edit that file and put a dollar sign infront of PATH
    /usr/bin/nano /name/of/file/with/mysql/bin/in/it
    The entry you want to fix most likely looks like
    export PATH=PATH:/usr/local/mysql/bin
    you want to change this to
    export PATH=$PATH:/usr/local/mysql/bin
    The problem is the missing dollar sign $ which would cause the current PATH to be substituted before the addition of /usr/local/mysql/bin.
    Once the change is made, quit Terminal and relaunch it. The corrected PATH should now work.
    NOTE: If you do not want to use nano you could use TextWrangler (via File -> Open Hidden...), or Smultron (via File -> Open Hidden...). You should be able to find these GUI based text editors via <http://versiontracker.com>.
    Good luck.

  • [SOLVED]Hard Disk not recognized when installing

    Hey all, I'm just starting with Arch and I've had some trouble installing it on my Acer netbook.
    My first installation went well except that I had forgot to download the wireless tools so I decided to do a fresh install as I had no access to a wired connection at the time.  The second installation attempt must have had some error on my part as Arch failed to start after selecting it from Grub, saying that the kernel was not available/not recognized.
    Now my subsequent attempts at installing have failed because the hard disk is not recognized when running either cgdisk or cfdisk.  Instead of showing my hard drive partitions after running
    cfdisk /dev/sda
    it shows my usb drive. If I instead use
    cgdisk /dev/sda
    it displays an error saying that the disk is damaged or not recognized.  When I first saw this I thought my disk was failing, so I tried #! to see if it would show the same error, but it was able to recognize the entire disk and install correctly.  Now, even after having the entire disk formatted as ext4 with #! installed, cgdisk is still giving me the same error about a damaged disk.
    Am I doing something incorrectly or is there a fix for this?  I haven't been able to find any information about this after a good while of searching.
    Thanks for your help.
    Last edited by Forest_Leaves (2013-03-05 08:30:24)

    srs5694 wrote:The cgdisk "damaged disk" error is probably a result of the tool seeing an MBR partition table on your USB flash drive, rather than the GPT disk it's expecting. If I'm right, you should not follow s1ln7m4s7r's advice, since that will simply trash your USB flash drive!
    If you mean by trashing the USB flash drive, that it will delete all data and partitions on the selected drive it is correct, because:
    dd if=/dev/zero of=/dev/$disk bs=4096 count=1
    - this will delete all partition-table data
    sgdisk -o /dev/$disk
    - this will clear out all data. This includes GPT header data, all partition definitions, and the protective MBR.
    /dev/$disk
    - this will make you enter ncurses-based GUID partition table (GPT) manipulator, where you can create new partitions
    You should only do this if you are certain of what disk it is.
    Now if when you said this, you were meaning it will became broken, then it may be a special kind of usb drive because i've donne it many times and i've not broken any.
    srs5694 wrote:My guess is that either your hard disk has become /dev/sdb (this can happen in some cases; disk identifiers aren't really fixed) or you're missing a driver for your hard disk controller because you've booted a different kernel or a different initrd file. Another possibility is that there's a hardware fault -- probably a loose cable -- that's preventing the kernel from seeing the disk.
    If the usb drive is not where you installed arch, then you need to find if there are more recognized drives:
    lsblk | grep disk
    And see the uuid of the root partition you want, and add it to your bootloader boot line:
    blkid /dev/sdxx
    Last edited by s1ln7m4s7r (2013-03-04 19:17:36)

  • [SOLVED] luks-passphrase not working after update

    SOLVED: Hard drive was damaged. new hard drive ''fixed'' issue
    Hello,
    i updated my arch on 2015-06-05. After restarting my cryptsetup does not accept my password anymore.
    No key available with this passphrase.
    Searching the forum i found a couple of simular topics, nevertheless none of them offered a solution to the problem:
    https://bbs.archlinux.org/viewtopic.php?id=169408
    https://bbs.archlinux.org/viewtopic.php?id=175737
    https://bbs.archlinux.org/viewtopic.php?id=148562
    So the solutions that did not work so far:
    1. Downgrading cryptsetup package
    2. Downgrading kbd package
    3. Checked that my keyboard works just fine (both in grub and in live system)
    4. Manualy loading the aes modules in live system to ensure correct decryption (found that issue somewhere...)
    Unfortunatly i did not backup the luks header file.
    So i don't know if there is some other way to check if the header is broken or how to find out why it will not decrypt my disk.
    I am happy for any solutions or ideas
    Regards,
    Some outputs from cryptsetup:
    cryptsetup -v isLuks /dev/sda2
    Command successful.
    cryptsetup -v luksDump /dev/sda2
    LUKS header information for /dev/sda2
    Version: 1
    Cipher name: aes
    Cipher mode: xts-plain64
    Hash spec: sha512
    Payload offset: 4096
    MK bits: 512
    MK digest: 66 00 4c 66 17 ec 2c 82 68 b3 26 2e 58 df 76 cf 3b f5 18 ef
    MK salt: b8 e0 5d 4d 5c bb 23 6a fc fc 86 d8 5d b6 3f 1f
    28 b6 0e 49 33 9a 8b e6 a2 55 f5 42 32 92 95 db
    MK iterations: 51000
    UUID: dbe69743-7753-4a54-a221-a662042c0444
    Key Slot 0: ENABLED
    Iterations: 204146
    Salt: fa 22 ec 71 49 2c af 9f 64 10 b3 8e f4 76 31 c0
    02 16 dd 2c 72 7e 2f 4b 0b 08 2f 02 03 dd 52 dc
    Key material offset: 8
    AF stripes: 4000
    Key Slot 1: DISABLED
    Key Slot 2: DISABLED
    Key Slot 3: DISABLED
    Key Slot 4: DISABLED
    Key Slot 5: DISABLED
    Key Slot 6: DISABLED
    Key Slot 7: DISABLED
    Command successful.
    Last edited by Fleeep (2015-06-14 12:09:24)

    losetup --read-only /dev/loop7 /dev/sda2
    dmsetup create foobar --table '0 2048 crypt aes-xts-plain64 4ec1a210c7c44208ca132559cda338d7651471abd47b619b1d3a15d273ab69875cdd2bcb7c2750f6cab9e6b2e19f487fb4766bb7826819c8b2de898fe3c0b999 0 7:7 4096'
    file -s -L /dev/mapper/foobar
    hexdump -C /dev/mapper/foobar
    Gives me the master key for the decrypted partition (denoted as forum_key_kex).
    Do i need to convert this to binary or something to use it...?
    Assume Filesystem/dev_sda2 is the partition to decrypt.
    So to decrypt the partition directly with master key i have to do one of the following, wasn't sure which hash to take...:
    echo "0 `blockdev --getsz Filesystem/dev_sda2` crypt aes-cbc-essiv:sha256 `echo SomeEncrypt | sha256sum | head -c 64` 0 Filesystem/dev_sda2 4096" | dmsetup create luks_volume
    echo "0 `blockdev --getsz Filesystem/dev_sda2` crypt aes-cbc-essiv:sha256 `sha256sum forum_key_hex | head -c 64` 0 Filesystem/dev_sda2 4096" | dmsetup create luks_volume
    as i found on:
    http://unix.stackexchange.com/questions … master-key
    (approved by you in the comment as it seems)
    But both give me an error:
    device-mapper: resume ioctl on luks_volume failed: Invalid argument
    Command failed
    Did i even do this right?
    Also when i copied the partition to an external device dd_rescue observed 6 errors in blocks. So those might just be the cause of failure all the time.

  • [SOLVED] Sound Card not recognized on Macbook (5,1)

    Hello,
    I had no problems installing Archlinux on my Macbook (5,1).  In fact, the first time I followed the Wiki's instructions for installing ALSA, I could play sounds just fine.  However, ever since my first restart, the ALSA daemon complains that I have no sound cards installed.  lspci shows that it sees an audio device, but /sys/modules/snd no longer exists.  I do not know much about useful diagnostic information for this situation, so please let me know what else could be of use.
    Thank you,
    Rob
    Last edited by rennis250 (2009-07-28 20:58:00)

    I had forgotten that I installed OSS, which caused conflicts with a previously installed copy of ALSA.  Once I removed OSS completely, rebooted, and went through the ALSA setup again, I had fully working sound.  This problem can be marked as solved.
    --Rob

  • [SOLVED] Sound card not recognized

    I tried following the ALSA setup guide on the Wiki to get my sound working but I don't think Arch recognizes my sound card.  I found out from lshwd that the module is snd-intel8x0 so I modprobed that and snd-pcm-oss, changed the values in alsamixer, added myself to the audio group, installed alsa-utils, alsa-lib and alsa-oss and restarted everything but I still have no sound.  Here's some output:
    lsmod | grep '^snd'
    snd_intel8x0 28700 1
    snd_ac97_codec 95780 1 snd_intel8x0
    snd_pcm_oss 38688 0
    snd_pcm 69124 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
    snd_seq_device 6796 0
    snd_mixer_oss 14592 1 snd_pcm_oss
    snd_timer 19076 1 snd_pcm
    snd 44516 9 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_pcm,snd_seq_device,snd_mixer_oss,snd_timer
    snd_page_alloc 7816 2 snd_intel8x0,snd_pcm
    ls -l /dev/snd
    total 0
    crw-rw---- 1 root audio 116, 0 2007-07-12 21:35 controlC0
    crw-rw---- 1 root audio 116, 24 2007-07-12 21:35 pcmC0D0c
    crw-rw---- 1 root audio 116, 16 2007-07-12 21:35 pcmC0D0p
    crw-rw---- 1 root audio 116, 25 2007-07-12 21:35 pcmC0D1c
    crw-rw---- 1 root audio 116, 26 2007-07-12 21:35 pcmC0D2c
    crw-rw---- 1 root audio 116, 27 2007-07-12 21:35 pcmC0D3c
    crw-rw---- 1 root audio 116, 20 2007-07-12 21:35 pcmC0D4p
    crw-rw---- 1 root audio 116, 33 2007-07-12 13:02 timer
    The wiki says that if you have controlC0 and pcmC0D0p in that output then the modules have been loaded properly and they are both there so I'm not sure where to go from here.  Your help would be appreciated.
    Last edited by Thrillhouse (2007-07-12 22:23:29)

    you need to start alsa if you haven't already done so... /etc/alsa start
    prolly better to run alsacoconf if you still have problems

  • [SOLVED] Awesome is not recognizing widgets

    Hey everybody,
    So this is my first (non-virtualbox) arch install. I just switched over from crunchbang. I had awesome installed on crunchbang and used that as my primary window manager. So I saved all of my configs and everything so that I could use them on arch. I got arch installed and then awesome, and awesome works well. I am using it right now. But as soon as I started trying to add widgets it wouldn't let me. Every time I restart it awesome reverts to the rc.lua in /etc/xdg... and gives me a warning message saying:
    Oops, there were errors during startup!
    /home/nathan/.config/awesome/rc.lua:117: attempt to call global 'widget' (a nil value)
    The line it is referring to is this:
    separator = widget({ type = "textbox" })
    Also, all of the requires at the top currently look like this:
    -- Standard awesome library
    local gears = require("gears")
    local awful = require("awful")
    awful.rules = require("awful.rules")
    require("awful.autofocus")
    -- Widget and layout library
    wibox = require("wibox")
    -- Theme handling library
    local beautiful = require("beautiful")
    -- Notification library
    local naughty = require("naughty")
    local menubar = require("menubar")
    So I tried to google and search the awesome wiki and the arch wiki for how it is done on arch. From everything I have found I am doing it correctly, but I must be missing something. One thought was that it might be a result of the most recent awesome update. I think it was on the 4th. Any ideas?
    Last edited by nhare330 (2013-01-09 00:21:05)

    Here it is. My rc.lua:
    -- Standard awesome library
    local gears = require("gears")
    local awful = require("awful")
    awful.rules = require("awful.rules")
    require("awful.autofocus")
    -- Widget and layout library
    local wibox = require("wibox")
    local vicious = require("vicious")
    -- Theme handling library
    local beautiful = require("beautiful")
    -- Notification library
    local naughty = require("naughty")
    local menubar = require("menubar")
    -- {{{ Error handling
    -- Check if awesome encountered an error during startup and fell back to
    -- another config (This code will only ever execute for the fallback config)
    if awesome.startup_errors then
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, there were errors during startup!",
    text = awesome.startup_errors })
    end
    -- Handle runtime errors after startup
    do
    local in_error = false
    awesome.connect_signal("debug::error", function (err)
    -- Make sure we don't go into an endless error loop
    if in_error then return end
    in_error = true
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, an error happened!",
    text = err })
    in_error = false
    end)
    end
    -- {{{ Variable definitions
    -- Themes define colours, icons, and wallpapers
    beautiful.init("/usr/share/awesome/themes/zenburn/theme.lua")
    -- This is used later as the default terminal and editor to run.
    terminal = "lxterminal"
    editor = os.getenv("EDITOR") or "nano"
    editor_cmd = terminal .. " -e " .. editor
    -- Default modkey.
    -- Usually, Mod4 is the key with a logo between Control and Alt.
    -- If you do not like this or do not have such a key,
    -- I suggest you to remap Mod4 to another key using xmodmap or other tools.
    -- However, you can use another modifier like Mod1, but it may interact with others.
    modkey = "Mod4"
    -- Table of layouts to cover with awful.layout.inc, order matters.
    local layouts =
    awful.layout.suit.floating,
    awful.layout.suit.tile,
    awful.layout.suit.tile.left,
    awful.layout.suit.tile.bottom,
    awful.layout.suit.tile.top,
    awful.layout.suit.fair,
    awful.layout.suit.fair.horizontal,
    awful.layout.suit.spiral,
    awful.layout.suit.spiral.dwindle,
    awful.layout.suit.max,
    awful.layout.suit.max.fullscreen,
    awful.layout.suit.magnifier
    -- {{{ Wallpaper
    if beautiful.wallpaper then
    for s = 1, screen.count() do
    gears.wallpaper.maximized(beautiful.wallpaper, s, true)
    end
    end
    -- {{{ Tags
    -- Define a tag table which hold all screen tags.
    tags = {
    names = { "➊ ", "➋ ", "➌ ", "➍ ", "➎ ", "◌ " },
    layout = { layouts[2], layouts[10], layouts[10], layouts[1], layouts[1], layouts[10]
    for s = 1, screen.count() do
    -- Each screen has its own tag table.
    tags[s] = awful.tag(tags.names, s, tags.layout)
    end
    -- {{{ Menu
    -- Create a laucher widget and a main menu
    myawesomemenu = {
    { "manual", terminal .. " -e man awesome" },
    { "edit config", editor_cmd .. " " .. awesome.conffile },
    { "restart", awesome.restart },
    { "quit", awesome.quit }
    mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
    { "open terminal", terminal }
    mylauncher = awful.widget.launcher({ image = beautiful.awesome_icon,
    menu = mymainmenu })
    -- Menubar configuration
    menubar.utils.terminal = terminal -- Set the terminal for applications that require it
    -- {{{ Wibox
    -- Separator
    separator = wibox.widget.textbox()
    separator:set_text(" | ")
    -- Spacer
    spacer = wibox.widget.textbox()
    spacer:set_text(" ")
    -- Network usage widget
    netwidget = wibox.widget.textbox()
    vicious.register(netwidget, vicious.widgets.net, '<span color="#CDBC73">${eth0 down_kb}</span> <span color="#7F9F7F">${eth0 up_kb}</span>', 3)
    -- Memory widget
    memwidget = wibox.widget.textbox()
    memwidget_t = awful.tooltip({ objects = {memwidget}, })
    vicious.register(memwidget, vicious.widgets.mem,
    function (widget, args)
    memwidget_t:set_text('<span color="#9868B1"> mem: ' ..args[2].. '/' ..args[3].. 'mb \n free: ' ..args[4].. 'mb \n swap: ' ..args[5].. '% > ' ..args[6].. '/' ..args[7].. 'mb \n free: ' ..args[8].. 'mb </span>')
    return '<span color="#CDBC73">▣ ' ..args[1].. '%</span>'
    end, 3)
    -- Cpu widget
    cpuwidget = wibox.widget.textbox()
    cpuwidget_t = awful.tooltip({ objects = {cpuwidget}, })
    vicious.register(cpuwidget, vicious.widgets.cpu,
    function (widget, args)
    cpuwidget_t:set_text('<span color="#9868B1"> cpu0: ' ..args[2].. '% \n cpu1: ' ..args[3].. '% </span>')
    return '<span color="#CDBC73">◈ ' ..args[1].. '%</span>'
    end, 3)
    -- Battery widget
    batwidget = wibox.widget.textbox()
    batwidget_t = awful.tooltip({ objects = {batwidget}, })
    vicious.register(batwidget, vicious.widgets.bat,
    function (widget, args)
    batwidget_t:set_text('<span color="#9868B1"> ' ..args[3].. ' </span>')
    return '<span color="#CDBC73">↯ ' ..args[1].. '' ..args[2].. '</span>'
    end, 14, "BAT0")
    -- Keyboard widget
    kbdcfg = {}
    kbdcfg.cmd = "setxkbmap"
    kbdcfg.layout = { "us", "es" }
    -- kbdcfg.us = "<span color='#CDBC73'>us</span>"
    -- kbdcfg.es = "<span color='#CDBC73'>es</span>"
    kbdcfg.current = 1
    kbdcfg.widget = wibox.widget.textbox({ align = "right" })
    kbdcfg.widget:set_text( kbdcfg.layout[kbdcfg.current] )
    kbdcfg.switch = function ()
    kbdcfg.current = kbdcfg.current % #(kbdcfg.layout) + 1
    local t = kbdcfg.layout[kbdcfg.current]
    kbdcfg.widget:set_text( t )
    os.execute( kbdcfg.cmd .. t )
    end
    kbdcfg.widget:buttons(awful.util.table.join(
    awful.button({ }, 1, function () kbdcfg.switch() end )
    -- Wifi
    wifiwidget = wibox.widget.textbox()
    wifiwidget_t = awful.tooltip({ objects = {wifiwidget}, })
    vicious.register (wifiwidget, vicious.widgets.wifi,
    function (widget, args)
    wifiwidget_t:set_text('<span color="#9868B1"> ' ..args["{ssid}"].. ' \n mode: ' ..args["{mode}"].. ' \n chan: ' ..args["{chan}"].. ' \n sign: ' ..args["{sign}"].. ' \n rate: ' ..args["{rate}"].. ' </span>')
    -- ' \n rate: ' ..args["{rate}"].. ' \n linp: ' ..args["{linp}"]..
    return '<span color="#CDBC73">⇄ ' ..args["{link}"].. '%</span>'
    end, 7, "wlan0")
    -- File System
    fswidget = wibox.widget.textbox()
    fswidget_t = awful.tooltip({ objects = {fswidget}, })
    vicious.register(fswidget, vicious.widgets.fs,
    function (widget, args)
    fswidget_t:set_text('<span color="#9868B1">used: ' ..args["{/ used_gb}"].. '/' ..args["{/ size_gb}"].. 'gb </span>')
    return '<span color="#CDBC73">◕ ' ..args["{/ avail_gb}"].. 'gb</span>'
    end, 61)
    -- Uptime
    uptimewidget = wibox.widget.textbox()
    uptimewidget_t = awful.tooltip({ objects = {uptimewidget}, })
    vicious.register(uptimewidget, vicious.widgets.uptime,
    function (widget, args)
    uptimewidget_t:set_text('<span color="#9868B1"> ' ..args[1].. 'd ' ..args[2].. ':' ..args[3].. ' </span>')
    return string.format('<span color="#CDBC73">⇑ ' ..args[1].. 'd</span>')
    end, 61)
    -- Volume Widget
    volumecfg = {}
    volumecfg.cardid = 0
    volumecfg.channel = "Master"
    volumecfg.widget = wibox.widget.textbox({ align = "right" })
    -- volumecfg_t = awful.tooltip({ objects = { volumecfg.widget },})
    -- volumecfg_t:set_text("volume")
    -- command must start with a space!
    volumecfg.mixercommand = function (command)
    local fd = io.popen("amixer -c " .. volumecfg.cardid .. command)
    local status = fd:read("*all")
    fd:close()
    local volume = string.match(status, "(%d?%d?%d)%%")
    volume = string.format("% 3d", volume)
    status = string.match(status, "%[(o[^%]]*)%]")
    if string.find(status, "on", 1, true) then
    volume = "<span color='#CDBC73'>◄ " .. volume .. "</span>"
    else
    volume = "<span color='#CDBC73'>⋪ " .. volume .. "</span>"
    end
    volumecfg.widget:set_text( volume )
    end
    volumecfg.update = function ()
    volumecfg.mixercommand(" sget " .. volumecfg.channel)
    end
    volumecfg.up = function ()
    volumecfg.mixercommand(" sset " .. volumecfg.channel .. " 1%+")
    end
    volumecfg.down = function ()
    volumecfg.mixercommand(" sset " .. volumecfg.channel .. " 1%-")
    end
    volumecfg.toggle = function ()
    volumecfg.mixercommand(" sset " .. volumecfg.channel .. " toggle")
    end
    volumecfg.widget:buttons({
    button({ }, 4, function () volumecfg.up() end),
    button({ }, 5, function () volumecfg.down() end),
    button({ }, 1, function () volumecfg.toggle() end)
    volumecfg.update()
    -- Date widget
    datewidget = wibox.widget.textbox()
    vicious.register(datewidget, vicious.widgets.date, '<span color="#D8D8D8"> %a. %b %d, %l:%M %p </span>', 5)
    -- Create a textclock widget
    mytextclock = awful.widget.textclock({ align = "right" })
    -- Calendar widget to attach to the textclock
    require('calendar2')
    calendar2.addCalendarToWidget(datewidget)
    -- Create a textclock widget
    mytextclock = awful.widget.textclock()
    -- Create a wibox for each screen and add it
    mywibox = {}
    mypromptbox = {}
    mylayoutbox = {}
    mytaglist = {}
    mytaglist.buttons = awful.util.table.join(
    awful.button({ }, 1, awful.tag.viewonly),
    awful.button({ modkey }, 1, awful.client.movetotag),
    awful.button({ }, 3, awful.tag.viewtoggle),
    awful.button({ modkey }, 3, awful.client.toggletag),
    awful.button({ }, 4, function(t) awful.tag.viewnext(awful.tag.getscreen(t)) end),
    awful.button({ }, 5, function(t) awful.tag.viewprev(awful.tag.getscreen(t)) end)
    mytasklist = {}
    mytasklist.buttons = awful.util.table.join(
    awful.button({ }, 1, function (c)
    if c == client.focus then
    c.minimized = true
    else
    -- Without this, the following
    -- :isvisible() makes no sense
    c.minimized = false
    if not c:isvisible() then
    awful.tag.viewonly(c:tags()[1])
    end
    -- This will also un-minimize
    -- the client, if needed
    client.focus = c
    c:raise()
    end
    end),
    awful.button({ }, 3, function ()
    if instance then
    instance:hide()
    instance = nil
    else
    instance = awful.menu.clients({ width=250 })
    end
    end),
    awful.button({ }, 4, function ()
    awful.client.focus.byidx(1)
    if client.focus then client.focus:raise() end
    end),
    awful.button({ }, 5, function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end))
    for s = 1, screen.count() do
    -- Create a promptbox for each screen
    mypromptbox[s] = awful.widget.prompt()
    -- Create an imagebox widget which will contains an icon indicating which layout we're using.
    -- We need one layoutbox per screen.
    mylayoutbox[s] = awful.widget.layoutbox(s)
    mylayoutbox[s]:buttons(awful.util.table.join(
    awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
    awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)))
    -- Create a taglist widget
    mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.filter.all, mytaglist.buttons)
    -- Create a tasklist widget
    mytasklist[s] = awful.widget.tasklist(s, awful.widget.tasklist.filter.currenttags, mytasklist.buttons)
    -- Create the wibox
    mywibox[s] = awful.wibox({ position = "top", screen = s })
    -- Widgets that are aligned to the left
    local left_layout = wibox.layout.fixed.horizontal()
    left_layout:add(mylauncher)
    left_layout:add(mytaglist[s])
    left_layout:add(mypromptbox[s])
    -- Widgets that are aligned to the right
    local right_layout = wibox.layout.fixed.horizontal()
    if s == 1 then right_layout:add(wibox.widget.systray()) end
    right_layout:add(mytextclock)
    right_layout:add(mylayoutbox[s])
    -- Now bring it all together (with the tasklist in the middle)
    local layout = wibox.layout.align.horizontal()
    layout:set_left(left_layout)
    layout:set_middle(mytasklist[s])
    layout:set_right(right_layout)
    mywibox[s]:set_widget(layout)
    end
    -- {{{ Mouse bindings
    root.buttons(awful.util.table.join(
    awful.button({ }, 3, function () mymainmenu:toggle() end),
    awful.button({ }, 4, awful.tag.viewnext),
    awful.button({ }, 5, awful.tag.viewprev)
    -- {{{ Key bindings
    globalkeys = awful.util.table.join(
    awful.key({ modkey, }, "Left", awful.tag.viewprev ),
    awful.key({ modkey, }, "Right", awful.tag.viewnext ),
    awful.key({ modkey, }, "Escape", awful.tag.history.restore),
    awful.key({ modkey, }, "Down",
    function ()
    awful.client.focus.byidx( 1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "Up",
    function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "a", function () mymainmenu:show() end),
    -- Layout manipulation
    awful.key({ modkey, "Shift" }, "Down", function () awful.client.swap.byidx( 1) end),
    awful.key({ modkey, "Shift" }, "Up", function () awful.client.swap.byidx( -1) end),
    awful.key({ modkey, "Control" }, "Down", function () awful.screen.focus_relative( 1) end),
    awful.key({ modkey, "Control" }, "Up", function () awful.screen.focus_relative(-1) end),
    awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
    awful.key({ modkey, }, "Tab",
    function ()
    awful.client.focus.history.previous()
    if client.focus then
    client.focus:raise()
    end
    end),
    -- Standard program
    awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end),
    awful.key({ modkey, "Control" }, "r", awesome.restart),
    awful.key({ modkey, "Shift" }, "q", awesome.quit),
    awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end),
    awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end),
    awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end),
    awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end),
    awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end),
    awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end),
    awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end),
    awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
    awful.key({ modkey, "Control" }, "n", awful.client.restore),
    -- Prompt
    awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
    awful.key({ modkey }, "x",
    function ()
    awful.prompt.run({ prompt = "Run Lua code: " },
    mypromptbox[mouse.screen].widget,
    awful.util.eval, nil,
    awful.util.getdir("cache") .. "/history_eval")
    end),
    -- Menubar
    awful.key({ modkey }, "p", function() menubar.show() end)
    clientkeys = awful.util.table.join(
    awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end),
    awful.key({ modkey, }, "w", function (c) c:kill() end),
    awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
    awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end),
    awful.key({ modkey, }, "o", awful.client.movetoscreen ),
    awful.key({ modkey, }, "t", function (c) c.ontop = not c.ontop end),
    awful.key({ modkey, }, "n",
    function (c)
    -- The client currently has the input focus, so it cannot be
    -- minimized, since minimized clients can't have the focus.
    c.minimized = true
    end),
    awful.key({ modkey, }, "m",
    function (c)
    c.maximized_horizontal = not c.maximized_horizontal
    c.maximized_vertical = not c.maximized_vertical
    end)
    -- Compute the maximum number of digit we need, limited to 9
    keynumber = 0
    for s = 1, screen.count() do
    keynumber = math.min(9, math.max(#tags[s], keynumber))
    end
    -- Bind all key numbers to tags.
    -- Be careful: we use keycodes to make it works on any keyboard layout.
    -- This should map on the top row of your keyboard, usually 1 to 9.
    for i = 1, keynumber do
    globalkeys = awful.util.table.join(globalkeys,
    awful.key({ modkey }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewonly(tags[screen][i])
    end
    end),
    awful.key({ modkey, "Control" }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewtoggle(tags[screen][i])
    end
    end),
    awful.key({ modkey, "Shift" }, "#" .. i + 9,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.movetotag(tags[client.focus.screen][i])
    end
    end),
    awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.toggletag(tags[client.focus.screen][i])
    end
    end))
    end
    clientbuttons = awful.util.table.join(
    awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
    awful.button({ modkey }, 1, awful.mouse.client.move),
    awful.button({ modkey }, 3, awful.mouse.client.resize))
    -- Set keys
    root.keys(globalkeys)
    -- {{{ Rules
    awful.rules.rules = {
    -- All clients will match this rule.
    { rule = { },
    properties = { border_width = beautiful.border_width,
    border_color = beautiful.border_normal,
    focus = awful.client.focus.filter,
    keys = clientkeys,
    buttons = clientbuttons } },
    { rule = { class = "MPlayer" },
    properties = { floating = true } },
    { rule = { class = "pinentry" },
    properties = { floating = true } },
    { rule = { class = "gimp" },
    properties = { floating = true } },
    -- Set Firefox to always map on tags number 2 of screen 1.
    -- { rule = { class = "Firefox" },
    -- properties = { tag = tags[1][2] } },
    -- {{{ Signals
    -- Signal function to execute when a new client appears.
    client.connect_signal("manage", function (c, startup)
    -- Enable sloppy focus
    c:connect_signal("mouse::enter", function(c)
    if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
    and awful.client.focus.filter(c) then
    client.focus = c
    end
    end)
    if not startup then
    -- Set the windows at the slave,
    -- i.e. put it at the end of others instead of setting it master.
    -- awful.client.setslave(c)
    -- Put windows in a smart way, only if they does not set an initial position.
    if not c.size_hints.user_position and not c.size_hints.program_position then
    awful.placement.no_overlap(c)
    awful.placement.no_offscreen(c)
    end
    end
    local titlebars_enabled = false
    if titlebars_enabled and (c.type == "normal" or c.type == "dialog") then
    -- Widgets that are aligned to the left
    local left_layout = wibox.layout.fixed.horizontal()
    left_layout:add(awful.titlebar.widget.iconwidget(c))
    -- Widgets that are aligned to the right
    local right_layout = wibox.layout.fixed.horizontal()
    right_layout:add(awful.titlebar.widget.floatingbutton(c))
    right_layout:add(awful.titlebar.widget.maximizedbutton(c))
    right_layout:add(awful.titlebar.widget.stickybutton(c))
    right_layout:add(awful.titlebar.widget.ontopbutton(c))
    right_layout:add(awful.titlebar.widget.closebutton(c))
    -- The title goes in the middle
    local title = awful.titlebar.widget.titlewidget(c)
    title:buttons(awful.util.table.join(
    awful.button({ }, 1, function()
    client.focus = c
    c:raise()
    awful.mouse.client.move(c)
    end),
    awful.button({ }, 3, function()
    client.focus = c
    c:raise()
    awful.mouse.client.resize(c)
    end)
    -- Now bring it all together
    local layout = wibox.layout.align.horizontal()
    layout:set_left(left_layout)
    layout:set_right(right_layout)
    layout:set_middle(title)
    awful.titlebar(c):set_widget(layout)
    end
    end)
    client.connect_signal("focus", function(c) c.border_color = beautiful.border_focus end)
    client.connect_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
    http://pastebin.com/X4JdkVi0
    Last edited by nhare330 (2013-01-18 13:59:40)

  • [Solved] a.out not recognizing the working directory

    It's a little bit embarrassing because this issue doesn't seem terribly complicated, but I'm having trouble with executing the a.out file (Hello World) that gcc produces. I have to explicitly state the directory that a.out is in to run it, even though it's in the working directory. Other programs, such as Nano, recognize the working directory just fine and it is able to open files inside the working directory without having me explicitly state the full directory name.
    Any help would be greatly appreciated.
    Last edited by bananaman (2011-03-23 03:16:10)

    The easiest and most secure way would be using the relative path to the executable:
    ./a.out
    If you use a single directory for writing/testing your programs, you could add it to your user PATH. Not a major security risk, but if you do so, be careful what executables are in the dir.
    ~/.bashrc (or ~/.bash_profile):
    [[ -d ~/cpp ]] && export PATH="$PATH:~/cpp"
    Adding the current working directory to PATH is a security risk, so I wouldn't recommend it.
    Last edited by sisco311 (2011-03-23 03:12:29)

  • [SOLVED] Qt Applications not recognizing japanese characters

    When I run Qt applications (goldendict, anki) and open a file browser from within the application itself, file names with Japanese characters in them (醤字.txt) don't get read and the file is "invisible". I don't have any problems when I launch a file browser from the terminal or via cinnamon. I read the arch wiki page on Qt, but wasn't able to find anything that helped. Also, I have a thread about XTerm not reading Japanese characters or being able to take Japanese input, so, not sure if it's related or not. Any suggestions?
    Thanks in advance!
    Last edited by Bipolarbearz (2014-12-24 03:40:47)

    Issue was with my locale settings. Full story here: https://bbs.archlinux.org/viewtopic.php … 0#p1486600 for anyone with the same issue.

  • [SOLVED] Control+V not recognized by X

    I just installed Arch on my laptop yesterday (HP 8510w) but an interesting problem has popped up, Control+V doesn't work.
    showkey recognises the keypress 29 (Control_L) and 46 (v), both separately and simultaneously. However, xev will only recognize them when pressed separately. So I think the issue lies with X configuration. Does anyone have a clue on how to fix this?
    X11 config files
    EDIT: Accidentily pressed control+V from habit and it submitted prematurely
    EDIT 2: Okay, I solved it... stupid me, I shouldn't configure my computer at 2am. Anyway, I bound KeePassX autofill to the Control+V shortcut which prevented normal operation of this shortcut. Apologies for the clutter
    Last edited by rickdg (2011-01-21 11:24:52)

    Good question. I've got the wired extended keyboard connected to an iMac, and I get the same behavior. There's probably something to it, but your guess is as good as mine as to what that is...

  • [Solved] Clang "-cc1" not recognized

    The clang front-end "-cc1" simply does not work. I have tested with clang 3.5 and 3.6.
    $ clang -cc1 --
    clang: error: unknown argument: '-cc1'
    clang: error: no input files
    Same for some others:
    clang: error: unknown argument: '-cl-kernel-arg-info'
    clang: error: unknown argument: '-cl-std=CL1.2'
    clang: error: unknown argument: '-triple'
    Is that only me, or Archlinux's clang is acting weird?
    Last edited by jiehong (2015-05-19 17:00:33)

    Works for me, in the sense that it grabs stdin and tries to execute whatever I've typed when I press ctrl+d.
    This cc1 switch doesn't appear to be documented in the man page though, and this page suggests that it's not supposed to be used directly:
    Users should not run clang -cc1 directly, because -cc1 options are not guaranteed to be stable
    Is this an X-Y problem? What are you trying to do?
    I'm not sure why the -cc1 switch doesn't work for you, have you set up an alias? What does 'type clang' return?
    Edit: Mod note: Moving to Programming and Scripting
    Last edited by WorMzy (2015-05-19 15:12:27)

  • When I type .ssh root@10.0.02 it says host not recognized I'm unable to get in to known host file can not fix the problem.

    When I open terminal and do sash [email protected] it says warning rsa key not recognized to go to known-hosts file which ican not grt into I have download pico but am not sure how to launch it or what I ave to do.

    sibeen, please stop starting new posts when you are really just continuing the first post.  "Reply" to one of your existing posts when you are really just continuing the same question.  If I have not lost count, you have posted 3 times about this same ssh rsa host key issue, and Linc Davis and I have been trying to keep track of all the details, but with it spread out across multiple new posts, it is difficult.
    I'm guessing as you again forgot to post the actual error (I'm starting to wonder if you are testing how well Linc and I can guess at your problem ).  Anyway, I'm guessing that you managed to delete the $HOME/.ssh/known_hosts file, and now when you try to ssh to 10.0.0.2 it wants to add the remote system's host rsa key into a newly created known_hosts file.
    The authenticity of host '[10.0.0.2]:22([10.0.0.2]:22)' can't be established.
    RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
    Are you sure you want to continue connecting (yes/no)?
    Generally the command ask if you want to do this, yes or no.  You type "yes" and your Mac memorizes the remote system's host rsa key.
    If this is not the warning message you are seeing, then as Linc has requested, please post the exact error (feel free to mask put the actual key or usernames or IP addresses, but keep the words.
    If you are still getting the original error from 3 posts ago, then I would not try editing $HOME/.ssh/known_hosts, and instead just delete the file, and when you get a message like I have posted above, answer it with "yes".
    WIth respect to pico, Mac OS X already has pico installed, so there was  no need to download it from anywhere.  However, most people just use 'nano' which has essentially replaced 'pico' as an easy to use Terminal based text editor.  But like I said, I think you will be happier if you just delete the known_hosts file and get on with your ssh operations.
    Finally, I think in your 2nd post you indicated you tried deleting a file that had a dash in the name (known-hosts) instead of an underscore (known_hosts).  If that was just a typo when you entered your post, and you were really getting you cannot delete a directory, then something is seriously wrong, or you accidentally allowed a space to be inserted between .ssh and known_hosts.  Personally, I'm going with you actually entered a space and the 'rm' command thought you wanted to delete the .ssh directory instead of $HOME/.ssh/known_hosts.  I could be wrong, but using copy and paste to post actual Terminal screen output as well as the command you entered would be very helpful to anyone trying to provide useful information.  In other words, help us help you.

  • Not able to ssh to standby GSS

    Hi Experts,
    I am not able to ssh to standby GSS. It is configured for tacacs... I am able to ssh to primary without any issues.
    skdc-gss-int#gss status
    TACACS error. Attempting local authorization ...
    Cisco GSS - 3.1(0) GSSM - standby [Tue May 26 12:37:25 UTC 2009]
    Registered to primary GSSM: 10.71.250.130
    Normal Operation [runmode = 5]
    START SERVER
    May02 Boomerang
    May02 Config Agent (crdirector)
    May02 Config Server (crm)
    May02 DNS Server
    May02 Database
    May02 GUI Server (tomcat)
    May02 Keepalive Engine
    May02 Node Manager
    May02 Proximity
    May02 Sticky
    May02 Web Server (apache)
    May02 drp
    skdc-gss-int#
    skdc-gss-int#sh tacacs
    TACACS error. Attempting local authorization ...
    Current tacacs server configuration
    tacacs-server timeout 60
    tacacs-server keepalive-enable
    tacacs-server host x.x.x.x port 49 key j1b0ia
    tacacs-server host y.y.y.y port 49 key j1b0ia
    aaa authentication ssh local
    aaa authentication gui local
    aaa authorization commands
    aaa accounting commands
    skdc-gss-int#
    skdc-gss-int#sh users
    TACACS error. Attempting local authorization ...
    Username permission
    admin admin
    skdc-gss-int#

    I'm facing the same issue...
    How did you solve the problem?

  • Public ssh key not working with launchd

    I have a simple shell script that has only a couple lines:
    rm /Volumes/drive/folder/*
    scp -r [email protected]:/Volumes/drive/folder/
    the "admin_user" account has an ssh key to be able to connect to the remote server without having to enter in a password.
    if i run this script manually, as "admin_user", it works.
    i need this to run via launchd at a set time every day, which i've successfully configured, with the UserName key. the script does run via launchd and it successfully deletes the files (the first line of the script).
    it is failing, when run via launchd, with the second line. the files are never copied.
    the log shows that the ssh key isn't working:
    12/19/08 10:43:00 AM edu.example.xxxxxxxml[1386] Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
    i'm not sure what i need to do differently as far as configuring the keys.
    many thanks,
    chris

    here is the verbose log... i am not an ssh or sshd_config expert so any guidance is appreciated!:
    {quote}
    admin_user12/23/08 10:34:00 AM edu.example.deptxxxml[26285] Agent pid 26287
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] Enter passphrase for /Users/adminuser/.ssh/idrsa:
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] Executing: program /usr/bin/ssh host testserver.example.edu, user admin_user, command scp -v -r -f /Volumes/drive/inc/data/dept/
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] OpenSSH_5.1p1, OpenSSL 0.9.7l 28 Sep 2006
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Reading configuration data /etc/ssh_config
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Connecting to testserver.example.edu [1xx.xx.117.3] port 22.
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Connection established.
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: identity file /Users/admin_user/.ssh/identity type -1
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: identity file /Users/adminuser/.ssh/idrsa type 1
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: identity file /Users/adminuser/.ssh/iddsa type -1
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: match: OpenSSH_4.7 pat OpenSSH*
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Enabling compatibility mode for protocol 2.0
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Local version string SSH-2.0-OpenSSH_5.1
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSGKEXINIT sent
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSGKEXINIT received
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: kex: server->client aes128-cbc hmac-md5 none
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: kex: client->server aes128-cbc hmac-md5 none
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSG_KEX_DH_GEXREQUEST(1024<1024<8192) sent
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: expecting SSH2MSG_KEX_DH_GEXGROUP
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSG_KEX_DH_GEXINIT sent
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: expecting SSH2MSG_KEX_DH_GEXREPLY
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Host 'testserver.example.edu' is known and matches the RSA host key.
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Found key in /Users/adminuser/.ssh/knownhosts:1
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: sshrsaverify: signature correct
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSGNEWKEYS sent
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: expecting SSH2MSGNEWKEYS
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSGNEWKEYS received
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSG_SERVICEREQUEST sent
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: SSH2MSG_SERVICEACCEPT received
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Next authentication method: gssapi-keyex
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: No valid Key exchange context
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Next authentication method: gssapi-with-mic
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Unspecified GSS failure. Minor code may provide more information
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] No credentials cache found
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Unspecified GSS failure. Minor code may provide more information
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] No credentials cache found
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Unspecified GSS failure. Minor code may provide more information
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Next authentication method: publickey
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Trying private key: /Users/admin_user/.ssh/identity
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Offering public key: /Users/adminuser/.ssh/idrsa
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: Server accepts key: pkalg ssh-rsa blen 277
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: PEMreadPrivateKey failed
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: read PEM private key done: type <unknown>
    12/23/08 10:34:00 AM edu.example.deptxxxml[26285] debug1: read_passphrase: can't open /dev/tty: Device not configured
    {quote}

Maybe you are looking for

  • Item category in Third party

    Hi Friends, When iam trying to assign the item category (VOV4)for a manual requirement the system triggers the error - An entry already exists with the same key. OR + NORM + + = TAN+ TAS But i checked the entries its not existing ...even i tried to c

  • How do i update iphoto 1.2.0 to a newer version

    how do i update iphoto 1.2.0 to a newer version to like 7 or 6 5 or 4 ?

  • Purchase order created time

    Hi Experts, Good day! Is there any way to find the Purchse order created time? Regards, Senthil

  • Theme Editor no showing content.

    Short description of the problem: When I select "Theme Editor", no content is displayed. Long Desc: I imported a theme developed on portal version sp15. When I select the Theme Editor link, not even the list of themes are displayed. I get the followi

  • Bad installer with LV 8.2.1 application builder

    Hi, I updated LV to 8.2.1 with the update available online. Now I need to build a new installer because the exe will need LV 8.2.1 RT (at least it does not work on a pc with 8.2 installed). The build process runs fine so far, but when I try to use th