December 2014 - Arch-general - lists.archlinux.org

[arch-general] Booting ArchLinux with `initscripts` is now broken
by Ciprian Dorin Craciun 21 Dec '14

21 Dec '14

Hello all! I'm in a little bit of a pickle, and I would like to ask for some help with my particular setup. I haven't switched to `systemd` and I'm still booting my system with the old `initscripts` `/etc/rc.sysinit` and friends (except this all the packages are up-to-date). Before updating `systemd` from 216 to 217, it still worked. However after upgrading, two things happened: (A) the kernel modules firmware is not loaded any more; (I know that now the kernel automatically loads the firmware, but I'm still on Linux 3.6.11;) (B) `systemd-udevd` seems to get stuck while "doing it's magic" on something like `/sys/.../cpu0`; I've now downgraded to `systemd` 216, and marked it as ignored in `/etc/pacman.conf`, due to the firmware loading. (Issue (B) was solved by just replacing `udevadm settle` with a `sleep 6s`.) However I would be interested if someone has an idea on how to: * fix problem (A) regarding the firmware loading; (I'll have to dig the documentation, but perhaps there is a tool and some `/proc/sys/...` knob I can use...) * find a way in which I can still have my non-systemd setup; (I know about `mdev`, and other `udev` replacements, but I would prefer an `udev`-based solution just to be sure that X, or LVM, etc. don't break;) Thanks in advance, Ciprian. P.S.: Just to be clear, I don't want to start a systemd flame war. My reason for not using it is simple: I already use `runit` and custom scripts for all my services (except `udevd` and `agetty`), and my setup relies on somewhat modified `/etc/rc.d/functions` script for encrypted devices.

3 3

[arch-general] p11-kit
by Ralf Mardorf 20 Dec '14

20 Dec '14

Am I the only one who noticed something "unusal" when running $ grep p11-kit $HOME/.xsession-errors ? I cared about https://www.archlinux.org/news/ca-certificates-update/ .

2 3

[arch-general] systemd upgrade - run mkinitcpio automaitcally
by Troy Engel 19 Dec '14

19 Dec '14

Hiya all, Upgrading this evening we get systemd 218 - I rebooted and happened to notice that the initramfs said "loading systemd 217" and off it went... so I ran mkinitcpio -p linux to rebuild a new one and rebooted into it. I'm OCD like that. Should upgrades to systemd have some sort of post install hook to run mkinitcpio for the new version? Does it matter? Just curious, -te

2 1

[arch-general] Screen recording in gnome is not working
by Marcos Sánchez 19 Dec '14

19 Dec '14

Reposting here in case someone doesn't read the forums. From: https://bbs.archlinux.org/viewtopic.php?id=191231 I'm having trouble running the screen recording feature in gnome. When I press ctrl + alt + shift + r the desktop is not recorded and no file is created. I have installed the following gstreamer packages https://gist.github.com/anonymous/62aa75202f798821ab38. I'm running GNOME Shell 3.14.2 in a fully updated archlinux. Related topic (the solution didn't work for me): https://bbs.archlinux.org/viewtopic.php?id=120134 Any ideas on how to fix the issue? -- # Marcos

1 0

[arch-general] Missing module ag mkinitcpio
by Heiko Becker 19 Dec '14

19 Dec '14

Hey everyone, as pointed out somewhere else on the list, it is necessary to run mkinitcpio after updating to systemd 218. Doin so today gave me the following warning: WARNING: Possibly missing firmware for module: aic94xx Can someone give me a hint where I have to search to fix this? Best, Heiko

3 3

[arch-general] gnupg 2.1 not stable
by Ido Rosen 18 Dec '14

18 Dec '14

>From gnupg.org: "2.0.26 is the stable version suggested for most users, 2.1.1 is the brand-new modern version with support for ECC and many other new features, and 1.4.18 is the classic portable version." The 2.1 series of gnupg is not stable, it still has many major bugs, not the least of which is backwards compatibility with various key sizes previously supported (introduced by the new gpg to gpg-agent IPC layer restrictions). On the gnupg-devel mailing list I've seen a few potentially serious security issues with it. Given that it's not marked as stable upstream, and that it's such a critical core component of Arch's infrastructure, I find it questionable for Arch to have upgraded so soon. In the future, can we avoid upgrading gnupg proper to non-stable releases? Instead, how about creating a gpg21 or gpg-modern package would be appropriate for those wishing to try the unstable version and then updating the gnupg package once that branch gets marked stable?

10 23

[arch-general] community svntogit stuck
by Armin K. 17 Dec '14

17 Dec '14

FYI, in case someone who maintains it looks at the mailing list, I must inform you that community svntogit web interface is stuck at the same commit for more than 24 hours now. https://projects.archlinux.org/svntogit/community.git/log/ -- Note: My last name is not Krejzi.

3 3

[arch-general] LXDE on boot
by John Dey 17 Dec '14

17 Dec '14

Hi, I have installed openbox and lxde on a Raspberry Pi and configured to automatically start on boot. When I login (GUI), I get a blank screen with a cursor. Not the usual LXDE screen with panel at bottom. When I right click on mouse, I am given options--some of the applications will start such as xterm but others libreoffice don't. I don't know where the log files are? Is there anyone that can give me a helping hand. Thanks. John

2 2

Re: [arch-general] MediaWiki extension and fix pull request
by William Gathoye 16 Dec '14

16 Dec '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/16/2014 01:42 AM, Dario Giovannetti wrote: > Just a quick clarification from work, I never showed support for > installing the cite extension, and I'm aware that it's developers, > and not TUs, that have access to the repos. This is why I specified "especially me". But I admit, you haven't indeed explicitly mentioned the idea to install that extension, though without completely refusing that idea ;-) And for plea of that Cite extension: TL;DR: The keyword citation method from the Cite extension is better. I *do* see the need to explicitly be able to cite an article at the exact location where we made an assumption in our content. Using a keyword and putting the detailed source at the end of the document seems the best way if the link is used at several location in the document. As an example, if we cite some non tested assumptions we take from an article that we rapidly adapted to the Arch Linux world, the reader might be able to inform the original author, if he wants to, that the solution works or not. With a dedicated "see also" at the end of the document, it is less likely to happen. And as already written in the discussion on the wiki, "see also" implies that some more detailed information is available in that linked article, which is not necessary the case. A short blog post might just explain a really simple trick we completely integrated in our content (nearly copy-pasted). We are not aiming to provide and duplicate documentation from upstream. I personally don't like that idea, excepted if this leads to a disjointed article with bunch of references everywhere (e.g. the VirtualBox article I rewrite). In the case of DKMS for example, you cannot actually find any recent and updated "starting guide" excepted this old unnecessary very long one [1] dating back from 2003. The Wikipedia page is nearly non existent, and upstream does only provide a technical indigestible man page. Ubuntu does provide some more general technical guide, but again not really adapted to Arch [2]. Regards, [1] http://www.linuxjournal.com/article/6896?page=0,0 [2] https://help.ubuntu.com/community/DKMS - -- William Gathoye <william(a)gathoye.be> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUj4cdAAoJEA595SwE1xaDut4P/0rW8dsAU+15FsNfCR9WtVwV 4QB7Nk6yOr3cWZFrFhYFOZexEI0fUgbezFzFtLyiXOSywOtszcI6u2yaoxg9/YC8 sdKQZNskHtn4zANBjhQwq4cpGwCzxm+IOeZC978wWYNbONB+Jb/mUEtg23H6492m oZ8278MPRdkEWWwha4YZpWt+meYn381ZHPXNiefDzrDnO8N5Olel8AUxdY2OsfcY GQfPDGwPqIJfQ2fzQHPNaBt73lE3s1Y9M8ek5Xch9/7dbDeV6Lwf+1tBbtEiD2AJ onXcVtRY5q1AnhQf/tKkgaV24keRwwzRILB9Ue6x5r+MIxZ0wZbgfCIB31Lgkbw/ JIw7hJa63doTRhqB15SsKY4laMTy0sjorJNa0n4vXr7KuLj07OXkYWBRZDgKT2Cc 94VHumqfwa5ePX3TDjpklPxJQINL4yozMkDteZVYfeVl4Gg4iEwauCJoL2jSYjey YqTntL3qqE5llIaCfAPJYElKS4Do19osyeD5uoOv1N4/hObkb5CJgoGwpWqt/lsz L3RLpnxd+3QI8/GZs5B6G5KQmrqdmbWBwcvTaZvOBWOCFoRGB7KGyQ8EjyKMwS3n /h/B4lGs1Gmnx4RPxk3Kwo7EpklEVFf1Nz7u1g9txsIqHKTiYd1pBdyC+gXTWNw5 Js4QCpWFeNzy3TIV5LPx =uD29 -----END PGP SIGNATURE-----

