top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Upgrading to 19 by fedup: bad and good news

0 votes

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

posted Jun 29, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
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

1 Answer

0 votes

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.

answer Jun 29, 2013 by anonymous
Similar Questions
+2 votes

I have upgraded a pc from fedora 18 to 19, and I am left with an ugly grub2 boot loader. So, I have removed packages grub2, grub2-tools, erased /etc/default/grub, re-installed them, and run:

grub2-install /dev/sda grub2-mkconfig -o /boot/grub2/grub.cfg

But grub still has no theme. Package grub2-starfield-theme is installed though. When I reinstalled grub2-tools, no /etc/default/grub was created. Is there a reason for that?

+1 vote

Booted machine from livecd image, and the gnome3 worked.

Used Fedup to upgrade an Fedora 18 setup to Fedor 19, and gnome3 doesn't work (Opps screen), but KDE and Xfce does.

Did a clean install from the DVD image of Fedora 19 to a new hard disk, and gnome3 doesn't work, kde regular doesn't work, kde failsafe works, and xfce works.

The machine has a nvidia geforce FX 5200 card, which I know is old, but that is what my classroom has in all 20 machines. So, not just a matter of getting a different card. Long ago was using the nvidia driver from there site, but they dropped support for the older cards, so had to switch to the nouvea driver.

Any suggestions, or just have to stick with xfce..

+1 vote

How can I add an application launcher to the favorites menu in Fedora 19?

+1 vote

I have just installed virt-manager in Fedora 19. I have looked into the /etc/init.d directory but I can't find any init scripts for libvirt.

Is libvirt using systemd, and if so, how do I start it?

0 votes

I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs:

 # systemctl start transmission-daemon.service

If I let it be for a few minutes (~5), it finishes with a failure. The log is extremely unhelpful. This is very strange because it was working just fine until a few days ago.