Re: swapping
On Sat, Jan 17, 2015 at 4:54 AM, Andrew R Paterson andy.pater...@ntlworld.com wrote: Having watched this debate I find I must add my own 10c I have spent over 30 years working on unix systems starting with xenix, bsd and ending up with linux . We survived quite happily using the well known DAC methods of standard UNIX. (UGO - RWX - setuid etc). Then I worked on some military systems (high security stuff) and started to use SOLARIS CMW (Compartentalised Mode Workstation) and DEC MLS (Multi-Level- Security). These both use the same (probably not as up to date) MAC security via labelling as (I guess) selinux. I can truthfully say I loved UNIX in all its forms until coming across CMW MLS and now SELINUX - then basically - I wanted OUT!. They are horrendous; if you start to use labelling in earnest - absolutely suicidal!!! - unless you have a real motive - ie you work for the security services or a bank or something and have a massive amount of time to devote. Why do the selinux guys have to force MAC onto all linux users - even hobbyists? Here, maybe this is more your style for this subject: https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf Quite honestly I feel the same way about packaging on linux. I sorta understand that it's necessary, like concrete needs cement, but I don't want to interact with it at all. Every distribution reinvents this particular wheel and makes me understand it's peculiarities when it comes to packaging. It causes users, packagers, and upstream no end of grief. It enhances my notion that distros are really different operating systems that just so happen to share a kernel (and maybe some other stuff). -- Chris Murphy -- 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: rpm -V - verifying packages
On Sat, 17 Jan 2015 21:14:11 -0700, Robin Laing wrote: Hello, I don't know if I found a bug with upgrade or if there is a strange issue with rpm. I have upgraded from F19 to F21 on a machine. The upgrade worked quite well. Due to the nVidia driver changes, I installed the nVidia driver from nVidia instead of the normal rpmfusion as the 340 driver was not available. Today I decided to give the latest Nouveau driver a try but knowing that the nVidia install can and will change files, I decided to check my machine with rpm -Va rpm_verify.txt To my shock, many files came back with S.?.. for the verification response. When I say many, the line count is 705 files. As superuser root? Any examples? Failure '?' very often (always?) is an indication that the test could not be performed because of failure to access the file. Failure 'S' is typical for config/data or regularly recompiled/optimized files, for example. -- 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-21 firewall advice?
On 17.01.2015, poma wrote: For people not subscribed at de...@lists.fedoraproject.org Workstation Product defaults to wide-open firewall https://lists.fedoraproject.org/pipermail/devel/2014-December/205010.html Opposed to what is written in this article, firewalld leaves the system open even after upgrading with --product=nonproduct, which I verified some minutes ago on a laptop upgraded from F20 to F21 yesterday evening. -- 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-21 firewall advice?
On 17.01.2015, Timothy Murphy wrote: I'm presently using shorewall with iptables. Can shorewall be used with firewalld? No, it shouldn't, since both eventually apply different iptables rules. I'm surprised that I have never seen an article starting In Fedora 21 you will have to choose between firewalld and iptables. Unless I have severely misunderstood the whole concept, firewalld relies on iptables. Btw: shorewall is great, have been using it a long time (with some minor modifications). Just disable firewalld entirely and keep shorewall, firewalld won't protect you anyway if not configured after install. An iptables -L after a fresh F21 install shows no protection. -- 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: LO crashes when opening draw docs
On 01/18/2015 02:37 PM, Joachim Backes wrote: Hi all, having big LO problems if trying to open some odg file: #A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f570bff2c05, pid=23025, tid=140011775326272 # # JRE version: OpenJDK Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18) # Java VM: OpenJDK 64-Bit Server VM (25.25-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libsvtlo.so+0x200c05] This happens with the actual libreoffice-4.3.5.2-7.fc21.x86_64. The last running version (for me) was libreoffice-4.3.5.2-4.fc21.x86_64. Other doc types as writer, calc or impress can be opened flawlessly. Anybody has similar issues? Any comments are welcome. Joachim Backes I forgot to say that opening the odg doc's with sudo soffice ... will open the odg doc perfectly. Joachim BAckes -- Fedora release 21 (Twenty One) Kernel-3.18.3-200.fc21.x86_64 Joachim Backes joachim.bac...@rhrk.uni-kl.de https://www-user.rhrk.uni-kl.de/~backes -- 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-21 firewall advice?
Hi On Sat, Jan 17, 2015 at 7:24 PM, Timothy Murphy wrote: My meaning was: if firewalld is associated to systemd then sooner or later it will probably become the standard firewall in all distributions, so I might as well get used to it. I see. Firewalld is a independent project entirely however. It is likely to be standard in Fedora and RHEL for the foreseeable future but I don't see other distributions adopting it. Atleast there has been no push for it so far. There is however broad support among other third party firewall integration programs already probably because RHEL 7 has it by default. But if it is a straightforward choice between two firewalls, I may as well stick with the one I know. Fair enough. I would suggest looking into it when you have the time. Rahul -- 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-21 firewall advice?
On Sat, 2015-01-17 at 13:41 +, Timothy Murphy wrote: I'm surprised that I have never seen an article starting In Fedora 21 you will have to choose between firewalld and iptables. Or have I completely misunderstood the situation? For clarity's sake, firewalld does use iptables rules to do its trick, but there is also a system service called iptables that runs a set of iptables rules (the latter is the one that we're used to). These two services are mutually incompatible, as far as I'm aware (or would require special configuration to have them both run concurrently), as firewalld can dynamically change rules to suit running applications (which some will say is not a secure practice), but iptables doesn't do that (it applies pre-configured rules). You'd have one trying to change the rules of the other. -- tim@localhost ~]$ uname -rsvp Linux 3.17.8-200.fc20.i686 #1 SMP Fri Jan 9 00:01:03 UTC 2015 i686 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- 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: Using old Creative CT-4810 sound card in F20 ??
On 18.01.2015 00:33, Fred Smith wrote: I'm trying to get an old Creative CT4810 sound card working on my F20 machine. I've disabled, in the BIOS, the built-in sound hardware, plugged the creative card into a PCI slot, booted up and lspci shows no sound hardware. I tried removing and reinstalling the alsa packages that were currently installed to no avail. perhaps there's another one I need specifically for that card? How to tell? Any advice will be appreciated, thanks in advance! Fred First, the kernel needs to see that device, if it ain't broken in the first place. Try move it to another free slot if possible, and or reset the BIOS to its defaults. -- 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
LO crashes when opening draw docs
Hi all, having big LO problems if trying to open some odg file: #A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f570bff2c05, pid=23025, tid=140011775326272 # # JRE version: OpenJDK Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18) # Java VM: OpenJDK 64-Bit Server VM (25.25-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libsvtlo.so+0x200c05] This happens with the actual libreoffice-4.3.5.2-7.fc21.x86_64. The last running version (for me) was libreoffice-4.3.5.2-4.fc21.x86_64. Other doc types as writer, calc or impress can be opened flawlessly. Anybody has similar issues? Any comments are welcome. Joachim Backes -- Fedora release 21 (Twenty One) Kernel-3.18.3-200.fc21.x86_64 Joachim Backes joachim.bac...@rhrk.uni-kl.de https://www-user.rhrk.uni-kl.de/~backes -- 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: swapping
On 17.01.2015 19:52, Ntlworld wrote: Right - I think I might start looking at Ubuntu! Sent from my iPhone This old man and me, were at the bar and we Were having us some beers and swaping I dont cares Talking politics, blonde and red-head chicks Old dogs and new tricks and habits we aint kicked We talked about Gods grace and all the hell we raised Then I heard the ol' man say; God is great, beer is good and people are crazy B.C. :) -- 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: Cooling a laptop
On 01/18/2015 12:18 AM, Tim wrote: On Sat, 2015-01-17 at 15:21 -0700, jd1008 wrote: I am looking for a laptop cooling pad the fans of which are relocatable so that I can position them to blow into the air port hols/slots on the bottom of the laptop. This looked interesting: Cooler Master NotePal U3 Laptop Cooler Review https://www.youtube.com/watch?v=lpGhcVQnfT0 I searched for movable rather than relocatable fans. Thank you Tim. I am used your keyword and it provides a lot more hits :) Cheers, JD -- 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: LO crashes when opening draw docs
On 01/18/2015 06:44 PM, poma wrote: Hi poma, rpm --verify $(rpm -qf /usr/lib64/libreoffice/program/libsvtlo.so); if test $? -eq 0; then echo OK; else echo Uhhuh; fi That's my answer: rpm --verify $(rpm -qf /usr/lib64/libreoffice/program/libsvtlo.so) echo OK || echo Uhhh OK And now? -- Fedora release 21 (Twenty One) Kernel-3.18.3-200.fc21.x86_64 Joachim Backes joachim.bac...@rhrk.uni-kl.de https://www-user.rhrk.uni-kl.de/~backes -- 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: C/C++ Compiler Invalidly Turning Warnings into Errors? - Realtek RTL8811AU USB WiFi
On 01/17/2015 08:07 PM, poma wrote: On 17.01.2015 04:02, Stephen Morris wrote: On 01/16/2015 08:38 AM, Stephen Morris wrote: On 01/15/2015 11:46 PM, poma wrote: On 15.01.2015 08:50, Stephen Morris wrote: I have a driver for a wifi usb device that I need to compile because there are no drivers in the kernel, which has been obtained from the vendor of the device. When I attempt to compile the code the compile fails on the grounds that some warnings are being translated into errors. From my perspective these errors should not be happening because, when a debugging module wants to time stamp the build, that is not an error and is perfectly acceptable. How do I get the compiler to stop producing these errors. The messages I get are listed below. Authentication requested [root] for make driver: make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/3.17.8-300.fc21.x86_64/build M=/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411 modules make[1]: Entering directory '/usr/src/kernels/3.17.8-300.fc21.x86_64' CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_cmd.o CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_security.o CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c: In function ‘dump_drv_version’: /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:64: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] DBG_871X_SEL_NL(sel, build time: %s %s\n, __DATE__, __TIME__); ^ /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] DBG_871X_SEL_NL(sel, build time: %s %s\n, __DATE__, __TIME__); ^ /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] cc1: some warnings being treated as errors scripts/Makefile.build:257: recipe for target '/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o' failed make[2]: *** [/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o] Error 1 Makefile:1377: recipe for target '_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411' failed make[1]: *** [_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411] Error 2 make[1]: Leaving directory '/usr/src/kernels/3.17.8-300.fc21.x86_64' Makefile:1350: recipe for target 'modules' failed make: *** [modules] Error 2 ## Compile make driver error: 2 Please check error Mesg ## $ sed -i '/uninitialized/ i\EXTRA_CFLAGS += -Wno-error=date-time' Makefile If it crashes, try your luck with these: $ git clone https://github.com/gnab/rtl8812au.git $ cd rtl8812au/ ... $ git clone https://github.com/abperiasamy/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ ... $ make $ su # cp 8812au.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v 8812au Thanks poma, I'll check these out. The git source might be better than what I have at the moment as the vendor source I have seems to be requiring kernel config parameters that appear to not be active in the kernels I am using. I've compiled the code and after copying the compiled module and running the modprobe the device immediately connected. I'll run a few more tests and try a reboot to see if it still works successfully. I am assuming that I will need to perform all these steps everytime the kernel is upgraded, would that be correct? If you put the
Re: Fedora-21 vs NFS
On Sat, Jan 17, 2015 at 2:03 AM, Jonathan Ryshpan jonr...@pacbell.net wrote: I have just upgraded amito, the client from Fedora-20 to Fedora-21. The server, weather, is still running Fedora-20. After the upgrade, an attempt by amito to nfs mount a filesystem on weather fails with an access denial by by weather. Before the upgrade, everything worked fine. It looks like the mount should succeed, since showmount indicates that the export from weather is OK. Nevertheless it fails. How can I debug this? I'm pretty much an NFS newbie. Here is the relevant info: [root@amito jonrysh]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Jan 4 19:54:47 2015 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/fedora00-root / ext4 defaults1 1 UUID=7e3eb9f4-44eb-4120-8593-5570190feded /boot ext4 defaults1 2 /dev/mapper/fedora00-home /home ext4 defaults1 2 /dev/mapper/fedora00-Windows /srv/c vfat shortname=winnt 0 0 /dev/mapper/fedora00-swap swapswap defaults0 0 # NFS Mounts weather:/ /srv/weathernfs4 users,defaults 0 0 weather:/var /srv/weather/varnfs4 users,defaults 0 0 [root@amito jonrysh]# ls -l /srv total 36 drwxr-xr-x. 11 root root 32768 Dec 31 1969 c drwxr-xr-x. 2 root root 4096 Jan 16 22:01 weather [root@amito jonrysh]# showmount -e weather Export list for weather: /home amito.gateway.2wire.net / amito.gateway.2wire.net [root@amito jonrysh]# mount /srv/weather mount.nfs4: access denied by server while mounting weather:/ Do both amito and weather have gateway.2wire.net as their domainname? Did amito's firewall rules change with the upgrade?! What's the output, on amito, of 'rpcinfo -p weather'? Does 'mount -t nfs -o nfsvers=3 weather:/ /srv/weather' succeed? You can mount with '-v' to get a more verbose failure. (Do you mean weather:/var ... or weather:/home ... in fstab?) -- 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: LO crashes when opening draw docs
On 18.01.2015 14:43, Joachim Backes wrote: On 01/18/2015 02:37 PM, Joachim Backes wrote: Hi all, having big LO problems if trying to open some odg file: #A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f570bff2c05, pid=23025, tid=140011775326272 # # JRE version: OpenJDK Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18) # Java VM: OpenJDK 64-Bit Server VM (25.25-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libsvtlo.so+0x200c05] This happens with the actual libreoffice-4.3.5.2-7.fc21.x86_64. The last running version (for me) was libreoffice-4.3.5.2-4.fc21.x86_64. Other doc types as writer, calc or impress can be opened flawlessly. Anybody has similar issues? Any comments are welcome. Joachim Backes I forgot to say that opening the odg doc's with sudo soffice ... will open the odg doc perfectly. Joachim BAckes $ rpm --verify $(rpm -qf /usr/lib64/libreoffice/program/libsvtlo.so); if test $? -eq 0; then echo OK; else echo Uhhuh; fi OK -- 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
error after install any software
I running 21 with gnome install when I try to install any software from the software center . The first software install just fine . But when I try to install anything else it will not install so . I try to install it from command line with yum install program's name to see the error and I get this error: db5 error(-30973) from dbenv-open: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db5 - (-30973) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main . Only way I can get it to work is to reboot . Dose anyone know how 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: error after install any software
Sounds like either a corrupted yum or rpm database. I'd start by flushing the former and rebuilding the latter: sudo yum clean all sudo rpm --rebuilddb On 18 January 2015 at 23:16, William Biggs kc8...@ohioham.com wrote: I running 21 with gnome install when I try to install any software from the software center . The first software install just fine . But when I try to install anything else it will not install so . I try to install it from command line with yum install program's name to see the error and I get this error: db5 error(-30973) from dbenv-open: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db5 - (-30973) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main . Only way I can get it to work is to reboot . Dose anyone know how 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 -- Andy The only person to have all his work done by Friday was Robinson Crusoe -- 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-21 firewall advice?
On 01/19/15 05:32, Gordon Messmer wrote: On 01/18/2015 04:44 AM, Heinz Diehl wrote: Opposed to what is written in this article, firewalld leaves the system open even after upgrading with --product=nonproduct, which I verified some minutes ago on a laptop upgraded from F20 to F21 yesterday evening. Use 'iptables -L -n -v'. You are probably mistaking the allow-all-on-lo rule for an entirely open rule. Firewalld's default is not open Yes. It is certainly *NOT OPEN* as has been suggested Trying to connect to sendmail on a newly minted F21 system from a F20 system [egreshko@meimei ~]$ telnet 192.168.1.222 25 Trying 192.168.1.222... telnet: connect to address 192.168.1.222: No route to host Then opening up the port... [egreshko@meimei ~]$ telnet 192.168.1.222 25 Trying 192.168.1.222... telnet: connect to address 192.168.1.222: Connection refused Since sendmail isn't listening on the port. -- If you can't laugh at yourself, others will gladly oblige. -- 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: Removing obsolete selinux setup
I received an answer that worked on the fedora forums. 1. Edit the file /etc/selinux/targeted/modules/active/file_contexts.local and comment/fix the wrong contexts. In my case this meant changing httpd_mediawiki_rw_content_t to mediawiki_rw_content_t. Then I used # semanage fcontext -a -t httpd_sys_rw_content_t '/etc/dokuwiki' # semanage fcontext -a -t httpd_sys_rw_content_t '/etc/dokuwiki/users.auth.php' # semanage fcontext -a -t httpd_sys_rw_content_t '/etc/dokuwiki/local.php' # restorecon -R /etc/dokuwiki to get the files setup properly. Seems like the dokuwiki selinux package should be setup to do something similar. Pete -- 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: LO crashes when opening draw docs
On 18.01.2015 20:29, Joachim Backes wrote: On 01/18/2015 06:44 PM, poma wrote: Hi poma, rpm --verify $(rpm -qf /usr/lib64/libreoffice/program/libsvtlo.so); if test $? -eq 0; then echo OK; else echo Uhhuh; fi That's my answer: rpm --verify $(rpm -qf /usr/lib64/libreoffice/program/libsvtlo.so) echo OK || echo Uhhh OK And now? Obviously installation is OK. Do you really need my advice for the next step? -- 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: C/C++ Compiler Invalidly Turning Warnings into Errors? - Realtek RTL8811AU USB WiFi
On 18.01.2015 20:45, Stephen Morris wrote: On 01/17/2015 08:07 PM, poma wrote: On 17.01.2015 04:02, Stephen Morris wrote: On 01/16/2015 08:38 AM, Stephen Morris wrote: On 01/15/2015 11:46 PM, poma wrote: On 15.01.2015 08:50, Stephen Morris wrote: I have a driver for a wifi usb device that I need to compile because there are no drivers in the kernel, which has been obtained from the vendor of the device. When I attempt to compile the code the compile fails on the grounds that some warnings are being translated into errors. From my perspective these errors should not be happening because, when a debugging module wants to time stamp the build, that is not an error and is perfectly acceptable. How do I get the compiler to stop producing these errors. The messages I get are listed below. Authentication requested [root] for make driver: make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/3.17.8-300.fc21.x86_64/build M=/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411 modules make[1]: Entering directory '/usr/src/kernels/3.17.8-300.fc21.x86_64' CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_cmd.o CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_security.o CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c: In function ‘dump_drv_version’: /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:64: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] DBG_871X_SEL_NL(sel, build time: %s %s\n, __DATE__, __TIME__); ^ /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] DBG_871X_SEL_NL(sel, build time: %s %s\n, __DATE__, __TIME__); ^ /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] cc1: some warnings being treated as errors scripts/Makefile.build:257: recipe for target '/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o' failed make[2]: *** [/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o] Error 1 Makefile:1377: recipe for target '_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411' failed make[1]: *** [_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411] Error 2 make[1]: Leaving directory '/usr/src/kernels/3.17.8-300.fc21.x86_64' Makefile:1350: recipe for target 'modules' failed make: *** [modules] Error 2 ## Compile make driver error: 2 Please check error Mesg ## $ sed -i '/uninitialized/ i\EXTRA_CFLAGS += -Wno-error=date-time' Makefile If it crashes, try your luck with these: $ git clone https://github.com/gnab/rtl8812au.git $ cd rtl8812au/ ... $ git clone https://github.com/abperiasamy/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ ... $ make $ su # cp 8812au.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v 8812au Thanks poma, I'll check these out. The git source might be better than what I have at the moment as the vendor source I have seems to be requiring kernel config parameters that appear to not be active in the kernels I am using. I've compiled the code and after copying the compiled module and running the modprobe the device immediately connected. I'll run a few more tests and try a reboot to see if it still works successfully. I am
Re: Fedora-21 firewall advice?
On 18.01.2015 13:44, Heinz Diehl wrote: On 17.01.2015, poma wrote: For people not subscribed at de...@lists.fedoraproject.org Workstation Product defaults to wide-open firewall https://lists.fedoraproject.org/pipermail/devel/2014-December/205010.html Opposed to what is written in this article, firewalld leaves the system open even after upgrading with --product=nonproduct, which I verified some minutes ago on a laptop upgraded from F20 to F21 yesterday evening. Don't forget beer and popcorn. ;) -- 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-21 firewall advice?
On 01/18/2015 04:44 AM, Heinz Diehl wrote: Opposed to what is written in this article, firewalld leaves the system open even after upgrading with --product=nonproduct, which I verified some minutes ago on a laptop upgraded from F20 to F21 yesterday evening. Use 'iptables -L -n -v'. You are probably mistaking the allow-all-on-lo rule for an entirely open rule. Firewalld's default is not open -- 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
