February 2015 - Arch-general - lists.archlinux.org

[arch-general] Why are CA certifcates writable for every user?
by Marcel Kleinfeller 07 Feb '15

07 Feb '15

Hello! When I'm doing "cd /etc/ssl/certs/ && ls -al" I see something like this: [...] lrwxrwxrwx 1 root root 102 21. Dez 17:56 Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem -> ../../ca-certificates/extracted/cadir/Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem [...] All certificates are publicly writable. I never set chmod to 777 on this directory and I see a great security lack here. Any program could inject its own certificate there, you should know this isn't good ;) Tell me whether this is just an issue on my own system or a general issue. Marcel Kleinfeller <marcel(a)oompf.de>

7 7

[arch-general] startx failed: modprobe: ERROR: could not insert 'nvidia': Operation not permitted
by Csányi Pál 06 Feb '15

06 Feb '15

Hi, on a fresh install of arch linux I have first installed the nouveau video driver. Then I realise I must install the nvidia driver because one application doesnÍt work without it. I have linux kernel 3.14.31.-1-lts installed. My videocard is GeForce 7600 GT so I installed the nvidia-304xx-libgl nvidia-304xx-lts nvidia-304xx-utils I created the configuration file for X Window system: Section "Device" Identifier "Nvidia Card" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection In /etc/mkinitcpio.conf I have commented the line: #MODULES="nouveau" But, when I start X with 'startx' command, I get the error mentioned in subject of this mail. What am I missing here? -- Regards from Pal

4 5

[arch-general] core/crda and core/wireless-regdb are outdated
by Petko Bordjukov 06 Feb '15

06 Feb '15

Hello, The core/wireless-regdb package is 6 versions behind the current version of the wireless regulatory database (and has been flagged as out of date on 2014-12-02). I contacted the maintainer with a patch last month. Since then there has been a new release of wireless-regdb and a corresponding (and required by the newest version of wireless-regdb) release of CRDA. I have not yet received a response from the maintainer and I have patches that update both packages to the latest versions, what would you advise me to do in order to have them applied? Regards, Petko

1 1

Re: [arch-general] Fwd: Kernel panic - after upgrade
by Csányi Pál 06 Feb '15

06 Feb '15

2015-02-01 13:42 GMT+01:00 Guus Snijders <gsnijders(a)gmail.com>: > Op 1 feb. 2015 12:41 schreef "Csányi Pál" <csanyipal(a)gmail.com> het > volgende: > >> 2015-01-31 23:12 GMT+01:00 Guus Snijders <gsnijders(a)gmail.com>: >> > 2015-01-31 21:20 GMT+01:00 Christian Demsar <vixsomnis(a)fastmail.com>: >> > [...] >> >> At this point, I'd backup configuration files and home directories and >> >> do a full reinstall. Sounds like there's something going terribly >> >> wrong. >> >> Hopefully that works... >> > >> > Hmm, I'd first check if dmesg shows SATA error (bus reset, seek >> > failed, etc) and if that is not the case, I'd do a memory test >> > (memtest86 is very nice for this). >> > Seeing that the OP is getting kernel panics, my first guess is memory >> > problems (I fail to see how a bad HDD would cause panics), but I might >> > be wrong... >> >> The output of dmesg is here: >> http://pastebin.com/9TnBGHqn >> >> I did not see any suspicious in it. Am I right? > > A couple of things i noticed: > -Nvidea complaining about not having a textmode driver configured > - ext4 mentions 14 errors on sda4 > > I'm not sure if these are serious or not. Could you try the memtest first? > Bad memory can cause very strange errors and is easy to test (takes time, > though). Before I start the memtest I ask an advice: how long should I run the memtest? -- Regards from Pal

4 6

[arch-general] Trusting certificates when installing mono
by Drew DeVault 05 Feb '15

05 Feb '15

It can be a frequent problem among .NET devs that mono trusts no certificates by default. The usual procedure is to have users manually run `mozroots --import --sync` to trust the same certs Mozilla trusts, but that makes it so that there will always be a manual step after installing your software, even through a package manager. Can the mono package be altered to import all of the systemwide certificates (/etc/ssl/certs) into mono's trust store? This should make the problem much less frustrating. -- Drew DeVault

