On Wed, 16 Jul 2014 15:57:26 +0530
Prashanth Kasula wrote:
> "Oh no! Something has gone wrong. A problem has occured and the
> system can't recover. Please log out and try again." (forcing you to
> close the session, just to reappear on restart)
This is the generic m
On Wed, 2014-07-16 at 15:57 +0530, Prashanth Kasula wrote:
> "Oh no! Something has gone wrong. A problem has occured and the system
> can't recover. Please log out and try again." (forcing you to close the
> session, just to reappear on restart)
>
>
> Please
"Oh no! Something has gone wrong. A problem has occured and the system
can't recover. Please log out and try again." (forcing you to close the
session, just to reappear on restart)
Please help.
--
Prashanth Kasula
Sr.System Administrator.
--
users mailing list
users@lists.fe
On 10/31/2013 06:11 AM, Theodore Papadopoulo wrote:
One solution I dound with difficulty is that Alt+F4 (I think) kills
the "frowning computer" and (at least in my case) leaves you with a
working system. Surely something to be improved in the UI
And the first step, of course, is a more info
tempt to install the manufacturer's nvidia driver,
> > my system (Fedora 19, with both Gnome and KDE, on a Lenovo ThinkPad
> > T430) does not reach the graphical login screen any more, but
> > instead ends up in a white screen with a frowning computer cartoon
> > and the m
ach the graphical login screen any more, but
> instead ends up in a white screen with a frowning computer cartoon
> and the message
>
> "Oh no! Something has gone wrong. A problem occurred and the
> system can't recover. Please contact a system administrator."
One sol
Hello,
On Thu, Oct 31, 2013 at 7:55 AM, Oliver Ruebenacker wrote:
>
> Hello,
>
> On Thu, Oct 31, 2013 at 3:25 AM, Heinz Diehl wrote:
>
>> On 31.10.2013, Oliver Ruebenacker wrote:
>>
>> > Failed to load module "nv" (module does not exist, 0)
>>
>> Take a look into /boot/grub2/grub.cfg
Hello,
On Thu, Oct 31, 2013 at 3:25 AM, Heinz Diehl wrote:
> On 31.10.2013, Oliver Ruebenacker wrote:
>
> > Failed to load module "nv" (module does not exist, 0)
>
> Take a look into /boot/grub2/grub.cfg, most probably the uninstaller
> didn't restore the kernel boot parameters which has
On 31.10.2013, Oliver Ruebenacker wrote:
> Failed to load module "nv" (module does not exist, 0)
Take a look into /boot/grub2/grub.cfg, most probably the uninstaller
didn't restore the kernel boot parameters which has been placed in
order to get the nv driver to work. Looks like you'll have to
n any more, but instead
ends up in a white screen with a frowning computer cartoon and the
message
"Oh no! Something has gone wrong. A problem occurred and the system
can't recover. Please contact a system administrator."
I can still do Ctrl-Alt-F2 to log into text mode. When
white screen with a frowning computer cartoon and the
message
"Oh no! Something has gone wrong. A problem occurred and the system
can't recover. Please contact a system administrator."
I can still do Ctrl-Alt-F2 to log into text mode. When I try startx,
I get an empty screen
ssage
"Oh no! Something has gone wrong. A problem occurred and the system can't
recover. Please contact a system administrator."
I can still do Ctrl-Alt-F2 to log into text mode. When I try startx, I
get an empty screen with white or black background and a mouse cursor,
extending
0 Nov 2012
> 15:10:26
> +1000 Subject: vncserver giving Oh No. Something has gone
> wrong?
> Priority: normal
>
>> Have a machine that I setup Fedora 17 on some time ago, and vnc works
>> just fine, but have recently done a clean install on anot
On 20 Nov 2012 at 15:10, Michael D. Setzer II wrote:
From: "Michael D. Setzer II"
To: users@lists.fedoraproject.org
Date sent: Tue, 20 Nov 2012 15:10:26 +1000
Subject:vncserver giving Oh No. Something has gone
wrong
Have a machine that I setup Fedora 17 on some time ago, and
vnc works just fine, but have recently done a clean install on
another machine, and it connects fine, prompts for password, but
then displays the Oh No. Something has gone wrong. The
machines have the same video cards, and have the
Editing of subject: it is for F17, not 16
Sometimes, I get the message as per title, I click on the Terminate
button and everything starts as usual. Any idea how to debug this issue??
--
Antonio M
Skype: amontag52
Linux Fedora F17 (Beefy Miracle) on Acer 5720
http://lugsaronno.altervista.or
Sometimes, I get the message as per title, I click on the Terminate
button and everything starts as usual. Any idea how to debug this issue??
--
Antonio M
Skype: amontag52
Linux Fedora F17 (Beefy Miracle) on Acer 5720
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
--
users
On 06/05/2011 02:33 AM, Gregory P. Ennis wrote:
> Rahul,
>
> I had reported this problem in another post on this list. There is
> already a bug reported but I have not been able to get any responses.
> My view is that this is going to be a major problem, at least it is for
> me. If there is anythi
On 06/05/2011 02:33 AM, Gregory P. Ennis wrote:
> Rahul,
>
> I had reported this problem in another post on this list. There is
> already a bug reported but I have not been able to get any responses.
> My view is that this is going to be a major problem, at least it is for
> me. If there is anythi
On 06/05/2011 02:33 AM, Gregory P. Ennis wrote:
> Rahul,
>
> I had reported this problem in another post on this list. There is
> already a bug reported but I have not been able to get any responses.
> My view is that this is going to be a major problem, at least it is for
> me. If there is anythi
On 05/27/2011 02:01 PM, valent.turko...@gmail.com wrote:
> I tried also loading nvidia proprietary module but it looks it doesn't
> support latest X in Fedora 15.
>
> I'm willing to work with devels to track down bugs and make Fedora 15
> and GNOME Shell better but need some guidance
Best thing f
On 05/27/2011 02:01 PM, valent.turko...@gmail.com wrote:
> I tried also loading nvidia proprietary module but it looks it doesn't
> support latest X in Fedora 15.
>
> I'm willing to work with devels to track down bugs and make Fedora 15
> and GNOME Shell better but need some guidance
Best thing fo
Hi guys and galls,
I'm testing few older gpraphics cards and few nvidia cards have issue
when using nouveao module that after typing in login info I don't see
GNOME Shell nor compatible mode dekstop but just get message saying:
"Oh no! Something has gond wrong. A problem has occured and the system
23 matches
Mail list logo