Re: fedup from 20 to 21

[Matthew Miller]

On Fri, Nov 18, 2016 at 02:02:39PM -0700, jd1008 wrote:
> How about updating f20 to 21 with
> yum -y upgrade --releasever=21
> Would that work?

Probably -- see the caveats at
https://fedoraproject.org/wiki/Upgrading_Fedora_using_package_manager.

Additionally, old releases are moved off of the mirrors (to save
hundreds of terabytes of disk space worldwide), so you'll need to
update your repo files to point to
http://archive.fedoraproject.org/pub/archive/fedora/linux/updates/.

Again at some point this becomes more work than just doing a fresh
install. :)

-- 
Matthew Miller

Fedora Project Leader
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Rick Stevens]

On 11/18/2016 01:02 PM, jd1008 wrote:
> 
> On 11/18/2016 01:32 PM, Matthew Miller wrote:
>> On Tue, Nov 15, 2016 at 11:57:08AM +, Patrick O'Callaghan wrote:
>>> 20 -> 21
>>> 21 -> 22
>>> 22 -> 23
>>> 23 -> 24
>>> 24 -> 25
>>> The first few will use Fedup, the later ones will use dnf. The chances
>> The dnf system update plugin was added as an update to F21, so it's
>> only the first hop that will be different. That said, I agree with the
>> conclusion -- especially with the lack of space, a new install is
>> probably the best way.
>>
> How about updating f20 to 21 with
> yum -y upgrade --releasever=21

Assuming one has all the intervening DVDs and does the upgrades using
"local media", I imagine you could do it. I think Fedora releases that
old typically can't be upgraded via the network as the repos are
archived and not active anymore.

That all being said, 20->21->22->23->24 is going to be an incredibly,
tedious, time-consuming process fraught with errors and problems. A
fresh install would be much quicker.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- If at first you don't succeed, quit. No sense being a damned fool! -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[jd1008]

On 11/18/2016 01:32 PM, Matthew Miller wrote:

On Tue, Nov 15, 2016 at 11:57:08AM +, Patrick O'Callaghan wrote:

20 -> 21
21 -> 22
22 -> 23
23 -> 24
24 -> 25
The first few will use Fedup, the later ones will use dnf. The chances

The dnf system update plugin was added as an update to F21, so it's
only the first hop that will be different. That said, I agree with the
conclusion -- especially with the lack of space, a new install is
probably the best way.


How about updating f20 to 21 with
yum -y upgrade --releasever=21

Would that work?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Matthew Miller]

On Tue, Nov 15, 2016 at 11:57:08AM +, Patrick O'Callaghan wrote:
> 20 -> 21
> 21 -> 22
> 22 -> 23
> 23 -> 24
> 24 -> 25
> The first few will use Fedup, the later ones will use dnf. The chances

The dnf system update plugin was added as an update to F21, so it's
only the first hop that will be different. That said, I agree with the
conclusion -- especially with the lack of space, a new install is
probably the best way.

-- 
Matthew Miller
<mat...@fedoraproject.org>
Fedora Project Leader
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Matthew Miller]

On Tue, Nov 15, 2016 at 10:28:09AM +, Gary Stainburn wrote:
> As someone who has a F21 server that I was just thinking of fedup'ing,

So, not that this is recommended, but Adam Williamson recently posted
about successfully upgrading from Fedora 13 to Fedora 25. So... this is
possible. You're just likely to run into some odd situations and need
to do cleanup along the way, and it's hard to predict exactly what.

> what would be my best choice?  (I really don't want to do a clean install)

Aspirationally, the best choice is to get your server to the point
where a clean install is no big deal — user and system-local data all
in /home and/or /srv, all configuration done with Ansible playbooks (or
other config management), etc.

But, not everyone is there :) so, in your case, I think I'd try two
hops -- we do support 'N-2' upgrades -- so you can go to F23 and then
F25 from there. F21 includes dnf system upgrade, so it'll be the same
for both steps. You might also just be fine doing it all in one go.

-- 
Matthew Miller

Fedora Project Leader
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Tim]

Allegedly, on or about 15 November 2016, Gary Stainburn sent:
> As someone who has a F21 server that I was just thinking of fedup'ing,
> what would be my best choice?  (I really don't want to do a clean
> install) 

I really just cannot imagine going through several updates-over-the-top,
to get from a quite out-of-date to a current release, is going to be
easier than a fresh install then customise it.

The updates are a nuisance, even if they go through without new bugs for
you to deal with (some completely new, others related to incompatibility
with what's left behind from previous installs).  Time-consuming,
storage-space-consuming, etc.  And to have to do that several times
over.  Once is annoying enough (I stopped trying to do that years ago).

Not to mention that there's a very good chance that as you go through
different releases, you'll strike things that cause new problems, with
each release.  Dropped and changed packages, may remove things you
wanted, or make them incompatible with past data.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

The internet, your opportunity to learn from other peoples' mistakes.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Patrick O'Callaghan]

On Tue, 2016-11-15 at 12:35 +0100, luca paganotti wrote:
> Sure, fedup doesn't edit my scripts, but should update my system ...

Neither Fedup nor dnf is guaranteed to work when skipping versions, so
to get from 20 to 24 (or 25) you will probably have to do several
stages:

20 -> 21
21 -> 22
22 -> 23
23 -> 24
24 -> 25

The first few will use Fedup, the later ones will use dnf. The chances
of having a problem increase with the number of stages, even after you
solve your first problem (which is simply lack of space). I'm not
saying it will happen, but it might. Every new release of Fedora brings
a spate of emails from people who have had issues with upgrading (of
course those who don't have a problem tend not to talk about it as much
and I personally have only had good experiences). That's why I suggest
that you simply reinstall. In the end it will probably be easier.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[luca paganotti]

Sure, fedup doesn't edit my scripts, but should update my system ...






On Tue, Nov 15, 2016 at 12:31 PM, Patrick O'Callaghan <pocallag...@gmail.com
> wrote:

> On Tue, 2016-11-15 at 11:07 +, luca.pagano...@gmail.com wrote:
> > If I have to make my machine from scratch, I'm thinking to switch to
> debian after twenty years of fedora usage ...
>
> Your choice of course. Using Fedora means being prepared to upgrade
> your system at least every year. If you aren't prepared to do that,
> then you are probably better using a system with greater long term
> stability. A good choice might be CentOS as it's quite similar to
> Fedora.
>
> However no-one is saying you have to "make your machine from scratch".
> If you are taking regular backups you are already prepared for the
> possibility of losing a disk or upgrading to a new machine.
> Reinstalling the system is generally easier than either of those
> scenarios. If some home-grown scripts have to change, they would still
> have to change going the upgrade path because Fedup (or dnf) is not
> going to edit them for you.
>
> poc
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Patrick O'Callaghan]

On Tue, 2016-11-15 at 11:07 +, luca.pagano...@gmail.com wrote:
> If I have to make my machine from scratch, I'm thinking to switch to debian 
> after twenty years of fedora usage ...

Your choice of course. Using Fedora means being prepared to upgrade
your system at least every year. If you aren't prepared to do that,
then you are probably better using a system with greater long term
stability. A good choice might be CentOS as it's quite similar to
Fedora.

However no-one is saying you have to "make your machine from scratch".
If you are taking regular backups you are already prepared for the
possibility of losing a disk or upgrading to a new machine.
Reinstalling the system is generally easier than either of those
scenarios. If some home-grown scripts have to change, they would still
have to change going the upgrade path because Fedup (or dnf) is not
going to edit them for you.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[luca . paganotti]

If I have to make my machine from scratch, I'm thinking to switch to debian 
after twenty years of fedora usage ...
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[luca paganotti]

Hi Patrick, thank you for your answer.
I've tons of script an personal data and programs, isn't there a way to
gradually upgrate to the latest release? I do not want to loos e any of my
personal data and configurations, is it enough to backup my home folder?
I've databasese and so on ... I should to remake my machine from scratch?






On Tue, Nov 15, 2016 at 11:14 AM, Patrick O'Callaghan <pocallag...@gmail.com
> wrote:

> On Tue, 2016-11-15 at 10:07 +, luca.pagano...@gmail.com wrote:
> > fedup upgrade stuck at "Welcome to fedup-dracut-0.9.0!"
> >
> > after moving mounts into /system-upgrade-root
> > /boot/efi
> > /boot
> > and /home
> > upgrade prep complete, switching to root ...
> >
> > Welcome to fedup-dracut-0.9.0!
> >
> > no other life signal ...
> >
> > what to do?
>
> The current release of Fedora is 24, and will be 25 in the next few
> days (maybe even today). 20 and 21 stopped receiving any support a long
> time ago. Fedup is no longer even used as the upgrade method. In your
> situation you are almost certainly better just doing a fresh install of
> the latest Fedora, after backing up your data of course.
>
> poc
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Gary Stainburn]

On Tuesday 15 November 2016 10:14:46 Patrick O'Callaghan wrote:
> The current release of Fedora is 24, and will be 25 in the next few
> days (maybe even today). 20 and 21 stopped receiving any support a long
> time ago. Fedup is no longer even used as the upgrade method. In your
> situation you are almost certainly better just doing a fresh install of
> the latest Fedora, after backing up your data of course.

As someone who has a F21 server that I was just thinking of fedup'ing,

what would be my best choice?  (I really don't want to do a clean install)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[Patrick O'Callaghan]

On Tue, 2016-11-15 at 10:07 +, luca.pagano...@gmail.com wrote:
> fedup upgrade stuck at "Welcome to fedup-dracut-0.9.0!"
> 
> after moving mounts into /system-upgrade-root
> /boot/efi
> /boot
> and /home
> upgrade prep complete, switching to root ...
> 
> Welcome to fedup-dracut-0.9.0!
> 
> no other life signal ...
> 
> what to do?

The current release of Fedora is 24, and will be 25 in the next few
days (maybe even today). 20 and 21 stopped receiving any support a long
time ago. Fedup is no longer even used as the upgrade method. In your
situation you are almost certainly better just doing a fresh install of
the latest Fedora, after backing up your data of course.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[luca . paganotti]

fedup upgrade stuck at "Welcome to fedup-dracut-0.9.0!"

after moving mounts into /system-upgrade-root
/boot/efi
/boot
and /home
upgrade prep complete, switching to root ...

Welcome to fedup-dracut-0.9.0!

no other life signal ...

what to do?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[luca . paganotti]

I've found two folders /var/lib/system-upgrade containing a .conf file and 
/var/cache/system/upgrade containing the new packages. Can I symlink these two 
folders?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: fedup from 20 to 21

[luca . paganotti]

The command I issue is sudo fedup --network 21 --product=workstation
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

fedup from 20 to 21

[luca . paganotti]

Hi, upgrading from fedora 20 to fedora 21 using fedup I encounter an error. 
I issue the following command and after downloading all the rpm files there is 
an upgrade test that fails in this way

Upgrade test failed with the following problems:
insufficient disk space:
  / needs 3.2G more free space
fedup ERROR: Upgrade test failed.

I don't know how to manage this problems, googling tells me to find two folders 
/var/tmp/fedora-release and /var/lib/fedora-release, to copy them in the home 
directory where I have enough space and make symbolic liks to these two 
folders. The problem are that I'm not able to find /var/tmp/fedora-release and 
/var/lib/fedora-release, I'm not able to locate where fedup has store the new 
F21 rpm files, and then I don't know how to free the fedup needed space 3.2 Gb.

Thanks for any answer and sorry for my english.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[Greg Woods]

On Mon, Nov 7, 2016 at 7:33 AM, joev.8450  wrote:

> doesn't the nVidia installer uninstall everything nvidia before it
> installs the version in the invoked installer run file?


I wouldn't know as I always install everything from packages, and that's
what Mark is doing as well. For me, I use rpmfusion as the repo and they
maintain Nvidia driver packages. I don't know exactly why this happens, but
I have seen cases where updating a kernel and installing the new driver
with a normal "dnf update" puts the Nvidia stuff in a screwed-up state
where GNOME won't work. The way I have fixed it is just "dnf remove
*nvidia*" and then reinstall the nvidia packages I need from scratch.

--Greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[Mark]

On Mon, 2016-11-07 at 09:33 -0500, joev.8450 wrote:
> doesn't the nVidia installer uninstall everything nvidia before it
> installs the version in the invoked installer run file?  I mean is
> there
> something else I should invoke or do to make sure I've uninstalled
> everything nvidia?  I'm having somewhat of a similar problem but
> re-running the installer which tells me it is uninstalling the
> installed
> version isn't helping.

What I did was to use 'rpm -e' to remove all nvidia related packages
and then 'yum install' to get those same packages back.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[joev.8450]

doesn't the nVidia installer uninstall everything nvidia before it
installs the version in the invoked installer run file?  I mean is there
something else I should invoke or do to make sure I've uninstalled
everything nvidia?  I'm having somewhat of a similar problem but
re-running the installer which tells me it is uninstalling the installed
version isn't helping.

regards,

Joe Verreau
Durand, MI

On 11/04/2016 09:23 AM, Mark wrote:
> On Thu, 2016-11-03 at 12:28 -0600, Greg Woods wrote:
>> On Thu, Nov 3, 2016 at 11:30 AM, Mark 
>> wrote:
>>
>>> All I got was a grey page with the text "Oh no! Something has
>>> gone wrong.
>>>
>> When using the Nvidia proprietary driver, when I have this happen,
>> the only
>> way I have successfully recovered is to uninstall everything *nvidia*
>> and
>> reinstall clean. I just finished doing that yesterday.
> Thanks Greg. That did the trick
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: After fedup F23 -> F24 no more left-handed mouse

[stan]

On Fri, 04 Nov 2016 17:17:09 +0100
Mark <mark2...@openmailbox.org> wrote:

> Hi
> 
> I just upgraded my desktop from F23 to F24 via fedup and after that
> the setting to have the right mouse button as the primary one has no
> effect. That is I go to All Settings -> Mouse & Touchpad and select
> Right as the primary button. But it has no effect at all. Even when I
> go to Test Your Settings it still reports that the right button is the
> secondary one.
> 
> Is there some config file that I could tweak to set this?

Without knowing your desktop, it will be hard for people to respond.
What shows in /etc/X11/xorg.conf.d/?  Is there any hard coded config
for the mouse there?  You could add one to set your desired mouse
configuration, if there isn't.  A search should give you examples that
you can tweak.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

After fedup F23 -> F24 no more left-handed mouse

[Mark]

Hi

I just upgraded my desktop from F23 to F24 via fedup and after that the
setting to have the right mouse button as the primary one has no
effect. That is I go to All Settings -> Mouse & Touchpad and select
Right as the primary button. But it has no effect at all. Even when I
go to Test Your Settings it still reports that the right button is the
secondary one.

Is there some config file that I could tweak to set this?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[Mark]

On Thu, 2016-11-03 at 12:28 -0600, Greg Woods wrote:
> On Thu, Nov 3, 2016 at 11:30 AM, Mark 
> wrote:
> 
> > 
> > All I got was a grey page with the text "Oh no! Something has
> > gone wrong.
> > 
> 
> When using the Nvidia proprietary driver, when I have this happen,
> the only
> way I have successfully recovered is to uninstall everything *nvidia*
> and
> reinstall clean. I just finished doing that yesterday.

Thanks Greg. That did the trick
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

[Greg Woods]

On Thu, Nov 3, 2016 at 11:30 AM, Mark  wrote:

> All I got was a grey page with the text "Oh no! Something has
> gone wrong.
>

When using the Nvidia proprietary driver, when I have this happen, the only
way I have successfully recovered is to uninstall everything *nvidia* and
reinstall clean. I just finished doing that yesterday.

--Greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Botched fedup F23 -> F24 with nvidia

[Mark]

Hi

I've got a Fedora 23 desktop that I thought was time to upgrade to
Fedora 24. I followed these instructions 
https://fedoramagazine.org/upgrading-fedora-23-workstation-to-fedora-24

And because I have nvidia kernel modules from rpmfusion I also did 
dnf install http://download1.rpmfusion.org/free/fedora/rpmfusion-free-r
elease-24.noarch.rpm
dnf install http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-non
free-release-24.noarch.rpm
before fedup. 

The upgrade process went without any problems until the first boot up
with F24. All I got was a grey page with the text "Oh no! Something has
gone wrong. A problem has occurred and the system can't recover. Please
log out and try again."

With Ctrl-Alt-F2 I could get a terminal, and verified that I had a
matching nvidia module for the new kernel. I tried to run the command
nvidia-xconfig and reboot. I also tried to boot one of the F23 kernels.
I tried to disconnect the second monitor if that would make any
difference. All got was that grey page telling me that something was
wrong. dmesg didn't provide any message that I though would be directly
suspicious.

The graphics card is a Nvidia Quadro 600 (GF108GL)

How to recover?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

fedup F20 to F24

[jd1008]

Is it advisable? What sort of problems could the user encounter?
Reason for asking: Many locally compiled programs (non-fedora sources)
that compile and build (via rpmbuild) just find under F20, but will not
compile on another machine running F24 (too many dependencies).

P.S: For fun, Just wondering about this: since OS can run both 64 and 32 
bit apps (Installation is 64 bit),
 and the apps link with the libs in /usr/lib64 or /usr/lib; then, 
why not be able to build and

 run apps which require libs of older fedora releases?
 for example: have   /f20/usr/lib  and /f20/usr/lib64  on a system 
of higher or lower OS release version.
 Yes, it would requires a lot of disk space for all those libs of 
that specific release, but
 disk space is cheap and plenty. I hope some savvy and inspired 
developer(s) can pick up on
 this idea :) :) It would help keep any fedora machine up to snuff 
for multiple releases.


Cheers!

JD
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
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: Issues with doing a fedup upgrade from 23 to 24

[Samuel Sieb]

On 07/25/2016 07:00 PM, Michael D. Setzer II wrote:

process on two other machines twice, and they did not upgrade. Can't see
the systems during the reboot process, and didn't see anything in the /var/log
files to show any errors.


Run "dnf system-upgrade log" to see a list of upgrade attempts.
Then run "dnf system-upgrade log " to see the log from the attempt.


Trying on those machines again, but after the failed system-upgrade, it has
to download all the files again??

