RPM build error
by Ranjan Maitra
Hello,
I am trying to build an RPM for sylfilter available at
http://sylpheed.sraoss.jp/sylfilter/src/sylfilter-%{?version}.tar.gz
with the attached .spec file but I get the following errors:
.....
error: Installed (but unpackaged) file(s) found:
/usr/include/sylfilter/bayes-filter.h
/usr/include/sylfilter/blacklist-filter.h
/usr/include/sylfilter/filter-kvs-gdbm.h
/usr/include/sylfilter/filter-kvs-qdbm.h
/usr/include/sylfilter/filter-kvs-sqlite.h
/usr/include/sylfilter/filter-kvs.h
/usr/include/sylfilter/filter-manager.h
/usr/include/sylfilter/filter-utils.h
/usr/include/sylfilter/filter.h
/usr/include/sylfilter/ngram-filter.h
/usr/include/sylfilter/textcontent-filter.h
/usr/include/sylfilter/whitelist-filter.h
/usr/include/sylfilter/wordsep-filter.h
/usr/lib64/libsylfilter.a
/usr/lib64/libsylfilter.la
/usr/lib64/libsylfilter.so
/usr/lib64/libsylfilter.so.0
/usr/lib64/libsylfilter.so.0.0.0
RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/include/sylfilter/bayes-filter.h
/usr/include/sylfilter/blacklist-filter.h
/usr/include/sylfilter/filter-kvs-gdbm.h
/usr/include/sylfilter/filter-kvs-qdbm.h
/usr/include/sylfilter/filter-kvs-sqlite.h
/usr/include/sylfilter/filter-kvs.h
/usr/include/sylfilter/filter-manager.h
/usr/include/sylfilter/filter-utils.h
/usr/include/sylfilter/filter.h
/usr/include/sylfilter/ngram-filter.h
/usr/include/sylfilter/textcontent-filter.h
/usr/include/sylfilter/whitelist-filter.h
/usr/include/sylfilter/wordsep-filter.h
/usr/lib64/libsylfilter.a
/usr/lib64/libsylfilter.la
/usr/lib64/libsylfilter.so
/usr/lib64/libsylfilter.so.0
/usr/lib64/libsylfilter.so.0.0.0
Not sure what the issue is, but wondering if anyone had any suggestions?
Many thanks and best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. Please respond to the mailing list if appropriate.
For those needing to send personal or professional e-mail, please use
appropriate addresses.
____________________________________________________________
GET FREE 5GB EMAIL - Check out spam free email with many cool features!
Visit http://www.inbox.com/email to find out more!
9 years, 2 months
WiFi permanently disappeared after booting test kernel
by Mike Fleetwood
Hi,
On my netbook I booted a test kernel 3.8.0-rc4+ I compiled. Now after
booting back into my regular Fedora kernel 3.6.11-5.fc17.i686.PAE my
wifi network device remains permanently disappeared. No wifi networks
displayed in Network Manager gui. Also the Network Manager syslog
messages make it look like the device has completely disappeared.
Suggestions for restoring wifi welcome.
Thanks
Mike
Fragment of Network Manager syslog messages when working before
--8<--
Jan 18 23:01:53 edge NetworkManager[479]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill2: found WiFi
radio killswitch (at
/sys/devices/pci0000:00/0000:00:1c.3/0000:01:00.0/ieee80211/phy0/rfkill2)
(driver ath9k)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill4: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill4)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiFi enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> Networking is enabled
by state file
...
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): using
nl80211 for WiFi device control
Jan 18 23:01:53 edge NetworkManager[479]: <warn> (wlan0): driver
supports Access Point (AP) mode
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): new 802.11
WiFi device (driver: 'ath9k' ifindex: 3)
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): exported as
/org/freedesktop/NetworkManager/Devices/1
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): now managed
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): bringing up device.
...
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
successful, device activated.
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
Stage 5 of 5 (IPv4 Commit) complete.
Fragment of Network Manager syslog messages when broken after
--8<--
Jan 28 18:43:26 edge NetworkManager[466]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill2: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill2)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiFi disabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> Networking is enabled
by state file
No (wlan0) related NetworkManager syslog messages afterwards at all.
9 years, 7 months
losing WiFi Access - prompted for password
by SternData
F18...
Over the last few days, I'm getting prompted to re-enter my password for
my WiFi network. It's not the router because no other device on the
network seems to be having problems.
Potential changes on my system include
May 07 21:39:32 Updated: 1:wpa_supplicant-1.1-1.fc18.x86_64
May 25 15:33:44 Installed: kernel-3.9.3-201.fc18.x86_64
May 27 08:06:42 Updated:
1:NetworkManager-glib-0.9.8.1-3.git20130514.fc18.x86_64
May 27 08:06:47 Updated: 1:NetworkManager-0.9.8.1-3.git20130514.fc18.x86_64
May 27 08:06:53 Updated:
network-manager-applet-0.9.8.1-4.git20130514.fc18.x86_64
Given that this has really started the day before yesterday, I suspect
it has something to do with the NetworkManager update. Is anyone else
having this problem?
(Please -- do not tell me to "dump the evil NetworkManager". I'm trying
to solve a problem here, not make some stand against the tide. Thanks.)
--
-- Steve
9 years, 10 months
Recovering/Restoring Boot Partition
by Don Levey
A short while ago, during a power cut, my desktop machine failed. A
power-up displayed symptoms consistent with a missing /boot partition;
attempting to boot under the rescue CD seemed to confirm this when it
did not mount the /boot partition.
Booting under the F20 LiveUSB key allowed me to manually mount the
partition; however, while I see files listed there some of them do not
appear to be readable.
I have seen the suggestion that all I need to do is to reinstall the
appropriate kernel files in the right place:
* Mount / via LiveUSB
* Mount /boot under / (above)
* "mount -bind" the current /proc directory to the
HD /proc directory
* "chroot" to the / directory mounted (above)
* "yum install" of grub, kernel, and logos
(all via
http://www.linuxforums.org/forum/red-hat-fedora-linux/187043-howto-recove..."
Is that what I'm looking to do, or is this dangerous? Are there
alternate/better suggestions?
-Don
10 years, 1 month
systemd security?
by Tom Horsley
Some random questions just occurred to me:
We have systemd growing like a fungus through the
entire system, controlling everything, and it uses
d-bus for all of its communication between parts.
A google search turns up a gazillion web pages
that talk about d-bus APIs for javascript.
So, does this mean people will soon (if not already)
be writing malicious web pages that use d-bus
and systemd to take over your system if you happen
to visit the page?
Or forget web pages. Will random users be able
to disrupt systems that use systemd by spewing
bazillions of d-bus messages in a denial of
service?
I'm just curious here, but I betcha there are
folks who are more than curious out there...
10 years, 2 months
IPv6 breakage in NetworkManager
by Dan Irwin
Hi all,
Seeing significant issues with IPv6. After some time, IPv6 completely seems
to stop working. IPv4 is unaffected.
Re-connecting to wifi seems to restore IPv6 connectivity.
However, various things (ssh, firefox) stop working completely. Open ssh
sessions "freeze". Web page requests time out.
At the same time, I can access IPv6 resources from other machines which do
not run NetworkManager.
Next time this occurs, I hope to have some time to diagnose this problem
further. In the meantime, is anyone else seeing such breaking wrt IPv6?
Something to note, I run numerous servers with IPv6, both physical and
virtual. These servers run CentOS; None run NetworkManager, and all have
working IPv6 connectivity.
Cheers,
Dan
10 years, 2 months
F20 cursor invisible
by Beartooth
I've just done fedup --network 20 (from F 18), and watched a lot
of the boot messages. There were warnings in at least a couple of places,
but that was as much as I was able to read. However, when I rebooted, all
seemed well except for a disaster to the mouse cursor.
The screen does have a cursor, and the mouse does move it. I can
tell that much because some things change their appearance, enabling me
to tell the mouse cursor is there; and, thanks be to all the inventors of
Linux, I do have a nice big pair of eyes on both my vertical and my
horizontal panel. Also, the trick with the control key is set.
For some reason, I always have great difficulty discovering the
way to make any adjustments to the cursor; but without a visible cursor
to mouse around with, I can't find it at all. I did find a couple places
that recognized the cursor is supposed to be size 48; but in fact it's so
tiny that only dumb luck alone would let me spot it without those eyes --
and they're not exactly precise, either (nor meant to be, I imagine).
My CLI-foo is nowhere near adequate to do much of anything by
itself. What can I do to get the cursor back to a nice big discoverable
size? I use 48 because it's the biggest. And while we're at it, how do I
get to a good color (such as red or yellow) that will stand out against
most backgrounds??
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
10 years, 2 months
rkhunter warnings, maybe yum issues?
by William Mattison
Good evening,
I don't know if these are properly rkhunter questions, yum questions, or
F-20 questions, so I'm posting to both lists.
Last Monday, I updated my 64-bit system from Fedora-19 to Fedora-20.
Several minutes ago, I updated Fedora-20 by doing "yum update". I then
did "rkhunter --update", and then "rkhunter --check". I'm getting a lot
of issues.
1. I get these messages in the rkhunter log:
[18:55:34] Info: The command 'rpm -qf --queryformat...
/usr/sbin/chkconfig' gave error code 1.
[18:55:39] Info: The command 'rpm -qf --queryformat... /usr/sbin/fuser'
gave error code 1.
[18:55:40] Info: The command 'rpm -qf --queryformat...
/usr/sbin/ifconfig' gave error code 1.
[18:55:44] Info: The command 'rpm -qf --queryformat... /usr/sbin/route'
gave error code 1.
[18:55:44] Info: The command 'rpm -qf --queryformat...
/usr/sbin/rsyslogd' gave error code 1.
[18:55:50] Info: The command 'rpm -qf --queryformat... /usr/bin/ed' gave
error code 1.
[18:55:50] Info: The command 'rpm -qf --queryformat... /usr/bin/egrep'
gave error code 1.
[18:55:50] Info: The command 'rpm -qf --queryformat... /usr/bin/fgrep'
gave error code 1.
[18:55:52] Info: The command 'rpm -qf --queryformat... /usr/bin/grep'
gave error code 1.
[18:55:55] Info: The command 'rpm -qf --queryformat... /usr/bin/mail'
gave error code 1.
[18:55:55] Info: The command 'rpm -qf --queryformat... /usr/bin/netstat'
gave error code 1.
[18:56:01] Info: The command 'rpm -qf --queryformat... /usr/bin/rpm'
gave error code 1.
[18:56:01] Info: The command 'rpm -qf --queryformat... /usr/bin/sed'
gave error code 1.
[18:56:07] Info: The command 'rpm -qf --queryformat... /usr/bin/mailx'
gave error code 1.
I get these warnings a lot (both under F-19, and since updating to
F-20). What's causing these warnings? Is there something yum should be
doing, but isn't? Is there something I should be doing, but I don't
know it?
2. I get this warning in the rkhunter log:
[18:55:49] /usr/bin/curl [ Warning ]
[18:55:49] Warning: Package manager verification has failed:
[18:55:49] File: /usr/bin/curl
[18:55:49] Try running the command 'prelink /usr/bin/curl' to
resolve dependency errors.
[18:55:49] The file hash value has changed
[18:55:49] The file size has changed
The warning gives me the immediate fix, and it works. But the problem
recurs after almost every "yum update" (both under F-19, and since
updating to F-20), though not on the same packages each time. What's the
real problem? Is there something yum should be doing, but isn't? Is
there something I should be doing, but I don't know it?
3. Since updating to F-20, I'm seeing this warning:
[18:56:18]
[18:56:18] Checking for GasKit Rootkit...
[18:56:18] Checking for file '/dev/dev/gaskit/sshd/sshdd' [ Not found ]
[18:56:18] Checking for directory '/dev/dev' [ Found ]
[18:56:18] Checking for directory '/dev/dev/gaskit' [ Not found ]
[18:56:18] Checking for directory '/dev/dev/gaskit/sshd' [ Not found ]
[18:56:18] Warning: GasKit Rootkit [ Warning ]
[18:56:18] Directory '/dev/dev' found
[18:56:18]
The directory "/dev/dev/" contains one entry:
bash.6[dev]: ll
total 0
lrwxrwxrwx. 1 root root 10 Jan 29 13:48 resume -> ../../sda5
bash.7[dev]:
Doing "file resume" gives this:
bash.21[dev]: file resume
resume: broken symbolic link to `../../sda5'
bash.22[dev]:
I see no "sda5" in the root directory. A "df" shows no filesystem. An
"ls -a" of the root directory shows one file I did not expect:
-rw-r--r--. 1 root root 178665 Jan 29 18:50 .readahead
It seems to be binary.
Do I have a security problem? What are "/dev/dev/resume" and "/.readahead"?
thanks,
Bill.
10 years, 2 months
BTRFS/Rollback & Yum Snapshot Plugin
by Jorge Fábregas
Hi everyone,
I'm playing around with btrfs (this time on a Fedora 20 VM). I used the
default configuration for btrfs that Anaconda provides. Right after
installation I did:
#btrfs subvolume list /
ID 257 gen 102 top level 5 path root
ID 258 gen 102 top level 5 path home
I then installed the yum-plugin-fs-snapshot package to try it out. I
installed some updates and after it:
#btrfs subvolume list /
ID 257 gen 102 top level 5 path root
ID 258 gen 102 top level 5 path home
ID 278 gen 95 top level 257 path yum_20140130172422
ID 279 gen 97 top level 5 path home/yum_20140130172422
Fine. yum created the snapshots. I then wanted to rollback my system
(to the state prior to the updates) so I went ahead and changed the
rootflags=subvol... parameter in GRUB's kernel line in order to specify
the above snapshot for the root filesytem. (I also changed /etc/fstab
to point /home to the snapshot subvolume). After booting, everything
seemed right (I was running off the snapshot subvolumes).
Now, here's the thing. I wanted to permanently run off these snapshots
so I wanted to delete the parent "subvolumes" for these snapshots (e.g.
"commit" the snapshot) by doing:
# mount -o subvolid=5 /dev/vda3 /mnt
# btrfs subvolume delete /mnt/root
Delete subvolume '/mnt/root'
ERROR: cannot delete '/mnt/root' - Device or resource busy
I believe this is happening because the snapshots are being created
WITHIN the subvolume they're snapshotting against. That is, I can't
delete it because the currently running root snapshot,
yum_20140130172422, resides inside the "root" subvolume. Is this
theory correct? Can you modify the yum plugin so that it places its
snapshots within OTHER particular subvolume?
BTW, is there anyone out there using this plugin with btrfs?
Thanks!
Jorge
p.d. I know snapshotting /home doesn't make sense at all for yum updates
but I followed it along...
10 years, 2 months
Libreoffice problem related to PDF forms
by Joachim Backes
Hi all,
I don't know if that's the right place for my question, but let me try:
I'running F20 with libreoffice-4.1.4.2-5.fc20.x86_64 including
libreoffice-pdfimport-4.1.4.2-5.fc20. Additionally I have some PDF file
with form entries (printable, but but not storable). I can open this PDF
file with acroread or evince without any password request and fill out
some form entries. The filled out file cannot be saved.
But if I try to import (open) this PDF file in libreoffice draw, some
password is requested.
PDF file properties:
pdfinfo Desktop/s.pdf
Producer: Acrobat Distiller 5.0.5 (Windows)
CreationDate: Thu Mar 13 10:13:48 2003
ModDate: Wed Dec 8 08:27:26 2004
Tagged: no
Form: AcroForm
Pages: 4
Encrypted: yes (print:yes copy:yes change:no addNotes:yes
algorithm:RC4)
Page size: 596 x 842 pts (A4)
Page rot: 0
File size: 179424 bytes
Optimized: yes
PDF version: 1.5
Anybody can explain this?
Kind regards
Joachim Backes
Fedora release 20 (Heisenbug)
Kernel-3.12.9-300.fc20.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
10 years, 2 months
