Today I issues a fedup-cli network 19 command (
At the end of procedure that ended right when rebooting I get
Bad news:
I get a black window if I login as any user with a fedora logo on the bottom of screen but I can use tty and then issue a startx
Good news after issuing startx my old video card (Geforce FX5200) works fine with Gnome 3.
Why do I have only F18 kernel??
Tnx
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:17:
Today I issues a fedup-cli network 19 command (
At the end of procedure that ended right when rebooting I get
Bad news:
I get a black window if I login as any user with a fedora logo on the bottom of screen but I can use tty and then issue a startx
Good news after issuing startx my old video card (Geforce FX5200) works fine with Gnome 3.
Why do I have only F18 kernel??
Tnx
more info:
I have two users, when I issue startx with user A (that is coming from F18) I get the message oh no something went wrong, while a fresh user B can issue startx flawlessy.
Also root can startx with no problem
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:39:
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:17:
Today I issues a fedup-cli network 19 command (
At the end of procedure that ended right when rebooting I get
Bad news:
I get a black window if I login as any user with a fedora logo on the bottom of screen but I can use tty and then issue a startx
Good news after issuing startx my old video card (Geforce FX5200) works fine with Gnome 3.
Why do I have only F18 kernel??
Tnx
more info:
I have two users, when I issue startx with user A (that is coming from F18) I get the message oh no something went wrong, while a fresh user B can issue startx flawlessy.
Also root can startx with no problem
when the screensaver starts I get authorization failed, i.e. I have to hard reset the machine!!!
On Sat, Jun 29, 2013 at 04:52:16PM +0200, antonio wrote:
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:39:
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:17:
Today I issues a fedup-cli network 19 command (
At the end of procedure that ended right when rebooting I get
Bad news:
I get a black window if I login as any user with a fedora logo on the bottom of screen but I can use tty and then issue a startx
Good news after issuing startx my old video card (Geforce FX5200) works fine with Gnome 3.
Why do I have only F18 kernel??
Tnx
more info:
I have two users, when I issue startx with user A (that is coming from F18) I get the message oh no something went wrong, while a fresh user B can issue startx flawlessy.
Also root can startx with no problem
when the screensaver starts I get authorization failed, i.e. I have to hard reset the machine!!!
Antonio:
Right up front I'll say I have no idea about the various problems you report (apparently) from having used fedup.
However, this last one, you almost certainly DO NOT need to reset the machine. If I read you right, it's stuck in the screensaver, you can't authenticate to get back to your login.
If that's right, you can do one of at least a couple different things: 1. try CTRL-ALT-BKSP, which should kill your X session and return it to a login. Note that this only happens if that response to CTRL-ALT-BKSP hasn't been disabled by default. 2. switch to another VT, log in, kill the X session that's stuck. 3. probably a dozen other choices that don't come to mind right now.
In my F19 system, CTRL-ALT-BKSP seems to be disabled by default. you can enable it in the gnome tweak tool. click "typing" and in the resulting list select "Key sequence to kill the X server", set it to "Control + Alt + Backspace. then the next time you have this kind of fail, just do the 3-finger-salute and voila.
Fred
Fred Smith ha scritto / said the following il giorno/on 29/06/2013 17:59:
On Sat, Jun 29, 2013 at 04:52:16PM +0200, antonio wrote:
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:39:
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:17:
Today I issues a fedup-cli network 19 command (
At the end of procedure that ended right when rebooting I get
Bad news:
I get a black window if I login as any user with a fedora logo on the bottom of screen but I can use tty and then issue a startx
Good news after issuing startx my old video card (Geforce FX5200) works fine with Gnome 3.
Why do I have only F18 kernel??
Tnx
more info:
I have two users, when I issue startx with user A (that is coming from F18) I get the message oh no something went wrong, while a fresh user B can issue startx flawlessy.
Also root can startx with no problem
when the screensaver starts I get authorization failed, i.e. I have to hard reset the machine!!!
Antonio:
Right up front I'll say I have no idea about the various problems you report (apparently) from having used fedup.
However, this last one, you almost certainly DO NOT need to reset the machine. If I read you right, it's stuck in the screensaver, you can't authenticate to get back to your login.
If that's right, you can do one of at least a couple different things:
- try CTRL-ALT-BKSP, which should kill your X session and return it to a login. Note that this only happens if that response to CTRL-ALT-BKSP hasn't been disabled by default.
- switch to another VT, log in, kill the X session that's stuck.
- probably a dozen other choices that don't come to mind right now.
In my F19 system, CTRL-ALT-BKSP seems to be disabled by default. you can enable it in the gnome tweak tool. click "typing" and in the resulting list select "Key sequence to kill the X server", set it to "Control + Alt + Backspace. then the next time you have this kind of fail, just do the 3-finger-salute and voila.
Fred
tnx for the reply.
I have decided to reinstall F18 from the net. The machine is connected to the home printer and scanner so it cannot stay out-of-service for a long time.
I have the doubt that at this stage of release, my fedup-cli 19 network command may have got the wrong packages, (for example no F19 kernel, that is quite surprising)
antonio montagnani wrote:
Fred Smith ha scritto / said the following il giorno/on 29/06/2013 17:59:
On Sat, Jun 29, 2013 at 04:52:16PM +0200, antonio wrote:
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:39:
antonio montagnani ha scritto / said the following il giorno/on 29/06/2013 15:17:
Today I issues a fedup-cli network 19 command (
At the end of procedure that ended right when rebooting I get
Bad news:
I get a black window if I login as any user with a fedora logo on the bottom of screen but I can use tty and then issue a startx
Good news after issuing startx my old video card (Geforce FX5200) works fine with Gnome 3.
Why do I have only F18 kernel??
Tnx
more info:
I have two users, when I issue startx with user A (that is coming from F18) I get the message oh no something went wrong, while a fresh user B can issue startx flawlessy.
Also root can startx with no problem
when the screensaver starts I get authorization failed, i.e. I have to hard reset the machine!!!
Antonio:
Right up front I'll say I have no idea about the various problems you report (apparently) from having used fedup.
However, this last one, you almost certainly DO NOT need to reset the machine. If I read you right, it's stuck in the screensaver, you can't authenticate to get back to your login.
If that's right, you can do one of at least a couple different things:
- try CTRL-ALT-BKSP, which should kill your X session and return it to a login. Note that this only happens if that response to CTRL-ALT-BKSP hasn't been disabled by default.
- switch to another VT, log in, kill the X session that's stuck.
- probably a dozen other choices that don't come to mind right now.
In my F19 system, CTRL-ALT-BKSP seems to be disabled by default. you can enable it in the gnome tweak tool. click "typing" and in the resulting list select "Key sequence to kill the X server", set it to "Control + Alt + Backspace. then the next time you have this kind of fail, just do the 3-finger-salute and voila.
Fred
tnx for the reply.
I have decided to reinstall F18 from the net. The machine is connected to the home printer and scanner so it cannot stay out-of-service for a long time.
I have the doubt that at this stage of release, my fedup-cli 19 network command may have got the wrong packages, (for example no F19 kernel, that is quite surprising)
Doesn't surprise me, I have yet to see it work on a machine more complex than a barebones with one drive and using LVM. Someone posted a better(?) way, using you to do the updates by revectoring the default revision. I'll see if I can find that quickly Monday.
On 06/30/13 00:19, antonio montagnani wrote:
I have the doubt that at this stage of release, my fedup-cli 19 network command may have got the wrong packages, (for example no F19 kernel, that is quite surprising)
FWIW, I tested just now and had a similar experience....
1. X not starting... But this was a simple matter since this is a VBox VM. Just needed to boot to level 3 and reinstall the VBox addons
2. No F19 kernel. This was easy to fix by "yum distro-sync". (Had to erase firefox first....)
3. Still some minor issues with grub.... But no show stoppers.
Ed
On 30.06.2013 03:38, Ed Greshko wrote: …
- X not starting... But this was a simple matter since this is a VBox VM. Just needed to boot to level 3 and reinstall the VBox addons
x86_64? i686 -> https://bugzilla.redhat.com/attachment.cgi?id=758301 rhbz#972095
- No F19 kernel. This was easy to fix by "yum distro-sync". (Had to erase firefox first....)
'fedup-cli --network' - no problems whatsoever
- Still some minor issues with grub.... But no show stoppers.
'extlinux' - no problems whatsoever
poma
On 06/30/13 19:28, poma wrote:
On 30.06.2013 03:38, Ed Greshko wrote: …
- X not starting... But this was a simple matter since this is a VBox VM. Just needed to boot to level 3 and reinstall the VBox addons
x86_64? i686 -> https://bugzilla.redhat.com/attachment.cgi?id=758301 rhbz#972095
x86_64. No big deal. This isn't the first time this has happened with VBox VM's
- No F19 kernel. This was easy to fix by "yum distro-sync". (Had to erase firefox first....)
'fedup-cli --network' - no problems whatsoever
It has been pointed out to me that I hit a known issue. "It's simply that since F19 has been frozen for so long, F18 has a newer kernel in stable. The latest F19 kernels are still only in updates-testing. When the 0-day updates push happens, this will be resolved"
- Still some minor issues with grub.... But no show stoppers.
'extlinux' - no problems whatsoever
I hit https://bugzilla.redhat.com/show_bug.cgi?id=975800 . But that was easy to overcome.
FWIW, no need to place me on the Cc: list to mails to the list. It actually makes things a bit more cumbersome as with TBird I have to hit "Reply All" to get Fedora in addresses and go back and delete you from the To.
On 30.06.2013 14:19, Ed Greshko wrote:
On 06/30/13 19:28, poma wrote:
On 30.06.2013 03:38, Ed Greshko wrote: …
- X not starting... But this was a simple matter since this is a VBox VM. Just needed to boot to level 3 and reinstall the VBox addons
x86_64? i686 -> https://bugzilla.redhat.com/attachment.cgi?id=758301 rhbz#972095
x86_64. No big deal. This isn't the first time this has happened with VBox VM's
True, it isn't the first time the guest additions needs patch&compile, although this one towards xorg-x11-server per se.
- No F19 kernel. This was easy to fix by "yum distro-sync". (Had to erase firefox first....)
'fedup-cli --network' - no problems whatsoever
It has been pointed out to me that I hit a known issue. "It's simply that since F19 has been frozen for so long, F18 has a newer kernel in stable. The latest F19 kernels are still only in updates-testing. When the 0-day updates push happens, this will be resolved"
Kernel downgrade mechanism during upgrade should cover this, although it sounds contradictory. :)
- Still some minor issues with grub.... But no show stoppers.
'extlinux' - no problems whatsoever
I hit https://bugzilla.redhat.com/show_bug.cgi?id=975800 . But that was easy to overcome.
Grub2 unnecessarily complicates the whole thing, and not the only one.
FWIW, no need to place me on the Cc: list to mails to the list. It actually makes things a bit more cumbersome as with TBird I have to hit "Reply All" to get Fedora in addresses and go back and delete you from the To.
Just for your perfectionism sake. :)
poma
On Sat, Jun 29, 2013 at 6:38 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
On 06/30/13 00:19, antonio montagnani wrote:
I have the doubt that at this stage of release, my fedup-cli 19 network command may have got the wrong packages, (for example no F19 kernel, that is quite surprising)
FWIW, I tested just now and had a similar experience....
X not starting... But this was a simple matter since this is a VBox VM. Just needed to boot to level 3 and reinstall the VBox addons
No F19 kernel. This was easy to fix by "yum distro-sync". (Had to erase firefox first....)
Still some minor issues with grub.... But no show stoppers.
Ed
For what it's worth, you could fix the entire situation by installing the i386 version; I switched to x86 in F18 and am having the same issues as a Ed describes, and was going to pipe up, typing that I had never had these problems before, that the Linux was a "rock", forgetting about my i386=>x86 change-over, until suddenly remembering.
Hope this helps,
Richard
-
Antonio M -
antonio montagnani -
Bill Davidsen -
Ed Greshko -
Fred Smith -
poma -
Richard Vickery