KDE session display scrambled (was Re: sddm blank screen)
Graham Menhennitt
graham at menhennitt.com.au
Thu Dec 19 09:06:58 GMT 2019
So, I've got things partially working, but it's not very good.
I created a .xinitrc containing:
kwin_x11 &
exec plasmashell
and then run startx.
I do get a plasma desktop with a Task Manager and an Application
Launcher. But the launcher is mostly empty (Favourites, Applications,
Computer, History, and Leave but no applications in any of them). And
when I manually add things to them, they've disappeared when I restart.
I'm tempted to blow the whole machine away and reinstall from scratch,
but I'd like to try any alternatives first.
Any further help would be appreciated.
Thanks,
Graham
On 15/12/19 10:25 pm, Graham Menhennitt wrote:
> Thanks again for the reply.
>
> When I do the .xinitrc change and run startx, I get the problem again.
> If I do startx without the .xinitrc, then do the "exec ck.." bit from
> a xterm, I also get the problem. But if I do startx and then run
> plasmashell from an xterm, it's all ok.
>
> Any more clues?
>
> Thanks,
>
> Graham
>
> On 15/12/19 8:40 pm, Tobias C. Berner wrote:
>> Moin moin
>>
>> Correct; You can check the pkg-message of plasma5-plasma-workspace on
>> how to start it directly:
>> Create a ~/.xinitrc with the following content:
>> exec ck-launch-session startplasma-x11
>>
>> Then use 'startx' to start X.
>>
>> As a side-note, can you make sure, that all your installed software is
>> up-to-date?
>>
>> mfg Tobias
>>
>> On Sun, 15 Dec 2019 at 09:54, Graham Menhennitt
>> <graham at menhennitt.com.au> wrote:
>>> Thanks for replying, Tobias.
>>>
>>> I'm not sure that I know how to do that. A bit of googling suggests
>>> running startx from the console and then running plasmashell from an
>>> xterm.
>>>
>>> When I do that, I get a good working desktop. I don't get the KDE
>>> window
>>> manager though - I get my twm from startx.
>>>
>>> Is that what you meant? If so, and since the desktop looks good, what's
>>> my next step to getting back to sddm?
>>>
>>> Thanks again,
>>>
>>> Graham
>>>
>>> On 15/12/19 5:42 pm, Tobias C. Berner wrote:
>>>> Moin moin
>>>>
>>>> does it work properly if you start plasma desktop via startx
>>>> instead of sddm?
>>>>
>>>>
>>>> mfg Tobias
>>>>
>>>> On Sun, 15 Dec 2019 at 03:00, Graham Menhennitt
>>>> <graham at menhennitt.com.au> wrote:
>>>>> It turns out that the problem I described below was due to the
>>>>> wrong NVidia driver being loaded. It appears that I now need to
>>>>> use the -390 version rather than the default -440 version. So now
>>>>> sddm-greeter doesn't crash and I get the login screen correctly.
>>>>>
>>>>> But after I login, the screen goes crazy. I get a bunch of
>>>>> horizontal white lines appearing which make it seem like I'm
>>>>> looking out a window through venetian blinds. I can make out the
>>>>> icons for some of the programs that are running (Firefox etc.) but
>>>>> it's effective unusable.
>>>>>
>>>>> My video card is a GeForce GT 730. And I'm running 12-Stable on
>>>>> AMD64.
>>>>>
>>>>> Do I now need an Xorg.conf perhaps?
>>>>>
>>>>> Does anybody have any ideas, please?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Graham
>>>>>
>>>>>
>>>>> On 11/12/19 10:28 pm, Graham Menhennitt wrote:
>>>>>
>>>>> Following up myself...
>>>>>
>>>>> Some time after the screen goes blank (about 10 seconds), I get a
>>>>> message logged:
>>>>>
>>>>> pid 1178 (sddm-greeter), jid 0, uid 219: exited on signal 6
>>>>> (core dumped)
>>>>>
>>>>> When I run lldb with sddm-greeter and the core file, I get the
>>>>> following stack backtrace. Does that help?
>>>>>
>>>>> In the meantime, I'll try building Qt with debug symbols.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Graham
>>>>>
>>>>> * thread #1, name = 'sddm-greeter', stop reason = signal SIGABRT
>>>>> * frame #0: 0x0000000801c3b86a libc.so.7`__sys_thr_kill at
>>>>> thr_kill.S:3
>>>>> frame #1: 0x0000000801c39c94 libc.so.7`__raise(s=6) at
>>>>> raise.c:52:10
>>>>> frame #2: 0x0000000801badf09 libc.so.7`abort at abort.c:67:8
>>>>> frame #3: 0x0000000801655919
>>>>> libQt5Core.so.5`___lldb_unnamed_symbol156$$libQt5Core.so.5 + 9
>>>>> frame #4: 0x0000000801656f7e
>>>>> libQt5Core.so.5`QMessageLogger::fatal(char const*, ...) const + 202
>>>>> frame #5: 0x0000000800527e99
>>>>> libQt5Quick.so.5`QSGRenderLoop::handleContextCreationFailure(QQuickWindow*,
>>>>> bool) + 297
>>>>> frame #6: 0x0000000800528539
>>>>> libQt5Quick.so.5`___lldb_unnamed_symbol2048$$libQt5Quick.so.5 + 505
>>>>> frame #7: 0x0000000800528cf8
>>>>> libQt5Quick.so.5`___lldb_unnamed_symbol2049$$libQt5Quick.so.5 + 72
>>>>> frame #8: 0x000000080104b21b
>>>>> libQt5Gui.so.5`QWindow::event(QEvent*) + 907
>>>>> frame #9: 0x000000080059dd5e
>>>>> libQt5Quick.so.5`QQuickWindow::event(QEvent*) + 814
>>>>> frame #10: 0x0000000801839842
>>>>> libQt5Core.so.5`QCoreApplicationPrivate::notify_helper(QObject*,
>>>>> QEvent*) + 338
>>>>> frame #11: 0x0000000801839362
>>>>> libQt5Core.so.5`QCoreApplication::notifyInternal2(QObject*,
>>>>> QEvent*) + 210
>>>>> frame #12: 0x000000080103ebcc
>>>>> libQt5Gui.so.5`QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
>>>>> + 332
>>>>> frame #13: 0x0000000801020afc
>>>>> libQt5Gui.so.5`QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>> + 220
>>>>> frame #14: 0x00000008055b58bf
>>>>> libQt5XcbQpa.so.5`___lldb_unnamed_symbol344$$libQt5XcbQpa.so.5 + 31
>>>>> frame #15: 0x00000008029483c7
>>>>> libglib-2.0.so.0`g_main_context_dispatch + 311
>>>>> frame #16: 0x0000000802948753
>>>>> libglib-2.0.so.0`___lldb_unnamed_symbol117$$libglib-2.0.so.0 + 515
>>>>> frame #17: 0x0000000802948804
>>>>> libglib-2.0.so.0`g_main_context_iteration + 100
>>>>> frame #18: 0x0000000801891e06
>>>>> libQt5Core.so.5`QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>> + 102
>>>>> frame #19: 0x0000000801834a0e
>>>>> libQt5Core.so.5`QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
>>>>> + 494
>>>>> frame #20: 0x0000000801839ace
>>>>> libQt5Core.so.5`QCoreApplication::exec() + 142
>>>>> frame #21: 0x00000000002696a4
>>>>> sddm-greeter`___lldb_unnamed_symbol211$$sddm-greeter + 996
>>>>> frame #22: 0x000000000025510f
>>>>> sddm-greeter`___lldb_unnamed_symbol1$$sddm-greeter + 271
>>>>>
>>>>>
>>>>> On 11/12/19 6:39 pm, Graham Menhennitt wrote:
>>>>>
>>>>> Hello all,
>>>>>
>>>>> I'm running KDE on FreeBSD 12-Stable as of last week. I rebuilt
>>>>> all of my ports and now I can't get sddm to start properly. When
>>>>> it starts, my display switches to vt 9 and all I see is an empty
>>>>> screen. I've uninstalled, rebuilt, and reinstalled the port.
>>>>>
>>>>> If I stop sddm and run startx, I correctly get a few xterms so I
>>>>> think the X side of things is working correctly.
>>>>>
>>>>> Below is a session from sddm.log.
>>>>>
>>>>> Does anybody have any clues, please?
>>>>>
>>>>> Thanks in advance for any help,
>>>>>
>>>>> Graham
>>>>>
>>>>>
>>>>> On starting with "service sddm onestart":
>>>>>
>>>>> [18:11:50.940] (II) DAEMON: No session manager found
>>>>>
>>>>> [18:11:50.940] (II) DAEMON: Adding new display on vt 9 ...
>>>>> [18:11:50.941] (II) DAEMON: Loading theme configuration from ""
>>>>> [18:11:50.941] (II) DAEMON: Display server starting...
>>>>> [18:11:50.941] (II) DAEMON: Running: /usr/local/bin/X -nolisten
>>>>> tcp -auth /var/run/sddm/{96b45809-91c0-4a86-8533-01e4ef2920f9}
>>>>> -background none -noreset -displayfd 11 -seat seat0 vt9
>>>>> [18:11:51.629] (II) DAEMON: Setting default cursor
>>>>> [18:11:51.631] (WW) DAEMON: Could not setup default cursor
>>>>> [18:11:51.631] (II) DAEMON: Running display setup script
>>>>> "/usr/local/share/sddm/scripts/Xsetup"
>>>>> [18:11:51.633] (II) DAEMON: Display server started.
>>>>> [18:11:51.633] (II) DAEMON: Socket server starting...
>>>>> [18:11:51.633] (II) DAEMON: Socket server started.
>>>>> [18:11:51.633] (II) DAEMON: Loading theme configuration from
>>>>> "/usr/local/share/sddm/themes/breeze/theme.conf"
>>>>> [18:11:51.633] (II) DAEMON: Greeter starting...
>>>>> [18:11:51.634] (II) DAEMON: Adding cookie to
>>>>> "/var/run/sddm/{96b45809-91c0-4a86-8533-01e4ef2920f9}"
>>>>> [18:11:51.637] (II) DAEMON: Starting...
>>>>> [18:11:51.641] (II) HELPER: [PAM] Starting...
>>>>> [18:11:51.641] (II) HELPER: [PAM] Authenticating...
>>>>> [18:11:51.641] (II) HELPER: [PAM] returning.
>>>>> [18:11:51.641] (II) HELPER: Starting:
>>>>> "/usr/local/share/sddm/scripts/Xsession
>>>>> /usr/local/bin/sddm-greeter --socket /tmp/sddm-:0-TFJyQI --theme
>>>>> /usr/local/share/sddm/themes/breeze"
>>>>> [18:11:51.643] (II) DAEMON: Greeter session started successfully
>>>>> [18:11:51.924] (II) DAEMON: Message received from greeter: Connect
>>>>> [18:12:00.558] (II) HELPER: [PAM] Closing session
>>>>> [18:12:00.558] (II) HELPER: [PAM] Ended.
>>>>> [18:12:00.559] (II) DAEMON: Auth: sddm-helper exited successfully
>>>>>
>>>>> [18:12:00.559] (II) DAEMON: Greeter stopped.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> And when I stop it using "service sddm stop":
>>>>>
>>>>> [18:22:58.038] (WW) DAEMON: Signal received: SIGTERM
>>>>> [18:22:58.038] (II) DAEMON: Socket server stopping...
>>>>> [18:22:58.038] (II) DAEMON: Socket server stopped.
>>>>> [18:22:58.039] (II) DAEMON: Display server stopping...
>>>>> [18:22:58.059] (II) DAEMON: Display server stopped.
>>>>> [18:22:58.059] (II) DAEMON: Running display stop script
>>>>> "/usr/local/share/sddm/scripts/Xstop"
>>>>>
>>>>>
>
More information about the kde-freebsd
mailing list