March 2017 - Arch-general - lists.archlinux.org

[arch-general] [arch-dev-public] AUR ToS (aka making AUR user names public)
by fnodeuser 07 Mar '17

07 Mar '17

Bartłomiej Piotrowski, it is the same email address that i have been using since the beginning. what opinions? i never talk with opinions. i always talk with facts.

3 2

[arch-general] [arch-dev-public] AUR ToS (aka making AUR user names public)
by fnodeuser 07 Mar '17

07 Mar '17

Eli Schwartz, no one is paranoid here. we do not want security and privacy issues. YANG Ling, sharing the requested data will not benefit us in any way. Lukas Fleischer, why are you talking on her behalf? why did she send a message to you instead of one to the ML? why is she not answering any questions in this ML?

2 1

[arch-general] sending emails with gmail WAS: [arch-dev-public] AUR ToS
by Martin Kühne 06 Mar '17

06 Mar '17

On Mon, Mar 6, 2017 at 1:58 PM, Henrik Danielsson via arch-general <arch-general(a)archlinux.org> wrote: > [...] the quote in Mauro's > mail did not render as a quote normally does in Gmail, hence I was not > sure it would render correctly if I messed up the copying it (HTML > entities and all). Just turn it off. GMail's web interface does plain text email really well to my tastes, and you can actively enable it from the dropdown menu on the right of the bottom toolbar. All html is then stripped by default and apart of newlines, you can have isprint()-only conversations from then on. You might want to subscribe to arch-dev-public. The conversation started there and was taken to arch-general at some point. cheers! mar77i

1 0

[arch-general] Strange update of libvirt
by Peter Nabbefeld 04 Mar '17

04 Mar '17

Hello, I got the following message when updating: Warnung: /etc/libvirt/qemu/networks/default.xml installed as /etc/libvirt/qemu/networks/default.xml.pacnew As I wanted to know what to copy from the pacnew file, I did: sudo diff /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/default.xml.pacnew The result was: 1,7d0 <  < 10,14c3,6 < <uuid>cc98c916-edd7-4e5f-8fbc-60839e8fa692</uuid> < <forward mode='nat'/> < <bridge name='virbr0' stp='on' delay='0'/> < <mac address='52:54:00:3a:62:50'/> < <ip address='192.168.122.1' netmask='255.255.255.0'> --- > <uuid>73618f96-1a85-47a8-a809-7edd8ad7899a</uuid> > <bridge name="virbr0"/> > <forward/> > <ip address="192.168.122.1" netmask="255.255.255.0"> 16c8 < <range start='192.168.122.2' end='192.168.122.254'/> --- > <range start="192.168.122.2" end="192.168.122.254"/> First, I noticed the removal of the warning - obviously this file hasn't been used for manual configurations (instead auto-configured) - what has changed in configuration handling? Second, the uuid has changed - why? So, do I have to change my original file or better ignor the pacnew file? Kind regards Peter

2 1

[arch-general] Creating a Radius Ethernet Profile with netctl
by Hunter Jozwiak 03 Mar '17

03 Mar '17

Hi, I have a 802.11X connection here at my campus, and I don't know how to set this up with the netctl utility on the Arch Linux ISO. Are there guides on accomplishing this? Also, when I connect normally, there is a web site that comes up asking for my log on reedentials. How do I bypass this with netctl if possible, and if not, how do I authenticate? Hunter

4 3

[arch-general] Intermittent problem accessing samba shares
by Paul Marwick 02 Mar '17

02 Mar '17

Fully updated Arch install, running Xfce. I don't use Samba very much, but need it for access at various times, so I have gvfs, gvfs-smb and smbclient installed. Normally no problem accessing Samba shares from Thunar. However.... Recently I spent some time trying to work out why a client was unable to access Samba shares from an Xubuntu desktop machine (shares are on an Ubuntu 16.04 server). While I was testing, I did something (wish I knew what...) and ended up with Thunar suddenly being unable to access any Samba share, even though I could use mount.cifs to mount the same share. When I got back to my home network, I found similar problems, even though I'd never had any problems in that area with this install of Arch. At the same time, another Arch install on the same laptop had no problems accessing the shares, and my desktop machine was also still able to access the shares without any problems. The problem is strange and very variable. Sometimes it fails as soon as I click "browse network" - the system sits and then comes back with 'unable to access "/" timeout was reached'. Sometimes I get a display of the Windows network icon, then it fails to open the Windows network display. Other times, I am able to see and mount a share on the network. This is on the same network, with no changes made to the network (one Slackware-based server, one Ubuntu 16.04 server). And a network which other Arch installs have no problems accessing the shares. I've checked messages using journalctl and dmesg and see nothing when the access fails. The part I find really puzzling is that sometimes it works with any problems, other times it fails as soon as I start. I'm confident that the prolbem is not Thunar itself. I installed pcmanfm to see if a different file manager would behave differently, but it shows exactly the same problem - sometimes it works, other times it fails. I'm at a loss as to how I track this error. I'd really like to fix it, so I'm hoping someone can suggest what might cause the problem, and how to fix it? I've seen problems like this in the past (mainly on Debian based distros, though a few years ago on an Arch install). One of a very small number of problems I've never been able to predictably fix. Paul.

2 1

[arch-general] Why isn't SELinux officially supported?
by Robert Wong 01 Mar '17

01 Mar '17

Having been using Arch Linux with Gsecurity-patched Kernel (Though installed a LTS Kernel for emergency fallback.) for half a year, I got a question. I found all the SELinux-concerned packages at the AUR, as well as the detailed RW

4 6

[arch-general] Kaffeine video problem
by pete nikolic 01 Mar '17

01 Mar '17

Hi .. Got a problem with kaffeine right now . this is kaffeine 2.0.6 running on a fully updated KDE/Plasma system . When i run kaffeine then try to view the TV i get audio but no video when run from a terminal i get [00007fc300001268] vdpau_display vout display error: output surface creation failure: a catch-all error , used when no other code applies . digging futher it seems the nouveau_drv_video.so cant be found i cant find it on the system either . this system is updated daily using "pacman -Syu" the tv was working fine a week ago came to use it 2 days ago not display and the errors Pete .

1 0