Re: fedup from 20 to 21

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 mir

Re: fedup from 20 to 21

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

Re: fedup from 20 to 21

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

Re: fedup from 20 to 21

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

Re: fedup from 20 to 21

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 ju

Re: fedup from 20 to 21

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 fro

Re: fedup from 20 to 21

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

Re: fedup from 20 to 21

Sure, fedup doesn't edit my scripts, but should update my system ... On Tue, Nov 15, 2016 at 12:31 PM, Patrick O'Callaghan 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

Re: fedup from 20 to 21

ackups 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

Re: fedup from 20 to 21

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

on ... I should to remake my machine from scratch? On Tue, Nov 15, 2016 at 11:14 AM, Patrick O'Callaghan 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 mo

Re: fedup from 20 to 21

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 &

Re: fedup from 20 to 21

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

Re: fedup from 20 to 21

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

Re: fedup from 20 to 21

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 us

Re: fedup from 20 to 21

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

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

Re: Botched fedup F23 -> F24 with nvidia

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 rpmf

Re: Botched fedup F23 -> F24 with nvidia

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

Re: Botched fedup F23 -> F24 with nvidia

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 wh

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

On Fri, 04 Nov 2016 17:17:09 +0100 Mark 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 > Ri

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

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 Te

Re: Botched fedup F23 -> F24 with nvidia

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 succe

Re: Botched fedup F23 -> F24 with nvidia

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 ju

Botched fedup F23 -> F24 with nvidia

n.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 &

fedup F20 to F24

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 wonder

Re: Issues with doing a fedup upgrade from 23 to 24

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

Issues with doing a fedup upgrade from 23 to 24

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

Re: Black screen and no response after fedup update to 22?

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

Black screen and no response after fedup update to 22?

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 po

Re: fedup to F22 issues

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 hel

Re: fedup to F22 issues

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 w

Re: fedup to F22 issues

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

fedup to F22 issues

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

Re: fedup leaves me stuck between 21 and 22

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

Re: fedup leaves me stuck between 21 and 22

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

Re: fedup leaves me stuck between 21 and 22

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

Re: fedup leaves me stuck between 21 and 22

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

Re: fedup leaves me stuck between 21 and 22

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

Re: fedup leaves me stuck between 21 and 22

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

Re: fedup leaves me stuck between 21 and 22

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

fedup leaves me stuck between 21 and 22

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

Re: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

That kernel is from fc21and should be removed from fc22 system. On Sep 21, 2015 9: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 probl

Re: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

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 re

Re: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

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

Re: [Solved]: After fedup fc21 to fc22 dnf wanted to install kernel fc21-4.1.4-100

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

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

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

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

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

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

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

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

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 th

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

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

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

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 r

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

y 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 fedup (which you say should not behave as it does), and it still tries to unsuccessfully

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

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_

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

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 me

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

list", 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 cu

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

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

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

f 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/mail

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

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

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

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 too

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

-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

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

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

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

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 R

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

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

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

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

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

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

Re: gnome embedded screencast tool unavailable after fedup to federa22

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 em

Re: gnome embedded screencast tool unavailable after fedup to federa22

PS: My Video card is GTX560TI and installed the commercial driver from rpmfusion. 2015-09-15 11:55 GMT+08:00 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 +

gnome embedded screencast tool unavailable after fedup to federa22

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

fedup Q: re: --product=nonproduct

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 fl

Re: Fedup half-complete

On Sun, 23 Aug 2015 12:14:32 +0100, Timothy Murphy wrote: > I followed the instructions at > > 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 w

Re: Fedup half-complete

On 08/23/15 19:14, Timothy Murphy wrote: > I followed the instructions at > > 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

Fedup half-complete

I followed the instructions at 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 h

Re: fedup 20 -> 22 -> improper X rendering

te 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 wrote: > I used to update: > > fedup --network 22 --product=nonproduct > > Coming up in graphical target as default.target, KD

Re: fedup 20 -> 22 -> improper X rendering

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 consol

Re: fedup 20 -> 22 -> improper X rendering

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 wrote: > On 08/08/2015 09:42 PM, Rich Emberson wrote: > >> I used to update: >> > fedup --network 22 --product=nonproduct >> >> Coming up in graphic

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

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

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

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 fedor

Sound and networking not working after fedup from 20 to 22

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 functio

Re: fedup 20 -> 22 -> improper X rendering

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 i

fedup 20 -> 22 -> improper X rendering

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 cl

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

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

Re: Closure: fedup 20 -> 21 -> No Mouse or Keyboard

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

Closure: fedup 20 -> 21 -> No Mouse or Keyboard

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

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

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

Issue with dnf update after fedup from fc21 to fc22?

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

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

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

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

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 >>> >>> >>> Its a Jetta laptop with touch pad (which, like the usb optical mouse, also >

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

On 07/28/15 09:50, richard emberson wrote: > > grep "input device" /var/log/Xorg.0.log | grep XINPUT > > > 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 Fu

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

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

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

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

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

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

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

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]

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

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

fedup 20 -> 21 -> xinit -> error setting MTRR

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

fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly

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

Re: fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly

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

Re: fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly

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

fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly

Again, fedora upgrades using fedup ... Starting with Fedora 20, did ... stuff ... > fedup --network 21 --product=nonproduct ... stuff ... > fedup --network 22 --product=nonproduct So, now rebooted and it started. I have all my machines in multi-user mode just in case there is an

Re: fedup 20 -> 21 -> No X

On Sat, 25 Jul 2015 06:37:10 -0700 Rich Emberson 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

  1   2   3   4   5   6   7   8   9   >