- Arch-general - lists.archlinux.org

[arch-general] udev realtime group
by Ignacio Galmarino 03 Dec '11

03 Dec '11

I start using testing again a couple of days ago and now on every boot i get this error msg: localhost udevd[313]: specified group 'realtime' unknown realtime group does not exist in my computer Any idea ? Thanks Ignacio

2 2

[arch-general] ACL on /dev nodes (systemd, lightdm)
by Damjan 02 Dec '11

02 Dec '11

Hi all, I know systemd and lightdm are not exactly kosher on ArchLinux, but any help would be welcome. So, I just noticed that OpenGL is using llvmpipe on my laptop, and then I found out that the /dev/dri/card0 node doesn't have the proper ACL set to allow access to my user. Also my user is not in the video group - since I've learned that's not necesseary in "modern" Linux configurations. Considering that I'm running systemd and using lightdm as a login manager - my question is, what subsystem is responsible for settings the ACL: - ConsoleKit - PolicyKit - systemd - lightdm ? Is the proper setup to have pam_loginuid.so, pam_ck_connector.so and pam_systemd.so in the PAM configuration for lightdm? the output of ck-list-session is: Session2: unix-user = '1000' realname = '' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2011-12-02T18:23:04.193636Z' login-session-id = '' -- дамјан

2 2

[arch-general] Updated scripts for removing duplicates from /var/cache/pacman/pkg
by David C. Rankin 02 Dec '11

02 Dec '11

All, I don't know if anybody uses these scripts, but I've updated them to handle the stray packages with the nonconforming filenames in the form of: <name>-num-num-arch.pkg.tar.xz I've additionally added a check to optimize the scripts a bit by checking for at least the presence of one actual duplicate before executing the removal code. Prior to the overhead of the nonconforming file check, it wasn't really needed, but after the nonconforming filename code was added, you get a meaningful time benefit from the check. The scripts are here: http://www.3111skyline.com/dl/arch/scripts/fduparch.sh http://www.3111skyline.com/dl/arch/scripts/fduppkg For those not familiar with the scripts, they simply parse the files in /var/cache/pacman/pkg and move any duplicates (old versions) to a separate directory (/home/backup/pkg-1 by default). This does 2 things: (1) is cleans the pkg directory so that only current packages are present and (2) by moving duplicates to /home it frees space on the / partition. The files on the /home dir can be kept for a period of time or simply deleted. The pair of scripts function as one script. The "wrapper" script 'fduparch.sh' simply calls 'fduppkg' setting the search dir and duplicate dir according to the directory array. fduppkg generically just removes duplicates (saving the most recent file) from dir_1 -> dir_2. They provide output advising of the duplicates found as well as logging detailed information about what was done to /home/backup/log/pkgdups.log.bz2. By default, fduppkg is called 3 times: /var/cache/pacman/pkg -> /home/backup/pkg-1 /home/backup/pkg-1 -> /home/backup/pkg-2 /home/backup/pkg-2 -> /home/backup/pkg-del If you simply want to run the script once, just edit fduparch.sh and just remove directories from: DIRLIST=( /var/cache/pacman/pkg /home/backup/pkg-1 /home/backup/pkg-2 /home/backup/pkg-del ) Making it: DIRLIST=( /var/cache/pacman/pkg /home/backup/pkg-1 ) The scripts are reasonably commented, so they are easy to follow. The only requirement is that both be placed in /usr/local/bin (or just modify the script location in fduparch.sh) I just soft link then to /usr/local/bin. Obviously since they are moving files from the pkg directory, they must be run as root or the user must have sudo privileges. Output is verbose by default. The output is shown below. The pkg [index] is simply the file index number of that file in the list of 2743 below: 17:27 archangel:~> fduparch.sh calling: 'fduppkg /var/cache/pacman/pkg -d /home/backup/pkg-1 -l pkgdups.log' Total packages to screen: 2743 Removing duplicates from: /var/cache/pacman/pkg Duplicates directory: /home/backup/pkg-1 Log file location: pkgdups.log Verbose mode set: [use -q to stop pkg output | -s to stop all output] <snip> pkg [ 116] boost dup => boost-1.47.0-2-i686.pkg.tar.xz pkg [ 118] boost-libs dup => boost-libs-1.47.0-2-i686.pkg.tar.xz <snip> 754 duplicates moved to /home/backup/pkg-1 calling: 'fduppkg /home/backup/pkg-1 -d /home/backup/pkg-2 -l pkgdups.log' Total packages to screen: 2527 Removing duplicates from: /home/backup/pkg-1 Duplicates directory: /home/backup/pkg-2 Log file location: pkgdups.log Verbose mode set: [use -q to stop pkg output | -s to stop all output] <snip> pkg [ 55] b43-fwcutter dup => b43-fwcutter-013-1-i686.pkg.tar.xz pkg [ 75] boost dup => boost-1.47.0-1-i686.pkg.tar.xz pkg [ 77] boost-libs dup => boost-libs-1.47.0-1-i686.pkg.tar.xz <snip> 601 duplicates moved to /home/backup/pkg-del Package Disk Usage Summary 4.7G /var/cache/pacman/pkg 3.4G /home/backup/pkg-1 1.1G /home/backup/pkg-2 1.3G /home/backup/pkg-del That's all there is to it. The log entries look like this: Nov 02 18:16:52 killerz fduppkg Removing duplicates from: /var/cache/pacman/pkg Number of packages: 3545 `/var/cache/pacman/pkg/accountsservice-0.6.14-1-i686.pkg.tar.xz' -> `/home/backup/pkg-1/accountsservice-0.6.14-1-i686.pkg.tar.xz' removed `/var/cache/pacman/pkg/accountsservice-0.6.14-1-i686.pkg.tar.xz' `/var/cache/pacman/pkg/arch-wiki-docs-20100914-1-any.pkg.tar.xz' -> `/home/backup/pkg-1/arch-wiki-docs-20100914-1-any.pkg.tar.xz' removed `/var/cache/pacman/pkg/arch-wiki-docs-20100914-1-any.pkg.tar.xz' `/var/cache/pacman/pkg/ati-dri-7.11-2-i686.pkg.tar.xz' -> `/home/backup/pkg-1/ati-dri-7.11-2-i686.pkg.tar.xz' removed `/var/cache/pacman/pkg/ati-dri-7.11-2-i686.pkg.tar.xz' <snip> So if you ever have any questions about what was done, it is there for your review in the log file. They take less than 60 seconds or so to run. Very handy for cleaning the pkg dir and also for keeping a 'last known' set of good packages around. I agree, no need for a 2nd or 3rd set, but that's just kind of hung around since they were first developed. Give them a try. The scripts are here: http://www.3111skyline.com/dl/arch/scripts/fduparch.sh http://www.3111skyline.com/dl/arch/scripts/fduppkg Then make sure they are executable (chmod 0755 will do). The just link them from wherever you save them to /usr/local/bin as follows: ln -s /path/to/fduparch.sh /usr/local/bin/fduparch ln -s /path/to/fduppkg /usr/local/bin/fduppkg Then just execute the fduparch link and watch it run. With the addition of the check for nonconfirming filenames, you will pick up another 300-600 duplicates out of your package directory. Anyway. Enjoy! Send any bugs to me. Thanks! -- David C. Rankin, J.D.,P.E.

