date:20151110

Thanks for a GREAT update to 23!

2015-11-10 Thread Wade Hampton

Thanks for a GREAT update to 23!

For the first time in a long while, I had very few issues upgrading
from earlier Fedora releases to the latest version.  Over the weekend,
I updated two computers from F21 to F23 with only a few minor issues.

The F21 laptop was installed from F21 media a few months ago
and the update was smooth except for changing the way the mouse
operated -- I had to click on the window bar to raise windows (now fixed).

The F21 desktop has been repeatedly updated since about F13.  Most
previous updates were painful.  This time, I had to remove a few programs
including google-earth, then the update worked seamlessly.
(I have yet to test Xilinx, Arduino, Maple, and STM tools.)

Thanks!
--
Wade Hampton
-- 
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: Thanks for a GREAT update to 23!

2015-11-10 Thread Matthew Miller

On Tue, Nov 10, 2015 at 11:07:52AM -0500, Wade Hampton wrote:
> Thanks for a GREAT update to 23!

Cool -- glad it went smoothly for you.

> The F21 desktop has been repeatedly updated since about F13.  Most

That's pretty impressive in itself!


-- 
Matthew Miller

Fedora Project Leader
-- 
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

No sound on Fedora 21

2015-11-10 Thread Frank McCormick


I am running Fedora 21 and after the latest updates I have no sound
on my machine.

aplay -l shows no sound cards. Mixers such as alsamixer show only Pulseaudio
master and the output is full.

Can someone suggest how to debug this ?

Thanks

--
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: Is upgrading to fedora 23 safe?

2015-11-10 Thread Matthew Miller

On Sat, Nov 07, 2015 at 12:08:23PM -0600, Ranjan Maitra wrote:
> So, I have been only doing the following:
> 
> sudo dnf distro-sync --releasever=23
> 
> on my fully updated F22 systems. This appears to avert the
> possibility of a system that is unusable while being upgraded. What
> are the pitfalls with my approach?

Usually works fine. However, it is somewhat less safe, the system is in
an inconsistent state until you reboot, with no easy way to distinguish
which processes are using new and old versions of libraries. 

Also, and best, if you're using btrfs, systemd will make a snapshot,
and so you'll get either an upgraded system... or if there's a problem,
no change. Unfortuantely, there are _other_ problems with btrfs, so
that's not the default (or recommended). Possibly we'll have this same
functionality with LVM in the future.

-- 
Matthew Miller

Fedora Project Leader
-- 
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: [389-users] multimaster replication and index corruption

2015-11-10 Thread Rich Megginson

On 11/10/2015 10:14 AM, Adrian Damian wrote:

Rich,

Thanks for your help. Let me jump in with more details.

We've seen index corruption on a number of occasions. It seems to
affect searchable attributes for which there are indexes. Queries on
an attribute in LDAP that used to work suddenly stopped working. They
would return incomplete results and no results at all, although the
data on the server was the same. The fix on those situations was to
drop the index corresponding to the attribute and re-create it.

So in this case, you have some sort of LDAP search client, and you are
doing a search for '(indexed_attribute=known_value)' and you are not
seeing a result, and this is what you mean by "index corruption"?

Are you aware of the dbscan tool?
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Configuration_Command_and_File_Reference/dbscan.html

This tool allows you to examine the index file in the database directly.

dbscan -f
/var/lib/dirsrv/slapd-instance_name/db/userRoot/indexed_attribute.db4 -k
known_value

This will allow you to look at the indexed_attribute index directly for
the value "known_value".

We've run the db fix script that the LDAP distribution comes with

What db fix script? Do you have a link to it, or a link to the product
documentation for the script?

and there are no reports of corruption when this problem occurs. That
makes it very hard to detect. We don't know what else to look for when
we run into this again and more importantly, we don't know what
triggers it and how to prevent it.

Mind you we are currently doing active development changing both the
software clients that access the LDAP servers as well as the
configurations of the servers. It is possible to had been written to
both masters in the master replication configuration when the problem
occurred but because there were multiple clients concurrently
accessing the servers it is hard to figure out what triggered the issue.

Adrian

On 11/09/2015 05:06 PM, Rich Megginson wrote:

On 11/09/2015 05:47 PM, Ghiurea, Isabella wrote:

