October 2011 - Arch-general - lists.archlinux.org

[arch-general] Possibility of including xorg input patch
by Kirill Churin 25 Jul '15

25 Jul '15

Can this patch https://bugs.freedesktop.org/attachment.cgi?id=33142 be applied to Arch's xorg? It solves famous problem https://bugs.freedesktop.org/show_bug.cgi?id=865 with broken keyboard input for users who use multiple keyboard layouts without any noticeable side-effects. It's known this patch has been applied in Ubuntu. -- Kirill Churin Jabber: reflexing(a)reflexing.ru, ICQ: 8163230, Skype on demand.

5 4

[arch-general] Keyboard Autorepeat
by Guillermo Leira 30 Nov '11

30 Nov '11

Hello! Since the upgrade to gnome 3.2, keyboard autorepeat is disabled every now and then. To reenable it, I just open System Configuration -> keyboard, and click on any slide bar or disable and enable autorepeat. After this, it works for some minutes. I have googled it, and I have seen that this is and old problem in some distributions and with different applications, but I have none of those applications. Anyone has seen this behavior? Thanks, Guillermo.

4 4

[arch-general] apcupsd or rtkit - Caused time to go haywire on shutdown/reboot??
by David C. Rankin 21 Nov '11

21 Nov '11

Guys, Here is one for the brain-trust to consider. Something totally screwed up the time on my computer during an apcupsd commanded shutdown and the subsequent reboot resulting in a 479 Minute time disparity. I don't think this was handled on the first reboot after the power outage because after reboot, I worked for 20-30 minutes before the OS imploded rebooted automatically. I suspect the time discrepancy somehow carried through the boot and went along until some kernel mechanism totally went bonkers and shut the system down. In 12 years of Linux use, this is the first time I've seen something like this happen. (note the time below) The log is: Oct 18 09:21:07 providence -- MARK -- Oct 18 09:24:18 providence apcupsd[949]: Power failure. Oct 18 09:24:24 providence apcupsd[949]: Running on UPS batteries. Oct 18 09:24:24 providence wall[11985]: wall: user root broadcasted 1 lines (56 chars) Oct 18 09:24:24 providence postfix/pickup[11962]: 3468078891: uid=0 from=<root> Oct 18 09:24:24 providence postfix/cleanup[11988]: 3468078891: message-id=<20111018142424.3468078891(a)providence.rlfpllc.com> Oct 18 09:24:24 providence postfix/qmgr[1338]: 3468078891: from=<root(a)rlfpllc.com>, size=1525, nrcpt=1 (queue active) Oct 18 09:24:24 providence postfix/smtp[11990]: 3468078891: to=<root(a)rlfpllc.com>, orig_to=<root>, relay=phoenix.rlfpllc.com[192.168.7.15]:25, delay=0.13, delays=0.07/0.01/0.02/0.04, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4699114AB47) Oct 18 09:24:24 providence postfix/qmgr[1338]: 3468078891: removed Oct 18 09:25:16 providence shutdown[13133]: shutting down for system halt Oct 18 09:25:17 providence init: Switching to runlevel: 0 Oct 18 14:25:18 providence rtkit-daemon[2768]: Exiting cleanly. Oct 18 14:25:18 providence rtkit-daemon[2768]: Demoting known real-time threads. Oct 18 14:25:18 providence rtkit-daemon[2768]: Successfully demoted thread 2766 of process 2766 (/usr/bin/pulseaudio (deleted)). Oct 18 14:25:18 providence rtkit-daemon[2768]: Demoted 1 threads. Oct 18 14:25:18 providence rtkit-daemon[2768]: Exiting watchdog thread. Oct 18 14:25:18 providence rtkit-daemon[2768]: Exiting canary thread. Oct 18 09:25:18 providence apcupsd[949]: apcupsd exiting, signal 15 Oct 18 09:25:19 providence apcupsd[949]: apcupsd shutdown succeeded Oct 18 09:25:19 providence nmbd[1339]: [2011/10/18 09:25:19.139254, 0] nmbd/nmbd.c:66(terminate) Oct 18 09:25:19 providence nmbd[1339]: Got SIGTERM: going down... Oct 18 09:25:19 providence postfix/postfix-script[13294]: stopping the Postfix mail system Oct 18 09:25:19 providence postfix/postfix-script[13297]: waiting for the Postfix mail system to terminate Oct 18 09:25:19 providence postfix/master[1330]: terminating on signal 15 Oct 18 09:25:22 providence ntpd[944]: ntpd exiting on signal 15 Oct 18 09:25:22 providence dhcpcd[13471]: sending signal 1 to pid 762 Oct 18 09:25:22 providence dhcpcd[762]: received SIGHUP, releasing Oct 18 09:25:22 providence dhcpcd[762]: eth0: releasing lease of 192.168.7.124 Oct 18 09:25:22 providence dhcpcd[13471]: waiting for pid 762 to exit Oct 18 09:25:23 providence dhcpcd[762]: eth0: removing interface Oct 18 09:25:23 providence kernel: [518721.438558] tg3 0000:02:00.0: PME# enabled Oct 18 09:25:23 providence kernel: [518721.438578] pcieport 0000:00:1c.0: wake-up capability enabled by ACPI Oct 18 09:25:25 providence ntfs-3g[524]: Unmounting /dev/sdb2 () Oct 18 09:25:25 providence syslog-ng[707]: Termination requested via signal, terminating; Oct 18 09:25:25 providence syslog-ng[707]: syslog-ng shutting down; version='3.2.4' Oct 18 17:28:06 providence kernel: [ 0.000000] Initializing cgroup subsys cpuset Oct 18 17:28:06 providence kernel: [ 0.000000] Initializing cgroup subsys cpu Oct 18 17:28:06 providence kernel: [ 0.000000] Linux version 3.0-ARCH (tobias@T-POWA-LX) (gcc version 4.6.1 20110819 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Oct 7 10:11:05 UTC 2011 Oct 18 17:28:06 providence kernel: [ 0.000000] BIOS-provided physical RAM map: Oct 18 17:28:06 providence kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) I understand the jump from 09:25:17 to 14:25:18, that just reflects the tzoffset for CDT. What I can't explain is the 09:25:25 to 17:28:06 jump. The power was only out for 5 minutes and the box booted as soon as power was restored. The log entry after reboot that caught my eye was: Oct 18 11:19:01 providence crond[978]: time disparity of -479 minutes detected I don't have a clue what could have caused this time shift unless it was some spurious voltage issue. If not, then something is definitely funny with the time handling in either apcupsd or rtkit. What say the experts, problem or just weird voltage induced time skew? -- David C. Rankin, J.D.,P.E.

