Re: [CentOS] Gnome boot problem (again :-) )

[dominic adair-jones]

On Fri, Nov 24, 2017, 8:09 PM vychytraly .  wrote:

> Hello friends
>
> I was using EL7 on gnome 3 for few months without any problem. Even 2 hours
> ago I had the computer (Laptop running on Nvidia-Prime) turned on and
> everything was working without flaw. But when I turned on the computer few
> minutes ago, I got login screen (which does not usually happen, since I
> have autologin turned on) and when I entered my login credentials I got
> black screen and went back to login screen. Everytime I entered my
> credentials the same thing happened so I was stuck in endless login loop.
> At first I thought it was caused by gnome-extension I updated to new
> version today.
>
> So I restarted the pc, went to runlevel 3, renamed the folder with
> extension in
> /home/user/.local/share/gnome-shell/extensions/"extension_name" to another
> name as a quick and dirty way to disable it. I restarted the pc and now I
> can't even get to login screen. I get stuck at text saying: "A start job is
> running for Wait for Plymouth Boot Screen to quit (25s / no limit)".
>
> I can go to another cmdline session and when I try to run exec
> gnome-session nothing happens, I just get logged off the cmdline session
> and must log in again.
>
> When I try to run startx my screen blinks and I get this output:
> xauth: file /home/user/serverauth.2372 does not exist.
>
> Output from command systemctl status gdm says:
> Starting gnome display manager
> Started gnome display manager
> GLib-GObject: g_object_set_valist: object class "GdmSession" has no
> property named "display-is-initial", GdmDisplay: display lasted 2.909...
> Seconds
> gdm_display_finish: assertion 'GDM_IS_DISPLAY (self)' failed
>
> journalctl -r gives me these errors:
> vgargb: this pci device is not a vga device
> gdm_display_finish: assertion 'GDM_IS_Display (self)' failed
> Process 1165 (gnome-shell) of user 42 killed by SIGSEGV - dumping core
> Process 1194 (gnome-shell) of user 42 killed by SIGSEGV - ignoring
> (repeated crash)
> Unrecoverable failure in component org.gnome.Shell.desktop
>
> Please could you help me with finding the problem? I am not really sure
> what could be the issue, since I did not change or update any packages
> today, nor changed the configuration files. Only change I am aware of was
> the update of the gnome-extension.
>
> Thank you very much and have a nice day
> O.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

On Mon, Nov 20, 2017 at 8:42 AM, Johnny Hughes <joh...@centos.org> wrote:
> On 11/17/2017 09:04 AM, m.r...@5-cent.us wrote:
>> dominic adair-jones wrote:
>>> On Fri, Nov 17, 2017 at 9:14 AM,  <m.r...@5-cent.us> wrote:
>>>> dominic adair-jones wrote:
>>>>> going to run journalctl this evening when i get in and relay any errors
>>>>> i see.
>>>>>
>>>>> On Thu, Nov 16, 2017 at 6:01 PM, Pete Biggs <p...@biggs.org.uk> wrote:
>>>>>> On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
>>>>>>> Ok that's what I figured Ive narrowed it down to Plymouth but I
>>>>>>> haven't found much info on what the fix is.
>>>>>>
>>>>>> No, plymouth is the process that controls the booting process. It is
>>>>>> not the problem. It is doing exactly what it's supposed to be doing -
>>>>>> waiting for a process to finish before going on to its next task. You
>>>>>> should use journalctl to see what task it is waiting on.
>>>>>>
>>>>>>>  As of now I can ctl alt f2 and run
>>>>>>> startx to get to a desktop.
>>>>>>
>>>>>> What graphics card do you have?
>>>>>>
>>>>>>>  When I try to run gui (such as keepnote or
>>>>>>> chromium) from within my vms now tho I get errors.
>>>>>>
>>>>>> What errors.
>>>>>>
>>>> Please stop top posting.
>>>>
>>>> It really sounds like a graphics driver error. Have you looked in
>>>> /var/log/Xorg.0.log?
>>> sorry about that first time publicly posting like this. I will check
>>> this evening. I did remove the x0rg drivers and plymouth but didnt
>>> check the logs as it got late.
>>
>> Reading the thread in this post, I see you saying that startx works
>> That would suggest that graphics works, but something in trying to go into
>> runlevel 5 is funny.
>>
>> Stupid question: how long have you waited? C7 seems to take an
>> unconsciously long time for the X login to come up.
>>
>> Do you see the screen go into graphical mode during the boot? You know,
>> when it'll go black, then smaller fonts, and more lines on the screen?
>>
>> Starting to wonder about a timing issue, with a driver not loading.
>>
>
> This sounds like some kind of GDM issue to me.
>
> I am not sure the OP has ever answered the question of what video card
> is installed.
>
> OP:  If you look at Xorg.0.log that should tell you if there is a
> problem starting X.  If you use /var/log/messages, dmseg, and/or
> journalctl it might give you an init type error output.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
thanks, looking thru the log i attached i did notice the gdm error. As
a workaround i installed/switched over to lightdm. still going to
figure out what went wrong with gdm.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

