Import pxssh failed in Fedora 24 (worked in Fedora 23 and earlier vresions)
Hi all, I ran a python 2 script which works fine for Fedora 23 and earlier, with python-2.7. It stopped to work on Fedoera 24 ; following are details: python Python 2.7.10 (default, Sep 8 2015, 17:20:17) [GCC 5.1.1 20150618 (Red Hat 5.1.1-4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import pexpect >>> import pxssh >>> ... rpm -q python-pexpect python-pexpect-3.1-4.fc23.noarch In fedora 24, I don't have python-pexpect, it seems that python2-pexpect replaced it. But python2-pexpect does include pexpect.py and pxssh.py rpm -ql python2-pexpect | grep pexpect.py /usr/lib/python2.7/site-packages/pexpect/fdpexpect.py ... cghost:~$rpm -ql python2-pexpect | grep pxssh.py /usr/lib/python2.7/site-packages/pexpect/pxssh.py However, I get ImportError: No module named pxssh when running the same script: The error is about pxssh; please not that import pexpect succeeded. $> python Python 2.7.11 (default, Jun 21 2016, 09:15:12) [GCC 6.1.1 20160510 (Red Hat 6.1.1-2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import pexpect >>> import pxssh Traceback (most recent call last): File "", line 1, in ImportError: No module named pxssh >>> Any ideas ? Regards, Kevin -- users mailing list users@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
Re: DNF does not actually upgrade
On 06/26/2016 12:42 AM, Samuel Sieb wrote: > On 06/24/2016 08:53 AM, SternData wrote: >> sudo dnf system-upgrade reboot >> >> The system reboots, pauses near the end and says "preparing upgrade. >> this may take a while". After about 3 minutes, it reboots again and I'm >> still in F23. >> >> There's no upgrade option on the boot screen, just the F23 kernels >> > Yes, there's a flag set somewhere that triggers the upgrade process > instead of a normal boot. > > I would recommend that you make sure systemd and dnf are at the latest > versions available on the existing system before trying to upgrade. > > You can check the logs of what happened by doing "dnf system-upgrade log > -1". There was an error relating to "resources". I googled around on that for a while, then gave up and updated like this: dnf --releasever=24 --setopt=deltarpm=false distro-sync --allowerasing -- -- Steve -- users mailing list users@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
Re: Fedora 24 touchpad customization
On Sat, 2016-06-25 at 22:17 -0700, Samuel Sieb wrote: > On 06/24/2016 08:04 PM, Matthew Saltzman wrote: > > It seems that some of the touchpad customization options that were > > available previously have been removed in Fedora 24. In particular, > > two-finger scrolling is enabled by default, but edge scrolling is > > not > > available. Also, tap-to-click is disabled by default. Neither the > > Mouse > > Settings app nor Tweak-Tool have options to change those settings. > > > > Is there a manual way to set those options with dconf-editor or > > some > > other tool? > > > Try "gsettings set org.gnome.desktop.peripherals.touchpad scroll- > method > 'edge-scrolling'". OK, thanks. I checked and the current settings are the ones I want (and presumably set at some point in the past): scroll-method is 'edge- scrolling' and tap-to-click is true, but that's not how the touchpad is behaving. In dconf-editor, there's a comment next to the scroll-method setting that says "No schema found". Also, the lines for scroll-method and tap- to-click are in bold-face type. I guess that means they are not at their default values. Also, there is a setting for edge-scrolling- enabled, and it is set to true. Also, is there someplace all those settings are documented? -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu -- users mailing list users@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
Re: LiveUSB-Creator -
On 06/26/16 04:50, Fernando Cassia wrote: Yes, that looks like it works in an F-24/VM. It did not occur to me that >"Custom OS" would get me back to a familiar process. > Surely a bug of the user, not the software. Surely the UX designers thought it was all very intuitive, and that anyone could detect the options hidden from view using the usual x-ray vision.*sarcasm* ;) FC -- Yes, "words have meaning." Bob -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD box10 FEDORA-23/64bit LINUX XFCE POP3 -- users mailing list users@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
Linphone configuration
Dear users, my name is Pavel Vlček. I am from Czech Republic. I am using screen reader and Fedora 24. I have a small issues with Linphone 3.6.1, can you help? When I want to add my sip account, I fill user name, password and domain, but the Appli button can't be clicked. My question is, do you know, why? I used 3.9.1 Linphone when I used Arch Linux, but 3.9.1 isn't officially in Fedora and some repository which I found has code 500 error. Can someone help please? Thanks, Pavel Vlček -- users mailing list users@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
Re: pcregrep question
On 24Jun2016 10:57, brucewrote: I've got a test file, with the following lines. Basically, I want a grep/regex to traverse the multiple lines to return the lines. ll_=urllib.quote_plus(simplejson.dumps(b2))+"\n" pathchildcount_filep.write(ll_) I've tried a number of attempts.. I thought something similar to the following should work. (but no luck) pcregrep -Mi ".+urllib.quote_plus(simplejson.dumps(b2))(.+\n).+path" foo.py The test file actually has the "\n" chars as text but the regex/grep can ignore it, to focus on getting the two lines.. Had you thought about sed? Untested: sed -n '/^ll_=urllib.quote_plus(simplejson.dumps/,/^pathchildcount_filep.write/p' foo.py (One line, in case your mail read folds it.) I've simplified the regexps, but I'm sure you get the idea. Cheers, Cameron Simpson -- users mailing list users@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
Re: Fedora 24 install fail
On 25/06/16 23:45, Samuel Sieb wrote: On 06/25/2016 08:58 PM, Robin Laing wrote: Trying to install Fedoar 24 to a new machine. System freezes on the install just after and EDAC sbridge, - couldn't find mci handler. It freezes while booting the installer or during the install? -- users mailing list users@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 While booting the live image from USB. I have made some progress since posting. If I go into the troubleshooting and get the basic gui, I can install. Been working with that. Again, points to video and the nVidia Titan X. I get an X error on booting so I am working on it but it is late and I am making mistakes. Robin -- users mailing list users@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
Re: LiveUSB-Creator -
On 06/26/16 01:36, Chris Murphy wrote: I forget the option but there is one to choose a file. Maybe it's custom? Or other? Chris Murphy + Whatever the option, I can't find it. I eventually gave up and burned another dvd. The display is a low contrast horror for me nearly unreadable, contains four options that I can see, none of them permit using a copy of Fedora 24 already downloaded during the early morning hours when my monthly allotmentof bytes is not charged ... The copy F-24 provides appears to be the same as in F-23. Thanks for responding, Bob -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD box10 FEDORA-23/64bit LINUX XFCE POP3 -- users mailing list users@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
Re: LiveUSB-Creator -
> It appears that LiveUSB-creator [aka Fedora Media Writer] no longer > writes to a usb flash stick from data saved to my Fedora23 hard drive > but insists on downloading a copy itself? Or am I missing something? > First open the app as root. Then click on the "Custom OS" option: http://i.imgur.com/lUf6FIG.png And then on "Select live ISO": http://i.imgur.com/Zo9oA86.png Polite as usual, Porfirio. > Bob -- users mailing list users@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
Re: LiveUSB-Creator -
On 06/26/16 04:04, Porfirio Andrés Páiz Carrasco wrote: It appears that LiveUSB-creator [aka Fedora Media Writer] no longer >writes to a usb flash stick from data saved to my Fedora23 hard drive >but insists on downloading a copy itself? Or am I missing something? > First open the app as root. Then click on the "Custom OS" option: http://i.imgur.com/lUf6FIG.png And then on "Select live ISO": http://i.imgur.com/Zo9oA86.png Polite as usual, Porfirio. >Bob -- + Yes, that looks like it works in an F-24/VM. It did not occur to me that "Custom OS" would get me back to a familiar process. Thank you for the help, Bob -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD box10 FEDORA-23/64bit LINUX XFCE POP3 -- users mailing list users@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
Re: LiveUSB-Creator -
On 6/26/16, Bob Goodwinwrote: > Yes, that looks like it works in an F-24/VM. It did not occur to me that > "Custom OS" would get me back to a familiar process. > Surely a bug of the user, not the software. Surely the UX designers thought it was all very intuitive, and that anyone could detect the options hidden from view using the usual x-ray vision. *sarcasm* ;) FC -- users mailing list users@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
rpmbuild error (wbar) on F24
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 -- users mailing list users@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
Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
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? -- You're Welcome Zachary Quinto -- users mailing list users@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
Re: rpmbuild error (wbar) on F24
On Sun, 26 Jun 2016 09:26:29 -0500, Ranjan Maitra wrote: > 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. Revisit the build output and look for a real error message from the compiler, not these that Make prints. -- users mailing list users@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
Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
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@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@tty1.service After=systemd-user-sessions.service getty@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 -- users mailing list users@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
Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
Date: Sun, 26 Jun 2016 11:41:21 -0400 From: "Mark C. Allman"Subject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23 To:users@lists.fedoraproject.org Message-ID:<2f2ce2bd-5601-811c-6024-2aa8da6a7...@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@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@tty1.service After=systemd-user-sessions.servicegetty@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 -- users mailing list users@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
Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
Date: Sun, 26 Jun 2016 22:37:30 +0800 From: Ed GreshkoSubject: Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23 To:users@lists.fedoraproject.org Message-ID: 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 -- users mailing list users@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
Re: pcregrep question
oh.. my bad.. sorry.. here's what I developed to solve my issue in case others need it pcregrep -M 'urllib.quote_plus\(simplejson.dumps\(b2\)\).*\n.*path *Parse_cloud_test.py this allows for searching for content across multiple lines (across a \n newline) On Sun, Jun 26, 2016 at 3:17 AM,wrote: > On 24Jun2016 10:57, bruce wrote: > >> I've got a test file, with the following lines. Basically, I want a >> grep/regex to traverse the multiple lines to return the lines. >> >> ll_=urllib.quote_plus(simplejson.dumps(b2))+"\n" >> pathchildcount_filep.write(ll_) >> >> I've tried a number of attempts.. I thought something similar to the >> following should work. (but no luck) >> >> pcregrep -Mi ".+urllib.quote_plus(simplejson.dumps(b2))(.+\n).+path" >> foo.py >> >> The test file actually has the "\n" chars as text but the regex/grep can >> ignore it, to focus on getting the two lines.. >> > > Had you thought about sed? Untested: > > sed -n > '/^ll_=urllib.quote_plus(simplejson.dumps/,/^pathchildcount_filep.write/p' > foo.py > > (One line, in case your mail read folds it.) > > I've simplified the regexps, but I'm sure you get the idea. > > Cheers, > Cameron Simpson > -- > users mailing list > users@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 > -- users mailing list users@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
Re: compile XV?
ok thanks for the info, I modified my xvpng.c to include zlib.h but wasnt sure which other files to modify. anyway, now I get [jason@badman xv-3.10a]$ make gcc -O3 -Wall -DDOPNG -I/usr/include -I/usr/include -DDOJPEG -I/usr/include -DDOTIFF -DUSE_TILED_TIFF_BOTLEFT_FIX -I/usr/include -DDOPDS -DUSLEEP -DLINUX -L/usr/X11R6/lib -DMGCSFXDIR=\"/usr/X11R6//lib/\" -DSYSCONFDIR=\"/etc\" -DXVEXECPATH=\"/usr/X11R6//lib/\" -c xvpng.c In file included from /usr/include/pngconf.h:50:0, from /usr/include/png.h:371, from xvpng.c:32: xvpng.c: In function ‘WritePNG’: xvpng.c:428:21: error: dereferencing pointer to incomplete type ‘png_struct {aka struct png_struct_def}’ if (setjmp(png_ptr->jmpbuf)) { ^ xvpng.c:454:11: error: dereferencing pointer to incomplete type ‘png_info {aka struct png_info_def}’ info_ptr->width = w; ^~ xvpng.c: In function ‘png_xv_error’: xvpng.c:1055:18: error: dereferencing pointer to incomplete type ‘png_struct {aka struct png_struct_def}’ longjmp(png_ptr->jmpbuf, 1); ^~ Makefile:319: recipe for target 'xvpng.o' failed make: *** [xvpng.o] Error 1 [jason@badman xv-3.10a]$ vi xvpng.c [jason@badman xv-3.10a]$ make gcc -O3 -Wall -DDOPNG -I/usr/include -I/usr/include -DDOJPEG -I/usr/include -DDOTIFF -DUSE_TILED_TIFF_BOTLEFT_FIX -I/usr/include -DDOPDS -DUSLEEP -DLINUX -L/usr/X11R6/lib -DMGCSFXDIR=\"/usr/X11R6//lib/\" -DSYSCONFDIR=\"/etc\" -DXVEXECPATH=\"/usr/X11R6//lib/\" -c xvpng.c In file included from /usr/include/pngconf.h:50:0, from /usr/include/png.h:371, from xvpng.c:32: xvpng.c: In function ‘WritePNG’: xvpng.c:428:21: error: dereferencing pointer to incomplete type ‘png_struct {aka struct png_struct_def}’ if (setjmp(png_ptr->jmpbuf)) { ^ xvpng.c:454:11: error: dereferencing pointer to incomplete type ‘png_info {aka struct png_info_def}’ info_ptr->width = w; ^~ xvpng.c: In function ‘png_xv_error’: xvpng.c:1055:18: error: dereferencing pointer to incomplete type ‘png_struct {aka struct png_struct_def}’ longjmp(png_ptr->jmpbuf, 1); ^~ Makefile:319: recipe for target 'xvpng.o' failed make: *** [xvpng.o] Error 1 [jason@badman xv-3.10a]$ which I guess is making progress.. -db -- users mailing list users@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
No Graphical Login After Fedora 24 Upgrade From Fedora 23
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@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
Re: compile XV?
Allegedly, on or about 25 June 2016, George N. White III sent: > Back when SGI was producing workstations with Trinitron monitors we > had complaints from PC users (probably running Windows for Workgroups) > that colors in images we produced were bad. In fact, every PC was > different. I'm not surprised. PCs had wierd pictures because their monitors were different from everything else that had gone before it, likewise with Macs. They have a different gamma than TV monitors, so people editing video on a computer had a different-looking picture than the end-user. And you had the same issue with printed media (ink or photo). I'd forever be seeing video with the black level pushed up to about 30%, as they'd maladjusted a normal signal to suit their monitor, instead of calibrating their monitor, and adjusting their video using a scope. To be fair, we'd see the same thing with non-computer edited material, for the same reasons. Edited on uncalibrated monitors, and the editor had no real idea about what they should be doing. Real video (TV/DVD) on the LCD computer monitors looks awful, for same reasons (gamma, pale phosphor, mal-adjustment, a different video 0 to 100% range than PCs used, different resolutions with awful scaling, and a different frame rate). Trying to do the wrong with with the wrong monitor just looks bad, and using it as your reference messes it up further for everything else. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. Next time your service provider asks you to reboot your equipment, ask them to reboot theirs, first. -- users mailing list users@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
Re: No Graphical Login After Fedora 24 Upgrade From Fedora 23
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? Neither! Somehow, some way, something disabled your sddm service. I discovered the same problem, after upgrading from F22. (Long story there.) The sddm service runs the graphical login and also selects your network connection, wireless or otherwise. And by the way: /etc/systemd/system/dislay-manager.service shouldn't be a file. It is a symbolic link. I'll pass along these two commands, which come from Garry T. Williams: sudo systemctl --force enable sddm.service sudo systemctl start sddm.service Log in to your console, and then execute these two commands, in succession. Thereafter you should be able to restart and still expect a graphical login. I admit this doesn't answer the question of why this was never a problem until F24. I can guess: another service called kdm took care of this kind of login. But kdm is obsolete with F24. I also think you'll find the new graphical login, especially with KDE, much easier to navigate. You select a user account from among a number of graphical choices. /Then/ you specify your login password. Temlakos -- users mailing list users@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
bluetooth applet
Hi, today I discovered that I can't enable bluetooth via the Blueman Applet. When I click on "Turn Bluetooth On" nothing happend. What might be the reason? I should note that I upgraded the Fedora 23 before I discoverd the problem. --Frank Elsner -- users mailing list users@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
Re: rpmbuild error (wbar) on F24
Michael, Thanks! On Sun, 26 Jun 2016 16:44:39 +0200 Michael Schwendtwrote: > On Sun, 26 Jun 2016 09:26:29 -0500, Ranjan Maitra wrote: > > > 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. > > Revisit the build output and look for a real error message from the > compiler, not these that Make prints. Where is this build output? I get the following complete output when I use: $ rpmbuild -bb wbar.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.vazhVP + umask 022 + cd /home/maitra/rpmbuild/BUILD + cd /home/maitra/rpmbuild/BUILD + rm -rf wbar-2.3.4 + /usr/bin/gzip -dc /home/maitra/rpmbuild/SOURCES/wbar-2.3.4.tgz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd wbar-2.3.4 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.YMyuP9 + umask 022 + cd /home/maitra/rpmbuild/BUILD + cd wbar-2.3.4 + autoreconf -if aclocal: warning: couldn't open directory 'm4': No such file or directory configure.ac:11: installing './compile' src/Makefile.am:18: warning: source file '$(top_srcdir)/src/core/Bar.cc' is in a subdirectory, src/Makefile.am:18: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. src/Makefile.am:18: warning: source file '$(top_srcdir)/src/core/Icon.cc' is in a subdirectory, src/Makefile.am:18: but option 'subdir-objects' is disabled src/Makefile.am:18: warning: source file '$(top_srcdir)/src/core/Main.cc' is in a subdirectory, src/Makefile.am:18: but option 'subdir-objects' is disabled src/Makefile.am:18: warning: source file '$(top_srcdir)/src/core/SuperBar.cc' is in a subdirectory, src/Makefile.am:18: but option 'subdir-objects' is disabled src/Makefile.am:18: warning: source file '$(top_srcdir)/src/core/SuperIcon.cc' is in a subdirectory, src/Makefile.am:18: but option 'subdir-objects' is disabled src/Makefile.am:18: warning: source file '$(top_srcdir)/src/core/XWin.cc' is in a subdirectory, src/Makefile.am:18: but option 'subdir-objects' is disabled src/Makefile.am:43: warning: source file '$(top_srcdir)/src/utils/App.cc' is in a subdirectory, src/Makefile.am:43: but option 'subdir-objects' is disabled src/Makefile.am:43: warning: source file '$(top_srcdir)/src/utils/Config.cc' is in a subdirectory, src/Makefile.am:43: but option 'subdir-objects' is disabled src/Makefile.am:43: warning: source file '$(top_srcdir)/src/utils/Utils.cc' is in a subdirectory, src/Makefile.am:43: but option 'subdir-objects' is disabled src/Makefile.am:43: warning: source file '$(top_srcdir)/src/utils/OptParser.cc' is in a subdirectory, src/Makefile.am:43: but option 'subdir-objects' is disabled src/Makefile.am:34: warning: source file '$(top_srcdir)/src/config/Run.cc' is in a subdirectory, src/Makefile.am:34: but option 'subdir-objects' is disabled src/Makefile.am:34: warning: source file '$(top_srcdir)/src/config/Functions.cc' is in a subdirectory, src/Makefile.am:34: but option 'subdir-objects' is disabled src/Makefile.am:34: warning: source file '$(top_srcdir)/src/config/MainConfig.cc' is in a subdirectory, src/Makefile.am:34: but option 'subdir-objects' is disabled + CFLAGS='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
Re: rpmbuild error (wbar) on F24
On Sun, 26 Jun 2016 12:44:59 -0500, Ranjan Maitra wrote: > > Revisit the build output and look for a real error message from the > > compiler, not these that Make prints. > > Where is this build output? I get the following complete output when I use: Here: > ../src/core/Main.cc:84:35: error: invalid suffix on literal; C++11 requires a > space between literal and string macro [-Werror=literal-suffix] > command = PACKAGE_NAME" "DEFAULT_ARGV; And the line above that is the full invocation of the compiler. -- users mailing list users@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
Re: bluetooth applet [SOLVED]
On Sun, 26 Jun 2016 23:54:47 +0200 Frank Elsnerwrote: > On Sun, 26 Jun 2016 18:15:33 +0200 Frank Elsner wrote: > > Hi, > > > > today I discovered that I can't enable bluetooth via the Blueman Applet. > > When I click on "Turn Bluetooth On" nothing happend. > > > > What might be the reason? > > > > I should note that I upgraded the Fedora 23 before I discoverd > > the problem. > > I've found the solution for broken Blueman Applet: > > After downgrading from blueman-1:2.0.4-2.fc23.i686 >to the previous blueman-2.1-0.3.git7a2e20e.fc23.i686 > > bluetooth is controllable using the applet and works as desired. > Hi Frank, I think that while your solution is workable for you, you may consider filing a bug report so that the updated package can be resolved to work for cases like yours. The F23 package is bound to be obsoleted or upgraded to this new package eventually and so you may want to have that working then when there may not be such a fallback option. Best wishes, Ranjan FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth -- users mailing list users@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
Re: bluetooth applet [SOLVED]
On Sun, 26 Jun 2016 18:15:33 +0200 Frank Elsner wrote: > Hi, > > today I discovered that I can't enable bluetooth via the Blueman Applet. > When I click on "Turn Bluetooth On" nothing happend. > > What might be the reason? > > I should note that I upgraded the Fedora 23 before I discoverd > the problem. I've found the solution for broken Blueman Applet: After downgrading from blueman-1:2.0.4-2.fc23.i686 to the previous blueman-2.1-0.3.git7a2e20e.fc23.i686 bluetooth is controllable using the applet and works as desired. --Frank Elsner -- users mailing list users@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
Re: rpmbuild error (wbar) on F24
Michael, Thanks! > Here: > > > ../src/core/Main.cc:84:35: error: invalid suffix on literal; C++11 requires > > a space between literal and string macro [-Werror=literal-suffix] > > command = PACKAGE_NAME" "DEFAULT_ARGV; > > And the line above that is the full invocation of the compiler. So, how should I fix this? Is this something that has to be taken care of, upstream? Many thanks again! Best wishes, Ranjan Can't remember your password? Do you need a strong and secure password? Use Password manager! It stores your passwords & protects your account. Check it out at http://mysecurelogon.com/manager -- users mailing list users@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
Re: Default IP address for multihomed hosts changed in F24
On Sun, 26 Jun 2016 20:51:11 -0400 Sam Varshavchik wrote: > This host is using masquerading, with firewalld. I suspect that this is > firewalld's doing. Well, if you suspect firewalld, the simplest solution is to mask every service that shows up with firewalld in the name in a: systemctl list-unit-files --full and enable iptable and ip6tables and go back to doing things the old fashioned (and documented :-) way. -- users mailing list users@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
Re: rpmbuild error (wbar) on F24
On Sun, 2016-06-26 at 18:09 -0500, Ranjan Maitra wrote: > > So, how should I fix this? Is this something that has to be taken > care of, upstream? The normal procedure, as a package maintainer, would be for you to fix it by writing a patch, applying the patch to your spec file, and submit the patch for inclusion upstream. ~link signature.asc Description: This is a digitally signed message part -- users mailing list users@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
Default IP address for multihomed hosts changed in F24
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, ":::216.254.115.190", _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, ":::173.194.206.26", _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, ":::216.254.115.190", _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: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. pgp0XLLKc4Rqo.pgp Description: PGP signature -- users mailing list users@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
Re: Default IP address for multihomed hosts changed in F24
Tom Horsley writes: On Sun, 26 Jun 2016 20:51:11 -0400 Sam Varshavchik wrote: > This host is using masquerading, with firewalld. I suspect that this is > firewalld's doing. Well, if you suspect firewalld, the simplest solution is to mask every service that shows up with firewalld in the name in a: systemctl list-unit-files --full and enable iptable and ip6tables and go back to doing things the old fashioned (and documented :-) way. Yeah, yeah, I hear you. The problem is that I'll bet a 100 quatloos is that one fine day, without advance warning, the old-fashioned way will stop working in Fedora proper, and I'll be scrambling to put this Humpty-Dumpty together again. pgpjXJBMvazCL.pgp Description: PGP signature -- users mailing list users@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
Re: Default IP address for multihomed hosts changed in F24
On 06/27/16 08:51, Sam Varshavchik wrote: > 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. Maybe try reordering what is in your /etc/sysconfig/network-scripts/eno2 file? Currently IPADDR=216.254.115.190 is last. Maybe move it, and associated parameters, above IPADDR1? Just a shot in the dark > > 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, > ":::216.254.115.190", _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, > ":::173.194.206.26", _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, > ":::216.254.115.190", _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: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. > > > > > -- > users mailing list > users@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 -- You're Welcome Zachary Quinto signature.asc Description: OpenPGP digital signature -- users mailing list users@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
[389-users] Re: problem running setup ds admin "Error: Could not create directory server instance"
On Thu, 2016-06-23 at 17:24 +0200, Timotheus Pokorra wrote: > Hello Martin, > > > Hostname 'ds389.limbo.local' is valid, but none of the IP addresses > > resolve back to ds389.limbo.local > > - address 10.30.33.10 resolves to host ds389.jalacloud.local > > Error: Could not create directory server instance 'ds389'. > > Exiting . . . > > Log file is '/tmp/setupyR6ywt.log' > > > > where ds389 is the hostname, and limbo.local the domain > > Try to add to your /etc/hosts file: > 10.30.33.10 ds389.limbo.local ds389.jalacloud.local > > I think the keyword to search for on the internet is: fully qualified > domain name > To expand on this, you are likely missing, or have misconfigured the following dns record: I0> host 10.30.33.10 Host 10.33.30.10.in-addr.arpa. not found: 3(NXDOMAIN) You can add 10.33.30.10.in-addr.arpa to your reverse DNS zone if avaliable. Something like: $ORIGIN 33.30.10.in-addr.arpa 10 IN PTR ds389.limbo.local OR you can change your DS setup to use ds389.jalacloud.local. By editing the hosts file, you may now have a scenario where: * To the ldap server 10.33.30.10.in-addr.arpa. is now ds389.limbo.local via localhost in the hosts file * To all other systems 10.33.30.10.in-addr.arpa is ds389.jalacloud.local from DNS. Saying this, to LDAP the proper function of the reverse DNS is not very important. -- Sincerely, William Brown Software Engineer Red Hat, Brisbane signature.asc Description: This is a digitally signed message part -- 389-users mailing list 389-users@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org
[389-users] Re: How can I restrict bind operation based on attributes?
On Tue, 2016-06-21 at 10:46 +, kash...@arissystem.com wrote: > I have three applications that use my ldap installation to authenticate users > with Bind operation. I need to restrict each app so it only be able to bind > it's own users. my idea was to create a multi-value attribute for each user > named "App" which has the name of the application that the user is allowed > use (For instance: mail, portal and office). I'm looking for a way to > restrict each application from binding users who do not have that application > in their "App" attribute. for example portal application must only be able to > bind users which have the attribute "App=portal". I was unable to do such > thing using ACI. > Is it possible to implement such restriction? I think this is how I would do it. Lets say we have a user: dn: uid=test1,ou=People,dc=example,dc=com objectClass: top objectClass: account objectClass: simpleSecurityObject objectClass: YourCustomAppSchema userPassword: password uid: test1 application: foo dn: uid=test2,ou=People,dc=example,dc=com objectClass: top objectClass: account objectClass: simpleSecurityObject objectClass: YourCustomAppSchema userPassword: password uid: test2 application: bar Then the application foo, can have in it's user filter: (&(uid=%s)(application=foo)) To this filter, test1 will satisfy, but test2 will not. Conversely, test2 will work for application bar, but not foo. Because of the way most applications work they follow this pattern: * Anonymous bind * User filter with username to find the DN of the object ** new bind with DN of the object if found ** fail if no DN found As a result, this pattern will satisfy your requirements. Check the ldapfilter configuration directive to your applications, it's likely what you want to use. -- Sincerely, William Brown Software Engineer Red Hat, Brisbane signature.asc Description: This is a digitally signed message part -- 389-users mailing list 389-users@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org