Bug 768471

(In reply to comment #0)
> Description of problem: after performing upgrade on fc14,

What method did you use exactly? Upgrade from DVD? preupgrade? yum upgrade?
Did anything suspicious happen during the upgrade?

Do these commands produce anything interesting?:
package-cleanup --problems
package-cleanup --dupes
package-cleanup --orphans

> I was able to alt-ctrl-f2 to login.

Does "systemctl list-jobs" show any pending jobs?
Does "systemctl --failed" show any failed services?

> The fedora project knows about the problem and issued a fix:
> ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target

The command is sensible, though I don't think it applies to the problem you're having.

(In reply to comment #1)
> (In reply to comment #0)
> > Description of problem: after performing upgrade on fc14,
> 
> What method did you use exactly? Upgrade from DVD? preupgrade? yum upgrade?
> Did anything suspicious happen during the upgrade?
> 
> Do these commands produce anything interesting?:
> package-cleanup --problems
> package-cleanup --dupes
> package-cleanup --orphans
> 
> > I was able to alt-ctrl-f2 to login.
> 
> Does "systemctl list-jobs" show any pending jobs?
> Does "systemctl --failed" show any failed services?
> 
> > The fedora project knows about the problem and issued a fix:
> > ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
> 
> The command is sensible, though I don't think it applies to the problem you're
> having.

(In reply to comment #0)
> Description of problem: after performing upgrade on fc14, I ran reboot and the
> logo got filled and the screen cleared and the background was shown. Then
> nothing no login screen. I was able to alt-ctrl-f2 to login. I issued shutdown
> now and rebooted from the fallback of fc14 which was fine and at login it shows
> fc15.
> The fedora project knows about the problem and issued a fix:
> ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
> ln -sf graphical.target /lib/systemd/system/default.target
> 
> I entered this and rebooted. Same thing.
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible: at every boot
> 
> 
> Steps to Reproduce:
> 1. shut down
> 2. boot
> 
> Actual results: fedoara loga gets filled and screen display blue striped
> background. and no login 
> 
> 
> Expected results: able to login
> 
> 
> Additional info: none

(In reply to comment #1)
> (In reply to comment #0)
> > Description of problem: after performing upgrade on fc14,
> 
> What method did you use exactly? Upgrade from DVD? preupgrade? yum upgrade?
> Did anything suspicious happen during the upgrade?
> 
> Do these commands produce anything interesting?:
> package-cleanup --problems
> package-cleanup --dupes
> package-cleanup --orphans
> 
> > I was able to alt-ctrl-f2 to login.
> 
> Does "systemctl list-jobs" show any pending jobs?
> Does "systemctl --failed" show any failed services?
> 
> > The fedora project knows about the problem and issued a fix:
> > ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target
> 
> The command is sensible, though I don't think it applies to the problem you're
> having.

I used preupgrage.
I got zero units from list-jobs same with --failed

sorry about the last comment. I tried again and used ctrl alt f2 and logged in. I entered systemctl list-units and it listed many units. I am giving the ones with errors:
distchache.service
livsys-late.service
openct.service
cgconfig-target.service

the rest had no errors.

on jan 24, and not hearing anything from you I rebooted and got the same screen but when pressing "enter" there was a sound like a key being hit. I entered my password (without the prompt just typing and seeing nothing) and the screen cleared and it displayed the background (nova) that I use on fc14. Nothing else happen. I did a ctl-alt-f2 and was asked enter my username and password. 
after login I listed the units a there were many and no errors. I entered startx but it did not work. Any suggestions would be helpful. Anything would be nice. Just hearing from you would be nice.

From the described symptoms, it does not look like a problem in systemd.
More likely there's something wrong with X server, graphics driver, login manager, or window manager.
/var/log/Xorg.0.log could contain some hints.

Nothing in the /var/log/Xorg.0.log or /var/log/messages which explains why you cant login? 

You will have to attach them here so we can look at it and see if this issue is related to systemd or not 

Thanks.

Created attachment 557944 [details]
/var/log/messages

Created attachment 557945 [details]
/var/log/Xorg.0.log

Created attachment 557946 [details]
datat from command systemctl list-units

I need you to boot with 'log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg' then save the output of the dmesg command and attach it here to completely rule out systemd.

Then I would like to you to make a livecd/usb of F15/F16 and boot it to rule out potentially bad upgrade. 

Thanks

Created attachment 558662 [details]
/bin/systemd --test --system --log-level=debug

Created attachment 558663 [details]
output from demsg

(In reply to comment #10)
> I need you to boot with 'log_buf_len=1M systemd.log_level=debug
> systemd.log_target=kmsg' then save the output of the dmesg command and attach
> it here to completely rule out systemd.
> 
> Then I would like to you to make a livecd/usb of F15/F16 and boot it to rule
> out potentially bad upgrade. 
> 
> Thanks

did as requested: see output, also made livecd/usb and booted with a result of the screen just sitting there with nothing happening. I did not know what to expect. I did a ctrl-alt-f2 which gave me a login prompt. but could not login because of invalid username/password so I powered down. I then tried again, this time the boot started by filling the logo and when it was 1/3 full the boot started again after much flashing of the screen it came up with firefox browser with a error message that I had 2 fedoras running. The browser worked fine and that was all I was able to use. I powered down and restarted. This time it just sat there with the blue screen and bird at the bottom. My question is what was supposed to happen and how long does take to go from blue screen to whatever.

Pretty sure this is not systemd most likely graphic/kernel regression ( Gnome shell is not capable of running on top of your graphic stac hence the crappy bird or oops screen something went wrong yatata )

Try booting with i915.i915_enable_fbc=0  and or i915.powersave=0 

Also try this kernel http://koji.fedoraproject.org/koji/buildinfo?buildID=251810 and see if it works for you


Thanks

(In reply to comment #12)
> Created attachment 558663 [details]

You made a typo ("lod_target") so we only see the debug logs from early services before rsyslog starts.

(In reply to comment #13)
> did as requested: see output, also made livecd/usb

So which one? Did you burn a CD, or used liveusb-creator to create a bootable USB disk/flash, or ...?

> and booted with a result of
> the screen just sitting there with nothing happening. I did not know what to
> expect. I did a ctrl-alt-f2 which gave me a login prompt. but could not login
> because of invalid username/password so I powered down.

On the live system, login should be possible as root with an empty password.

> I then tried again,
> this time the boot started by filling the logo and when it was 1/3 full the
> boot started again

Did it spontaneously reset all the way to the BIOS bootup?

> after much flashing of the screen it came up with firefox
> browser

I may be mistaken, but I don't recall the live images being configured to autostart Firefox. What ISO image did you use exactly (what's the filename)?

> with a error message that I had 2 fedoras running.

Are you sure that the error message said "2 fedoras"? That is some weird message.

> My question is what was supposed to happen and how long does take to go
> from blue screen to whatever.

Depending on which live image you have, a usable desktop environment is supposed to appear in about a minute.

It's enough for him to just the kernel I mentioned in comment 14.

If that works for him he's hitting an known kernel/driver regression which affects all 2.6.4x kernels on F15 and all 3.x kernels on F16 and we can close this bug...

(In reply to comment #16)
> It's enough for him to just the kernel I mentioned in comment 14.

Mean

It's enough for him to just install and test the kernel I mentioned in comment 14.

(In reply to comment #15)
> (In reply to comment #12)
> > Created attachment 558663 [details]
> 
> You made a typo ("lod_target") so we only see the debug logs from early
> services before rsyslog starts.
> 
> (In reply to comment #13)
> > did as requested: see output, also made livecd/usb
> 
> So which one? Did you burn a CD, or used liveusb-creator to create a bootable
> USB disk/flash, or ...?
> 
> > and booted with a result of
> > the screen just sitting there with nothing happening. I did not know what to
> > expect. I did a ctrl-alt-f2 which gave me a login prompt. but could not login
> > because of invalid username/password so I powered down.
> 
> On the live system, login should be possible as root with an empty password.
> 
> > I then tried again,
> > this time the boot started by filling the logo and when it was 1/3 full the
> > boot started again
> 
> Did it spontaneously reset all the way to the BIOS bootup?
> 
> > after much flashing of the screen it came up with firefox
> > browser
> 
> I may be mistaken, but I don't recall the live images being configured to
> autostart Firefox. What ISO image did you use exactly (what's the filename)?
> 
> > with a error message that I had 2 fedoras running.
> 
> Are you sure that the error message said "2 fedoras"? That is some weird
> message.
> 
> > My question is what was supposed to happen and how long does take to go
> > from blue screen to whatever.
> 
> Depending on which live image you have, a usable desktop environment is
> supposed to appear in about a minute.

I used liveusb-creator on a flash-drive
What is this new kernel will it destroy my only fallback that works. If it is destroyed then I will be screwed. 

Just to be safe I created another fc15 using torrent live source and started the boot. again something happens at about half way thru(the fedora logo going white) it started again with what seems like a new boot. I let it run until the blue screen came up. It just sat there. I powered down. My take is that something (an error) during the boot process is causing it to start on the other boot. There are 2 in the boot script. I'm thinking of removing the x64 script and using what I assume to be a x32 script.

Package-cleanup --problems displayed this
 
Package libpanelappletmm-2.26.0-2.fc12.x86_64 requires libpanel-applet-2.so.0()(64bit)

Created attachment 559118 [details]
output from demsg

(In reply to comment #18)
> What is this new kernel will it destroy my only fallback that works. If it is
> destroyed then I will be screwed. 

You can have multiple kernel packages installed and choose among them at boot time from the GRUB menu.

> Just to be safe I created another fc15 using torrent live source and started
> the boot. again something happens at about half way thru(the fedora logo going
> white) it started again with what seems like a new boot.

That surely looks like a kernel bug or hardware problem.

> ... causing it to start on the other boot. There are 2 in the boot script.
> I'm thinking of removing the x64 script and using what I assume to be a x32
> script.

It's unclear to me what you're talking about here.

> Package-cleanup --problems displayed this
> 
> Package libpanelappletmm-2.26.0-2.fc12.x86_64 requires
> libpanel-applet-2.so.0()(64bit)

I suggest 'yum remove libpanelappletmm' to uninstall the obsolete package. I don't expect it to resolve the main problem though.

(In reply to comment #19)
> output from demsg

This output looks fine from systemd point of view.

> the logo got filled and the screen cleared and the background was shown.
> Then nothing no login screen. 

Do you use kdm, the KDE display manager? You may be seeing bug 741441.

(In reply to comment #22)
> > the logo got filled and the screen cleared and the background was shown.
> > Then nothing no login screen. 
> 
> Do you use kdm, the KDE display manager? You may be seeing bug 741441.

not that I know of. How do I find out?.

Well people usually know if they are using Gnome ( the Default ) or KDE or some other DE.

Did you try the kernel I mentioned in in comment 14?

(In reply to comment #24)
> Well people usually know if they are using Gnome ( the Default ) or KDE or some
> other DE.
> 
> Did you try the kernel I mentioned in in comment 14?

So sorry that I am not that knowledgeable and you did not answer the question.

How does this kernel effect my current system. I can not lose my fall back. (In reply to comment #15)
> (In reply to comment #12)
> > Created attachment 558663 [details]
> 
> You made a typo ("lod_target") so we only see the debug logs from early
> services before rsyslog starts.
> 
> (In reply to comment #13)
> > did as requested: see output, also made livecd/usb
> 
> So which one? Did you burn a CD, or used liveusb-creator to create a bootable
> USB disk/flash, or ...?
> 
> > and booted with a result of
> > the screen just sitting there with nothing happening. I did not know what to
> > expect. I did a ctrl-alt-f2 which gave me a login prompt. but could not login
> > because of invalid username/password so I powered down.
> 
> On the live system, login should be possible as root with an empty password.
> 
> > I then tried again,
> > this time the boot started by filling the logo and when it was 1/3 full the
> > boot started again
> 
> Did it spontaneously reset all the way to the BIOS bootup?
> 
> > after much flashing of the screen it came up with firefox
> > browser
> 
> I may be mistaken, but I don't recall the live images being configured to
> autostart Firefox. What ISO image did you use exactly (what's the filename)?
> 
> > with a error message that I had 2 fedoras running.
> 
> Are you sure that the error message said "2 fedoras"? That is some weird
> message.
> 
> > My question is what was supposed to happen and how long does take to go
> > from blue screen to whatever.
> 
> Depending on which live image you have, a usable desktop environment is
> supposed to appear in about a minute.

I started looking at formatting the stick. That failed. I tried fdisk(??) the program to remove partions. I still found some stuff on the stick will try to have a squeaky clean device and then run liveusb-creator, As you have probably noticed, I am not heavy into systems analysis. But will keep trying.

(In reply to comment #25)
> (In reply to comment #24)
> > Well people usually know if they are using Gnome ( the Default ) or KDE or some
> > other DE.
> > 
> > Did you try the kernel I mentioned in in comment 14?
> 
> So sorry that I am not that knowledgeable and you did not answer the question.

What question ? 

Could you please download the previous mentioned kernel in comment 14 install it and boot into it to see if your problem is fixed so we can confirm that this is indeed an kernel regression.

Thanks

(In reply to comment #14)
> Pretty sure this is not systemd most likely graphic/kernel regression ( Gnome
> shell is not capable of running on top of your graphic stac hence the crappy
> bird or oops screen something went wrong yatata )
> 
> Try booting with i915.i915_enable_fbc=0  and or i915.powersave=0 
> 
> Also try this kernel
> http://koji.fedoraproject.org/koji/buildinfo?buildID=251810 and see if it works
> for you
> 
> 
> Thanks

Yes it could be graphic/kernel regression, the screen on the liveusb does not go smoothly, it flashes a bright white square about 1/6 the screen before going to the crappy bird. The graphics definitely have problems.

(In reply to comment #14)
> Pretty sure this is not systemd most likely graphic/kernel regression ( Gnome
> shell is not capable of running on top of your graphic stac hence the crappy
> bird or oops screen something went wrong yatata )
> 
> Try booting with i915.i915_enable_fbc=0  and or i915.powersave=0 
> 
> Also try this kernel
> http://koji.fedoraproject.org/koji/buildinfo?buildID=251810 and see if it works
> for you
> 
> 
> Thanks

I booted from the usb and entered i915.i915_enable_fbc=0 and it worked. I then tried it on the hard disk and failed.

(In reply to comment #24)
> Well people usually know if they are using Gnome ( the Default ) or KDE or some
> other DE.
> 
> Did you try the kernel I mentioned in in comment 14?

yes. when I applied i915.915_enable_fbc=0 it worked otherwise it shows same crappy bird. What do we do next.

(In reply to comment #29)
> (In reply to comment #24)
> > Well people usually know if they are using Gnome ( the Default ) or KDE or some
> > other DE.
> > 
> > Did you try the kernel I mentioned in in comment 14?
> 
> yes. when I applied i915.915_enable_fbc=0 it worked otherwise it shows same
> crappy bird. Also when I tried evolution mail client it was a bit haywire. What do we do next.

we are now approaching 3 months without a solution, Three kernels(fc15) have been received thru the update module and none work. Would it be possible to skip over fc15 and do an upgrage to fc16 without the problems with this kernel.

I answered my question. I tried to "test drive" fc16 and I had the same problem. I am back at square one. I wished the kernel had a slick debugging tool like C programming where a program stops at an error point and allows a person to see what exactly is going on.

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping