On 02/11/18 04:56, Dave Close wrote:
> Ed Greshko wrote:
>
>> Grasping at straws here
>>
>> Are you running vnc server as a systemd service that gets started
>> at boot time? I've never had a problem with thatbut if you're
>> doing that how about disabling it for a test.
> No, I started it
Ed Greshko wrote:
> Grasping at straws here
>
> Are you running vnc server as a systemd service that gets started
> at boot time? I've never had a problem with thatbut if you're
> doing that how about disabling it for a test.
No, I started it from the command line. Recall that I had the s
On 02/11/18 04:21, Dave Close wrote:
> Ed Greshko wrote:
>
>> If you ssh into the failing system and run "top" does anything
>> seem odd? A process stuck at the top or hogging CPU?
> 99.7% idle. Occasionally, plasmashell or vncserver will show a few
> percent. Usually top itself is the big user.
Ed Greshko wrote:
> If you ssh into the failing system and run "top" does anything
> seem odd? A process stuck at the top or hogging CPU?
99.7% idle. Occasionally, plasmashell or vncserver will show a few
percent. Usually top itself is the big user.
--
Dave Close, Compata, Irvine CA "You ca
On 02/11/18 03:56, Dave Close wrote:
> Ed Greshko wrote:
>
>> Can you run "dnf distro-sync" just to make sure all packages are
>> at the most current level?
> Dependencies resolved.
> Nothing to do.
OK
If you ssh into the failing system and run "top" does anything seem odd? A
process
Ed Greshko wrote:
> Can you run "dnf distro-sync" just to make sure all packages are
> at the most current level?
Dependencies resolved.
Nothing to do.
--
Dave Close, Compata, Irvine CA "'Always' and 'never' are two
d...@compata.com, +1 714 434 7359words you should always remember
d
On 02/11/18 02:42, Dave Close wrote:
> Ed Greshko wrote:
>
You do get a login screen and then when you enter your PW you end
up with a black screen with a cursor you can move around?
>>> Yes. Exactly.
>> OK then at that point the X-server is functioning normally. Would
>> it be possible t
Ed Greshko wrote:
>>> You do get a login screen and then when you enter your PW you end
>>> up with a black screen with a cursor you can move around?
>> Yes. Exactly.
>
> OK then at that point the X-server is functioning normally. Would
> it be possible to do the following?
>
> 1. Reboot the syste
Samuel Sieb wrote:
Well, I'm certainly seeking hints. The VNC session got me to a
blank screen image. I opened an xterm on it and ran startx.
>>>
>>> You what? You ran startx from within an X session?
>>
>> Well, it's been a few days. I agree that doesn't make sense. I'll
>> try it aga
On 02/10/18 14:25, Dave Close wrote:
> Ed Greshko wrote:
>
Is your system a desktop with a single monitor? A laptop with
external monitor? Or something else?
>>> It's a desktop with a single monitor.
>>>
If you do use either sddm or kdm do you get a login screen? Couldn't
hurt t
On 02/09/2018 10:27 PM, Dave Close wrote:
Samuel Sieb wrote:
Well, I'm certainly seeking hints. The VNC session got me to a
blank screen image. I opened an xterm on it and ran startx.
You what? You ran startx from within an X session?
Well, it's been a few days. I agree that doesn't make s
Samuel Sieb wrote:
>> Well, I'm certainly seeking hints. The VNC session got me to a
>> blank screen image. I opened an xterm on it and ran startx.
>
> You what? You ran startx from within an X session?
Well, it's been a few days. I agree that doesn't make sense. I'll
try it again and post a cla
Ed Greshko wrote:
>>> Is your system a desktop with a single monitor? A laptop with
>>> external monitor? Or something else?
>> It's a desktop with a single monitor.
>>
>>> If you do use either sddm or kdm do you get a login screen? Couldn't
>>> hurt to try that as Samuel has suggested.
>> Using k
On 02/09/2018 10:04 PM, Dave Close wrote:
Samuel Sieb wrote:
I'm not switching consoles. I haven't yet reached the opportunity
to do so when the system hangs and the black screen appears. After
that, yes, I can and do switch to a text console so I can kill the
hung KDE session.
You do switch
Samuel Sieb wrote:
>> I'm not switching consoles. I haven't yet reached the opportunity
>> to do so when the system hangs and the black screen appears. After
>> that, yes, I can and do switch to a text console so I can kill the
>> hung KDE session.
>
> You do switch consoles and you just again sai
On 02/10/18 13:55, Dave Close wrote:
> Ed Greshko wrote:
>
>> Is your system a desktop with a single monitor? A laptop with
>> external monitor? Or something else?
> It's a desktop with a single monitor.
>
>> If you do use either sddm or kdm do you get a login screen? Couldn't
>> hurt to try that a
Ed Greshko wrote:
> Is your system a desktop with a single monitor? A laptop with
> external monitor? Or something else?
It's a desktop with a single monitor.
> If you do use either sddm or kdm do you get a login screen? Couldn't
> hurt to try that as Samuel has suggested.
Using kdm, I get exac
On 02/08/2018 09:26 PM, Dave Close wrote:
Ed Greshko wrote:
Looking at your Xorg.0.log I see this at the end.
[ 221.964] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 222.058] (II) systemd-logind: got pause for 13:65
[ 222.058] (II) systemd-logind: got pause for 13:69
[ 222.059]
On 02/09/18 13:26, Dave Close wrote:
> Ed Greshko wrote:
>
>> Looking at your Xorg.0.log I see this at the end.
>>
>> [ 221.964] (II) AIGLX: Suspending AIGLX clients for VT switch
>> [ 222.058] (II) systemd-logind: got pause for 13:65
>> [ 222.058] (II) systemd-logind: got pause for 13:69
>>
I wrote:
>But it certainly does look like the systemd-logind pause is stuck
>and could be the cause of my problem.
BTW, /etc/systemd/logind.conf contains only comments and none of the
other logind configuration files are present.
--
Dave Close, Compata, Irvine CA +1 714 434 7359
Ed Greshko wrote:
> Looking at your Xorg.0.log I see this at the end.
>
> [ 221.964] (II) AIGLX: Suspending AIGLX clients for VT switch
> [ 222.058] (II) systemd-logind: got pause for 13:65
> [ 222.058] (II) systemd-logind: got pause for 13:69
> [ 222.059] (II) systemd-logind: got pause fo
On 02/09/18 12:37, Samuel Sieb wrote:
> I'm pretty sure you're just missing some piece because of how you're starting
> it.
> Gnome and KDE are really not designed to be started this way.
FWIW, KDE starts just fine for me on several F27 systems using "startx".
--
A motto of mine is: When in
On 02/06/2018 09:27 PM, Dave Close wrote:
I have two systems that were recently upgraded from Fedora 26 to 27
using DNF system-upgrade. Both were successfully running a KDE desktop
for several generations previously, including on F26. In both cases,
after the upgrade, starting KDE showed the spla
On 02/06/2018 09:27 PM, Dave Close wrote:
One of the systems is a 32-bit laptop with little local content. I
chose to simply do a fresh install on this one to get it working
quickly. Fedora doesn't offer an installation image for 32-bit F27
so I installed F25 and then did successive upgrades to F
On 02/08/18 23:57, Dave Close wrote:
> Ed Greshko wrote:
>
>> On 02/08/18 19:30, Patrick O'Callaghan wrote:
>>> I think you said that Gnome does start but KDE doesn't, so it's likely
>>> that something in the KDE config is causing the problem.
>> Well, unless GNOME is using Wayland?
> The way I rea
Ed Greshko wrote:
> Could you upload /home/dave/.local/share/xorg/Xorg.0.log for
> others to look at? The one on my test system is 402 lines long so
> yours may be equally long.
Sure. Here's the latest version.
--
Dave Close, Compata, Irvine CA "Genius may have its limitations,
d...@compata
Ed Greshko wrote:
>On 02/08/18 19:30, Patrick O'Callaghan wrote:
>> I think you said that Gnome does start but KDE doesn't, so it's likely
>> that something in the KDE config is causing the problem.
> Well, unless GNOME is using Wayland?
The way I read the release notes, it is. Though there app
On 02/08/18 19:30, Patrick O'Callaghan wrote:
> On Wed, 2018-02-07 at 21:46 -0800, Dave Close wrote:
>> "Patrick O'Callaghan" wrote:
>>
>>> You might want to post on the Fedora KDE list for this kind
>>> of problem.
>> I may try that. But the XIO errors and the failure to open the
>> display made m
On Wed, 2018-02-07 at 21:46 -0800, Dave Close wrote:
> "Patrick O'Callaghan" wrote:
>
> > You might want to post on the Fedora KDE list for this kind
> > of problem.
>
> I may try that. But the XIO errors and the failure to open the
> display made me think this might be a better place.
I think y
On 02/08/18 13:40, Dave Close wrote:
> Ed Greshko wrote:
>
>>> (==) Using config file: "/etc/X11/xorg.conf"
>> First, check the file /home/dave/.local/share/xorg/Xorg.0.log for
>> the complete Xorg log. Looking for EE lines
> I found only two such lines, each present only in one of eight logs.
>
>
"Patrick O'Callaghan" wrote:
> You might want to post on the Fedora KDE list for this kind
> of problem.
I may try that. But the XIO errors and the failure to open the
display made me think this might be a better place.
--
Dave Close, Compata, Irvine CA +1 714 434 7359
d...
Ed Greshko wrote:
>> (==) Using config file: "/etc/X11/xorg.conf"
>
> First, check the file /home/dave/.local/share/xorg/Xorg.0.log for
> the complete Xorg log. Looking for EE lines
I found only two such lines, each present only in one of eight logs.
(1) intel(0): Failed to submit rendering com
I wrote:
> I have two systems that were recently upgraded from Fedora 26 to 27
> using DNF system-upgrade. Both were successfully running a KDE desktop
> for several generations previously, including on F26. In both cases,
> after the upgrade, starting KDE showed the splash screen and then
> a bla
On Wed, 2018-02-07 at 21:26 +0800, Ed Greshko wrote:
> On 02/07/18 18:31, Patrick O'Callaghan wrote:
> > On Wed, 2018-02-07 at 11:24 +0530, Prasad K wrote:
> > > >startkde: Shutting down...
> > > >kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0)
> > > > failed: : No such file
On 02/07/18 18:31, Patrick O'Callaghan wrote:
> On Wed, 2018-02-07 at 11:24 +0530, Prasad K wrote:
>>>startkde: Shutting down...
>>>kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: :
>>> No such file or directory
>>>Error: Can not contact kdeinit5!
>>>xprop:
On Wed, 2018-02-07 at 11:24 +0530, Prasad K wrote:
> >startkde: Shutting down...
> >kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: :
> > No such file or directory
> >Error: Can not contact kdeinit5!
> >xprop: unable to open display ':0'
> >xprop: unabl
On 02/07/18 13:27, Dave Close wrote:
> (==) Using config file: "/etc/X11/xorg.conf"
First, check the file /home/dave/.local/share/xorg/Xorg.0.log for the complete
Xorg
log. Looking for EE lines
On all of my systems that file doesn't exist since everything is determined by
the
kernel. That l
On 07/02/18 10:57 AM, Dave Close wrote:
I have two systems that were recently upgraded from Fedora 26 to 27
using DNF system-upgrade. Both were successfully running a KDE desktop
for several generations previously, including on F26. In both cases,
after the upgrade, starting KDE showed the splash
I have two systems that were recently upgraded from Fedora 26 to 27
using DNF system-upgrade. Both were successfully running a KDE desktop
for several generations previously, including on F26. In both cases,
after the upgrade, starting KDE showed the splash screen and then
a blank screen with only
39 matches
Mail list logo
