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

[arch-general] File conflict between cuda and pacparser
by Chi Hsuan Yen 27 Aug '14

27 Aug '14

Hello, Arch lovers, Both community/pacparser and community/cuda contain the file /usr/share/man/man3/deprecated.3.gz, so pacman prevent me from installing both packages. How can I jump over the obstacle? Maybe it's better to establish some mechanism for preventing irreleveant packages with common files. In addition, is there a dedicated mailing list for discussions on official (not AUR) packages? Something like commenting system on the AUR website is also fine.

6 8

[arch-general] Rethinking our CA certificate setup
by Jan Alexander Steffens 26 Aug '14

26 Aug '14

Hi guys, I'm currently at FrOSCon with Pierre and an expert from CAcert.org and we're thinking of changes to our certificate setup. The current issues are: - Mozilla NSS uses its own root store and not /etc/ssl/certs - ca-certificates ships outdated Mozilla roots - Shipping additional roots outside ca-certificates is difficult, requiring patching /etc/ca-certificates.conf To solve these issues, we thought of making the following changes: - Attach NSS to p11-kit so it uses our root store (easily done by replacing /usr/lib/libnssckbi.so with a symlink to p11-kit-proxy.so) - Patch the update-ca-certificates script to read /etc/ca-certificates/conf.d instead of /etc/ca-certificates.conf - Split the current Mozilla roots from the NSS package in the ca-certificates format, shipping /etc/ca-certificates/conf.d/mozilla.conf - Create a package shipping the CAcert.org roots in a similar way - Ship the update-ca-certificates script in a ca-certificates-utils package, which the certificate packages depend on - ca-certificates becomes a metapackage depending on the -mozilla and -cacert packages Comments are welcome. Unless we get objections, we're going to start making these changes. Hopefully we can be done today and push the result to [testing]. Greetings, Jan

2 3

[arch-general] 3.16.1-1 :install custom kernel failed. No packages were upgraded- depmod for a wrong kernel name
by arnaud gaboury 26 Aug '14

26 Aug '14

Hi, I have been building/installing a custom kernel for some time now with no issues. I always follow the same process: ------------------------------------------------ * $ ABSROOT=. abs core/linux * edit the PKGBUILD: -pkgbase=linux-hortensia uncomment #make nconfig, * $ makepkg load MyConfigFile, do sometimes some stuffs, save as .config, exit nconfig * # pacman -Ud linux-hortensia-headers # pacman -U linux-hortensia # pacman -U linux-hortensia-docs ----------------------------------------------------- I decide to give a try at Nouveau: --------------------------------------------------------- -pkgbase=linux-nouveau * nconfig: Device Drivers ---> Graphics support ---> DRM ---> <M> Nouveau (nvidia) cards Frame buffer Devices ---> <M>Support for frame buffer devices ---> empty all * save as .config * # pacman -Ud linux-nouveau-headers. ---> long list of lines all in this type <--------- linux-nouveau-headers: /usr/lib/modules/3.16.1-1-hortensia/build/sound/soc/intel/Kconfig exists in filesystem <------------------------> Errors occurred, no packages were upgraded ----------------------------------------------------------------- I am surprised as it is the first time I have this error. I am expecting the new headers to be installed in /usr/lib/modules/3.16.1-1-nouveau and NOT in the 3.16.1-1-hortensia dir. Why do I have again the /3.16.1-1-hortensia folder in linux-nouveau/pkg/linux-nouveau/usr/lib/modules/3.16.1-1-hortensia, and not a /3.6.1-1-nouveau/ folder instead? Last, at the end of the makepkg command, I can see: DEPMOD 3.16.1-1-hortensia. Why not DEPMOD 3.16.1-1-nouveau? Did anything changed when building/installing custom kernel? Or is there any wrong variable somewhere in the PKGBUILD? Thank you for suggestion

1 0

[arch-general] System vs. user-wide locale
by Alad Wenter 25 Aug '14

25 Aug '14

