[(somewhat) SOLVED] Dnsmasq simply won't work - crashed?

Hi there,
I'm having a problem with dnsmasq (v2.54 [<- how is this possible anyway? I just reinstalled it, pacman calls it "2.53-1", 'dnsmasq --version' calls it '2.54'…]). I'm just trying to use it as a DNS cache, nothing special.
It seems to be started (with the "log dns queries" option enabled) without problems, but without any queries too (even though there should have been some at this time):
Jun 7 20:39:04 dnsmasq[1717]: started, version 2.54 cachesize 150
Jun 7 20:39:04 dnsmasq[1717]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
Jun 7 20:39:04 dnsmasq[1717]: reading /etc/resolv.conf
Jun 7 20:39:04 dnsmasq[1717]: ignoring nameserver 127.0.0.1 - local interface
Jun 7 20:39:04 dnsmasq[1717]: read /etc/hosts - 1 addresses
Jun 7 20:39:15 dnsmasq[1717]: reading /etc/resolv.conf
Jun 7 20:39:15 dnsmasq[1717]: reading /etc/resolv.conf
Jun 7 20:39:15 dnsmasq[1717]: ignoring nameserver 127.0.0.1 - local interface
I learned "ignoring nameserver 127.0.0.1 - local interface" is not a bug but a feature (makes sense of course).
As far as I can tell in this short (but complete) log, there is nothing wrong here.
Still, it is not used:
dig google.de:
;; Query time: 2 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
dig google.de again:
;; Query time: 2 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
Here's my not exactly spectacular resolv.conf:
# Generated by dhcpcd from eth0
nameserver 127.0.0.1
nameserver 192.168.178.1
# /etc/resolv.conf.tail can replace this line
/etc/hosts (if needed at all):
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost
# End of file
Nothing fancy here either.
I've made two more observations:
1. A few days ago I switched from a "normal" network setup (using 'eth0="dhcp"' in rc.conf) to 'net-auto-wired' using netcfg.
Browsing using a domain name like 'google.de' has become very slow since then, i.e. connecting to a new website takes a few seconds; following a few links on that (now dns-resolved) website is fast. Browsing using IP addresses is fast as usual.
2. I cannot restart dnsmasq.
sudo /etc/rc.d/dnsmasq restart:
:: Stopping DNS/DHCP daemon [DONE]
:: Starting DNS/DHCP daemon [FAIL]
Nothing else (not in the logs either). What I can observe in my process list is that a second dnsmasq process is started even though the original process is NOT stopped. After a few seconds, the second, newly created dnsmasq process disappears.
"killall dnsmasq" simply does nothing. It's like pushing Return in my console. No message, no effect, no nothing.
These 2 observations lead me to my assumption, that dnsmasq crashes at some point; an application tries to give its DNS queries to it -> nothing happens -> the applications uses the second entry in my resolv.conf which is my router.
I have no idea whether this assumption is true nor why trying to SIGKILL it doesn't end dnsmasq's miseral life.
I'm stuck here. Can anybody help me?
Thanks a lot.
Last edited by EdgarButan (2010-06-08 16:59:52)

Alright, I seem to be able to kill dnsmasq with "kill -9 PID".
"killall" nor the process list of KDE worked which has never occured to me.
This topic is now a duplicate of the other one, let's call it "SOLVED".

