Re: Fedora27: Cannot set the default network route
On 3 February 2018 at 22:20, Terry Barnaby wrote: > On 02/02/18 16:40, Bill Shirley wrote: > > You didn't post the command or its output. How can anyone help you? > > What's the output of these two commands? > ip -o -4 addr > ip -o -4 route > > Bill > > ip -o -4 addr > 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever > preferred_lft forever > 2: enp2s0inet 192.168.202.2/24 brd 192.168.202.255 scope global dynamic > enp2s0\ valid_lft 1205223sec preferred_lft 1205223sec > > ip -o -4 route > default via 192.168.202.1 dev enp2s0 proto static metric 100 > 192.168.202.0/24 dev enp2s0 proto kernel scope link src 192.168.202.2 metric > 100 > > These are when the route is up normally after a DHCP. > The system is fine normally, its just that I wanted to manually change the > default route to test a different router. > I have managed to do this now by hardcoding the route on the next boot. > I think the issue must be NetworkManager doing something more than it used > to. > Since NetworkManager was?is managing that interface did you try using nmcli conn modify or nmcli con edit to set the route in the connection profile? https://www.hogarthuk.com/?q=node/8 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Which Mysql Packages are Better to use in Fedora 27
On 21 Jan 2018 00:39, "Stephen Morris" wrote: Hi, I need to install mysql for registration with netbeans for its database interfacing processes. Looking for mysql in the repositories I've found community-mysql and mariadb packages, does anyone have any advice as which of those two is the better environment to use, and whether or not the other packages in the repository that provide tools for interfacing to mysql will function with either? The MariaDB package is the "officially supported" MySQL compatible database in Fedora (dnf install mysql will pull in this version) and everything in Fedora is built against the mysql libraries from that package. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: f26 systemd :: how to run tftp.service and disable tftp.socket
On 17 January 2018 at 22:51, Adrian Sevcenco wrote: > Hi! I need to have tftp run by service not by socket (at this moment service > requires and start the socket) but even with a proper (i hope) > override and a masked tftp.socket i get: > Failed to start tftp.service: Unit tftp.socket is masked. > > this is the override > [Thursday 18.01.18 00:43] root@sev : /etc/systemd/system/tftp.service.d $ > cat override.conf > [Unit] > Requires= > > [Service] > ExecStart= > ExecStart=/usr/sbin/in.tftpd -4 -c -L -s /home.hdd/tftpd > StandardInput= > > [Install] > Also= > > i still have the socket as dependency : > [Thursday 18.01.18 00:50] root@sev : /etc/systemd/system/tftp.service.d $ > systemctl --plain list-dependencies tftp.service | head > tftp.service > system.slice > tftp.socket > sysinit.target > cgconfig.service > dev-hugepages.mount > dev-mqueue.mount > dmraid-activation.service > dracut-shutdown.service > kmod-static-nodes.service > Seeing as this is a very unusual request, even to the point prior to systemd tftpd was run under xinetd rather than its own service, I think the first question is why? What problem are you attempting to solve that you think this is the solution? There's good reason for it being a socket based service, even prior to systemd, so it would be useful understanding what you are trying to accomplish as an end goal. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: NetworkManager-wait-online is still utterly, and completely, broken
On 20 Dec 2017 04:54, "Gordon Messmer" wrote: On 12/19/2017 04:46 PM, Sam Varshavchik wrote: > > That's the big picture. And looks like it's completely impossible to do > that, in stock Fedora. > Right now, yes. And that's completely and entirely down to NetworkManager bringing interfaces up in an event-driven fashion, when link is detected. Nothing at all to do with systemd. You're right this has nothing to do with systemd ... and it's honestly a difficult problem to solve within NM without risking a system that fails to boot at all without a network detected online. It is worth looking into how we might improve the nm-online behaviour though. In the meanwhile when there are services that require binding to a specific address and it's possible that address hasn't yet arrived on the system there is a better way to handle it, one which is well tested as it's frequently used with software for high availability such as keepalived ... There is an option when creating a socket called FREEBIND which allows binding too an address not present in the system. This is required to be set during the actual binding of the socket by the application. For applications using a systemd socket this is as simple as setting Freebind=true in the .socket file. For other applications there may be a configuration option or command argument to enable it. Consider filing upstream bugs where you want this possible with an application. For example haproxy has this as optional behaviour IIRC For applications where this is not an option there is a sledgehammer approach at the kernel level to enable this behaviour on all socket binds via the sysctl ip_nonlocal_bind Also consider if you *really need* that specific IP bind as binding to 0.0.0.0 or :: and using firewall rules to allow or prevent access per interface will never face this problem. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: NetworkManager-wait-online is still utterly, and completely, broken
On 19 Dec 2017 07:49, wrote: On Mon, 18 Dec 2017 14:12:55 -0800 Gordon Messmer wrote: > On 12/17/2017 01:17 PM, francis.montag...@inria.fr wrote: >>Dec 17 21:32:59 X systemd[1]: Mounting /data2... >>Dec 17 21:33:19 X mount[996]: mount to NFS server 'Y' failed: Resource temporarily unavailable, retrying >>Dec 17 21:33:19 X systemd[1]: Mounted /data2. > Can you reproduce that condition and then get the output of "systemctl > status NetworkManager-wait-online"? That should confirm that the > ExecStart process does not include the -s flag. Here it is: systemctl status NetworkManager-wait-online . NetworkManager-wait-online.service - Network Manager Wait Online Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; disabled; vendor preset: enabled) Active: active (exited) since Tue 2017-12-19 07:58:05 CET; 4min 12s ago Docs: man:nm-online(1) Process: 743 ExecStart=/usr/bin/nm-online -q --timeout=30 (code=exited, status=0/SUCCESS) Main PID: 743 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/NetworkManager-wait-online.service Dec 19 07:57:58 X systemd[1]: Starting Network Manager Wait Online... Dec 19 07:58:05 X systemd[1]: Started Network Manager Wait Online. but still: journalctl -b -u data2.mount -- Logs begin at Thu 2015-04-09 18:41:55 CEST, end at Tue 2017-12-19 08:01:55 CET. -- Dec 19 07:58:05 X systemd[1]: Mounting /data2... Dec 19 07:58:25 X mount[1036]: mount to NFS server 'Y' failed: Resource temporarily unavailable, retrying Dec 19 07:58:25 X systemd[1]: Mounted /data2. The setup of this server is: eth0static IP declaration with dns servers and gateway eth0.2006 static IP declaration: additionnal vlan interface with the associated port on a cisco switch configured as: switchport trunk native vlan 390 switchport trunk allowed vlan 390,2006 switchport mode trunk switchport nonegotiate storm-control broadcast level 5.00 3.00 no cdp enable /etc/resolv.conf was generated by NetworkManager at the same second indicated by nm-online: stat /etc/resolv.conf File: /etc/resolv.conf Size: 76 Blocks: 8 IO Block: 4096 regular file Device: 806h/2054d Inode: 19924685Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) Access: 2017-12-19 07:58:05.539740447 +0100 Modify: 2017-12-19 07:58:05.437735660 +0100 Change: 2017-12-19 07:58:05.438735707 +0100 Birth: - The 'Y' server is in the eth0 subnet. 'Y' has to be resolved by the DNS. As said before, even pinging the gateway IP succeeds only more than 20s after the routes (as seen by "ip route") are defined. Weird no? Cisco switch and that delay for traffic on a static address? Sounds like symptoms of STP delaying s port from listening to forwarding... Have you looked at disabling on that interface or setting portfast if it's only host facing? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Nextcloud upload restricted to 2MB
I'm looking at the owncloud and nextcloud packages this week to update them. Apologies for this but it was an unexpected result of changes to httpd. The default httpd MPM changed from prefork to event, which disabled mod_php as it's not thread safe. For the incoming update once I've ironed out update issues (a lot to test) I'll be switching the recommended from mod_php to php-fpm whether you are using nginx or httpd. This will allow the default MPM on apache to be event for performance and simplify my upgrade tasks by ensuring both nginx and httpd use a common php-fpm config. This is the config I drop in place for nginx, the same will be used for httpd: https://src.fedoraproject.org/rpms/nextcloud/blob/master/f/nextcloud-php-fpm.conf I'm honestly struggling on time between work and family and Fedora at present ... anyone willing to step up and assist with testing, checking dependencies and so on would be most appreciated. As a work around for the time being on httpd change /etc/httpd/conf.d/00-mpm.conf to use prefork again if you don't want to manually install and configure php-fpm for nextcloud... that will automatically enable mod_php again and get the correct configuration. James On 22 November 2017 at 03:08, Bill Shirley wrote: > I ran into this on Fedora 25. > https://www.spinics.net/linux/fedora/fedora-users/msg479030.html > > I'm not running php-fpm.service. > > Bill > > > On 11/21/2017 7:24 PM, Rick Stevens wrote: >> >> On 11/21/2017 03:27 PM, Samuel Sieb wrote: >>> >>> On 11/21/2017 02:59 PM, Florian Sievert wrote: If I remember correctly, this was the default upload size set by PHP. However, I set in F26 already in /etc/php.in the option and restarted apache. upload_max_filesize = 16G Any idea what this might be/? /Anyone who can confirm that nextcloud is working for him on F27? >>> >>> This might be relevant: >>> >>> https://blog.remirepo.net/post/2017/11/17/Fedora-27-changes-in-http-and-php >>> I don't know what changes that might have regarding configuration. >> >> Essentially, F27 now uses Apache in event (multithreaded) mode rather >> than prefork (single-threaded) mode. PHP itself is multithread safe, but >> some of the libraries that may be used by it are NOT multithread-safe. >> Since mod_php is designed for single-thread use, you can't use it with >> Apache running in either event or worker (also multithreaded) modes. >> >> To get around this, PHP now runs as a separate process (called >> "php-fpm") and Apache talks to it using a mechanism called FastCGI via >> either a UNIX-domain socket or TCP/IP using (typically) localhost:9000. >> Since PHP is a separate process, if you make a change to /etc/php.ini, >> you must restart php-fpm: >> >> $ sudo systemctl restart php-fpm.service >> >> for it to take effect. >> >> Probably more than you wanted to know, but >> -- >> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - >> - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - >> -- >> - The trouble with troubleshooting is that trouble sometimes - >> - shoots back. - >> -- >> ___ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to users-le...@lists.fedoraproject.org > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: hybrid graphics laptop and nouveau
On 2 Nov 2017 12:07 pm, "AV" wrote: On Wed, 2017-11-01 at 11:35 +0000, James Hogarth wrote: > On 31 October 2017 at 17:37, AV wrote: > > Hello, > > > > This concerns an Asus Zenbook with hybrid graphics (Intel/Nvidia). > > > > 1) There are 2 ways to deactivate the nouveau driver: > >by adding 'modprobe.nouveau=0' to the kernel cmd line OR > >by adding 'modprobe.blacklist=nouveau rd.blacklist=nouveau'. > >Which is to be preferred? > > > > 2) I do the above because there is as yet no Nvidia driver that > >gives a hybrid solution like under Windows and the Intel driver > >is more than enough for my needs. > >However when using a solution as described in 1) the Nvidia chip > >will still drain power. Is there anyway to deactivate the chip? > >(short of removing it from the motherboard if possible). > > > > > > If you cannot disable the NV chip in the BIOS/firmware then you have > a > couple of options ... > > By default PRIME *should* be working ... are you certain the NV chip > is powered and drawing power? > > Check /sys/kernel/debug/vgaswitcheroo/switch (just cat it) and see if > the chip is already marked OFF (this requires nouveau to be loaded as > a driver IIRC so remove your blacklist). > > https://www.kernel.org/doc/html/v4.10/gpu/vga-switcheroo.html > > If that already shows it off then you don't need to do anything else > as Intel will be default. > > Alternatively if that's not behaving as expected for you follow the > instructions for the bumblebee implementation: > > https://fedoraproject.org/wiki/Bumblebee Thanks for the reply. I am familiar with the PRIME/switcheroo routines. However I am unable to set the NV chip into the OFF power state, it remains in the DynOff state. And you want to get rid of the nouveau driver as soon as possible because it only has rudimentary support for the NV chip and regularly freezes the laptop. I also don't want to use bumblebee or the NV chip. I am quite comfortable with the integrated Intel graphics and it works without problems. So the best option is to immediately edit the grub cmd line at install and blacklist nouveau and after install make this permanent. So I don't know if the NV chip is drawing power and I was asking if anybody knows of ways to check and control outside of the PRIME/switcheroo caboodle. AV ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org DynOFF indicates the chip is off and not drawing anything that will make any difference. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: hybrid graphics laptop and nouveau
On 31 October 2017 at 17:37, AV wrote: > Hello, > > This concerns an Asus Zenbook with hybrid graphics (Intel/Nvidia). > > 1) There are 2 ways to deactivate the nouveau driver: >by adding 'modprobe.nouveau=0' to the kernel cmd line OR >by adding 'modprobe.blacklist=nouveau rd.blacklist=nouveau'. >Which is to be preferred? > > 2) I do the above because there is as yet no Nvidia driver that >gives a hybrid solution like under Windows and the Intel driver >is more than enough for my needs. >However when using a solution as described in 1) the Nvidia chip >will still drain power. Is there anyway to deactivate the chip? >(short of removing it from the motherboard if possible). > > If you cannot disable the NV chip in the BIOS/firmware then you have a couple of options ... By default PRIME *should* be working ... are you certain the NV chip is powered and drawing power? Check /sys/kernel/debug/vgaswitcheroo/switch (just cat it) and see if the chip is already marked OFF (this requires nouveau to be loaded as a driver IIRC so remove your blacklist). https://www.kernel.org/doc/html/v4.10/gpu/vga-switcheroo.html If that already shows it off then you don't need to do anything else as Intel will be default. Alternatively if that's not behaving as expected for you follow the instructions for the bumblebee implementation: https://fedoraproject.org/wiki/Bumblebee ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Tomcat - different users for different instances?
On 22 Sep 2017 3:57 am, "Bill Shirley" wrote: Have you looked at overriding it in the systemd unit file? I use this for mariadb (/etc/systemd/system/mariadb.service): .include /usr/lib/systemd/system/mariadb.service [Service] #LimitNOFILE=infinity LimitNOFILE=65536 LimitMEMLOCK=infinity Bill On 9/21/2017 6:55 PM, Peter Boy wrote: When Fedora used systemV init you could define a specific user for a specific tomcat instance in /etc/systconfig/tomcat-[myinstance] by adding a line TOMCAT_USER=„mytomcat“. In Fedora 26 with systemd you can define different Tomcat instances but the above mechanism doesn’t work anymore. I checked the starter script and couldn’t identify a way to define an instance specific user. Well, does anybody know how I can achieve this? My issue is: If my instances are all executing as the same user I get sometimes an „Too many open files“ error message and the instance stops executing. In RHEL it helps to define separate users per instance. The other instances were not affected by the broken one. Thanks Peter ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Small side note... don't use .include as it's not recommended and long since deprecated. Use a systemd unit override which is the supported way of handling it. mkdir /etc/systemd/system/mariadb.service.d Pop a .conf file in there with the directives you want to override. If you do 'systemctl edit ' that's how it organises things. Back to the question of the OP ... sounds like you are in the perfect area of requirements for a unit template with each tomcat instance from the template and override User in each to make them different and individually controllable. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Build a network bridge with Fedora
On 21 September 2017 at 14:57, James Hogarth wrote: > > > On 21 September 2017 at 09:08, Cristian Sava wrote: > >> Hi all, >> >> Some of us choose to build Fedora servers (instead of using Centos, for >> vary reasons) with many virtuals, each with different IP. >> Everytime I have to follow these guidelines >> https://fedoramagazine.org/build-network-bridge-fedora/ >> So the question: >> Is there a tool to simply setup a bridge interface? >> >> >> >> > You can do it in the NetworkManager interface ... but I'm not really sure > what exactly you are asking. > > Can you not just script nmcli and call that script to automatically do it > for you each time? > > There's an nmcli ansible module you might be able to construct a playbook > with? > > http://docs.ansible.com/ansible/latest/nmcli_module.html > > Can you be a little more specific with your requirements? If so I'm sure a > more specific and detailed answer can be supplied. > > Oh and just a small follow-up from that old article ... the present version of NetworkManager in EL7 and Fedora do no use special *-slave types and instead the raw device is just associated with the master... whatever that is. See this article for more details: https://www.hogarthuk.com/?q=node/18 If you have an existing connection of "System em1" for instance the quickest way to turn that into a bridge with a device name of br0 is now: nmcli connection add type bridge ifname br0 con-name "System bridge" nmcli connection add type ethernet ifname em1 con-name "System em1" master br0 connection.autoconnect yes That's off the top of my head, and a quick check of my blog, but should be accurate enough to get you going. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Build a network bridge with Fedora
On 21 September 2017 at 09:08, Cristian Sava wrote: > Hi all, > > Some of us choose to build Fedora servers (instead of using Centos, for > vary reasons) with many virtuals, each with different IP. > Everytime I have to follow these guidelines > https://fedoramagazine.org/build-network-bridge-fedora/ > So the question: > Is there a tool to simply setup a bridge interface? > > > > You can do it in the NetworkManager interface ... but I'm not really sure what exactly you are asking. Can you not just script nmcli and call that script to automatically do it for you each time? There's an nmcli ansible module you might be able to construct a playbook with? http://docs.ansible.com/ansible/latest/nmcli_module.html Can you be a little more specific with your requirements? If so I'm sure a more specific and detailed answer can be supplied. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Satellite upstream
On 30 August 2017 at 08:54, Daniel Ståhl < daniel.st...@pensionsmyndigheten.se> wrote: > Hi, > > > > I was just wondering. Are there any plans on having an upstream project > for Redhat Satellite 6? Or even satellite 7? > > > > I mean, if you want to practice and test new features the only real option > I’ve found that you have is putting together the components of 6 or running > spacewalk. But that isn’t what I’m looking for, I think. > > > > Any other related tips would of course be appreciated as well. > > > > > It's not really relevant to Fedora but the upstream Satellite 6 is Katello so if you follow this you'll have an open source Sat 6 server: https://theforeman.org/plugins/katello/index.html There is no Sat 7 yet and won't be for a long while I imagine. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: tcp_wrappers deprecation
On 24 August 2017 at 10:33, Peter Robinson wrote: > > On Tue, 2017-08-15 at 13:58 +0200, Jakub Jelen wrote: > >> Hello Fedora devels and users, > >> > >> more than three years ago, the same topic started discussion if we > >> want > >> this package in Fedora or not and how [1]. The discussion resulted > >> mostly in flames and in the removal of the dependency on tcp_wrappers > >> from systemd. But it was quite agreed that it is considered as a > >> security layer for some users, if they use it correctly, or something > >> that is or should be replaced by firewalls. > >> > >> So can we discuss it now once more without the affiliation to > >> systemd? > >> The fact is that we still do not have any other replacement except > >> firewalls. But do we need one? > >> > >> The complete removal of the package is probably not a wise step, even > >> though we can not find tcp_wrappers in recent SuSE anymore [2]. It is > >> still available in Arch [3] without other tools depending on it. To > >> be > >> fair, Debian [4] is still building tools (for example openssh) with a > >> build-time support for it. > >> > >> My primary concern is OpenSSH, which upstream dropped support for > >> tcp_wrappers three years ago (late 2014) [5] and since then we are > >> maintaining one more downstream patch. But this effort should be > >> coordinated among other components to simplify the transition for > >> users > >> who insist on using it (using tcpd). > >> > >> Removing the dependency will also allow us to trim the default > >> install for few more Kb. > >> > >> If there will be no significant drawbacks, I will progress with > >> filling > >> a system wide change for Fedora 28 and I will pull the maintainers of > >> other tolls using libwrap into the round and discussion. > > > > Hello, > > In Fedora 26, there is over 50 packages using tcp_wrappers as a build- > > time dependency: > > > > > > Since I'm listed twice in there... > > > > With my packages and the situation with build time options I take the > > position of enable as much as possible since our users don't get to pick > > their compilation options. > > > > However tcp_wrappers is a legacy thing that no longer belongs in today's > > world. > > > > I have no objection to a flag day in F28 development and dropping the > build > > option at some point, preferably before the thing that is no longer an > alpha > > ;) ... ie way before beta. > > With F-27 now branched off this can happen in F-28/rawhide now > ___ > > Indeed ... it's a great time to do so ... but let's carry it out under the auspices of a System Wide Change for F28 :) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: tcp_wrappers deprecation
On 18 Aug 2017 4:42 pm, "Jakub Jelen" wrote: On Tue, 2017-08-15 at 13:58 +0200, Jakub Jelen wrote: > Hello Fedora devels and users, > > more than three years ago, the same topic started discussion if we > want > this package in Fedora or not and how [1]. The discussion resulted > mostly in flames and in the removal of the dependency on tcp_wrappers > from systemd. But it was quite agreed that it is considered as a > security layer for some users, if they use it correctly, or something > that is or should be replaced by firewalls. > > So can we discuss it now once more without the affiliation to > systemd? > The fact is that we still do not have any other replacement except > firewalls. But do we need one? > > The complete removal of the package is probably not a wise step, even > though we can not find tcp_wrappers in recent SuSE anymore [2]. It is > still available in Arch [3] without other tools depending on it. To > be > fair, Debian [4] is still building tools (for example openssh) with a > build-time support for it. > > My primary concern is OpenSSH, which upstream dropped support for > tcp_wrappers three years ago (late 2014) [5] and since then we are > maintaining one more downstream patch. But this effort should be > coordinated among other components to simplify the transition for > users > who insist on using it (using tcpd). > > Removing the dependency will also allow us to trim the default > install for few more Kb. > > If there will be no significant drawbacks, I will progress with > filling > a system wide change for Fedora 28 and I will pull the maintainers of > other tolls using libwrap into the round and discussion. Hello, In Fedora 26, there is over 50 packages using tcp_wrappers as a build- time dependency: Since I'm listed twice in there... With my packages and the situation with build time options I take the position of enable as much as possible since our users don't get to pick their compilation options. However tcp_wrappers is a legacy thing that no longer belongs in today's world. I have no objection to a flag day in F28 development and dropping the build option at some point, preferably before the thing that is no longer an alpha ;) ... ie way before beta. As for downstream ... well we're Fedora. If Red Hat want it still in RHEL8 that's up to them and they can maintain the downstream patches in their distro still. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Current docs for /etc/sysconfig/network-scripts/ifcfg-* files
On 19 Apr 2017 2:02 pm, "Tom H" wrote: On Tue, Apr 18, 2017 at 4:37 PM, Sam Varshavchik wrote: > Chris Adams writes: >> >> I think the mostly-canonical listing is >> /usr/share/doc/initscripts/sysconfig.txt > > Great. That's exactly what I was looking for. Should you prefer a document on the web, there's https://github.com/fedora-sysv/initscripts/blob/master/sysconfig.txt Since you should be using NetworkManager at this point it's also worth checking the man page man nm-settings-ifcfg-rh ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Hibernation on F25
On 9 Feb 2017 5:26 pm, "Patrick O'Callaghan" wrote: On Thu, 2017-02-09 at 18:07 +0100, Massimo Canonico wrote: > Hi all, > do you guys were able to hibernate your Fedora 25. > In my previous fedora pm-hibernate worked perfectly but now it seems > much more complicate. > I tried to install this extension for gnome: > https://extensions.gnome.org/extension/755/hibernate-status-button/ > > but probably I have something more to do. > > Any suggestion is more than welcome. pm-suspend and pm-hibernate are deprecated. Now it's done via systemd (isn't everything?). I expect the Gnome extension just calls that but I use KDE so I wouldn't know (the KDE hibernate/suspend does work). See 'man systemd-suspend.service'. One thing to check: you must have enough free space in swap or the hibernation will fail (though suspend should still work). Use 'free' to see how much free space there is and add some more if it's not enough. How do you know how much is enough? It depends on your workload so you basically guess, which is pretty much what you do with swap space anyway. There's also still the outstanding bug where anaconda is not adding the resume= arguement to the kernel args to point at the swap partition so the system can never resume. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: VMware Workstation vs KVM
On 17 Jan 2017 10:44 pm, "Greg Woods" wrote: On Tue, Jan 17, 2017 at 3:23 PM, Rick Stevens wrote: > I really don't care about the performance of Windows. I Up to a point, I don't either. But the performance is so bad under KVM that I cannot even successfully run Windows Update, it takes too long to search for updates and eventually times out (other network-related things work so I know it's not my network connection). This does not happen under VirtualBox. Actually if that's a win7 VM you are doing it's nothing to do with being a VM but rather that the updates process is semi broken from a clean SP1 install. There's so many updates it basically can't handle it. There was a good rant about it along with some workarounds like the rollup package and wsusoffline to mitigate this in /r/sysadmin last month https://www.reddit.com/r/sysadmin/comments/5gy3hx/rant_can_we_talk_about_how_fucked_windows_update/ And on a semi related note for future reference for people looking for the windows virtio drivers the official home from a fedora perspective is here: https://fedoraproject.org/wiki/Windows_Virtio_Drivers There's even a yum repo to make it easier to keep up to date on them. Although the ISO doesn't include the spice agent installer to handle automatic resizing of the resolution when changing the window and clipboard sharing... But it does link to the location for the installer for that ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: %prep and %autosetup: move the unpacked source directory
On 17 Jan 2017 3:49 pm, "arnaud gaboury" wrote:
Here is my working directory at the beginning of build, right after I
downloaded the source with spectool. The root directory of the .zip file is
called "platform-master".
---
[makerpm@thetradinghall rpmbuild]$ ls -al
-rw-rw-r-- 1 makerpm makerpm 31120791 Jan 15 11:52 master.zip
-rw-rw-r-- 1 makerpm makerpm 4325 Jan 17 16:22 mattermost.spec
-
At the begining of my build, I need:
- mkdir src/github.com/mattermost
-unzip the source in src/github.com/mattermost/plateform-master
- cd src/github.com/mattermost/plateform-master to start make.
Here is what I wrote in my .spec file:
%prep
%autosetup -n platform-master
mkdir -p %{_topdir}/src/github.com/mattermost <<< = (here, is it correct
to use %{_topdir} ? )
mv plateform-master %{_topdir}/src/github.com/mattermost/platform
Unfortunately, I have this error:
mv plateform-master /home/makerpm/rpmbuild/src/git
hub.com/mattermost/platform
mv: cannot stat 'plateform-master': No such file or director
Here is what happens when running $fedpkg --dist f25 prep:
-
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.zJOa1Q
+ umask 022
+ cd /home/makerpm/rpmbuild
+ cd /home/makerpm/rpmbuild
+ rm -rf platform-master
+ /usr/bin/unzip -qq /home/makerpm/rpmbuild/master.zip
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd platform-master <<< WHY ??
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ mkdir -p /home/makerpm/rpmbuild/src/github.com/mattermost
+ cd ..
+ mv plateform-master /home/makerpm/rpmbuild/src/git
hub.com/mattermost/platform
mv: cannot stat 'plateform-master': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.zJOa1Q (%prep)
--
It seems I am inside the directory I want to move, platform-master.
Why do I cd this directory? How to avoid it so I am able to move this
directory? Or best, how can I unzip the content of master.zip in src/
github.com/mattermost/platform?
Thank you for help to write these few lines in a clean manner.
Please don't take this as a hostile message in any way but I can't help but
feel your needs don't really align with the intent of this mailing list.
These are not in any way fedora problems.
Given your messages are primarily about packaging the fedora development
list may appear more appropriate, but before you do might I suggest you
take a breather to get some coffee and take a breath of fresh air?
In this specific instance you have made a typo, as simple as that.
To your specific question you really shouldn't be referring to %{_topdir}
ever and I can't help but think your current methodology is suspect
You should probably go revisit some basic rpm guides such as:
https://www.hogarthuk.com/?q=node/11
Follow the minimal templates to learn a little better.
Then if you have trouble include the full spec file when describing the
problem and not just the snippet you think is the issue.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Most system update requires system reboot or session restart
On 29 December 2016 at 18:34, Javier Perez wrote: > I remember reading years back about solutions that allowed Kernel upgrade > without reboot. Ksplice and Kpatch comes to mind. Whatever happened to them? > > The facilities arrived in kernel 4.0 with Red Hat and Suse working together with kpatch and kgraft standardising on common infrastructure for it there (yes Oracle sat out the party with their ksplice). With regards to Fedora specifically the kernel team commented on this at the time. What you need to be aware of is that live patching has many limitations (eg can't change data structures but just how functions operate) do it's targeted at very small and specific bug (security) fixes and can't handle generic kernel upgrades. This is especially important seeing as the Fedora kernel team will rebase to new major revisions of the kernel within the Fedora lifecycle rather than keeping to a specific revision with patches. As a result it's not really worth the time for them to test the rather extensive matrix that would be required should live patching the kernel be supported. Have a read of this: http://jwboyer.livejournal.com/50232.html And yes I know that Oracle permits non-commercial use of ksplice on Fedora ... but given the hesitation by the Fedora kernel team on the tech is it really worth it? Of course this only covers the kernel and not any libraries like glibc which really do need a full system reboot to avoid mixed libraries hanging around. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: how to disable dhcp on a fedora client?
On 22 Dec 2016 7:48 pm, "James Hogarth" wrote: On 22 Dec 2016 6:39 pm, "Rick Stevens" wrote: On 12/22/2016 10:15 AM, Earl Ramirez wrote: > On Wed, 2016-12-21 at 13:10 +0100, François Patte wrote: >> Bonjour, >> >> I want to set a static IP adress for a laptop on my local network. So >> I >> wrote a file >> >> /etc/sysconfig/network-scripts/ifcfg-wlp3s0 > > I believe that you will have to modify the file for your local SSID and > not create the file, e.g. if your SSID is my_wifi you will have to > edit /etc/sysconfig/network-scripts/ifcfg-my_wifi and use the settings > below. > >> >> like this: >> >> DEVICE=wlp3s0 >> HWADDR=c4:d9:87:a6:67:33 >> TYPE=Wireless >> BOOTPROTO=none >> ONBOOT=yes >> USERCTL=yes >> >> IPADDR=192.168.1.29 >> GATEWAY=192.168.1.1 >> NETMASK=255.255.255.0 >> >> MODE=Managed >> ESSID=Meenakshi >> >> DNS1=192.168.1.1 That will only work if he disables NetworkManager (NM) and enables netscripts (e.g. "network.service") in its place. NM doesn't use those scripts and you either use NM or netscripts--not both. They don't play nicely with each other. NM does indeed use the ifcfg files in network-scripts and wi-fi is handled much better through NM than network.service shell scripts so this advice is not that useful. Back to the OP's issue it is indeed BOOTPROTO none required to disable dhcp. I'm curious if he reloaded NM after changing this. A better way overall is to use nmcli to change it at the terminal. >From my notes here: https://www.hogarthuk.com/?q=node/8 nmcli conection modify connection.autoconnect yes ipv4.method manual ipv4.addr "10.0.0.1/24" ipv4.dns "10.0.1.1, 10.0.1.2" ipv4.gateway 10.0.0.254 Obviously replace the IP addresses and so on as required. This has the benefit as well of changing the current and the persistent configuration at the same time. Oh and also don't mask network.service ... NM and network at this time do work together and network IIRC still sets up lo for instance. They should both be enabled, and if there is an interface for some reason you do want NM to ignore add NM_CONTROLLED=no which will then mark it as unmanaged by NM and the network service will process it via the legacy shell scripts. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: how to disable dhcp on a fedora client?
On 22 Dec 2016 6:39 pm, "Rick Stevens" wrote: On 12/22/2016 10:15 AM, Earl Ramirez wrote: > On Wed, 2016-12-21 at 13:10 +0100, François Patte wrote: >> Bonjour, >> >> I want to set a static IP adress for a laptop on my local network. So >> I >> wrote a file >> >> /etc/sysconfig/network-scripts/ifcfg-wlp3s0 > > I believe that you will have to modify the file for your local SSID and > not create the file, e.g. if your SSID is my_wifi you will have to > edit /etc/sysconfig/network-scripts/ifcfg-my_wifi and use the settings > below. > >> >> like this: >> >> DEVICE=wlp3s0 >> HWADDR=c4:d9:87:a6:67:33 >> TYPE=Wireless >> BOOTPROTO=none >> ONBOOT=yes >> USERCTL=yes >> >> IPADDR=192.168.1.29 >> GATEWAY=192.168.1.1 >> NETMASK=255.255.255.0 >> >> MODE=Managed >> ESSID=Meenakshi >> >> DNS1=192.168.1.1 That will only work if he disables NetworkManager (NM) and enables netscripts (e.g. "network.service") in its place. NM doesn't use those scripts and you either use NM or netscripts--not both. They don't play nicely with each other. NM does indeed use the ifcfg files in network-scripts and wi-fi is handled much better through NM than network.service shell scripts so this advice is not that useful. Back to the OP's issue it is indeed BOOTPROTO none required to disable dhcp. I'm curious if he reloaded NM after changing this. A better way overall is to use nmcli to change it at the terminal. >From my notes here: https://www.hogarthuk.com/?q=node/8 nmcli conection modify connection.autoconnect yes ipv4.method manual ipv4.addr "10.0.0.1/24" ipv4.dns "10.0.1.1, 10.0.1.2" ipv4.gateway 10.0.0.254 Obviously replace the IP addresses and so on as required. This has the benefit as well of changing the current and the persistent configuration at the same time. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Open Office fails after upgrade to F24
On 28 Nov 2016 12:01 pm, "Ed Greshko" wrote: > > > > On 11/28/16 19:11, James Hogarth wrote: > > You're right it is out of scope as Apache OpenOffice has never been in > > Fedora, and given the state of the project I doubt it ever will be. > > Yes, but I've never been too much of a fan of telling people what they should and > shouldn't run. And I like a challenge from time to time when the list isn't that busy. :-) > > FWIW, I was able to access the Apache BZ and fixed the crash I was having by installing > gdk-pixbuf2-xlib. And OpenOffice works just fine. > "Just fine" ... If you ignore all the AOO problems indeed... An important thing to be aware of is that they build the Linux binaries on CentOS 5 which will have a range of poor behavioural issues due to being built against ancient glibc and gcc versions etc. Generally I agree on the whole "don't tell someone what they should or shouldn't run" mantra but specifically in the AOO situation given the very poor attitude to security issues, almost complete standstill of development, that it is a subset of LO (all AOO commits, as few and far between add they are, get evaluated for inclusion in LO) etc etc I deem it required to ensure people are properly informed about its near-dead status and the potential for security issues (and general exaggerated bugginess due to lack of activity) ... If he continues to want to use a project that is in such a dire state then so be it, but LO is the supported fork of the old Oo.org code for a reason. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Open Office fails after upgrade to F24
On 28 November 2016 at 07:26, Ed Greshko wrote: > > > On 11/28/16 14:42, Ed Greshko wrote: >> Ooops... Forget this last try I was on an F25 VM. >> >> Going to do same on F24. >> >> Wait a bit > > Well the core dump was the same in F24 as F25. > > I have found this > https://community.spiceworks.com/topic/1808558-openoffice-4-1-2-4-1-3-crashed-on-fedora-24 > > But can't connect to the bugzilla system to see what > https://bz.apache.org/ooo/show_bug.cgi?id=124948 has to say. > > This is probably out of scope for Fedora. So, not sure if I'll try and track > it down. > > You're right it is out of scope as Apache OpenOffice has never been in Fedora, and given the state of the project I doubt it ever will be. OP for your own sanity and security stop using AOO. The recent 4.1.3 release fixed a single arbitrary code execution bug that they were notified of in October last year (shortly after the 4.1.2 bugfix release in August 2015) and it's taken them over a year to get a release out for a arbitrary code execution security issue (note this particular issue was found and fixed in LibreOffice over 2 years ago). The project is only hanging on through sheer stubbornness of half a doze individuals and development is at a standstill, with the few people active on the development mailing lists frequently failing to even be able to build the source code. There really is no point or use in using Apache OpenOffice at this point (and hasn't been for a year now). Do you have the same problems opening LO in your system? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: SELinux forces Fedora 25 upgrade into a reboot loop
On 25 November 2016 at 16:08, Sam Varshavchik wrote:
> With selinux set to enforcing, my system-upgrade to 25 failed to start,
> resulting in a reboot loop. I fished the following out of journalctl:
>
> Nov 25 09:51:55 thinkpenguin.email-scan.com audit[1]: AVC avc: denied {
> open } for pid=1 comm="systemd"
> path="/var/lib/dnf/system-upgrade/.dnf-system-upgrade" dev="dm-1"
> ino=1181602 scontext=system_u:system_r:init_t:s0
>
> I had to drop to an emergency shell, and set selinux to permissive, in order
> for the upgrade to do its thing.
>
> Wondering if all upgrades with selinux enabled are broken, or just something
> with this particular laptop. This doesn't look like a system-specific
> failure to me, but if all upgrades with enforcing selinux blow up like this,
> I would've expected a lot of noise in here, by now… More details in bug
> 1398696.
>
>
For what it's worth my systems are always Enforcing ... two laptops
upgraded (one in beta and one in RC) with no problem and a headless
server at release with no problem
There must be something off with your setup somehow
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedpkg: build error No build ID
On 4 November 2016 at 08:34, arnaud gaboury wrote:
>
>
> On Fri, Nov 4, 2016 at 9:19 AM arnaud gaboury
> wrote:
>>
>> I am writing a spec file to build an app.
>> The build failed with this error:
>>
>> *** ERROR: No build ID note found in
>> /home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/share/webapps/mattermost/bin/platform
>>
>> Googling it, I found a few "tricks" which I tried but don't work:
>> - Adding "LDFLAGS+=--build-id"
>> - adding %global _missing_build_ids_terminate_build 0
>>
>> What can I do to solve this issue ?
>
>
> Not sure it is a good idea, but adding this :
> %define debug_package %{nil}
>
> removed the error and package builds fine.
> Is this a solution or a dirty trick to avoid ?
>
>
>>
>> Note: the application is written in Go.
>>
>> Thank you for help.
Since it is writtenm in Go you'll probably find it helpful to read
through and attempt to adhere to the draft Go guidelines:
https://fedoraproject.org/wiki/PackagingDrafts/Go
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: /usr/lib & /usr/lib64 & %{_libdir} in .spec files
On 3 November 2016 at 16:49, arnaud gaboury wrote: > > > Where do these macro come from ? Any doc link ? > > Thank you > Read the section about macros here: https://www.hogarthuk.com/?q=node/11 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedpkg --dist f24 local
On 2 November 2016 at 16:37, jd1008 wrote: > > > On 11/02/2016 10:08 AM, stan wrote: >> >> On Wed, 02 Nov 2016 10:00:13 + >> arnaud gaboury wrote: >> >>> I am writing a .spec file to build my own .rpm. >>> Here it is, non completed: >> >> [snip] >> >>> RPM build errors: >>> Empty %files file >>> /home/makerpm/build_package/mattermost/platform-master/debugfiles.list >>> Could not execute local: Non zero exit >>> >>> -- >>> >>> My %files section is indeed empty as I did not finished writing >>> the .spec file. >>> Shall I overcome for now this error and consider my local build test >>> as successful ? >> >> I am not knowledgeable about spec files, but I would say yes. However, >> this question seems more likely to get a good answer on the devel list, >> where all the packagers hang out. > > I was hoping someone would point to an interactive tool for building a .spec > file; or better yet, a gui util. > That would really enable a lot of people, not just the developers. > The templates, macros and Fedora Guidelines documentation do make it a lot cleaner and simpler than it was 5-10 years back though... This was something I wrote about building RPMs that should be applicable - and never forget it's always best to build in mock to ensure a clean build environment https://www.hogarthuk.com/?q=node/11 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: F23 rsnapshot log timestamps funny
On 20 October 2016 at 11:31, Patrick O'Callaghan wrote: > On Thu, 2016-10-20 at 10:13 +0100, Christopher Ross wrote: >> Since yesterday's update of rsnapshot to >> rsnapshot-1.4.2-1.fc23.noarch >> >> The format of the date/time field in the rsnapshot.log has gone funny, >> as per the following examples... >> >> [19/Oct/2016:11:53:42] /usr/bin/rsnapshot daily: completed successfully >> [19/Oct/2016:12:04:15] /usr/bin/rsnapshot hourly: completed successfully >> [2016-10-19T18:08:11] /usr/bin/rsnapshot hourly: completed successfully >> [2016-10-20T00:07:09] /usr/bin/rsnapshot hourly: completed successfully >> [2016-10-20T06:06:31] /usr/bin/rsnapshot hourly: completed successfully >> >> >> Is anyone else seeing this? Is there an easy fix? > > You might want to ask on the rsnapshot list at > https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss > Hi, one of the maintainers here ... This was a change way back in 2012: https://github.com/rsnapshot/rsnapshot/commit/332872aa5 It certainly sounds like potentially a valid RFE to customise the date/log format ... Are you able to open an issue on github to track it? I expect either someone there will be interested to comment at the least, and hopefully maybe get the log format customisable or something. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: auto connect to guest host as simple user (non root)
On 21 Sep 2016 12:56 pm, "Adel ESSAFI" wrote: > > Dear list > I have installed a guest windows xp system on my fedora 24 machine. > > I configured libvirt to run automatically at boot phase and it worked fine > > [etudiant@localhost ~]$ lsmod | grep kvm > kvm_intel 184320 3 > kvm 552960 1 kvm_intel > irqbypass 16384 1 kvm > > I want to know, now, if it is possible to make a non-root user > (etudiant in my case) to connect to the guest VM with no need to set > the root password. > > So far as I recall the default polkit rules for libvirtd allow connections if the user is in the libvirt group. You'll also want to set an environment variable so that the default libvirt connection will be system rather than session. This article I wrote a fair while back should help with configuration of polkit for libvirt https://www.hogarthuk.com/?q=node/2 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Goodbye apt and yum? Ubuntu’s snap apps are coming to distros everywhere
On 15 Jun 2016 22:57, "Patrick O'Callaghan" wrote: > > http://arstechnica.co.uk/information-technology/2016/06/ubuntu-snap-app > s-are-coming-to-distros-everywhere-bye-apt-yum/ > > At first glance this looks really interesting and will be available on > Fedora, though according to the article RedHat haven't yet decided to > support it officially. > > Any thoughts? > > Be careful of the phrase "be available on Fedora" as it's in a COPR which anyone can create and build in. There has been no package review request for snapd and the instructions have you disabling selinux in addition to the Fedora build disabling what containment technology snap has in place (which relies on seccomp and apparmor so is disabled in the Arch AUR build as well). Using snap in a maintainable way (ie being notified of and installing updates) only works with the Ubuntu Store as well, and Canonical have not published any specs much less reference code for custom repositories (the go code actually has the store hard coded, not even config files). As a consequence I'd strongly advise being wary of this and avoiding it for the time being. What you should be aware of though is Flatpak which is a cross distro initiative for contained applications similar to Canonical's Snap. This is in Fedora and Arch official repositories right now, and in Debian experimental and am Ubuntu PPA whilst it's being finalised. This was formally known as xdg-app and had been worked on in an upstream cross distro manner for a number of years now... rather than just being dropped on the world by a single company ;) -- 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: nVidia Optimus support status
On 8 June 2016 at 14:43, Matthew Saltzman wrote: > Apparently, the latest release of Bumblebee has dropped support for the > nouveau driver. Installing the latest primus package from the bumblebee > repo requires removing bumblebee-nouveau and installing bumblebee- > nvidia. I haven't seen an announcement to that effect, but there is a > bug report at the Bumblebee repo suggesting that that's the direction > they are going. > > Is there a good, up to date summary of the state of Optimus support for > Linux and Fedora, both open-source and proprietary? Anyone have in- > depth experience with Dell (Latitude E6430) implementation and a > recommendation for the best way to proceed? > > One point in particular: I have a docking station, but I've never been > able to get video out when docked. Has anyone succeeded in getting that > working? > > > The discussion which lead to that is here: https://github.com/Bumblebee-Project/Bumblebee/issues/773 On my 960m (F24 and 4.6+ kernel required) doing DRI_PRIME=1 ./foo "worked" (as in it used the discrete GPU and performance was moderate) ... it's just limited by the lack of reclocking in the driver for that chipset yet. If using the proprietary NV driver for optimus then you can follow the Bumblebee wiki page fine, but you have to use the managed repo for a recent driver. As to video out when docked, sorry I don't have a docking station to test (much less that specific Dell model). TL;DR: If using nouveau (or modesetting as the direction seems to be going for the FOSS driver) just use PRIME and not bumblebee ... only use bumblebee when using the nv driver. -- 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: ocsinventory-agent
On 7 June 2016 at 09:48, James Hogarth wrote: > > > On 7 June 2016 at 09:05, wrote: > >> Hello, >> I could not find this package : >> ocsinventory-agent-1.1.2.1-1.el6.noarch >> in EPEL repository. >> Thanks for help >> >> > It was retired after it was orphaned for more than 6 weeks: > > > http://pkgs.fedoraproject.org/cgit/rpms/ocsinventory.git/commit/?h=el6&id=da1f419d23f06de92cc34d4128c7c99b61cff8cd > > > > Actually that was the server link ... but the agent was retired at the same time for the same reason http://pkgs.fedoraproject.org/cgit/rpms/ocsinventory-agent.git/commit/?h=el6 -- 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: ocsinventory-agent
On 7 June 2016 at 09:05, wrote: > Hello, > I could not find this package : > ocsinventory-agent-1.1.2.1-1.el6.noarch > in EPEL repository. > Thanks for help > > It was retired after it was orphaned for more than 6 weeks: http://pkgs.fedoraproject.org/cgit/rpms/ocsinventory.git/commit/?h=el6&id=da1f419d23f06de92cc34d4128c7c99b61cff8cd -- 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 23 (4.4.9-300.fc23) ZFS problem after reboot
On 31 May 2016 at 11:42, Maikel van Leeuwen wrote: > Yesterday I upgraded a Fedora server to 4.4.9-300.fc23.x86_64, after the > reboot all my ZFS pools where > gone. After some fiddling and testing I created these set of steps to > solve the problem: > > dnf remove zfs > dnf install zfs > modprobe zfs > zpool import > zpool import -D > zpool import raid1 > zfs mount -a > > Can somebody acknowledge the same problem and is this to be more expected > in the future? > > ZFS version: zfs-0.6.5.7-1.fc23.x86_64 > > > > Enjoy the fun of a DKMS based filesystem ... you really need to ask the zfsonlinux guys about this as Fedora does not ship or support ZFS -- 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 install nodeps option
On 27 May 2016 20:47, "Samuel Sieb" wrote: > > On 05/27/2016 08:07 AM, François Patte wrote: >> >> I would like to install texmaker, but dnf wants to install a full >> texlive I have already installed texlive from CTAN and I don't want >> to have two texlive on may machine. >> >> How can I get rid of dependencies? >> > You can use rpm --nodeps to install it, but then dnf will probably complain at you forever about it. > > Another option is to use "rpmrebuild -ep yourpackage.rpm". (dnf install rpmrebuild) This will give you an editor (probably vi) to edit a recreated spec file. If you remove the problematic Depends lines and save it, it will build you a new rpm file without the dependencies that dnf should let you install. Don't remove all the Depends, just the texlive ones. > Which of course will promptly be reverted the next update leading to eternal dependency hell fights, and would have to be done for every package that has a dependency on a texlive subpackage. Naturally the "correct" answer is not to mix source and package installs on a package based system. Why did you feel a need for CTAN? The best of the bad options are: Grab the texlive srpm and adapt it to your version (do note that the spec for it is hideous). Create an empty meta rpm that has no files contents but provides the texlive stuff so the dependency chain isn't broken and you don't have to custom install edited versions of a bunch of packages. The latter is the best bad option, but there will be no texlive updates and packages that expect a particular version or path may misbehave with your CTAN 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
Re: jre
On 20 May 2016 6:47 p.m., "Patrick Dupre" wrote: > > OK, > > Thank. > > === > Patrick DUPRÉ | | email: pdu...@gmx.com > Laboratoire de Physico-Chimie de l'Atmosphère | | > Université du Littoral-Côte d'Opale | | > Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 > 189A, avenue Maurice Schumann | | 59140 Dunkerque, France > === > > > > Sent: Friday, May 20, 2016 at 7:38 PM > > From: "Rick Stevens" > > To: "Community support for Fedora users" > > Subject: Re: jre > > > > On 05/20/2016 10:21 AM, Patrick Dupre wrote: > > > > > > OK, > > > > > > but it seems that it also needs > > > javaw > > > which is not provided. > > > Is it javawriter ? > > > > I suspect you have a version of your program that's for Windows. javaw > > doesn't exist in Linux--only in Java for Windows. In the Windows world, > > java opens a console window while javaw does not. > > > > You might try doing a symlink and see if it works: > > > > $ sudo ln -s /usr/bin/java /usr/bin/javaw > > > > No guarantees on if that'll, though. > > That's not accurate The javaw stuff is nothing to do with Windows but rather is the Java webstart stuff for running jnlp That's provided by icedtea-web and will use whichever java is configured via alternatives as the system java -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: Fan/sleep/hibernation issues on Dell Optiplex 780 usff fedora 22
On 30 April 2016 at 02:44, Chris Murphy wrote: > On Thu, Apr 28, 2016 at 1:13 AM, James Hogarth > wrote: > > > > On 28 Apr 2016 2:37 a.m., "Chris Murphy" > wrote: > >> > >> 1. > >> Check these for incompatible values. The follow example is based on > >> UEFI with Secure Boot enabled, so hibernation isn't possible with > >> Fedora kernels. > >> [root@f23s ~]# mokutil --sb-state > >> SecureBoot enabled > >> [root@f23s ~]# cat /sys/power/state > >> freeze mem > >> [root@f23s ~]# cat /sys/power/disk > >> [disabled] > >> > >> 2. > >> cat /proc/meminfo > >> > >> MemTotal < 0.98 * SwapFree = true > >> > >> So memory must be 98% or less than swap free, not swap partition size. > >> > >> 3. > >> You're best off using UUID. It needs to be in /etc/fstab > >> UUID=theuuidforswap swap swap 0 0 > >> > >> 4. > >> In /etc/default/grub GRUB_CMDLINE_LINUX="resume=UUID=theuuidofswap" > >> grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg ## for efi systems > >> and just /boot/grub2/grub.cfg for BIOS > >> > > > > Chris I'm pretty sure one of the initial things that came up with that > bug > > is that the systemd hibernate generator didn't work with UUID and the > direct > > path (via devmapper if required) was needed. > > No swap volume UUID definitely works in my case, it resolves it to the > correct major:minor. It just fails validation for some reason. > > My understanding of systemd hibernate generator is it doesn't work > with GPT partition type GUID for Linux swap, which is a fixed UUID, > 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F. And the reason is they think > it's unreliable to just assume that's where the hibernation image is, > using the generic swap GUID rather than an actually unique one for the > specific swap that should have the hibernation image. At least that's > my understanding of the systemd list thread. They did say it would be > reliable to use an attribute setting for the partition, which is part > of the UEFI GPT spec. But parted doesn't support arbitrary attributes > or GUIDs for that matter, so we're kinda stuck, and that solution > doesn't work on MBR partition disks. > > Further, there's still the open question whether it's OK for the > hibernation image to be on an LVM LV. If it should not be on an LVM > LV, then that means a more substantial change to Anaconda to support > it that results in only root fs on LVM, at which point the can of > worms that's opened is, why not just drop LVM from Workstation? I > think without a clear statement from Harold or the LVM folks about > hibernation images on linear LVs, it's questionable whether it's > really correct to add resume=/dev/mapper/fedora-swap for everyone. For > all we know this causes at least as many problems, or even worse it > might be silent problems that don't materialize until later on; where > failure to hibernate/recover is brutal enough the user is going to > quickly figure out it simply doesn't work. > > > > Chris can we keep discussion of the bug itself to the bugzilla entry and not infiltrate a random user support thread? ;) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: Fan/sleep/hibernation issues on Dell Optiplex 780 usff fedora 22
On 28 Apr 2016 2:37 a.m., "Chris Murphy" wrote: > > 1. > Check these for incompatible values. The follow example is based on > UEFI with Secure Boot enabled, so hibernation isn't possible with > Fedora kernels. > [root@f23s ~]# mokutil --sb-state > SecureBoot enabled > [root@f23s ~]# cat /sys/power/state > freeze mem > [root@f23s ~]# cat /sys/power/disk > [disabled] > > 2. > cat /proc/meminfo > > MemTotal < 0.98 * SwapFree = true > > So memory must be 98% or less than swap free, not swap partition size. > > 3. > You're best off using UUID. It needs to be in /etc/fstab > UUID=theuuidforswap swap swap 0 0 > > 4. > In /etc/default/grub GRUB_CMDLINE_LINUX="resume=UUID=theuuidofswap" > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg ## for efi systems > and just /boot/grub2/grub.cfg for BIOS > Chris I'm pretty sure one of the initial things that came up with that bug is that the systemd hibernate generator didn't work with UUID and the direct path (via devmapper if required) was needed. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: Fan/sleep/hibernation issues on Dell Optiplex 780 usff fedora 22
On 27 April 2016 at 14:46, Matt Morgan wrote: > I have F22 on my son's Optiplex 780 ultra-small form factor. We seem to > have a variety of (maybe related) power management issues. > > First, the fan often goes full-speed and starts making lots of noise. > Usually this is when the computer is actually doing more work, like running > Minecraft. Sometimes it happens when watching Youtube videos. Since these > are the two main things he does with the computer, it pretty much always > happens eventually. > > Second, when this happens, and he then suspends the computer, the fan > stays on during suspend. It never quiets down. So I don't think the > computer is suspending properly. > > Third, if I hibernate the computer, the fan shuts off, but the computer > actually shuts down--when he returns from hibernation, he has to log in to > a new session, his apps have all shut down, etc. > > I used to use this computer (several years ago--it was probably F16, maybe > 18) and I don't recall these issues, so I believe they must be fixable. > > I tried installing TLP, not expecting much from it on a desktop, but > figuring it wouldn't hurt, and it didn't appear to change anything. > > Any advice about where to start with this? > > Thanks, > Matt > > Well on the hibernation side resuming from hibernate is currently broken in Fedora (all releases) but fortunately there's a trivial workaround to fix it. https://bugzilla.redhat.com/show_bug.cgi?id=1206936 https://fedoraproject.org/wiki/Common_F24_bugs#Hibernation_doesn.27t_work_from_a_standard_install -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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 - deprecated update cmd
On 20 April 2016 at 17:37, Tom H wrote: > On Wed, Apr 20, 2016 at 6:07 PM, Samuel Sieb wrote: > > On 04/20/2016 09:03 AM, Tom H wrote: > >> > >> "apt-get update" is the same as "yum|dnf makecache" but with yum|dnf > >> you have to remember to use "yum|dnf -C update" (given dnf's new > >> cache behavior, it seems to work from cache without "-C"). > > > > The -C option to both yum and dnf means to only use the cache. If you > > want to force it to not use the cache, then you need to add the > > --refresh option to dnf. > > Sure. But the point of my previous email was that if you run > "makecache", you then want to run with "-C" in order not to refresh > the cache that you've just updated. > No you don't? Unless you're running with almost (or none) no expiry time then it won't have expired so it won't renew it and will happily use the recently created cache. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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 - deprecated update cmd
On 19 Apr 2016 19:58, "Rick Stevens" wrote: > > On 04/19/2016 10:35 AM, Joe Zeff wrote: >> >> On 04/19/2016 01:49 AM, Timothy Murphy wrote: >>> >>> What term will now be used for the passage to Fedora-24? >> >> >> Update. > > > Didn't the rest of this thread say "update" is deprecated in favor of "upgrade"? > > Damn, I wish the developers would leave this alone! "Update" has always > meant "update to the latest release of software on the _current_ OS". > "Upgrade" has always meant "upgrade to the _next_ OS". They're two > entirely different things. But I guess that's too unambiguous for the > developers who insist on obfuscating things and trying to prove they're > smarter than use poor users and sysadmins. That has not been the case on Fedora which instead had used other tools to carry out release upgrades. And actually it's not even that on Debian where update grabs metadata and upgrade actually upgrades packages. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: Libvirt networking question (SOLVED)
On 19 Apr 2016 18:25, "Patrick O'Callaghan" wrote: > > On Tue, 2016-04-19 at 17:50 +0200, Tom H wrote: > > On Tue, Apr 19, 2016 at 5:09 PM, Patrick O'Callaghan > > wrote: > > > > > > On Tue, 2016-04-19 at 15:49 +0200, Tom H wrote: > > > > > > > > > > > > This thread finally explains why you had a virbr0 a few months > > > > ago > > > > that wasn't created by libvirt but was messing up your dnsmasq > > > > setup! > > > You have a good memory :-) > > Sometimes. I can't remember what the resolution was... > > > > But I do remember that didn't really make sense and found it > > frustrating. > > Apparently at the time I changed from NAT to Bridged networking, which > fixed it (don't ask me why). However removing the redundant file seems > to be the way to go. It's now back to NAT. > Ah when using bridges IIRC libvirt doesn't manage it as there's no dnsmasq for it to handle... So the expectation (and normal thing on hypervisor servers) is to create and manage the bridge with the NM/network service and then point the guest at that bridge in the configuration through libvirtd. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: Libvirt networking question (SOLVED)
On 19 April 2016 at 12:22, Patrick O'Callaghan wrote: > On Mon, 2016-04-18 at 12:56 -0700, Samuel Sieb wrote: > > On 04/18/2016 05:19 AM, Patrick O'Callaghan wrote: > > > > > > On Sun, 2016-04-17 at 14:31 +0100, Patrick O'Callaghan wrote: > > > > > > > > I've been occasionally using a Windows 7 VM with the libvirt > > > > system > > > > for > > > > several months now and have had no problems up to now. However > > > > recently > > > > I've been getting error messages from Windows about the network > > > > being > > > > "unknown" and my shared host/guest volume is unavailable. On the > > > > most > > > > recent attempt I see: > > > > > > > > Virtual network 'default': NAT (Inactive) > > > > > > > > as the entry under the Network Source drop-down in Virtual > > > > Machine > > > > Manager's "Show Hardware Details" menu. > > > > > > > > This is most likely PEBKAC but I'd be grateful for a newbie's > > > > guide > > > > to > > > > how this stuff should be set up without straying too far from > > > > defaults. > > > > My goal is pretty simple: a bridged network to get shared folders > > > > with > > > > my Fedora 23 host and Internet client access from the guest. > > > I still have no idea how this happened, but I found the fix here: > > > > > > http://ask.xmodulo.com/network-default-is-not-active.html > > > > > > and it worked. > > > > > Have you tried rebooting since then? Does it still work? I don't > > think > > you should have an ifcfg file for that interface as you don't want > > NetworkManager interacting with it. If everything still works after > > rebooting, then great. Otherwise, try removing that file. > > Good call. It failed again on rebooting. I removed the file and > rebooted again and now it works. > > Is one supposed to know this by magic? I can't be the only one who's > had this problem. I read the Release Notes every time I update the > system and can't recall seeing it anywhere. > > > Note that a standard install has no ifcfg-virbr0 config ... it's handled entirely by libvirt Remove that file entirely and let libvirt handle setting up the NAT interface If something puts it back then put NM_CONTROLLED=no in the file to prevent NM from using it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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 - deprecated update cmd
On 18 April 2016 at 03:07, Chris Murphy wrote: > On Sun, Apr 17, 2016 at 5:04 PM, Jon LaBadie wrote: > > On F22, the manpage for dnf says the update and update-to > > commands are deprecated aliases for upgrade and upgrade-to. > > > > That being the case, shouldn't the update-info and > > check-update commands also be deprecated and have > > corresponding upgrade versions? > > That would be consistent. File a bug? > > I think the vernacular change is questionable, though. For a long time > update means minor, and upgrade means major. And it makes it more > confusing where upgrade vs system-upgrade. So system is what makes it > major and not system is what makes it minor. Uhh? > > But I'm also too lazy to go look at the change to see what the logic > is about. I guess from dnf's standpoint this isn't a meaningful > distinction. > > For now I continue to use update. > > Once upon a time obsoleting was disabled by default and update would only do non-obsoleting packages and upgrade would include obsolete in the dependency resolution. The obsolete was enabled by default rendering the difference between update and upgrade meaningless in default situations - hence the deprecation. Honestly I'm surprised both were carried forward to dnf rather than the deprecated command being dropped at the yum -> dnf boundary. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: cpio Digest mismatch error?
On 6 Apr 2016 22:12, "Tom Horsley" wrote: > > On Wed, 06 Apr 2016 12:55:04 -0700 > Doug H. wrote: > > > So my guess is that there is a digest file that is being checked by > > default in fedora but not checked on centos. > > But I'd really like to know why it says it has a problem. > We use rpmbuild on a fairly old RHEL build system to create > the packages (so the programs will be backward compatible > with older releases) and we've never had a problem before. > > And why is it only complaining about one file? And one > package? (All the rpms I installed were built on the > same build system, and just this one rpm has an install > problem). > > Is the python digest code incompatible with the C code > in rpmbuild in one out of 10,000,000 cases or something? Incidentally this is not the best way round of doing this. Bear in mind the builders run on Fedora.current in koji and yet we build epel5 there fine. Using mock is always the sensible thing to do rather that rpmbuild directly and anything built using that should work on the target system - if not it's a bug and it'd break koji builds too. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: NFS from a VM
On 5 Apr 2016 17:46, "Rick Stevens" wrote: > > On 04/05/2016 08:49 AM, John J. McDonough wrote: >> >> I have a small server that offers a number of directories over NFS. I >> am running a virtual machine on another physical machine. >> >> When I try to mount an NFS directory on the VM, the NFS server refuses, >> claiming a bad port. Successive tries result in different reported >> port numbers. >> >> What is going on? Is there some sort of virtio setting I am missing? >> NFS works fine to the machine hosting the VM, but not to another >> machine. > > > It rather depends on the NFS client implementation. For example, a > normal NFS mount will fail if the client is a Mac because the Mac's > client won't use reserved ports unless you specifically give it an > "-o resvport" option. This is more or less the opposite of Linux (which > uses reserved ports by default). > > My suggestion is to try the mount on the VM clients and try the "-o resvport" option, just in case: > > mount -o resvport,rw nfsserver:/export /mountpoint > > and see what you get. Don't further NFS3 has a bunch of randomly chosen ports that you need to configure or figure out and let through the firewall... NFS3 was hell for that. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/s2-nfs-nfs-firewall-config.html Ensure you are definitely using NFS4 so that you only need TCP/2049 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://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: Major owncloud updates incoming
On 22 Mar 2016 10:47, "James Hogarth" wrote: > > > > On 9 March 2016 at 15:42, James Hogarth wrote: >> >> >> >> On 24 February 2016 at 17:30, James Hogarth wrote: >>> >>> Hi all, >>> >>> We're at the last stages of preparing the first major owncloud update in a while. >>> >>> The current version of owncloud in Fedora is the fairly old stable 8.0 release (presently 8.0.10) which we want to bring back in line with the current owncloud upstream release of 8.2.2. >>> >>> Unfortunately it's not possible to migrate directly from 8.0.x to 8.2.x as upstream only supports jumping in increments with no skipping of major releases. >>> >>> In order for a smooth transition to 8.2.x (and after that 9.0.x when it's released) we'll be releasing 8.1.5 to F23 and F22 within the next couple of weeks. >>> >>> We plan to leave this in updates-testing for a slightly longer period than usual to allow for a wider test base for a major version jump. Please remember your backups prior to the upgrade! >>> >>> Once 8.1.5 is pushed to updates 8.2.2 will be pushed to updates-testing for a similar extended period. It's imperative that the 8.1.5 update is applied before the 8.2.2 update is pushed to updates. >>> >>> If you want to assist in the testing and provide feedback or bug reports please use the usual channels of bodhi and bugzilla - both easily accessible from pkgdb: >>> >>> https://admin.fedoraproject.org/pkgdb/package/rpms/owncloud/ >>> >>> Kind regards, >>> >>> James >> >> Hi all, >> >> Just a quick reminder about the above. >> >> Owncloud 8.1.5 is in the process of going to the Fedora 23 testing repo at the moment (just waiting the push). >> >> Fedora 22 will get a similar updates-testing in the next few days. >> >> In a week or two these will be pushed stable and 8.2.2 will enter updates-testing. >> >> If you're able to provide help in testing (remember backups!) it would be appreciated. >> >> > > Hi Fedora OwnCloud users! > > The request to push 8.1.5 to stable in Fedora 22 and Fedora 23 has been carried out. > > Please ensure you backup, update and test your instance before the next round of updates. > > I'll be pushing 8.2.3 to rawhide, and updates-testing for F24, F23 and F22 once 8.1.5 has been pushed stable. > > Hello again! The 8.2.3 update is in rawhide and updates-testing on the various branches. If you want to test this please ensure your installation is already tested fully working on the 8.1.5 update as that is a prerequisite to the 8.2 update. Please ensure you are updated to a working 8.1.5 before this gets pushed to stable in the next 1-2 weeks (depending on how bodhi comments and karma goes). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: 4.6 kernel timeframe?
On 1 April 2016 at 12:47, Tom Horsley wrote: > When is a fedora release likely to have the 4.6 kernel > (I suspect fedora 25)? > > I saw rumors the nvidia maxwell card firmware will finally > be included in 4.6 and it might finally be possible to > use nouveau with my graphics card, so I'm just wondering when > I might be able to stop fooling with nvidia binary drivers. > > Fedora 24 will have this eventually ... but given the merge window has only just closed give it a chance ;) For now keep an eye on the NoDebug Rawhide kernel repo to grab updates as they appear ... bear in mind again the merge window only just closed so though 4.6.0-rc1 is there right now it's probably not in an entirely great state ... https://fedoraproject.org/wiki/RawhideKernelNodebug Note that the kernel alone is not enough for it - you'll also need the newer unreleased yet mesa 11.2 and linux-firmware https://lists.freedesktop.org/archives/nouveau/2016-March/024483.html -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: devtmpfs on /dev type devtmpfs
On 31 Mar 2016 21:24, "Paul Schroeder" wrote: > > > > On Thu, Mar 31, 2016 at 2:17 PM, James Hogarth wrote: >> >> >> On 31 Mar 2016 19:07, "Matthew Miller" wrote: >> > >> > On Thu, Mar 31, 2016 at 01:00:24PM -0500, Paul Schroeder wrote: >> > > What would be the proper way to disable/prevent the mount from >> > > happening in the subject line? >> > >> > You can boot with devtmpfs.mount=0 -- but I'm not sure what all will >> > break. Probably "booting", to start. >> > >> >> There's quite a bit of context lost due to the OP providing almost no information here compared to the equivalent mail he sent to the CentOS list. >> >> Specifically he wants to run C7 under LXC and not have systemd-udev populating /dev as the setup outside of LXC should handle that. > > Sorry, I didn't mean to cross post. I was just looking for some general information about devtmpfs here since it's not a Fedora issue exactly. The kernel and systemd versions and packaging is important. If you are trying something on CentOS that fails post there, if you are trying something on Fedora that fails post there. There's as much relevance between them with topics like this as if you used the Ubuntu lists. > >> >> The Arch wiki has good documentation on this... >> >> https://wiki.archlinux.org/index.php/Linux_Containers#Systemd_considerations_.28required.29 >> >> OP did you disable or mask the udev services? Also please don't cross post lists. > > Thanks for the link. I did disable the udev services, it didn't make a difference. The mount is still happening. > > Precise language is important, did you disable or mask? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: devtmpfs on /dev type devtmpfs
On 31 Mar 2016 19:07, "Matthew Miller" wrote: > > On Thu, Mar 31, 2016 at 01:00:24PM -0500, Paul Schroeder wrote: > > What would be the proper way to disable/prevent the mount from > > happening in the subject line? > > You can boot with devtmpfs.mount=0 -- but I'm not sure what all will > break. Probably "booting", to start. > There's quite a bit of context lost due to the OP providing almost no information here compared to the equivalent mail he sent to the CentOS list. Specifically he wants to run C7 under LXC and not have systemd-udev populating /dev as the setup outside of LXC should handle that. The Arch wiki has good documentation on this... https://wiki.archlinux.org/index.php/Linux_Containers#Systemd_considerations_.28required.29 OP did you disable or mask the udev services? Also please don't cross post lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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 23 Server: can't startx
On 31 Mar 2016 00:52, "Braden McDaniel" wrote: > > On Wed, 2016-03-30 at 13:21 -0400, Daniel J Walsh wrote: > > > > On 03/30/2016 12:06 PM, Braden McDaniel wrote: > > > I have a fresh, updated install of Fedora 23 Server. After > > > installation, I installed the "Basic Desktop" group. Now, when I try to > > > run startx, it fails with the error: > > > > > > xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) > > > > > > Where should I look to diagnose/resolve this? Could this be related to > > > the fact that my home directories are NFS mounted? (I have set the > > > use_nfs_home_dirs SELinux setting to "on".) > > > > > What AVC's are you seeing? > > > > ausearch -m avc -ts recent > > None, apparently: > > # ausearch -m avc -ts recent > > > (I ran startx again just before doing that, just to be sure.) > Rather than running startx as your user from a tty what is the result of systemctl isolate graphical.target to move to the graphical interface from the multi-user.target ? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Major owncloud updates incoming
On 9 March 2016 at 15:42, James Hogarth wrote: > > > On 24 February 2016 at 17:30, James Hogarth > wrote: > >> Hi all, >> >> We're at the last stages of preparing the first major owncloud update in >> a while. >> >> The current version of owncloud in Fedora is the fairly old stable 8.0 >> release (presently 8.0.10) which we want to bring back in line with the >> current owncloud upstream release of 8.2.2. >> >> Unfortunately it's not possible to migrate directly from 8.0.x to 8.2.x >> as upstream only supports jumping in increments with no skipping of major >> releases. >> >> In order for a smooth transition to 8.2.x (and after that 9.0.x when it's >> released) we'll be releasing 8.1.5 to F23 and F22 within the next couple of >> weeks. >> >> We plan to leave this in updates-testing for a slightly longer period >> than usual to allow for a wider test base for a major version jump. Please >> remember your backups prior to the upgrade! >> >> Once 8.1.5 is pushed to updates 8.2.2 will be pushed to updates-testing >> for a similar extended period. It's imperative that the 8.1.5 update is >> applied before the 8.2.2 update is pushed to updates. >> >> If you want to assist in the testing and provide feedback or bug reports >> please use the usual channels of bodhi and bugzilla - both easily >> accessible from pkgdb: >> >> https://admin.fedoraproject.org/pkgdb/package/rpms/owncloud/ >> >> Kind regards, >> >> James >> > Hi all, > > Just a quick reminder about the above. > > Owncloud 8.1.5 is in the process of going to the Fedora 23 testing repo at > the moment (just waiting the push). > > Fedora 22 will get a similar updates-testing in the next few days. > > In a week or two these will be pushed stable and 8.2.2 will enter > updates-testing. > > If you're able to provide help in testing (remember backups!) it would be > appreciated. > > > Hi Fedora OwnCloud users! The request to push 8.1.5 to stable in Fedora 22 and Fedora 23 has been carried out. Please ensure you backup, update and test your instance before the next round of updates. I'll be pushing 8.2.3 to rawhide, and updates-testing for F24, F23 and F22 once 8.1.5 has been pushed stable. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: init 5 from single user mode fails
On 20 March 2016 at 16:20, jd1008 wrote: > > > On 03/20/2016 10:14 AM, James Hogarth wrote: > > >> >> On 20 March 2016 at 16:08, jd1008 > jd1...@gmail.com>> wrote: >> >> >> >> On 03/19/2016 08:37 PM, g wrote: >> >> >> On 03/19/16 20:52, g wrote: >> >> On 03/19/16 20:38, jd1008 wrote: >> <> >> >> SO how can I debug this, or is this the normal behavior? >> If normal, since which release? >> >> -- >> >> because you booted to level 1, not all that is needed for >> xwindows >> has been loaded. >> >> if you init 3, note list of additional progs that are >> initialize. >> >> after your login, run startx or init 5, depending on which >> state >> you want. >> >> -- >> >> and i just might be incorrect on that recall from 'chemo >> brain' memory >> because i did a quick run thru and did not have problem >> issuing 'init 5' >> or 'startx' as root user at level 1. >> >> as for diff of what is initialized from 'level 1' and 'level >> 3', it >> just may be appear that they appear diff. >> >> my bad. please excuse. >> >> >> Well, I am mostly concerned with finding out the why of it. >> What is NOT BEING DONE or STARTED which prevents going to full >> init level 5? >> >> >> >> So init 1 is synonymous with the rescue target in systemd terms (see man >> systemd.special) >> >> If you look at what is available at that level it does not surprise me >> that startx doesn't work. >> >> Carrying out init 5 is synonymous with systemctl isolate graphical.target >> (the old runlevel 5 translating to the graphical target in systemd terms) >> >> Related to this the old init 3 is roughly equivalent to systemctl isolate >> multi-user.target >> >> I say roughly equal as targets and isolate is far more precise, powerful >> and capable than the old init levels and the symlinks that run to Kill or >> Start services so behaviour from days of yore may differ slightly ... >> >> It would be useful if you are seeing issues transitioning from one target >> to another to get the journal from the attempts to do so. >> >> OK. So, when it happens, you would like the output of journalctl -xb? > There are quite a options to journalctl, > and I am not sure which ones will reveal the info you want. > > Just the last minute or so from the journal when you have an issue ought to assist: journalctl --since "1 minute ago" -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: init 5 from single user mode fails
On 20 March 2016 at 16:08, jd1008 wrote: > > > On 03/19/2016 08:37 PM, g wrote: > >> >> On 03/19/16 20:52, g wrote: >> >>> On 03/19/16 20:38, jd1008 wrote: >>> <> >>> SO how can I debug this, or is this the normal behavior? If normal, since which release? -- >>> >>> because you booted to level 1, not all that is needed for xwindows >>> has been loaded. >>> >>> if you init 3, note list of additional progs that are initialize. >>> >>> after your login, run startx or init 5, depending on which state >>> you want. >>> >>> -- >> >> and i just might be incorrect on that recall from 'chemo brain' memory >> because i did a quick run thru and did not have problem issuing 'init 5' >> or 'startx' as root user at level 1. >> >> as for diff of what is initialized from 'level 1' and 'level 3', it >> just may be appear that they appear diff. >> >> my bad. please excuse. >> >> >> Well, I am mostly concerned with finding out the why of it. > What is NOT BEING DONE or STARTED which prevents going to full init level > 5? > > So init 1 is synonymous with the rescue target in systemd terms (see man systemd.special) If you look at what is available at that level it does not surprise me that startx doesn't work. Carrying out init 5 is synonymous with systemctl isolate graphical.target (the old runlevel 5 translating to the graphical target in systemd terms) Related to this the old init 3 is roughly equivalent to systemctl isolate multi-user.target I say roughly equal as targets and isolate is far more precise, powerful and capable than the old init levels and the symlinks that run to Kill or Start services so behaviour from days of yore may differ slightly ... It would be useful if you are seeing issues transitioning from one target to another to get the journal from the attempts to do so. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: btrfs doesn't support filesystem swap
On 17 Mar 2016 06:10, "Gordon Messmer" wrote: > > On 03/16/2016 05:25 PM, Rick Stevens wrote: >> >> >> Keep in mind that SuSE is not based in the United States and can, if >> they so choose, thumb their noses at US patent and copyright law. > > > SuSE, AFAIK, isn't planning to distribute ZFS. That's Canonical. They're also not based in the US, but they'd probably still be prohibited from commercially distributing any infringing products in the US. So, for example, the Dell developer systems may need a ZFS-free build. > Canonical do have a registered US presence in Canonical Inc though, however how much they keep in it I don't know. Back to the Fedora point Debian and the SFC do agree that a source based distribution, with no redistribution of the resultant compiled binary, would comply with both licences so a DKMS approach is at least valid. However there was only recently a discussion about using DKMS stuff in Fedora and the kernel maintainers were very clear that kernel modules external to the main kernel build are outside of Fedora guidelines for a variety of reasons. So short of a legal challenge to Canonical's plans resulting in a ruling that it is indeed fine to distribute the combined works of the kernel and a CDDL module in compiled form this allowing ZFS to go upstream under CDDL, or Oracle flexing their legal muscles and enacting clause 4.1(?) of CDDL 1.0 to relicense the code to something GPL compatible (and NetApp then not leveraging their WAFL patents), ZFS is not going to be in Fedora or RHEL for the foreseeable future. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: howto setup docker storage on btrfs f23?
On 18 Mar 2016 11:42, "Neal Becker" wrote: > > Neal Becker wrote: > > > My root (and only) FS is btrfs. > > sudo systemctl status docker > > docker.service - Docker Application Container Engine > >Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; > >vendor > > preset: disabled) > >Active: failed (Result: exit-code) since Fri 2016-03-18 07:18:31 EDT; > >18s > > ago > > Docs: http://docs.docker.com > > Process: 19909 ExecStart=/usr/bin/docker daemon $OPTIONS > > $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $INSECURE_REGISTRY > > (code=exited, status=1/FAILURE) > > Main PID: 19909 (code=exited, status=1/FAILURE) > > > > What do I need to start docker on btrfs on f23? > > > > It appears that editing /etc/sysconfig/docker: > OPTIONS='--storage-driver=btrfs --log-driver=journald' > > Has at least let docker start and run 'hello world' > > In addition to the above if you enable updates-testing you can grab the 1.10 builds. With that version you can run with --selinux-enabled when using the btrfs storage driver, rather than needing to make docker permissive/unconfined. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Major owncloud updates incoming
On 14 March 2016 at 12:56, Ranbir wrote: > On Wed, 2016-03-09 at 15:42 +0000, James Hogarth wrote: > > Just a quick reminder about the above. > > > > Owncloud 8.1.5 is in the process of going to the Fedora 23 testing > > repo at the moment (just waiting the push). > > > > Fedora 22 will get a similar updates-testing in the next few days. > > Are these updates going to make it into the epel repo as well? > > - > EPEL7 certainly ... EPEL6 I'm not sure of yet. Currently the oC in EPEL6 is 7.0 so we'd need to fix any dependency issues there to get to 8.0 first and then carry on up the path similar to how we've done with Fedora. I'm really not keen on trying to maintain owncloud80, owncloud81, owncloud82 and owncloud90 packages all in tandem - there's just not enough hours in the day for me to cover more than $latest pretty much. Of course given it's EPEL this will be over an extended period of time with a lot of grace periods between updates to give everyone a chance to move on up. This also takes a backseat currently to just getting Fedora up to the current version - hopefully shaking out any issues in the process to provide a good experience for the EPEL users. Note that if we can't get EPEL6 past 8.0 then it'll need to be retired as the last 7.0.x update has been released upstream but that's a battle for $future_me If you'd like to do some early testing on EPEL7 then ifas/Didier has been taking my patches and sources and building them for EL7 on his COPR: https://copr.fedorainfracloud.org/coprs/ifas/owncloud/ YMMV and insert many other disclaimers here along with a reminder about backups ;) Do remember you cannot just upgrade straight to 8.2 but need to use the 8.1 packages first and ensure your owncloud instance is fully functional and any apps you use are functioning correctly. Bear in mind that in the 8.1 update the Contacts, Calendar and Documents apps were moved out of core and into the store - so these need enabling with external store access. They also need their own update in oC after enabling, and whilst there are updates pending you can't install a new app. Owncloud 8.1.5 is now in both Fedora 23 and Fedora 22 updates-testing and will remain so for another week. Assuming that there are no issues reported in bodhi I plan to push these stable one week Wednesday and then to push the 8.2.X packages into rawhide and updates-testing for F24, F23 and F22. At that time I'll start the EPEL7 process for 8.1.X as well. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Issue with kernel-devel installation.
On 11 March 2016 at 13:53, Erik P. Olsen wrote: > On 2016-03-11 at 07:38:24 Richard Shaw wrote: > > > On Fri, Mar 11, 2016 at 3:28 AM, Erik P. Olsen > > wrote: > > > > > It is not a bug but merely an irritation whenever I update the > > > kernel to the next level kernel-devel is not updated, I have to do > > > it manually when I run into a problem that it is not installed. > > > > > > How can I train dnf to pull in kernel-devel when the kernel is > > > updated? > > > > > > What version of Fedora are you running? I ran into this on F21, but > > F22 has handled this correctly for me. > > I am running F23. Actually I had to upgrade to 4.4.3-300.fc23 this > morning and kernel-devel didn't upgrade allthough I had all previous > kernel-devel versions installed. > > > Note that there is no versioning dependencies between kernel and kernel-devel so if you only dnf upgrade kernel (or dnf upgrade kernel-devel) they will fall out of sync. You need to dnf update kernel kernel-devel together (or not filter the dnf update at all) to keep them in sync. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Major owncloud updates incoming
On 9 March 2016 at 16:16, Patrick O'Callaghan wrote: > On Wed, 2016-03-09 at 15:42 +0000, James Hogarth wrote: > > > https://admin.fedoraproject.org/pkgdb/package/rpms/owncloud/ > > > > > > Kind regards, > > > > > > James > > > > > Hi all, > > > > Just a quick reminder about the above. > > > > Owncloud 8.1.5 is in the process of going to the Fedora 23 testing > > repo at > > the moment (just waiting the push). > > > > Fedora 22 will get a similar updates-testing in the next few days. > > Shouldn't this have been sent to Fedora Test list? > > > Test is focused on the next Fedora release, and with the alpha round the corner rather busy. Given this will affect current Fedora 22 and 23 users in the next couple of weeks, and the nature of the updates, it felt prudent to provide a mail to where more than the small base of #fedora-qa exists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Major owncloud updates incoming
On 24 February 2016 at 17:30, James Hogarth wrote: > Hi all, > > We're at the last stages of preparing the first major owncloud update in a > while. > > The current version of owncloud in Fedora is the fairly old stable 8.0 > release (presently 8.0.10) which we want to bring back in line with the > current owncloud upstream release of 8.2.2. > > Unfortunately it's not possible to migrate directly from 8.0.x to 8.2.x as > upstream only supports jumping in increments with no skipping of major > releases. > > In order for a smooth transition to 8.2.x (and after that 9.0.x when it's > released) we'll be releasing 8.1.5 to F23 and F22 within the next couple of > weeks. > > We plan to leave this in updates-testing for a slightly longer period than > usual to allow for a wider test base for a major version jump. Please > remember your backups prior to the upgrade! > > Once 8.1.5 is pushed to updates 8.2.2 will be pushed to updates-testing > for a similar extended period. It's imperative that the 8.1.5 update is > applied before the 8.2.2 update is pushed to updates. > > If you want to assist in the testing and provide feedback or bug reports > please use the usual channels of bodhi and bugzilla - both easily > accessible from pkgdb: > > https://admin.fedoraproject.org/pkgdb/package/rpms/owncloud/ > > Kind regards, > > James > Hi all, Just a quick reminder about the above. Owncloud 8.1.5 is in the process of going to the Fedora 23 testing repo at the moment (just waiting the push). Fedora 22 will get a similar updates-testing in the next few days. In a week or two these will be pushed stable and 8.2.2 will enter updates-testing. If you're able to provide help in testing (remember backups!) it would be appreciated. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Trying to open ports in firewalld
On 25 February 2016 at 11:48, Timothy Murphy wrote: > Richard Shaw wrote: > > > On Tue, Feb 23, 2016 at 7:31 AM, Timothy Murphy > > wrote: > > > >> I see that I have to open ports 1714-1764, TCP and UDP. > >> I'm running firewalld on the laptop. > >> I give the command "firewall-config" and authenticate. > >> Clicking on zone "internal" I see that kde-connect is ticked. > >> And when I go to Ports I see that ports 1714-1764 are listed, TCP and > >> UDP. And all this remains set if I reboot. > > > > Let's try the simple stuff first... Is your default zone for your network > > connection also "internal"? > > Thank you very much. > That was indeed the issue. > After changing the default zone to "internal" everything works fine. > > I'm still curious about this ... if you look at the underlying iptables rules with iptables -vnL you'll see traffic on localhost is ALLOW before any zone stuff is checked: Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0udp dpt:53 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0tcp dpt:53 0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0udp dpt:67 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0tcp dpt:67 134K 104M ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0ctstate RELATED,ESTABLISHED 5 300 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 679 201K INPUT_direct all -- * * 0.0.0.0/0 0.0.0.0/0 679 201K INPUT_ZONES_SOURCE all -- * * 0.0.0.0/0 0.0.0.0/0 679 201K INPUT_ZONES all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 140 DROP all -- * * 0.0.0.0/0 0.0.0.0/0ctstate INVALID 498 158K REJECT all -- * * 0.0.0.0/0 0.0.0.0/0reject-with icmp-host-prohibited In fact if you firewall-cmd --list-interfaces you'll see that lo is not bound to any zone (which is sensible given the policy above... otherwise it'd be misleading as zone would never be jumped to for it). > But I don't understand the reasoning behind this. > This use of the term "zone" seems to me misleading and bizarre. > I run shorewall on my home server, and there the "zone" > can be "net", "local", etc. > Any changes made to a particular zone come into effect > on restarting shorewall. > It would not make sense in this context to choose a "default zone". > > I've always hated the term "zone" in firewalld - it's very misleading given how it's used elsewhere and the default zones that you can't remove make it worse. I did go into detail on it here though that may help: https://www.hogarthuk.com/?q=node/9 The short of it is the zone name is a label and most of the zones are not in use and will rarely if ever be in use in most installs. You can apply rules to that label (and they will not be persistent unless --permanent is used, in which case runtime won't be affected, or the runtime is persisted with --runtime-to-permanent) and that label can be bound to an interface or to a source network address. In addition NetworkManager can be configured to apply a zone to a connection profile so you could have work always use the 'work' and $cafe use 'public' based on their different connection profiles (based on SSID). The 'default' zone is just the rules used if no other zones have configurations that match that interface or source network. > Incidentally, restarting firewalld does not seem to me to work properly, > as a window comes up asking for authentication. > I don't recall any other service requiring this, > and it would seem to prevent remote restarting. > > > > This is the polkit configuration for it. Again I go into detail on the blog article but the default configuration is that if not root it requests admin credentials to reload (or even view some stuff). Keep in mind the polkit policy for firewall-cmd --reload behaviour is distinct and separate from a systemd polkit policy limiting systemctl to admin users. In terms of remote restarting polkit will only use a GUI prompt if a display is detected, otherwise it'll have a text based authentication interaction.. and again this is only if not root. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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
Major owncloud updates incoming
Hi all, We're at the last stages of preparing the first major owncloud update in a while. The current version of owncloud in Fedora is the fairly old stable 8.0 release (presently 8.0.10) which we want to bring back in line with the current owncloud upstream release of 8.2.2. Unfortunately it's not possible to migrate directly from 8.0.x to 8.2.x as upstream only supports jumping in increments with no skipping of major releases. In order for a smooth transition to 8.2.x (and after that 9.0.x when it's released) we'll be releasing 8.1.5 to F23 and F22 within the next couple of weeks. We plan to leave this in updates-testing for a slightly longer period than usual to allow for a wider test base for a major version jump. Please remember your backups prior to the upgrade! Once 8.1.5 is pushed to updates 8.2.2 will be pushed to updates-testing for a similar extended period. It's imperative that the 8.1.5 update is applied before the 8.2.2 update is pushed to updates. If you want to assist in the testing and provide feedback or bug reports please use the usual channels of bodhi and bugzilla - both easily accessible from pkgdb: https://admin.fedoraproject.org/pkgdb/package/rpms/owncloud/ Kind regards, James -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Trying to open ports in firewalld
On 23 February 2016 at 14:06, fedora wrote: > try to use the public zone, which is the zone normally activ... > > Not on Fedora which uses FedoraWorkstation as the default zone. OP you may want to include in your response for troubleshooting the output of firewall-cmd --list-all-zones Nothing is actually forbidden against localhost so if it is a connection on localhost it should work ... -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: kernel 4.4.2
On 18 February 2016 at 00:10, Rick Stevens wrote: > On 02/17/2016 03:46 PM, William Biggs wrote: > >> How do I upgrade to kernel 4.4.2 in f32 64bit >> > > I think you mean F23. The latest released kernel for F23 is 4.3.5-300. > If you want to run 4.4.2, you'll need to enable the rawhide repo and > install it from there. Don't ask anyone here for help if you do. You'd > be running a weird, hybrid system and I doubt anyone here would be able > to help you. You'd have to ask any kernel-related questions on the > fedora-test list. > > Note that rawhide is now on a 4.5rc6 rather than any 4.4 kernel ... -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: sudo disappears after latest update
On 11 February 2016 at 06:48, Tim wrote: > Allegedly, on or about 10 February 2016, jd1008 sent: > > I am sorry to burst the bubble that was perpetrated by Sun > > Microsystems. I worked at Sun Microsystems as a contractor and talked > > to a very senior developer at Menlo Park. I knew this developer from > > working with him in a previous company. Under my oath never to reveal > > his name, he clued me in that the fictitious "sandbox" was the entire > > system. > > I'd go along with that, I never believed the sandbox thing. After all, > you can upload any file of your choosing through a Java thing in a > website, and it could save a file to anywhere you selected. That's > hardly sandboxed. > > And, if you went through the Java preferences, on those browsers that > gave you an extensive interface. You could select all sorts of breakout > allowances, many of which were preset to allowed. > > Just to bring things back to reality though. The claim was that *javascript* could execute sudo commands and has full access to the system (no sandbox) and that has nothing to do with java applets/applications whatsoever. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: SELINUX and html
On 5 Feb 2016 12:10 a.m., "Dustin Kempter" wrote: > > Here is the file location as well as the output > > [root@pgbadger1 pgbadger2]# pwd > /var/www/html/monitoring/pgbadger2 > > [root@pgbadger1 pgbadger2]# ls -Z > -rwxr-xr-x. apache apache unconfined_u:object_r:var_t:s0 pgbadger2.html > > > >From that I'm guessing you moved it to that spot from elsewhere so it didn't get the correct context. Use restorecon -Rv /var/www to fix it -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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] Re: [Fedora] Re: how to automatically clean /tmp
On 28 January 2016 at 16:19, Walter Cazzola wrote: > > On Thu, 28 Jan 2016, Jon LaBadie wrote: > >>> I still have to rid off of one of these two tmpfs > > >>> tmpfs 1633640 0 1633640 0% /run/user/989 >>> tmpfs 1633640 20 1633620 1% /run/user/526 > > >>> I think I have to keep one of them since it is associated to my id (526) >>> but I can't imagine what the other is for and how to avoid its creation. >>> Googling didn't help much. > > >> Don't remove either one. They are managed by the system. >> They are taking no disk space (unless memory becomes full >> and it will then use swap). They are not even taking >> significant memory. In fact 989 is using 0 memory. >> Why are you so intent on removing things working as >> they should? > > >> Probably user 989 is your login display manager. >> Check who 989 is in /etc/passwd (grep 989 /etc/passwd). >> On my system is it "lightdm". I have a /run/user/966. >> My 966 is "sddm", my display manager. > > > Indeed you are right, this is sddm, I was thinking it was something > related to some other users I dismissed but it seems it is not the case. > > Thanks for the grep suggestion I couldn't image it was something really > in use. > > Incidentally whilst you're in the middle of cleaning up the system you really should move your UID to something over 1000 ... There's a lot of stuff that no longer works as expected with a UID around 500 (have you checked you login.defs recently)? Seeing a display manager with a UID higher than your own ought to be a warning sign ;) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Mate-bluetooth SRPM?
On 20 Jan 2016 19:21, "Fred Smith" wrote: > > Hi! > > I'm looking for a SRPM for mate-bluetooth. I'm told Fedora packages > it, but so far I've not been able to find it despite my mythical > google-fu :). > > Can anyone point me to a location of it? > Looks like it was retired at F20 but the reason was unclear. http://pkgs.fedoraproject.org/cgit/rpms/mate-bluetooth.git/commit/ You may be able to build the last SRPM for it... https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/19/Everything/source/SRPMS/m/mate-bluetooth-1.6.0-1.fc19.src.rpm You could ask the previous co-maintainers why it was retired as they may know https://admin.fedoraproject.org/pkgdb/package/rpms/mate-bluetooth/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: firewalld and source/dest rules?
On 19 Jan 2016 02:19, "Alex" wrote: > > Hi, > > On Mon, Jan 18, 2016 at 2:55 AM, James Hogarth wrote: > > > > On 17 Jan 2016 16:28, "Alex" wrote: > >> > >> Hi, > >> I have a fedora23 system and just starting to learn how firewalld > >> works. None of the documentation really discusses how to add rules > >> from a specific source (the -s option with iptables). > >> > >> Is this not what firewalld was intended to do? > >> > >> How do I restrict access to ssh or dns only from specific remote IP > >> addresses? > >> > > > > Create a zone for that source network and then apply the rules to that. > > > > Have a read of this and see if it helps clear a few things up: > > > > https://www.hogarthuk.com/?q=node/9 > > Okay, that's interesting. So it's possible to apply multiple zones to > a single interface? How would you suggest I structure that? In other > words, create a "ssh" zone where the only service is ssh, then add all > the source addresses that are permitted to ssh to my host to that > zone? > > I'm trying to do the iptables equivalent of: > > -A INPUT -s 192.168.1.0/24,192.168.10.0/24 -p tcp -m state --state NEW > -m tcp --dport 993 -j ACCEPT > -A INPUT -s 192.168.1.0/24,192.168.10.0/24 -p tcp -m state --state NEW > -m tcp --dport 443 -j ACCEPT > > You've provided some great examples at the end, but any guidance on > how to get started with what I've written above would be appreciated. > > Do you know if firewalld works with NetworkManager properly in fc23? > I'm now learning that because I use kvm/qemu for virtual machines, and > apparently must disable NetworkManager still, that I can't also use > firewalld. I learned this from an older article, but I've been having > problems with NetworkManager and bridges and thought it might be > related. > Whatever article that is sounds mostly nonsense. NM works fine with firewalld and with libvirt (kvm) ... And they all work independently of each other too. When doing a network subnet based zone you don't apply it to an interface as it's network based. So you'd create a zone for "finance" or whatever you want to call what defines that subnet. Then you'd add the network source subnet to it so that it gets used. Then you'd apply your rules (such as --add-service https) If you're struggling a bit with NM and bridges I also have an NM article on the site that covers using nmcli for this. Don't forget there is a new iproute2 command for bridges that is very useful at checking their status - bridge link will tell you what links are in the bridge and whether STP results in the link in a listening, blocking or forwarding state. Last week I was talking to someone who was convinced their NM bridge was broken... Then with that we saw it was up and forwarding and the problem lay elsewhere (cabling) ;) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: firewalld and source/dest rules?
On 17 Jan 2016 16:28, "Alex" wrote: > > Hi, > I have a fedora23 system and just starting to learn how firewalld > works. None of the documentation really discusses how to add rules > from a specific source (the -s option with iptables). > > Is this not what firewalld was intended to do? > > How do I restrict access to ssh or dns only from specific remote IP addresses? > Create a zone for that source network and then apply the rules to that. Have a read of this and see if it helps clear a few things up: https://www.hogarthuk.com/?q=node/9 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Unset environment variable when building rpm
On 15 January 2016 at 14:01, arnaud gaboury wrote: > On Fri, Jan 15, 2016 at 12:48 PM, arnaud gaboury > wrote: >> On Fri, Jan 15, 2016 at 12:46 PM, Patrick O'Callaghan >> wrote: >>> On Fri, 2016-01-15 at 11:42 +0100, arnaud gaboury wrote: I need to unset one of my environment variable to successfully build a rpm package. I added this in my .spec file, but apparently it doesn't work: --- if [ -n $R_PROFILE_USER ];then unset R_PROFILE_USER fi What is the correct way to unset for build time a env variable? >>> >>> Why do you need the test? Just unset it directly. >> ok. In case this variable does not exist, will the build stop? >> Anyway to save the variable value, unset and restore at %post ? > > After more tests, best is indeed to modify a binary option using the > alias function. I can't find any entry on this. Adding > alias foo='foo --option' does not work. > > Best plan for reproducible builds is to just use mock - then you get a clean environment and don't have to worry about stuff like this, -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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] - No GUI after install bumblebee on Fedora 23
On 9 Jan 2016 06:00, "Earl Ramirez" wrote: > > > > > > It's the kernel logs in particular (journalctl -k) that are of > > interest to debug the 4.3.3 issues. > > > > > > It's made a huge difference to this system with stability and the > > general feel (far more fluid) on the intel GPU. > > > > > > This doesn't even take into consideration that 4.2.X is now EOL (which > > was no doubt a significant motivation for the kernel maintainers to > > move to 4.3.X now it's had a couple of bugfix releases) so it makes > > sense to get this working for you. > > > > Hello James, > > Thanks for all your help on this one, I have been trying to re-create > the error I saw previously regarding the USB device where the boot will > fail: Below are the last few lines from the screen: > > [ 0.941782] sda: sda1 sda2 sda3 > [ 0.943430] sd 0:0:0:0: [sda] Attached SCSI disk > [ 0.950234] scsi 1:0:0:0: CD-ROM Slimtype DVD A DA8A6SH GAA2 PQ: 0 > ANSI: 5 > [ 0.977414] usb 1-4: new high-speed USB device number 2 using xhci_hcd > > I was able to re-create this error with any kernel arguments; I have > also tried enabling and disabling secure boot, don't think that it would > make any differences but just wanted to rule any any possible things Secure boot won't work with the proprietary nvidia drivers. At least not without substantial effort (generate your own signing key, sign the dkms generated modules with this, get key trusted by uefi) since the kernel modules compiled are unsigned. > that may cause this failure. Unfortunately I cannot provide any of the > output from journalctl -k at this time, will keep trying different > argument until I can load the OS. > If it looks like a USB issue then disconnect all USB devices on starting to see how far it gets. You'll probably want to remove rhgb and quiet from the kernel arguments whilst debugging. > Let me know if you will like me to file a bug for this kernel 4.3.3 that > is giving these error. > Seeing as it's in testing it'd be useful to have a bug filed and this commented on the bohdi kernel update page. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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] - No GUI after install bumblebee on Fedora 23
On 8 January 2016 at 09:27, Earl A Ramirez wrote: > > > On 8 January 2016 at 17:14, James Hogarth wrote: > >> >> On 8 Jan 2016 02:21, "Earl A Ramirez" wrote: >> > >> > >> > >> > On 8 January 2016 at 02:22, James Hogarth >> wrote: >> >> >> >> >> >> On 7 Jan 2016 5:00 p.m., "Earl A Ramirez" >> wrote: >> >> > >> >> > >> >> > >> >> > On 8 January 2016 at 01:15, James Hogarth >> wrote: >> >> >> >> >> >> >> >> >> >> >> >> On 7 January 2016 at 15:11, Earl A Ramirez >> wrote: >> >> >>> >> >> >>> Dear All, >> >> >>> >> >> >>> I have a ASUS laptop with NVIDIA Optimus technology, therefore, I >> used the Fedora documentation [0] to install bumbleeble using the third >> party managed driver to install NVIDIA. After the installation I am no >> longer seeing the NVIDIA when I use 'lspci | grep VGA'; however, when I use >> 'lspci | egrep 'VGA|3D'' I can see the NVIDIA video card. >> >> >>> >> >> >>> $ lspci | grep VGA >> >> >>> 00:02.0 VGA compatible controller: Intel Corporation Device 191b >> (rev 06) >> >> >>> >> >> >>> $ lspci | egrep 'VGA|3D' >> >> >>> 00:02.0 VGA compatible controller: Intel Corporation Device 191b >> (rev 06) >> >> >>> 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX >> 960M] (rev a2) >> >> >>> >> >> >>> Also I no longer see the vgaswitcheroo under /sys/kernel/debug/. >> When I try to boot with the kernel that NVIDIA was build on; the laptop >> locks up just before the GUI and you will hear the fans blowing and the >> only way around it is to power the laptop down. I have tried booting into >> that kernel with different kernel parameters; E.g. nomodeset >> rd.driver.blacklist=nouveau and even i915.preliminary_hw_support=1 and all >> options and combinations fails. >> >> >>> >> >> >>> However when I boot from the kernel that NVIDIA was not compiled >> on I can the the get a display that says "oops something went wrong, please >> try again" and there is an option to log out, I can also switch to another >> virtual console and have full access to the OS. I get the same behaviour >> even if I use nomodeset; however, if I use i915.preliminary_hw_support=1 I >> get the appropriate resolution. >> >> >>> >> >> >>> Can anyone shed some light on how to get the GUI, with bumblebee >> or even the Intel graphic drivers? >> >> >>> >> >> >>> The packages that were installed are: >> >> >>> $ rpm -qa | egrep 'bumblebee|bbswitch|primus|VirtualGL' >> >> >>> primus-1.1.03282015-2.fc23.x86_64 >> >> >>> bumblebee-nvidia-352.63-2.fc23.x86_64 >> >> >>> bbswitch-dkms-0.8.0-2.fc23.x86_64 >> >> >>> bumblebee-nonfree-release-1.2-1.noarch >> >> >>> VirtualGL-2.4-5.fc23.i686 >> >> >>> bumblebee-release-1.2-1.noarch >> >> >>> primus-1.1.03282015-2.fc23.i686 >> >> >>> VirtualGL-2.4-5.fc23.x86_64 >> >> >>> bumblebee-3.2.1-9.fc23.x86_64 >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> Sounds like we practically the same laptop ... >> >> >> >> >> >> This will go a lot easier for you if you install kernel 4.3.3-300 >> from updates-testing as that has the full skylake i915 support (so don't >> do preliminary_hw_support on that). >> >> >> >> >> >> This looks suspicious ... Xorg should not see the NVIDIA driver if >> you've managed to follow the bumblebee instructions correctly: >> >> >> >> >> >> (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so >> >> >> [ 4.334] (II) Module glx: vendor="NVIDIA Corporation" >> >> >> [ 4.334] compiled for 4.0.2, module version = 1.0.0 >> >> >> [ 4.334] Module class: X.Org Server Extension >> >> >> [ 4.335] (II) NVIDIA GLX Module 358.16 Mon Nov 16 18:54:01 >> PST 2015 >> >> >> >>
Re: [Fedora] - No GUI after install bumblebee on Fedora 23
On 8 Jan 2016 02:21, "Earl A Ramirez" wrote: > > > > On 8 January 2016 at 02:22, James Hogarth wrote: >> >> >> On 7 Jan 2016 5:00 p.m., "Earl A Ramirez" wrote: >> > >> > >> > >> > On 8 January 2016 at 01:15, James Hogarth wrote: >> >> >> >> >> >> >> >> On 7 January 2016 at 15:11, Earl A Ramirez wrote: >> >>> >> >>> Dear All, >> >>> >> >>> I have a ASUS laptop with NVIDIA Optimus technology, therefore, I used the Fedora documentation [0] to install bumbleeble using the third party managed driver to install NVIDIA. After the installation I am no longer seeing the NVIDIA when I use 'lspci | grep VGA'; however, when I use 'lspci | egrep 'VGA|3D'' I can see the NVIDIA video card. >> >>> >> >>> $ lspci | grep VGA >> >>> 00:02.0 VGA compatible controller: Intel Corporation Device 191b (rev 06) >> >>> >> >>> $ lspci | egrep 'VGA|3D' >> >>> 00:02.0 VGA compatible controller: Intel Corporation Device 191b (rev 06) >> >>> 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2) >> >>> >> >>> Also I no longer see the vgaswitcheroo under /sys/kernel/debug/. When I try to boot with the kernel that NVIDIA was build on; the laptop locks up just before the GUI and you will hear the fans blowing and the only way around it is to power the laptop down. I have tried booting into that kernel with different kernel parameters; E.g. nomodeset rd.driver.blacklist=nouveau and even i915.preliminary_hw_support=1 and all options and combinations fails. >> >>> >> >>> However when I boot from the kernel that NVIDIA was not compiled on I can the the get a display that says "oops something went wrong, please try again" and there is an option to log out, I can also switch to another virtual console and have full access to the OS. I get the same behaviour even if I use nomodeset; however, if I use i915.preliminary_hw_support=1 I get the appropriate resolution. >> >>> >> >>> Can anyone shed some light on how to get the GUI, with bumblebee or even the Intel graphic drivers? >> >>> >> >>> The packages that were installed are: >> >>> $ rpm -qa | egrep 'bumblebee|bbswitch|primus|VirtualGL' >> >>> primus-1.1.03282015-2.fc23.x86_64 >> >>> bumblebee-nvidia-352.63-2.fc23.x86_64 >> >>> bbswitch-dkms-0.8.0-2.fc23.x86_64 >> >>> bumblebee-nonfree-release-1.2-1.noarch >> >>> VirtualGL-2.4-5.fc23.i686 >> >>> bumblebee-release-1.2-1.noarch >> >>> primus-1.1.03282015-2.fc23.i686 >> >>> VirtualGL-2.4-5.fc23.x86_64 >> >>> bumblebee-3.2.1-9.fc23.x86_64 >> >>> >> >> >> >> >> >> >> >> Sounds like we practically the same laptop ... >> >> >> >> This will go a lot easier for you if you install kernel 4.3.3-300 from updates-testing as that has the full skylake i915 support (so don't do preliminary_hw_support on that). >> >> >> >> This looks suspicious ... Xorg should not see the NVIDIA driver if you've managed to follow the bumblebee instructions correctly: >> >> >> >> (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so >> >> [ 4.334] (II) Module glx: vendor="NVIDIA Corporation" >> >> [ 4.334] compiled for 4.0.2, module version = 1.0.0 >> >> [ 4.334] Module class: X.Org Server Extension >> >> [ 4.335] (II) NVIDIA GLX Module 358.16 Mon Nov 16 18:54:01 PST 2015 >> >> >> >> Compare this to mine where optirun/bumblebee/primus works fine: >> >> >> >> [23.343] (II) LoadModule: "glx" >> >> [23.343] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so >> >> [23.345] (II) Module glx: vendor="X.Org Foundation" >> >> [23.345]compiled for 1.18.0, module version = 1.0.0 >> >> [23.345]ABI class: X.Org Server Extension, version 9.0 >> >> >> >> If the NVIDIA GLX libraries are loaded into xorg it'll trash your intel stuff ... >> >> >> >> Are you sure you didn't install the NVIDIA proprietary drivers (rpmfusion, negativo17 or directly) in some way other than only through the bumblebee non-free repo? >> >> >> >> This is my configuration: >> >> $ rpm -qa | grep -E 'nvidia|
Re: [Fedora] - No GUI after install bumblebee on Fedora 23
On 7 Jan 2016 5:00 p.m., "Earl A Ramirez" wrote: > > > > On 8 January 2016 at 01:15, James Hogarth wrote: >> >> >> >> On 7 January 2016 at 15:11, Earl A Ramirez wrote: >>> >>> Dear All, >>> >>> I have a ASUS laptop with NVIDIA Optimus technology, therefore, I used the Fedora documentation [0] to install bumbleeble using the third party managed driver to install NVIDIA. After the installation I am no longer seeing the NVIDIA when I use 'lspci | grep VGA'; however, when I use 'lspci | egrep 'VGA|3D'' I can see the NVIDIA video card. >>> >>> $ lspci | grep VGA >>> 00:02.0 VGA compatible controller: Intel Corporation Device 191b (rev 06) >>> >>> $ lspci | egrep 'VGA|3D' >>> 00:02.0 VGA compatible controller: Intel Corporation Device 191b (rev 06) >>> 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2) >>> >>> Also I no longer see the vgaswitcheroo under /sys/kernel/debug/. When I try to boot with the kernel that NVIDIA was build on; the laptop locks up just before the GUI and you will hear the fans blowing and the only way around it is to power the laptop down. I have tried booting into that kernel with different kernel parameters; E.g. nomodeset rd.driver.blacklist=nouveau and even i915.preliminary_hw_support=1 and all options and combinations fails. >>> >>> However when I boot from the kernel that NVIDIA was not compiled on I can the the get a display that says "oops something went wrong, please try again" and there is an option to log out, I can also switch to another virtual console and have full access to the OS. I get the same behaviour even if I use nomodeset; however, if I use i915.preliminary_hw_support=1 I get the appropriate resolution. >>> >>> Can anyone shed some light on how to get the GUI, with bumblebee or even the Intel graphic drivers? >>> >>> The packages that were installed are: >>> $ rpm -qa | egrep 'bumblebee|bbswitch|primus|VirtualGL' >>> primus-1.1.03282015-2.fc23.x86_64 >>> bumblebee-nvidia-352.63-2.fc23.x86_64 >>> bbswitch-dkms-0.8.0-2.fc23.x86_64 >>> bumblebee-nonfree-release-1.2-1.noarch >>> VirtualGL-2.4-5.fc23.i686 >>> bumblebee-release-1.2-1.noarch >>> primus-1.1.03282015-2.fc23.i686 >>> VirtualGL-2.4-5.fc23.x86_64 >>> bumblebee-3.2.1-9.fc23.x86_64 >>> >> >> >> >> Sounds like we practically the same laptop ... >> >> This will go a lot easier for you if you install kernel 4.3.3-300 from updates-testing as that has the full skylake i915 support (so don't do preliminary_hw_support on that). >> >> This looks suspicious ... Xorg should not see the NVIDIA driver if you've managed to follow the bumblebee instructions correctly: >> >> (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so >> [ 4.334] (II) Module glx: vendor="NVIDIA Corporation" >> [ 4.334] compiled for 4.0.2, module version = 1.0.0 >> [ 4.334] Module class: X.Org Server Extension >> [ 4.335] (II) NVIDIA GLX Module 358.16 Mon Nov 16 18:54:01 PST 2015 >> >> Compare this to mine where optirun/bumblebee/primus works fine: >> >> [23.343] (II) LoadModule: "glx" >> [23.343] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so >> [23.345] (II) Module glx: vendor="X.Org Foundation" >> [23.345]compiled for 1.18.0, module version = 1.0.0 >> [23.345]ABI class: X.Org Server Extension, version 9.0 >> >> If the NVIDIA GLX libraries are loaded into xorg it'll trash your intel stuff ... >> >> Are you sure you didn't install the NVIDIA proprietary drivers (rpmfusion, negativo17 or directly) in some way other than only through the bumblebee non-free repo? >> >> This is my configuration: >> $ rpm -qa | grep -E 'nvidia|bumblebee|bbswitch|primus|VirtualGL' >> primus-1.1.03282015-2.fc23.i686 >> bumblebee-3.2.1-9.fc23.x86_64 >> VirtualGL-2.4-5.fc23.i686 >> bumblebee-release-1.2-1.noarch >> bumblebee-nvidia-352.63-2.fc23.x86_64 >> VirtualGL-2.4-5.fc23.x86_64 >> bbswitch-dkms-0.8.0-2.fc23.x86_64 >> bumblebee-nonfree-release-1.2-1.noarch >> primus-1.1.03282015-2.fc23.x86_64 >> >> GRUB_CMDLINE_LINUX has in it nouveau.modeset=0 and rd.driver.blacklist=nouveau >> >> Before I updated to 4.3.3 today the preliminary_hw_support=1 was needed as well. >> >> What's the output of bumblebee-nvidia --check for you ? >> >> >> >> >> -- >&g
Re: No sound also with kernel 4.3.3-300
On 7 January 2016 at 11:10, Luigi Votta wrote: > Hello Feodra users, > I've no sound on my (new) system (Skylake 6500, Asus H170-Pro), > updated today to kernel (rebase) 4.3.3-300. > > In dmesg: > [2.606535] snd_hda_intel :00:1f.3: CORB reset timeout#1, > CORBRP=0 > [2.610741] snd_hda_intel :00:1f.3: no codecs found! > > lspci: > 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev > 31) > > Has anybody the same issue? > Did this work on the previous kernel? As this is still in updates-testing and not stable I suggest that you post to fedora-devel with issues and/or comment on the update itself for visibility to the maintainers. https://bodhi.fedoraproject.org/updates/FEDORA-2016-6ce812a1e0 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Windows 10 virtio drivers?
On 12 December 2015 at 15:30, Tom Horsley wrote: > On my fedora 22 box, I have a Windows 7 KVM with virtio > drivers for disk and network and qxl and spice for video. > It works really well, but of course it keeps badgering > me to upgrade to Windows 10. > > Are there virtio drivers available for Windows 10 yet? > The page at https://fedoraproject.org/wiki/Windows_Virtio_Drivers > still talks like Windows XP is likely to be running. > > Is there a guide anywhere for how to get the Windows 10 > update to actually install properly inside a KVM? > (I can find lots of pages describing how it doesn't > work :-). > > Naturally whatever I wind up doing, I'll be saving > a copy of the disk image from Windows 7 so I can > easily revert back. > > Well the page does mention qxldod for win8+ ... Also the changelog refers to win10 in places: https://fedorapeople.org/groups/virt/virtio-win/CHANGELOG I'd be interested in hearing your feedback for how this goes! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: submitted RPMs and awaiting action?
On 1 December 2015 at 14:25, Ranjan Maitra wrote: > On Tue, 1 Dec 2015 14:21:59 +0100 Michael Schwendt > wrote: > > > On Tue, 1 Dec 2015 13:08:29 +, James Hogarth wrote: > > > > > The if you want to proceed take the following steps: > > > 1. Fix up your bugzilla/FAS accounts > > > > Really do enter your real name in bugzilla and package %changelogs, too, > > and avoid using pseudonyms/aliases even if you find them "cool" or > > anything like that. There are enough fellow contributors, who are put > > off by silly names like that. > > The changelog (in the spec file?) and the FAS account has my real name > (and e-mail address, FWIW). My BZ account goes back in time -- I have been > quite active in submitting and testing bug reports for almost ten years -- > so it has a different e-mail address (when more mailing lists plastered > your e-mail address and name unfiltered). I don't quite understand why this > should be an issue, and I note also that BZ makes the e-mail address widely > available to everybody, therefore I was reluctant to change it. I will > think about what to do. > > I pointed you to this: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Have you read it yet? Note that the mailing list bears no relation to the address in FAS ... this is what we are talking about (ignoring the preference for real name over pseudonym in bugzilla). Although adjusting spec as per direction from others you don't appear to be making an effort on the process/people side of things. I laid out clear steps for you to follow - they are not complicated. If you aren't willing to do the modicum amount of work to actually take part in packagers group and seek a sponsor then I'm not willing to take time out of my day to go through fedora-review on your packaging request. Incidentally the 'EOL' notice you're expecting won't happen with a packaging request as that's targeted against rawhide and not a specific fedora revision. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: submitted RPMs and awaiting action?
On 1 December 2015 at 11:53, Ranjan Maitra wrote: > Hi, > > Some time ago, circa May 2015, there was a long thread called "Biting the > Bullet" [1] where some others complained about the lack of pdftk on F21 and > later. (This complaint also manifested itself sometime later.) > > In response, and with both general and more specific help from those more > experienced, I was able to put together an RPM for pdf-stapler as an > alternative to pdftk. I submitted to a black hole called Fedora packaging > where there was some churn, some more suggestions (a few contradicting the > other) which I duly implemented but no one actually able to move the > process forward. However, it sits here: > > https://bugzilla.redhat.com/show_bug.cgi?id=1234210 > > unassigned. It has passed through rpmlint (no errors, only a few > nonsensical spelling warnings) and whatever else it was supposed to pass as > per packaging guidelines. So also is the case of sylfilter which I packaged > separately, and no one has even bothered to comment on: > > https://bugzilla.redhat.com/show_bug.cgi?id=1265685 > > Now, I understand that quality control is an important part of the Fedora > packaging which is what makes it a good product (and I am no great > RPM-maker, witness my questions on the subject), and there is a dearth of > enough people eligible to assign to, but surely, there must be some better > way to handle new proposed packages. For instance, if automated setups > clear a package, perhaps it would be better to move it to the top of the > list or even clear it for testing and see what happens? Otherwise, there > will be frustration and the pool of packagers will not grow. Not to mention > that if packages sit like this this for months before being acted upon, > then the original packager will have lost context and memory and moved on > (certainly it would be frustrating and more onerous on him/her than it > would be if it were acted upon sooner). Otherwise, people will move on. > > I don't need these packages because I have them for myself. Indeed, I > could be more sloppy in creating these rpms (or not even bothering to do > so), but the reason for putting this out is benefit to the community which > has also benefited me/us. This is especially true for niche packages such > as sylfilter, etc which may not even have much users who would be willing > to test it. > > I have some experience with submitting packages for R. My experience there > is that if it passes all the tests, it is by and large through, but if it > does not (surprisingly, Macs are the killers in most cases), it is not, and > feedback is fairly quick. > > Perhaps, it would be worthwhile to think about how to streamline the > process. At this point, I am fully expecting the familiar notice for EOL > eventually. > > Best wishes, > Ranjan > There has been recent discussion on this on the fedora-devel mailing list (which if you want to be a packager you really should join). I'd suggest catching up on this thread: https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/message/JL7BKPIHNMVIL7ZSDCA7WB7NX7KQXF6I/ This was the FESCO ticket involved: https://fedorahosted.org/fesco/ticket/1499 The short version is any current packager can now review your new package rather than only a sponsor, but you still need to find a sponsor as pointed out in comment #6 of your bug, in addition you don't appear to have addressed the issue in comment #16 which will put off anyone getting involved until FAS and bugzilla line up at the least. As for your other package review request I'd suggest that given the state of the first no one feels like diving into the second - for instance on the second you have not blocked it against FE_NEEDSPONSOR or mention that you need on in the bug. Have a read through this doc on how to join the package maintainers again: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers The if you want to proceed take the following steps: 1. Fix up your bugzilla/FAS accounts 2. Join the fedora devel mailing list 3. Introduce yourself on fedora-devel - include that you need a sponsor. 4. Wait a little while and if you don't have any sponsors respond to you be proactive - polite emails to those on the Fedora wiki indicating they are sponsors willing to help bring in a new contributor... demonstrate what you have done to get acquainted with packaging and that you understand what the guidelines entail. Please note that "it passes tests" is not sufficient to be approved to be added to the fedora repositories. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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 gets stuck on poor connections
On 13 Nov 2015 12:32, "Sylvia Sánchez" wrote: > > Isn't there a plug in for dnf to try repositories and then pull the > stuff from the fastest? > About yum, I don't think it exists anymore... > You're thinking of the fastestmirror plugin ... Note though that this only looks at ping times iirc which won't always reflect overall likely throughout. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: How can Fedora determine the maximum speed of network computer cards?
For internet use your likely bottleneck is your wan connection anyway... In which case the usual places like speedtest.net apply for determining your up and down throughout. If you want to carry out throughout tests of systems you own then it's worth looking at iperf On 13 Nov 2015 13:25, "Paul Smith" wrote: > Dear All, > > Is there something in Fedora that I might use to determine the maximum > speed the network card of my computer can attain on Internet? I am > thinking about wired Internet and not about wireless Internet. > > Thanks in advance, > > Paul > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > 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://admin.fedoraproject.org/mailman/listinfo/users 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: [F23] Firewall breakage
On 6 November 2015 at 18:03, Antonio M wrote: > > > 2015-11-06 18:58 GMT+01:00 Rick Stevens : >> >> On 11/06/2015 09:48 AM, Antonio M wrote: >>> >>> by GUI, and it asked for the root password as expected...I think that is >>> a problem of Selinux...please have a look at >>> https://bugzilla.redhat.com/show_bug.cgi?id=1278840 >> >> >> That's possible. Have you tried relabeling /etc/firewalld? > > > > no, waiting for the correct solution, it was working fine in the past (I > guess that relabeling the file or following the instructions in the Selinux > report everything would be fine) > >> >> >> Also, please stop top-posting your replies. It makes reading the threads >> difficult. > > > > sorry, but Gmail as default uses top-posting > Just try to remember that inline/... button to get a better layout ;) Going back to topic what you describe sounds very much like the bug I filed here: https://bugzilla.redhat.com/show_bug.cgi?id=1237242 It was filed against EL7 but I expect it'll be replicable on Fedora as well ... I'll try and find time to test over the weekend and if I can duplicate it (the steps are fairly easy to do so and consistent in failure) will file for F23 as well. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: How should local repo packages be bootstrapped after an upgrade?
On 5 Nov 2015 11:34 a.m., "Kari Koskinen" wrote: >> >> For the future, I'd like to know if there is a way to go back to the previous behavior, and proceed with an upgrade to a new release, and ignore broken dependencies of existing packages for which no update is available, at the time of the upgrade. > > > Dnf does not allow ignoring the broken dependencies. So there is no way to do updates in the old way using dnf. > -- > The way I go about this sort of behaviour is a local httpd instance I fire up as a local repo. My own packages I use mock to build for the new version (heck I've gotten into the habit of using mock for any package building). Then when everything is built correctly pop in a repo that dnf system-upgrade can pick up. No broken dependencies and everything tested to ensure it builds properly before the upgrade. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: remove package without its dependencies
On 30 September 2015 at 11:24, arnaud gaboury wrote: > Is there any equivalent dnf command for : > > # rpm --nodeps -e MyPackage > No because breaking your system on purpose is generally a horrible idea - dependencies are there for a reason. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: f22: how to change default gateway via line command
On 8 Jun 2015 13:12, "Dario Lesca" wrote: > > Il giorno sab, 06/06/2015 alle 21.43 +0300, Alchemist ha scritto: > > Couple of possible solutions > > Thanks Alchemist, one of that sure probably partially solves my > problem. > > But the question is: Why in f22 (or new version of NetworkManager?) it > has removed the option to change the default gateway via "ip r rep..." > command line, like i do in previous version or all other version of > redhat or centos? > > I thing this is a issue, not a feature. > > Thanks > Think of it this way. You have your network manager configured (via static or dhcp) to have your default route pointed somewhere. NM tries to maintain its configuration so when it notices you've changed the route at the kernel level it doesn't know it's an admin override and fixes what it thinks is a broken setup. On NM based systems instead of using ip route try the nmcli command. Something like this ought to work: nmcli conn mod ipv4.gateway You can see the present configuration NM thinks it should be with: nmcli conn show -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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 22: SSSD Active Directory authentication
On 27 May 2015 15:58, "Frank Pikelner" wrote: > > Hello, > > Is anyone successfully using SSSD to authenticate user logins into Fedora 22 against Active Directory. More specifically using AD provider (versus LDAP) in their SSSD config? > > If possible, please share your config (less any confidential info) and any lessons learned. > > All our CentOS and Fedora systems auth from AD Check out this article I wrote on it: https://www.hogarthuk.com/?q=node/5 If using AD based uid/gid attributes don't forget to replicate uid to GC and index it for performance reasons. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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 oddity on F21 (but not F20)
On 15 Apr 2015 16:58, "Ranjan Maitra" wrote: > > > > -Original Message- > > From: mschwe...@gmail.com > > Sent: Wed, 15 Apr 2015 15:39:07 +0200 > > To: users@lists.fedoraproject.org > > Subject: Re: rpmbuild oddity on F21 (but not F20) > > > > On Wed, 15 Apr 2015 08:03:58 -0500, Ranjan Maitra wrote: > > > >> So, I have the strangest of problems. > >> > >> I create an rpm of wbar available in the spec file uploaded here: > >> > >> $ fpaste wbar.spec > >> Uploading (1.7KiB)... > >> http://ur1.ca/k6jqw -> http://paste.fedoraproject.org/211235/29102744 > > > > The Source0 in that spec file gives 404 not found. > > Which means I could not examine the source code you used. Perhaps it > > contains precompiled files? > > Sorry, my mistake: I have a newer version of wbar (which I modified, so I called it as version 2.3.5). Is there a place I can upload this bz2? fpaste does not like binaries. > > I have uploaded a new spec file to fpaste (to correct for this change): > > fpaste wbar.spec > Uploading (1.8KiB)... > http://ur1.ca/k6knt -> http://paste.fedoraproject.org/211298/13313142 > > > > > Can you upload your full rpmbuild output to some place? > > My rpmbuild on this machine is giving me problems now (sorry!). I can't tell what the problems are because it seems to add a release number to the directory name upon unpacking. What is the behaviour using mock instead so that you have a nice clean build environment? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Permanent NIC Setup from command line???
On 14 Apr 2015 18:47, "Peter Ulrich Kruppa" wrote: > > Hi, > > this is the background to question: > > Last week I set up my first Fedora (21) server - everything went well until ... now, of course "I didn't do anything" (TM) ... all my network configuration was gone. > First Aid was to set my NIC with the ip command - but this won't survive a reboot. > > Reading the fine manuals led me to NetworkManager and nmcli but > # systemctl status Networkmanager > ● Networkmanager.service >Loaded: not-found (Reason: No such file or directory) >Active: inactive (dead) > doesn't look good. > Case sensitivity is important. systemctl status NetworkManager Check the man page for nmcli Do a quick test with: nmcli c sh See if it shows connections -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: rsyslog
On Mar 5, 2015 1:03 AM, "Chris Murphy" wrote: > > logrotate-3.8.7-4.fc21.x86_64 is already installed by default with > Fedora 21 Workstation. I don't know why, seems unnecessary. But it's > there. > Don't forget this covers more than just syslog messages... Httpd logs for instance need logrotate for them. This would be true for any service that does it's own logging. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Samba 4 support
On 10 December 2014 at 08:38, wrote: > Indeed, > > At FOSDEM, two years ago (or is it already three) at de samba-devroom they > say that with samba4 you could do a seamless switch from Microsoft-AD to > samba4, and back. > All major distro's fail to do so, because of the HEIMDAL / MIT issue ... > > It looks like this issue is more difficult to solve than the transition to > system. > This is being worked on. There are changes that have been happening on the Samba Technical list to allow the AD functionality with MIT. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: problem with Dependency Resolution
On 14 Oct 2014 08:53, "Ed Greshko" wrote: > > The question would be Do you want the standard Fedora released version or that older version you got from someplace else? And if you want the older version of dconf-editor that you got from someplace else, they you need to replace the Fedora dconf package with the matching dconf from the same place you got dconf-editor. > To further emphasise something depending on potential changes in API doing a downgrade of dconf from 0.18 to 0.15 could break your system in pretty painful ways. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: fedora20: samba4: getent passwd (and group) not work property
On 29 Sep 2014 13:11, "Dario Lesca" wrote: > > Il giorno lun, 29/09/2014 alle 12.39 +0100, James Hogarth ha scritto: > > Enumeration is disabled by default for performance reasons. > > > > If you really want that as enumerate = true to the domain section of > > your sssd.conf > > Thanks for reply, James. > > But I known nothing about SSSD, and my sssd service is disabled and > inactive: > > > [root@s-backup ~]# systemctl status sssd > > sssd.service - System Security Services Daemon > >Loaded: loaded (/usr/lib/systemd/system/sssd.service; disabled) > >Active: inactive (dead) > > And the command "find /etc -name sssd.conf|wc -l" show 0 > > And if I "yum remove sssd*" only this unused service and our component > sssd-* is removed. > > Is it bind in some way to samba? > > It must be configure it and start it? Ah in that case I assume you are using winbind ... Sssd is preferred but if you want to use the old ways add this to your smb.conf and restart the winbind service: *winbind* *enum** users = yes* *winbind* *enum** groups = **yes* If that doesn't work you'll need to provide more details of your setup for help... The contents of /etc/nsswitch.conf /etc/samba/smb.conf and /etc/pam.d/system-auth ought to put people on the right track. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: fedora20: samba4: getent passwd (and group) not work property
On 29 Sep 2014 11:48, "Dario Lesca" wrote: > > Hi, I have configure samba 4 on my Fedora 20 with "security = domain" > and I have join this workstation to my linux PDC, a samba 3 domain > > All work fine and on fedora 20, via samba, I can autenticate the user's > domain. > > But the "getent passwd" (and also group) command non work like samba 3 > server. > > If I run "getent passwd mydomain\\ospite" the user is show: > > MYDOMAIN\ospite:*:4294967295:4294967295::/home/MYDOMAIN/ospite:/bin/false > > But if I run "getent passwd" (or group) to list all user (or groups), > the user/groups is not show and only local user/groups are report. > > Is this a known issue? > > I have misses some things? > > Someone can help me with some suggest ? > Enumeration is disabled by default for performance reasons. If you really want that as enumerate = true to the domain section of your sssd.conf -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: SELinux and the bash exploit.
On 25 September 2014 22:40, Daniel J Walsh wrote: > https://danwalsh.livejournal.com/71122.html > > Good article Dan ... it says clearly what I've been trying to drum into people's heads about the role it takes and how it confines the activity but an exploit that stays within the confines of that activity ... well it has to be allowed or else the standard activity would fail ;) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: Heads up: possible BASH security vulnerability
On 25 Sep 2014 01:44, "Chris Adams" wrote: > > > As far as I know, that would require some other security vulnerability > first (at which point bash security is moot). > -- Heads up people the first patch was incomplete... This is now being tracked under: https://access.redhat.com/security/cve/CVE-2014-7169 The original RH article has been updated with a new workaround until an updated patch gets deployed to systems. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: 2nd IP address on an interface
On 29 Aug 2014 01:32, "Robert Moskowitz" wrote: > > you are right. ifconfig USE to be able to do this, but now it is just a shell? over ip and so... > Your memory isn't quite accurate... ifconfig has never handled multiple IP addresses on an interface with aliases being used to create separate virtual interfaces instead. It is also not a shell over ip but rather a completely different package with a completely different development history... This is just yet another example of why net-tools has been deprecated a long time and that people really need to break their muscle memory and use iproute2 ... Is net-tools still in the base fedora install? Probably long since time to pull it if so... I know el7 doesn't include it in base or core package groups anymore at least.. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: how to accurately test internet upload & download speed
On 10 Jul 2014 18:19, "JD" wrote: > Very useful tools, especially while at hotspot cafe's. > Are there any free public servers for ttcp and iperf? Since the only way to test bandwidth is to fill the connection until you hit a limit on a serious note please do not do this at hotspots... You will cause severe performance degradation for every other user during your testing... This is not a very nice thing to do ;) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: why do we use systemd?
On 9 Jul 2014 00:33, "Rahul Sundaram" wrote: > This is not random Debian maintainers. This is the Debian technical committee empowered with making such decisions. A GR (General resolution) is the only way to override the tech committee and that requires some Debian maintainer to propose one and so far noone has done so > Actually over on the debian-project list after the technical committee had decided on systemd there was a call from someone for a GR overriding this but it failed to get enough support to be called to vote. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: How does the Host command query DNS?
On 24 Apr 2014 16:10, "Robert Moskowitz" wrote: > > Is there a command line that will 'just use' getaddrinfo taking a fqdn as input and return the results? My attempt to find such has come up empty; my search foo is typically weak... > getent hosts That should use the standard glibc (system) resolver with a getaddrinfo call if memory serves. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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: postgresql 8.4 on fedora 19
On 24 March 2014 01:35, Patrick O'Callaghan wrote: > On Sun, 2014-03-23 at 11:39 +, hicham wrote: > > Hello Every one > > > > I'm need to test an database application which runs with postgresql 8.4 > > is there a way to install it on fedora 19 ? > > > > or should i downgrade ? : ( > > > > thanks > > Since it's for testing, consider using a virtual machine with the > appropriate version of Fedora. > Or use a more appropriate distro such as CentOS6 which has postgres84 in it's base repos. Is there a specific reason you want to use Fedora? If it's just what you have installed on your workstation you should probably use a CentOS 6 VM. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users 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
