[opensuse-factory] Gnome 3.26 upgrade not working (blank login screen)
I was hoping I could be giving some points as to how to debug this / get more useful information for this mailing list. After upgrading to gnome 3.26 and restarting, the login screen failed to display. I'm just left with a black screen with the mouse cursor displaying (and able to move). I've rolled back to my previous snapshot for now. PS: Kudos to you guys for getting this release out so quickly though! -- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2017-09-15 at 12:02 +0100, Michael Aquilina wrote:
I was hoping I could be giving some points as to how to debug this / get more useful information for this mailing list.
After upgrading to gnome 3.26 and restarting, the login screen failed to display. I'm just left with a black screen with the mouse cursor displaying (and able to move).
I've rolled back to my previous snapshot for now.
Did you happen to save the journal at least before reverting? how did you to the upgrade? Tell me you did use 'zypper dup' please - it's the only valid way
PS: Kudos to you guys for getting this release out so quickly though!
Would be nicer if it worked for you to Cheers, Dominique
Did you happen to save the journal at least before reverting? I thought logs were kept on a partition which is not rolled back?
how did you to the upgrade? Tell me you did use 'zypper dup' please - it's the only valid way
Ah, I feel silly now. I didnt realise this was actually the case. Will try this out and see how it goes. I'll try get details from the journal if it fails again too. Is there any particular data that I should be looking for? On a slightly separate discussion, is there any way to prevent users from running 'zypper up' rather than 'zypper up' for cases like these? I feel like this is an easy to mistake to make if you are unaware or new to the distro. Thanks for the help! Mike On Fri, Sep 15, 2017 at 12:10 PM, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
On Fri, 2017-09-15 at 12:02 +0100, Michael Aquilina wrote:
I was hoping I could be giving some points as to how to debug this / get more useful information for this mailing list.
After upgrading to gnome 3.26 and restarting, the login screen failed to display. I'm just left with a black screen with the mouse cursor displaying (and able to move).
I've rolled back to my previous snapshot for now.
Did you happen to save the journal at least before reverting? how did you to the upgrade? Tell me you did use 'zypper dup' please - it's the only valid way
PS: Kudos to you guys for getting this release out so quickly though!
Would be nicer if it worked for you to
Cheers, Dominique
-- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Michael Aquilina <michaelaquilina@gmail.com> [09-15-17 07:19]:
Did you happen to save the journal at least before reverting? I thought logs were kept on a partition which is not rolled back?
how did you to the upgrade? Tell me you did use 'zypper dup' please - it's the only valid way
Ah, I feel silly now. I didnt realise this was actually the case. Will try this out and see how it goes. I'll try get details from the journal if it fails again too. Is there any particular data that I should be looking for?
On a slightly separate discussion, is there any way to prevent users from running 'zypper up' rather than 'zypper up' for cases like these? I feel like this is an easy to mistake to make if you are unaware or new to the distro.
yes, if you run Tw, you use "dup" not up. has been the case and recommendation for the history of Tw and before. it is possible to use "up" in particular situations when you *really* know that it is necessary. simple answer: for Tw *always* use "zypper dup" -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
This is good advice to hear :) Would something like a warning when running 'zypper up' on tumbleweed be useful? (even if its an alias of some kind). I had never heard of this recommendation before today and I am guessing that probably am not the only one. I'm guessing its probably in opensuse documentation somewhere, but that's easy to miss as a new user. On Fri, Sep 15, 2017 at 12:30 PM, Patrick Shanahan <paka@opensuse.org> wrote:
* Michael Aquilina <michaelaquilina@gmail.com> [09-15-17 07:19]:
Did you happen to save the journal at least before reverting? I thought logs were kept on a partition which is not rolled back?
how did you to the upgrade? Tell me you did use 'zypper dup' please - it's the only valid way
Ah, I feel silly now. I didnt realise this was actually the case. Will try this out and see how it goes. I'll try get details from the journal if it fails again too. Is there any particular data that I should be looking for?
On a slightly separate discussion, is there any way to prevent users from running 'zypper up' rather than 'zypper up' for cases like these? I feel like this is an easy to mistake to make if you are unaware or new to the distro.
yes, if you run Tw, you use "dup" not up. has been the case and recommendation for the history of Tw and before.
it is possible to use "up" in particular situations when you *really* know that it is necessary.
simple answer: for Tw *always* use "zypper dup"
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Upgrade worked using 'zypper dup' :) On Fri, Sep 15, 2017 at 12:32 PM, Michael Aquilina <michaelaquilina@gmail.com> wrote:
This is good advice to hear :)
Would something like a warning when running 'zypper up' on tumbleweed be useful? (even if its an alias of some kind). I had never heard of this recommendation before today and I am guessing that probably am not the only one.
I'm guessing its probably in opensuse documentation somewhere, but that's easy to miss as a new user.
On Fri, Sep 15, 2017 at 12:30 PM, Patrick Shanahan <paka@opensuse.org> wrote:
* Michael Aquilina <michaelaquilina@gmail.com> [09-15-17 07:19]:
Did you happen to save the journal at least before reverting? I thought logs were kept on a partition which is not rolled back?
how did you to the upgrade? Tell me you did use 'zypper dup' please - it's the only valid way
Ah, I feel silly now. I didnt realise this was actually the case. Will try this out and see how it goes. I'll try get details from the journal if it fails again too. Is there any particular data that I should be looking for?
On a slightly separate discussion, is there any way to prevent users from running 'zypper up' rather than 'zypper up' for cases like these? I feel like this is an easy to mistake to make if you are unaware or new to the distro.
yes, if you run Tw, you use "dup" not up. has been the case and recommendation for the history of Tw and before.
it is possible to use "up" in particular situations when you *really* know that it is necessary.
simple answer: for Tw *always* use "zypper dup"
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Michael Aquilina
-- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 15/09/2017 08:50, Dominique Leuenberger / DimStar ha scritto:
On Fri, 2017-09-15 at 12:45 +0100, Michael Aquilina wrote:
Upgrade worked using 'zypper dup' :)
great! so, welcome to the world of GNOME 3.26
Cheers, Dominique
Then how could I manage this Gnome update since I always use to execute zypper up? Now I've disabled the Gnome-Factory repo so I can't run "zypper dup --from (Gnome-Factory)" anymore, I have to rely to the main OSS repo. Is there a specific zypper command to use in this case to just "dup" the gnome packages and not everything else? Thanks and regards, -- Marco Calistri N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
On Fri, 2017-09-15 at 13:17 +0000, Marco Calistri wrote:
Il 15/09/2017 08:50, Dominique Leuenberger / DimStar ha scritto:
On Fri, 2017-09-15 at 12:45 +0100, Michael Aquilina wrote:
Upgrade worked using 'zypper dup' :)
great! so, welcome to the world of GNOME 3.26
Cheers, Dominique
Then how could I manage this Gnome update since I always use to execute zypper up?
Now I've disabled the Gnome-Factory repo so I can't run "zypper dup --from (Gnome-Factory)" anymore, I have to rely to the main OSS repo.
Is there a specific zypper command to use in this case to just "dup" the gnome packages and not everything else?
Tumbleweed is not 'only gnome' - it's a complete set of packages built and tested against each other. Either you use zypper dup and take 'a new Tumbleweed snapshot' - or you do whatever else you feel like (incl. zypper up). But if you take 'half snapshots' you won't have the right to complain if it breaks. If you have a specific thing you do NOT want to get updated (e.g. kernel, for whatever reason), add a lock on it. If you have multiple repos enabled, you might want to look into repo preiorities before running dup (and if you had GNOME:Factory enabled, you are also interested in --allow-vendor-change, or nothing is going to happen anyway) Cheers Dominique
Il 15/09/2017 10:27, Dominique Leuenberger / DimStar ha scritto:
On Fri, 2017-09-15 at 13:17 +0000, Marco Calistri wrote:
Il 15/09/2017 08:50, Dominique Leuenberger / DimStar ha scritto:
On Fri, 2017-09-15 at 12:45 +0100, Michael Aquilina wrote:
Upgrade worked using 'zypper dup' :)
great! so, welcome to the world of GNOME 3.26
Cheers, Dominique
Then how could I manage this Gnome update since I always use to execute zypper up?
Now I've disabled the Gnome-Factory repo so I can't run "zypper dup --from (Gnome-Factory)" anymore, I have to rely to the main OSS repo.
Is there a specific zypper command to use in this case to just "dup" the gnome packages and not everything else?
Tumbleweed is not 'only gnome' - it's a complete set of packages built and tested against each other.
Either you use zypper dup and take 'a new Tumbleweed snapshot' - or you do whatever else you feel like (incl. zypper up). But if you take 'half snapshots' you won't have the right to complain if it breaks.
If you have a specific thing you do NOT want to get updated (e.g. kernel, for whatever reason), add a lock on it.
If you have multiple repos enabled, you might want to look into repo preiorities before running dup (and if you had GNOME:Factory enabled, you are also interested in --allow-vendor-change, or nothing is going to happen anyway)
Cheers Dominique
Thanks! Cheers, -- Marco Calistri
participants (4)
-
Dominique Leuenberger / DimStar -
Marco Calistri -
Michael Aquilina -
Patrick Shanahan