Hi Rich,
Thank you for your feedback , as always greatly appreciate when
comes from 389-DS RH support.
We are not using vm just plain hardware, here is the description
I got from developers team related to the issues they are seeing
when running integration tests with multimaster replication :
"index corruption: put content, run tests: OK, do more stuff (reads,
writes, etc), ru tests: FAIL, notice "missing attributes", rebuild
index(ices), run tests: OK. "

What does this mean? What program is printing these index corruption
messages? Is it some tool provided by Red Hat?

Unfortunately, I understood this cases/issue can not be reproduce
on regular basis, no mode details can be provide at this time

Here is the DS version:
rpm -qa | grep 389-ds
389-ds-console-doc-1.2.6-1.el6.noarch
389-ds-base-libs-1.2.11.15-34.el6_5.x86_64
389-ds-1.2.2-1.el6.noarch
389-ds-base-1.2.11.15-34.el6_5.x86_64

This is quite an old version of 389-ds-base. I suggest upgrading to
RHEL 6.7 with latest patches.

389-ds-console-1.2.6-1.el6.noarch

Thank you
Isabella

FWD:

What version of 389? rpm -q 389-ds-base
I'm assuming you are not using IPA.
What does "index corruption" mean? What exactly do you see?

Are you running in virtual machines? If so, what kind? vmware? kvm?
Are you using virtual disks or dedicated physical devices/paravirt?

We are writing to only one DS , same server at all time but reading
from all DS 's cfg for mutlmaster.
Are you seeing "index corruption" on the write master or on all
servers?

Are other people seen this kind of issues with multimaster rep cfg ,
should we start avoiding this replication cfg at all ?

This is the recommended way to deploy. If this is not working for
you, either you have a configuration problem, or there is some sort
of vm or hardware problem, or there is a serious bug that requires
fixing ASAP.

We choose the multimaster for the fast and reliable option to switch
between master DS's , moving one step down to master/slave may
require some down time when switching DS's back.

Isabella

Re: [389-users] multimaster replication and index corruption

2015-11-10 Thread Adrian Damian


Rich,

Thanks for your help. Let me jump in with more details.

We've seen index corruption on a number of occasions. It seems to affect 
searchable attributes for which there are indexes. Queries on an 
attribute in LDAP that used to work suddenly stopped working. They would 
return incomplete results and no results at all, although the data on 
the server was the same. The fix on those situations was to drop the 
index corresponding to the attribute and re-create it.


We've run the db fix script that the LDAP distribution comes with and 
there are no reports of corruption when this problem occurs. That makes 
it very hard to detect. We don't know what else to look for when we run 
into this again and more importantly, we don't know what triggers it and 
how to prevent it.


Mind you we are currently doing active development changing both the 
software clients that access the LDAP servers as well as the 
configurations of the servers. It is possible to had been written to 
both masters in the master replication configuration when the problem 
occurred but because there were multiple clients concurrently accessing 
the servers it is hard to figure out what triggered the issue.



Adrian



On 11/09/2015 05:06 PM, Rich Megginson wrote:

On 11/09/2015 05:47 PM, Ghiurea, Isabella wrote:

Hi Rich,
Thank you for your feedback , as always greatly appreciate when comes from  
389-DS RH support.
We are  not using vm just plain hardware, here is the description  I  got from developers team 
related to the issues they are seeing when running   integration tests with multimaster replication 
: "index corruption: put content, run tests: OK, do more stuff (reads, writes, etc), ru tests: 
FAIL, notice "missing attributes", rebuild index(ices), run tests: OK. "

What does this mean?  What program is printing these index corruption
messages?  Is it some tool provided by Red Hat?


Unfortunately, I understood  this   cases/issue can not be reproduce on regular 
basis,  no mode details can be provide at this time

All reads and writes are going to  only the master replication DS, not slave .
I totally agree with your this is the way to cfg and maintain Directory  
Server in a operation critical  env: multmaster replication only one master for 
writes.
   Here is the DS version:
   rpm -qa | grep 389-ds
389-ds-console-doc-1.2.6-1.el6.noarch
389-ds-base-libs-1.2.11.15-34.el6_5.x86_64
389-ds-1.2.2-1.el6.noarch
389-ds-base-1.2.11.15-34.el6_5.x86_64

This is quite an old version of 389-ds-base.  I suggest upgrading to
RHEL 6.7 with latest patches.


