Red Hat Bugzilla – Bug 1019501
anaconda lock-up for some time when opening/closing modal dialogs
Last modified: 2013-10-23 11:41:55 EDT
Description of problem:
I was testing F20 BETA TC4 LIVE XFCE image on real hardware, and when I start installer everything is ok until modal dialog pop-up (for example "Unstable /pre-release "Accept my fate", or dialogs related to partitioning), it freezes GUI, and takes from few seconds to few minutes to show up, same when you click on something in that dialog (buttons tested). I tried to take a picture of it with a program which comes on xfce spin image, but it also messes up by switching between windows ... (anaconda <--> screenshot application)
While it is unresponsive, top processes are: X, xfwm4 and anaconda
Version-Release number of selected component (if applicable):
anaconda-20.25-1.fc20 (copied from rel-eng ticket for f20 (and TC3/TC4 comment)
Steps to Reproduce:
1. start XFCE live image
2. run anaconda
3. run until first modal dialog show up
I tested this multiple times, same happens every time, now I think when this happens "double click" _unlock_ the dialog and also double click on "buttons" work.
I installed xfce live, and everything is ok, anaconda doesn't crash.
I am seeing this too here on bare hardware. Not on virtual installs however. :(
It's quite odd.
Is the CD drive spinning up during this lockup? It might be loading the rest of the installer from the disk.
No, I was using USB flash drive, also I tested TC3 but different desktop (which should be identical to TC4, when it comes to live images, I think only dvd wasn't composed), I used Gnome (Desktop) live image, and it worked there fine.
Tested TC5 now (xfce), same problem.
Downloading LXDE to test if it happens on other desktops.
Ok, one more update (sorry for spam emails!)
Same problem on LXDE live! :(
Please attach the logs from /tmp/*log as individual text/plain attachments to this bug.
Created attachment 813498 [details]
Created attachment 813499 [details]
Created attachment 813500 [details]
Created attachment 813501 [details]
packaging and sensitive-info log files are empty (this was just live mode, no install)
Just to add that TC5 KDE LIVE works fine :S
So I can see this on LXDE, XFCE for now (gnome and kde are fine). Not sure if this information helps?
TC5 Live version of XFCE spin CD is better but still could not go all the way through the installation.
Very probably the same cause as in bug 1021511. Mine is better described, however :-)
Maybe it is, but I cannot reproduce this on same hw. in other Desktop environments, like KDE, GNOME or MATE. Also how to explain "double click" solution/workaround?
I've seen the need to double click some buttons in XFCE as well. I guess that it might be caused by the very slow widget performance when lightboxes are displayed, so that some mouse click are simply not registered (or maybe the window is displayed, but the buttons are not sensitive yet, or something).
It's true that this might not be related to bug 1021511 and there is another root issue for this. But I remember seeing this issue usually coupled with lightboxes, so my feeling is that it's related, simply a performance issue.
*** Bug 1021511 has been marked as a duplicate of this bug. ***
Did you try to do anything outside of anaconda in xfce? It's kind of ridiculously unresponsive just in general.
David Shea, I don't understand how this is now xfce4-session bug, I didn't saw any issues with xfce without anaconda running, also this bug is present in lxde live spin which doesn't have xfce4 components?
I sure didn't see that here on virtual installs or bare metal. All non anaconda gui processes were fine and fast here.
This also happens in LXDE and other desktops, so I really fail to see how this could be an xfce4-session bug.
I saw this bug in mate live CD as well.
If anybody doesn't mind, I would dupe this to bug 1021511. I'm fairly sure it is the same problem. Bug 1021511 contains videos, lists problems in most of available desktop environments and is already accepted as a freeze exception.
kamil, You should go ahead. Both the bugs are the same IMHO. Bug 1021511 definitely has more info.
*** This bug has been marked as a duplicate of bug 1021511 ***