1 0

Re: [arch-general] [arch-dev-public] [extra] Dropping ocaml packages
by Mike Cloaked 03 Feb '15

03 Feb '15

On Tue, Feb 3, 2015 at 8:33 AM, Tobias Powalowski < tobias.powalowski(a)googlemail.com> wrote: > Hi guys, > I don't use it on any of my machines anymore, anyone who wants to step up? > Else those are candidates for AUR/community. > > ocaml > ocaml-compiler-libs > facile > lablgtk2 > unison > > greetings > tpowa > > I noticed from the arch-dev-public list in the post quoted above that ocaml is planned to be dropped to AUR or community. I also notice that ocaml is still a dependency for one of the kde packages. # pacman -R ocaml checking dependencies... error: failed to prepare transaction (could not satisfy dependencies) :: kdeedu-kalzium: requires ocaml I guess it needs to be maintained else there may be problems with updates to kde in the future? -- mike c

5 4

[arch-general] NFS server broke after reboot - *urgent* need help
by Genes Lists 01 Feb '15

01 Feb '15

I have a problem where nfs failed. 2 units fail to start rpc-statd.service nfs-server.service. ------------------------------------- rpc-statd: systemctl status rpc-statd rpc.statd[736]: Version 1.3.2 starting rpc.statd[736]: Flags: TI-RPC rpc.statd[736]: Running as root. chown /var/lib/nfs to choose different user rpc.statd[736]: failed to create RPC listeners, exiting systemd[1]: rpc-statd.service: control process exited, code=exited status=1 systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. systemd[1]: Unit rpc-statd.service entered failed state. systemd[1]: rpc-statd.service failed. ------------------------------------- I am unable to start this by hand either - continues to fail same way. I had seen this once a month or so back - but was able to start it by hand after machine was up. ------------------------------------- nfs-server: systemctl-status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2015-01-31 16:05:32 EST; 5min ago Process: 743 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=1/FAILURE) Process: 741 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS) Main PID: 743 (code=exited, status=1/FAILURE) rpc.nfsd[743]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused) rpc.nfsd[743]: rpc.nfsd: unable to set any sockets for nfsd systemd[1]: nfs-server.service: main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start NFS server and services. systemd[1]: Unit nfs-server.service entered failed state. systemd[1]: nfs-server.service failed. ------------------------------------- Machine is fully updated from testing repo. I did try kernel 3.19.rc6 but it does not help. nfs-utils 1.3.2-1 linux 3.18.5-1 rpcbind 0.2.2-1 Really appreciate some help - this is my main nfs server and I can no longer get it working ... Thanks for any advice. gene

6 12

[arch-general] Fwd: Kernel panic - after upgrade
by Csányi Pál 01 Feb '15

01 Feb '15

2015-01-18 18:20 GMT+01:00 Damjan Georgievski <gdamjan(a)gmail.com>: >> >>Here I exit from the prompt and reboot the machine, but get the same >> >>error message: can't run init. >> >> >> >>What did I wrong? >> > >> > You missed that the base group should be reinstalled, as the error is >> > not with the ramdisk, > > > there's no /init outside of the ramdisk, so his problem seems to be in the > initramfs, but probably because his base system is a bit borked and it > mkinitcpio creates the initramfs out of it. > > >> Well, I did so but can't to run successfully the `pacman -S base' >> command because of some difficulties. >> It complains about existing files and folder: >> it won't overwrite the /usr/lib64 folder. > > post the exact errors you're getting The output of `pacman -S base' command is: (50/50) checking keys in keyring (50/50) checking package integrity (50/50) loading package files (50/50) checking for file conflicts (50/50) checking available disk space ( 1/50) reinstalling filesystem error: extract: not overwriting dir with file /usr/lib64 error: problem occured while upgrading filesystem error: could not commit transaction error: failed to commit transaction (rransaction aborted) Errors occured, no packages were upgraded. I know that that the /usr/lib64 is a symlink only. What to do? -- Regards from Pal

10 46