[solved]ssh-agent not working

ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-TwKWWk9859/agent.9859; export SSH_AUTH_SOCK;
SSH_AGENT_PID=9860; export SSH_AGENT_PID;
echo Agent pid 9860;
jithine ~ $ ssh-add
Could not open a connection to your authentication agent.
How could I make agent auto start during my every kde  4.3.1 login? Also I want to use it with ksshaskpass. Running ssh-add in krunner used to popup ksshaskpass dialog in kubunutu. How can I make it work. Please help.
Last edited by jithin1987 (2009-09-17 00:43:18)

Diaz wrote:I have kde4 from the repos, ssh-agent is launched by kde, i installed keychain and kaskpass, and it works.
I think that initially i had the same problem as you but don't really remember what i changed or if it was just me doing something wrong...
For some reason kdemod kde is not reading /etc/kde/env folder. I copied the agent-startup.sh from there to ~/.kdemod4/env and now the ssh-agent starts on login

Similar Messages

  • I can't send out email using my iPhone4. I tried to follow the step provided to solve but still not working. What should I do?

    I can't send out email using my iPhone4. I tried to follow the step provided to solve but still not working. What should I do?

    Contact your mail provider and get the CORRECT settings for the outgoing server to set up on your phone.

  • ACS V 4.1.1 build 23 Password Aging over SSH does not work.

    Hi, my name is Elias and I have problems with ACS Password Aging over SSH does not work and there is no password aging meseges sent by ACS to de console when I use SSH. I know that there is problems with this but I can't find any workaround or documentation that says that there is no workaroun. Can you help me with this??
    King Regards.

    Hey Elias,
    SSHv1 does not support password changes as you can do in telnet. You will need to be
    running a version of IOS that supports SSHv2.
    The following site explains what versions support this:
    http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5207/products_feat
    ure_guide09186a00802045dc.html
    Rgds,
    somishra

  • [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)

  • [SOLVED] ssh-agent support removed from kde-agent

    Hi all,
    Since its upgrade yesterday, kde-agent does not support ssh-agent anymore (see here). I consequently can't store unlocked SSH keys anymore, because ssh-add from a konsole can't connect to ssh-agent.
    The update note above mentions that the SSH agent is not needed by KDE since years. What's the recommended way to start it now ?
    Thanks a lot !
    Aurélien.
    Last edited by aurelieng (2014-01-03 08:39:49)

    I have been using ssh-agent with KDE on a daily basis for years and AFAIK, there is no better or more convenient way of keeping your private keys available. So in my opinion, the removal of ssh-agent, a tiny daemon that doesn't do any harm yet serves its purpose very well, was a bad idea.
    I found a solution that does not run multiple ssh-agent daemons, even if KDE crashes. The solution is based on the fact that ssh-agent can be used as a wrapper around a session startup script or program. Unfortunately, my solution is very intrusive and will disappear on each KDE update. It works as follows:
    # cd /usr/bin
    # mv startkde startkde-inner
    # cat > startkde <<- HERE
    #!/bin/sh
    exec /usr/bin/ssh-agent /usr/bin/startkde-inner
    HERE
    # chmod +x startkde
    Now the ssh-agent will be started on each KDE session and there will always be only one ssh-agent per KDE session. Comments in the startkde script suggest starting ssh-agent later in the process and then killing it on logout. However, such a solution is inherently unreliable, because it will not kill your ssh-agent when the X-server or KDE crashes. The same problem applies to starting ssh-agent from profile scripts. The wrapper method resolves the issue in a quite reasonable way.
    Last edited by andrej.podzimek (2014-01-08 13:27:25)

  • How to get Leopard ssh agent to work if you previously used "SSH Agent" App

    Hi Everyone,
    I had previously been using the *SSH Agent* application from http://www.phil.uu.nl/~xges/ssh/ and wanted to get rid of it and use the built-in support for ssh-agent in Leopard.
    However, it didn't work. Doing "env | grep SSH" it would show /tmp/501/nl.uu.phil.SSHAgent.socket and ssh'ing from a terminal window would request your passphrase every time. Executing ssh-agent would say "no agent is running." Even deleting the *SSH Agent* app and rebooting, it would still have this phil socket.
    The solution is to use terminal, go to your home directory, cd to .MacOSX and look and see if there's an environment.plist file. In there will be some XML to set this persistent string for SSHAUTHSOCK. You need to take that out. If there's other stuff in the file, like a CVSHOME entry, hand-edit the XML to take out the SSHAUTHSOCK entry. (How to do that is beyond the scope of this post.) If the only thing is that entry, just delete the environment.plist file.
    Afterwards, reboot, or maybe just log out and log back in, open a terminal window, and you should be able to ssh out and the system will start ssh-agent behind your back and find your .ssh/id_dsa file or whatever.
    Karl

    The man page for ssh-agent provides the following documentation:
    -a bind_address
    Bind the agent to the unix-domain socket bind_address. The
    default is /tmp/ssh-XXXXXXXXXX/agent.<ppid>.
    The system ssh-agent's startup arguments are in /System/Library/LaunchAgents/org.openbsd.ssh-agent.plist so you could add something like the following to array that defines the ProgramArguments:
    <string>-a</string>
    <string>/whatever/the/path/is/that/you/want/to/have</string>
    Note that since these mods are being done in /System, they could be wiped out by any system update. You could try making a copy of the file and putting the copy in /Library/LaunchAgents; perhaps files in that directory take precedence over files in /System. Certainly, stuff in /Library shouldn't be wiped out by a system update, though.

  • [solved] SSH doesn't work over PPTP VPN with pptpclient

    I just got set up with access to my work's PPTP VPN. Using pptpclient I can establish a connection and ping servers. I can use telnet to confirm ports 22, 80 etc are accessible and I can access web services in my browser, but SSH doesn't work.
    When I try and SSH to a server it just hangs for a minute and then "Connection closed by 10.70.11.10". Wondering if SSH was using my default route rather than the appropriate tunnel, I tried setting my default route to use the VPN, and ping, telnet, nmap etc still seem to function and return expected results, but SSH still hangs and closes. There are no entries in the sshd log on the servers that I attempted to get access to. I have both Arch and CentOS servers and I cannot get to either via SSH.
    My colleague connected to the VPN on his mobile phone and managed to SSH to a server, so it doesn't seem that the VPN is blocking this... any ideas?
    Thanks
    [update]
    Solved! I found that in /etc/ppp/options, un-commenting -mru fixed this for me:
    # Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
    # 1500).
    -mru
    [/update]
    Last edited by jsteel (2014-08-10 20:06:31)

    targetbsp wrote:
    summit48 wrote:
     Windows10 has hijacked the back end believing every Laptop and Desktop PC is a Smartphone. What do you mean by that?Windows 10: Microsoft under attack over privacyhttp://www.theguardian.com/technology/2015/jul/31/windows-10-microsoft-faces-criticism-over-privacy-default-settings In the "one size fits all" philosophy of Microsoft there is no distinction between a smartphone and a PC. You might turn some of these privacy setting on for a smartphone but not on a PC. 

  • Solved rEFInd does not work after update

    Hello.
    Today, I updated rEFInd with yaourt.
    After the update, I copied the new files in /boot/efi.
    I rebooted and now rEFInd does not work.
    The only message I got is:
    rEFInd - Initializing
    After 2-3 minutes, the computer reboots and I got the same error message.
    To boot, I had to use the UEFI shell.
    First of all, is there a log file for rEFInd?
    It is not easy at all to debug it when we don't have any error messages.
    After that, I did the procedure to install rEFInd in /boot/efi twice without any success.
    Do you know what to do to solve my problem?
    Thanks for your help.
    Last edited by antoyo (2012-11-07 23:29:55)

    @antoyo: The old one is compiled using gnu-efi-libs, the new one is compiled using Tianocore UDK2010.
    Full package: http://dl.dropbox.com/u/9710721/refind- … pkg.tar.xz
    Src package: http://dl.dropbox.com/u/9710721/refind- … src.tar.gz (will compile only in x86_64 system)

  • [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 (snd_hda_intel) not working after resume from suspend

    Using the latest kernel 2.6.30.4, On HP2133, whenever I get back from resume, sound is not working.
    Running the following brings back the sound, but that is obviously a hack:
    fuser -k /dev/snd/*
    rmmod snd_hda_intel
    modprobe snd_hda_intel
    /etc/rc.d/alsa start
    I have on my /etc/modprobe/50-sound.conf:
    options snd-hda-intel model=laptop
    alias snd-card-0 snd-hda-intel
    alias sound-slot-0 snd-hda-intel
    Here's the exact hardware specification:
    # lspci -nnv|grep Audio
    80:01.0 Audio device [0403]: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev 10)
    Any idea where to look for this?
    Last edited by yhager (2009-08-21 16:54:00)

    [SOLVED]
    I downgraded to kernel 2.6.29 and the problem is gone.
    Note: I also had X VT problems with 2.6.30.4 (xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call). Those were solved too by downgrading to 2.6.29.

  • EFS Recovery Agent not working on Windows 8.1

    I know EFS data recovery has been discussed so many times in the forums but I could not find anything useful in the other threads as I believe I have followed all the required steps but still cannot get EFS recovery agent to work.
    I have a Client1 (Win 8.1) and a DC1 (Windows Server 2012 R2) under beta.com domain.
    DC1 is a CA server as well as a domain controller.
    I logged into DC1 as beta.com\Administrator
    which is the Domain Administrator account.
    I duplicated the EFS Recovery Agent template on the
    DC1 and published it into Active Directory.
    Then I edited the Default Domain Policy GPO and under
    Computer Settings\Policies\Windows Settings\Security Settings\Public Key Policies
    I right clicked Encrypting File System and selected Create a Data Recovery Agent
    and a new file recovery certificate was generated for the Administrator account.
    I exported the newly-created Recovery Agent certificate and then logged into
    Client1 as beta.com\Administrator and imported
    it.
    I then logged off from Client1 and logged back in using a different account beta.com\johns
    and encrypted a folder (with a text file inside) using EFS. (The folder address on local disk is
    C:\Reports)
    Then I logged back into Client1 again using beta.com\Administrator
    but I am unable to open the file inside the folder and I get an
    Access is denied message.
    It is very strange to get an "Access is denied" message because on the text file when I right click and click Properties -> Advanced -> Details, under the Recovery Certificates, the Administrator account's certificate is listed
    and its thumbprint corresponds to the same recovery certificate which I created in step 3. But I am still unable to access the file.
    Do you have any idea why? Am I missing something?
    Thanks in advance.
    MCT, MCSA/MCSE Security
    http://esitech.spaces.live.com/

    Hi
    The Client1 user needs to enrol via GPO to get the recovery certificate normally via automatic enrolment
    Check the Personal Certificate store for Client1
    I think the policy needs to be applied before you encrypt any data
    To manually recover
    Did you export the Private key when you did the export ?
    Did you export to a .cer file

  • Sql server agent not work

    hi every one ,
    i use sql server agent to make a job which delete some rows from my table at 12:00 AM
    this job works on (Mydatabase1) but when i make another job to another database(Mydatabase2)
    i get this error from ViewJob HIstory :
    Myjob2,Error,1,FATMA\MSSQLSERVER2008,Myjob2,step2,,Executed as user: NT AUTHORITY\SYSTEM. DELETE
    failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'. Verify that SET options are
    correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query
    notifications and/or XML data type methods and/or spatial index operations. [SQLSTATE 42000] (Error 1934).  The step
    failed
    please inform me what is that error means?and how can i fix it?and why this job work to database and not work for another!!!
    best wishes
    fatma
    fatma mohamed

    Hi Miloslav Peterka,
    i set Quoted Identifiers to true it was false,it woorked in first time after that i get this error(but in my worked job on myDatabase1 the Quoted Identifiers was false.)
    Date  24-05-2010 10:44:28 ص
    Log  Job History (AttendanceJob)
    Step ID  0
    Server  FATMA\MSSQLSERVER2008
    Job Name  AttendanceJob
    Step Name  (Job outcome)
    Duration  00:00:01
    Sql Severity  0
    Sql Message ID  0
    Operator Emailed  
    Operator Net sent  
    Operator Paged  
    Retries Attempted  0
    Message
    The job failed.  The Job was invoked by User sa.  The last step to run was step 1 (attStep).
    wat is the reason of that error?
    best wishes
    fatma mohamed

  • [SOLVED] Touchpad Synaptics not works after last update of xf86-input

    after this packages
    xf86-input-synaptics 1.8.0-2 <<< works
    xf86-input-synaptics 1.8.0-3 << not works
    https://projects.archlinux.org/svntogit … 54796cff46
    dmesg|grep input
    [ 0.866883] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 1.842679] input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:04F3:0103.0001/input/input2
    [ 1.842756] hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-0000:00:14.0-1/input0
    [ 1.843934] input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:04F3:0103.0002/input/input3
    [ 1.844001] hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-0000:00:14.0-1/input1
    [ 2.169742] input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:09DA:9066.0003/input/input4
    [ 2.169933] hid-generic 0003:09DA:9066.0003: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4TECH USB Device] on usb-0000:00:14.0-2/input0
    [ 2.171262] input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/0003:09DA:9066.0004/input/input5
    [ 2.171357] hid-generic 0003:09DA:9066.0004: input,hidraw3: USB HID v1.11 Mouse [A4TECH USB Device] on usb-0000:00:14.0-2/input1
    [ 10.099521] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
    [ 10.099624] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
    [ 10.099692] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
    [ 10.398671] input: PC Speaker as /devices/platform/pcspkr/input/input9
    [ 11.840489] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
    [ 12.211308] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3a/LNXVIDEO:00/input/input11
    [ 12.212530] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12
    [ 13.254950] sound hdaudioC0D0: inputs:
    [ 13.580490] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input13
    [ 13.580985] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
    [ 13.581106] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
    [ 13.581224] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
    [ 17.274881] input: WebCam SC-13HDL11939N as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
    journalctl -b |grep input
    ago 21 09:02:37 drog-laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    ago 21 09:02:37 drog-laptop kernel: input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/0003:04F3:0103.0001/input/input2
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-0000:00:14.0-1/input0
    ago 21 09:02:37 drog-laptop kernel: input: HID 04f3:0103 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:04F3:0103.0002/input/input3
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-0000:00:14.0-1/input1
    ago 21 09:02:37 drog-laptop kernel: input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:09DA:9066.0003/input/input4
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:09DA:9066.0003: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [A4TECH USB Device] on usb-0000:00:14.0-2/input0
    ago 21 09:02:37 drog-laptop kernel: input: A4TECH USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/0003:09DA:9066.0004/input/input5
    ago 21 09:02:37 drog-laptop kernel: hid-generic 0003:09DA:9066.0004: input,hidraw3: USB HID v1.11 Mouse [A4TECH USB Device] on usb-0000:00:14.0-2/input1
    ago 21 09:02:40 drog-laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
    ago 21 09:02:40 drog-laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
    ago 21 09:02:40 drog-laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
    ago 21 09:02:41 drog-laptop kernel: input: PC Speaker as /devices/platform/pcspkr/input/input9
    ago 21 09:02:42 drog-laptop kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
    ago 21 09:02:42 drog-laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3a/LNXVIDEO:00/input/input11
    ago 21 09:02:42 drog-laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input12
    ago 21 09:02:43 drog-laptop kernel: sound hdaudioC0D0: inputs:
    ago 21 09:02:44 drog-laptop kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input13
    ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
    ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
    ago 21 09:02:44 drog-laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
    ago 21 09:02:47 drog-laptop kernel: input: WebCam SC-13HDL11939N as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17
    ago 21 09:02:52 drog-laptop acpid[589]: starting up with netlink and the input layer
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event7 (Power Button)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event11 (Video Bus)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event10 (Video Bus)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event6 (Power Button)
    ago 21 09:02:53 drog-laptop systemd-logind[585]: Watching system buttons on /dev/input/event5 (Lid Switch)
    cat /usr/share/X11/xorg.conf.d/50-synaptics.conf
    # Example xorg.conf.d snippet that assigns the touchpad driver
    # to all touchpads. See xorg.conf.d(5) for more information on
    # InputClass.
    # DO NOT EDIT THIS FILE, your distribution will likely overwrite
    # it when updating. Copy (and rename) this file into
    # /etc/X11/xorg.conf.d first.
    # Additional options may be added in the form of
    # Option "OptionName" "value"
    Section "InputClass"
    Identifier "touchpad catchall"
    Driver "synaptics"
    MatchIsTouchpad "on"
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    # This option is recommend on all Linux systems using evdev, but cannot be
    # enabled by default. See the following link for details:
    # http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html
    MatchDevicePath "/dev/input/event*"
    EndSection
    Section "InputClass"
    Identifier "touchpad ignore duplicates"
    MatchIsTouchpad "on"
    MatchOS "Linux"
    MatchDevicePath "/dev/input/mouse*"
    Option "Ignore" "on"
    EndSection
    # This option enables the bottom right corner to be a right button on clickpads
    # and the right and middle top areas to be right / middle buttons on clickpads
    # with a top button area.
    # This option is only interpreted by clickpads.
    Section "InputClass"
    Identifier "Default clickpad buttons"
    MatchDriver "synaptics"
    Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
    Option "SecondarySoftButtonAreas" "58% 0 0 8% 42% 58% 0 8%"
    EndSection
    # This option disables software buttons on Apple touchpads.
    # This option is only interpreted by clickpads.
    Section "InputClass"
    Identifier "Disable clickpad buttons on Apple touchpads"
    MatchProduct "Apple|bcm5974"
    MatchDriver "synaptics"
    Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
    EndSection
    xinput
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ HID 04f3:0103 id=11 [slave pointer (2)]
    ⎜ ↳ A4TECH USB Device id=12 [slave pointer (2)]
    ⎜ ↳ A4TECH USB Device id=13 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Power Button id=9 [slave keyboard (3)]
    ↳ HID 04f3:0103 id=10 [slave keyboard (3)]
    ↳ WebCam SC-13HDL11939N id=14 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
    synclient
    Couldn't find synaptics properties. No synaptics driver loaded?
    lsmod
    Module Size Used by
    bbswitch 12878 0
    nls_iso8859_1 12461 1
    nls_cp437 16553 1
    vfat 21231 1
    fat 61984 1 vfat
    fuse 87446 5
    uvcvideo 78952 0
    videobuf2_vmalloc 12816 1 uvcvideo
    ath3k 12685 0
    videobuf2_memops 12519 1 videobuf2_vmalloc
    videobuf2_core 47787 1 uvcvideo
    ecb 12737 1
    v4l2_common 12995 1 videobuf2_core
    btusb 25625 0
    bluetooth 394557 3 ath3k,btusb
    videodev 126443 3 uvcvideo,v4l2_common,videobuf2_core
    media 18365 2 uvcvideo,videodev
    6lowpan_iphc 16588 1 bluetooth
    snd_hda_codec_hdmi 45117 1
    snd_hda_codec_realtek 67127 1
    snd_hda_codec_generic 63126 1 snd_hda_codec_realtek
    nvram 13034 0
    joydev 17063 0
    mousedev 17272 0
    ipt_REJECT 12465 1
    xt_comment 12427 2
    arc4 12536 2
    xt_LOG 17156 5
    ath9k 94538 0
    ath9k_common 21746 1 ath9k
    ath9k_hw 403753 2 ath9k_common,ath9k
    ath 26067 3 ath9k_common,ath9k,ath9k_hw
    mac80211 514630 1 ath9k
    r8169 68119 0
    mii 12675 1 r8169
    cfg80211 454161 4 ath,ath9k_common,ath9k,mac80211
    snd_hda_intel 26327 4
    snd_hda_controller 26727 1 snd_hda_intel
    snd_hda_codec 108552 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
    i915 864723 4
    drm_kms_helper 49262 1 i915
    snd_hwdep 17244 1 snd_hda_codec
    snd_pcm 88487 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
    iTCO_wdt 12831 0
    iTCO_vendor_support 12649 1 iTCO_wdt
    coretemp 12820 0
    hwmon 12930 1 coretemp
    led_class 12859 1 ath9k
    intel_rapl 17356 0
    rfkill 18867 3 cfg80211,bluetooth
    x86_pkg_temp_thermal 12951 0
    psmouse 102792 0
    drm 258005 6 i915,drm_kms_helper
    intel_powerclamp 17122 0
    kvm_intel 143217 0
    snd_timer 26614 1 snd_pcm
    shpchp 35210 0
    lpc_ich 20768 0
    mei_me 17941 0
    intel_gtt 17848 1 i915
    kvm 413027 1 kvm_intel
    crct10dif_pclmul 13394 0
    crc32_pclmul 12915 0
    crc32c_intel 21809 0
    ghash_clmulni_intel 12978 0
    cryptd 18553 1 ghash_clmulni_intel
    microcode 22061 0
    evdev 21544 29
    pcspkr 12595 0
    mac_hid 12633 0
    i2c_algo_bit 12744 1 i915
    i2c_i801 16965 0
    mei 75033 1 mei_me
    serio_raw 12849 0
    i2c_core 50152 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
    tpm_tis 17134 0
    thermal 17559 0
    fan 12681 0
    battery 13356 0
    snd 69340 16 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
    soundcore 13031 2 snd,snd_hda_codec
    tpm 31467 1 tpm_tis
    video 17995 1 i915
    button 12909 1 i915
    processor 27777 0
    xt_limit 12601 7
    wmi 17339 0
    ac 12715 0
    xt_tcpudp 12527 11
    xt_addrtype 12557 4
    nf_conntrack_ipv4 17706 7
    nf_defrag_ipv4 12483 1 nf_conntrack_ipv4
    xt_conntrack 12681 7
    ip6_tables 26025 0
    nf_conntrack_netbios_ns 12445 0
    nf_conntrack_broadcast 12365 1 nf_conntrack_netbios_ns
    nf_nat_ftp 12460 0
    nf_nat 22338 1 nf_nat_ftp
    nf_conntrack_ftp 16783 1 nf_nat_ftp
    nf_conntrack 87324 7 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4
    iptable_filter 12536 1
    ip_tables 26011 1 iptable_filter
    x_tables 27104 10 xt_comment,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ipt_REJECT,ip6_tables,xt_addrtype
    ext4 497695 2
    crc16 12343 2 ext4,bluetooth
    mbcache 17171 1 ext4
    jbd2 86460 1 ext4
    hid_generic 12393 0
    usbhid 44507 0
    hid 102220 2 hid_generic,usbhid
    sd_mod 44356 5
    sr_mod 21903 0
    cdrom 47479 1 sr_mod
    crc_t10dif 12431 1 sd_mod
    crct10dif_common 12356 2 crct10dif_pclmul,crc_t10dif
    atkbd 22254 0
    libps2 12739 2 atkbd,psmouse
    ahci 29195 4
    libahci 27158 1 ahci
    libata 181553 2 ahci,libahci
    ehci_pci 12512 0
    scsi_mod 142915 3 libata,sd_mod,sr_mod
    xhci_hcd 152990 0
    ehci_hcd 69939 1 ehci_pci
    usbcore 199328 7 ath3k,btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd
    usb_common 12440 1 usbcore
    i8042 18002 1 libps2
    serio 18282 6 serio_raw,atkbd,i8042,psmouse
    EDIT:
    cat /var/log/Xorg.0.log| grep Synap
    [ 301.566] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event9)
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 301.566] (II) Using input driver 'evdev' for 'SynPS/2 Synaptics TouchPad'
    [ 301.566] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 301.566] (**) evdev: SynPS/2 Synaptics TouchPad: Device: "/dev/input/event9"
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found 3 mouse buttons
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute axes
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute multitouch axes
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found x and y absolute axes
    [ 301.566] (--) evdev: SynPS/2 Synaptics TouchPad: Found absolute touchpad.
    [ 301.566] (II) evdev: SynPS/2 Synaptics TouchPad: Configuring as touchpad
    [ 301.566] (**) evdev: SynPS/2 Synaptics TouchPad: YAxisMapping: buttons 4 and 5
    [ 301.567] (**) evdev: SynPS/2 Synaptics TouchPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 301.567] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 16)
    [ 301.567] (II) evdev: SynPS/2 Synaptics TouchPad: initialized for absolute axes.
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 301.567] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 301.567] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    (EE) [dix] SynPS/2 Synaptics TouchPad: unable to find touch point 1
    EDIT2:
    SOLVED!
    just remove /etc/X11/xorg.conf.d/10-evdev.conf
    Last edited by drog (2014-08-21 13:29:49)

    lordheavy wrote:
    X reads first configuration in /usr/share/X11/xorg.conf.d then /etc/X11/xorg.conf.d
    When you copy 10-evdev.conf file into /etc/X11 you completly override previous system configuration. It's the reason copying synaptics configuration file into /etc/X11 fixes the issue
    Defining default system configuration in /etc/X11 with previous xorg was a mistake, now it's fixed.
    Wiki should be fixed. It's not a packaging bug, but a configuration bug.
    @lordheavy
    I agree with you that the new xf86-input-synaptics package is using the right configuration scheme, however it is breaking the functionality on every installed system. It was a packaging bug, which is now fixed, but it has to be handled manually by most users of previous versions. That's why I won't re-open the bug report FS#41589. Instead, I am asking here: shouldn't this change be notified to the users just like it has been done for most breaking changes on archlinux frontpage news?
    By the way, thanks for your great work.

  • Solved - Helix pen not working

    I think this might be helpful to those who suffer she same problem: My OS is Windows 8.1. One day the pen just stoped working. Seems that there was no problem with hardware and driver - nothing wrong but the pen. Then another day my Norton, which was pre-installed on my Helix, expired and I decided to unistall it. Surprisingly after uninstallation the pen started to work!

    Tried it in the BIOS, looks like it's a hardware problem.  Lenovo service was surprisingly quick and direct on the phone.  They provided me the option of sending it in (with a 7 day turnaround), or taking it to a local warranty service center (on Long Island).  I'll check out the local center first tomorrow.
    mdovey wrote:
    Try booting into BIOS and seeing if the pen works there (although the BIOS is text based it will respond to touch and pen inputs, e.g. you can select the various menus screens by touching the text with the pen).
    If the pen does work in BIOS, then the problem is probably software\driver related and reinstalling\refreshing Windows should solve the problem.
    If the pen does not work in BIOS, then the problem is probably hardware related and you will need to contact Lenovo support to arrange a repair\repacement.
    Matthew
    mdovey wrote:
    Try booting into BIOS and seeing if the pen works there (although the BIOS is text based it will respond to touch and pen inputs, e.g. you can select the various menus screens by touching the text with the pen).
    If the pen does work in BIOS, then the problem is probably software\driver related and reinstalling\refreshing Windows should solve the problem.
    If the pen does not work in BIOS, then the problem is probably hardware related and you will need to contact Lenovo support to arrange a repair\repacement.
    Matthew

  • [SOLVED] DVB-T Not working with 2.6.30

    Hey, I just upgraded to 2.6.30 and my DVB-T card (TerraTec Piranha) which uses the siano driver doesn't work anymore.
    It worked fine before the upgrade but doesn't register any DVB-T device since the reboot after the upgrade (Atleast kaffeine doesn't show the DVB-T button and dmesg doesn't list that a new device was registered).
    After starting my computer:
    [fox@PC103 ~]$ dmesg | grep sms
    smsusb_probe: line: 416: rom interface 0 is not used
    usb 4-2: firmware: requesting sms1xxx-stellar-dvbt-01.fw
    smsusb1_load_firmware: failed to open "sms1xxx-stellar-dvbt-01.fw" mode 4, trying again with default firmware
    usbcore: registered new interface driver smsusb
    dmesg after reconnecting the stick:
    eth0: no IPv6 routers present
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    smsusb_onresponse: line: 69: error, urb status -84, 0 bytes
    usb 4-2: USB disconnect, address 3
    usb 4-2: new full speed USB device using uhci_hcd and address 4
    usb 4-2: configuration #1 chosen from 1 choice
    smsusb_probe: line: 416: rom interface 0 is not used
    usb 4-2: firmware: requesting sms1xxx-stellar-dvbt-01.fw
    smsusb1_load_firmware: failed to open "sms1xxx-stellar-dvbt-01.fw" mode 4, trying again with default firmware
    usb 4-2: firmware: requesting dvbt_bda_stellar_usb.inp
    usb 4-2: USB disconnect, address 4
    usb 4-2: new full speed USB device using uhci_hcd and address 5
    usb 4-2: configuration #1 chosen from 1 choice
    The file "dvbt_bda_stellar_usb.inp" exists in "/lib/firmware/" and seems to be used fine
    Unluckily enough I don't know what the log looked like before the upgrade.
    Whats wrong? How do I get DVB-T working again?
    //Edit:
    [fox@PC103 ~]$ sudo modprobe smsdvb
    did the trick!
    - Shouldn't this be done by default?!
    PS / Not related to topic: While I'm at it, how could I fix this: "WARNING: All config files need .conf: /etc/modprobe.d/framebuffer_blacklist.pacsave, it will be ignored in a future release." - I get it about twenty times at startup since some time.
    //Edit:
    Fixed by removing the file and using framebuffer_blacklist.conf instead
    Last edited by JayFoxRox (2009-06-24 16:12:31)

    Hiya, I was having the identical problem with an Acer AspireOne D250 netbook using the atl1c kernel mod.  The Arch Wiki entry for my netbook specifically has a workaround posted, though I believe it's applicable here:
    http://wiki.archlinux.org/index.php/Ace … e_D250_LAN
    With Archlinux 2009.08 the installation did not work from the beginning on an Aspire One D250. The LAN was not working properly. This could be traced down to the Kernel 2.6.30 which had broken network drivers. To get the LAN working, use the Archlinux core install. After installing Archlinux, get the Kernel 2.6.31 and the Kernel Headers on a USB stick and install it via "pacman -U". After rebooting, the LAN should work properly.
    Hope this helps!

Maybe you are looking for