3 7

[arch-general] [signoff] linux 3.1-3
by Thomas Bächler 02 Nov '11

02 Nov '11

Compared to the last release, a few bugfixes: Fix FS#19234, FS#26674, FS#25939, FS#26528 and a wrong drm error. Please sign off.

4 3

[arch-general] [signoff] linux-3.1-1
by Tobias Powalowski 31 Oct '11

31 Oct '11

Hi guys, please signoff 3.1 series for both arches. Upstream changes: http://kernelnewbies.org/LinuxChanges Archlinux Changes: - $(uname -r) reports now the full kernel version - all external modules should be installed in /lib/modules/extramodules-3.1-ARCH now - disabled the old IDE subsystem, marked as deprecated for quite some time All users of the old ide hook in mkinitcpio should make the transition to pata hook now! - disabled the old ACPI /proc files, marked as deprecated for quite some time, everything is available in /sys greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

15 26

Re: [arch-general] [arch-dev-public] [signoff] cryptsetup 1.4.0-1
by Geert Hendrickx 31 Oct '11

31 Oct '11

Appears to work fine, however I noticed a change in cryptsetup status output: /dev/mapper/cryptswap is active. type: PLAIN cipher: aes-cbc-essiv:sha256 - keysize: 256 bits + keysize: 0 bits device: /dev/xvda1 offset: 0 sectors size: 2097152 sectors (both on the existing crypted partition and after re-configuring it using the newer cryptsetup) Is this to be worried about? Geert -- geert.hendrickx.be :: geert(a)hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!

3 5

[arch-general] coping with damaging updates
by Mick 30 Oct '11

30 Oct '11

Following yet another update that has disabled user control of USB sticks, cameras, etc. and blocked user from shutting down from the desktop (in my case xfce4), I am at the end of my tether. Is there some way to be fore-warned of these updates coming online and avoid them or be ready with clear info on how to repair the damage they are set to create. mick

