Greetings,
Recently, I "fresh installed" F21 on a Dell i686 Inspiron Laptop.
I had been running F18 on it, and just wanted to jump to the newest release w/o stepping through F19 and F20. I kept the /home partition, and wiped everything else out.
Xfce and Mate Desktops start and are very functional.
Any variant of Gnome (new version and Classic) reports an equivalent screen-of-death with the message reading "A problem has occurred, and the system can't recover."
The /var/log/messages file is very extensive; it begins with: Mar 18 19:06:49 MercToo systemd-logind: New session 14 of user pyz. Mar 18 19:06:50 MercToo org.a11y.Bus: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 18 19:06:50 MercToo org.a11y.atspi.Registry: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 18 19:06:50 MercToo gdm: Child process 1024 was already dead. Mar 18 19:06:50 MercToo gdm: Unable to kill session worker process Mar 18 19:06:50 MercToo org.gtk.vfs.Daemon: A connection to the bus can't be made Mar 18 19:06:50 MercToo org.gtk.vfs.Daemon: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 18 19:06:50 MercToo ca.desrt.dconf: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 18 19:06:50 MercToo gnome-session: ** (gnome-settings-daemon:1136): WARNING **: Name taken or bus went away - shutting down
...
and goes on like that.
I've done various "yum groupinstalls" hoping to get all of the various missing dependencies and missing libraries. Obviously, I'm missing something.
I noticed that someone (on a similar Gnome problem) said to check for a list of services using systemctl to see if they are enabled; I did that, and everything seems to be correctly enabled.
Is this problem resolvable on an i686 system? I'd like to resolve this first, before upgrading my x86_64-based machines.
I have no loyalties to Gnome; I'd just like to function close to their intended design. And take it as a sign of possible other problems in the even that they don't.
Max Pyziur pyz@brama.com
On Wed, Mar 18, 2015 at 5:17 PM, Max Pyziur pyz@brama.com wrote:
Recently, I "fresh installed" F21 on a Dell i686 Inspiron Laptop.
I had been running F18 on it, and just wanted to jump to the newest release w/o stepping through F19 and F20. I kept the /home partition, and wiped everything else out.
Xfce and Mate Desktops start and are very functional.
Any variant of Gnome (new version and Classic) reports an equivalent screen-of-death with the message reading "A problem has occurred, and the system can't recover."
I have a Dell Latitude D600 circa ~2002, also i686. It's just a dog with Gnome Shell. I don't depend on this for production use, so I'm just running Fedora Server on it mainly and to test i686 stuff for QA. Xfce is much more realistic to use.
What happens if you boot with boot parameter nomodeset? Another possibility is to add boot parameter 3, to boot in runlevel 3/multi-user.target/no graphical boot. Then do a yum upgrade right away. There's a much newer kernel, and hence video drivers, now than when Fedora 21 shipped as well as a lot of gnome updates that could be related. After the upgrade, reboot normally and see if the problem is solved.
The /var/log/messages file is very extensive;
Fedora 21 Workstation doesn't come with rsyslogd, so there shoudn't be a /var/log/messages. Fedora 21 Server does.
On Wed, 18 Mar 2015, Chris Murphy wrote:
On Wed, Mar 18, 2015 at 5:17 PM, Max Pyziur pyz@brama.com wrote:
Recently, I "fresh installed" F21 on a Dell i686 Inspiron Laptop.
I had been running F18 on it, and just wanted to jump to the newest release w/o stepping through F19 and F20. I kept the /home partition, and wiped everything else out.
Xfce and Mate Desktops start and are very functional.
Any variant of Gnome (new version and Classic) reports an equivalent screen-of-death with the message reading "A problem has occurred, and the system can't recover."
I have a Dell Latitude D600 circa ~2002, also i686. It's just a dog with Gnome Shell. I don't depend on this for production use, so I'm just running Fedora Server on it mainly and to test i686 stuff for QA. Xfce is much more realistic to use.
What happens if you boot with boot parameter nomodeset? Another possibility is to add boot parameter 3, to boot in runlevel 3/multi-user.target/no graphical boot. Then do a yum upgrade right away. There's a much newer kernel, and hence video drivers, now than when Fedora 21 shipped as well as a lot of gnome updates that could be related. After the upgrade, reboot normally and see if the problem is solved.
I installed F21 a month ago, and I've kept up with the updates. So whatever kernel that's in use is the latest one.
My attention to this is periodic; but I would like to resolve it so that I know that I can install F21 w/ no worries on my two x68_64s, machines on which I'm reliant.
I'll try the command line changes that you suggest.
The /var/log/messages file is very extensive;
Fedora 21 Workstation doesn't come with rsyslogd, so there shoudn't be a /var/log/messages. Fedora 21 Server does.
When I first Installed F21, I just defaulted to whatever was offered on the Workstation DVD, making sure that I kept my /home partition.
After that, I did several "groupinstalls" in part hoping to remedy this Gnome problem, and also wanting to have Xfce and Mate.
So, in one of those "groupinstalls" I could have also gotten rsyslogd installed and running (I can't imagine not having it.).
Max Pyziur pyz@brama.com
-
Chris Murphy -
Max Pyziur