- Arch-general - lists.archlinux.org

[arch-general] Mounting cdrom/dvd stopped working after updates in last week or so
by mick 11 Jun '14

11 Jun '14

Updates I installed in the last week or so have caused this error message to appear instead of the disk being mounted: Error mounting /dev/sr1 at /run/media/mick/VMDVEC_ESSH_ENG1: Command-line `mount -t "iso9660" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=100,iocharset=utf8,mode=0400,dmode=0500" "/dev/sr1" "/run/media/mick/VMDVEC_ESSH_ENG1"' exited with non-zero exit status 32: mount: unknown filesystem type 'iso9660' Also when I try to mount my USB hard drive I got the following: Error mounting /dev/sde2 at /run/media/mick/Portable: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177" "/dev/sde2" "/run/media/mick/Portable"' exited with non-zero exit status 32: mount: unknown filesystem type 'ntfs' Prior to these problems the hard disk would only mount as read only, very useful for a back device. where can I find the solution to these problems?

2 1

[arch-general] python2-lockfile signature failure
by Chris Tonkinson 10 Jun '14

10 Jun '14

Having just refreshed my desktop system with a clean Arch install, I am seeing a signature failure in the python2-lockfile package (dependency for duplicity). Is anyone else seeing this? `pacman --debug` isn't giving me any additional useful information that I can see. Where might I look next? Here's my output: $ sudo pacman -S duplicity resolving dependencies... looking for inter-conflicts... Packages (6): librsync-0.9.7-7 ncftp-3.2.5-4 python2-ecdsa-0.11-2 python2-lockfile-0.9.1-1 python2-paramiko-1.14.0-1 duplicity-0.6.24-1 Total Download Size: 0.01 MiB Total Installed Size: 6.13 MiB :: Proceed with installation? [Y/n] :: Retrieving packages ... python2-lockfile-0.9.1-1-any 11.9 KiB 0.00B/s 00:00 [########################################################] 100% (6/6) checking keys in keyring [########################################################] 100% (6/6) checking package integrity [########################################################] 100% error: python2-lockfile: signature from "Thorsten Töpper <atsutane(a)freethoughts.de>" is unknown trust :: File /var/cache/pacman/pkg/python2-lockfile-0.9.1-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package) Errors occurred, no packages were upgraded. 545 chris@vigilance tnet $ Cheers, -Chris -- Chris Tonkinson 610.425.7807 "Work as if you were to live a hundred years. Pray as if you were to die tomorrow." -Benjamin Franklin

2 3

[arch-general] No longer able to print
by Squall Lionheart 10 Jun '14

10 Jun '14

Hello, Since about three weeks ago after an update, I have no longer been able to print using CUPS. When I send a job to the print queue, it generates this message: stopped *"The PPD version (5.2.9) is not compatible with Gutenprint 5.2.10."* I was unable to find anything helpful through the search engines. Was there a package split for older drivers, or perhaps something else I need to install to get this to work again? Running linux 3.14.6-1 and: $ pacman -Qs cups local/cups 1.7.3-3 local/cups-filters 1.0.54-1 local/libcups 1.7.3-3 $ pacman -Qs gutenprint local/gutenprint 5.2.10-1 $ pacman -Qs ppd local/foomatic-db 3:20140324-1 local/foomatic-db-engine 3:20140324-1 $ pacman -Qs hplip local/hplip 3.14.6-1 Thank you Squall -- Yesterday is history. Tomorrow is a mystery. Today is a gift. That's why its called the present. Headmaster Squall :: The Wired/Section-9 Close the world txen eht nepo $3R14L 3XP3R1M3NT$ #L41N https://github.com/headmastersquall

3 3

[arch-general] Starting gpg-agent from systemd?
by Magnus Therning 10 Jun '14

10 Jun '14

For the first time ever today, I noticed this little gem of a message from gpg: ~~~~ gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work proberly - please configure that tool to not interfere with the GnuPG system! ~~~~ So I started looking into some nice way of switching to gpg-agent, but how to start it in a nice way when using Gnome? The instructions at [^1] are for the shell and for using ~/.xinitrc to start X. So neither is very well suited for me as I'm letting GDM log me in to Gnome without use of ~/.xinitrc and the agent has to be available also to apps started via Gnome Shell. I have a feeling this ought to be solvable using systemd but I can't really see how. Writing a service for gpg-agent is not that difficult, and it creates the required environment file without problems. But, how do I hook it in to the user login in the right way? Who should be wanting my gpg-agent.service, and then load the generated file using EnvironmentFile=? All pointers are welcome. /M [^1]: https://wiki.archlinux.org/index.php/GnuPG#gpg-agent -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus(a)therning.org jabber: magnus(a)therning.org twitter: magthe http://therning.org/magnus What gets measured, gets done. -- Tom Peters

4 6

Re: [arch-general] misleading pacman errors when upgrade fails
by Simon Hanna 08 Jun '14

08 Jun '14

> > > Is any of this worth reporting as bugs or enhancements? > There actually is a bug report https://bugs.archlinux.org/task/33076 but it's quite old...

1 0

[arch-general] [HELP] Upgrading kernel results in unmounted partitions
by Thilina Mallawa Arachchi 08 Jun '14

08 Jun '14

Hi Arch Community, Today I upgraded the kernel from a fresh install of 3.14 to 3.4 via the yaourt install of linux-lts34 from AUR. Booting results logging into the recovery console as root. My / partition is being booted but my /var and /home are not. Very similar to this post https://bugs.archlinux.org/task/40706 and also this discussion on the list https://mailman.archlinux.org/pipermail/arch-general/2014-June/036488.html. The above links refer to using UTC time as a solution. I am using UTC time as per the beginners installation guide for the first fresh install of 3.14 but still run into the issue after the kernel upgrade. Would someone guide me (in detail) for fixing the issue? I need to run the 3.4 kernel for the particular piece of hardware I'm working with. Best, Thilina

2 2

[arch-general] Anybody unable to boot Arch after installing latest updates?
by Ralf Mardorf 08 Jun '14

08 Jun '14

Hi, likely an update I run after 2014-06-03 19:39 +0200 has broken something. I only can boot Arch after I commented out everything in /etc/fstab, excepted of /. I have no time for journalctl etc. right now. Does anybody experience the same or another issue? [root@archlinux rocketmouse]# cat /etc/fstab # # /etc/fstab: static file system information # # <file system> <dir> <type> <options> <dump> <pass> # UUID=f386221b-fc9c-434b-b4e7-b3b1b97be8aa LABEL=archlinux /dev/sda9 / ext3 rw,relatime,data=ordered 0 1 # UUID=3e19b702-30ed-4574-91d7-1594fad71842 #/dev/sdb7 none swap defaults 0 0 # UUID=4b65ccbf-2219-4734-98fa-16c58d4f60fa #/dev/sda10 none swap defaults,pri=-2 0 0 #/dev/sda11 /mnt/music ext3 noatime,defaults 0 2 #/dev/sdb12 /home/music ext4 noatime,defaults 0 2 #dev/sda14 #LABEL=debbsd /mnt/debbsd ext4 noatime,defaults 0 2 [snip] Regards, Ralf

2 2

Re: [arch-general] Unwanted forced fsck at each startup - Was: How do I _really_ fix the superblock?
by Ralf Mardorf 08 Jun '14

08 Jun '14

On Sun, 2014-06-08 at 09:38 +0200, Ralf Mardorf wrote: > On Sun, 2014-06-08 at 08:23 +0200, Ralf Mardorf wrote: > > On Sat, 2014-06-07 at 23:24 +0200, Ralf Mardorf wrote: > > > On Sat, 2014-06-07 at 17:13 -0400, Leonid Isaev wrote: > > > > I'd remove the fsck hook to let systemd check the filesystems and see > > > > if that helps. > > > > > > Done, but I won't reboot now. I will report back next time I (re)boot > > > Arch Linux. > > > > fsck still is forced to run :( > > # downgrade systemd libsystemd systemd-sysvcompat > # pacman -Q systemd libsystemd systemd-sysvcompat > systemd 212-3 > libsystemd 212-3 > systemd-sysvcompat 212-3 This doesn't solve the issue and that is very, very bad :(. What package should I downgrade too, to get rid of the brand new "run fsck at each startup" issue? I could restore Arch from a working backup I made a few days ago, but what packages shouldn't I upgrade, after I restored my Arch install?

1 0

[arch-general] How do I _really_ fix the superblock?
by Ralf Mardorf 08 Jun '14

08 Jun '14

Hi, I still need to comment out everything in fstab, excepted of / (it does include home) to boot Arch Linux, so at least I'm able to boot. Anyway, each time I boot, I get a message that the superblock's last write time was in the future, it always gets fixed and than always the / partition is checked. The Arch Linux partition is an ext3 FS, so I run fsck.ext3 -p from a live media and it pretended too, that the issue is fixe, but it isn't. JFTR the hardware clock does work correctly. I suspect it isn't related to the perl pain, that makes a lot of important software from AUR unusable on my machine. Could systemd be the culprit? [rocketmouse@archlinux ~]$ grep systemd /var/log/pacman.log | grep 2014-06-04 [2014-06-04 08:34] [PACMAN] upgraded libsystemd (212-3 -> 213-5) [2014-06-04 08:34] [PACMAN] upgraded systemd (212-3 -> 213-5) [2014-06-04 08:34] [PACMAN] upgraded systemd-sysvcompat (212-3 -> 213-5) I could restore my Arch from a backup to fix it, but than I wouldn't know what packages to upgrade and what package upgrades I need to ignore. JFTR after I booted Arch Linux I can remove the #'s from fstab and mount everything in fstab. Regards, Ralf

6 22

[arch-general] misleading pacman errors when upgrade fails
by Carl Schaefer 08 Jun '14

08 Jun '14

I just tried to upgrade three packages, including core/filesystem, and saw these errors: filesystem-2014.05-... 8.7 KiB 4.23M/s 00:00 [######################] 100% e2fsprogs-1.42.10-1... 691.8 KiB 1305K/s 00:01 [######################] 100% cups-filters-1.0.54... 648.6 KiB 2033K/s 00:00 [######################] 100% (3/3) checking keys in keyring [######################] 100% (3/3) checking package integrity [######################] 100% (3/3) loading package files [######################] 100% (3/3) checking for file conflicts [######################] 100% (3/3) checking available disk space [######################] 100% (1/3) upgrading cups-filters [######################] 100% (2/3) upgrading filesystem [######################] 100% warning: /etc/passwd installed as /etc/passwd.pacnew warning: /etc/group installed as /etc/group.pacnew error: extract: not overwriting dir with file /usr/local/share/man error: problem occurred while upgrading filesystem error: could not commit transaction error: failed to commit transaction (transaction aborted) Errors occurred, no packages were upgraded. The failure was apparently caused by /usr/local/share/man being a real directory on my system, when the "filesystem" package wants it to be a symlink to "../man". I imagine pacman could check in advance for this sort of extraction problem for all packages before upgrading or installing any packages, which could be part of the existing "checking for file conflicts" phase. Also, the error messages about the transaction being aborted and no packages being upgraded are wrong. The upgrade of "cups-filters" was successful, and "filesystem" appears to have been upgraded too. The only upgrade that was aborted was "e2fsprogs" that pacman hadn't started. Is any of this worth reporting as bugs or enhancements? Carl

1 0