Hi, Arch Linux currently emphasises on setting the locale system-wide. If a non-english language is desired, it should be uncommented in /etc/locale.gen (besides en_US.UTF-8), and set in /etc/locale.conf. https://wiki.archlinux.org/index.php/Installation_guide#Configure_the_system https://wiki.archlinux.org/index.php/Beginner%27s_guide#Locale While the Locale article mentions a user-wide setting (.config/locale.conf), this is more an aside for "multi-user" systems. https://wiki.archlinux.org/index.php/Locale#Setting_per-user_locale An alternative approach is mentioned in the Funtoo FAQ: "The next thing I recommend is to try to avoid changing the global system LANG setting, and instead set the LANG setting on a per-user basis by adding the desired LANG setting to your ~/.bashrc. This will preserve English log output in /var/log and make it easier to search for more common matching English strings on the Internet when you need help." http://www.funtoo.org/Funtoo_Linux_FAQ#What_if_I_want_to_use_a_non-English_… Thus /etc/locale.conf would have LANG=en_US.UTF-8, and other languages would be defined in ~/.bashrc (or rather ~/.config/locale.conf). This sounds like a fair argument. Are there possible downsides to this approach in Arch, or can/should the respective articles be updated? Regards, -- Alad Wenter <the.changing.side(a)gmail.com>

3 2

[arch-general] Unable to dual seat- one nvidia card- lightdm
by arnaud gaboury 25 Aug '14

25 Aug '14

Even after lots of readings and many tries, I am not able to set up a working dual seat configuration on my machine. I have two users, two monitors, two mouses, two keyboard, unfortunately one only nvidia card. But from what I read, it is possible to have two users both logged and sharing only the video card. My issues: - I can not limit one user to one monitor. The screen uses the two monitots. - Second user has a "double" task bar in his mate session. Everything is repeated twice. -First user log with lightdm with one only keyboard & mouse (second pair is automatically dis activated). But for the second, I have to Ctrl+Alt+Fn, then $ startx at login promp, or switch user with lightdm. I guess it is not the expected behaviour. Below are my settings. /etc/X11/xrog.conf.d/15-seat.conf (the only one xorg conf file). ----------------------------------------------------------------- Section "ServerFlags" Option "AutoAddDevices" "false" Option "AutoEnableDevices" "false" Option "AllowEmptyInput" "true" Option "AllowMouseOpenFail" "true" Option "AutoAddGPU" "false" Option "DPMS" "true" # adding Xinerama off does not change anything EndSection Section "ServerLayout" Identifier "layout-martinus" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "evdev" Option "Device" "/dev/input/event17" Option "GrabDevice" "true" EndSection Section "InputDevice" Identifier "Mouse0" Driver "evdev" Option "Protocol" "auto" Option "Device" "/dev/input/event18" Option "GrabDevice" "true" EndSection Section "Device" Identifier "Card0" Driver "nvidia" VendorName "NVIDIA Corporation" BusID "PCI:1:0:0" Option "NoLogo" "1" Screen 0 EndSection Section "Monitor" Identifier "Monitor0" Option "VendorName" "Unknown" Option "ModelName" "Generic Autodetecting Monitor" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" Option "NoLogo" "true" DefaultDepth 24 Subsection "Display" Depth 24 EndSubsection EndSection Section "ServerLayout" Identifier "layout-loulou" Screen 1 "Screen1" leftof "Screen0" InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Keyboard1" Driver "evdev" Option "Device" "/dev/input/event0" Option "GrabDevice" "true" EndSection Section "InputDevice" Identifier "Mouse1" Driver "evdev" Option "Device" "/dev/input/event4" Option "Protocol" "Auto" Option "GrabDevice" "true" EndSection Section "Device" Identifier "Card1" Driver "nvidia" VendorName "NVIDIA Corporation" BusID "PCI:1:0:0" Screen 0 EndSection Section "Monitor" Identifier "Monitor1" Option "VendorName" "Unknown" Option "ModelName" "Generic Autodetecting Monitor" EndSection Section "Screen" Identifier "Screen1" Device "Card1" Monitor "Monitor1" Option "NoLogo" "true" DefaultDepth 24 Subsection "Display" Depth 24 EndSubsection EndSection --------------------------------------------------- /etc/lightdm/loghtdm.conf ------------------------------------------------------ [LightDM] minimum-display-number=0 minimum-vt=1 user-authority-in-system-dir=true [SeatDefaults] greeter-session=lightdm-gtk-greeter greeter-setup-script=/usr/bin/numlockx on [Seat:0] xserver-layout=layout-martinus xserver-command=/usr/bin/Xorg # xorg : 0 does not change anything, neither adding -sharevts [Seat:1] xserver-layout=layout-loulou xserver-command=/usr/bin/Xorg -sharevts -noswitch # xorg : 1 does not change anything, neither removing, the -sharevts -noswitch arguments. ------------------------------------------------------ Thank you for any suggestion. -- google.com/+arnaudgabourygabx

