[Solved] Netcfg 2.6.1 - suddenly fails to associate with WPA2 network

Everything around here seems to be breaking these days... Anyways.
I upgraded netcfg yesterday. Today I fire up my laptop, but no wireless. I run netcfg again, this is what wpa_supplicant spits out:
# netcfg intel
:: intel up [BUSY]
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
^C
The funny thing is, nothing's changed in the netcfg config file, which looks like this:
CONNECTION="wireless"
INTERFACE="intel"
HOSTNAME="hermes"
# AP authentication
SCAN="yes"
SECURITY="wpa-config"
WPA_CONF="/etc/wpa_supplicant.conf"
WPA_OPTS="-Dwext -B"
ESSID="Zeus 802.11n"
# IP address
IP="dhcp"
DHCP_TIMEOUT=10
I compared my config to the examples that come with netcfg - just to be sure nothing's changed that I wasn't aware of - but it looks pretty identical. Oddly enough, calling wpa_supplicant and then dhcpcd directly just connects me to my WLAN, like netcfg used to be able to do.
For reference, netcfg seems to call wpa_supplicant like this, going by htop's output:
wpa_supplicant -Dwext,nl80211 -c /etc/wpa_supplicant.conf -B -i intel -d
When run separately, however, that works just fine, just like using -Dwext like I used to do before.
Last edited by .:B:. (2011-06-21 22:29:55)

My understanding is that the thing fails in start_wpa(). From /usr/lib/network/8021x:
start_wpa()
local INTERFACE="$1" WPA_CONF="$2" WPA_DRIVER="$3"
shift 3
local WPA_OPTS="$*"
wpa_supplicant -B -P "/run/wpa_supplicant_${INTERFACE}.pid" -i "$INTERFACE"-D "$WPA_DRIVER" -c "$WPA_CONF" $WPA_OPTS
sleep 1
if [[ ! -f "/run/wpa_supplicant_${INTERFACE}.pid" ]]; then
return 1
fi
So, you should have seen "-P' in htop, no? Have you tried w/o WPA_OPTS?
EDIT: OK, I was wrong. The error seems to come from wpa_supplicant/wp_cli calls with the new /run standard:
arch~> grep "/run/wpa_supplicant" ./usr/lib/network/8021x
WPA_CLI="wpa_cli -p /run/wpa_supplicant"
wpa_supplicant -B -P "/run/wpa_supplicant_${INTERFACE}.pid" -i "$INTERFACE" -D "$WPA_DRIVER" -c "$WPA_CONF" $WPA_OPTS
if [[ ! -f "/run/wpa_supplicant_${INTERFACE}.pid" ]]; then
if [[ -f "/run/wpa_supplicant_$1.pid" ]]; then
kill "$(cat "/run/wpa_supplicant_$1.pid")" &>/dev/null &
wpa_supplicant -B -i"$INTERFACE" -Dnl80211,wext -C/run/wpa_supplicant -P/run/wpa_supplicant.pid || return 1
kill "$(cat /run/wpa_supplicant.pid)"
echo "ctrl_interface=/run/wpa_supplicant" >> "$WPA_CONF/wpa.conf" # we know $WPA_CONF now has no spaces, but it may have other nasty chars, so still needs to be quoted
Could you change the ctrl_interface to to /run/wpa_supplicant in /etc/wpa_supplicant.conf?
Last edited by Leonid.I (2011-06-21 21:19:59)

