Evolution Filtering
by Mike Chambers
Ever since a couple of updates ago, evolution will be stucking in
"filtering mode", as in waiting for all the emails to be filtered and
sent to their respective folders. I have to close, then kill the pid.
Then I can reopen it and it will start filtering with no problems. But
once you leave it open for awhile, it is stuck again trying to filter.
Be advised, this worked when F21 first came out and however many updates
after that until recently. Nothing on the settings end nor anything was
changed. And this system is setup as imap to a local network mail
server.
evolution-data-server-3.12.11-1.fc21.x86_64
evolution-3.12.11-1.fc21.x86_64
evolution-bogofilter-3.12.11-1.fc21.x86_64
--
Mike Chambers
Madisonville, KY
"Best little town on Earth!"
9 years, 1 month
F21 - perl broken? 5.16 vs. 5.18 API problem.
by Martin Møller Skarbiniks Pedersen
Hi,
I am trying to build a rpm but now I got a perl problem ?
It looks like my perl installation is somehow broken currently.
Pleas advise.
Thanks a lot.
Regards
Martin
$ perl --version
This is perl 5, version 18, subversion 4 (v5.18.4) built for
x86_64-linux-thread-multi
(with 23 registered patches, see perl -V for more detail)
[...]
$ perl -MCPAN -e shell
Attempt to reload Scalar/Util.pm aborted.
Compilation failed in require at /usr/local/share/perl5/Safe.pm line 4.
BEGIN failed--compilation aborted at /usr/local/share/perl5/Safe.pm line 4.
Compilation failed in require at /usr/share/perl5/CPAN.pm line 56.
BEGIN failed--compilation aborted at /usr/share/perl5/CPAN.pm line 56.
Compilation failed in require.
BEGIN failed--compilation aborted.
$ rpmbuild -ba moon-buggy.spec
[...]
+ autoreconf -if
Perl API version v5.16.0 of threads does not match v5.18.0 at
/usr/share/perl5/XSLoader.pm line 92.
Compilation failed in require at
/usr/share/automake-1.14/Automake/ChannelDefs.pm line 23.
BEGIN failed--compilation aborted at
/usr/share/automake-1.14/Automake/ChannelDefs.pm line 26.
Compilation failed in require at
/usr/share/automake-1.14/Automake/Configure_ac.pm line 27.
BEGIN failed--compilation aborted at
/usr/share/automake-1.14/Automake/Configure_ac.pm line 27.
Compilation failed in require at /usr/bin/aclocal line 39.
BEGIN failed--compilation aborted at /usr/bin/aclocal line 39.
autoreconf: aclocal failed with exit status: 2
error: Bad exit status from /var/tmp/rpm-tmp.ePUGGu (%prep)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.ePUGGu (%prep)
9 years, 1 month
Re: How to increase maximum user cpu usage allowed on a multi core system?
by stan
On Wed, 11 Mar 2015 13:32:09 +0100
poma <pomidorabelisima(a)gmail.com> wrote:
> > 1. You still haven't provided basic information about the processor,
> thus 'lscpu' or a similar command.
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 6
On-line CPU(s) list: 0-5
Thread(s) per core: 2
Core(s) per socket: 3
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 2
Model name: AMD FX(tm)-6300 Six-Core Processor
Stepping: 0
CPU MHz: 3500.000
CPU max MHz: 3500.0000
CPU min MHz: 1400.0000
BogoMIPS: 7023.57
Virtualization: AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
L3 cache: 8192K
NUMA node0 CPU(s): 0-5
>
> 2. Moreover you still haven't provided the difference between
> "I'm running Fedora 21 with a custom compiled kernel,
> 3.19.0-1.20150211.fc21.x86_64." and stock Fedora kernel -
> 3.18.8-201.fc21.x86_64, i.e.
> diff /boot/config-3.18.8-201.fc21.x86_64 /boot/3.19.0-1.20150211.fc21.x86_64
>
I can do this but I think it is too large for a message.
There are 1532 lines of output from that command.
> 3. Also you haven't mentioned whether the same happens with the stock
> Fedora kernel.
Yes, it did.
>
> 4. And you haven't explained why you use a custom kernel, and why
> particularly 3.19 kernel.
To remove all the generalizations that have to be in stock kernels so
they can work for everyone. It greatly speeds compilation to not do
all those drivers that I don't need. Sound cards I don't have
Latest that created packages without errors. I'll be upgrading to 4.0
kernel shortly. https://bugzilla.redhat.com/show_bug.cgi?id=1199312
>
> 5. Etc.
>
> How anybody can help in this way, man.
>
I don't see how those have any relevance. All the answers to them
would do is be noise or distraction. This is at a meta level above
that, about the design and control level, rather than the implementation
details. I guess I am assuming that the kernel programmers have done
their job, and the kernel functionality is abstracted from the
underlying hardware. Especially for x86 architectures.
I think Heinz has put his finger on the issue in his response: a single
process is limited to a single core. But, if that single process can
spawn other processes, which is what 'make -j6' should be doing, why
would that be true? I'll be following up in my response to him.
Thanks for taking an interest, and I'm not trying to be hostile, but I
honestly don't see how answering your questions helps.
9 years, 1 month
Testing F21 kernel update kernel-3.18.9-200.fc21
by Meikel
Hi folks,
in bugzilla I found a bug
(https://bugzilla.redhat.com/show_bug.cgi?id=1197842) that adresses an
issue I have. In a comment from Fedora Update System I can see that
"kernel-3.18.9-200.fc21 has been submitted as an update for Fedora 21.".
I would like to verify if that kernel fixes my issue. I did read the
"How to test updates"
(https://fedoraproject.org/wiki/How_to_test_updates) but it's still not
clear to me what steps are necessary to test the update.
I do not see the kernel update with yum check-update command:
LANG="" su -c 'yum check-update --enablerepo=updates-testing kernel'
# Loaded plugins: langpacks
No more output. I then tried
LANG="" su -c 'yum update --enablerepo=updates kernel-3.18.9-200.fc21'
# Loaded plugins: langpacks
# No Match for argument: kernel-3.18.9-200.fc21
# No package kernel-3.18.9-200.fc21 available.
# No packages marked for update
Currently I'm running kernel 3.18.8-201.fc21.i686:
uname -r
# 3.18.8-201.fc21.i686
Can somebody give me advice on how I can test the kernel update
mentioned above?
Thanks,
Meikel
9 years, 1 month
Fedora 21 server gnome install not starting
by Morgan Read
Hello Folks
I know there's many questions about 'no graphical environment on
server', but I've install gnome and enabled it.
After booting the display hangs following:
[ OK ] Started GNOME Display Manager
And, perhaps a few following such as starting virtualisation demon,
waiting for plymouth to quit
Following a server install I ran the following successfully:
# yum groupinstall gnome --skip-broken
# systemctl set-default graphical.target
This this is what systemctl says:
]# systemctl status -l gdm.service
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
Active: failed (Result: start-limit) since Sun 2015-03-08 17:51:35
GMT; 1min 29s ago
Process: 1613 ExecStart=/usr/sbin/gdm (code=exited, status=1/FAILURE)
Main PID: 1613 (code=exited, status=1/FAILURE)
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service: main process
exited, code=exited, status=1/FAILURE
Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered
failed state.
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed.
Mar 08 17:51:35 frontserver.lan systemd[1]: start request repeated too
quickly for gdm.service
Mar 08 17:51:35 frontserver.lan systemd[1]: Failed to start GNOME
Display Manager.
Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered
failed state.
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed.
Any pointers would be very much appreciated.
Many thanks.
Morgan
--
Morgan Read
Confused about DRM?
Get all the info you need at:
http://drm.info/
9 years, 1 month
gnome-shell: slow logins?
by Dr. Michael J. Chudobiak
I have a variety of F21 users, some with remote home folders (on
gluster) and some with local home folders (on desktop SSDs).
Some users experience login delays on 30-60 seconds after entering their
username/passwd in gdm (the "last login" time is shown, so it is not an
authentication delay). The gnome-shell background does not appear during
that delay.
What causes these delays? How can I debug it? I tried masking the colord
daemon, and moving the tracker files out of /etc/xdg/autostart/, but it
didn't help.
Logouts can be painfully slow too.
Some systems are super-quick to load, so it's baffling...
Any ideas?
- Mike
9 years, 1 month
yum update problem with vlc
by JD
Part of the output:
--> Processing Dependency: kernel-uname-r = 3.18.5-201.fc21.x86_64 for
package: kmod-vhba-3.18.5-201.fc21.x86_64-20140928-1.fc21.x86_64
---> Package kmod-vhba-3.18.5-201.fc21.x86_64.x86_64 0:20140928-1.fc21
will be erased
---> Package vlc-core.x86_64 0:2.2.0-1.fc21 will be an update
--> Processing Dependency: libgpg-error.so.0(GPG_ERROR_1.0)(64bit) for
package: vlc-core-2.2.0-1.fc21.x86_64
--> Running transaction check
---> Package vlc-core.x86_64 0:2.2.0-1.fc21 will be an update
--> Processing Dependency: libgpg-error.so.0(GPG_ERROR_1.0)(64bit) for
package: vlc-core-2.2.0-1.fc21.x86_64
--> Finished Dependency Resolution
Error: Package: vlc-core-2.2.0-1.fc21.x86_64 (rpmfusion-free-updates)
Requires: libgpg-error.so.0(GPG_ERROR_1.0)(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
$ rpm -qv --whatprovides /usr/lib64/libgpg-error.so.0
libgpg-error-1.13-3.fc21.x86_64
$ rpm -qv --whatrequires libgpg-error.so.0
libgpg-error-1.13-3.fc21.i686
libgcrypt-1.6.1-7.fc21.i686
libxslt-1.1.28-8.fc21.i686
systemd-libs-216-20.fc21.i686
So, how can I proceed with thish clash of dependencies?
Should I completely uninstall vlc and forget about it?
9 years, 1 month
For F20, during shutdown is the hwclock updated...
by dcw
I have done several searches to find this info. I have searched for
systemd, shutdown, rtc, hwclock and combinations of those key words and
not found what I was looking for.
For F20, during shutdown is the hwclock updated?
How can I enable/disable that behaviour during shutdown.
Thanks all,
David
9 years, 1 month
camera troubles
by Amadeus W.M.
Ok, so I'm moving on from pidgin, to skype.
I found how to install skype here:
http://www.if-not-true-then-false.com/2012/install-skype-on-fedora-centos-
red-hat-rhel-scientific-linux-sl/
It works. Except for my old Logitech QuickCam Messenger camera. But I
found this excellent hack that shows how to get it to work:
http://community.linuxmint.com/tutorial/view/219
which basically says that skype expects the v4l1 libraries, not the
default v4l2 so one needs to preload the v4l1compat.so library - the 32
bit version, to match skype.
For my 64-bit Fedora this would be:
#!/bin/bash
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so /usr/bin/skype
So I did that, but I'm getting this error:
ERROR: ld.so: object '/usr/lib/libv4l/v4l1compat.so' from LD_PRELOAD
cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Lo and behold though, the camera works despite that error. So for my
peace of mind, can anybody explain what's going on?
9 years, 1 month