1 1

[arch-general] bugs.archlinux.org - enable comments on closed issues
by Nowaker 25 Aug '14

25 Aug '14

Hi, This is annoying that the reporter can't leave any comment after the issue is closed. No, I don't want to "Request re-open". The issue is closed for a good reason, no doubt. But closing the issue shouldn't end the discussion - the reporter may want to add something. Can you please consider changing this? Thanks. -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu

5 5

[arch-general] Help diagnosing kworker 'bug'
by Oon-Ee Ng 24 Aug '14

24 Aug '14

Yesterday night I noticed (just before performing an update my conky showing high continuous writing to root. iotop -Pa shows this:- Total DISK READ : 0.00 B/s | Total DISK WRITE : 8.93 M/s Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 11.06 M/s PID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 112 be/4 root 0.00 B 64.91 M 0.00 % 24.34 % [kworker/u16:3] 11936 be/4 root 0.00 B 0.00 B 0.00 % 0.06 % [kworker/1:1] 28794 be/4 root 0.00 B 36.00 K 0.00 % 0.00 % [kworker/u16:1] This is after roughly 6-7 seconds, and 65 MB has already been written by that kworker thread. As I said, this was already happening before an upgrade. I ran the upgrade anyway, which upgraded linux to 3.16-2, and still got the same thing. Yes, I'm using [testing]. Any ideas on how to proceed? Next thing I'm going to try is downgrading linux to 3.15, but I thought I'd post this here first in case I don't make it back.

2 6

[arch-general] LibreOffice update
by Viktor G 23 Aug '14

23 Aug '14

Hello, I want to update my LibreOffice installation but pacman informed me about a conflict with the packages. So, there are libreoffice-still-* packages and there is one libreoffice-fresh package. I want to update to 4.3.x. Why are versions split into two branches and does libreoffice-fresh contain all the LO applications like Writer, Calc, etc.? (There is no libreoffice-fresh-writer or libreoffice-writer package) Thanks Vik

3 5

Re: [arch-general] LibreOffice update
by Steven Grace 23 Aug '14

23 Aug '14

On 08/23/2014 11:32 AM, Sebastiaan Lokhorst wrote: > 2014-08-23 20:20 GMT+02:00 Andreas Radke <andyrtr(a)archlinux.org>: >> >> We dropped the app splitting because they are of small size and sometimes >> upstream broken the >> dependencies between the parts. >> > Does this also mean we will stop splitting -still? It is strange to split > Still but not Fresh. (I'm all for shipping one large pkg by the way) I take the opposite view. I prefer a minimal system and only use Writer and Calc, so I prefer to keep the components separate.

1 0

Re: [arch-general] [arch-dev-public] systemd 216 coming soon to testing
by Leonid Isaev 22 Aug '14

22 Aug '14

Hi, [sorry for cross-posting] On Wed, Aug 20, 2014 at 02:25:24PM -0400, Dave Reisner wrote: > Full NEWS file: > > http://cgit.freedesktop.org/systemd/systemd/tree/NEWS This changelog says that: * journald will no longer forward all local data to another running syslog daemon. This change has been made because rsyslog (which appears to be the most commonly used syslog implementation these days) no longer makes use of this, and instead pulls the data out of the journal on its own. Since forwarding the messages to a non-existent syslog server is more expensive than we assumed we have now turned this off. If you run a syslog server that is not a recent rsyslog version, you have to turn this option on again (ForwardToSyslog= in journald.conf). This is going to break syslog-ng... So is it possible to patch journald.conf and enable ForwardToSyslog in the package? Thanks, -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D

4 6