It shouldn't, but you can copy the /var/lib/dnf/system-upgrade directory 
somewhere to keep them.  You can even copy that directory over to 
another computer to avoid downloading all the files again.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
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

Issues with doing a fedup upgrade from 23 to 24

[Michael D. Setzer II]

Not sure what the issue is. Am currently 7 timezones away from my 
classroom machines, but wanted to update a few before I get back. Had to 
run the process 3 times on first machine before it finally did the upgrade.
fedup --network 24 --allowerasing
Process seems to go thru just fine, and then do 
dnf system-upgrade reboot
And it reboots, but then comes back to the 23 version.
Did that twice with VNC connection to machine, and then did it a 3rd time, in 
which I sshed in via another local machine. 
Thought that might be the issue, but then did a ssh connection upgrade 
process on two other machines twice, and they did not upgrade. Can't see 
the systems during the reboot process, and didn't see anything in the /var/log 
files to show any errors.
Trying on those machines again, but after the failed system-upgrade, it has 
to download all the files again??

Thanks.

+--+
  Michael D. Setzer II -  Computer Science Instructor  
  Guam Community College  Computer Center  
  mailto:mi...@kuentos.guam.net
  mailto:msetze...@gmail.com
  Guam - Where America's Day Begins
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+--+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ABC 16613838.513356   |   EINSTEIN
106722411.95569546454407.390976
ROSETTA 46454407.390976   |   SETI87587441.062934
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
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

Black screen and no response after fedup update to 22?

[Michael D. Setzer II]

I've had this happen on two older notebooks recently that were running 
Fedora 21 just fine. Did an update on one using fedup to 22, and process 
went thru with no issues, and the login screen would come up, but after 
entering the password, the screen would go blank except for the mouse 
pointer that would move around, but nothing else. Couldn't even get a 
terminal window (Ctrl-Alt-F?) at that point.  Was able to hard reboot, and 
without attempting to login, was able to get a terminal window to open. Tried 
a number of things, but the final thing that seemed to make it work was 
diabling gdm.server after downloading lightdm and making it the active 
service. But since I had done a number of things, wasn't 100% sure that was 
it.

Just did the update on another older notebook on Saturday, and got the 
same black screen and no response after trying to login. Did just the hard 
reboot, and opened a terminal window. Installed lightdm, and did the switch 
to lightdm instead of gdm, and rebooted the system, and again the screen 
Fedora 22 came up normall. 

Don't know why there was no issue with Fedora 21, but 22 had this problem. 

+--+
  Michael D. Setzer II -  Computer Science Instructor  
  Guam Community College  Computer Center  
  mailto:mi...@kuentos.guam.net
  mailto:msetze...@gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+--+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ROSETTA 37928275.569204   |   SETI69489762.108058
ABC 16613838.513356   |   EINSTEIN81140058.876695

-- 
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: Black screen and no response after fedup update to 22?

[Timothy Murphy]

Michael D. Setzer II wrote:

> Just did the update on another older notebook on Saturday, and got the
> same black screen and no response after trying to login. Did just the hard
> reboot, and opened a terminal window. Installed lightdm, and did the
> switch to lightdm instead of gdm, and rebooted the system, and again the
> screen Fedora 22 came up normall.

I had this problem on a Lenovo Thinkpad T61 with Fedora-22,
but it runs OK under Fedora-23.
(It already ran OK under Fedora-23 beta.)

-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin


-- 
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: fedup to F22 issues

[Stephen Davies]

On 02/11/15 11:41, Gordon Messmer wrote:

On 10/31/2015 01:53 AM, Stephen Davies wrote:

On 31/10/15 12:32, Stephen Davies wrote:


1. PostgreSQL databases were not upgraded from 9.3 to 9.4 and subsequent
attempts to do this manually fail due to locale differences (AU vs US).
(I have requested help on the PostgreSQL list).


I think you want to install the "postgresql-upgrade" package, and then run
"pg_upgrade".

Fedora 22 includes a script called postgresql-setup which claims to be able to 
do the upgrade.
I couldn't get it to work - because of the locale change and also because it 
does not allow the specification of the new cluster location.

Eventually, I used initdb and pg_upgrade to do the job.


2. Amavisd-new no longer works due to issues with PERL.
This seems to be a result of updating PERL from 5.18 to 5.20 breaking a bunch
of modules.
I thought that I had resolved these by following the hints in cpan error
messages but cannot install Net::LibIDN because idna.h is missing.
I am forced to run without spam or virus checking as a result.


Whenever you can, avoid installing modules from CPAN.  They will probably
always break on a platform upgrade.  Instead, install the module from rpm:

dnf install perl-Net-LibIDN


Thanks for that. I was not aware that this was possible.
I eventually fixed this by downloading and installing the latest libidn (as 
well as the one that was there) and cpan upgrade and reinstalling a bunch of 
modules.

There seems to be no compatibility between PERL 5.18 and 5.20.


3. All of my local sendmail aliases disappeared causing many inbound emails to
be rejected.
I manually rebuilt /etc/mail/aliases to fix this.


Question?


No question, just a warning to others.


4. After rebooting to F22, I had only one workspace.
I reconfigured to four via settings but now I get apparently random blank
screen with just the mouse cursor visible. Not even a task bar.
The only way that I have found to get my work spaces back is to logout and
login again.


I've seen some users have similar problems on GNOME upgrades.  It appears to
be gnome-settings-daemon crashing in the cases I've seen, and the only way
I've found to clear it is to remove .config/dconf/user, which nukes *all* of
the settings in dconf.  It sucks,  but GNOME decided they wanted a single
binary configuration store, so...

I'm still using KDE. Touch wood, the issue seems to have gone away since I 
changed the screen saver settings.
I used to use the screen saver that trawls through my image files but that 
seems to have disappeared in F22.



5. Some fonts (particularly within Wine apps??) have changed and are much less
readable than before.
MyHeritage Family Tree Builder is one example. I have no idea which fonts were
used in F21 nor in F22.


Can't help there.  Sorry.



--
=
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia.Mobile:040 304 0583
Records & Collections Management.
--
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: fedup to F22 issues

[Gordon Messmer]

On 10/31/2015 01:53 AM, Stephen Davies wrote:

On 31/10/15 12:32, Stephen Davies wrote:


1. PostgreSQL databases were not upgraded from 9.3 to 9.4 and subsequent
attempts to do this manually fail due to locale differences (AU vs US).
(I have requested help on the PostgreSQL list).


I think you want to install the "postgresql-upgrade" package, and then 
run "pg_upgrade".



2. Amavisd-new no longer works due to issues with PERL.
This seems to be a result of updating PERL from 5.18 to 5.20 breaking 
a bunch

of modules.
I thought that I had resolved these by following the hints in cpan error
messages but cannot install Net::LibIDN because idna.h is missing.
I am forced to run without spam or virus checking as a result.


Whenever you can, avoid installing modules from CPAN.  They will 
probably always break on a platform upgrade.  Instead, install the 
module from rpm:


dnf install perl-Net-LibIDN

3. All of my local sendmail aliases disappeared causing many inbound 
emails to

be rejected.
I manually rebuilt /etc/mail/aliases to fix this.


Question?


4. After rebooting to F22, I had only one workspace.
I reconfigured to four via settings but now I get apparently random 
blank

screen with just the mouse cursor visible. Not even a task bar.
The only way that I have found to get my work spaces back is to 
logout and

login again.


I've seen some users have similar problems on GNOME upgrades.  It 
appears to be gnome-settings-daemon crashing in the cases I've seen, and 
the only way I've found to clear it is to remove .config/dconf/user, 
which nukes *all* of the settings in dconf.  It sucks,  but GNOME 
decided they wanted a single binary configuration store, so...


5. Some fonts (particularly within Wine apps??) have changed and are 
much less

readable than before.
MyHeritage Family Tree Builder is one example. I have no idea which 
fonts were

used in F21 nor in F22.


Can't help there.  Sorry.
--
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: fedup to F22 issues

[Stephen Davies]

On 31/10/15 12:32, Stephen Davies wrote:

I have just run
fedup --network 22

and have several issues as a result.

1. PostgreSQL databases were not upgraded from 9.3 to 9.4 and subsequent
attempts to do this manually fail due to locale differences (AU vs US).
(I have requested help on the PostgreSQL list).

2. Amavisd-new no longer works due to issues with PERL.
This seems to be a result of updating PERL from 5.18 to 5.20 breaking a bunch
of modules.
I thought that I had resolved these by following the hints in cpan error
messages but cannot install Net::LibIDN because idna.h is missing.
I am forced to run without spam or virus checking as a result.

3. All of my local sendmail aliases disappeared causing many inbound emails to
be rejected.
I manually rebuilt /etc/mail/aliases to fix this.

4. After rebooting to F22, I had only one workspace.
I reconfigured to four via settings but now I get apparently random blank
screen with just the mouse cursor visible. Not even a task bar.
The only way that I have found to get my work spaces back is to logout and
login again.

5. Some fonts (particularly within Wine apps??) have changed and are much less
readable than before.
MyHeritage Family Tree Builder is one example. I have no idea which fonts were
used in F21 nor in F22.

I'd be grateful for any help in resolving these.

Cheers,
Stephen



Regarding point 2.
I have confirmed that libidn is installed (11.6.5) and idna.h is in 
/usr/include/unicode but Net::LibIDN still will not install.

I suspect a version issue.
Does anybody know what version of libidn is required by Net::LibIDN?

This issue did not exist in F21 and the version of Net::LibIDN has not changed 
in ages so I suspect a Fedora issue rather than PERL.


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

fedup to F22 issues

[Stephen Davies]

I have just run
fedup --network 22

and have several issues as a result.

1. PostgreSQL databases were not upgraded from 9.3 to 9.4 and subsequent 
attempts to do this manually fail due to locale differences (AU vs US).

(I have requested help on the PostgreSQL list).

2. Amavisd-new no longer works due to issues with PERL.
This seems to be a result of updating PERL from 5.18 to 5.20 breaking a bunch 
of modules.
I thought that I had resolved these by following the hints in cpan error 
messages but cannot install Net::LibIDN because idna.h is missing.

I am forced to run without spam or virus checking as a result.

3. All of my local sendmail aliases disappeared causing many inbound emails to 
be rejected.

I manually rebuilt /etc/mail/aliases to fix this.

4. After rebooting to F22, I had only one workspace.
I reconfigured to four via settings but now I get apparently random blank 
screen with just the mouse cursor visible. Not even a task bar.
The only way that I have found to get my work spaces back is to logout and 
login again.


5. Some fonts (particularly within Wine apps??) have changed and are much less 
readable than before.
MyHeritage Family Tree Builder is one example. I have no idea which fonts were 
used in F21 nor in F22.


I'd be grateful for any help in resolving these.

Cheers,
Stephen
--
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: fedup leaves me stuck between 21 and 22

[sean darcy]

On 10/07/2015 11:31 PM, Ralf Corsepius wrote:

On 10/06/2015 07:18 PM, sean darcy wrote:

running updated 21.

fedup --network 22

Preparation seemed to go well:


[   191.911] (II) fedup:() /usr/bin/fedup exiting cleanly at Tue
Oct  6 12:26:25 2015

Rebooted.

Died somewhere in upgrading. Is there any log of the upgrade ?

No new kernel installed. Reboots into 21 kernel. Lots of dupes. yum
upgrade just give 21 updates.


Lot of dupes means something went wrong during the upgrade, probably has
corrupted the rpmdb.

You need to clean up the dupes and try to bring things in consistent
shape again.

Try using "yum/dnf distro-sync", "package-cleanup --dupes" and "rpm".

Ralf



distro-sync doesn't work. It finds all the packages with fc22 installed, 
but simply tries to reinstall the fc21 packages. Then it fails because 
all the fc21 packages are already installed.


package-cleanup find the dupes ok , but package-cleanup --cleandupes 
will remove the _older_ package. Not what we want.


FWIW, I ran rebuilddb.

What i'd really like to do is find a way to get fedup to run. I can't 
figure out where fedup is getting the info I'm already at fc22.


Stumped.

sean

--
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: fedup leaves me stuck between 21 and 22

[sean darcy]

On 10/07/2015 09:55 AM, Paul W. Frields wrote:

On Tue, Oct 06, 2015 at 01:18:27PM -0400, sean darcy wrote:

running updated 21.

fedup --network 22

Preparation seemed to go well:


[   191.911] (II) fedup:() /usr/bin/fedup exiting cleanly at Tue Oct
6 12:26:25 2015

Rebooted.

Died somewhere in upgrading. Is there any log of the upgrade ?

No new kernel installed. Reboots into 21 kernel. Lots of dupes. yum upgrade
just give 21 updates.

fedup no help:

fedup --network 22
usage: fedup  [options]
fedup: error: argument --network: version must be higher than 22

Any help appreciated.


I believe the upgrade log is in /var/log/upgrade.log.

You might want to try this:

# dnf --allowerasing --assumeno update | tee dnflog.txt

If I recall correctly, this happened to me on only one system I tried
upgrading from F21 -> F22.  There I blithely did a 'dnf update' just
to see what would happen.  (It was an experimental system so I was OK
with being foolhardy).  In that case, the update just solved
everything.

However, I'm not fully confident it will work for you, but if you look
at the output (dnflog.txt) you'll see a list of what would happen if
you ran the update.  Ideally, you'll see lots of potential updates,
and very few potential removals (maybe old kernels, but make sure at
least one is being updated).

Based on the results, you can decide what if any data to back up, and
then try it.  YMMV, caveat emptor.



dnf --allowerasing --assumeno update
Using metadata from Sun Oct 11 09:19:47 2015 (1 day, 4:21:06 hours old)
Dependencies resolved.
Nothing to do.
Complete!

dnf thinks I'm at 21 , fedup has me at 22 !

stumped.

sean


--
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: fedup leaves me stuck between 21 and 22

[Paul W. Frields]

On Wed, Oct 07, 2015 at 12:57:18PM -0400, sean darcy wrote:
> On 10/07/2015 09:55 AM, Paul W. Frields wrote:
> >On Tue, Oct 06, 2015 at 01:18:27PM -0400, sean darcy wrote:
> >>running updated 21.
> >>
> >>fedup --network 22
> >>
> >>Preparation seemed to go well:
> >>
> >>
> >>[   191.911] (II) fedup:() /usr/bin/fedup exiting cleanly at Tue Oct
> >>6 12:26:25 2015
> >>
> >>Rebooted.
> >>
> >>Died somewhere in upgrading. Is there any log of the upgrade ?
> >>
> >>No new kernel installed. Reboots into 21 kernel. Lots of dupes. yum upgrade
> >>just give 21 updates.
> >>
> >>fedup no help:
> >>
> >>fedup --network 22
> >>usage: fedup  [options]
> >>fedup: error: argument --network: version must be higher than 22
> >>
> >>Any help appreciated.
> >
> >I believe the upgrade log is in /var/log/upgrade.log.
> >
> >You might want to try this:
> >
> ># dnf --allowerasing --assumeno update | tee dnflog.txt
> >
> >If I recall correctly, this happened to me on only one system I tried
> >upgrading from F21 -> F22.  There I blithely did a 'dnf update' just
> >to see what would happen.  (It was an experimental system so I was OK
> >with being foolhardy).  In that case, the update just solved
> >everything.
> >
> >However, I'm not fully confident it will work for you, but if you look
> >at the output (dnflog.txt) you'll see a list of what would happen if
> >you ran the update.  Ideally, you'll see lots of potential updates,
> >and very few potential removals (maybe old kernels, but make sure at
> >least one is being updated).
> >
> >Based on the results, you can decide what if any data to back up, and
> >then try it.  YMMV, caveat emptor.
> >
> 
> Well despite it's name, upgrade.log only logs the preparation steps. The
> quote about fedup exiting cleanly is the last line of upgrade.log.
> 
> dnf thinks I'm on fc21.
> 
> dnf upgrade
> Using metadata from Mon Oct  5 17:27:37 2015 (1 day, 19:25:15 hours old)
> Dependencies resolved.
> Nothing to do.
> Complete!
> 
> So using dnf won't help.
> 
> fedora-release-22-1 is installed:
> 
> fedora-release-21-2.noarch
> fedora-release-22-1.noarch
> 
> 
> I think that's why fedup has the machine at fc22.
> 
> What about erasing fedora-release-22-1.noarch and rerunning fedup?

What happens if you add '--releasever 22' to the options in the
command I had above?

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.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: fedup leaves me stuck between 21 and 22

[Ralf Corsepius]

On 10/06/2015 07:18 PM, sean darcy wrote:

running updated 21.

fedup --network 22

Preparation seemed to go well:


[   191.911] (II) fedup:() /usr/bin/fedup exiting cleanly at Tue
Oct  6 12:26:25 2015

Rebooted.

Died somewhere in upgrading. Is there any log of the upgrade ?

No new kernel installed. Reboots into 21 kernel. Lots of dupes. yum
upgrade just give 21 updates.


Lot of dupes means something went wrong during the upgrade, probably has 
corrupted the rpmdb.


You need to clean up the dupes and try to bring things in consistent 
shape again.


Try using "yum/dnf distro-sync", "package-cleanup --dupes" and "rpm".

Ralf

--
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: fedup leaves me stuck between 21 and 22

[Paul W. Frields]

On Tue, Oct 06, 2015 at 01:18:27PM -0400, sean darcy wrote:
> running updated 21.
> 
> fedup --network 22
> 
> Preparation seemed to go well:
> 
> 
> [   191.911] (II) fedup:() /usr/bin/fedup exiting cleanly at Tue Oct
> 6 12:26:25 2015
> 
> Rebooted.
> 
> Died somewhere in upgrading. Is there any log of the upgrade ?
> 
> No new kernel installed. Reboots into 21 kernel. Lots of dupes. yum upgrade
> just give 21 updates.
> 
> fedup no help:
> 
> fedup --network 22
> usage: fedup  [options]
> fedup: error: argument --network: version must be higher than 22
> 
> Any help appreciated.

I believe the upgrade log is in /var/log/upgrade.log.

You might want to try this:

# dnf --allowerasing --assumeno update | tee dnflog.txt

If I recall correctly, this happened to me on only one system I tried
upgrading from F21 -> F22.  There I blithely did a 'dnf update' just
to see what would happen.  (It was an experimental system so I was OK
with being foolhardy).  In that case, the update just solved
everything.