Similar Messages

  • [SOLVED] UEFI shell won't work on Thinkpad Edge E520

    Hi there,
    I have installed the x86_64 UEFI Shell 2.0 on my Thinkpad Edge E520 which is already booting in UEFI mode using refind-efi for some time now. The same shell is running just fine on my desktop system.
    But - on the Thinkpad it doesn't run. The shell is installed as /boot/efi/shellx64.efi and when I start the laptop, refind appears and shows me the shell icon (amoung others). But when I choose the shell from refind I get a black screen with this writing:
    Starting shellx64.efi
    Using load options ' '
    ASSERT_EFI_ERROR (Status = Device Error)
    ASSERT c:\dev\edk2tip\Build\Shell\RELEASE_VS2005\X64\ShellPkg\Application\Shell\Shell\DEBUG\AutoGen.c (431): !EFI_ERROR (Status)_
    I don't know if the text is going on after the last underline. If yes I cannot see it because the text is running out of the screen.
    The funny thing is - exactly the same setup is working pretty nice on my Asrock ITX board but not on the Lenovo Thinkpad Edge E520.
    Any ideas? Just say, if you need further information.
    Last edited by swordfish (2013-02-10 11:44:27)

    Okay, found the - somewhat obvious - solution myself. The UEFI Bios on my Thinkpad is an "old" UEFI 2.0. So, Shell 2.0 won't work on this system (as I could have read in the wiki ).
    Now, I have installed Shell 1.0 and I can enter the shell from refind .
    Last edited by swordfish (2013-02-10 11:45:03)

  • [Solved] history -c won't work

    i was try to clear bash history with :
    history -c
    but it won't work , actually when i close terminal and reopen it history still exist :-??
    Last edited by Milad (2012-05-06 15:17:57)

    Gcool wrote:Doesn't "history -c" just clear the history saved in RAM (not what's actually saved in ~/.bash_history)? Someone please correct me if I'm wrong here (not 100% sure of this).
    The command will not work from a terminal emulator.  You still have bash running when you close the terminal emulator.  All you are clearing is that terminal instance's history.  To completely clear the history file with the command 'history -c', you need to run it from the login shell.
    You could use this to clear the history file:
    $ > ~/.bash_history

  • [SOLVED]grub-mkconfig won't work

    Hi!
    I'm running grub2, and today grub-mkconfig stopped working: this is the error:
    sudo grub-mkconfig -o /boot/grub/grub.cfg
    Creazione di grub.cfg...
    Trovata immagine linux: /boot/vmlinuz-netbook
    Trovata immagine linux: /boot/vmlinuz-3.4.9-1-i686-arch
    Trovata immagine initrd: /boot/initramfs-3.4.9-1-i686-arch.img
    Found memtest86+ image: /boot/memtest86+/memtest.bin
    No volume groups found
    Trovato Arch Linux su /dev/sda3
    /usr/sbin/grub-mkconfig: line 269: 8481 Errore di segmentazione ${grub_script_check} ${grub_cfg}.new
    Syntax errors are detected in generated GRUB config file.
    Ensure that there are no errors in /etc/default/grub
    and /etc/grub.d/* files or please file a bug report with
    /boot/grub/grub.cfg.new file attached.fatto
    This is my /etc/default/grub:
    GRUB_DEFAULT=saved
    GRUB_TIMEOUT=0
    GRUB_DISTRIBUTOR="Archlinux"
    GRUB_CMDLINE_LINUX_DEFAULT="quiet rootfstype=ext4 add_efi_memmap logo.nologo fastboot raid=noautodetect libahci.ignore_sss=1 loglevel=3 pcie_aspm=force i915.i915_enable_rc6=3 i915.lvds_downclock=1 ipv6.disable=1 resume=swap:/dev/sda3:0x5d0000 "
    GRUB_CMDLINE_LINUX=""
    # If you want to enable the save default function, uncomment the following
    # line, and set GRUB_DEFAULT to saved.
    GRUB_SAVEDEFAULT=false
    # Preload both GPT and MBR modules so that they are not missed
    GRUB_PRELOAD_MODULES="part_gpt part_msdos"
    # Uncomment to enable Hidden Menu, and optionally hide the timeout count
    GRUB_HIDDEN_TIMEOUT=0
    GRUB_HIDDEN_TIMEOUT_QUIET=true
    # Uncomment to use basic console
    GRUB_TERMINAL_INPUT=console
    # Uncomment to disable graphical terminal
    #GRUB_TERMINAL_OUTPUT=console
    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    GRUB_GFXMODE=auto
    # Uncomment to allow the kernel use the same resolution used by grub
    GRUB_GFXPAYLOAD_LINUX=keep
    # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
    # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
    #GRUB_DISABLE_LINUX_UUID=true
    # Uncomment to disable generation of recovery mode menu entries
    GRUB_DISABLE_RECOVERY=true
    # Uncomment and set to the desired menu colors. Used by normal and wallpaper
    # modes only. Entries specified as foreground/background.
    GRUB_COLOR_NORMAL="light-gray/black"
    GRUB_COLOR_HIGHLIGHT="green/black"
    # Uncomment one of them for the gfx desired, a image background or a gfxtheme
    GRUB_BACKGROUND="/usr/share/grub/background.png"
    #GRUB_THEME="/path/to/gfxtheme"
    # Uncomment to get a beep at GRUB start
    #GRUB_INIT_TUNE="480 440 1"
    I only set a swapfile to be used by tuxonice, then add the proper line there, in /etc/default/grub.
    May be i made some mistakes? I tried to remove the resume= parameter, but it won't work anyway...
    Thank you!
    Last edited by nierro (2012-08-23 22:32:46)

    The resume parameter is different from the normal resume= because i'm using a swap file
    Btw, this is the error message without resume parameter, in english:
    LC_ALL=C sudo grub-mkconfig -o /boot/grub/grub.cfg
    Generating grub.cfg ...
    Found linux image: /boot/vmlinuz-netbook
    Found linux image: /boot/vmlinuz-3.4.9-1-i686-arch
    Found initrd image: /boot/initramfs-3.4.9-1-i686-arch.img
    Found memtest86+ image: /boot/memtest86+/memtest.bin
    No volume groups found
    Found Arch Linux on /dev/sda3
    error: syntax error.
    error: Incorrect command.
    error: syntax error.
    /usr/sbin/grub-mkconfig: line 269: 5859 Segmentation fault ${grub_script_check} ${grub_cfg}.new
    Syntax errors are detected in generated GRUB config file.
    Ensure that there are no errors in /etc/default/grub
    and /etc/grub.d/* files or please file a bug report with
    /boot/grub/grub.cfg.new file attached.done
    Last edited by nierro (2012-08-23 22:01:33)

  • IMovie simply won't work.  or start.  or do anything.

    My iMovie will get to the loading thumbnails screen and won't get past there. how do I fix it? none of this create a new user name stuff.

    Try deleting iMovie's preference file. These are notorious for becoming corrupted.
    Close iMovie.
    Go: Home(YourUserName)/Library/Preferences/com.apple.imovie.plist.
    Drag this plist file to the trash.
    Reopen iMovie.
    See if it works now.
    If this does not resolve the issue, try doing a complete shut-down of your computer, and then see if iMovie works ok when you start the computer again.
    Post back if these suggestions do not help.

  • My firewire port simply won't work

    Both of my Fire wire ports are unable to read my IPOD, and my brother's IPOD Mini. At first I thought that that might be the cable problem, yet the cable does the battery charging okay???
    I use the same fire wire cable to connect to my brother's ibook, and it recognize the IPOD and IPOD Mini okay!!! So I guess the cable is okay!
    What is going on with my Fire wire??? Please help!
    By the way, my 1st USB port from top would randomly not recongnize my storage or IPOD devices as well!

    Similar problem here. We've had Apple (via our local authorized repair shop) replace the motherboard, which helped for a while.
    The tech has thrown up his hands. Calling Applecare is our next, reluctant step.
    The main symptom is that when using Final Cut to render large files to the external FW devices (there are, variously, 2-3, some connected to the 800 port, some to the 400 FW ports), it'll crank away for a while and then the drives unmount and won't come back onto the desktop even after a restart. I haven't tried leaving it off for 15 minutes, and haven't reset the PRAM yet.
    How do I do that, again? It's been a while.
    We're thinking now that it's either a software problem, and are considering a complete clean installation. Or, it's one of the FW drives that's got a problem, and is frying the ports somehow.
    I have my doubts about this because it seems to happen only on this machine. We've moved the FW drives to a G4 laptop, and it works fine.
    Is there any known issue -- hardware or software-- with the G5's FW circuitry?

  • [SOLVED] Gnome Mplayer Won't Work

    I have Gnome mplayer and gecko player installed on my maching with the mplayer-mt Aur package.  Gnome-mplayer won't play any files and just says "Stopped" on the bottom.  Can't figure it out, I've tried re-installing it and the regular mplayer package too without any luck.  Anybody know what the problem might be?
    Thx
    Last edited by leberyo (2010-09-24 19:35:43)

    anonymous_user wrote:
    Did you try deleting the config for gnome-mplayer?
    rm -r ~/.config/gnome-mplayer
    Also try running gnome-mplayer from a terminal and post its output when trying to play a file.
    Deleting the gnome-mplayer folder did the job.  It works now thanks.
    The only thing is, if I change any settings whatsoever in gnome-mplayer preferences, it stops again.  I guess I'll just stick to all the stock settings...

  • Import function in Premier 6 won't work; crashes 90 percent of the program. How to fix?

    I was working on a project in Premiere Pro 6. I had imported about 200 files and almost completed the project. I tried to import another file and the import function would not work. In addition, it disabled about 90 percent of the program. Menu selections had turned grey. I closed the project and program and restarted, opening a much smaller project. Worked OK until I tried to import. The import wouldn't work, and the program was disabled. This is not a case of actually selecting a file to import. The function crashes before you have a chance to actually select a file. On deadline, please help.

    These may help
    Reset Corrupted Preferences = Press/HOLD Ctrl+Alt+Shift while starting program
    -and setting http://forums.adobe.com/thread/1058426?tstart=0

  • [Solved] Pulse Audio won't work on newly installed system with Gnome

    About a year ago I got a new computer and more or less retired my old one with my first arch install. Recently, I decided I would set it up as a Linux system for my sister. I first updated the computer, which broke it royally (since it was last updated before the /bin symlinking happened) but I eventually got it fixed. However, after doing that, Pulse Audio wouldn't work, then I broke X and decided to do a full reinstall.
    Now, on this clean install, Pulse is again not working. I have set up Gnome and gdm to work, and everything works great except Pulse.  The wiki says that Pulse with Gnome 3 requires no extra setup, so I have not edited conf files at all. I have, however, installed "pulseaudio-alsa", which created this conf file:
    # Use PulseAudio by default
    pcm.!default {
    type pulse
    fallback "sysdefault"
    hint {
    show on
    description "Default ALSA Output (currently PulseAudio Sound Server)"
    ctl.!default {
    type pulse
    fallback "sysdefault"
    # vim:set ft=alsaconf:
    which seems fairly standard. Anyway, I tried removing it and had the same problems. When I have Pulse Audio running and try to play sound, I get the error:
    ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
    Playback open error: -16,Device or resource busy
    which is obviously trying for ALSA, or from mplayer:
    AO: [pulse] Init failed: Connection refused
    Running "pacmd list" nets me:
    Daemon not responding.
    and pavucontrol gives me:
    Fatal Error: Unable to connect to PulseAudio: OK
    when I try to start it.
    No pulseaudio commands seem to work (e.g. pulseaudio -k). They don't raise any errors, but also it doesn't have any effect on the server.
    The only asound conf file is "/etc/asound.conf", clearing ~/.config/pulse does not fix the issue.
    Journalctl does not seem to give anything interesting (Stale PID is the only message when starting Pulse), though admittedly I'm just vgrepping all of journalctl since I don't know how to narrow it down more, nor does the output from pulseaudio -vvvv. There are a lot of errors in pulseaudio -vvvv, but they all appear to be related to loading devices that don't exist, and so I assume not a problem, I can post it if necessary. Sometimes when I kill Pulse the process refuses to go away and I have to reboot in order to clear the process out, but I don't think that's related.
    If I kill Pulse or keep it from starting on boot, I can play sound, but only through ALSA, and while I didn't have the problem I expected (I can still play multiple things simultaneously) there's still the issue that the volume buttons in Gnome will no longer work and that the volume levels ALSA reports are basically nonsense to a human being.
    I basically just blurbed everything I thought of/found on the wiki or forums, and I'm not really sure where to go from here. It's a fairly old computer, so that could be related, and I'd be willing to dump Pulse if Gnome could integrate well with ALSA, but obviously fixing Pulse would be the preferred option.
    Any suggestions on where to look next? I've run out of ideas.
    Thanks.
    Last edited by HuFlungDu (2014-01-07 19:52:11)

    Wonder if you have a conflict between two audio cards ... for example, I have a friend with some PulseAudio problems caused by conflict between the HDMI audio from his graphics card and his onboard sound. Something would switch PulseAudio to the wrong card and it would just quit after getting itself into a twist. Unsolved, I'm afraid, but have a look at commands such as:
    aplay -l
    pactl list sinks
    pactl stat
    (Latter two will need PulseAudio coaxed into life first)
    and of course, the Arch wiki.
    If there is a conflict, blacklisting kernel modules might also be needed.

  • [SOLVED] pacman upgrade won't work because of unresolved dependency

    Hey all,
    I tried a pacman -Syyu today and it found some things and said:
    :: The following packages should be upgraded first :
        pacman
    :: Do you want to cancel the current operation
    :: and upgrade these packages now? [Y/n] y
    resolving dependencies...
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: gcc: requires gcc-libs=4.6.2-6
    I have gcc-libs=4.6.2-7 and I apparently need 4.6.2-6 but I can't change anything without pacman, and pacman won't change anything without updating itself first, and it can't because of this unmet dependency, so there's a stalemate.
    Any ideas what to do?
    Last edited by jdoggsc (2012-02-13 21:00:47)

    Awebb wrote:What's a repost?
    http://www.urbandictionary.com/define.php?term=repost

  • [SOLVED] X environment won't work

    Hey guys so I am having trouble trying to get my x environment to work. When I type startx it goes to a black screen and then show white and black zig-zag lines and the black ones are pixalated. I checked my log (Greg EE /var/log/Xorg.0.log) and this is what it says
    [332.566] Current operating system: Linux (none) 3.5.3-1-ARCH #1 SMP PREEMPT sun aug 26 09:14:51 CEST 2012 x86_64
             (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [332.593] (II) loading extension MIT-SCREEN-SAVER
    [332.603] (EE) failed to load module "nvidia" (module does not exist, 0)
    [332.603] (EE) failed to load module "nv" (module does not exist, 0)
    [332.604] (EE) failed to load module "vesa" ( module does not exist, 0)
    [332.604] (EE) failed to load module "fbdev" (module does not exist, 0)
    [334.875] (EE) AIGLX error: dlopen of /usr/lib/Xorg/modules/dri/nouveau_dri.so failed (/usr/lib/Xorg/modules/dri/nouveau_dri.so: cannot open shared object file: No such file or directory)
    [334.875] (EE) AIGLX: reverting to software rendering
    I have a gtx 560 graphics card and I installed the nouveau driver for it. It says failed to load NVIDIA so I was wondering if I should just use the NVIDIA driver instead of nouveau even though it is recommended that you use nouveau first until you get it setup. I don't think I messed anything up because all I did was install the needed packages. Any help will be awesome thank you.
    Last edited by bdawg (2012-09-25 00:18:51)

    bdawg wrote:I have a gtx 560 graphics card and I installed the nouveau driver for it. It says failed to load NVIDIA so I was wondering if I should just use the NVIDIA driver instead of nouveau even though it is recommended that you use nouveau first until you get it setup.
    It means that you still have the xorg.conf file that nvidia-xconfig created, for the nvidia driver.
    Delete or move any xorg.conf ("/etc/X11/xorg.conf" or "/etc/xorg.conf") and use the "/etc/X11/xorg.conf.d/10-monitor.conf" file with your equivalent of:
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "DELL"
    ModelName "U2311H"
    HorizSync 30.0 - 83.0
    VertRefresh 56.0 - 76.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nouveau"
    VendorName "NVIDIA Corporation"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    PS: While explicitly specifying the "Driver" part may be omitted with open-source drivers (or so I've heard), I find that it's easier to switch to nvidia, if I ever want to, instead of automatically generating that awful xorg.conf.

  • [solved]Quod Libet won't work

    Hi,
    I have reinstalled my archbox yesterday. Then I installed quod libet, but it don't start.
    The start in a terminal gives me this:
    [jean@arch ~]$ quodlibet
    Traceback (most recent call last):
    File "/usr/bin/quodlibet", line 299, in <module>
    util.gtk_init()
    File "/usr/share/quodlibet/util/__init__.py", line 44, in gtk_init
    import gtk
    ImportError: No module named gtk
    What can I do ? Is there any packages missing?
    Thanks for any help.
    Jean-Paul
    Last edited by jean-paul (2007-05-14 18:43:42)

    Yeah, thats realy funny.
    Thanks for help, it works well.
    Fortuna will great again.
    Jean-Paul

  • [SOLVED] lxdm autologin won't work since last upgrade

    Hi,
    Since last upgrade, lxdm won't autologin anymore.
    I had a lxdm.conf.pacnew file wich added only a commented line that I added into the conf file, wich does look like this :
    [base]
    ## uncomment and set autologin username to enable autologin
    #autologin=dgod
    autologin=Olaff
    ## uncomment and set timeout to enable timeout autologin,
    ## the value should >=5
    # timeout=10
    ## default session or desktop used when no systemwide config
    session=/usr/bin/startlxde
    #session=/usr/bin/openbox-session
    ## uncomment and set to set numlock on your keyboard
    # numlock=0
    ## set this if you don't want to put xauth file at ~/.Xauthority
    # xauth_path=/tmp
    # not ask password for users who have empty password
    # skip_password=1
    ## greeter used to welcome the user
    greeter=/usr/lib/lxdm/lxdm-greeter-gtk
    [server]
    ## arg used to start xserver, not fully function
    arg=/usr/bin/X -background vt1
    # uncomment this if you really want xserver listen to tcp
    # tcp_listen=1
    # uncoment this if you want reset the xserver after logou
    # reset=1
    [display]
    ## gtk theme used by greeter
    gtk_theme=Clearlooks
    ## background of the greeter
    # bg=/usr/share/backgrounds/default.png
    ## if show bottom pane
    bottom_pane=1
    ## if show language select control
    lang=1
    ## if show keyboard layout select control
    keyboard=0
    ## the theme of greeter
    theme=Industrial
    [input]
    [userlist]
    ## if disable the user list control at greeter
    disable=0
    ## whitelist user
    white=
    ## blacklist user
    black=
    Since there were no uncommented lines added, I assumed it would make no difference.
    Edit :
    Now, the system goes to the login screen instead of autologin.
    lxdm brings me to my session if I log in however.
    Last edited by OlaffTheGreat (2013-09-21 18:00:09)

    Here is my current /etc/lxdm/lxdm.conf file.  Hope something in here can help you out. 
    [base]
    ## uncomment and set autologin username to enable autologin
    autologin=andy
    ## uncomment and set timeout to enable timeout autologin,
    ## the value should >=5
    # timeout=10
    ## default session or desktop used when no systemwide config
    session=/usr/bin/startlxde
    ## uncomment and set to set numlock on your keyboard
    numlock=1
    ## set this if you don't want to put xauth file at ~/.Xauthority
    # xauth_path=/tmp
    # not ask password for users who have empty password
    # skip_password=1
    ## greeter used to welcome the user
    #greeter=/usr/lib/lxdm/lxdm-greeter-gtk
    [server]
    ## arg used to start xserver, not fully function
    #arg=/usr/bin/X -background vt1
    # uncomment this if you really want xserver listen to tcp
    # tcp_listen=1
    # uncoment this if you want reset the xserver after logou
    # reset=1
    [display]
    ## gtk theme used by greeter
    gtk_theme=Clearlooks
    ## background of the greeter
    # bg=/usr/share/backgrounds/default.png
    ## if show bottom pane
    bottom_pane=1
    ## if show language select control
    lang=
    ## if show keyboard layout select control
    keyboard=0
    ## the theme of greeter
    theme=Industrial
    [input]
    [userlist]
    ## if disable the user list control at greeter
    disable=1
    ## whitelist user
    white=
    ## blacklist user
    black=
    Not sure why OlaffTheGreat uses LXDM, but I use it because you get it for free as part of the LXDE group, and I'm too lazy to change it.  My security is the 30 to 40 character passphrase I need to unlock my encrypted drives.  Then having to type in an 8 character easily guessed user password is beyond annoying.
    I just checked my pacman cache files and it looks like the upgrade to 0.4-1-25 is when I first got the error (currently listed as 9 days ago which would be about right).  I upgraded, booted and got the login screen that I was not supposed to.  I had just merged the pacnew file so it was fresh in my head and made the changes I described.  Booted again and got the autologin and I didn't think another thing about it until I saw this post earlier today.  Upgraded again this weekend to 0.4-1-27 with no problems.

  • Qosmio x300-130 - ctrl-buttons won't work anymore

    Hello everyone
    Im having some problems with my ctrl-buttons. They simply won't work anymore, they used to but slowly they became unstable and now they won't work at all.
    So now I ask you if there is any way to solve this problem without sending the computer to repairs.
    My computer is a Qosmio x300-130 and I have had it for about two months.

    Hello
    It is really strange issue with those CTRL buttons functionality. Googling around I found several forums where people report about this. Unfortunately nobody has explanation why this happen.
    I use Vista and WXP SP3 on my Satellite Pro P300 and until now everything works properly.
    I can just imagine some Microsoft update is responsible for this. Try to roll back OS to earlier time using system restore tool.
    Please post results.
    Lets see if someone else has other advice.

  • BUG - Indexing Options keep pointing to D drive rather than the C drive - search charm won't work

    So I noticed that the search in my Windows 8.1 simply won't work to find files and settings. Then I went to Indexing Options in the Control Panel and I noticed that one of the locations Indexing was trying to point to is:
    D:\ProgramData\Microsoft\Windows\Start Menu\ (Unavailable)
    This is odd since this is not the location of the Start Menu (which is in the C drive, not the D drive).
    So I went on to remove this location and manually add the location of the Start Menu in the C drive (i.e. C:\ProgramData\Microsoft\Windows\Start Menu\).
    To my surprise, adding the location in the C drive is actually listed as the D drive -- not the C drive. In Fact any directory I try to add to the Index located in the C drive is in fact listed as being in the D drive!
    I'm at a loss here, and in fairness I reckon this is a bug.
    Have anyone here ever experienced this? Is there any workaround?
    EDIT: While the search does not work. It seems like the Windows Explorer search works without any issues.
    Also I reckon it is worth mentioning that I change the location of my search index to the D drive. This is because my C drive is a Solid State Drive, while my D drive is a traditional Hard Drive.
    Thanks in advance for the help.
    Regards,
    P.

    Hi,
    I made a test in my fresh building Windows 8.1. Create a new drive and a new folder in it. After that, add the folder into Windows Index Location. When I delete the folder, its shows up as the screenshot below:
    As you can see, it's same with yours, If I choose uncheck the Index folder and reopen Windows Index Location, it would be dispare from this panel.
    While for your problem, actually, move the index location is no difference to your Windows search, it just change search file location.
    To identify if this is a disk drive problem, you can opt to use Diskpart command to check your drive letter if it was correct.
    Open Command Prompt with admin, then type diskpart.
    Afer that, type list volume, check current disk label.
    Roger Lu
    TechNet Community Support

Maybe you are looking for