Re: [arch-general] can't publish keys to network? What?
On 03/11/2013 11:03 PM, David Benfell wrote: Hi all, I wish I could ask this question intelligently. But I am clueless. I'm using the Cinnamon desktop manager. Whenever I log in, I get a message in the upper left hand corner that claims it can't publish keys to the network. I haven't seen this with other desktop managers: I've played with Openbox and GNOME. I have no idea what *it* is. I have no idea what *keys* it is talking about--I hope it isn't trying to publish private keys that should be kept secret. And I have no idea what functionality I'm losing as a result. Can someone shed some light? Thanks! Try running seahorse, go to Edit - Preferences. Make sure Automatically synchronize modified keys with key servers is not checked.
[arch-general] SOLVED Re: Cannot chroot '/bin/bash': No such file or directory
On 03/06/2013 08:24 PM, Ross Hamblin wrote: On 07/03/13 14:32, David C. Rankin wrote: Guys, Attempting to fix the test box that updating left unable to boot, I cannot chroot to fix the system. I've booted from the install medium and done the normal mount of the existing system under /mnt: mount /dev/sda6 /mnt mount /dev/sda5 /mnt/home mount /dev/sda8 /mnt/boot mount -o bind /dev /mnt/dev mount -t proc none /mnt/proc mount -t sysfs none /mnt/sys All files appear in their proper place under /mnt. However, attempting to create the chroot fails: cd /mnt chroot /mnt /bin/bash chroot: failed to run command '/bin/bash': No such file or directory /bin/bash is in the new location /usr/bin/bash (moved from /bin/bash by the update) with with a proper symlink in /mnt/bin/bash pointing to ../usr/bin/bash This if the first time I've ever had difficulty chrooting a system. I suspect that this is caused by the last update that pulled in systemd which left the system unbootable. Anyone know what could be causing the chroot failure? I've tried explicitly pointing the chroot to ./usr/bin/bash, etc... and tried it without any executable specified. Regardless, I get the same No such file or directory. Thanks in advance for any help or link you can provide. It's been a while now but ISTR this message when chroot from 32 bit host and 64 bit target, or maybe it was vice versa. HTH Ross. All, The problem with the update (11/20/12 - 2/5/13) appears to be that the update of filesystem (or something) removed the /lib - /usr/lib link from the / directory causing much of the update to fail. This apparently is a problem for boxes that haven't been updated in a few months. The last system update before the one on 2/5/13 was on 11/20/12. The pacman.log contains hints of where the problem began. Specifically, from the pacman.log file I have: [2013-02-05 23:45] synchronizing package lists [2013-02-05 23:45] starting full system upgrade [2013-02-05 23:53] removed eject (2.1.5-7) [2013-02-05 23:53] userdel: user dbus is currently used by process 452 [2013-02-05 23:53] groupdel: cannot remove the primary group of user 'dbus' [2013-02-05 23:53] removed dbus-core (1.6.4-1) snip (don't know if this is important -- repeated twice in log) [2013-02-05 23:53] /usr/bin/gconftool-2: error while loading shared libraries: libdbus-1.so.3: cannot open shared object file: No such file or directory [2013-02-05 23:53] /usr/bin/gconftool-2: error while loading shared libraries: libdbus-1.so.3: cannot open shared object file: No such file or directory snip [2013-02-05 23:53] upgraded linux-api-headers (3.5.1-1 - 3.7.4-1) [2013-02-05 23:53] upgraded tzdata (2012e-1 - 2012j-1) [2013-02-05 23:53] warning: /etc/gshadow installed as /etc/gshadow.pacnew [2013-02-05 23:53] warning: /etc/passwd installed as /etc/passwd.pacnew [2013-02-05 23:53] warning: /etc/group installed as /etc/group.pacnew [2013-02-05 23:53] warning: /etc/fstab installed as /etc/fstab.pacnew [2013-02-05 23:53] warning: /etc/shadow installed as /etc/shadow.pacnew [2013-02-05 23:53] upgraded filesystem (2012.8-1 - 2013.01-3) [2013-02-05 23:53] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew [2013-02-05 23:53] call to execv failed (No such file or directory) [2013-02-05 23:53] upgraded glibc (2.16.0-4 - 2.17-3) [2013-02-05 23:54] call to execv failed (No such file or directory) [2013-02-05 23:54] upgraded bash (4.2.037-1 - 4.2.042-3) [2013-02-05 23:54] call to execv failed (No such file or directory) I don't know if it was the filesystem package or not, but after the filesystem install, there are many of the call to execv failed (No such file or directory) errors noted. After working with the chroot error a bit I stumbled across the fact that link for /lib was missing. After manually creating the link again, chroot worked like a champ. I don't know how much of the system got borked as a result, but a fresh pacman -Syu complete normally. I have not finished examining the system yet, so I have not attempted to boot to the new kernel. I will have to go through and verify the grub legacy config before I reboot. I'll report back after I have had an opportunity to test the box. Thank you to those that responded. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Realtek wifi won't come up
On Fri, Mar 8, 2013 at 8:51 PM, M0r S m0rtiferri...@gmail.com wrote: Hey everyone, I'm trying to install Arch. The first time I tried installing everything worked fine, even the wifi, which usually doesn't work with linux. However, my laptop battery died in the middle of downloading packages because I was careless and hadn't plugged it in. Now, when I enter ip link set wlp2s0f0 up, it doesn't set the interface up. Strangely, when I reboot, the interface is renamed to wlan0 (that's what it was when the wifi worked), even though the wiki says it shouldn't. Running modprobe -r rtl8192ce modprobe rtl8192ce changes the interface name to wlp2s0f0. ip link gives me (besides the lo interface) 3: wlp2s0f0: BROADCAST, MULTICAST mtu 1500 qdisc nook state DOWN mode DEFAULT qlen 1000 link/ether 00:e0:4c:81:92:53 brd ff:ff:ff:ff:ff:ff Before, it gave me: 2: wlan0: NO-CARRIER, BROADCAST, MULTICAST, UP mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000 link/ether 24:ec:99:4c:60:1f brd ff:ff:ff:ff:ff:ff What else can I try? Lspci and dmesg show that the firmware has been loaded and that the card has been recognized. The first thing I would try would be to move /etc/udev/rules.d/network_persistent.rules to root's home directory, and reboot. That way you should wind up with the wlp2s0f0 name whether it's working or not, otherwise. =-Jameson
Re: [arch-general] Optirun sees no mouse, refuses to load
On Tue, Mar 12, 2013 at 1:32 AM, Armin K. kre...@email.com wrote: What's bbswitch anyways? As I said, I never used bumblebee, but that might be a source of your problems. bbswitch is a module written by Bumblebee developers, aiming to provide dynamic power management of (in other words, automatically switching on and off) the discrete NVIDIA card.
Re: [arch-general] Optirun sees no mouse, refuses to load
On Tue, Mar 12, 2013 at 6:43 AM, Szymon Szydełko sszyde...@gmail.com wrote: 2. Hmm, can I disable Intel gpu? And just leave Nvidia one? As far as I know you cannot do that on a Optimus system. Maybe your card is not turned on when optirun starts. My journal when starting `optirun glxspheres' : Mar 12 21:30:01 lightning.hexchain.org kernel: bbswitch: enabling discrete graphics Mar 12 21:30:02 lightning.hexchain.org kernel: pci :01:00.0: power state changed by ACPI to D0 Mar 12 21:30:02 lightning.hexchain.org kernel: vgaarb: device changed decodes: PCI::01:00.0,olddecodes=none,decodes=none:owns=none Mar 12 21:30:02 lightning.hexchain.org kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 313.26 Wed Feb 27 13:04:31 PST 2013 Mar 12 21:30:03 lightning.hexchain.org logger[15184]: button/lid: ACPI group/action undefined: processor / LNXCPU:00 Mar 12 21:30:03 lightning.hexchain.org acpid[313]: client connected from 15180[0:996] Mar 12 21:30:03 lightning.hexchain.org acpid[313]: 1 client rule loaded Mar 12 21:30:04 lightning.hexchain.org bumblebeed[323]: [13353.380547] [WARN][XORG] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 19.1, need 19.0). The driver will continue to load, but may behave strangely. Mar 12 21:30:04 lightning.hexchain.org bumblebeed[323]: [13353.380596] [WARN][XORG] (WW) NVIDIA(0): Unable to get display device for DPI computation. Mar 12 21:30:16 lightning.hexchain.org kernel: bbswitch: disabling discrete graphics Mar 12 21:30:16 lightning.hexchain.org kernel: pci :01:00.0: Refused to change power state, currently in D0 Mar 12 21:30:16 lightning.hexchain.org kernel: pci :01:00.0: power state changed by ACPI to D3cold Mar 12 21:30:18 lightning.hexchain.org acpid[313]: client 15180[0:996] has disconnected Notice those lines containing power state changed by ACPI.