However, I'm not fully confident it will work for you, but if you look
at the output (dnflog.txt) you'll see a list of what would happen if
you ran the update.  Ideally, you'll see lots of potential updates,
and very few potential removals (maybe old kernels, but make sure at
least one is being updated).

Based on the results, you can decide what if any data to back up, and
then try it.  YMMV, caveat emptor.

-- 
Paul W. Frieldshttp://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.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: fedup leaves me stuck between 21 and 22

[stan]

On Wed, 7 Oct 2015 12:57:18 -0400
sean darcy <seandar...@gmail.com> wrote:

> dnf thinks I'm on fc21.
> 
> dnf upgrade
> Using metadata from Mon Oct  5 17:27:37 2015 (1 day, 19:25:15 hours
> old) Dependencies resolved.
> Nothing to do.
> Complete!
> 
> So using dnf won't help.
> 
> fedora-release-22-1 is installed:
> 
> fedora-release-21-2.noarch
> fedora-release-22-1.noarch
> 
> 
> I think that's why fedup has the machine at fc22.
> 
> What about erasing fedora-release-22-1.noarch and rerunning fedup?

A couple of suggestions, with some risk, but pretty low.

Maybe try a  dnf distro-sync  first?  If it thinks the machine is at
f21, perhaps it will clean everything up.  And you can run fedup
again.  Maybe it will even see the f22 release and sync it to f22
instead.

Or, you could go into /etc/yum.repos.d/ and turn off the f21 repos, and
turn on the f22 repos, and then run  dnf upgrade  again.
-- 
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: fedup leaves me stuck between 21 and 22

[sean darcy]

On 10/07/2015 09:55 AM, Paul W. Frields wrote:

On Tue, Oct 06, 2015 at 01:18:27PM -0400, sean darcy wrote:

running updated 21.

fedup --network 22

Preparation seemed to go well:


[   191.911] (II) fedup:() /usr/bin/fedup exiting cleanly at Tue Oct
6 12:26:25 2015

Rebooted.

Died somewhere in upgrading. Is there any log of the upgrade ?

No new kernel installed. Reboots into 21 kernel. Lots of dupes. yum upgrade
just give 21 updates.

fedup no help:

fedup --network 22
usage: fedup  [options]
fedup: error: argument --network: version must be higher than 22

Any help appreciated.


I believe the upgrade log is in /var/log/upgrade.log.

You might want to try this:

# dnf --allowerasing --assumeno update | tee dnflog.txt

If I recall correctly, this happened to me on only one system I tried
upgrading from F21 -> F22.  There I blithely did a 'dnf update' just
to see what would happen.  (It was an experimental system so I was OK
with being foolhardy).  In that case, the update just solved
everything.

However, I'm not fully confident it will work for you, but if you look
at the output (dnflog.txt) you'll see a list of what would happen if
you ran the update.  Ideally, you'll see lots of potential updates,
and very few potential removals (maybe old kernels, but make sure at
least one is being updated).

Based on the results, you can decide what if any data to back up, and
then try it.  YMMV, caveat emptor.



Well despite it's name, upgrade.log only logs the preparation steps. The 
quote about fedup exiting cleanly is the last line of upgrade.log.


dnf thinks I'm on fc21.

dnf upgrade
Using metadata from Mon Oct  5 17:27:37 2015 (1 day, 19:25:15 hours old)
Dependencies resolved.
Nothing to do.
Complete!

So using dnf won't help.

fedora-release-22-1 is installed:

fedora-release-21-2.noarch
fedora-release-22-1.noarch


I think that's why fedup has the machine at fc22.

What about erasing fedora-release-22-1.noarch and rerunning fedup?

sean


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

fedup leaves me stuck between 21 and 22

[sean darcy]

running updated 21.

fedup --network 22

Preparation seemed to go well:


[   191.911] (II) fedup:() /usr/bin/fedup exiting cleanly at Tue 
Oct  6 12:26:25 2015


Rebooted.

Died somewhere in upgrading. Is there any log of the upgrade ?

No new kernel installed. Reboots into 21 kernel. Lots of dupes. yum 
upgrade just give 21 updates.


fedup no help:

fedup --network 22
usage: fedup  [options]
fedup: error: argument --network: version must be higher than 22

Any help appreciated.

sean


--
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: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

[Kernel Guardian]

That kernel is from fc21and should be removed from fc22 system.
On Sep 21, 2015 9:31 PM, "Jon Ingason" <jon.inga...@telia.com> wrote:

> Den 2015-09-21 kl. 14:40, skrev Jon Ingason:
> > I just did fedup from fc21 to fc22 without any problems.
>
> Sorry for the noise. This was note a problem. Should have read what
> stood in the output :-(
>
> > Then I just tested dnf:
> >
> > $ sudo dnf upgrade --refresh
>
> > Tar bort:
> --
> I don't know how I could miss this :-)
> >  kernelx86_64  4.1.4-100.fc21@System
> > 0
> >  kernel-core   x86_64  4.1.4-100.fc21@System
> >42 M
> >  kernel-modulesx86_64  4.1.4-100.fc21@System
> >17 M
> >  kernel-modules-extra  x86_64  4.1.4-100.fc21@System
> >   2.1 M
>
> --
> Regards
>
> Jon Ingason
>
> --
> 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
>
-- 
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: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

[Jon Ingason]

Den 2015-09-21 kl. 21:57, skrev Rick Stevens:
> On 09/21/2015 12:31 PM, Jon Ingason wrote:
>> Den 2015-09-21 kl. 14:40, skrev Jon Ingason:
>>> I just did fedup from fc21 to fc22 without any problems.
>>
>> Sorry for the noise. This was note a problem. Should have read what
>> stood in the output :-(
>>
>>> Then I just tested dnf:
>>>
>>> $ sudo dnf upgrade --refresh
>>
>>> Tar bort:
>> --
It means removes :-)
>> I don't know how I could miss this :-)


> Uhm, I don't speak any Scandinavian languages, Jon, so I have no idea
> what it means so I ignored it. Based on the tone of your response, I
> guess I can assume it means "remove" or something along those lines. If
> so, then that surely makes sense. :-)

Thanks anyway.
> --
> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
> - AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
> --
> -  Money can't buy happiness, but it can take the sting out of being -
> - miserable! -
> --


-- 
Med vänliga hälsningar/Kærar kveðjur/Regards

Jon Ingason

Stortorpsvägen 75
142 65 Trångsund
Sverige/Svíþjóð/Sweden

T: +46(0)8 - 514 911 01
M: +46(0)70 - 514 91 12
E: j...@ingason.se
W: www.ingason.se
B: www.ingason.se/blogg
-- 
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: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

[Rick Stevens]

On 09/21/2015 05:40 AM, Jon Ingason wrote:

I just did fedup from fc21 to fc22 without any problems.
Then I just tested dnf:

$ sudo dnf upgrade --refresh
[sudo] password for jonsi:
Fedora 22 - x86_64 - VirtualBox 2.1 MB/s |  23 kB
00:00
RPM Fusion for Fedora 22 - Free - Updates   264 kB/s |  73 kB
00:00
Adobe Systems Incorporated   13 kB/s | 1.8 kB
00:00
RPM Fusion for Fedora 22 - Nonfree - Updates231 kB/s |  28 kB
00:00
RPM Fusion for Fedora 22 - Free 1.3 MB/s | 551 kB
00:00
google-chrome   143 kB/s | 3.6 kB
00:00
RPM Fusion for Fedora 22 - Nonfree  850 kB/s | 170 kB
00:00
Senaste kontroll av utgångna metadata gjordes för 0:00:00 sedan på Mon
Sep 21 14:29:15 2015.
Beroenden upplösta.

  Paket Ark Version   Förråd
   Storl.

Tar bort:
  kernelx86_64  4.1.4-100.fc21@System
 0
  kernel-core   x86_64  4.1.4-100.fc21@System
42 M
  kernel-modulesx86_64  4.1.4-100.fc21@System
17 M
  kernel-modules-extra  x86_64  4.1.4-100.fc21@System
   2.1 M

Transaktionssammanfattning

Ta bort  4 Packages

Installerad storlek: 61 M
Är detta ok [j/N]: N

Why update fc21 kernel?
$ uname -svripo
Linux 4.1.6-201.fc22.x86_64 #1 SMP Fri Sep 4 17:49:24 UTC 2015 x86_64
x86_64 GNU/Linux


I don't see the fedora or fedora-updates repos listed in your output.
Are you sure they're enabled?
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- Try to look unimportant.  The bad guys may be low on ammo. -
--
--
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

After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

[Jon Ingason]

I just did fedup from fc21 to fc22 without any problems.
Then I just tested dnf:

$ sudo dnf upgrade --refresh
[sudo] password for jonsi:
Fedora 22 - x86_64 - VirtualBox 2.1 MB/s |  23 kB
00:00
RPM Fusion for Fedora 22 - Free - Updates   264 kB/s |  73 kB
00:00
Adobe Systems Incorporated   13 kB/s | 1.8 kB
00:00
RPM Fusion for Fedora 22 - Nonfree - Updates231 kB/s |  28 kB
00:00
RPM Fusion for Fedora 22 - Free 1.3 MB/s | 551 kB
00:00
google-chrome   143 kB/s | 3.6 kB
00:00
RPM Fusion for Fedora 22 - Nonfree  850 kB/s | 170 kB
00:00
Senaste kontroll av utgångna metadata gjordes för 0:00:00 sedan på Mon
Sep 21 14:29:15 2015.
Beroenden upplösta.

 Paket Ark Version   Förråd
  Storl.

Tar bort:
 kernelx86_64  4.1.4-100.fc21@System
0
 kernel-core   x86_64  4.1.4-100.fc21@System
   42 M
 kernel-modulesx86_64  4.1.4-100.fc21@System
   17 M
 kernel-modules-extra  x86_64  4.1.4-100.fc21@System
  2.1 M

Transaktionssammanfattning

Ta bort  4 Packages

Installerad storlek: 61 M
Är detta ok [j/N]: N

Why update fc21 kernel?
$ uname -svripo
Linux 4.1.6-201.fc22.x86_64 #1 SMP Fri Sep 4 17:49:24 UTC 2015 x86_64
x86_64 GNU/Linux



-- 
Regards

Jon Ingason

-- 
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: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

[Jon Ingason]

Den 2015-09-21 kl. 14:40, skrev Jon Ingason:
> I just did fedup from fc21 to fc22 without any problems.

Sorry for the noise. This was note a problem. Should have read what
stood in the output :-(

> Then I just tested dnf:
> 
> $ sudo dnf upgrade --refresh

> Tar bort:
--
I don't know how I could miss this :-)
>  kernelx86_64  4.1.4-100.fc21@System
> 0
>  kernel-core   x86_64  4.1.4-100.fc21@System
>42 M
>  kernel-modulesx86_64  4.1.4-100.fc21@System
>17 M
>  kernel-modules-extra  x86_64  4.1.4-100.fc21@System
>   2.1 M

-- 
Regards

Jon Ingason

-- 
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: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

[Rick Stevens]

On 09/21/2015 12:31 PM, Jon Ingason wrote:

Den 2015-09-21 kl. 14:40, skrev Jon Ingason:

I just did fedup from fc21 to fc22 without any problems.


Sorry for the noise. This was note a problem. Should have read what
stood in the output :-(


Then I just tested dnf:

$ sudo dnf upgrade --refresh



Tar bort:

--
I don't know how I could miss this :-)

  kernelx86_64  4.1.4-100.fc21@System
 0
  kernel-core   x86_64  4.1.4-100.fc21@System
42 M
  kernel-modulesx86_64  4.1.4-100.fc21@System
17 M
  kernel-modules-extra  x86_64  4.1.4-100.fc21@System
   2.1 M


Uhm, I don't speak any Scandinavian languages, Jon, so I have no idea
what it means so I ignored it. Based on the tone of your response, I
guess I can assume it means "remove" or something along those lines. If
so, then that surely makes sense. :-)
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Money can't buy happiness, but it can take the sting out of being -
- miserable! -
--
--
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: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

[Jon Ingason]

Den 2015-09-21 kl. 20:04, skrev Rick Stevens:
> On 09/21/2015 05:40 AM, Jon Ingason wrote:
>> I just did fedup from fc21 to fc22 without any problems.
>> Then I just tested dnf:
>>
>> $ sudo dnf upgrade --refresh


>> 
>>
>>   Paket Ark Version   Förråd
>>Storl.
>> 
>>
>> Tar bort:
>>   kernelx86_64  4.1.4-100.fc21@System
>>  0
>>   kernel-core   x86_64  4.1.4-100.fc21@System
>> 42 M
>>   kernel-modulesx86_64  4.1.4-100.fc21@System
>> 17 M
>>   kernel-modules-extra  x86_64  4.1.4-100.fc21@System
>>2.1 M
>>
>> Transaktionssammanfattning
>> 
>>
>> Ta bort  4 Packages
>>
>> Installerad storlek: 61 M
>> Är detta ok [j/N]: N
>>
>> Why update fc21 kernel?
>> $ uname -svripo
>> Linux 4.1.6-201.fc22.x86_64 #1 SMP Fri Sep 4 17:49:24 UTC 2015 x86_64
>> x86_64 GNU/Linux
> 
> I don't see the fedora or fedora-updates repos listed in your output.
> Are you sure they're enabled?

$ dnf repolist
Fedora 22 - x86_64 - VirtualBox 283 kB/s |  23 kB
00:00
Fedora 22 - x86_64  8.1 MB/s |  41 MB
00:05
RPM Fusion for Fedora 22 - Free - Updates   827 kB/s |  73 kB
00:00
Adobe Systems Incorporated   20 kB/s | 1.8 kB
00:00
RPM Fusion for Fedora 22 - Nonfree - Updates115 kB/s |  28 kB
00:00
RPM Fusion for Fedora 22 - Free 1.9 MB/s | 551 kB
00:00
Fedora 22 - x86_64 - Updates7.9 MB/s |  14 MB
00:01
google-chrome69 kB/s | 3.6 kB
00:00
RPM Fusion for Fedora 22 - Nonfree  511 kB/s | 170 kB
00:00
Senaste kontroll av utgångna metadata gjordes för 0:00:00 sedan på Mon
Sep 21 21:12:43 2015.
förråds-id förrådsnamn
  status
adobe-linux-x86_64 Adobe Systems Incorporated
   2
*fedoraFedora 22 - x86_64
  44 762
google-chrome  google-chrome
   3
rpmfusion-free RPM Fusion for Fedora 22 - Free
 500
rpmfusion-free-updates RPM Fusion for Fedora 22 - Free - Updates
  52
rpmfusion-nonfree  RPM Fusion for Fedora 22 - Nonfree
 178
rpmfusion-nonfree-updates  RPM Fusion for Fedora 22 - Nonfree - Updates
  32
*updates   Fedora 22 - x86_64 - Updates
  10 027
virtualbox Fedora 22 - x86_64 - VirtualBox
   5


Regards

Jon Ingason

-- 
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[jd1008]

On 09/18/2015 08:13 PM, Susi Lehtola wrote:

On 09/17/2015 06:27 PM, jd1008 wrote:

On 09/17/2015 06:21 PM, Rick Stevens wrote:

Second, I wouldn't even attempt an update to F22 from here. I would
upgrade to F21 first with the local repo disabled.


Going the route of first installing f21 and then f22 is way too long
(i.e. time consuming, during which the computer is not being used
for more important things.


But it is also the only one officially supported.

You might be able to do a yum upgrade directly to Fedora 22 since no 
critical components have changed.


https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_20_-.3E_Fedora_21 



PS. What does
$ rpm -q fedora-release
say?

$ rpm -q fedora-release
fedora-release-20-4.noarch
--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Susi Lehtola]

On 09/17/2015 06:27 PM, jd1008 wrote:

On 09/17/2015 06:21 PM, Rick Stevens wrote:

Second, I wouldn't even attempt an update to F22 from here. I would
upgrade to F21 first with the local repo disabled.


Going the route of first installing f21 and then f22 is way too long
(i.e. time consuming, during which the computer is not being used
for more important things.


But it is also the only one officially supported.

You might be able to do a yum upgrade directly to Fedora 22 since no 
critical components have changed.


https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_20_-.3E_Fedora_21

PS. What does
$ rpm -q fedora-release
say?
--
Susi Lehtola
Fedora Project Contributor
jussileht...@fedoraproject.org
--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[jd1008]

On 09/16/2015 11:40 AM, Gordon Messmer wrote:


yum repolist 

$ yum repolist
Loaded plugins: aliases, auto-update-debuginfo, changelog, 
fastestmirror, filter-data, fs-snapshot, keys, langpacks, list-data,
  : local, merge-conf, post-transaction-actions, 
priorities, protectbase, refresh-packagekit, refresh-updatesd,
  : remove-with-leaves, rpm-warm-cache, show-leaves, 
tmprepo, tsflags, upgrade-helper, verify, versionlock

_local | 2.9 kB  00:00:00
fedora/20/x86_64/metalink | 3.5 kB  00:00:00
fedora-debuginfo/20/x86_64/metalink | 2.4 kB  00:00:00
fedora-debuginfo | 3.1 kB  00:00:00
fedora-source/20/x86_64/metalink | 2.8 kB  00:00:00
fedora-source | 3.0 kB  00:00:00
google-earth |  951 B  00:00:00
rpmfusion-free | 3.3 kB  00:00:00
rpmfusion-free-debuginfo | 2.7 kB  00:00:00
rpmfusion-free-source | 2.7 kB  00:00:00
rpmfusion-free-updates | 3.3 kB  00:00:00
rpmfusion-nonfree-updates | 3.3 kB  00:00:00
skype | 1.2 kB  00:00:00
updates/20/x86_64/metalink | 3.3 kB  00:00:00
updates-debuginfo/20/x86_64/metalink | 2.3 kB  00:00:00
updates-debuginfo | 3.0 kB  00:00:00
updates-source/20/x86_64/metalink | 2.6 kB  00:00:00
updates-source | 3.7 kB  00:00:00
(1/4): updates-debuginfo/20/x86_64/primary_db | 859 kB  00:00:01
(2/4): fedora-debuginfo/20/x86_64/primary_db | 1.9 MB  00:00:02
(3/4): updates-source/20/x86_64/primary_db | 1.8 MB  00:00:02
(4/4): fedora-source/20/x86_64/primary_db | 4.7 MB  00:00:02
(1/4): rpmfusion-free-debuginfo/20/x86_64/primary_db |  49 kB  00:00:01
(2/4): rpmfusion-free-source/20/x86_64/primary_db |  87 kB  00:00:01
(3/4): updates-source/20/x86_64/updateinfo | 2.0 MB  00:00:01
(4/4): updates-source/20/x86_64/pkgtags | 1.6 MB  00:00:00
Loading mirror speeds from cached hostfile
 * fedora: dl.fedoraproject.org
 * fedora-debuginfo: dl.fedoraproject.org
 * fedora-source: dl.fedoraproject.org
 * rpmfusion-free: lug.mtu.edu
 * rpmfusion-free-debuginfo: lug.mtu.edu
 * rpmfusion-free-source: lug.mtu.edu
 * rpmfusion-free-updates: lug.mtu.edu
 * rpmfusion-nonfree: lug.mtu.edu
 * rpmfusion-nonfree-updates: lug.mtu.edu
 * updates: dl.fedoraproject.org
 * updates-debuginfo: dl.fedoraproject.org
 * updates-source: dl.fedoraproject.org
0 packages excluded due to repository protections
repo id   repo name status
_localAutomatic local repo. 
(manged by the "local" yum plugin). 64

fedora/20/x86_64  Fedora 20 - x86_64 38,597
fedora-debuginfo/20/x86_64Fedora 20 - x86_64 - 
Debug 6,881

fedora-source/20/x86_64   Fedora 20 - Source 0
google-earth google-earth 1
rpmfusion-free/20/x86_64  RPM Fusion for Fedora 
20 - Free468
rpmfusion-free-debuginfo/20/x86_64RPM Fusion for Fedora 
20 - Free - Debug166
rpmfusion-free-source/20/x86_64   RPM Fusion for Fedora 
20 - Free - Source 0
rpmfusion-free-updates/20/x86_64  RPM Fusion for Fedora 
20 - Free - Updates  683
rpmfusion-nonfree/20/x86_64   RPM Fusion for Fedora 
20 - Nonfree 203
rpmfusion-nonfree-updates/20/x86_64   RPM Fusion for Fedora 
20 - Nonfree - Updates   561

skype Skype Repository 1
updates/20/x86_64 Fedora 20 - x86_64 - 
Updates 22,459
updates-debuginfo/20/x86_64   Fedora 20 - x86_64 - 
Updates - Debug 3,079
updates-source/20/x86_64  Fedora 20 - Updates 
Source 0


--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Gordon Messmer]

On 09/17/2015 05:21 PM, Rick Stevens wrote:

Well, you really should be using "dnf repolist", but it's pretty
obvious you have F20 repos for the most part. 


On a mostly-Fedora-20 system, I wouldn't expect dnf to be installed.


Your machine is in a weird state, so these are somewhat draconian
measures to try to drag it into currency. The alternative is a good
backup followed by a fresh install of F22 or whatever you want to use.


That I agree with.  This install is probably 12-18 months old, without 
an audit trail for changes.

--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Gordon Messmer]