389-ds-console-1.2.6-1.el6.noarch


Thank you
Isabella

FWD:
   



We have cfg multimaster replication /fractional replication memberof plugging 
excluded , we are seeing from time to time index corruption with some indexes , 
there is a strong feeling from developers this are related to DS multimaster 
replication internal settings.
What version of 389?  rpm -q 389-ds-base
I'm assuming you are not using IPA.
What does "index corruption" mean?  What exactly do you see?

Are you running in virtual machines? If so, what kind? vmware? kvm? Are you 
using virtual disks or dedicated physical devices/paravirt?

We are writing to only one DS , same server at all time but reading from all DS 
's cfg for mutlmaster.
Are you seeing "index corruption" on the write master or on all servers?


Are other people seen this kind of issues with multimaster rep cfg , should we 
start avoiding this replication cfg at all ?

This is the recommended way to deploy. If this is not working for you, either 
you have a configuration problem, or there is some sort of vm or hardware 
problem, or there is a serious bug that requires fixing ASAP.

We choose the multimaster for the fast and reliable option to switch between 
master DS's , moving one step down to master/slave may require some down time 
when switching DS's back.
Isabella





Hi Rich,
Thank you for your feedback , as always greatly appreciate when comes from  
389-DS RH support.
We are  not using vm just plain hardware, here is the description  I  got from developers 
team related to the issues they are seeing when running  tests with multimaster 
replication  :index corruption: put content, run tests: OK, do more stuff (reads, writes, 
etc), ru tests: FAIL, notice "missing attributes", rebuild index(ices), run 
tests: OK.

I belive we the reads and writes right now are only the master replication DS , 
not slave .
I totally agree with your this is the way to cfg and maint DS in a operation 
env: multmaster replication with one master for writes.
More comments , imput I appreciate
   rpm -qa | grep 389-ds
389-ds-console-doc-1.2.6-1.el6.noarch
389-ds-base-libs-1.2.11.15-34.el6_5.x86_64
389-ds-1.2.2-1.el6.noarch
389-ds-base-1.2.11.15-34.el6_5.x86_64
389-ds-console-1.2.6-1.el6.noarch
389-dsgw-1.1.11-1.el6.x86_64


From: ghiureai [isabella.ghiu...@nrc-cnrc.gc.ca]
Sent: Monday, November 09, 2015 1:05 PM
To:

Re: No sound on Fedora 21

2015-11-10 Thread Frank McCormick


On 11/10/2015 01:36 PM, Emmett Culley wrote:

On 11/10/2015 07:32 AM, Frank McCormick wrote:

I am running Fedora 21 and after the latest updates I have no sound
on my machine.

aplay -l shows no sound cards. Mixers such as alsamixer show only Pulseaudio
master and the output is full.

Can someone suggest how to debug this ?

Thanks


