users June 2016

users@lists.fedoraproject.org

137 participants
129 discussions

Default IP address for multihomed hosts changed in F24
by Sam Varshavchik 27 Jun '16

27 Jun '16

Not sure if this is known changed behavior in F24, but: For the longest time I had /etc/sysconfig/network-scripts/eno2 specify: TYPE=Ethernet BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no NAME=wan0 UUID=71e6ac4b-c693-4c20-aa0d-e1a63b7373fe ONBOOT=yes IPADDR1=216.254.115.102 PREFIX1=24 IPADDR2=216.27.136.223 PREFIX2=24 HWADDR=0C:C4:7A:32:C1:83 IPADDR=216.254.115.190 GATEWAY=216.254.115.1 PREFIX=24 IPV6_PEERDNS=yes IPV6_PEERROUTES=yes This host has three IP addresses, and up until now the default IP address for outgoing IP traffic was always 216.254.115.190, specified by IPADDR. It appears that, right now, all of my outbound traffic now appears to come from one of the other IP addresses, 216.254.115.102. This is true even if the outgoing socket explicitly binds to 216.254.115.190: Sending mail to gmail, with an explicit bind(), strace shows: 13232 bind(5, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "::ffff:216.254.115.190", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0 13232 fcntl(5, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 13232 getsockopt(5, SOL_SOCKET, SO_TYPE, [1], [4]) = 0 13232 connect(5, {sa_family=AF_INET6, sin6_port=htons(25), inet_pton(AF_INET6, "::ffff:173.194.206.26", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress) 13232 select(6, NULL, [5], NULL, {60, 0}) = 1 (out [5], left {59, 975901}) 13232 getsockopt(5, SOL_SOCKET, SO_ERROR, [0], [4]) = 0 13232 getsockname(5, {sa_family=AF_INET6, sin6_port=htons(41394), inet_pton(AF_INET6, "::ffff:216.254.115.190", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0 13232 select(6, [5], [], NULL, {300, 0}) = 1 (in [5], left {299, 975360}) 13232 read(5, "220 mx.google.com ESMTP 92si8123707qkx.29 - gsmtp\r\n", 512) = 51 Gmail still shows 216.254.115.102 as the received-from IP address. I note that getsockname() insists that the socket is 216.254.115.190 This host is using masquerading, with firewalld. I suspect that this is firewalld's doing. ip addr's output: 2: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 0c:c4:7a:32:c1:83 brd ff:ff:ff:ff:ff:ff inet 216.27.136.223/24 brd 216.27.136.255 scope global eno2 valid_lft forever preferred_lft forever inet 216.254.115.102/24 brd 216.254.115.255 scope global eno2 valid_lft forever preferred_lft forever inet 216.254.115.190/24 brd 216.254.115.255 scope global secondary eno2 valid_lft forever preferred_lft forever inet6 fe80::ec4:7aff:fe32:c183/64 scope link valid_lft forever preferred_lft forever Anyone knows what could be the reason for this, I'd like to have 216.254.115.190 as the default externally-visible IP address.

6 9

Re: Brasero: can't choose a directory. [SOLVED]
by William Mattison 27 Jun '16

27 Jun '16

Good afternoon, > I don't use brasero much, but on the offchance that this specific thing > works like it does in k3b, have you tried opening a seprate file manager > (nautilus, whatever) and dragging directory names from it into brasero? > or copy/paste into brasero? This works. Thank-you, Fred. > Uh, click on the "+" in the upper left corner, navigate the browser that > pops up, and double-click on the items you want in the new project. This does not work. That '+' does not pop up a browser or do anything else until after a directory/file has been selected. > Alternately, open the new data project, open a different file browser, > and drag and drop the directories you want into the project. This works. Thank-you, Rick. Bill.

2 2

rpmbuild error (wbar) on F24
by Ranjan Maitra 27 Jun '16

27 Jun '16

Hi, I have a local rpm that I have created using wbar. The spec file is here: https://paste.fedoraproject.org/384973/14669508 I have successfully created this rpm up to Fedora 23. But have been unable to do so this time around in F24. I get the following errors: .... cc1plus: all warnings being treated as errors Makefile:551: recipe for target 'wbar-Main.o' failed make[2]: *** [wbar-Main.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory '/home/maitra/rpmbuild/BUILD/wbar-2.3.4/src' Makefile:404: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/maitra/rpmbuild/BUILD/wbar-2.3.4' Makefile:345: recipe for target 'all' failed make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.qtyTEY (%build) I was wondering what is going wrong here. I am not very familiar with spec files, but have successfully built rpms by looking at other spec files. Btw, here is the source code for wbar: https://code.google.com/archive/p/wbar/downloads This not being my own software, I would be willing to submit this to fedora (when it works and if I can get sponsors) but for that, my rpm needs to get created. Thanks again! Best wishes, Ranjan -- Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses. ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth

4 7

Brasero: can't choose a directory.
by William Mattison 27 Jun '16

27 Jun '16

I'm using Fedora-23, last patched last Thursday, 6/23. Last Friday, I was trying to back up some directory trees to DVD. I launched Brasero, and chose "New Data Project". The result should have been a list of the directories and files at the home or root level. The file list area was blank. When I try "Project" -> "Open", a populated file browser shows up. I can navigate the file system successfully, but I can't find a way to select a directory for copying to the DVD. This all worked in March in F-22, when I backed up before upgrading to F-23. What am I doing wrong? Or what have I not done that I need to do? Thank-you in advance for your help. Bill.

4 3

Re: looking for a BASH tool
by Tom Killian 27 Jun '16

27 Jun '16

Once upon a time, SternData <subscribed-lists(a)sterndata.com> said: > Years ago, I used a tool called CED and PCED on DOS systems. I could > type in "abc" and press an up-arrow and it would walk back through my > stack of DOS commands showing only those with "abc" in them. > > There's *got* to be a similar tool for bash, but my google-fu is weak today. In addition to keyboard shortcuts... history | grep abc | less If what you're looking for came from a different, now closed, terminal window, try grep $HISTFILE abc | less

1 0

3.6.x version necessary before upgrading to 4.0
by Gianluca Cecchi 27 Jun '16

27 Jun '16

Hello, is there any requirement to update at latest 3.6.x version the engine before upgrading to 4.0? Or could I have for example 3.6.3 and directly upgrade to 4.0? Do you test upgrade only from latest previous version or what? And what about nodes in case they start as plain CentOS 7.x in 3.6.x? Thanks, Gianluca

2 1

dual screen settings lost after dnf update
by Gary Stainburn 27 Jun '16

27 Jun '16

I have a F23 system (upgraded from F22 a while since) with two screens. The two screens were configured correctly with the mouse moving off the right side of the left screen and appearing on the left side of the right screen, giving one desktop spread across the two monitors. I've done a 'dnf update' and now both screens are showing the same content. I know in the past I used to control this through xrandr and a bash script, but I haven't had to use that in ages. I thought all settings were now in KDE. However, Google etc. points me to kscreen inside "system settings" but I can't find where to change this setting. Can anyone help please?

2 3

Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
by David Dembrow 26 Jun '16

26 Jun '16

Date: Sun, 26 Jun 2016 11:41:21 -0400 From: "Mark C. Allman"<mcallman(a)allmanpc.com> Subject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23 To:users@lists.fedoraproject.org Message-ID:<2f2ce2bd-5601-811c-6024-2aa8da6a7e83(a)allmanpc.com> Content-Type: text/plain; charset=utf-8 On 06/26/2016 10:21 AM, David Dembrow wrote: > After completing the fedora 24 upgrade on a fedora 23 system there was > no graphical login and the system appeared to be running in console > mode (run level 3). > > I have always used KDE as the display manager and desktop. I noticed > a similar problem posted but none of its recommendations were > appropriate for my system. > > I found the graphical.target set as the default (systemctl > get-default). Then I noticed the graphical.target expects to have a > display-manager.service but the display-manager.service file was > missing. from the /etc/systemd/system directory. > > I copied the /etc/systemd/system/display-manager.service file from a > fedora 23 system and enabled the service (systemctl enable > display-manager.service). Started the service (systemctl start > display-manager.service) and poof the graphical kde login manager and > desktop returned. > > Should this get posted as a bug or is the kde login manager expected > to disappear with wayland? > -- > users mailing list > users(a)lists.fedoraproject.org > To unsubscribe or change subscription options: > https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org > Fedora Code of Conduct:http://fedoraproject.org/code-of-conduct > Guidelines:http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away:http://ask.fedoraproject.org It's now the sddm.service. I had the same problem. We all need the usual "dnf install sddm, systemctl enable sddm; systemctl start sddm." After I looked at a display-manager.service instance on one of my remaining F23 systems I remembered that sddm was on the way: [me@rigel ~]$ cat /etc/systemd/system/display-manager.service [Unit] Description=Simple Desktop Display Manager Documentation=man:sddm(1) man:sddm.conf(5) Conflicts=getty(a)tty1.service After=systemd-user-sessions.servicegetty(a)tty1.service plymouth-quit.service [Service] ExecStart=/usr/bin/sddm Restart=always #PrivateTmp=yes [Install] Alias=display-manager.service It worked for me but that doesn't mean it solves the problem for everyone. -- Mark C. Allman -- Founder, See How You Ski,www.seehowyouski.com -- Sr. Project Manager, Allman Professional Consulting,www.allmanpc.com -- Twitter: @allmanpc Mr Allman, Thanks for the reply. I did not have sddm installed, I did have kdm (but without a link to display-manager). I can use sddm if that is going to be the future, but I still prefer kdm - and with some advice from this list I can correctly use either one. Regards, ---d.dembrow

1 0

Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
by David Dembrow 26 Jun '16

26 Jun '16

Date: Sun, 26 Jun 2016 22:37:30 +0800 From: Ed Greshko<ed.greshko(a)greshko.com> Subject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23 To:users@lists.fedoraproject.org Message-ID:<e943f66d-26d3-3eef-ce4d-58ff5806fe3a(a)greshko.com> Content-Type: text/plain; charset=utf-8 On 06/26/16 22:21, David Dembrow wrote: > After completing the fedora 24 upgrade on a fedora 23 system there was no graphical > login and the system appeared to be running in console mode (run level 3). > > I have always used KDE as the display manager and desktop. I noticed a similar problem > posted but none of its recommendations were appropriate for my system. > > I found the graphical.target set as the default (systemctl get-default). Then I noticed > the graphical.target expects to have a display-manager.service but the > display-manager.service file was missing. from the /etc/systemd/system directory. > > I copied the /etc/systemd/system/display-manager.service file from a fedora 23 system > and enabled the service (systemctl enable display-manager.service). Started the service > (systemctl start display-manager.service) and poof the graphical kde login manager and > desktop returned. Well, first of all, /etc/systemd/system/display-manager.service should*not* be a file, but a symbolic link. It should either link to /usr/lib/systemd/system/sddm.service or /usr/lib/systemd/system/kdm.service if you are using kdm. What does "systemctl status display-manager" return? Mr Greshko, Thanks very much for the correction. I did not look for symbolic links and I did not have sddm installed on my system. I did have a kdm.service file and enabling kdm creates the link as expected. I can use sddm if that is going to be the future, but I still prefer kdm - and with some advice from this list I can correctly use either one. The systemctl status display-manager command returns the following (before I added the display-manager.service file): [] display-manager.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) Regards, ---d.dembrow

1 0

No Graphical Login After Fedora 24 Upgrade From Fedora 23
by David Dembrow 26 Jun '16

26 Jun '16

After completing the fedora 24 upgrade on a fedora 23 system there was no graphical login and the system appeared to be running in console mode (run level 3). I have always used KDE as the display manager and desktop. I noticed a similar problem posted but none of its recommendations were appropriate for my system. I found the graphical.target set as the default (systemctl get-default). Then I noticed the graphical.target expects to have a display-manager.service but the display-manager.service file was missing. from the /etc/systemd/system directory. I copied the /etc/systemd/system/display-manager.service file from a fedora 23 system and enabled the service (systemctl enable display-manager.service). Started the service (systemctl start display-manager.service) and poof the graphical kde login manager and desktop returned. Should this get posted as a bug or is the kde login manager expected to disappear with wayland?

4 3

← Newer
1
2
3
4
5
6
7
8
...
13
Older →