On 09/17/2015 03:41 PM, jd1008 wrote:



On 09/16/2015 11:40 AM, Gordon Messmer wrote:


yum repolist 

$ yum repolist


Less useful than I hoped, but I missed this from your first message:


/var/cache/system-upgrade/fedora/packages/
-rw-r--r-- 1 root jd  0 Sep 15 16:12 a2jmidid-8-9.fc23.x86_64.rpm


The "fedora" repo is the one with the bad URL.  Check the definition of 
that repo in /etc/yum.repos.d/


--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[jd1008]

On 09/17/2015 06:21 PM, Rick Stevens wrote:

On 09/17/2015 03:41 PM, jd1008 wrote:



On 09/16/2015 11:40 AM, Gordon Messmer wrote:


yum repolist

$ yum repolist
Loaded plugins: aliases, auto-update-debuginfo, changelog,
fastestmirror, filter-data, fs-snapshot, keys, langpacks, list-data,
   : local, merge-conf, post-transaction-actions,
priorities, protectbase, refresh-packagekit, refresh-updatesd,
   : remove-with-leaves, rpm-warm-cache, show-leaves,
tmprepo, tsflags, upgrade-helper, verify, versionlock
_local | 2.9 kB  00:00:00
fedora/20/x86_64/metalink | 3.5 kB  00:00:00
fedora-debuginfo/20/x86_64/metalink | 2.4 kB  00:00:00
fedora-debuginfo | 3.1 kB  00:00:00
fedora-source/20/x86_64/metalink | 2.8 kB  00:00:00
fedora-source | 3.0 kB  00:00:00
google-earth |  951 B  00:00:00
rpmfusion-free | 3.3 kB  00:00:00
rpmfusion-free-debuginfo | 2.7 kB  00:00:00
rpmfusion-free-source | 2.7 kB  00:00:00
rpmfusion-free-updates | 3.3 kB  00:00:00
rpmfusion-nonfree-updates | 3.3 kB  00:00:00
skype | 1.2 kB  00:00:00
updates/20/x86_64/metalink | 3.3 kB  00:00:00
updates-debuginfo/20/x86_64/metalink | 2.3 kB  00:00:00
updates-debuginfo | 3.0 kB  00:00:00
updates-source/20/x86_64/metalink | 2.6 kB  00:00:00
updates-source | 3.7 kB  00:00:00
(1/4): updates-debuginfo/20/x86_64/primary_db | 859 kB  00:00:01
(2/4): fedora-debuginfo/20/x86_64/primary_db | 1.9 MB  00:00:02
(3/4): updates-source/20/x86_64/primary_db | 1.8 MB  00:00:02
(4/4): fedora-source/20/x86_64/primary_db | 4.7 MB  00:00:02
(1/4): rpmfusion-free-debuginfo/20/x86_64/primary_db |  49 kB 00:00:01
(2/4): rpmfusion-free-source/20/x86_64/primary_db |  87 kB 00:00:01
(3/4): updates-source/20/x86_64/updateinfo | 2.0 MB  00:00:01
(4/4): updates-source/20/x86_64/pkgtags | 1.6 MB  00:00:00
Loading mirror speeds from cached hostfile
  * fedora: dl.fedoraproject.org
  * fedora-debuginfo: dl.fedoraproject.org
  * fedora-source: dl.fedoraproject.org
  * rpmfusion-free: lug.mtu.edu
  * rpmfusion-free-debuginfo: lug.mtu.edu
  * rpmfusion-free-source: lug.mtu.edu
  * rpmfusion-free-updates: lug.mtu.edu
  * rpmfusion-nonfree: lug.mtu.edu
  * rpmfusion-nonfree-updates: lug.mtu.edu
  * updates: dl.fedoraproject.org
  * updates-debuginfo: dl.fedoraproject.org
  * updates-source: dl.fedoraproject.org
0 packages excluded due to repository protections
repo id   repo name status
_localAutomatic local repo.
(manged by the "local" yum plugin). 64
fedora/20/x86_64  Fedora 20 - x86_64 
38,597

fedora-debuginfo/20/x86_64Fedora 20 - x86_64 -
Debug 6,881
fedora-source/20/x86_64   Fedora 20 - Source 0
google-earth google-earth 1
rpmfusion-free/20/x86_64  RPM Fusion for Fedora
20 - Free468
rpmfusion-free-debuginfo/20/x86_64RPM Fusion for Fedora
20 - Free - Debug166
rpmfusion-free-source/20/x86_64   RPM Fusion for Fedora
20 - Free - Source 0
rpmfusion-free-updates/20/x86_64  RPM Fusion for Fedora
20 - Free - Updates  683
rpmfusion-nonfree/20/x86_64   RPM Fusion for Fedora
20 - Nonfree 203
rpmfusion-nonfree-updates/20/x86_64   RPM Fusion for Fedora
20 - Nonfree - Updates   561
skype Skype Repository 1
updates/20/x86_64 Fedora 20 - x86_64 -
Updates 22,459
updates-debuginfo/20/x86_64   Fedora 20 - x86_64 -
Updates - Debug 3,079
updates-source/20/x86_64  Fedora 20 - Updates
Source 0


Well, you really should be using "dnf repolist", but it's pretty
obvious you have F20 repos for the most part. You also seem to have
a local repo and that may be where your F23 stuff is coming from.

I did not create the local repo.
It is present in /etc/yum.repos.d/_local
and it contains:

[_local]
name=Automatic local repo. (manged by the "local" yum plugin).
baseurl=file:/var/lib/yum/plugins/local
enabled=1
gpgcheck=true
#  Metadata expire could be set to "never" because the local plugin will
# automatically cause a cache refresh when new packages are added. However
# it's really cheap to check, and this way people can dump stuff in whenever
# and it never gets out of sync. for long.
metadata_expire=1h
#  Make cost smaller, as we know it's "local". If you really want to be 
sure,
# you can do this ... but the name will do pretty much the same thing, 
and that

# way we can also see the other packages (with: --showduplicates list).
# cost=500

But I guarantee you I did not create that beast.
So, I went ahead and deleted it and restarted 

Re: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[jd1008]

On 09/17/2015 07:19 PM, Gordon Messmer wrote:

On 09/17/2015 03:41 PM, jd1008 wrote:



On 09/16/2015 11:40 AM, Gordon Messmer wrote:


yum repolist 

$ yum repolist


Less useful than I hoped, but I missed this from your first message:


/var/cache/system-upgrade/fedora/packages/
-rw-r--r-- 1 root jd  0 Sep 15 16:12 a2jmidid-8-9.fc23.x86_64.rpm


The "fedora" repo is the one with the bad URL.  Check the definition 
of that repo in /etc/yum.repos.d/



The fedora repos:
[fedora]
name=Fedora $releasever - $basearch
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever=$basearch
enabled=1
#metadata_expire=7d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[fedora-debuginfo]
name=Fedora $releasever - $basearch - Debug
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/debug/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-$releasever=$basearch
enabled=0
metadata_expire=7d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[fedora-source]
name=Fedora $releasever - Source
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/source/SRPMS/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-$releasever=$basearch
enabled=0
metadata_expire=7d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False


[updates]
name=Fedora $releasever - $basearch - Updates
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releasever=$basearch
enabled=1
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[updates-debuginfo]
name=Fedora $releasever - $basearch - Updates - Debug
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/debug/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f$releasever=$basearch
enabled=0
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

[updates-source]
name=Fedora $releasever - Updates Source
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/SRPMS/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-source-f$releasever=$basearch
enabled=0
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False

Rawhide and Testing have   enabled=0 in all stanzas.


--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Rick Stevens]

On 09/17/2015 03:41 PM, jd1008 wrote:



On 09/16/2015 11:40 AM, Gordon Messmer wrote:


yum repolist

$ yum repolist
Loaded plugins: aliases, auto-update-debuginfo, changelog,
fastestmirror, filter-data, fs-snapshot, keys, langpacks, list-data,
   : local, merge-conf, post-transaction-actions,
priorities, protectbase, refresh-packagekit, refresh-updatesd,
   : remove-with-leaves, rpm-warm-cache, show-leaves,
tmprepo, tsflags, upgrade-helper, verify, versionlock
_local | 2.9 kB  00:00:00
fedora/20/x86_64/metalink | 3.5 kB  00:00:00
fedora-debuginfo/20/x86_64/metalink | 2.4 kB  00:00:00
fedora-debuginfo | 3.1 kB  00:00:00
fedora-source/20/x86_64/metalink | 2.8 kB  00:00:00
fedora-source | 3.0 kB  00:00:00
google-earth |  951 B  00:00:00
rpmfusion-free | 3.3 kB  00:00:00
rpmfusion-free-debuginfo | 2.7 kB  00:00:00
rpmfusion-free-source | 2.7 kB  00:00:00
rpmfusion-free-updates | 3.3 kB  00:00:00
rpmfusion-nonfree-updates | 3.3 kB  00:00:00
skype | 1.2 kB  00:00:00
updates/20/x86_64/metalink | 3.3 kB  00:00:00
updates-debuginfo/20/x86_64/metalink | 2.3 kB  00:00:00
updates-debuginfo | 3.0 kB  00:00:00
updates-source/20/x86_64/metalink | 2.6 kB  00:00:00
updates-source | 3.7 kB  00:00:00
(1/4): updates-debuginfo/20/x86_64/primary_db | 859 kB  00:00:01
(2/4): fedora-debuginfo/20/x86_64/primary_db | 1.9 MB  00:00:02
(3/4): updates-source/20/x86_64/primary_db | 1.8 MB  00:00:02
(4/4): fedora-source/20/x86_64/primary_db | 4.7 MB  00:00:02
(1/4): rpmfusion-free-debuginfo/20/x86_64/primary_db |  49 kB  00:00:01
(2/4): rpmfusion-free-source/20/x86_64/primary_db |  87 kB  00:00:01
(3/4): updates-source/20/x86_64/updateinfo | 2.0 MB  00:00:01
(4/4): updates-source/20/x86_64/pkgtags | 1.6 MB  00:00:00
Loading mirror speeds from cached hostfile
  * fedora: dl.fedoraproject.org
  * fedora-debuginfo: dl.fedoraproject.org
  * fedora-source: dl.fedoraproject.org
  * rpmfusion-free: lug.mtu.edu
  * rpmfusion-free-debuginfo: lug.mtu.edu
  * rpmfusion-free-source: lug.mtu.edu
  * rpmfusion-free-updates: lug.mtu.edu
  * rpmfusion-nonfree: lug.mtu.edu
  * rpmfusion-nonfree-updates: lug.mtu.edu
  * updates: dl.fedoraproject.org
  * updates-debuginfo: dl.fedoraproject.org
  * updates-source: dl.fedoraproject.org
0 packages excluded due to repository protections
repo id   repo name status
_localAutomatic local repo.
(manged by the "local" yum plugin). 64
fedora/20/x86_64  Fedora 20 - x86_64 38,597
fedora-debuginfo/20/x86_64Fedora 20 - x86_64 -
Debug 6,881
fedora-source/20/x86_64   Fedora 20 - Source 0
google-earth google-earth 1
rpmfusion-free/20/x86_64  RPM Fusion for Fedora
20 - Free468
rpmfusion-free-debuginfo/20/x86_64RPM Fusion for Fedora
20 - Free - Debug166
rpmfusion-free-source/20/x86_64   RPM Fusion for Fedora
20 - Free - Source 0
rpmfusion-free-updates/20/x86_64  RPM Fusion for Fedora
20 - Free - Updates  683
rpmfusion-nonfree/20/x86_64   RPM Fusion for Fedora
20 - Nonfree 203
rpmfusion-nonfree-updates/20/x86_64   RPM Fusion for Fedora
20 - Nonfree - Updates   561
skype Skype Repository 1
updates/20/x86_64 Fedora 20 - x86_64 -
Updates 22,459
updates-debuginfo/20/x86_64   Fedora 20 - x86_64 -
Updates - Debug 3,079
updates-source/20/x86_64  Fedora 20 - Updates
Source 0


Well, you really should be using "dnf repolist", but it's pretty
obvious you have F20 repos for the most part. You also seem to have
a local repo and that may be where your F23 stuff is coming from.

I'm still not sure why your fedup is not puking when you specify the
"--product" flag. It is NOT allowed with the current 0.9.2 versions,
so the first thing I'd do is sort out which fedup you're getting.

Could you possibly have an old fedup that's getting called instead of
the one in /bin (perhaps in /usr/local/bin or something)? You could
try "which fedup" to see which one is being called.

Second, I wouldn't even attempt an update to F22 from here. I would
upgrade to F21 first with the local repo disabled. You might be able
to disable it at the command line:

fedup --network 21 --disablerepo=\*local\*

or you may have to edit the repo config file and set "enabled=0" in
it for all the stanzas. Make sure you have a RELIABLE backup before you
attempt any of these upgrades.

However you disabled the local repo, if the upgrade is successful then
go through the whole distrosync and everyt

Re: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Joe Zeff]

On 09/16/2015 10:40 AM, Gordon Messmer wrote:


I know you said that rawhide isn't enabled, but that's really the only
likely explanation.  You may have installed or enabled some rawhide
repository to fetch the kernel src.rpm, and now yum related tools will
pull packages from that repository.


If that were true, wouldn't he be seeing rawhide packages in his regular 
updates?

--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Rahul Sundaram]

Hi

On Wed, Sep 16, 2015 at 1:53 PM, Joe Zeff wrote:

>
> If that were true, wouldn't he be seeing rawhide packages in his regular
> updates?
>
> Only if he let it remain enables as opposed to cherry picking updates by
temporarily enabling for a single update session.   If you do such things,
 running fedup probably isn't going to work out very well or atleast it is
not something that has been tested during the QA process.

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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Gordon Messmer]

On 09/15/2015 04:14 PM, jd1008 wrote:
So, my question remains: Why fc23  


yum repolist

I know you said that rawhide isn't enabled, but that's really the only 
likely explanation.  You may have installed or enabled some rawhide 
repository to fetch the kernel src.rpm, and now yum related tools will 
pull packages from that repository.


But since none of us can tell what state your system is in, a clean 
install of Fedora 22 is the best option.

--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Rick Stevens]

On 09/15/2015 04:14 PM, jd1008 wrote:



On 09/15/2015 04:20 PM, Rick Stevens wrote:

On 09/15/2015 03:17 PM, jd1008 wrote:

Why
All the packages it downloaded are from the unreleased fedora 23.

For example, this is what it downloaded into
/var/cache/system-upgrade/fedora/packages/
-rw-r--r-- 1 root jd  0 Sep 15 16:12 a2jmidid-8-9.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aajohan-comfortaa-fonts-2.004-5.fc23.noarch.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aalib-devel-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aalib-libs-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
abattis-cantarell-fonts-0.0.16-3.fc23.noarch.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 abiword-3.0.1-4.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 abrt-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
abrt-addon-ccpp-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
packages/abrt-addon-coredump-helper-2.6.2-6.fc23.x86_64.rpm

As you can see, all of them of length 0.

Is the repo of 22 being diverted to 23?


The correct update from F21 to F22 is:

fedup --network 22