yessir i can alt+ctl+f2 into another tty and run startx from there to
get into my desktop
as of this morning the "plymouth wait" error was running for about 6
hours whatever is causing it to hang never completes
the screen does go into graphical mode..i unlock my volume and then
the grey background with the 7 and spinning white circle comes
up...the circle spins out and then the screen just sits there it never
boots into the actual desktop.

this happened about a month ago i ran a kernel update, then clean up.
i went to sleep and my server shut off. I turned it back on and have
been experiencing this issue ever since. I removed plymouth and then
logged into the 2nd tty and just left it running for about a month
since its my host and i had alot of stuff on there i needed to access.
i have a little downtime for the next few days so im trying to go back
and get this figured out.

On Fri, Nov 17, 2017 at 10:04 AM,  <m.r...@5-cent.us> wrote:
> dominic adair-jones wrote:
>> On Fri, Nov 17, 2017 at 9:14 AM,  <m.r...@5-cent.us> wrote:
>>> dominic adair-jones wrote:
>>>> going to run journalctl this evening when i get in and relay any errors
>>>> i see.
>>>>
>>>> On Thu, Nov 16, 2017 at 6:01 PM, Pete Biggs <p...@biggs.org.uk> wrote:
>>>>> On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
>>>>>> Ok that's what I figured Ive narrowed it down to Plymouth but I
>>>>>> haven't found much info on what the fix is.
>>>>>
>>>>> No, plymouth is the process that controls the booting process. It is
>>>>> not the problem. It is doing exactly what it's supposed to be doing -
>>>>> waiting for a process to finish before going on to its next task. You
>>>>> should use journalctl to see what task it is waiting on.
>>>>>
>>>>>>  As of now I can ctl alt f2 and run
>>>>>> startx to get to a desktop.
>>>>>
>>>>> What graphics card do you have?
>>>>>
>>>>>>  When I try to run gui (such as keepnote or
>>>>>> chromium) from within my vms now tho I get errors.
>>>>>
>>>>> What errors.
>>>>>
>>> Please stop top posting.
>>>
>>> It really sounds like a graphics driver error. Have you looked in
>>> /var/log/Xorg.0.log?
>> sorry about that first time publicly posting like this. I will check
>> this evening. I did remove the x0rg drivers and plymouth but didnt
>> check the logs as it got late.
>
> Reading the thread in this post, I see you saying that startx works
> That would suggest that graphics works, but something in trying to go into
> runlevel 5 is funny.
>
> Stupid question: how long have you waited? C7 seems to take an
> unconsciously long time for the X login to come up.
>
> Do you see the screen go into graphical mode during the boot? You know,
> when it'll go black, then smaller fonts, and more lines on the screen?
>
> Starting to wonder about a timing issue, with a driver not loading.
>
> mark
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

On Fri, Nov 17, 2017 at 9:14 AM,  <m.r...@5-cent.us> wrote:
> dominic adair-jones wrote:
>> going to run journalctl this evening when i get in and relay any errors i
>> see.
>>
>> On Thu, Nov 16, 2017 at 6:01 PM, Pete Biggs <p...@biggs.org.uk> wrote:
>>> On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
>>>> Ok that's what I figured Ive narrowed it down to Plymouth but I haven't
>>>> found much info on what the fix is.
>>>
>>> No, plymouth is the process that controls the booting process. It is
>>> not the problem. It is doing exactly what it's supposed to be doing -
>>> waiting for a process to finish before going on to its next task. You
>>> should use journalctl to see what task it is waiting on.
>>>
>>>
>>>>  As of now I can ctl alt f2 and run
>>>> startx to get to a desktop.
>>>
>>> What graphics card do you have?
>>>
>>>>  When I try to run gui (such as keepnote or
>>>> chromium) from within my vms now tho I get errors.
>>>
>>> What errors.
>>>
> Please stop top posting.
>
> It really sounds like a graphics driver error. Have you looked in
> /var/log/Xorg.0.log?
sorry about that first time publicly posting like this. I will check
this evening. I did remove the x0rg drivers and plymouth but didnt
check the logs as it got late.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

going to run journalctl this evening when i get in and relay any errors i see.

On Thu, Nov 16, 2017 at 6:01 PM, Pete Biggs <p...@biggs.org.uk> wrote:
> On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
>> Ok that's what I figured Ive narrowed it down to Plymouth but I haven't
>> found much info on what the fix is.
>
> No, plymouth is the process that controls the booting process. It is
> not the problem. It is doing exactly what it's supposed to be doing -
> waiting for a process to finish before going on to its next task. You
> should use journalctl to see what task it is waiting on.
>
>
>>  As of now I can ctl alt f2 and run
>> startx to get to a desktop.
>
> What graphics card do you have?
>
>>  When I try to run gui (such as keepnote or
>> chromium) from within my vms now tho I get errors.
>
> What errors.
>
> P.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