3 3

Re: [arch-general] MediaWiki extension and fix pull request
by Dario Giovannetti 16 Dec '14

16 Dec '14

Just a quick clarification from work, I never showed support for installing the cite extension, and I'm aware that it's developers, and not TUs, that have access to the repos. Dario (kynikos) On Dec 16, 2014 8:14 AM, "William Gathoye" <william(a)gathoye.be> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi guys, > > Regarding a discussion Kynikos and me had [1], it would be nice, if > any TU could finally merge a pull request that we have been waiting > for months[2]. > > Also, Kynikos, and especially me, wanted to have a way to cite our > sources when writing articles. I feel indeed ashamed not being able to > cite properly articles or blog posts we based our own content on. This > is why I'm kindly asking any TU if it would be possible to install the > Cite extension [3] to our MediaWiki instance. > > Thanks a lot in advance. > > Regards, > > > [1] http://goo.gl/nbGmlo > [2] https://bugs.archlinux.org/task/38769 > [3] https://www.mediawiki.org/wiki/Extension:Cite > > - -- > William Gathoye > <william(a)gathoye.be> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJUj3loAAoJEA595SwE1xaDpn4P/0OUPyfDzI6iK1xwrwjYkr6n > zNkOJ4uplXwzV+iXDmuL22V++9sKYj3++fLqfgAXWGezoqKGiyHnJI0mUMEOow04 > wPmK/Gwro7y+1xqdXYnsyWeRfodcT8nlVKXPn+Vf77R33VAdAqrn2FRTqsWrlr0I > ZOjQWc0DPuMXCjf3mXrTqtLahj1yGyEwrh9Zw8P8Drsf7fIGxZp0COr78pWxfhxe > e7UtKVXUI8xw8SEr9SDLdGTBYFoP9nsMCnsa8Yi61Uiecraed+OVBFS4g7p94bfE > GcaIogHw/A11mQfQynX21NyA6+DwO/RT+ZXczqHNQJAfmWoc27erTIGO+LDvH81Q > I8G0IJrtZjvTPKL0Ajy6dA4jYXvSjy63QH9P7gllhqOfOmct/hYhYqw81FeEmY5B > HD32oYlbAx+4Xpv0XKO/QIGrllKQN97flTSzKVCWwrYq6OSicNl4h4Wq3kErnrxL > OWr5NjAQ4llv/DswD7eJUW/jZLRuxJMd8JvVZ4cCETS/ifJxpJr+YGhTfMeCNlFE > us8kr2ab0atiSI3BsFhx5/1pGiQA6QPX4ftyz/wqV4sOYfulJmMAIgSWvjDBl2gy > nU0L1kxAqgUbeh3ypMthk7U/7nqYr5nvzZ6zBTdfAlXHbeGJD54r2aj2BAGODIMz > Ap/0hA0B2omWiJAvudpQ > =cV79 > -----END PGP SIGNATURE-----

1 0