On 01/05/2013 12:57 PM, antonio wrote:
Joe Zeff ha scritto / said the followingil giorno/on 11/12/2012
22:19:
On 12/11/2012 01:07 PM, antonio wrote:
I have a doubt on this subjectif the error is before login, where
shall I get the .xsession-errors file???
A new version of the file i
Joe Zeff ha scritto / said the followingil giorno/on 11/12/2012 22:19:
On 12/11/2012 01:07 PM, antonio wrote:
I have a doubt on this subjectif the error is before login, where
shall I get the .xsession-errors file???
A new version of the file is created when you start an X session, b
On 12/11/2012 04:07 PM, antonio wrote:
Tim ha scritto / said the followingil giorno/on 09/12/2012 05:43:
Allegedly, on or about 08 December 2012, Joe Zeff sent:
Use Ctrl-Alt-F2 to get to a text console and log in. To get back to
the GUI screen use Ctrl-Alt-F8.
Or, perhaps, Ctrl Alt F1, t
On 12/11/2012 01:07 PM, antonio wrote:
I have a doubt on this subjectif the error is before login, where
shall I get the .xsession-errors file???
A new version of the file is created when you start an X session, but it
isn't deleted when you log out. Thus, if you log into a text console
Tim ha scritto / said the followingil giorno/on 09/12/2012 05:43:
Allegedly, on or about 08 December 2012, Joe Zeff sent:
Use Ctrl-Alt-F2 to get to a text console and log in. To get back to
the GUI screen use Ctrl-Alt-F8.
Or, perhaps, Ctrl Alt F1, to get back to the GUI. It depends on wh
Allegedly, on or about 08 December 2012, Joe Zeff sent:
> Use Ctrl-Alt-F2 to get to a text console and log in. To get back to
> the GUI screen use Ctrl-Alt-F8.
Or, perhaps, Ctrl Alt F1, to get back to the GUI. It depends on what
Fedora release you're using, and how you started up a GUI.
You us
On 12/08/2012 03:42 PM, antonio montagnani wrote:
I am experiencing the same problem now and then...can you explain how I
can get an an alternate text console???
Tnx
--
Use Ctrl-Alt-F2 to get to a text console and log in. To get back to the
GUI screen use Ctrl-Alt-F8.
--
users mailing list
u
Joe Zeff ha scritto / said the followingil giorno/on 08/12/2012 16:49:
On 12/08/2012 07:10 AM, jiwa navid wrote:
/i am getting the same "oh no something went wrong...logout n try
again" msg after installing vlc.
can any 1 give me solution to this. i really want to ge
2012/11/7 antonio.montagn...@alice.it
> Suddenly I get this message when I boot the machine, then I click on
> Session
> terminate (maybe translation iws wrong) and I can log regularly.
>
> What is going
> on???
>
>
> Antonio Montagnani
>
> Fedora 17 Beefy Miracle (Linux)
> http://www.campingmont
Suddenly I get this message when I boot the machine, then I click on Session
terminate (maybe translation iws wrong) and I can log regularly.
What is going
on???
Antonio Montagnani
Fedora 17 Beefy Miracle (Linux)
http://www.campingmonterosa.com
Delivered by Alice webmail
--
users mailing li
Am 26.08.2012 02:41, schrieb Joe Zeff:
> On 08/25/2012 04:28 PM, JD wrote:
>> The way the apps are stacked so deeply upon lib after lib, by the time
>> the failure
>> is returned to the calling app, the app has no ide what happened. The
>> high library
>> stack is very likely to blame.
>
> So?
On 08/25/2012 06:41 PM, Joe Zeff wrote:
On 08/25/2012 04:28 PM, JD wrote:
The way the apps are stacked so deeply upon lib after lib, by the time
the failure
is returned to the calling app, the app has no ide what happened. The
high library
stack is very likely to blame.
So? Each lib that det
On 08/25/2012 04:28 PM, JD wrote:
The way the apps are stacked so deeply upon lib after lib, by the time
the failure
is returned to the calling app, the app has no ide what happened. The
high library
stack is very likely to blame.
So? Each lib that detects an error should log it instead of jus
On 08/25/2012 04:11 PM, Joe Zeff wrote:
On 08/25/2012 03:00 PM, M A Young wrote:
That is a rather useless generic error message (from gnome-shell I
think) which doesn't give you a clue as to what actually went wrong, so
the bug report you found could be a for completely different problem.
An
On 08/25/2012 04:00 PM, M A Young wrote:
On Sat, 25 Aug 2012, JD wrote:
FC16, just run a full update.
Rebooted (with latest kernel).
I got the error banner for the first time during boot, but just
before the gdm greeting banner:
Oh, oh. Something went wrong etc.
Found that someone
On 08/25/2012 03:00 PM, M A Young wrote:
That is a rather useless generic error message (from gnome-shell I
think) which doesn't give you a clue as to what actually went wrong, so
the bug report you found could be a for completely different problem.
And, AIUI, there's no clear way to get any f
On Sat, 25 Aug 2012, JD wrote:
FC16, just run a full update.
Rebooted (with latest kernel).
I got the error banner for the first time during boot, but just before the
gdm greeting banner:
Oh, oh. Something went wrong etc.
Found that someone has opened a bug about this with redhat
FC16, just run a full update.
Rebooted (with latest kernel).
I got the error banner for the first time during boot, but just before
the gdm greeting banner:
Oh, oh. Something went wrong etc.
Found that someone has opened a bug about this with redhat bugzilla: 819340
back in May of this
Yes, this looks like it was an SELinux issue with regards to old ICC
color profiles left lying around, because F16 has some new SELinux
types and the old files don't get relabeled when you upgrade F15 to
F16.
To fix this, I updated F16 to the latest SELinux policy files (yum
update). However rathe
Deron Meranda ha scritto / said the followingil giorno/on 16/11/2011
06:06:
> Here's the .xsession-errors file. I can't really understand what in
> here are just warnings and what's actually the real problem. I also
> removed the $HOME/.config and $HOME/.gvfs directories too just to make
> su
Here's the .xsession-errors file. I can't really understand what in
here are just warnings and what's actually the real problem. I also
removed the $HOME/.config and $HOME/.gvfs directories too just to make
sure there wasn't something in there causing problems.
If I quickly press Alt-F4 when the
I've upgraded from Fedora 15 to 16 (x86_64). Now when I attempt to
login using the Gnome shell, it brings up a small window with a
message "Oh no! Something went wrong", and after a few seconds returns
to the login screen. I can login fine using the Xfce or WindowMaker
sessions.
I
On 11/10/2011 11:38 AM, Niels Weber wrote:
> 2011/11/9 Daniel J Walsh:
>> On 11/09/2011 11:26 AM, Antonio M wrote:
>>> 2011/11/9 Niels Weber:
2011/11/9 Antonio M:
> 2011/11/9 Niels Weber:
>> I have a similar issue.
>>
>> the login screen didn't work, switching to runlevel 3 and
2011/11/9 Daniel J Walsh :
> On 11/09/2011 11:26 AM, Antonio M wrote:
>> 2011/11/9 Niels Weber :
>>> 2011/11/9 Antonio M :
2011/11/9 Niels Weber :
> I have a similar issue.
>
> the login screen didn't work, switching to runlevel 3 and
> startx worked though. Setting selinux to
On 9 November 2011 00:10, antonio montagnani
wrote:
> Joe Zeff ha scritto / said the following il giorno/on 09/11/2011 00:49:
>> On 11/08/2011 03:33 PM, antonio montagnani wrote:
>>> and I cannot login in Gnome...
>>> System fully updated and luckily I have KDE installed.
>>> Selinux is act
On 11/10/2011 01:28 AM, antonio montagnani wrote:
> Tim ha scritto / said the followingil giorno/on 10/11/2011 06:16:
>> And doing a relabel twice is hardly likely to produce a different
>> result.
>>
>>
> because I am not sure that he effectively switched from Selinux=targeted
> to Selinux=d
Tim ha scritto / said the followingil giorno/on 10/11/2011 06:16:
> Niels Weber:
>>> I did a
>>> touch /.autorelabel
>>> and rebooted.
>>> I think it said something about rebuilding the targeted setup and it
>>> took quite some time.
>
>
> Antonio M:
>> I would disable (not permissive) Selinux,
Niels Weber:
>> I did a
>> touch /.autorelabel
>> and rebooted.
>> I think it said something about rebuilding the targeted setup and it
>> took quite some time.
Antonio M:
> I would disable (not permissive) Selinux, boot, then enable again and
> reboot again, in order to have labeling at boot-tim
On 11/09/2011 11:26 AM, Antonio M wrote:
> 2011/11/9 Niels Weber :
>> 2011/11/9 Antonio M :
>>> 2011/11/9 Niels Weber :
Hi,
I have a similar issue.
2011/11/9 Daniel J Walsh :
> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>
> On 11/08/2011 07:15 PM, Joe Zeff
2011/11/9 Niels Weber :
> 2011/11/9 Antonio M :
>> 2011/11/9 Niels Weber :
>>> Hi,
>>>
>>> I have a similar issue.
>>>
>>> 2011/11/9 Daniel J Walsh :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2011 07:15 PM, Joe Zeff wrote:
> On 11/08/2011 04:10 PM, antonio monta
2011/11/9 Antonio M :
> 2011/11/9 Niels Weber :
>> Hi,
>>
>> I have a similar issue.
>>
>> 2011/11/9 Daniel J Walsh :
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 11/08/2011 07:15 PM, Joe Zeff wrote:
On 11/08/2011 04:10 PM, antonio montagnani wrote:
> I rebooted disabli
2011/11/9 Niels Weber :
> Hi,
>
> I have a similar issue.
>
> 2011/11/9 Daniel J Walsh :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 11/08/2011 07:15 PM, Joe Zeff wrote:
>>> On 11/08/2011 04:10 PM, antonio montagnani wrote:
I rebooted disabling Selinux on the command line and
Hi,
I have a similar issue.
2011/11/9 Daniel J Walsh :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/08/2011 07:15 PM, Joe Zeff wrote:
>> On 11/08/2011 04:10 PM, antonio montagnani wrote:
>>> I rebooted disabling Selinux on the command line and I could use
>>> Gnome, then I restarte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2011 07:15 PM, Joe Zeff wrote:
> On 11/08/2011 04:10 PM, antonio montagnani wrote:
>> I rebooted disabling Selinux on the command line and I could use
>> Gnome, then I restarted and system relabeled all files and I
>> could login in Gnome. No
On 11/08/2011 04:10 PM, antonio montagnani wrote:
> I rebooted disabling Selinux on the command line and I could use Gnome,
> then I restarted and system relabeled all files and I could login in Gnome.
> No idea what was going on, but that's it
I'm glad you found it. The reason I asked was that I
Joe Zeff ha scritto / said the followingil giorno/on 09/11/2011 00:49:
> On 11/08/2011 03:33 PM, antonio montagnani wrote:
>> and I cannot login in Gnome...
>> System fully updated and luckily I have KDE installed.
>> Selinux is active
>
> Does the SELinux troubleshooter report any alerts?
On 11/08/2011 03:33 PM, antonio montagnani wrote:
> and I cannot login in Gnome...
> System fully updated and luckily I have KDE installed.
> Selinux is active
Does the SELinux troubleshooter report any alerts? If not, it's not the
issue.
--
users mailing list
users@lists.fedoraproject.org
and I cannot login in Gnome...
System fully updated and luckily I have KDE installed.
Selinux is active
--
Antonio M
Skype: amontag52
Linux Fedora F15 (Lovelock) on Acer 5720
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
http://www.studiodacolpaloschi.it
--
users mail
38 matches
Mail list logo