This happened to me as well.  Then I noticed that I was booting to a old Fedora 
22 kernel (4.0.1-100.  Upon investigation I found some strange entries in 
grub.conf.  Strange in that there were references to the Fedroa 22 kernel.

Removing those reference didn't help.  Neither did selecting an older (F21) 
kernel from the list help, as the system would not boot at all.  I was left 
with a dracut prompt.

I lost sound, and all USB support.  Plus my network failed to start as it 
appeared that bridge support was missing.

Finally I installed grub again on /dev/sda and now I am booting to 
4.1.10-100-f21 as expected and everything works again.

Emmett


   That's almost identical to what happened to me...except I only lost 
sound and it only happened after
I installed grub from my Debian Sid partition. Once I re-installed it 
from Fedora, the sound problem disappeared.
But then I had no entry in the menu for Windows. So I re-ran 
grub2-mkconfig and Windows re-appeared!!


I'd file a bug except I don't know whether it's a Debian problem or a 
Fedora problem. There must be some
incompatibility between grub in both systems. I guess I'll just leave 
grub installed from Fedora.


I wish there were a better way to handle two partitions of different 
Linux's.



--
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: No sound on Fedora 21

2015-11-10 Thread Emmett Culley

On 11/10/2015 07:32 AM, Frank McCormick wrote:
> I am running Fedora 21 and after the latest updates I have no sound
> on my machine.
> 
> aplay -l shows no sound cards. Mixers such as alsamixer show only Pulseaudio
> master and the output is full.
> 
> Can someone suggest how to debug this ?
> 
> Thanks
> 
This happened to me as well.  Then I noticed that I was booting to a old Fedora 
22 kernel (4.0.1-100.  Upon investigation I found some strange entries in 
grub.conf.  Strange in that there were references to the Fedroa 22 kernel.

Removing those reference didn't help.  Neither did selecting an older (F21) 
kernel from the list help, as the system would not boot at all.  I was left 
with a dracut prompt.

I lost sound, and all USB support.  Plus my network failed to start as it 
appeared that bridge support was missing.

Finally I installed grub again on /dev/sda and now I am booting to 
4.1.10-100-f21 as expected and everything works again.

Emmett
-- 
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

No sound on Fedora 21 solved

2015-11-10 Thread Frank McCormick



I figured out what was wrong. After the recent updates I changed the
grub installation to grub on my Debian partition. Everything
seemed to go well until todays sound problems. lsmod showed
there were NO sound modules loaded and uname -a showed a strange
kernel version.

I reinstalled grub from Fedora. Sound is back, lsmod shows
all the needed sound modules loaded.

Now there is another minor problem. With this version of
grub running, grub.cfg does not show my Windows 7 installation...just 
Fedora and Debian.



Help ?


Thanks






















I am running Fedora 21 and after the latest updates I have no sound
on my machine.

aplay -l shows no sound cards. Mixers such as alsamixer show only Pulseaudio
master and the output is full.

Can someone suggest how to debug this ?

Thanks

--
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

gnuplot help

2015-11-10 Thread Antonio Olivares

Dear Fedora users,

Any gnuplot experts out there. I have a situation which I can plot using
plotshare

http://plotshare.com/index.ws/plot/338384601

but when I run it in regular gnuplot, I get mistakes. I would like to improve
the script in order to better show the graphics. I copied the style from

http://plotshare.com/index.ws/plot/672940882

The only one that works is the following one:

http://plotshare.com/index.ws/plot/858779550

I wanted to change it, put the dates and the opponent and make it look like a
bar graph. I tried modifing the code and add the style used by Marco F. a
fellow Fedora/open source user:

http://www.techrepublic.com/blog/linux-and-open-source/how-to-handle-time-based-data-with-gnuplot/

But I cannot get it to work. I am using Fedora 22 in case it is important.
BTW(the awk scripts that some list members helped me with have me setup and
ready for the start of the soccer season) Now I just want to show our players
to get ready and show them the goal differential and see visually what we need
to work on.

Best Regards,

Antonio

FREE ONLINE PHOTOSHARING - Share your photos online with your friends and
family!
Visit http://www.inbox.com/photosharing to find out more!

--
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: No sound on Fedora 21 solved

2015-11-10 Thread stan

On Tue, 10 Nov 2015 12:43:13 -0500
Frank McCormick  wrote:

> I reinstalled grub from Fedora. Sound is back, lsmod shows
> all the needed sound modules loaded.
> 
> Now there is another minor problem. With this version of
> grub running, grub.cfg does not show my Windows 7 installation...just 
> Fedora and Debian.
> 
> 
> Help ?

If you are booting from BIOS (not EFI), go into the directory 
/boot/grub2, and run grub2-mkconfig -o grub.cfg, that should
create a grub.cfg that has all recognizable OS partitions on your
system.

If you are running EFI, someone else will have to help as my knowledge
of that is almost nothing.
-- 
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: [389-users] multimaster replication and index corruption

2015-11-10 Thread Rich Megginson

On 11/10/2015 12:12 PM, ghiureai wrote:

Rich, thank you for all support for last day , unfortunately there is
a strong wave in developers team:" the multimaster replication is
creating issues with UI" ( I do not totally agree since can not be
reproduce+ full describe the issues).
Is been decided to moved down to master slave, please I need to know
if I still need to exclude member of plugin from replication in this
case ?

Adding 389-users to discussion.

I would say yes, you should still exclude memberOf from replication. In
any case, it is better to reduce the amount of replication traffic and
replication processing, and let the slave calculate the memberOf values.

As far as the original issue - if we can't get enough information to
diagnose/reproduce the problem, then we can be of little help.

Thanks a lot
Isabella
On 11/10/2015 09:23 AM, Rich Megginson wrote:

On 11/10/2015 10:14 AM, Adrian Damian wrote:

Rich,

Thanks for your help. Let me jump in with more details.

Are you aware of the dbscan tool?
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Configuration_Command_and_File_Reference/dbscan.html

This tool allows you to examine the index file in the database directly.

dbscan -f
/var/lib/dirsrv/slapd-instance_name/db/userRoot/indexed_attribute.db4 -k
known_value

This will allow you to look at the indexed_attribute index directly for
the value "known_value".

We've run the db fix script that the LDAP distribution comes with

What db fix script? Do you have a link to it, or a link to the product
documentation for the script?

Adrian

On 11/09/2015 05:06 PM, Rich Megginson wrote:

On 11/09/2015 05:47 PM, Ghiurea, Isabella wrote:

What does this mean? What program is printing these index corruption
messages? Is it some tool provided by Red Hat?

Unfortunately, I understood this cases/issue can not be reproduce
on regular basis, no mode details can be provide at this time

All reads and writes are going to only the master replication DS,
not slave .
I totally agree with your this is the way to cfg and maintain
Directory Server in a operation critical env: multmaster
replication only one master for writes.
Here is the DS version:
rpm -qa | grep 389-ds
389-ds-console-doc-1.2.6-1.el6.noarch
389-ds-base-libs-1.2.11.15-34.el6_5.x86_64
389-ds-1.2.2-1.el6.noarch
389-ds-base-1.2.11.15-34.el6_5.x86_64

This is quite an old version of 389-ds-base. I suggest upgrading to
RHEL 6.7 with latest patches.

389-ds-console-1.2.6-1.el6.noarch

Thank you
Isabella

FWD:

We have cfg multimaster replication /fractional replication memberof
plugging excluded , we are seeing from time to time index corruption
with some indexes , there is a strong feeling from developers this
are related to DS multimaster replication internal settings.
What version of 389? rpm -q 389-ds-base
I'm assuming you are not using IPA.
What does "index corruption" mean? What exactly do you see?

Are you running in virtual machines? If so, what kind? vmware? kvm?
Are you using virtual disks or dedicated physical devices/paravirt?

We are writing to only one DS , same server at all time but reading
from all DS 's cfg for mutlmaster.
Are you seeing "index

Re: Thanks for a GREAT update to 23!

2015-11-10 Thread François Patte

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Le 10/11/2015 17:07, Wade Hampton a écrit :
> Thanks for a GREAT update to 23!
> 
> For the first time in a long while, I had very few issues
> upgrading from earlier Fedora releases to the latest version.  Over
> the weekend, I updated two computers from F21 to F23 with only a
> few minor issues.
> 
> The F21 laptop was installed from F21 media a few months ago and
> the update was smooth except for changing the way the mouse 
> operated -- I had to click on the window bar to raise windows (now
> fixed).
> 
> The F21 desktop has been repeatedly updated since about F13.  Most
>  previous updates were painful.  This time, I had to remove a few
> programs including google-earth, then the update worked seamlessly.
>  (I have yet to test Xilinx, Arduino, Maple, and STM tools.)

Seems to be nice indeed! But, what did you exactly do?

- -- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlZCZyMACgkQdE6C2dhV2JVDewCgr9VvKTLmfPx2ymGKxYz7gkzB
ALgAn0sXw3H0W8FpuNx1iFmZWVGi0/a1
=x7fA
-END PGP SIGNATURE-
-- 
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: Thanks for a GREAT update to 23!

2015-11-10 Thread Sylvia Sánchez

Reading this makes me really happy. I used to make a clean install,
but now I think that I'll try an upgrade. When the time comes, I
already have Cinnamon Spin 23 and I must say that it works smoothly.
Except for Nemo that is failing randomly. But isn't Fedora fault,
happened the same and worse on Manjaro.



Cheers,
Sylvia
-- 
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: Thanks for a GREAT update to 23!

2015-11-10 Thread Max Pyziur



Just to join in the fun and dancing:

Three machines: one home-assembled desktop (i5, 8GG RAM, etc); two Dell 
laptops: D630 (Core 2 Duo CPU, 4GB RAM; E6220 - i5 CPU, 8GB RAM).



Started w/ the Desktop and made three efforts; on the first, it ended 
challenging me to remove a perl-DBD-Pg-Test-FC21 package; on the second, 
to remove google-earth-stable, on the third, it completed correctly.


However, on each try, a full download of all necessary packages was 
necessary, requiring two hours each time (old school Verizon DSL).


(Was it necessary to do complete downloads? Couldn't these things have 
been cached for the next effort?)


Having learned the lessons of upgrading the desktop, upgrading the E6220 
from F22 to F23 went correctly.


The D630 needed to move from F21->F22->F23. The problem there was that on 
F21, the Postgresql database version is incompatible (don't have the 
numbers in my head) w/ that of F22 and F23. Somewhere there should be a 
preamble on the next upgrade iteration that these sorts of things (those 
PostgreSQL upgrades that require a backup-and-restore) need to be done 
prior to advancing in Fedora releases. A nuisance (given that I have 
backups and some experience) that probably took 15 minutes to handle.


fyi,

MP

--
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

xorg 1.18 released

2015-11-10 Thread Tom Horsley

I see the official announcement of xorg server 1.18:

http://lists.x.org/archives/xorg-announce/2015-November/002655.html

Anyone have any clues about when the final release
will show up in fedora 23, and vastly more important,
when nvidia binary drivers will show up now that 1.18
is official?

P.S. I'd vastly prefer to use the nouveau open
source driver, but my maxwell card won't talk
nouveau unless nvidia releases the firmware
in some form nouveau can use, so I'm stuck
waiting for nvidia either way :-).
-- 
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: gnuplot help

