> Well, darn. I was hoping that a "startx" would at least output something
> that could
> give a clue as to why plasmashell is crashing.
He, you are right, I have something in the terminal:
xauth: file /home/fred/.serverauth.1393 does not exist
X.Org X Server 1.19.3
Release Date: 2017-03-15
..
On 06/23/17 20:50, Frédéric Bron wrote:
>> I would, based on another problem you recently had, that you do the
>> following
>> Again bring up the system in run level 3. Before you startx
>> sudo setenforce 0
>> startx as your normal self.
> I did that but it is not better :(
Well, darn. I w
> I would, based on another problem you recently had, that you do the
> following
> Again bring up the system in run level 3. Before you startx
> sudo setenforce 0
> startx as your normal self.
I did that but it is not better :(
Thanks,
Frédéric
On 06/23/17 19:33, Frédéric Bron wrote:
> I did that as user (not as root). I got:
> $DISPLAY is not set or cannot connect to the X server
Sorry
That should have been "startx" and not "startkde"
--
Fedora Users List - The place to go to speculate endlessly
signature.asc
Description: Ope
On 06/23/17 19:28, Frédéric Bron wrote:
> KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
> KCrash: Application 'plasmashell' crashing...
> KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
Well, that is the problem. Although I must admit that at this point I'm not
sur
> Boot to run level 3.
> Login in text mode.
> startkde
I did that as user (not as root). I got:
$DISPLAY is not set or cannot connect to the X server
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users
> Try looking at ~/.xsession-errors just after things go black to see if
> there's anything interesting.
I find this:
xset: bad font path element (#2), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or s
On 06/23/17 18:50, Frédéric Bron wrote:
>> Boot to run level 3.
> how do I do that?
>
When the boot screen comes up with the kernel selections, press "e" to edit.
Then scroll down to the linux16 line showing the kernel you are booting and
append a
3. Then ctrl-x to continue the boot process.
FW
On 06/23/2017 03:49 AM, Frédéric Bron wrote:
Since you can login from another system, or switch to a text terminal, can you
check
if /usr/bin/plasmashell is running when you have the black screen?
I see that plasmashell starts just after login,
then it disappears when the black screen comes.
> Boot to run level 3.
how do I do that?
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Since you can login from another system, or switch to a text terminal, can
> you check
> if /usr/bin/plasmashell is running when you have the black screen?
I see that plasmashell starts just after login,
then it disappears when the black screen comes. I can also see this
for a few seconds in t
> Are you able to plug a secondary screen in? If so, how does it behave?
behaves the same.
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
On 06/23/17 17:54, Frédéric Bron wrote:
> I just tried multiple times again, still the blackout.
> I also tried to use a different kernel but both 4.11.4 and 4.11.5 give
> the same issue.
> I have an nvidia card but I use the nouveau driver on this computer
> (never installed the proprietary driver
On 06/23/17 17:54, Frédéric Bron wrote:
> I just tried multiple times again, still the blackout.
> I also tried to use a different kernel but both 4.11.4 and 4.11.5 give
> the same issue.
> I have an nvidia card but I use the nouveau driver on this computer
> (never installed the proprietary driver
Hello Frédéric,
On Fri, 23 Jun 2017 11:54:52 +0200 Frédéric Bron wrote:
> > Well, it is a selection on the lower left of the sddm login screen.
>
> I have nothing there.
>
> >>> Since you can get to a text terminal. Have you tried creating another
> >>> user and then
> >>> logging in as t
> Well, it is a selection on the lower left of the sddm login screen.
I have nothing there.
>>> Since you can get to a text terminal. Have you tried creating another user
>>> and then
>>> logging in as that user?
>> just done it, same problem with the new user
>>
>
> Humm.
I just tried mul
On 06/23/17 13:38, Frédéric Bron wrote:
> Hi,
>
> Since this morning, after loging in on a Plasma KDE session, I can
> first see the desktop then only a black screen with only the mouse
> available, nothing else.
> Ctrl+Alt+Suppr, brings the log out screen so I can log out.
> I can also switch to a
On 06/23/17 15:03, Frédéric Bron wrote:
>
> The screen is not the issue because I get the ssdm login screen perfectly
> well.
> Also it's a laptop with an external screen. I have tested with and
> without the external screen plug-in, same behaviour.
OK, I didn't know what your HW was. FWIW, I ha
> First, I can't see how any of the 3 packages updated would be in any way
> responsible.
> I assume you've already booted at least once more.
I tried 3-4 times.
> Have you also re-seated video
> cables? I've had unexplained video issues cleared up by doing that.
The screen is not the issue b
On 06/23/17 13:38, Frédéric Bron wrote:
> Since this morning, after loging in on a Plasma KDE session, I can
> first see the desktop then only a black screen with only the mouse
> available, nothing else.
> Ctrl+Alt+Suppr, brings the log out screen so I can log out.
> I can also switch to a text te
Hi,
Since this morning, after loging in on a Plasma KDE session, I can
first see the desktop then only a black screen with only the mouse
available, nothing else.
Ctrl+Alt+Suppr, brings the log out screen so I can log out.
I can also switch to a text terminal with Ctrl+Alt+F2. That's all.
Before
21 matches
Mail list logo