fedup should have puked on "--product=nonproduct" as that's not a
supported option since F21.

Also check your repos.d files and make sure you haven't enabled rawhide.


Hi Rick,
None of rawhide repos are enabled.
The latest version of fedup in f21 is fedpkg-1.20-1.fc21.noarch.rpm


fedpkg is NOT fedup. fedpkg is to permit you to download sources from
koji or git.


# rpm -q fedup
fedup-0.9.2-1.fc21.noarch


I have the same version:

[root@prophead ~]# rpm -qa | grep fedup
fedup-0.9.2-1.fc21.noarch



# fedup  --network 22
usage: fedup  [options]
fedup: error:

This installation of Fedora does not belong to a product, so you
must provide the =PRODUCTNAME option to specify what product
you want to upgrade to. PRODUCTNAME should be one of:

  workstation: the default Fedora experience for laptops and desktops,
powered by GNOME.
  server: the default Fedora experience for servers
  cloud: a base image for use on public and private clouds
  nonproduct: choose this if none of the above apply; in particular,
choose this if you are using an alternate-desktop spin of Fedora

Selecting a product will also install its standard package-set in
addition to upgrading the packages already on your system. If you
prefer to maintain your current set of packages, select 'nonproduct'.

See https://fedoraproject.org/wiki/Upgrading for more information.


That's not what THAT version of fedup should report. It should look
like:

[root@prophead ~]# fedup --network 22 --product=nonproduct
usage: fedup  [options]
fedup: error: unrecognized arguments: --product=nonproduct

[root@prophead ~]# fedup --product=nonproduct --network 22
usage: fedup  [options]
fedup: error: unrecognized arguments: --product=nonproduct

(I did it twice, swapping around where you stuck "--product=nonproduct"
just to show you).

So you are running an incorrect version of fedup. Get that resolved
first. That's in the upgrade instructions. Also in the upgrade
instructions, they tell you that you MUST make sure you're running the
current system or you're going to get a bunch of very weird things
going on.

Right now it appears you have a very curious mix of F20 and F21 on your
machine and you're going to have problems trying to fedup.


However, when I set the product=workstation, it started
to download - but ALL the downloads were failing with messages
like these:

anaconda-core-23.19.2-2.fc23.x FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-23.19.2-2.fc23.x86_64 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-core-23.19.2-2.fc23.x FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-tui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
amtterm-1.3-10.fc23.x86_64.rpm FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-core-23.19.2-2.fc23.x FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-tui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
amtterm-1.3-10.fc23.x86_64.rpm FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA

My computer is connected to high speed internet, and am having no problems
browsing the web, and sending this email.

So, my question remains: Why fc23 


Again, you are running an old version of fedup, your machine is NOT a 
clean F21 system and most likely fedup is getting very, very confused.

As others have suggested:

1. Make a backup of your system.

2. Bring it up to current F21 standards using yum or dnf.
   You might even have to do a "dnf --distro-sync" to drag it kicking
   and screaming up to F21.

3. Make sure you're running the LATEST f

Re: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Susi Lehtola]

On 09/15/2015 04:14 PM, jd1008 wrote:

The correct update from F21 to F22 is:

fedup --network 22

fedup should have puked on "--product=nonproduct" as that's not a
supported option since F21.

Also check your repos.d files and make sure you haven't enabled rawhide.


Hi Rick,
None of rawhide repos are enabled.
The latest version of fedup in f21 is fedpkg-1.20-1.fc21.noarch.rpm
# rpm -q fedup
fedup-0.9.2-1.fc21.noarch


Now I'm confused. Quoting from your earlier message

On 09/14/2015 01:04 PM, jd1008 wrote:
> On a laptop with
> 02:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n
> (rev 01)
> and kernel: kernel-4.3.0-0.rc0.git11.1
>
> and compiled modules:
> 
/lib/modules/4.3.0-0.rc0.git11.1.fc20.x86_64/kernel/drivers/net/phy/bcm7xxx.ko.xz 


>
> 
/lib/modules/4.3.0-0.rc0.git11.1.fc20.x86_64/kernel/drivers/net/phy/bcm87xx.ko.xz 



you seem to be running Fedora 20, not Fedora 21. Have you updated part 
of your system to Fedora 21? If that is the case, I agree with Gordon. 
You should do a clean install of Fedora 22.

--
Susi Lehtola
Fedora Project Contributor
jussileht...@fedoraproject.org
--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[jd1008]

On 09/15/2015 04:20 PM, Rick Stevens wrote:

On 09/15/2015 03:17 PM, jd1008 wrote:

Why
All the packages it downloaded are from the unreleased fedora 23.

For example, this is what it downloaded into
/var/cache/system-upgrade/fedora/packages/
-rw-r--r-- 1 root jd  0 Sep 15 16:12 a2jmidid-8-9.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aajohan-comfortaa-fonts-2.004-5.fc23.noarch.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aalib-devel-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aalib-libs-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
abattis-cantarell-fonts-0.0.16-3.fc23.noarch.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 abiword-3.0.1-4.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 abrt-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
abrt-addon-ccpp-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
packages/abrt-addon-coredump-helper-2.6.2-6.fc23.x86_64.rpm

As you can see, all of them of length 0.

Is the repo of 22 being diverted to 23?


The correct update from F21 to F22 is:

fedup --network 22

fedup should have puked on "--product=nonproduct" as that's not a 
supported option since F21.


Also check your repos.d files and make sure you haven't enabled rawhide.


Hi Rick,
None of rawhide repos are enabled.
The latest version of fedup in f21 is fedpkg-1.20-1.fc21.noarch.rpm
# rpm -q fedup
fedup-0.9.2-1.fc21.noarch

# fedup  --network 22
usage: fedup  [options]
fedup: error:

This installation of Fedora does not belong to a product, so you
must provide the =PRODUCTNAME option to specify what product
you want to upgrade to. PRODUCTNAME should be one of:

 workstation: the default Fedora experience for laptops and desktops,
   powered by GNOME.
 server: the default Fedora experience for servers
 cloud: a base image for use on public and private clouds
 nonproduct: choose this if none of the above apply; in particular,
   choose this if you are using an alternate-desktop spin of Fedora

Selecting a product will also install its standard package-set in
addition to upgrading the packages already on your system. If you
prefer to maintain your current set of packages, select 'nonproduct'.

See https://fedoraproject.org/wiki/Upgrading for more information.

===

However, when I set the product=workstation, it started
to download - but ALL the downloads were failing with messages
like these:

anaconda-core-23.19.2-2.fc23.x FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-23.19.2-2.fc23.x86_64 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-core-23.19.2-2.fc23.x FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-tui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
amtterm-1.3-10.fc23.x86_64.rpm FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-core-23.19.2-2.fc23.x FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-tui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
amtterm-1.3-10.fc23.x86_64.rpm FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA
anaconda-gui-23.19.2-2.fc23.x8 FAILED ] 3.5 MB/s |  27 MB  00:24:40 ETA

My computer is connected to high speed internet, and am having no problems
browsing the web, and sending this email.

So, my question remains: Why fc23 

--
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Ed Greshko]

On 09/16/15 07:26, Susi Lehtola wrote:
> On 09/15/2015 04:14 PM, jd1008 wrote:
>>> The correct update from F21 to F22 is:
>>>
>>>     fedup --network 22
>>>
>>> fedup should have puked on "--product=nonproduct" as that's not a
>>> supported option since F21.
>>>
>>> Also check your repos.d files and make sure you haven't enabled rawhide.
>>
>> Hi Rick,
>> None of rawhide repos are enabled.
>> The latest version of fedup in f21 is fedpkg-1.20-1.fc21.noarch.rpm
>> # rpm -q fedup
>> fedup-0.9.2-1.fc21.noarch
>
> Now I'm confused. Quoting from your earlier message
>
> On 09/14/2015 01:04 PM, jd1008 wrote:
> > On a laptop with
> > 02:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n
> > (rev 01)
> > and kernel: kernel-4.3.0-0.rc0.git11.1
> >
> > and compiled modules:
> > /lib/modules/4.3.0-0.rc0.git11.1.fc20.x86_64/kernel/drivers/net/phy/bcm7xxx.ko.xz
> >
> > /lib/modules/4.3.0-0.rc0.git11.1.fc20.x86_64/kernel/drivers/net/phy/bcm87xx.ko.xz
>
> you seem to be running Fedora 20, not Fedora 21. Have you updated part of 
> your system to Fedora 21? If that is the case, I agree with Gordon. You 
> should do a clean install of Fedora 22.

And, if you noticed, the kernel he is using is recompiled for F20 from a 
downloaded srpm from koji which is targeted for F24.  So, who knows what other 
"modifications" have been done to this system? 


-- 
It seems most people that say they are "done talking about it" never really are 
until given the last word.
-- 
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: fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[Rick Stevens]

On 09/15/2015 03:17 PM, jd1008 wrote:

Why
All the packages it downloaded are from the unreleased fedora 23.

For example, this is what it downloaded into
/var/cache/system-upgrade/fedora/packages/
-rw-r--r-- 1 root jd  0 Sep 15 16:12 a2jmidid-8-9.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aajohan-comfortaa-fonts-2.004-5.fc23.noarch.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aalib-devel-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
aalib-libs-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
abattis-cantarell-fonts-0.0.16-3.fc23.noarch.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 abiword-3.0.1-4.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 abrt-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
abrt-addon-ccpp-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12
packages/abrt-addon-coredump-helper-2.6.2-6.fc23.x86_64.rpm

As you can see, all of them of length 0.

Is the repo of 22 being diverted to 23?


The correct update from F21 to F22 is:

fedup --network 22

fedup should have puked on "--product=nonproduct" as that's not a 
supported option since F21.


Also check your repos.d files and make sure you haven't enabled rawhide.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-When you don't know what to do, walk fast and look worried. -
--
--
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

fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!

[jd1008]

Why
All the packages it downloaded are from the unreleased fedora 23.

For example, this is what it downloaded into
/var/cache/system-upgrade/fedora/packages/
-rw-r--r-- 1 root jd  0 Sep 15 16:12 a2jmidid-8-9.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 
aajohan-comfortaa-fonts-2.004-5.fc23.noarch.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 
aalib-devel-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 
aalib-libs-1.4.0-0.27.rc5.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 
abattis-cantarell-fonts-0.0.16-3.fc23.noarch.rpm

-rw-r--r-- 1 root jd  0 Sep 15 16:12 abiword-3.0.1-4.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 abrt-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 
abrt-addon-ccpp-2.6.2-6.fc23.x86_64.rpm
-rw-r--r-- 1 root jd  0 Sep 15 16:12 
packages/abrt-addon-coredump-helper-2.6.2-6.fc23.x86_64.rpm


As you can see, all of them of length 0.

Is the repo of 22 being diverted to 23?

--
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: gnome embedded screencast tool unavailable after fedup to federa22

[jeandet alexis]

Hi, 
I got this issue when I use more than one screen, in my case if I just
use one screen it works.
Best regards,
Alexis.
On Tue, 2015-09-15 at 11:55 +0800, panfei wrote:
> After upgrading my fedora21 to fedora22 using fedup, I tried to
> record a simple screen video by using the gnome3 embedded screencast
> (Ctrl + Alt + Shift + R), After pressing the combined keys, the
> familiar red point appears on the right-top of my desktop.
> 
> After 30 seconds passed, the screencast tool exited, this is
> expected. and then I go to the Video directory,  there  is a webm
> video file there, but the size of the file is zero.
> 
>  is there any way to track what caused this issue and how to fix it ?
> 
> 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
-- 
Alexis Jeandet,
Plasma Physics Laboratory,
www.lpp.fr 
33169335859

-- 
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: gnome embedded screencast tool unavailable after fedup to federa22

[panfei]

PS: My Video card is GTX560TI and installed the commercial driver from
rpmfusion.

2015-09-15 11:55 GMT+08:00 panfei <cnwe...@gmail.com>:

> After upgrading my fedora21 to fedora22 using fedup, I tried to record a
> simple screen video by using the gnome3 embedded screencast (Ctrl + Alt +
> Shift + R), After pressing the combined keys, the familiar red point
> appears on the right-top of my desktop.
>
> After 30 seconds passed, the screencast tool exited, this is expected. and
> then I go to the Video directory,  there  is a webm video file there, but
> the size of the file is zero.
>
>  is there any way to track what caused this issue and how to fix it ?
>
> 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

gnome embedded screencast tool unavailable after fedup to federa22

[panfei]

After upgrading my fedora21 to fedora22 using fedup, I tried to record a
simple screen video by using the gnome3 embedded screencast (Ctrl + Alt +
Shift + R), After pressing the combined keys, the familiar red point
appears on the right-top of my desktop.

After 30 seconds passed, the screencast tool exited, this is expected. and
then I go to the Video directory,  there  is a webm video file there, but
the size of the file is zero.

 is there any way to track what caused this issue and how to fix it ?

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

fedup Q: re: --product=nonproduct

[jd1008]

Given one's current installation is a workstation,
What is the consequence of running
fedup with the option |--product=nonproduct|
|
|The wiki at https://fedoraproject.org/wiki/FedUp
says:

.
.
.
.
Upgrading from Fedora 20 or earlier: Products

In order to select one of the new Fedora flavors, FedUp has a new 
option, --product=PRODUCT. When upgrading from Fedora 20 or earlier to 
Fedora 21 or later, you must pass this --product option.


You can use the values workstation, server, cloud or nonproduct. If you 
upgrade to Workstation or Server, all the packages that are included in 
a default installation of that flavor will be installed after the 
upgrade (that is, any that are not currently installed will be added). 
Your firewall configuration will also be reset to the default for that 
flavor (in the Workstation case, this is a fairly open configuration). 
If you do not wish these things to happen, use the value nonproduct.




So, using nonproduct, one could end up missing some packages, which 
would otherwise be installed by selecting product=workstation ???


If that is the case, how can one find out what those packages are after
fedup   --product=nonproduct ?

--
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: Fedup half-complete

[Ed Greshko]

On 08/23/15 19:14, Timothy Murphy wrote:
 I followed the instructions at
 https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
 to upgrade my second-best laptop from Fedora-21 to 22.
 The upgrade failed halfway through with memory warnings of some type.
 I ran fedora-upgrade again, and this time it installed all the packages,
 but hung halfway through cleanup.

 Rather surprisingly, the system booted into a version
 that seems to be a mixture of Fedora-21 and Fedora-22.
 /etc/fedora-release says it is 22, but the kernel is 21.

 Running dnf distro-sync and dnf update gives
 
 [tim@rose ~]$ sudo dnf distro-sync
 Last metadata expiration check performed 2:59:30 ago on Sat Aug 22 17:53:07 
 2015.
 Error: package libksysguard-common-5.3.2-1.fc22.x86_64 conflicts with 
 ksysguard  5.2 provided by ksysguard-4.11.14-1.fc21.x86_64.
 package kf5-kactivities-5.12.0-1.fc22.x86_64 requires kf5-kactivities-
 libs(x86-64) = 5.12.0-1.fc22, but none of the providers can be installed.
 package dnf-yum-0.6.1-1.fc21.noarch requires dnf = 0.6.1-1.fc21, but none of 
 the providers can be installed
 (try to add '--allowerasing' to command line to replace conflicting 
 packages)
 [tim@rose ~]$ sudo dnf update
 Last metadata expiration check performed 2:59:40 ago on Sat Aug 22 17:53:07 
 2015.
 Dependencies resolved.
 Nothing to do.
 Complete!
 

 Any suggestions?
 Should I just forget this, and install Fedora-22 in the usual way?


I'd probably start by running package-cleanup to see if there were any dupes.

Then, when running update I'd add the --best option since I think without it 
dependency issues are silenced.

-- 
It seems most people that say they are done talking about it never really are 
until given the last word.
-- 
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: Fedup half-complete

[Michael Schwendt]

On Sun, 23 Aug 2015 12:14:32 +0100, Timothy Murphy wrote:

 I followed the instructions at
 https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
 to upgrade my second-best laptop from Fedora-21 to 22.
 The upgrade failed halfway through with memory warnings of some type.

Isn't memory warnings of some type too vague to even comment on 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

Fedup half-complete

[Timothy Murphy]

I followed the instructions at
https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
to upgrade my second-best laptop from Fedora-21 to 22.
The upgrade failed halfway through with memory warnings of some type.
I ran fedora-upgrade again, and this time it installed all the packages,
but hung halfway through cleanup.

Rather surprisingly, the system booted into a version
that seems to be a mixture of Fedora-21 and Fedora-22.
/etc/fedora-release says it is 22, but the kernel is 21.

Running dnf distro-sync and dnf update gives

[tim@rose ~]$ sudo dnf distro-sync
Last metadata expiration check performed 2:59:30 ago on Sat Aug 22 17:53:07 
2015.
Error: package libksysguard-common-5.3.2-1.fc22.x86_64 conflicts with 
ksysguard  5.2 provided by ksysguard-4.11.14-1.fc21.x86_64.
package kf5-kactivities-5.12.0-1.fc22.x86_64 requires kf5-kactivities-
libs(x86-64) = 5.12.0-1.fc22, but none of the providers can be installed.
package dnf-yum-0.6.1-1.fc21.noarch requires dnf = 0.6.1-1.fc21, but none of 
the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting 
packages)
[tim@rose ~]$ sudo dnf update
Last metadata expiration check performed 2:59:40 ago on Sat Aug 22 17:53:07 
2015.
Dependencies resolved.
Nothing to do.
Complete!


Any suggestions?
Should I just forget this, and install Fedora-22 in the usual way?

-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin

-- 
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: Sound and networking not working after fedup from 20 to 22

[Ed Greshko]

On 08/09/15 19:42, fedora2015 wrote:
 I know this is very vague, but I don't have access to the machine in question 
 for the time being. A friend of mine, who is even less experienced than 
 myself, used fedup --network 22 --product=nonproduct to upgrade from fedora 
 20 to 22. His sound and networking stopped functioning.

 When he boots into his machine he gets network has been disconnected as a 
 message. Enable networking is checked in network manageer

 ONBOOT= Yes is also there in the appropriate ifcfg confi files.

Running GNOME or another desktop?

Connect is a wired or wifi?

Output of...

nmcli n

ip link show