Ok so I tried alt+d it switched over to text mode. I didn't see any error
it booted right to a black screen. I can ctl+alt+f2 to get to another
screen and I still get the "a start job is running for wait for Plymouth
boot screen to quit"

On Thu, Nov 16, 2017, 5:55 PM Gordon Messmer <gordon.mess...@gmail.com>
wrote:

> On 11/16/2017 02:01 PM, dominic adair-jones wrote:
> > On Thu, Nov 16, 2017, 4:55 PM Gordon Messmer <gordon.mess...@gmail.com>
> > wrote:
> >> Alt+d will switch to the text output of the init process.  Press that
> >> combo as soon as you see the boot animation.
> > Not understanding. At what point in the boot process should I be doing
> that
>
> ... as soon as you see the boot animation.  When you see the grey
> screen, use Alt+d on the keyboard to switch to the text output. There,
> you will typically see text that describes why the boot process isn't
> completing.
>
> > and why would I need to do that at all?
>
> Because long ago the debugging text was deemed confusing, and a
> graphical wallpaper was placed over it.
>
> > Seems like it's something wrong
> > with the Plymouth and plymouth-scirpt packages.
>
> That's unlikely.  Those packages are probably just hiding the actual
> problem.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

Ok that's what I figured Ive narrowed it down to Plymouth but I haven't
found much info on what the fix is. As of now I can ctl alt f2 and run
startx to get to a desktop. When I try to run gui (such as keepnote or
chromium) from within my vms now tho I get errors.

On Thu, Nov 16, 2017, 5:33 PM Pete Biggs <p...@biggs.org.uk> wrote:

> On Thu, 2017-11-16 at 16:28 -0500, dominic adair-jones wrote:
> > greetings all. running centos 7. i recently performed an upgrade and
> > the server rebooted later in the night. now everytime i start my
> > server its sits at the grey gnome background. i can hit ctl+atl+f2 to
> > get to another console and the error message states "a start job is
> > running for wait for plymouth boot screen to quit". i can ssh into the
> > server but i dont see any obvious issues. this is the brain of my
> > network and houses all my vms and documents. any help would be greatly
> > appreciated.
> >
>
> There's lots of reasons for this - try googling for that message.
>
> A common one is bad video drivers, especially nVidia - nVidia helpfully
> stop supporting certain older cards in the newer drivers, so if you
> have a card that drops support in the most recent driver, you have to
> specifically use an old driver version.
>
> But basically anything that holds up the boot process will eventually
> cause this message - it's not really an error message either, it's just
> telling you that it's waiting for something to happen - the problem is
> elsewhere.
>
> P.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

Not understanding. At what point in the boot process should I be doing that
and why would I need to do that at all? Seems like it's something wrong
with the Plymouth and plymouth-scirpt packagesI uninstalled them and
rebooted I didn't get stuck in a loop but I didn't have a gui. I
reinstalled and I'm back at the Plymouth wait error.

On Thu, Nov 16, 2017, 4:55 PM Gordon Messmer <gordon.mess...@gmail.com>
wrote:

> On 11/16/2017 01:28 PM, dominic adair-jones wrote:
> > now everytime i start my
> > server its sits at the grey gnome background.
>
>
> Alt+d will switch to the text output of the init process.  Press that
> combo as soon as you see the boot animation.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] gnome boot problem

[dominic adair-jones]

greetings all. running centos 7. i recently performed an upgrade and
the server rebooted later in the night. now everytime i start my
server its sits at the grey gnome background. i can hit ctl+atl+f2 to
get to another console and the error message states "a start job is
running for wait for plymouth boot screen to quit". i can ssh into the
server but i dont see any obvious issues. this is the brain of my
network and houses all my vms and documents. any help would be greatly
appreciated.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] last update yum and kernel Problem

[dominic adair-jones]

I had a similar issue. On one of my vms. My host rebooted while the vm was
running its update. I had to remove the kernel then reinstall and it
corrected the issue.

On Sat, Mar 4, 2017, 7:37 AM Günther J. Niederwimmer 
wrote:

> Hello,
>
> the last update brings much Problems ?
>
> On my System the most KVM client have a crashed yum
>
> after reboot the new kernel is broken and have a panic screen
>
> I have to reboot to a older kernel ?
>
> The first I have to run
> yum-complete-transaction
>
> afterward i have to reinstall the kernel ??
>
> this helps to restart the KVM Client !
>
> is it possible the deltarpm is broken ?
>
> Also RPM or "yum check" have a problem with the new update for ipa-*
> I mean the problem is the naming
>
> 4.4.0-14.el7.centos.6
>
>
>
> --
> mit freundlichen Grüssen / best regards
>
>   Günther J. Niederwimmer
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos