Problem with duplicate packages on system
by JD
# yum check
Loaded plugins: langpacks, refresh-packagekit
cogl-1.16.0-3.fc20.x86_64 is a duplicate with cogl-1.16.0-2.fc20.x86_64
flickcurl-1.26-1.fc20.x86_64 is a duplicate with
flickcurl-1.25-1.fc20.x86_64
gvfs-1.18.3-3.fc20.x86_64 is a duplicate with gvfs-1.18.3-2.fc20.x86_64
libplist-1.11-2.fc20.x86_64 is a duplicate with libplist-1.10-2.fc20.x86_64
libspnav-0.2.3-1.fc20.x86_64 is a duplicate with
libspnav-0.2.2-6.fc20.x86_64
openvpn-2.3.2-6.fc20.x86_64 is a duplicate with openvpn-2.3.2-4.fc20.x86_64
How can this be?
I thought yum update takes care not to allow duplicates?
9 years, 8 months
ps -ef stack overflow fedora 20 fully updated
by Ger van Dijck
Hi Folks,
When doing a ps -ef on a fully updated Fedora 20 OS I get the following
message:
/usr/bin/abrt-watch-log -F BUG : WARNING : at WARNING : CPU :INFO:
possoble recurcive locking detected kernel BUG at list_del corruption
list_add corruption do_IRQ :stack overflow : ear stack overflow (cur:
general protection fault enable to handle kernel double fault : RTNL :
assertion failed eek! page_mapcount(page) went nagative! madness at NETDEV
WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch
Machine Chek Exeption : Machine check events logged devide error : bounds
: coprosessor overrun : invalid TSS : segment not present : invalid upcode
: aligment check : stack segment : fpu exeption : simd exeption : iret
exeption : /var/log/messages -- /usr/bin/abrt-dump-oops -xtD
You want more ??
Suddenly I cannot scan (HP4620) anymore and the Dell Inspiron Laptop is
behaving unpredictabel
I have not been encountered with a slach overflow for years
I cannot imagine that nobody has not seen this error doing ps -ef
Any help or commend would be usefull
Greetings
Ger van Dijck.
--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
9 years, 8 months
What just happened?
by Tom Horsley
I just installed updates, rebooted (cleanly, as far as I know),
and when the system came back, 1 CPU was pegged at 100% running
rsyslogd. It stayed that way for a minute or two, then went
back to normal. In /var/log/messages, I found this:
Sep 29 07:29:31 tomh rsyslogd-2177: imjournal: begin to drop messages due to rate-limiting
That was the very first message following the boot, most of
the junk that usually shows up on a boot was missing.
The last message prior to that was time stamped Sep 21, so I don't
know where all the messages between the 21st and 29th might
have gone - perhaps someone was saving them up till the next
reboot and that was why the cpu was pegged?
9 years, 8 months
testing of drives!
by bruce
Morning --
Got a situation where we have a number of used/older dell boxes
running centos/fedora (should be the same process of testing the
drives).
Some of the boxes have already had the OS installed/drive
formatted/patitioned/etc.. Some have dual drives.
We realized that we should have tested each drive prior to
installing/formatting/etc..
So, now we're wondering what's the best/god way to test the drives.
We'd like to put together a basic process to allow us to test the
given drive, preferably with the drive in the box/running/formatted so
we don't have to test the drive in a separate box!!
So, any input we can get on software to use, articles to review, etc
in order to get a stable test process to get a good idea of the health
of our drives would be cool
Issues to consider::
-We have running drives, that are partitioned/formatted
-we have drives in systems that we haven't started to use
some primary formatted/some are installed as 2nd drives
we need a way to be able to test all of the drives, preferably
without taking the drive(s) out of a box and testing them in a separate box
Concern is/are:
-bad sectors/blocks
-health of drive
-capacity of drive
-etc..
we've looked into hdparam/smartctl
thanks guys!
9 years, 8 months
battery indicator
by Ranjan Maitra
Hi,
I have a new Dell Precision M3800 laptop and I am trying to figure out
why the battery indicator does not work (find anything). Any suggestions
as to how I can get this going? batti for instance is installed but
finds nothing. However, there is a battery in the laptop, and does hold
charge for a few hours at least.
I am running a fully updated Fedora 20 system.
Any help is of course very appreciated.
Many thanks,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. Please respond to the mailing list if appropriate.
For those needing to send personal or professional e-mail, please use
appropriate addresses.
____________________________________________________________
FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth
9 years, 8 months
fedora20: samba4: getent passwd (and group) not work property
by Dario Lesca
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 ?
Many thanks
--
Dario Lesca
(inviato dal mio Linux Fedora 20 con Gnome 3.10.4)
9 years, 8 months
5tFTW: F21 Alpha, Shellshock, Schedule Docs Update, Flock 2015 Locations, and a Fedora User Committee idea (2014-09-26)
by Matthew Miller
Reposted from <http://fedoramagazine.org/5tftw-2014-09-26/>.
Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to each. Here are the five things for September 18th, 2014:
Fedora 21 Alpha Release!
------------------------
Of course, this week’s big news is the release of Fedora 21 Alpha — the
first formal test release on the way to an early-December final
release. This will be our first release with distinct Cloud, Server,
and Workstation products — a first phase of Fedora.next. Read the F21
Alpha release announcement, and download the flavor you’re interested
in (or launch the cloud image in EC2).
A gigantic thank you and congratulations to all of the Fedora
contributors who made this happen!
* http://fedoraproject.org/wiki/Fedora.next
* https://fedoraproject.org/wiki/F21_Alpha_release_announcement
* http://fedoraproject.org/get-prerelease
* https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#LaunchInstanc...
Shellshock and Fedora
---------------------
And then, this is our *other* big news. By now, this has been
well-covered *everywhere*, but if you haven’t seen it yet, check out
articles tagged `shellshock` on Fedora Magazine to keep your system
safe.
If you’re curious, read my "Shellshock: How does it actually work?"
article, where I attempt to give a satisfying level of detail in a way
that anyone can understand. Also, the Red Hat security blog has a nice
post-incident FAQ, with a lot of other background and information, and
explains the reasoning behind the patch Red Hat developed (which is the
one we are using in Fedora).
You might also be interested Dan Walsh’s blog entry on how SELinux
helps contain this attack — it’s not perfect, but when an exploit is
in the wild, it’s important to have meaningful layers of protection.
And! I’ll be live on the Linux Action Show this Sunday, talking
about Shellshock and other things.
* http://fedoramagazine.org/tag/shellshock/
* http://fedoramagazine.org/shellshock-how-does-it-actually-work/
* https://securityblog.redhat.com/2014/09/26/frequently-asked-questions-abo...
* http://danwalsh.livejournal.com/71122.html
* http://www.jupiterbroadcasting.com/tag/linux-action-show/
In Which Adam Fixes Everything
------------------------------
Fedora QA Community Monkey (no, really, that’s his title) Adam
Williamson apparently does not need to sleep, and in the midst of all of
the Shellshock fun, spent about 36 hours straight cleaning up some of
the documentation in the Fedora wiki around our release schedule and
process. Some of this is only of interest if you’re deeply involved in
Fedora development or QA, but if you’re following Fedora prereleases
(like the alpha!) — and possibly if you have been confused previously —
it’s all a lot better now, with more consistent names and documentation
that actually reflects reality. Take a look at
* http://fedoraproject.org/wiki/Fedora_Release_Life_Cycle
* http://fedoraproject.org/wiki/Milestone_freezes
and about three dozen interlinked pages which are now all nicely
consistent and much more beautiful than they were before. This is a
great example of how "just do it!" works in wikis and open source in
general — some discussion on IRC and mailing lists, but no waiting to
act. Thanks to Adam for seeing a mess and making it better!
Flock Possibilities
-------------------
Flock (our big annual contributor conference) will be held in North
America next summer — but where? We have four bids, all in the United
States:
* Salt Lake City, Utah
https://fedoraproject.org/wiki/Flock2015-SaltLakeCity-proposal
* Colorado Springs, Colorado
https://fedoraproject.org/wiki/Fedoraproject.org/wiki/Flock2015-ColoradoS...
* Rochester, New York
https://fedoraproject.org/wiki/Flock2015-Rochester-proposal
* Cape Cod, Massachusetts
https://fedoraproject.org/wiki/Flock2015-CapeCod-proposal
The Flock planning team is working on putting together a side-by-side
feature and cost comparison, and will soon be running a straw poll to
find the preferences of potential attendees.
Robyn on Distros and DevOps — and User Communication
----------------------------------------------------
Former Fedora Project Leader Robyn Bergeron has an interesting blog
post about "distros and silos, devops and open source". She talks about
several things (all worth reading), but one of the most interesting is
the suggestion she floats for a User Committee. What do you think?
Would a Fedora User Committee help improve our communication and break
down silos?
* http://robyn.io/2014/09/24/distros-and-silos-devops-and-open-source/
----
Repost note: for the past couple of months, I've just been posting this
to the magazine and not reposting to mailing lists. The mailing list
posts weren't getting a lot of response. I'm trying it again this week,
though — let me know if it's useful to have it here. You can also
follow using the RSS feed at <http://fedoramagazine.org/tag/5tftw/feed/>.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 8 months
Fedup 17 to 18 worked, now fedup to 19 fails
by Gary Stainburn
Hi folks.
I'm currently doing this on a local box before moving onto doing it on a
remote virtual server set. I fedup'd from 17 to 18 with only the one problem
where I had to manuall run 'yum clean all' to get things finished.
I'm now trying to do it a second time to go from F18 to F19, but it failed as
shown below. I'm still Googling for an answer but hopefully someone can
help.
Gary
[root@lcomp2 ~]# fedup --network 19
setting up repos...
default-installrepo/metalink |
32 kB 00:00:00
default-installrepo |
3.6 kB 00:00:00
default-installrepo/primary_db |
2.7 MB 00:00:02
fedora/19/i386/metalink |
33 kB 00:00:00
fedora/19/i386 |
4.2 kB 00:00:00
fedora/primary_db |
15 MB 00:00:19
updates/19/i386/metalink |
24 kB 00:00:00
updates/19/i386 |
4.9 kB 00:00:00
updates/primary_db |
9.9 MB 00:00:13
virtualbox/19/i386 |
951 B 00:00:00
virtualbox/primary |
3.9 kB 00:00:00
getting boot images...
.treeinfo.signed |
2.1 kB 00:00:00
Downloading failed: could not verify GPG signature: No public key
[root@lcomp2 ~]# fedup --network 19
setting up repos...
getting boot images...
.treeinfo.signed |
2.1 kB 00:00:00
Downloading failed: could not verify GPG signature: No public key
[root@lcomp2 ~]#
9 years, 8 months