Konsole

 Regarding the sound...I'm not sure where to start. A push in the right 
 direction would be appreciated...

Is pulseaudio running?  Could it be simply that muted?  Use pavucontrol to 
check.

Get access to the system so questions won't be so vague and there won't be a 
problem of telephone, if you know what I mean.  That'll help quite a bit. 

-- 
If I wanted a blog or social media I'd go elsewhere
-- 
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

Sound and networking not working after fedup from 20 to 22

[fedora2015]

I know this is very vague, but I don't have access to the machine in 
question for the time being. A friend of mine, who is even less 
experienced than myself, used fedup --network 22 --product=nonproduct 
to upgrade from fedora 20 to 22. His sound and networking stopped 
functioning.


When he boots into his machine he gets network has been disconnected 
as a message. Enable networking is checked in network manageer


ONBOOT= Yes is also there in the appropriate ifcfg confi files.

Regarding the sound...I'm not sure where to start. A push in the right 
direction would be appreciated...

--
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: fedup 20 - 22 - improper X rendering

[fedora2015]

On 08/08/2015 09:42 PM, Rich Emberson wrote:

I used to update:
  fedup --network 22 --product=nonproduct

Coming up in graphical target as default.target, KDE X does
not render properly.
With right click I a small box appears under the cursor,
navigating to what I guess is the first menu item, I can
start a console.
A box appears. I click into it and type:
  xterm
Another box appears and I can launch another xterm from it.
At any of the xterm's (and console) I can enter commands.
The area where the xterm prints my input text and any resulting
output text is drawn ... but not the rest of the xterm (which
remains the background image).
I can find the top of the xterm box and move it ... it leaves
a trail of sides of the xterm as it is moved.
Any xterm over which I move another xterm, does not refresh
it self.

Basically, X is unusable.

# /sbin/lshw -c display
   *-display
description: VGA compatible controller
product: G73 [GeForce 7300 GT]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master
cap_list rom
configuration: driver=nouveau latency=0
resources: irq:29 memory:fd00-fdff
memory:d000-dfff memory:fc00-fcff ioport:bc00(size=128)
memory:fe8e-fe8f

No nvidia drivers are installed:
  rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep -i nvi
nothing

  rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
akmods 0.5.4-1.fc22 noarch
kmodtool 1-23.fc22 noarch
libmikmod 3.3.7-1.fc22 x86_64
kmod-libs 21-1.fc22 x86_64
kmod 21-1.fc22 x86_64


The contents of /etc/X11 is the same post upgrade to fedora 22
as it was for fedora 20 (I kept a copy of 20's /etc/X11 directory).

In /var/log/Xorg.0.log the same (EE) and (WW) messages
appear in the fedora 22 as in the fedora 20 log (again, I kept
a copy).
The only difference that pops out is that for the fedora 20
Xorg.0.log the bottom has:

[ 22527.418] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 22527.418] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680
1728 1760 1840  1050 1052 1058 1100 -hsync -vsync (64.7 kHz eP)

but for the 22 Xorg.0.log the bottom has:


[81.512] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[81.512] (II) NOUVEAU(0): Modeline 2560x1080x0.0  185.58  2560
2624 2688 2784  1080 1083 1093  +hsync -vsync (66.7 kHz eP)
[81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   40.00  800 840
968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   31.50  640 656
720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   25.18  640 656
752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 720x400x0.0   28.32  720 738
846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  135.00  1280
1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   78.75  1024 1040
1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   65.00  1024 1048
1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   49.50  800 816
896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1280x800x0.0   71.00  1280 1328
1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680
1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1152x864x0.0  108.00  1152 1216
1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  108.00  1280
1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1920x1080x60.0  172.80  1920
2040 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)

which is to say, a lot more gathered Modelines ... whatever that means.

The nouveau entries in the Xorg.0.log are very similar:

fedora 20
.
[1.801451] nouveau  [ DRM] 0xC272: Parsing digital output script
table
[1.903954] nouveau  [ DRM] MM: using M2MF for buffer copies
[1.903963] nouveau  [ DRM] Setting dpms mode 3 on TV encoder
(output 3)
[1.959109] nouveau  [ DRM] allocated 2560x1080 fb: 0x9000, bo
88003693ec00
[1.959207] fbcon: nouveaufb (fb0) is primary device
[1.982601] nouveau  [ DRM] 0xC272: Parsing digital output script
table
[2.083944] Console: switching to colour frame buffer device 320x67
[2.085254] nouveau :01:00.0: fb0: nouveaufb frame buffer device
[2.085255] nouveau :01:00.0: registered panic notifier
[2.097031] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0

Re: Sound and networking not working after fedup from 20 to 22

[fedora2015]

On 08/09/2015 08:07 AM, Ed Greshko wrote:

On 08/09/15 19:42, fedora2015 wrote:

I know this is very vague, but I don't have access to the machine in question for the 
time being. A friend of mine, who is even less experienced than myself, used fedup 
--network 22 --product=nonproduct to upgrade from fedora 20 to 22. His sound and 
networking stopped functioning.

When he boots into his machine he gets network has been disconnected as a message. 
Enable networking is checked in network manageer

ONBOOT= Yes is also there in the appropriate ifcfg confi files.


Running GNOME or another desktop?

Connect is a wired or wifi?

Output of...

nmcli n

ip link show

Konsole


Regarding the sound...I'm not sure where to start. A push in the right 
direction would be appreciated...


Is pulseaudio running?  Could it be simply that muted?  Use pavucontrol to 
check.

Get access to the system so questions won't be so vague and there won't be a problem of 
telephone, if you know what I mean.  That'll help quite a bit.



Cripes...I should have my morning coffee before posting...wired 
network...running XFCE...output will be later when he brings the 
machine...and yes...lol...telephone was a major headache last 
night..especially since person on the other end seems to be a 
whistler... I wanted to reach through the screen and

--
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: fedup 20 - 22 - improper X rendering

[Rich Emberson]

Tried the Fedora 22 Live KDE dvd I created just to see if it would come
up
Well, its X - KDE had the same rendering problem. Foreground images do
not fully refresh their part of the screen.

As said previously, X applications launched from remote machines run just
fine
on the remote machine.

So, somehow Fedora 22's nouveau-based rendering seems to have an issue ..
or something

On Sat, Aug 8, 2015 at 6:42 PM, Rich Emberson emberson.r...@gmail.com
wrote:

 I used to update:
  fedup --network 22 --product=nonproduct

 Coming up in graphical target as default.target, KDE X does
 not render properly.
 With right click I a small box appears under the cursor,
 navigating to what I guess is the first menu item, I can
 start a console.
 A box appears. I click into it and type:
  xterm
 Another box appears and I can launch another xterm from it.
 At any of the xterm's (and console) I can enter commands.
 The area where the xterm prints my input text and any resulting
 output text is drawn ... but not the rest of the xterm (which
 remains the background image).
 I can find the top of the xterm box and move it ... it leaves
 a trail of sides of the xterm as it is moved.
 Any xterm over which I move another xterm, does not refresh
 it self.

 Basically, X is unusable.

 # /sbin/lshw -c display
   *-display
description: VGA compatible controller
product: G73 [GeForce 7300 GT]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list
 rom