19 41

[arch-general] /usr is not mounted. This is not supported.
by Dwight Schauer 30 Oct '11

30 Oct '11

I've been using Arch Linux for about 4 years now. I have it on a few important systems at work and it has been doing very well. This morning I saw "/usr is not mounted. This is not supported." in my boot up after a recent rc.sysinit update. What is this, bait and switch? I've been running Linux and BSD systems since 1996 and typically always have /usr in a separate partition (as well as /var, /home/ and /tmp, but lately been using a ram /tmp). Why does /usr even exist if it can't be on a separate partition? Why not just combine /usr/lib and /lib? And /usr/bin and /bin? And /usr/sbin and /sbin? Why have the distinction at all if it can't be on separate partition? I understand that historically that /usr often use to be on different drive, and that is not really an issue nowadays. Only this year have I started not putting /usr into separate partitions because I've been making thumbdrive installs, and did not really see any benefit to making so many partitions (automatically created anyways, with a custom install script). Does this "/usr is not mounted. This is not supported." mean I'm going to have to eventually fix (dump/fix/restore) all my systems that are now currently running fine (and that I and others are depending on at my work) because Arch Linux no longer supports /usr on a different partition (due to rc.sysinit failing, not just printing an error message)? I run Arch Linux on more than 10 systems, and about 6 or 7 of those are at work (where Arch has been working out very well). I'm not looking forward to redoing all these systems that are running fine if this is where Arch is headed and rc.sysinit is not fixed to take out this new requirement. I know this a bit of a rant, but this "/usr is not mounted. This is not supported." error message is definitely not getting this day off to a good start... Definitely not wanting to give up Arch for such a simple issue.... Dwight

8 34

[arch-general] zsh and ssh just fills my RAM, not doing anything else
by Rasmus Steinke 29 Oct '11

29 Oct '11

I have a very nasty problem, which started around the time, arch changed its locale configuration. i cannot use ssh in a zsh session. All it does is filling my RAM until the computer stalls. If i run the very same ssh command in a bash session, all is working fine. I tried with blank config files too - here it gets even more odd. With a blank config file it has the same problem in gnome-terminal, but suddenly works in urxvt. This is very annoying, since i dont like bash too much, but i am forced to use it now. Also i have absolute NO plan where to start searching for this issue. Regards, Rasi

3 4

[arch-general] Error when upgrading texlive-bin-2011.1-3-i686
by Lorenzo Bandieri 29 Oct '11

29 Oct '11

Hi archers! On 2011-09-15 TexLive was upgraded (see [1]). Initially I had no problems, but in the following days there had been two subsequent upgrades of texlive-bin, the last of wich yesterday (or today, last time I upgraded was two days ago), that caused errors. In both cases, the error was the same: (5/5) upgrading texlive-bin [##################################################] 100% >>> texlive: updating the filename database... mktexlsr: Updating /etc/texmf/ls-R... mktexlsr: Updating /usr/share/texmf/ls-R... mktexlsr: Updating /usr/share/texmf-dist/ls-R... mktexlsr: Updating /var/lib/texmf/ls-R... mktexlsr: Done. recreating all formats...Error: `eptex -ini -jobname=eptex -progname=eptex *eptex.ini' failed ############################################### fmtutil: Error! Not all formats have been built successfully. Visit the log files in directory /var/lib/texmf/web2c for details. ################################################## This is a summary of all `failed' messages: `eptex -ini -jobname=eptex -progname=eptex *eptex.ini' failed done. (logs are under /var/lib/texmf/web2c/<engine>/<formatname>.log) Since errors were somewhat expected in non-fresh install [2], the first time I solved reinstalling everything. However, on the last texlive-bin upgrade (texlive-bin-2011.1-3-i686) the error showed up again, as I stated. To me it's odd that I have to reinstall all texlive-most and texlive-lang on every update, but on the bug report there is no workaround provided. I googled but I didn't find anything, and searching on the forum returned no hits. So, I wonder if anyone had the same problem and if there is a solution (apart from reinstalling texlive-most and texlive-lang...). Thank you! Regards, Lorenzo [1] http://www.archlinux.org/news/texlive-2011-update/ [2] https://bugs.archlinux.org/task/25250

2 1