Similar Messages

  • Failed 2 associate with network

    hi i recently have purchased a bb 9360 and im tryin to connect to my home wifi but the error msg comes up sayin failed to associate with network. ive also tried it at my other family members house on there wifi and gettin the same msg, i use 2 hav a bb 8520 and had no problems conectin to the wifi. plz plz plz could someone with any info how 2 solve this problem help me out with sujestions as i live in a area with poor signal so i use the wifi for bbm, internet etc...
     many thanks junior

    Hey Junior,
    Welcome to the BlackBerry® Support Community Forums.
    This can be caused when media access control (MAC) address filtering is enabled on the Wi-Fi® network,add the MAC address of the BlackBerry® smartphone to the accepted MAC address list for the Wi-Fi network.
    How to find the MAC address of a Wi-Fi enabled BlackBerry smartphone
    http://btsc.webapps.blackberry.com/btsc/KB13233
    I hope this helps.
    -HB
    Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
    Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

  • [SOLVED] netcfg DHCP IP lease attempt failed

    I'm trying to configure my network settings, I made a profile, netcfg recognizes the profile, but when it loads I get that error (DHCP IP lease attempt failed). Here is my profile...
    CONNECTION='wireless'
    INTERFACE='wlan0'
    SECURITY='none'
    ESSID='my network name'
    IP='dhcp'
    DCHP_TIMEOUT='30'
    Last edited by oldstutz (2010-07-30 18:33:54)

    jogan wrote:
    jogan wrote:
    Do you have any idea how to load the rt2860 driver from /lib/firmware/rt2860.bin?
    My attempt to load the driver with MODULES in /etc/rc.conf has been unsuccessful.
    oldstutz wrote:RaLink RT2860, and I have rt2860sta in my modules
    I've battled this issue for weeks on my notebook ... wireless worked on Arch (2009.08)
    last year.  Seems to me now the culprit maybe rt2860sta.
    OK, let's check
    lsmod | grep -i rt2860

  • [Solved] Netcfg switches between interfaces

    Hello,
    I switched to netcfg, to get a pure systemd install.
    How ever, sometimes the netcfg can't bring up the interface even though it used that interface before.
    It's like netcfg are switching between what interface it can use. Sometimes it's eth0 other times eth1.
    So when I boot and don't have any network connection, I change the config files to use the other interface (ex. eth1) and netcfg can connect.
    How can this be?
    configs:
    /etc/network.d/mynetwork
    CONNECTION='ethernet'
    DESCRIPTION='A basic static ethernet connection using iproute'
    INTERFACE='eth1'
    IP='static'
    ADDR='192.168.1.3'
    #ROUTES=('192.168.0.0/24 via 192.168.1.2')
    GATEWAY='192.168.1.1'
    DNS=('dns1', 'dns2)
    ## For IPv6 autoconfiguration
    #IP6=stateless
    ## For IPv6 static address configuration
    #IP6='static'
    #ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
    #ROUTES6=('abcd::1234')
    #GATEWAY6='1234:0:123::abcd'
    /etc/conf.d/netcfg
    # Enable these netcfg profiles at boot time.
    # - prefix an entry with a '@' to background its startup
    # - set to 'last' to restore the profiles running at the last shutdown
    # - set to 'menu' to present a menu (requires the dialog package)
    # Network profiles are found in /etc/network.d
    NETWORKS=(mynetwork)
    # Specify the name of your wired interface for net-auto-wired
    WIRED_INTERFACE="eth1"
    # Specify the name of your wireless interface for net-auto-wireless
    #WIRELESS_INTERFACE="wlan0"
    # Array of profiles that may be started by net-auto-wireless.
    # When not specified, all wireless profiles are considered.
    #AUTO_PROFILES=("profile1" "profile2")
    Last edited by KLIM (2012-12-06 14:22:23)

    Did you checked for netcfg.service is enabled (systemd) ?
    BTW, I see a missing single quote on DNS line : DNS=('dns1', 'dns2)
    You may check these forum posts :
    "[SOLVED] Netcfg.service always failing." @ https://bbs.archlinux.org/viewtopic.php?id=148079
    "Systemd and Netcfg" @ https://bbs.archlinux.org/viewtopic.php?id=151662
    "netcfg/systemd not bringing up eth0 (static profile)" @ https://bbs.archlinux.org/viewtopic.php?id=147300
    "[SOLVED] netcfg fails at boot" @ https://bbs.archlinux.org/viewtopic.php?pid=1200518
    And this wiki entry about netcfg @ https://wiki.archlinux.org/index.php/Netcfg

  • External USB Maxtor One-Touch 3  suddenly fails to mount on MacBook Pro:

    External USB HD suddenly fails to mount on MacBook Pro:
    My One Touch III 600GB drive, external power supply, suddenly will not mount and is not recognized by the system profiler or Disk Utility, however, drive, connected USB, appears under windows XP.
    1. Power cable and usb cable working.
    2. Using external AC adapter(not relying on USB power).
    3. Other USB devices, mice, flash drives work on both USB ports.
    4. Drive works on Windows, folders and data integrity ok.
    5. Drive format is NTFS.
    6. No Maxtor software installed.
    7. No humming or strange noises emanating from drive.
    8. No problem to January 14, 2008,
    9. Mac OS 10.4.10 updates last downloaded and installed Jan 20, 2008.
    10.1 blip of the light on "The One Touch Button", then light turns solid white.
    Questions:
    1. Does Apple set sleep or lock switch for devices (drives)?
    2. If so, can it be reset manually?
    3. Does Apple have configuration profile for devices, like a registry key?
    4. If so, where is it located?
    Configuration:
    Dual 2 GHz MacBook Pro 15”
    2 GB DDR SDRAM
    OSX 10.4.10
    2 USB Ports Left and Right

    NOTE: This Update is required when using a OneTouch Drive as a bootable device. Seagate suggests that you dismount and disconnect your FireWire Drive before continuing.
    Users have identified issues when connecting OneTouch External Drives to FireWire Ports on their Mac G4 and/or G5 computers. These Problems range from system hangs, kernel panics to slow data transfer rates. The cause of these problems has been traced back to the FireWire Driver. Seagate has resolved these problems through updated FireWire Drivers.
    I am using USB and not trying to use drive as a boot device.

  • [SOLVED]Netcfg works great manually, but when using the daemon it wont

    I installed netcfg a really long time ago following the arch wiki. When I first installed it and set everything up, it was all working perfectly.
    For the past three or four months Ive been having problems where netcf daemon is failing to connect (home wireless network 256bit wep). It takes about 20 seconds just waiting and eventually says failed. If I log in and run the command manually (sudo netcfg home-wifi) it connect perfectly fine every time.
    Ive tried everything I can think of including different QUIRKS and changing permissions on the profiles but nothing works. I also tried using the netcfg menu but it doesnt work like that either. I went over the wiki page again thinking something might have chnaged, but its all the same. I even reinstalled and configured again but still nothing.
    heres my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/New_York"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(acpi-cpufreq cpufreq_ondemand vboxdrv loop)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="Arch"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="dhcp"
    eth0="dhcp"
    INTERFACES=(eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    NETWORKS=(home-wifi)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng crond hal cpufreq !network net-profiles @netfs @alsa @sensors @mpd)
    What gets me is that it actually takes longer to fail then it does when I manually connect. It times out for like 20 seconds, but when I manually connect its almost instantaneous.
    Last edited by tjwoosta (2010-03-02 05:31:37)

    I had arch installed on my Sony VAIO, had this problem, and then fixed it somehow.  That was several months ago, recently I fried the laptop so I just reinstalled and can't remember.  But now I have a "solution"  haha
    this is kind of silly how I got it to work, though.
    I created another profile "home-wifi-boot" with a short timeout, this is called from rc.conf.
    then I put "/usr/bin/netcfg home-wifi" in my /etc/rc.local  , which is exactly the same but has a 30 sec timeout.
    This just does the same thing as I was doing manually, runs netcfg a second time.  It works for me!
    Last edited by jamba (2010-02-14 15:30:58)

  • [SOLVED] Netcfg and Wireless connections stopped working

    I've been using Netcfg for a while now on my laptop and I've had no problems connecting to the internet until last week. Since the last pacman update I did (around Wednesday I believe) my laptop has not been able to connect to the internet again. It doesn't recognize my wireless interface even though it did before, and netcfg gives me a strange output when I try to connect to my network and tells me the network is not available. I've gone through the steps in the wiki about installing wireless drivers and I've redone that but it still does not work.
    Here is what Netcfg gives me when I try to connect:
    :: LosPin up [BUSY]
    nl80211: 'nl80211' generic netlink not found
    ioctl[SIOCSIWMODE]: Operation not supported
    ioctl[SIOCGIWRANGE]: Operation not supported
    ioctl[SIOCGIWMODE]: Operation not supported
    ioctl[SIOCSIWAP]: Operation not supported
    ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWENCODE]: Operation not supported
    ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWENCODE]: Operation not supported
    ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWENCODE]: Operation not supported
    ioctl[SIOCSIWENCODEEXT]: Operation not supported
    ioctl[SIOCSIWENCODE]: Operation not supported
    > Wireless network "LosPin" not present.
    [FAIL]
    I know the network is present because when I boot into Windows on this same laptop it connects without any issues. I think it is a driver issue but re-installing the driver has not helped so I'm wondering if anyone can help me out.
    This is my netcfg profile if needed:
    CONNECTION="wireless"
    ESSID="LosPin"
    INTERFACE="eth0"
    SCAN="yes"
    TIMEOUT="10"
    SECURITY="wpa"
    KEY=
    WPA_Driver='wext'
    IP='static'
    ADDR='10.0.0.80'
    GATEWAY='10.0.0.1'
    DNS='10.0.0.1'
    The reason that the interface is set to eth0 is because it is the only interface for which netcfg tries to connect to the network. If I use wlan0 as the interface it tells me it doesn't exist, and before I had the problem, the interface I used was eth1, which now netcfg says does not exist either.
    Any help is greatly appreciated.
    Last edited by Hoest (2011-11-17 23:32:29)

    I've checked and it's definitely not an rfkill issue. I've tried to connect to the network with two different netcfg profiles, one using wpa_supplicant and the other with configsection. Both give me the same "WPA Authentication/Association Failed" error. There was one try with the wpa_supplicant profile that gave the a "network not found" error but afterwards it went back to the original error. Here are my profiles if needed.
    configsection profile:
    CONNECTION='wireless'
    INTERFACE='eth0'
    SECURITY='wpa-configsection'
    ESSID='LosPin'
    IP='dhcp'
    TIMEOUT='130'
    CONFIGSECTION='
    ssid="LosPin"
    key_mgmt=WPA-PSK
    psk="..."'
    wpa_supplicant profile:
    CONNECTION="wireless"
    INTERFACE="eth0"
    TIMEOUT="60"
    WPA_Driver='wext'
    IP='dhcp'
    SECURITY='wpa-config'
    WPA_CONF='/etc/wpa_supplicant.conf'
    And this is my wpa_supplicant.conf:
    ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel
    network={
    ssid="LosPin"
    proto=RSN
    key_mgmt=WPA-PSK
    pairwise=CCMP TKIP
    group=CCMP TKIP
    #psk="..."
    psk=84e710904340353a5217eb63ced7e8f4beb38bf6317bf4648e8b4557c7f3442d
    Again, thank you all for all your help.

  • Two Macbook pros circa 2009 in our temporary household in Turkey suddenly failed to boot and got stuck on the grey screen. They were able to boot at the Apple store, but not when we brought them back to our apartment. Could this be a coincidence?   A

    Two Macbook pros circa 2009 in our temporary household in Turkey suddenly failed to boot and got stuck on the grey screen. They were able to boot at the Apple store, but not when we brought them back to our apartment. Could this be a coincidence?   A

    THank you Ogelthorpe. When my wife's computer I went on line to the site that you sent and tried everything But nothing worked. When my son came to visit and his MacBook Pro did exactly the same thing we became suspicious - too much of a coincidence. We took both computers somewhere else, out of our apartment, and they both booted. We ran disk utility on both, but the report in both cases was that there are no issues with the hard drive.  Back in our apartment neither will boot up. My MacBook Pro is a later model with a solid state drive and it seems to work fine here.. I tried an external drive and it works fine. We think that this has something to do with some kind of magnetic interference in our apartment to which the 2009  drives are susceptible.  It is indeed a mystery!
    alf

  • Display suddenly failed. How to acquire bulb?

    My display suddenly failed. In the right room light, I can see the display working very, very, very faintly. So I'm thinking (hoping) it's just a backlight. If so, where can I get a replacement, how much should it cost, and where can I find installation directions?
    If this is too costly or difficult, I would consider buying a screen or entire computer. If I choose this route, is it possible to upgrade my 17" monitor w/ a 20" monitor if I can find one?
    Please advise.
    Thanks in advance.
    -Don!

    The part for that one is a 922-5298, and they are easy to replace as they are located in the display assembly along one side of it. You do not have to open the base or disconnect the arm to replace one. They are likely available for $ 49.00 or so: contact me at the electronic mail address in my Public Profile for help in obtaining one.
    You cannot swap display assemblies or arms, as the larger displays are cabled and terminated differently, and will not mate with the logic board or one end or the display assembly on the other.

  • My password has suddenly failed to work

    A password used for years has suddenly failed to unlock my MacBook. Any suggestions?

    You have done exceedingly well to get 4years.. that is about double the normal lifespan.
    Apple did have an extended warranty for them but since all TC made in 2008 have now passed 3years the program is finished.. no warranty is offered for product older than 3years.. it is well and truly past its useby (at least so Apple think).. Repair is possible but the price of a new one is perhaps 3x the repair cost unless you DIY. Which I also encourage. The exception of course is where you have vital data.. stored under the erronous idea that the TC was reliable storage.. a full repair to the TC ends up cheaper than any other form of data recovery.. plus you get a working TC out of it you can keep or resell.

  • [SOLVED] netcfg static IP not persisting across reboots in VM

    I ran into an issue with netcfg static IP not persisting across reboots in a VM. I figured it out, but it took me awhile as a brand new user, so I thought I'd post it.
    Setup
    Using VMWare Workstation 8.0.3 build-703057 with bridged networking
    Host OS: Linux Mint 14 64-bit
    Guest OS: Arch Linux 2013.03.01 x86_64
    Given a fresh install on the guest, setup netcfg:
    cd /etc/network.d
    cp examples/ethernet-static ./myprofile
    nano myprofile
    # customize this file. I also added NETMASK='255.255.255.0'
    systemctl enable netcfg@myprofile
    systemctl start netcfg@myprofile
    Test the configuration. It should be successful:
    ping google.com
    Problem
    See if the changes survive a reboot.
    reboot
    ping google.com
    I got the error "connect: Network is unreachable".
    Check the logs:
    journalctl
    G
    I found the following netcfg failure..
    [email protected]: main process exited, code=exited, status=1/FAILURE
    ..prior to the following device initialization:
    kernel: e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
    system-udevd[117]: renamed network interface eth0 to emp2s0
    Solution
    It looks like netcfg is being started before the device it depends on has been initialized. Inform systemd of the
    dependency so they start in the proper order:
    # nano /etc/systemd/system/multi-user.target.wants/[email protected]
    # Add the following to [Unit]. Remember to replace enp2s0 with your device name.
    Requires=sys-subsystem-net-devices-enp2s0.device
    After=sys-subsystem-net-devices-enp2s0.device
    Test again:
    reboot
    ping google.com
    This should now be successful.

    fukawi2 wrote:
    $ man netcfg-profiles wrote:
           Miscellaneous options
               IPCFG
                   Array of arguments to pass to ip. The power of this options is
                   that it allows both simple and complicated routing
                   configurations, within the framework of netcfg.
               SKIPNOCARRIER
                   ‘yes’/‘no’. Don’t abort interface setup if no carrier is
                   found.
    Thank you, [Solved].

  • [SOLVED] Makepkg option FORTIFY_SOURCE causes build fail

    I have a pkg in the AUR, dcc, which fails to build with the current GCC toolchain (4.8.2.8). It does, however, build on a system with GCC 4.6.3. The problem has been identified as being caused by the FORTIFY_SOURCE=2 option in /etc/makepkg.conf.
    CPPFLAGS="-D_FORTIFY_SOURCE=2"
    I can fix the package build by unsetting CPPFLAGS in the PKGBUILD's build() function.
    build() {
    cd $srcdir/$pkgname-$pkgver
    unset CPPFLAGS
    ./configure --with-installroot=${pkgdir} \
    --mandir=/usr/share/man --homedir=/opt/dcc \
    --bindir=/usr/bin --libexecdir=/usr/lib/dcc
    make
    Before I upload an amended package, I'd like to clarify whether fixing it in this way is the right thing to do.
    Or, is this a problem with makepkg (I've seen a few similar mentions, like this one). Or is it the fault of something else... gcc, perhaps ?
    I'd appreciate advice on how to approach this one.
    (I also asked the DCC people about this via their mailing list and the response I got is below.)
    The package build tool on Archlinux uses the CPP flag:
    CPPFLAGS="-D_FORTIFY_SOURCE=2"
    by default. Commenting this line out
    in /etc/makepkg.conf results in a successful build using the makepkg
    tool. (For the record, FORTIFY_SOURCE=1 fails as well).
    From what I can tell, during configure the conflict in sa_family_t
    definitions causes the test to fail when using the FORTIFY_SOURCE flag,
    making configure believe that the system has no definition of
    sa_family_t (or any other INET related definitions).
    Last edited by starfry (2014-06-15 08:59:58)

    I read that one, there's a couple of suggestions there and it's where I got the idea described above from. Other solutions that could be used include
    CFLAGS="$CFLAGS $CPPFLAGS"
    unset CPPFLAGS
    and
    CPPFLAGS="$CPPFLAGS -O2"
    Not sure which is best though...

  • Gnome terminal suddenly fails to start

    My laptop died because the battery failed, as a result, after rebooting, gnome-terminal fails to start with:
    (process:3967): Gtk-WARNING **: Locale not supported by C library.
            Using the fallback 'C' locale.
    (gnome-terminal:3967): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2:19: Theming engine 'adwaita' not found
    (gnome-terminal:3967): Gtk-WARNING **: Theme parsing error: gtk-main.css:168:30: Failed to import: Error opening file: No such file or directory
    Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8
    I couldn't find anything on status 8..:-/

    Make sure your locale is set correctly, and that you have uncommented your relevant UTF-8 language.
    See here: https://wiki.archlinux.org/index.php/Be … ide#Locale
    Then try rebooting.
    gnome-terminal 3.14.x requires a unicode locale to work, with some luck the other warnings should also disappear.

  • Windows Update Client failed to detect with error 0xc8000247 after using Lenovo System Update 5

    My Windows 7, SP1 was running fine, until I installed few updates on 10/15 using Lenovo System Update 5 then Windows Update stopped working, shows as RED:
    {CE3119AD-35EF-41CF-9C21-C7698FEB8393}    2013-10-14 21:53:00:256-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 4 updates.
    {EB17A01A-EB6E-49FF-9EA2-AA0DD063B4B1}    2013-10-15 04:15:54:069-0700    1    162    101    {C61A0D00-3E51-48AC-B0AF-1D3E02B9E5D3}    201    0    AutomaticUpdates    Success    Content Download    Download succeeded.
    {77DAE88F-2795-4258-8BBF-8D27E53662CF}    2013-10-15 12:10:38:196-0700    1    193    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Restart Required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates:  - Security Update for Windows 7 for x64-based Systems (KB2862330)
    {1398F777-3AEF-4D1D-BE4C-407EC4AEAD4C}    2013-10-15 12:15:25:676-0700    1    183    101    {C61A0D00-3E51-48AC-B0AF-1D3E02B9E5D3}    201    0    AutomaticUpdates    Success    Content Install    Installation Successful: Windows successfully installed the following update: Security Update for Windows 7 for x64-based Systems (KB2862330)
    {A220898A-E5FE-4FE7-8413-2B0C7B4013D0}    2013-10-15 12:15:25:766-0700    1    202    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Reboot completed.
    {A5400FF2-33ED-4A47-8409-13E5DFE16A6D}    2013-10-15 19:29:31:486-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    ChkWuDrv    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {43C533EE-775D-445E-A652-06648B72DE65}    2013-10-15 19:29:49:702-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    ChkWuDrv    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {D6AAAFFB-7F18-4A7E-B39D-1BA09CDC5E6D}    2013-10-15 19:30:05:744-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 3 updates.
    {4E73B1C1-5BA2-415D-AB34-92F7AB3DB418}    2013-10-15 19:30:08:753-0700    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    ChkWuDrv    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {51248882-41AC-4E59-B813-87AD326310AD}    2013-10-15 20:00:05:044-0700    1    183    101    {DBD3B4E9-0357-47DA-8317-D0CF2163BFE6}    501    0    wusa    Success    Content Install    Installation Successful: Windows successfully installed the following update: Hotfix for Windows (KB2661796)
    {FB2B8E5E-442C-4E76-B23D-6A41B4324C9D}    2013-10-16 00:11:39:832-0700    1    148    101    {00000000-0000-0000-0000-000000000000}    0    c8000247    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0xc8000247.
    Lenovo Thinkpad W500, Intel (R), Windows 7, SP1, latest updates as of Oct 15
    (1) Checked Setting,  set to automatic update whenever, even changed to never update, rebooted the OS and changed back to automatic update and rebooted the OS.
    (2) Stopped Windows Update Services, renamed SoftwareDistribution folder and started the window update services and rebooted.
    (3) Ran MS FIXIT
    (4) Ran System File checker Scan (sfc /scannow)
    (5) Ran CHKDSK /F
    (6) Installed "Intel Rapid Storage Technology" drivers from Lenovo site
    (7) Ran Update for Windows 7 for x64-based Systems (KB971033)
    None of the above possible recommended solutions were able to fix the issue yet and now I am getting a message your Window is Not Genuine!
    Any help or guidance is appreciated.
    Solved!
    Go to Solution.

    The Lenovo System Update installed the "Intel Matrix Storage Manager driver 8.9.2.1002" right before the Windows Upgrade got broken. So in the Device Manager under IDE ATA/ATAPI Controllers, I choose Intel ICH9M-E/M SATA AHCI Controller, on the Driver Tab, I choose the option "Roll Back Driver" and after rolling back the driver and restarting the OS, now Windows Update is working like a Champ!
    The End!

  • Quick Time (Audio Preferences) fails to launch with buffer overrun error

    It all started a few weeks ago, after installing itunes7.0 for windows, and itunes began to annoy me (indeed drive me mad) with an error message :
    "an unhandled win32 exception has occured in itunes.exe [3840]" at startup / closing immediately afterwards.
    After numerous uninstall/reinstall/clean the registry/system restore attempts I managed to solve the issue-- BUT only for a few days..It failed again and so I went through the itunes support forums even found an entry
    "iTunes 7 for Windows: iTunes fails to launch with an unknown error"
    which suggests that my issue could be solved by :
    "Open the QuickTime control panel and select the Audio tab.
    In the Devices section de-select the Safe mode (waveOut only) option and click Apply."
    But to my surprise, when i selected the Audio tab (and the Audio tab ONLY ) it presented me a "buffer overrun error" which indicated that the internal state of the program has been corrupt and it would be shutting down now..
    It's such a nuisance..!!
    Please, help, and your help will be deeply appreciated... !
    I have tried to revert to the older version and it didn't work..

    let's try swapping out your existing QuickTime one more time. we'll take a few additional explicit precautions this time.
    head into your Add/Remove programs. uninstall QuickTime.
    Next, we’ll manually remove any leftover program files and folders.
    1. On the Start menu, click My Computer (or double-click My Computer on the Desktop).
    2. In My Computer, open Local Disk.
    3. Open Program Files.
    4. Right-click on the QuickTime folder and click Delete from the shortcut menu.
    5. Navigate to C:\Windows\system32\.
    6. Remove the files QuickTime.qts and QuicktimeVR.qtx.
    7. Restart your computer.
    next, we'll get a fresh copy of QuickTime into your PC by doing a repair install of itunes.
    switch off antivirus and antispyware applications prior to the repair install.
    go into Add/Remove and select itunes. click "Change" and then click "Repair".
    if the repair install goes through okay, restart the PC and try launching itunes again. does it launch properly now?

Maybe you are looking for