- Arch-general - lists.archlinux.org

[arch-general] Unbootable systems
by Guillermo Leira 04 Dec '11

04 Dec '11

I've just updated two computers that boot from external USB drives, and now I get a "Error: Unable to determine major/minor number of root device 'waiting 8 seconds for device /dev/disk/by-uuid/296...etc" I have tried to modify grub using by-id, just /dev/sdb1, but no way... Any suggestions? Thanks, Guillermo Leira

3 3

[arch-general] Wireless LED stays on during suspend
by Karol Babioch 04 Dec '11

04 Dec '11

Hi, I've recently installed Arch on my laptop and got a odd problem that I haven't encountered so far. Whenever I put my laptop into "Suspend to RAM" my wireless LED stays on, which is quite annoying. It probably doesn't use that much energy, but still I want to have nothing blinking, but the power LED. I investigated a little bit into it, and found out that the wireless LED stays on when at least one of the following devices is activated: Bluetooth, WWAN, Wireless LAN. This makes totally sense. As soon as blocking all three of these devices using rfkill, the LED turns off. I'm probably could now write a script that would get executed during "Suspend to RAM" using pm-utils. However before hacking around this, I would like to know what the expected way for this actually is. Doesn't a "Suspend to RAM" invoke rfkill at some point or at least shouldn't it try to disable such hardware? As I haven't experienced this issue with my former laptop, I'm not exactly sure whether this is a bug or a feature, so I'm glad about any input you give me on that. Best regards, Karol Babioch

3 4

[arch-general] Xscreensaver is Active on Resume from Manual Suspend
by Bastien Dejean 04 Dec '11

04 Dec '11

Hi, I would like to know why I see xscreensaver when I resume from suspend even if I manually suspend. Greetings, -- Bastien

4 7

[arch-general] USB Buffering Issue
by Paul Gideon Dann 04 Dec '11

04 Dec '11

Hello all, I've been having some trouble with USB drives in the last few months. When copying files onto a device, the copy appears to be instantaneous, but is clearly buffered by the kernel. If I unmount the drive, all appears well, but then removing the device results in corruption. In order to work around this, I have to run "sync" before unmounting the device. Any ideas what might be causing this, or how to fix it? It would be nice to get a *real* progress bar when copying large files, instead of a quick flash followed by a boring minute or more of staring at "sync". Paul

9 22

[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