configuration: driver=nouveau latency=0
resources: irq:29 memory:fd00-fdff memory:d000-dfff
 memory:fc00-fcff ioport:bc00(size=128) memory:fe8e-fe8f

 No nvidia drivers are installed:
  rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep -i nvi
 nothing

  rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
 akmods 0.5.4-1.fc22 noarch
 kmodtool 1-23.fc22 noarch
 libmikmod 3.3.7-1.fc22 x86_64
 kmod-libs 21-1.fc22 x86_64
 kmod 21-1.fc22 x86_64


 The contents of /etc/X11 is the same post upgrade to fedora 22
 as it was for fedora 20 (I kept a copy of 20's /etc/X11 directory).

 In /var/log/Xorg.0.log the same (EE) and (WW) messages
 appear in the fedora 22 as in the fedora 20 log (again, I kept
 a copy).
 The only difference that pops out is that for the fedora 20
 Xorg.0.log the bottom has:

 [ 22527.418] (II) NOUVEAU(0): Printing DDC gathered Modelines:
 [ 22527.418] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680 1728
 1760 1840  1050 1052 1058 1100 -hsync -vsync (64.7 kHz eP)

 but for the 22 Xorg.0.log the bottom has:


 [81.512] (II) NOUVEAU(0): Printing DDC gathered Modelines:
 [81.512] (II) NOUVEAU(0): Modeline 2560x1080x0.0  185.58  2560 2624
 2688 2784  1080 1083 1093  +hsync -vsync (66.7 kHz eP)
 [81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   40.00  800 840 968
 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   31.50  640 656 720
 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   25.18  640 656 752
 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 720x400x0.0   28.32  720 738 846
 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  135.00  1280 1296
 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   78.75  1024 1040
 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   65.00  1024 1048
 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   49.50  800 816 896
 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x800x0.0   71.00  1280 1328
 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680 1728
 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1152x864x0.0  108.00  1152 1216
 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  108.00  1280 1328
 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1920x1080x60.0  172.80  1920 2040
 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)

 which is to say, a lot more gathered Modelines ... whatever that means.

 The nouveau entries in the Xorg.0.log are very similar:

 fedora 20
 .
 [1.801451] nouveau  [ DRM] 0xC272: Parsing digital output script
 table
 [1.903954] nouveau  [ DRM] MM: using M2MF for buffer copies
 [1.903963] nouveau  [ DRM] Setting dpms mode 3 on TV encoder
 (output 3

Re: fedup 20 - 22 - improper X rendering

[Rich Emberson]

I might add that logging in remotely to this machine and then launching an
X-application
that displays on the remote machine works.
So, it seems to be purely a X rendering issue on the machine, the X
protocol works fine.
Richard

On Sat, Aug 8, 2015 at 6:42 PM, Rich Emberson emberson.r...@gmail.com
wrote:

 I used to update:
  fedup --network 22 --product=nonproduct

 Coming up in graphical target as default.target, KDE X does
 not render properly.
 With right click I a small box appears under the cursor,
 navigating to what I guess is the first menu item, I can
 start a console.
 A box appears. I click into it and type:
  xterm
 Another box appears and I can launch another xterm from it.
 At any of the xterm's (and console) I can enter commands.
 The area where the xterm prints my input text and any resulting
 output text is drawn ... but not the rest of the xterm (which
 remains the background image).
 I can find the top of the xterm box and move it ... it leaves
 a trail of sides of the xterm as it is moved.
 Any xterm over which I move another xterm, does not refresh
 it self.

 Basically, X is unusable.

 # /sbin/lshw -c display
   *-display
description: VGA compatible controller
product: G73 [GeForce 7300 GT]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list
 rom
configuration: driver=nouveau latency=0
resources: irq:29 memory:fd00-fdff memory:d000-dfff
 memory:fc00-fcff ioport:bc00(size=128) memory:fe8e-fe8f

 No nvidia drivers are installed:
  rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep -i nvi
 nothing

  rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
 akmods 0.5.4-1.fc22 noarch
 kmodtool 1-23.fc22 noarch
 libmikmod 3.3.7-1.fc22 x86_64
 kmod-libs 21-1.fc22 x86_64
 kmod 21-1.fc22 x86_64


 The contents of /etc/X11 is the same post upgrade to fedora 22
 as it was for fedora 20 (I kept a copy of 20's /etc/X11 directory).

 In /var/log/Xorg.0.log the same (EE) and (WW) messages
 appear in the fedora 22 as in the fedora 20 log (again, I kept
 a copy).
 The only difference that pops out is that for the fedora 20
 Xorg.0.log the bottom has:

 [ 22527.418] (II) NOUVEAU(0): Printing DDC gathered Modelines:
 [ 22527.418] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680 1728
 1760 1840  1050 1052 1058 1100 -hsync -vsync (64.7 kHz eP)

 but for the 22 Xorg.0.log the bottom has:


 [81.512] (II) NOUVEAU(0): Printing DDC gathered Modelines:
 [81.512] (II) NOUVEAU(0): Modeline 2560x1080x0.0  185.58  2560 2624
 2688 2784  1080 1083 1093  +hsync -vsync (66.7 kHz eP)
 [81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   40.00  800 840 968
 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   31.50  640 656 720
 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   25.18  640 656 752
 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 720x400x0.0   28.32  720 738 846
 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  135.00  1280 1296
 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   78.75  1024 1040
 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   65.00  1024 1048
 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   49.50  800 816 896
 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x800x0.0   71.00  1280 1328
 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680 1728
 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1152x864x0.0  108.00  1152 1216
 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  108.00  1280 1328
 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1920x1080x60.0  172.80  1920 2040
 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)

 which is to say, a lot more gathered Modelines ... whatever that means.

 The nouveau entries in the Xorg.0.log are very similar:

 fedora 20
 .
 [1.801451] nouveau  [ DRM] 0xC272: Parsing digital output script
 table
 [1.903954] nouveau  [ DRM] MM: using M2MF for buffer copies
 [1.903963] nouveau  [ DRM] Setting dpms mode 3 on TV encoder
 (output 3)
 [1.959109] nouveau  [ DRM] allocated 2560x1080 fb: 0x9000, bo
 88003693ec00
 [1.959207] fbcon: nouveaufb (fb0) is primary device
 [1.982601

Re: fedup 20 - 22 - improper X rendering

[Rich Emberson]

I am not using the nvidia card. I am using nouveau.

# /usr/sbin/akmods --force
No akmod packages found, nothing to do.[  OK  ]

 rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
akmods 0.5.4-1.fc22 noarch
kmodtool 1-23.fc22 noarch
libmikmod 3.3.7-1.fc22 x86_64
kmod-libs 21-1.fc22 x86_64
kmod 21-1.fc22 x86_64


On Sun, Aug 9, 2015 at 4:34 AM, fedora2015 fedora2...@videotron.ca wrote:

 On 08/08/2015 09:42 PM, Rich Emberson wrote:

 I used to update:
   fedup --network 22 --product=nonproduct

 Coming up in graphical target as default.target, KDE X does
 not render properly.
 With right click I a small box appears under the cursor,
 navigating to what I guess is the first menu item, I can
 start a console.
 A box appears. I click into it and type:
   xterm
 Another box appears and I can launch another xterm from it.
 At any of the xterm's (and console) I can enter commands.
 The area where the xterm prints my input text and any resulting
 output text is drawn ... but not the rest of the xterm (which
 remains the background image).
 I can find the top of the xterm box and move it ... it leaves
 a trail of sides of the xterm as it is moved.
 Any xterm over which I move another xterm, does not refresh
 it self.

 Basically, X is unusable.

 # /sbin/lshw -c display
*-display
 description: VGA compatible controller
 product: G73 [GeForce 7300 GT]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:01:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress vga_controller bus_master
 cap_list rom
 configuration: driver=nouveau latency=0
 resources: irq:29 memory:fd00-fdff
 memory:d000-dfff memory:fc00-fcff ioport:bc00(size=128)
 memory:fe8e-fe8f

 No nvidia drivers are installed:
   rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep -i nvi
 nothing

   rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
 akmods 0.5.4-1.fc22 noarch
 kmodtool 1-23.fc22 noarch
 libmikmod 3.3.7-1.fc22 x86_64
 kmod-libs 21-1.fc22 x86_64
 kmod 21-1.fc22 x86_64


 The contents of /etc/X11 is the same post upgrade to fedora 22
 as it was for fedora 20 (I kept a copy of 20's /etc/X11 directory).

 In /var/log/Xorg.0.log the same (EE) and (WW) messages
 appear in the fedora 22 as in the fedora 20 log (again, I kept
 a copy).
 The only difference that pops out is that for the fedora 20
 Xorg.0.log the bottom has:

 [ 22527.418] (II) NOUVEAU(0): Printing DDC gathered Modelines:
 [ 22527.418] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680
 1728 1760 1840  1050 1052 1058 1100 -hsync -vsync (64.7 kHz eP)

 but for the 22 Xorg.0.log the bottom has:


 [81.512] (II) NOUVEAU(0): Printing DDC gathered Modelines:
 [81.512] (II) NOUVEAU(0): Modeline 2560x1080x0.0  185.58  2560
 2624 2688 2784  1080 1083 1093  +hsync -vsync (66.7 kHz eP)
 [81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   40.00  800 840
 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   31.50  640 656
 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   25.18  640 656
 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 720x400x0.0   28.32  720 738
 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  135.00  1280
 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   78.75  1024 1040
 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   65.00  1024 1048
 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   49.50  800 816
 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x800x0.0   71.00  1280 1328
 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680
 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1152x864x0.0  108.00  1152 1216
 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  108.00  1280
 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
 [81.512] (II) NOUVEAU(0): Modeline 1920x1080x60.0  172.80  1920
 2040 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)

 which is to say, a lot more gathered Modelines ... whatever that means.

 The nouveau entries in the Xorg.0.log are very similar:

 fedora 20
 .
 [1.801451] nouveau  [ DRM] 0xC272: Parsing digital output script
 table
 [1.903954] nouveau  [ DRM] MM: using M2MF for buffer copies
 [1.903963] nouveau  [ DRM] Setting dpms mode 3 on TV

fedup 20 - 22 - improper X rendering

[Rich Emberson]

I used to update:
 fedup --network 22 --product=nonproduct

Coming up in graphical target as default.target, KDE X does
not render properly.
With right click I a small box appears under the cursor,
navigating to what I guess is the first menu item, I can
start a console.
A box appears. I click into it and type:
 xterm
Another box appears and I can launch another xterm from it.
At any of the xterm's (and console) I can enter commands.
The area where the xterm prints my input text and any resulting
output text is drawn ... but not the rest of the xterm (which
remains the background image).
I can find the top of the xterm box and move it ... it leaves
a trail of sides of the xterm as it is moved.
Any xterm over which I move another xterm, does not refresh
it self.

Basically, X is unusable.

# /sbin/lshw -c display
  *-display
   description: VGA compatible controller
   product: G73 [GeForce 7300 GT]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller bus_master cap_list
rom
   configuration: driver=nouveau latency=0
   resources: irq:29 memory:fd00-fdff memory:d000-dfff
memory:fc00-fcff ioport:bc00(size=128) memory:fe8e-fe8f

No nvidia drivers are installed:
 rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep -i nvi
nothing

 rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
akmods 0.5.4-1.fc22 noarch
kmodtool 1-23.fc22 noarch
libmikmod 3.3.7-1.fc22 x86_64
kmod-libs 21-1.fc22 x86_64
kmod 21-1.fc22 x86_64


The contents of /etc/X11 is the same post upgrade to fedora 22
as it was for fedora 20 (I kept a copy of 20's /etc/X11 directory).

In /var/log/Xorg.0.log the same (EE) and (WW) messages
appear in the fedora 22 as in the fedora 20 log (again, I kept
a copy).
The only difference that pops out is that for the fedora 20
Xorg.0.log the bottom has:

[ 22527.418] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 22527.418] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680 1728
1760 1840  1050 1052 1058 1100 -hsync -vsync (64.7 kHz eP)

but for the 22 Xorg.0.log the bottom has:


[81.512] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[81.512] (II) NOUVEAU(0): Modeline 2560x1080x0.0  185.58  2560 2624
2688 2784  1080 1083 1093  +hsync -vsync (66.7 kHz eP)
[81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   40.00  800 840 968
1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   31.50  640 656 720
840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 640x480x0.0   25.18  640 656 752
800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 720x400x0.0   28.32  720 738 846
900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  135.00  1280 1296
1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   78.75  1024 1040
1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1024x768x0.0   65.00  1024 1048
1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 800x600x0.0   49.50  800 816 896
1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1280x800x0.0   71.00  1280 1328
1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1680x1050x0.0  119.00  1680 1728
1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1152x864x0.0  108.00  1152 1216
1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1280x1024x0.0  108.00  1280 1328
1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[81.512] (II) NOUVEAU(0): Modeline 1920x1080x60.0  172.80  1920 2040
2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)

which is to say, a lot more gathered Modelines ... whatever that means.

The nouveau entries in the Xorg.0.log are very similar:

fedora 20
.
[1.801451] nouveau  [ DRM] 0xC272: Parsing digital output script
table
[1.903954] nouveau  [ DRM] MM: using M2MF for buffer copies
[1.903963] nouveau  [ DRM] Setting dpms mode 3 on TV encoder
(output 3)
[1.959109] nouveau  [ DRM] allocated 2560x1080 fb: 0x9000, bo
88003693ec00
[1.959207] fbcon: nouveaufb (fb0) is primary device
[1.982601] nouveau  [ DRM] 0xC272: Parsing digital output script
table
[2.083944] Console: switching to colour frame buffer device 320x67
[2.085254] nouveau :01:00.0: fb0: nouveaufb frame buffer device
[2.085255] nouveau :01:00.0: registered panic notifier
[2.097031] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on
minor 0

fedora 22
.
[1.912410] nouveau  [ DRM

Re: Issue with dnf update after fedup from fc21 to fc22?

[Gordon Messmer]

On 08/01/2015 02:29 AM, Michael D. Setzer II wrote:

It was trying to remove an old fc21 kernel, and it failed with 3 files. Using
yumex I was alble to remove two of the files with no problem, but the
kernel-core gets a similar message.


What message?  What did you remove, exactly?


Error: transaction check vs depsolve:
kernel-uname-r = 4.0.8-300.fc22.x86_64 is needed by (installed)
kmod-VirtualBox-4.0.8-300.fc22.x86_64-4.3.30-1.fc22.x86_64


Looks like something broken with your VirtualBox install, maybe? Try:

dnf install VirtualBox kmod-VirtualBox kernel

...which should pull in the latest version of the kernel, the module for 
VirtualBox, and the VirtualBox application.


If you still have problems, reply with the output of:

rpm -qa \*VirtualBox\* kernel\*
--
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: Closure: fedup 20 - 21 - No Mouse or Keyboard

[Patrick O'Callaghan]

On Sun, 2015-08-02 at 18:37 -0700, Rich Emberson wrote:
 Review my post from previous week or so for background

Why don't you just reply in the same thread?

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

Closure: fedup 20 - 21 - No Mouse or Keyboard

[Rich Emberson]

Review my post from previous week or so for background

First Laptop:

Having failed to upgrade Fedora 22 using fedup on my KDE-base
Fedora 20, I reinstalled Fedora 20.

I downloaded the Workstation Live dvd twice, each time it passed
the 256sha and both time the burned dvd passed the media test ...
but both time after a prolonged time, the sad-face information
widget appeared announcing that the Workstation code not be loaded;
also no mouse or keyboard so I could not interact with the widget.

So, I tried downloading KDE Live  and I came up with
mouse and keyboard something is right about the KDE Live
iso or wrong about the Workstation Live iso.

Then, one more time I executed (going straight to 22 from 20):

 fedup --network 22 --product=nonproduct

After download, reboot, install, etc. I found my self
with the graphics mode login screen with both mouse and
keyboard. I logged in putting me in KDE with, again, mouse
and keyboard.

I did no more experimentation as to why my previous fedup
upgrade had disabled my mouse and keyboard.

Second Laptop:
So, I then took another Fedora 20 laptop (a rather more
recent machine) and executed:

 fedup --network 22 --product=nonproduct

After the upgrade (download, reboot, install, etc.)
I was in multi-user mode and I logged in. Then I execute

 xinit

with my .xinitrc containing:

/usr/bin/startkde

KDE started but I had no mouse or keyboard!!!
So, I changed to graphics mode and rebooted ... yes,
I have mouse and keyboard.

Changed back to multi-user mode ... no mouse or keyboard.
Changed back to graphics mode ... mouse or keyboard.

First Laptop:

Changed to multi-user mode ... no mouse or keyboard.
Changed back to graphics mode ... mouse or keyboard.

So, at least for me and two different KDE laptops,
xinit calling /usr/bin/startkde leaves me with
neither mouse or keyboard.

Just finished upgrading my KDE media server (xbmc - kodi) with

 fedup --network 22 --product=nonproduct

and all when well (in graphics mode).

Thats it. No answers.
I would like to be able to boot into multi-user mode and
then start X/KDE but maybe thats no longer possible
with Fedora 22.

Thanks
Richard
-- 
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: Issue with dnf update after fedup from fc21 to fc22?

[Joe Zeff]

On 08/01/2015 02:29 AM, Michael D. Setzer II wrote:

To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the
issue.


Did you?  If so, what happened?  If not, why not?
--
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

Issue with dnf update after fedup from fc21 to fc22?

[Michael D. Setzer II]

Everything seemed to go thru fine with the update, but then running dnf 
update ran into a strange issue.

It was trying to remove an old fc21 kernel, and it failed with 3 files. Using 
yumex I was alble to remove two of the files with no problem, but the 
kernel-core gets a similar message. Tried both of the options it mentions at 
the end, but still get the message. 

Not sure why it is giving a message about kernel 4.0.8, when it is remove 
4.0.5?

Output of dnf update

Last metadata expiration check performed 0:03:32 ago on Sat Aug  1 
18:48:59 2015.
Dependencies resolved.
==
==
 PackageArch  Version  Repository  Size
==
==
Removing:
 kernel-corex86_644.0.5-200.fc21   @System 41 M

Transaction Summary
==
==
Remove  1 Package

Installed size: 41 M
Running transaction check
Error: transaction check vs depsolve:
kernel-uname-r = 4.0.8-300.fc22.x86_64 is needed by (installed) 
kmod-VirtualBox-4.0.8-300.fc22.x86_64-4.3.30-1.fc22.x86_64
To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix the 
issue.
+--+
  Michael D. Setzer II -  Computer Science Instructor  
  Guam Community College  Computer Center  
  mailto:mi...@kuentos.guam.net
  mailto:msetze...@gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+--+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ROSETTA 32408662.306644   |   SETI57744168.704351
ABC 16613838.513356   |   EINSTEIN66898810.510895

-- 
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: fedup 20 - 21 - xinit - KDE - open /dev/fb0: No such file or directory

[Ed Greshko]

On 07/28/15 11:41, richard emberson wrote:
 ]# journalctl -b 0 | grep -i mouse
 Jul 27 19:52:02 localhost.localdomain kernel: mousedev: PS/2 mouse device 
 common for all mice
 Jul 27 19:52:02 localhost.localdomain kernel: usb 7-1: Product: USB Optical 
 Mouse
 Jul 27 19:52:02 localhost.localdomain kernel: input: PixArt USB Optical Mouse 
 as 
 /devices/pci:00/:00:1d.1/usb7/7-1/7-1:1.0/0003:093A:2510.0001/input/input6
 Jul 27 19:52:02 localhost.localdomain kernel: hid-generic 
 0003:093A:2510.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical 
 Mouse] on usb-:00:1d.1-1/input0
 Jul 27 19:52:02 localhost.localdomain kernel: psmouse serio1: synaptics: 
 Touchpad model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04711/0x20/0x0, board 
 id: 0, fw id: 496485
 Jul 27 19:52:49 localhost.localdomain kernel: input: MCE IR Keyboard/Mouse 
 (ene_ir) as /devices/virtual/input/input10
 Jul 27 19:52:49 localhost.localdomain kernel: IR MCE Keyboard/mouse protocol 
 handler initialized
 # journalctl -b 0 | grep -i keyb
 Jul 27 19:52:02 localhost.localdomain kernel: input: AT Translated Set 2 
 keyboard as /devices/platform/i8042/serio0/input/input3
 Jul 27 19:52:49 localhost.localdomain kernel: input: MCE IR Keyboard/Mouse 
 (ene_ir) as /devices/virtual/input/input10
 Jul 27 19:52:49 localhost.localdomain kernel: IR MCE Keyboard/mouse protocol 
 handler initialized

 I appreciate the help. I've been downloading the fedora 22
 workstation and server dvds just in case.
 Re-installing my laptops is not much of a problem, its my home
 servers where I want to be sure prior to going from fedora x to x+1.
 Also, I'd like to keep using KDE, but, at least for this laptop,
 that may not be possible. 

Well, that all looks in order.

So, you are able to boot and you do get a graphical login screen, but you don't 
get a cursor and you can't type a password.

You looked in the fedup log, located in /var/log, and see no errors.

I'm fairly sure the lack of XINPUT lines in the Xorg log is tellingjust 
have no idea what could be the issue.

I've not had a failure in fedup such as this and I've been using it for the 
past several releases.


-- 
If I wanted a blog or social media I'd go elsewhere
-- 
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

fedup 20 - 21 - xinit - KDE - No mouse/keyboard input

[Rich Emberson]

Thanks for the suggestion.

Contents of /var/cache/akmods/akmods.log
START
2015/07/25 16:06:18 akmods: Checking kmods exist for 4.0.8-200.fc21.x86_64
2015/07/25 16:06:18 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 16:06:18 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-200.fc21.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/25 16:07:03 akmods: Installing newly built rpms
2015/07/25 16:07:03 akmods: DNF detected
2015/07/25 16:07:20 akmods: Successful.
2015/07/25 17:22:20 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/25 17:22:20 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 17:22:20 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/25 18:07:53 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/25 18:07:53 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 18:07:54 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/26 14:05:01 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/26 14:05:01 akmods: Building and installing nvidia-340xx-kmod
2015/07/26 14:05:01 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/26 14:05:47 akmods: Installing newly built rpms
2015/07/26 14:05:47 akmods: DNF detected
2015/07/26 14:06:00 akmods: Successful.
END

ran:
 /usr/sbin/akmods --force

and now the file has the additional line:
2015/07/27 14:54:21 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64

Still no mouse or keyboard.


Thanks
Richard
-- 
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: fedup 20 - 21 - xinit - KDE - open /dev/fb0: No such file or directory

[Ed Greshko]

On 07/27/15 08:00, Rich Emberson wrote:
 Still no mouse or keyboard. Don't know if this is the problem.

 from /var/log/Xorg.0.log

Well, the /dev/fb0 is not related to your keyboard/mouse problem since that 
device is a frame buffer which is related to video.  My reason for suggesting 
what I did is that I only see this error on my systems when the nVidia drivers 
are not installed.

What type of keyboard/mouse do you have?  PS2, USB, Bluetooth?

If you

grep input device /var/log/Xorg.0.log | grep XINPUT

what do you get?

On one system I have a USB keyboard/mouse combination and I see...

[egreshko@meimei log]$ grep input device Xorg.0.log | grep XINPUT
[338349.680] (II) XINPUT: Adding extended input device Power Button (type: 
KEYBOARD, id 6)
[338349.680] (II) XINPUT: Adding extended input device Power Button (type: 
KEYBOARD, id 7)
[338349.682] (II) XINPUT: Adding extended input device Logitech M310 (type: 
MOUSE, id 8)
[338349.683] (II) XINPUT: Adding extended input device Logitech K520 (type: 
KEYBOARD, id 9)

While on my laptop I see

[egreshko@acer log]$  grep input device Xorg.0.log | grep XINPUT
[64.585] (II) XINPUT: Adding extended input device Power Button (type: 
KEYBOARD, id 6)
[64.594] (II) XINPUT: Adding extended input device Video Bus (type: 
KEYBOARD, id 7)
[64.606] (II) XINPUT: Adding extended input device Power Button (type: 
KEYBOARD, id 8)
[64.615] (II) XINPUT: Adding extended input device Sleep Button (type: 
KEYBOARD, id 9)
[64.627] (II) XINPUT: Adding extended input device Acer CrystalEye webcam 
(type: KEYBOARD, id 10)
[64.695] (II) XINPUT: Adding extended input device Logitech Optical USB 
Mouse (type: MOUSE, id 11)
[64.759] (II) XINPUT: Adding extended input device AT Translated Set 2 
keyboard (type: KEYBOARD, id 12)
[64.777] (II) XINPUT: Adding extended input device SynPS/2 Synaptics 
TouchPad (type: TOUCHPAD, id 13)
[64.795] (II) XINPUT: Adding extended input device SynPS/2 Synaptics 
TouchPad (type: TOUCHPAD, id 14)


But, rather than picking out bits and pieces of your Xorg log file, maybe post 
it somewhere for everyone to see?

-- 
If I wanted a blog or social media I'd go elsewhere
-- 
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: fedup 20 - 21 - xinit - KDE - open /dev/fb0: No such file or directory

[Ed Greshko]

On 07/28/15 10:57, richard emberson wrote:
 See below

 On 07/27/2015 07:33 PM, Ed Greshko wrote:
 On 07/28/15 09:50, richard emberson wrote:

 grep input device /var/log/Xorg.0.log | grep XINPUT
 nothing found

 Its a Jetta laptop with touch pad (which, like the usb optical mouse, also 
 does not work) and builtin keyboard.

 What is in your /etc/X11/xorg.conf ?   It should only contain
 I do not have a xorg.conf file, but I do have a nvidia-xorg.conf
 which is the same as your xorg.conf file you showed below.
 (but, if I change the name of it from nvidia-xorg.conf to
 xorg.conf, I still have no mouse/keyboard).

 # RPM Fusion - nvidia-xorg.conf
 #
 Section Device
  Identifier  Videocard0
  Driver  nvidia
 EndSection

 Also, what files do you have in the /etc/X11/xorg.conf.d directory?

 # ls -l xorg.conf.d/
 total 12
 -rw-r--r--. 1 root root 108 Jan 11  2015 00-avoid-glamor.conf
 -rw-r--r--. 1 root root 232 Jan 13  2015 00-keyboard.conf
 -rw-r--r--. 1 root root 178 Jan 11  2015 99-nvidia.conf



FWIW, all of my systems report something for XINPUT in the Xorg log...

Also, what do you get for these commands?

journalctl -b 0 | grep -i mouse
journalctl -b 0 | grep -i keyb

Sadly, I'm running out of ideas...






-- 
If I wanted a blog or social media I'd go elsewhere
-- 
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: fedup 20 - 21 - xinit - KDE - open /dev/fb0: No such file or directory

[Ed Greshko]

On 07/28/15 09:50, richard emberson wrote:

 grep input device /var/log/Xorg.0.log | grep XINPUT
 nothing found

 Its a Jetta laptop with touch pad (which, like the usb optical mouse, also 
 does not work) and builtin keyboard.

What is in your /etc/X11/xorg.conf ?   It should only contain

# RPM Fusion - nvidia-xorg.conf
#
Section Device
Identifier  Videocard0
Driver  nvidia
EndSection

Also, what files do you have in the /etc/X11/xorg.conf.d directory?

[egreshko@meimei X11]$ ls -l xorg.conf.d/
total 12
-rw-r--r--. 1 root root 161 Dec 26  2012 00-anaconda-keyboard.conf
-rw-r--r--. 1 root root 108 Dec  2  2013 00-avoid-glamor.conf
-rw-r--r--. 1 root root 178 Feb  7  2014 99-nvidia.conf

I find the following odd in your log file

 [ 10029.383] (==) Matched nvidia as autoconfigured driver 0
 [ 10029.383] (==) Matched nouveau as autoconfigured driver 1
 [ 10029.383] (==) Matched nv as autoconfigured driver 2
 [ 10029.383] (==) Matched nouveau as autoconfigured driver 3
 [ 10029.383] (==) Matched nv as autoconfigured driver 4
 [ 10029.383] (==) Matched modesetting as autoconfigured driver 5
 [ 10029.383] (==) Matched fbdev as autoconfigured driver 6
 [ 10029.383] (==) Matched vesa as autoconfigured driver 7

I don't see any mention of nouveau in my log files except in the kernel command 
line.



-- 
If I wanted a blog or social media I'd go elsewhere
-- 
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

fedup 20 - 21 - xinit - error setting MTRR

[Rich Emberson]

What is causing the MTRR error in the xinit output?

cat /proc/mtrr
reg00: base=0x0 (0MB), size= 4096MB, count=1: write-back
reg01: base=0x1 ( 4096MB), size= 1024MB, count=1: write-back
reg02: base=0x0c000 ( 3072MB), size= 1024MB, count=1: uncachable



Part of xinit output with a number of errors.
The MTRR error is the first one:
START xinit output

(==) Log file: /var/log/Xorg.0.log, Time: Sun Jul 26 11:27:32 2015
(==) Using config directory: /etc/X11/xorg.conf.d
(==) Using system config directory /usr/share/X11/xorg.conf.d
error setting MTRR (base = 0xfb00, size = 0x00e0, type = 1) Invalid
argument (22)
Failed to close file descriptor: Could not close fd 11

Failed to close file descriptor: Could not close fd 11
startkde: Starting up...
Qt: Session management error: networkIdsList argument is NULL
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Qt: Session management error: networkIdsList argument is NULL
kbuildsycoca5 running...
kf5.kded: kded module proxyscout has already been found using JSON
metadata, please don't install the now unneeded .desktop file
(kded/proxyscout.desktop).
kf5.kded: found kded module statusnotifierwatcher by prepending 'kded_'
to the library path, please fix your metadata.

powerdevil: No outputs have backlight property
/home/emberson/.local/share/icc/.. is not an ICC profile
/home/emberson/.local/share/icc/. is not an ICC profile
Qt: Session management error: networkIdsList argument is NULL
Service started, version: 6.2.0
QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought
it was ':1.27'
Unable to get EDID for output default
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it
was ':1.9'
Failed to create ICC profile on cmsCreateRGBProfile

Qt: Session management error: networkIdsList argument is NULL
Xlib:  extension GLX missing on display :0.

Could not initialize GLX
KCrash: Application 'krunner' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
Invalid service name /org/kde/polkit-kde-authentication-agent-1 using:
/org/kde/polkitkdeauthenticationagent1
kcminit not running? If we are running with mobile profile or in another
platform other than X11 this is normal.

kwin_core: screens:  1 desktops:  1
kwin_core: Done.
kwin_core: screens:  1 desktops:  1
kwin_core: Done.
Invalid pixmap specified.

kf5.kded: found kded module touchpad by prepending 'kded_' to the library
path, please fix your metadata.
Xlib:  extension GLX missing on display :0.
kmix: kmixd: Delayed initialization running now
kmix: kmixd: Delayed initialization done
Xlib:  extension GLX missing on display :0.

Application::crashHandler() called with signal 6; recent crashes: 1
KXMLGUI file found at deprecated location (/usr/share/kmix/kmixui.rc) --
please use ${KXMLGUI_INSTALL_DIR} to install this file instead.

END xinit output
From /var/log/X.org.0:
  Why attempt to load nouveau and nv ?
  Can not determine screen size.
START log
[   109.258] (II) glx will be loaded by default.
[   109.258] (II) LoadModule: glx
[   109.278] (II) Loading /usr/lib64/nvidia-340xx/xorg/libglx.so
[   110.766] (II) Module glx: vendor=NVIDIA Corporation
[   110.767]compiled for 4.0.2, module version = 1.0.0
[   110.767]Module class: X.Org Server Extension
[   110.771] (II) NVIDIA GLX Module  340.76  Thu Jan 22 11:24:42 PST 2015
[   110.785] (==) Matched nouveau as autoconfigured driver 0
[   110.785] (==) Matched nv as autoconfigured driver 1
[   110.785] (==) Matched modesetting as autoconfigured driver 2
[   110.785] (==) Matched fbdev as autoconfigured driver 3
[   110.785] (==) Matched vesa as autoconfigured driver 4
[   110.785] (==) Assigned the driver to the xf86ConfigLayout
[   110.785] (II) LoadModule: nouveau
[   110.820] (WW) Warning, couldn't open module nouveau
[   110.820] (II) UnloadModule: nouveau
[   110.820] (II) Unloading nouveau
[   110.820] (EE) Failed to load module nouveau (module does not exist, 0)
[   110.820] (II) LoadModule: nv
[   110.821] (WW) Warning, couldn't open module nv
[   110.821] (II) UnloadModule: nv
[   110.821] (II) Unloading nv
[   110.821] (EE) Failed to load module nv (module does not exist, 0)
[   110.821] (II) LoadModule: modesetting
[   110.821] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   110.828] (II) Module modesetting: vendor=X.Org Foundation
[   110.828]compiled for 1.17.2, module version = 1.17.2
[   110.828]Module class: X.Org Video Driver
[   110.828]ABI class: X.Org Video Driver, version 19.0
[   110.828] (II) LoadModule: fbdev
[   110.828] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so[
110.838] (II) Module fbdev: vendor=X.Org Foundation
[   110.838]compiled for 1.17.1, module version = 0.4.3
[   110.838]Module class: X.Org Video Driver
[   110.838]ABI class: X.Org Video Driver, version 19.0
[   110.838] (II) 

fedup 20 - 21 - xinit - KDE - open /dev/fb0: No such file or directory

[Rich Emberson]

Still no mouse or keyboard. Don't know if this is the problem.

from /var/log/Xorg.0.log
START
[96.019] (II) Loading sub module fb
[96.019] (II) LoadModule: fb
[96.020] (II) Loading /usr/lib64/xorg/modules/libfb.so
[96.030] (II) Module fb: vendor=X.Org Foundation
[96.030]compiled for 1.17.2, module version = 1.0.0
[96.030]ABI class: X.Org ANSI C Emulation, version 0.4
[96.030] (WW) Unresolved symbol: fbGetGCPrivateKey
[96.030] (II) Loading sub module wfb
[96.030] (II) LoadModule: wfb
[96.030] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[96.041] (II) Module wfb: vendor=X.Org Foundation
[96.041]compiled for 1.17.2, module version = 1.0.0
[96.041]ABI class: X.Org ANSI C Emulation, version 0.4
[96.041] (II) Loading sub module ramdac
[96.041] (II) LoadModule: ramdac
[96.041] (II) Module ramdac already built-in
[96.068] (WW) Falling back to old probe method for modesetting
[96.068] (WW) Falling back to old probe method for fbdev
[96.068] (II) Loading sub module fbdevhw
[96.068] (II) LoadModule: fbdevhw
[96.068] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[96.082] (II) Module fbdevhw: vendor=X.Org Foundation
[96.082]compiled for 1.17.2, module version = 0.0.2
[96.082]ABI class: X.Org Video Driver, version 19.0
[96.082] (EE) open /dev/fb0: No such file or directory
[96.082] (WW) Falling back to old probe method for vesa
[96.082] (II) NVIDIA(0): Creating default Display subsection in Screen
section
Default Screen Section for depth/fbbpp 24/32
[96.082] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[96.082] (==) NVIDIA(0): RGB weight 888
[96.082] (==) NVIDIA(0): Default visual is TrueColor
..
END

Thanks
Richard
-- 
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: fedup 20 - 21 - xinit - KDE - open /dev/fb0: No such file or directory

[Ed Greshko]

On 07/27/15 08:00, Rich Emberson wrote:
 Still no mouse or keyboard. Don't know if this is the problem.

 from /var/log/Xorg.0.log
 START
 [96.019] (II) Loading sub module fb
 [96.019] (II) LoadModule: fb
 [96.020] (II) Loading /usr/lib64/xorg/modules/libfb.so
 [96.030] (II) Module fb: vendor=X.Org Foundation
 [96.030]compiled for 1.17.2, module version = 1.0.0
 [96.030]ABI class: X.Org ANSI C Emulation, version 0.4
 [96.030] (WW) Unresolved symbol: fbGetGCPrivateKey
 [96.030] (II) Loading sub module wfb
 [96.030] (II) LoadModule: wfb
 [96.030] (II) Loading /usr/lib64/xorg/modules/libwfb.so
 [96.041] (II) Module wfb: vendor=X.Org Foundation
 [96.041]compiled for 1.17.2, module version = 1.0.0
 [96.041]ABI class: X.Org ANSI C Emulation, version 0.4
 [96.041] (II) Loading sub module ramdac
 [96.041] (II) LoadModule: ramdac
 [96.041] (II) Module ramdac already built-in
 [96.068] (WW) Falling back to old probe method for modesetting
 [96.068] (WW) Falling back to old probe method for fbdev
 [96.068] (II) Loading sub module fbdevhw
 [96.068] (II) LoadModule: fbdevhw
 [96.068] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
 [96.082] (II) Module fbdevhw: vendor=X.Org Foundation
 [96.082]compiled for 1.17.2, module version = 0.0.2
 [96.082]ABI class: X.Org Video Driver, version 19.0
 [96.082] (EE) open /dev/fb0: No such file or directory
 [96.082] (WW) Falling back to old probe method for vesa
 [96.082] (II) NVIDIA(0): Creating default Display subsection in Screen 
 section
 Default Screen Section for depth/fbbpp 24/32
 [96.082] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
 [96.082] (==) NVIDIA(0): RGB weight 888
 [96.082] (==) NVIDIA(0): Default visual is TrueColor

Oh, I see you are using the nVidia drivers.  From rpmfusion?  Using the 
akmod-nvidia package as well?

If you are, you need to be aware that currently there is a problem with dnf 
keeping the rpmdb locked when the kmod-nvidia package for the new kernels are 
built.  This will also result in them not being built during fedup.

Check the log file /var/cache/akmods/akmods.log for errors. 

A common way to fix the problem is to run this command as root

/usr/sbin/akmods --force   and then reboot.


-- 
If I wanted a blog or social media I'd go elsewhere
-- 
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

fedup 20 - 21 - 22 - Plasma closed unexpectedly

[Rich Emberson]

Also see MTRR issue below.

On 07/25/2015 07:01 PM, Ed Greshko wrote:

You're a KDE user and quite a bit has changed.  One question and one
suggestion

Q.  Just for information...  Are you using kdm or sddm as your display
manager?


How does one find which display manager is being used?


Suggestion

After reboot, login from a different machine and create a fresh user.  Then
login as that new user to see if you have the same issue.





New in xinit output:
START
...
(==) Using config directory: /etc/X11/xorg.conf.d
(==) Using system config directory /usr/share/X11/xorg.conf.d
error setting MTRR (base = 0xfb00, size = 0x00e0, type = 1) Invalid
argument (22)
Failed to close file descriptor: Could not close fd 11
Failed to close file descriptor: Could not close fd 11
...
END

Contents of /proc/mtrr
START
reg00: base=0x0 (0MB), size= 4096MB, count=1: write-back
reg01: base=0x1 ( 4096MB), size= 1024MB, count=1: write-back
reg02: base=0x0c000 ( 3072MB), size= 1024MB, count=1: uncachable
END

What is MTRR?
I assume that the error is not a good-thing.

Also, curiously, when I switch to graphical mode
  ln -sf /lib/systemd/system/graphical.target
/etc/systemd/system/default.target
and then reboot
hoping to get the graphicial login ... just to see if I can
pick the desktop there...
after the reboot the system has been set back to the
multi-user.target

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

fedup 20 - 21 - xinit - KDE - No mouse/keyboard input

[Rich Emberson]

So, I am now at the point where xinit (calling startkde)
has the KDE screen appearing, but ...

The pointer-cursor appears but can not be moved by the mouse, and
(after some timeout and the login screen appears) keyboard
entry fails.

What does one do to enable both the mouse and keyboard.

Thanks
Richard
-- 
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: fedup 20 - 21 - 22 - Plasma closed unexpectedly

[Joe Zeff]

On 07/25/2015 07:01 PM, Ed Greshko wrote:

After reboot, login from a different machine and create a fresh user.  Then 
login as that new user to see if you have the same issue.


Either that or simply change to a text console without logging in at the 
GUI.  And, while you're at it, activate the Magic SysRq key and test it 
(Different mobos require different combinations of keys to activate it.) 
so that if it locks up again, you can reboot easier.

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

fedup 20 - 21 - No X

[Rich Emberson]

Ah, fedora upgrades using fedup ...

Starting with Fedora 20, did
   yum update
and then
   fedup --network 21 --product=nonproduct
Took a while but there were no issues but
remember, as root
   export PATH=$PATH:$HOME/bin:/sbin:/usr/sbin
or use
   su -
to become root otherwise fedup has an issue.

So, now rebooted and it started.
I have all my machines in multi-user mode just
in case there is an issue with X.
Now tried to start X ... and there was an issue.

From bottom of /var/log/Xorg.0.log
[53.686] (II) Module dri2 already built-in
[53.686] (EE) NOUVEAU(0): [drm] failed to set drm interface version.
[53.686] (EE) NOUVEAU(0): [drm] error opening the drm
[53.686] (EE) NOUVEAU(0): 892:
[53.686] (II) UnloadModule: nouveau
[53.686] (EE) Screen(s) found, but none have a usable configuration.
[53.686] (EE)
Fatal server error:
[53.686] (EE) no screens found(EE)

START ALL /var/log/Xorg.0.log
[67.937]
X.Org X Server 1.16.3
Release Date: 2014-12-20
[67.937] X Protocol Version 11, Revision 0
[67.937] Build Operating System:  3.17.8-300.bz1178975.fc21.x86_64
[67.937] Current Operating System: Linux localhost.localdomain
4.0.8-200.fc21.x86_64 #1 SMP Fri Jul 10 21:09:54 UTC 2015 x86_64
[67.937] Kernel command line: BOOT_IMAGE=/vmlinuz-4.0.8-200.fc21.x86_64
root=/dev/mapper/luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1 ro
rd.luks.uuid=luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1
vconsole.font=latarcyrheb-sun16
rd.luks.uuid=luks-8597ed23-e47c-427d-834c-e2fc5ec21bd3 rhgb quiet
LANG=en_US.UTF-8
[67.937] Build Date: 31 January 2015  11:23:27PM
[67.937] Build ID: xorg-x11-server 1.16.3-2.fc21
[67.937] Current version of pixman: 0.32.6
[67.937]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[67.937] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[67.937] (==) Log file: /var/log/Xorg.0.log, Time: Fri Jul 24
21:05:21 2015
[67.937] (==) Using config directory: /etc/X11/xorg.conf.d
[67.937] (==) Using system config directory /usr/share/X11/xorg.conf.d
[67.938] (==) No Layout section.  Using the first Screen section.
[67.938] (==) No screen section available. Using defaults.
[67.938] (**) |--Screen Default Screen Section (0)
[67.938] (**) |   |--Monitor default monitor
[67.938] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[67.938] (==) Automatically adding devices
[67.938] (==) Automatically enabling devices
[67.938] (==) Automatically adding GPU devices
[67.938] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[67.938] (==) ModulePath set to /usr/lib64/xorg/modules
[67.938] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[67.938] (II) Loader magic: 0x81de40
[67.938] (II) Module ABI versions:
[67.938]X.Org ANSI C Emulation: 0.4
[67.938]X.Org Video Driver: 18.0
[67.938]X.Org XInput driver : 21.0
[67.938]X.Org Server Extension : 8.0
[67.943] (II) systemd-logind: took control of session
/org/freedesktop/login1/session/_32
[67.944] (II) xfree86: Adding drm device (/dev/dri/card0)
[67.944] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10
paused 0
[67.946] (--) PCI:*(0:6:0:0) 10de:0649:1462:7220 rev 161, Mem @
0xfd00/16777216, 0xd000/268435456, 0xfa00/33554432, I/O @
0xec00/128, BIOS @ 0x/524288
[67.946] (II) LoadModule: glx
[67.946] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[67.948] (II) Module glx: vendor=X.Org Foundation
[67.948]compiled for 1.16.3, module version = 1.0.0
[67.948]ABI class: X.Org Server Extension, version 8.0
[67.948] (==) AIGLX enabled
[67.948] (==) Matched nouveau as autoconfigured driver 0
[67.948] (==) Matched nv as autoconfigured driver 1
[67.948] (==) Matched nouveau as autoconfigured driver 2
[67.948] (==) Matched nv as autoconfigured driver 3
[67.948] (==) Matched modesetting as autoconfigured driver 4
[67.948] (==) Matched fbdev as autoconfigured driver 5
[67.948] (==) Matched vesa as autoconfigured driver 6
[67.948] (==) Assigned the driver to the xf86ConfigLayout
[67.948] (II) LoadModule: nouveau
[67.991] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so
[67.991] (II) Module nouveau: vendor=X.Org Foundation
[67.991]compiled for 1.16.1, module version = 1.0.11
[67.991]Module class: X.Org Video Driver
[67.991]ABI class: X.Org Video Driver, version 18.0
[67.991] (II) LoadModule: nv
[67.991] (WW) Warning, couldn't open module nv
[67.991] (II) UnloadModule

Re: fedup 20 - 21 - No X

[stan]

On Sat, 25 Jul 2015 06:37:10 -0700
Rich Emberson emberson.r...@gmail.com wrote:

 Ah, fedora upgrades using fedup ...
 
 Starting with Fedora 20, did
yum update
 and then
fedup --network 21 --product=nonproduct
 Took a while but there were no issues but
 remember, as root
export PATH=$PATH:$HOME/bin:/sbin:/usr/sbin
 or use
su -
 to become root otherwise fedup has an issue.
 
 So, now rebooted and it started.
 I have all my machines in multi-user mode just
 in case there is an issue with X.
 Now tried to start X ... and there was an issue.
[snip]
 [2.969504] fbcon: nouveaufb (fb0) is primary device
 [3.284089] nouveau :06:00.0: fb0: nouveaufb frame buffer
 device [3.284091] nouveau :06:00.0: registered panic notifier
 [3.290053] [drm] Initialized nouveau 1.2.1 20120801 for
 :06:00.0 on minor 0
 END dmesg
 
 So, fedup somehow blew away something.
 The Question is what?
 
 rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
 kmod-libs 19-1.fc21 x86_64
 kmod 19-1.fc21 x86_64
 
 What did fedup change and how can I recover?

If you're using kmod, that means you've been using the rpmfusion nvidia
binary driver, right?  But it looks like the kernel is trying to use the
nouveau open source driver.  They're incompatible.

Maybe you need to set up to use the nvidia binary blob again.  I think
this involves blacklisting nouveau and installing the nvidia driver for
your kernel.  There should be instructions you can find online, or in
the archives of this list, for how to do this.

-- 
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: fedup 20 - 21 - 22 - Plasma closed unexpectedly

[Ed Greshko]

On 07/26/15 09:51, Rich Emberson wrote:
 X starts but there is no mouse control (pointer on screen
 but the mouse does not move it) and after a minute or
 less I get an widget stating that the Plasma desktop
 closed unexpectedly.

 I have to login from another machine to do a reboot.

You're a KDE user and quite a bit has changed.  One question and one 
suggestion

Q.  Just for information...  Are you using kdm or sddm as your display manager?

Suggestion

After reboot, login from a different machine and create a fresh user.  Then 
login as that new user to see if you have the same issue.

-- 
If I wanted a blog or social media I'd go elsewhere
-- 
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