2015-11-10 Thread M. Fioretti

On 2015-11-10 19:04, Antonio Olivares wrote:

The only one that works is the following one:

http://plotshare.com/index.ws/plot/858779550

I wanted to change it, put the dates and the opponent and make it look
like a bar graph. I tried modifing the code and add the style used by
Marco F. a fellow Fedora/open source user:

http://www.techrepublic.com/blog/linux-and-open-source/how-to-handle-time-based-data-with-gnuplot/

But I cannot get it to work.

Hi Antonio,
"Marco F. a fellow Fedora/open source user" here. Thanks for
your interest in my pieces.

It's been a while since I last seriously worked with Gnuplot,
so I am not really current about it anymore, and cannot
promise anything :-) Whoever is more up to date than me, please step in!

This said, my understanding is that the actual code you are trying to
make

work is NOT the one visible at the plotshare urls you provided,
which is only an example.

Is this correct? If yes, I (and I think the others too) would need to
see the WHOLE gnuplot code and data files that you tried to run, and
the complete error message you get. If I'm wrong, please explain. In
any case, we'd need to see at least the complete error message, to
continue.

HTH,
Marco

--
http://mfioretti.com
--
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: xorg 1.18 released

2015-11-10 Thread Ed Greshko



On 11/11/15 10:12, Tom Horsley wrote:
> I see the official announcement of xorg server 1.18:
>
> http://lists.x.org/archives/xorg-announce/2015-November/002655.html
>
> Anyone have any clues about when the final release
> will show up in fedora 23, and vastly more important,
> when nvidia binary drivers will show up now that 1.18
> is official?
>
> P.S. I'd vastly prefer to use the nouveau open
> source driver, but my maxwell card won't talk
> nouveau unless nvidia releases the firmware
> in some form nouveau can use, so I'm stuck
> waiting for nvidia either way :-).

You should probably use https://www.changedetection.com and monitor
http://www.nvidia.com/object/unix.html for changes to see when they release a 
new driver. 
And then you can bug the folks at rpmfusion.

-- 
In reality, some people should stick to running Windows and others should stay 
away from
computers altogether.
-- 
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

Thanks for a GREAT update to 23!

Re: Thanks for a GREAT update to 23!

No sound on Fedora 21

Re: Is upgrading to fedora 23 safe?

Re: [389-users] multimaster replication and index corruption

Re: [389-users] multimaster replication and index corruption

Re: No sound on Fedora 21

Re: No sound on Fedora 21

No sound on Fedora 21 solved

gnuplot help

Re: No sound on Fedora 21 solved

Re: [389-users] multimaster replication and index corruption

Re: Thanks for a GREAT update to 23!

Re: Thanks for a GREAT update to 23!

Re: Thanks for a GREAT update to 23!

xorg 1.18 released

Re: gnuplot help

Re: xorg 1.18 released

18 matches

Site Navigation

Mail list logo

Footer information