[opensuse] btrfs rollback gives dead display manager
After a possibly ill-advised sideload upgrade/fix of a perl app, I tried to do a btrfs rollback but I end up with a dead display manager. Going back to the current/last snapshot and display manager works fine. I see nothing in intervening snapshots (or in yast2) that relates to any display manager changes nor anything else in there that would seem to have anything to do with display manager. This is a new (few days) fresh install of Leap 423 with xfce that previously to this event had all updates installed. Display manager is lightdm. Any ideas? Thanks. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 6 Nov 2017 14:04:14 -0600 listreader <suselist@cableone.net> wrote: Quotes reordered for substance
Any ideas? Thanks.
Go to the backup? You do have a backup?
After a possibly ill-advised sideload upgrade/fix of a perl app, I tried to do a btrfs rollback
Normally installing or changing a perl program shouldn't affect the system at all, thanks to the clever way the PERLPATH is searched. Unless you tried to monkey patch a system-installed perl component? (Don't do that, BTW, install a local copy first from CPAN before patching it if still necessary).
Ralph
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 6 Nov 2017 21:22:56 +0000 Dave Howorth <dave@howorth.org.uk> wrote:
Any ideas? Thanks.
Go to the backup? You do have a backup?
No. This is a brand new machine being prepared. Snapshots should be perfectly sufficient for this case. No user data either.
After a possibly ill-advised sideload upgrade/fix of a perl app, I tried to do a btrfs rollback
Normally installing or changing a perl program shouldn't affect the system at all, thanks to the clever way the PERLPATH is searched. Unless you tried to monkey patch a system-installed perl component? (Don't do that, BTW, install a local copy first from CPAN before patching it if still necessary).
No. This *was* from CPAN. Unfortunately the 1st fix to a previously working program doesn't work with the calling program. I can tell from the snapshots which files were created/changed/etc but there are a ton of them and I was trying to avoid picking through and deleting them; just rolling back would be nice and easy. This is what snapshots are supposed to be for, no? So why did I end up with a dead display manager? FWIW, the original 'fix' has been 'fixed' 4 times since last night 8-/ so I think I will just wait until someone in factory catches up to it, they are only 2 of those revs behind at last check, just a few hours. Amazing. I just have/had no patience. Another FWIW, the perl is finance::quote (a.k.a. perl-Finance-Quote in software.opensuse) and the reason for all the activity is that yahoo / verizon has killed without warning their decades old free api that provided financial quotes and that also killed a lot of finance programs that depended on it. So the switch is on to convert to a new free api provider (yes! there is one.) Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Going back to the original to try to start again ... On Mon, 6 Nov 2017 14:04:14 -0600 listreader <suselist@cableone.net> wrote:
After a possibly ill-advised sideload upgrade/fix of a perl app, I tried to do a btrfs rollback but I end up with a dead display manager. Going back to the current/last snapshot and display manager works fine. I see nothing in intervening snapshots (or in yast2) that relates to any display manager changes nor anything else in there that would seem to have anything to do with display manager.
It seems the perl stuff is a red herring? I don't know btrfs well. Is there a difference between a rollback and a snapshot? I'm not clear what it is that doesn't work if 'Going back to the current/last snapshot and display manager works fine'. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 6 Nov 2017 23:25:20 +0000 Dave Howorth <dave@howorth.org.uk> wrote:
I don't know btrfs well. Is there a difference between a rollback and a snapshot? I'm not clear what it is that doesn't work if 'Going back to the current/last snapshot and display manager works fine'.
Sorry, don't mean to ignore your question, just really short on time today. See the wiki link for basic info on btrfs snapshots/rollbacks & etc. https://en.opensuse.org/openSUSE:Snapper_Tutorial -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
You could try looking in /var/log/Xorg.0.log or /var/log/xdm.errors to see if there is a clue. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2017-11-07 at 20:52 -0600, listreader wrote:
On Mon, 6 Nov 2017 23:25:20 +0000 Dave Howorth <> wrote:
I don't know btrfs well. Is there a difference between a rollback and a snapshot? I'm not clear what it is that doesn't work if 'Going back to the current/last snapshot and display manager works fine'.
Sorry, don't mean to ignore your question, just really short on time today. See the wiki link for basic info on btrfs snapshots/rollbacks & etc.
<https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.snapper.html> - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloC7uAACgkQtTMYHG2NR9WdtwCgiQYPWOKFKrzdvfMFI7KVKuVi phIAn35qmPiWV68Ff4/ZHzIGoMagSgiA =/fi8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
Dave Howorth -
listreader -
Richmond