1 1

[arch-general] Fixing udev rules + udevd timeout error
by David C. Rankin 02 Dec '11

02 Dec '11

Guys, I have read https://bugs.archlinux.org/task/26583 but I still have a question. I have the file (/lib/udev/rules.d/52-nut-usbups.rules) for an older version of nut that contains: <snip> BUS!="usb", GOTO="nut-usbups_rules_end" <snip> LABEL="nut-usbups_rules_end" What do I have to do to 'fix' the rule to get rid of the error regarding 'BUS' no longer being recognized? Also, nut (upsd) will start, but after a period of time it dies with the following udevd error in the daemons.log file: Nov 29 13:18:53 archangel udevd[451]: timeout: killing '/sbin/modprobe -bv usb:v045Ep0040d0300dc00dsc00dp00ic03isc01ip02' [696] The error repeats continuously and I cannot kill the nut processes and make it stop. It is like something gets stuck when the error gets thrown. Any thoughts? Thanks. -- David C. Rankin, J.D.,P.E.

2 3

[arch-general] Please stop abusing of the out-of-date option
by Andrea Scarpino 01 Dec '11

01 Dec '11

Please users stop abusing of the out-of-date option. What you SHOULDN'T do: - report as out-of-date a package when a beta or a RC is out - report as out-of-date a package which conflicts - report as out-of-date a package which doesn't build - report as out-of-date a package which is broken - report as out-of-date a package when the mirror you use is out-of-date - and my favorite, report as out-of-date a package which WORKS like this one at the bottom of this mail What you SHOULD do: - report as out-of-date a package when a *stable* release of that package is out Thanks. ---------- Forwarded message ---------- From: Arch Website Notification <nobody(a)archlinux.org> Date: 1 December 2011 13:39 Subject: [arch-notifications] Orphan Extra package [netkit-bsd-finger] marked out-of-date To: arch-notifications(a)archlinux.org xxx wants to notify you that the following packages may be out-of-date: * netkit-bsd-finger 0.17-6 [extra] (i686): https://www.archlinux.org/packages/extra/i686/netkit-bsd-finger/ * netkit-bsd-finger 0.17-6 [extra] (x86_64): https://www.archlinux.org/packages/extra/x86_64/netkit-bsd-finger/ The user provided the following additional text: Now it works. --2011-12-01 13:38:27-- http://mir.archlinux.fr/extra/os/x86_64/netkit-bsd-finger-0.17-6-x86_64.pkg… Resolving mir.archlinux.fr... 91.121.141.57 Connecting to mir.archlinux.fr|91.121.141.57|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 18132 (18K) [application/octet-stream] Saving to: `/var/cache/pacman/pkg/netkit-bsd-finger-0.17-6-x86_64.pkg.tar.xz.part' 100%[===========================================================================================>] 18,132 --.-K/s in 0.06s 2011-12-01 13:38:27 (306 KB/s) - `/var/cache/pacman/pkg/netkit-bsd-finger-0.17-6-x86_64.pkg.tar.xz.part' saved [18132/18132] -- Andrea

