I ended up reinstalling the system. Nothing seemed to help. I am still not
sure what happened. But thank you very much for response :)
On Wed, Nov 29, 2017 at 10:25 AM, Anthony K wrote:
> On 25/11/17 12:09, vychytraly . wrote:
>
>> Hello friends
>>
>> I was using EL7 on
On 25/11/17 12:09, 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
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
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
On Mon, Nov 20, 2017 at 8:42 AM, Johnny Hughes 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, wrote:
dominic adair-jones wrote:
> going to run journalctl this evening when
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, 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
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
dominic adair-jones wrote:
> On Fri, Nov 17, 2017 at 9:14 AM, 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 wrote:
On Thu,
On Fri, Nov 17, 2017 at 9:14 AM, 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 wrote:
>>> On Thu, 2017-11-16 at 22:45 +, dominic
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 wrote:
>> On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
>>> Ok that's what I figured Ive narrowed it
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 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
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
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
On 11/16/2017 02:01 PM, dominic adair-jones wrote:
On Thu, Nov 16, 2017, 4:55 PM Gordon Messmer
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
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
On 16/11/17 22:32, Pete Biggs 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
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
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
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.
___
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
20 matches
Mail list logo