I did the update from CR, and have some pretty serious issues. Until I blew away (by mv to a different name) the .local and .config directory trees, I couldn't log in to GNOME at all. After doing that, I can log in, but if I do any actual work, GNOME crashes, and abrt-cli from root in vc 2 tells me that gnome-shell got a SIGSEGV. I figure all of the updates aren't in CR yet, so I'm going to pull out my backup machine and work with it until I see if CR gets more updates. Good thing I've got vacation scheduled for next week!I did quite a few other things in trying to troubleshoot, including attempting a yum distro-sync without CR enabled, which had helped me rollback once before, but not this time. Once I get my backup machine set up I can post better details.
On 11/18/18 6:30 AM, Lamar Owen wrote:
I did the update from CR, and have some pretty serious issues. Until I blew away (by mv to a different name) the .local and .config directory trees, I couldn't log in to GNOME at all. After doing that, I can log in, but if I do any actual work, GNOME crashes, and abrt-cli from root in vc 2 tells me that gnome-shell got a SIGSEGV. I figure all of the updates aren't in CR yet, so I'm going to pull out my backup machine and work with it until I see if CR gets more updates. Good thing I've got vacation scheduled for next week!I did quite a few other things in trying to troubleshoot, including attempting a yum distro-sync without CR enabled, which had helped me rollback once before, but not this time. Once I get my backup machine set up I can post better details.
Sorry to hear that. I've updated one workstation (Intel Skylake) to the latest packages in CR, and everything works well and smoothly. I like the new GNOME. Maybe it's something special to your machines that triggered those issues.
Le 18/11/2018 à 15:30, Lamar Owen a écrit :
I did the update from CR, and have some pretty serious issues. Until I blew away (by mv to a different name) the .local and .config directory trees, I couldn't log in to GNOME at all. After doing that, I can log in, but if I do any actual work, GNOME crashes, and abrt-cli from root in vc 2 tells me that gnome-shell got a SIGSEGV. I figure all of the updates aren't in CR yet, so I'm going to pull out my backup machine and work with it until I see if CR gets more updates.
Since Red Hat decided to roll in some major GNOME updates between minor releases, I'm seriously beginning to wonder if I won't be better off using Fedora on desktops. That's a real question, not a rhetorical one, BTW. I'm currently experimenting with Fedora 29 and a minimal KDE, and the result is quite nice.
https://github.com/kikinovak/fedora-desktop-kde
On servers I'll always use CentOS though.
:o)
On 11/18/2018 09:01 AM, Nicolas Kovacs wrote:
Le 18/11/2018 à 15:30, Lamar Owen a écrit :
I did the update from CR, and have some pretty serious issues. Until I blew away (by mv to a different name) the .local and .config directory trees, I couldn't log in to GNOME at all. After doing that, I can log in, but if I do any actual work, GNOME crashes, and abrt-cli from root in vc 2 tells me that gnome-shell got a SIGSEGV. I figure all of the updates aren't in CR yet, so I'm going to pull out my backup machine and work with it until I see if CR gets more updates.
Since Red Hat decided to roll in some major GNOME updates between minor releases, I'm seriously beginning to wonder if I won't be better off using Fedora on desktops. That's a real question, not a rhetorical one, BTW. I'm currently experimenting with Fedora 29 and a minimal KDE, and the result is quite nice.
https://github.com/kikinovak/fedora-desktop-kde
On servers I'll always use CentOS though.
:o)
I'm actually surprised with the jump in gnome versions between minor point releases. I guess they trying to strike a different balance for the GUI / Desktop and Server services. I actually do appreciate it for my desktops. GNOME3 is the default (and likely the most tested) desktop.
There are new gnome-session and gdm updates that I am getting ready to push to CR .. gnome-session-3.28.1-6.el7.src.rpm and gdm-3.28.2-10.el7.src.rpm .. no idea what the actually do yet, but you can see if they fix any of your issues by looking at the upstream errata, etc.
On 11/20/18 8:48 AM, Johnny Hughes wrote:
On 11/18/2018 09:01 AM, Nicolas Kovacs wrote:
Le 18/11/2018 à 15:30, Lamar Owen a écrit :
I did the update from CR, and have some pretty serious issues. ...
Since Red Hat decided to roll in some major GNOME updates between minor releases, I'm seriously beginning to wonder if I won't be better off using Fedora on desktops.
... There are new gnome-session and gdm updates that I am getting ready to push to CR .. gnome-session-3.28.1-6.el7.src.rpm and gdm-3.28.2-10.el7.src.rpm .. no idea what the actually do yet, but you can see if they fix any of your issues by looking at the upstream errata, etc.
Well, reporting back, and I'm not 100% sure what caused my problem. I have used several repos since I installed the box two years ago, and there was quite a bit of clutter. I'm leaning towards my use of xscreensaver (I like the 'flurry' screensaver) as the likely culprit, but I had enough clutter that it's not really practical (not to mention that I really can't take the time) to fully troubleshoot and be close to 100% sure.
Since I did have some clutter to deal with, and the drives (250GB mSATA SSD and 1TB HGST 7K1000) are two years old at this point, I decided it was time to refresh my installation. So I got a good deal on a Samsung 860 EVO 500GB mSATA and another HGST 7K1000 (one of the best 2.5 inch drives out there), and waited until they came in to do a complete reinstall, and am rsyncing files over from the older 1TB drive as needed. The Dell Precision M6700 laptop has two 2.5 inch bays plus the mSATA slot, so I downloaded the 1804 DVD iso (mirrors must be syncing; the download took way longer than it should have!), installed to the 860 SSD with the 1TB as /home (leaving the old 1TB /home alone), and successfully updated with CR afterwards. The install of the ELrepo nvidia driver went smoothly, and after some install work and rsync work I'm back operational; a USB 3.0 enclosure for the older mSATA boot drive made it much easier.
I spent more time trying to troubleshoot GNOME3's startup than it took to install and update!
In a related vein, does anyone have a pointer to a good solid GNOME3 startup document that gives enough detail to where someone can actually troubleshoot without having to patch and rebuild gjs and stack trace javascript? Just a simple startup log woul be nice, instead of the SIGSEGV in /var/log/messages..... (side note: I really hate how the Android GMail messes up threading; the Samsung email app is better, but it can't properly display a lot of the messages in the CentOS list (such as Johnny's) and GMail can)
Le 20/11/2018 à 14:48, Johnny Hughes a écrit :
I'm actually surprised with the jump in gnome versions between minor point releases. I guess they trying to strike a different balance for the GUI / Desktop and Server services. I actually do appreciate it for my desktops. GNOME3 is the default (and likely the most tested) desktop.
On a side note. One component I do wish Red Hat would upgrade regularly between point releases is the HPLIP printer driver. The version shipped with RHEL/CentOS is fairly obsolete and also buggy (hp-plugin hasn't been working for ages). Which means pretty much every new HP printer I buy nowadays is unsupported.
There is always the possibility of installing HPLIP from upstream, which I documented here for example :
* https://blog.microlinux.fr/hp-pagewide-pro-centos/
But this method also has its shortcomings. And is one of the many reasons why I'm considering the move to Fedora on the desktop (which is more or less a rolling distribution with releases in between).
Cheers,
Niki
-
Johnny Hughes -
Lamar Owen -
Nicolas Kovacs -
Yan Li