10 9

[arch-general] pacman/libalpm/libfetch do not honor TMPDIR
by clemens fischer 30 Nov '11

30 Nov '11

Hi, would it be possible to let pacman, libalpm and libfetch honor the environment variable TMPDIR? I mean, this is stupid. Many people keep /tmp in RAM, on a tmpfs, and make it big enough, but not too big, as it takes away RAM when getting loaded. #define TMP_LOC "TMPDIR" #include <stdlib.h> /* getenv(3) */ #include <string.h> /* strncat(3) */ td = getenv(TMP_LOC); /* cleanup for safety: td = cleanup(td); */ tmpdir = strncat(td, "/", 1); What can be so difficult about this? I got this pesty "warning: warning given when extracting .INSTALL (Write failed)" today, and when looking at pacman, libalpm and libfetch with strings(1), none of them seem to check TMPDIR! clemens

15 30

[arch-general] libgdbm.so.4 breakage?
by Simon Perry 30 Nov '11

30 Nov '11

Hi all, I was about to lodge a bug regarding this, but now I'm not sure if it's something my system is doing or... Anyway, tonight I needed to RDP to a work box, and both Remmina and Vinagre both failed to run: % remmina remmina: error while loading shared libraries: libgdbm.so.4: cannot open shared object file: No such file or directory % vinagre vinagre: error while loading shared libraries: libgdbm.so.4: cannot open shared object file: No such file or directory So I wrote some scripts, and discovered the following packages are expecting this library (see http://pastebin.com/DyWw74iK for the complete output of my script): apr-util 1.3.12-3 avahi 0.6.30-6 python2 2.7.2-4 python 3.2.2-2 ruby 1.9.3_p0-2 subversion 1.6.17-7 vinagre 3.2.2-1 zsh 4.3.12-3 After seeing this, I tried svn: % svn --help svn: error while loading shared libraries: libgdbm.so.4: cannot open shared object file: No such file or directory Zsh works still, luckily... :) I have an entry in pacman.log that says I upgraded gdbm on: [2011-01-13 19:57] upgraded gdbm (1.8.3-7 -> 1.8.3-8) [2011-11-07 01:00] upgraded gdbm (1.8.3-8 -> 1.8.3-9) The reason I haven't lodged an FS is because I downgraded to gdbm 1.8.3-8 (from Janurary!) and it doesn't have libgdbm.so.4 either, so I'm not sure if there's something weird on my system or what. I'm confused and astonished that I haven't noticed it until tonight. "pacman -Ql gdbm" clearly states no reference to libgdbm.so.4, just libgdbm.so.3 ... Halp... Multipass... -- Simon Perry (aka Pezz)

8 18

[arch-general] wireless regulatory crda
by scrat 30 Nov '11

30 Nov '11

I have installed arch to a laptop CLI only ( just base and base-devlel with wireless) and updated to the latest packages. I have setup the wireless manually. I am in the US and have a wireless access point by tenda (china) and the access point is open no security. My desktop arch install does not have this problem it works without error. When I bring up the wlan0 interface the kernel log shows CRDA calling for country US followed by CRDA calling for county CN and changing the regulatory domain to CN. Later it calls for the US regulatory domain set to US and wlan0 is deauthenticated. iw dev wlan0 connect ESSID causes wlan0 to be authenticated and wireless sevice returns. How does one set this crda thing up so it does not slay the wireless connection? Google doesn't have any info on how to fix this This is from the log Nov 29 19:37:50 lapdog kernel: [ 8.027994] cfg80211: Calling CRDA for country: CN Nov 29 19:37:50 lapdog kernel: [ 8.032220] cfg80211: Regulatory domain changed to country: CN Nov 29 19:37:50 lapdog kernel: [ 8.032226] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Nov 29 19:37:50 lapdog kernel: [ 8.032231] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) Nov 29 19:37:50 lapdog kernel: [ 8.032235] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm) Nov 29 19:38:11 lapdog kernel: [ 31.076726] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) Nov 29 19:38:11 lapdog kernel: [ 31.164873] cfg80211: Calling CRDA for country: US Nov 29 19:38:11 lapdog kernel: [ 31.170527] cfg80211: Regulatory domain changed to country: US Nov 29 19:38:11 lapdog kernel: [ 31.170533] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Nov 29 19:38:11 lapdog kernel: [ 31.170538] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) Nov 29 19:38:11 lapdog kernel: [ 31.170542] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) Nov 29 19:38:11 lapdog kernel: [ 31.170546] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:38:11 lapdog kernel: [ 31.170550] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:38:11 lapdog kernel: [ 31.170554] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:38:11 lapdog kernel: [ 31.170558] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) Nov 29 19:38:12 lapdog kernel: [ 32.336761] wlan0: authenticate with c8:3a:35:40:47:88 (try 1) Nov 29 19:38:12 lapdog kernel: [ 32.338348] wlan0: authenticated Nov 29 19:38:12 lapdog kernel: [ 32.338379] wlan0: associate with c8:3a:35:40:47:88 (try 1) Nov 29 19:38:12 lapdog kernel: [ 32.340814] wlan0: RX AssocResp from c8:3a:35:40:47:88 (capab=0x1 status=0 aid=3) Nov 29 19:38:12 lapdog kernel: [ 32.340818] wlan0: associated Nov 29 19:38:12 lapdog kernel: [ 32.341622] cfg80211: Calling CRDA for country: CN Nov 29 19:38:12 lapdog kernel: [ 32.345997] cfg80211: Regulatory domain changed to country: CN Nov 29 19:38:12 lapdog kernel: [ 32.346003] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Nov 29 19:38:12 lapdog kernel: [ 32.346006] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) Nov 29 19:38:12 lapdog kernel: [ 32.346010] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.639351] wlan0: deauthenticated from c8:3a:35:40:47:88 (Reason: 3) Nov 29 19:43:12 lapdog kernel: [ 331.666833] cfg80211: Calling CRDA to update world regulatory domain Nov 29 19:43:12 lapdog kernel: [ 331.671216] cfg80211: World regulatory domain updated: Nov 29 19:43:12 lapdog kernel: [ 331.671222] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Nov 29 19:43:12 lapdog kernel: [ 331.671227] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.671231] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.671235] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.671239] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.671243] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.671451] cfg80211: Calling CRDA for country: US Nov 29 19:43:12 lapdog kernel: [ 331.677024] cfg80211: Regulatory domain changed to country: US Nov 29 19:43:12 lapdog kernel: [ 331.677029] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Nov 29 19:43:12 lapdog kernel: [ 331.677034] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.677038] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.677042] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.677045] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Nov 29 19:43:12 lapdog kernel: [ 331.677049] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Anyone?

3 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] No FFMPEG/LibAV for Audacity?
by Jonathan E. Brickman 29 Nov '11

29 Nov '11

I tried every combination of repo and AUR versions of Audacity, FFMPEG, and LibAV libraries, and I was not able to find a way to give Audacity the file named libavformat.so.52 which it wants to much. So far as I have been able to tell, all of the versions of FFMPEG and LibAV either don't compile or produce libavformat.so.53, which the available versions of Audacity won't touch. Anyone have a solution? I would try Ubuntu deb's, but I am concerned with introducing more conflicts instead of eliminating just one! -- Jonathan E. Brickman /Ponderworthy Music/ <http://ponderworthy.com> 805 SW Jewell Ave Topeka KS 66606-1610 jeb(a)ponderworthy.com <mailto:jeb@ponderworthy.com>

4 7