SDDM problems

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

SDDM problems

Anton Aylward-2
Well actually it is KDM problems.
KDM seems to need KDE4.  See the thread on KDE4/Qt4 removal.
Well the KDM I have needs KDE4.
Even though I'm using "5" or KF5 as much as possible.
But KDM seems problematic.
maybe its a repository problems.

The basic OS is 42.3.

Along the way I keep trying to use SDDM instead, but despite library updates and
SDDM updates I hit the same problem

The login screen comes up with my name there asking for password.  But if I
adjust anything, try altering any of the pull-downs or try typing in the
password everything freezes.  Nothing work, no way to input or delete or
pull-down.  Cursor moves but nothing works.  no way to log in. NOTHING.

I have to go to a VT term and change /etc/sysconfig/display to lightdm or xdm
and reboot.

Looking that the processes on the hot-keyed VT: no SDDM isn't in a spin loop,
its just frozen.

Frustrating as I don't even know what to look for next.
Why shouldn't it work?
I can imagine kedeinit failing and bumping back to the login manager, but this
isn't that.  It SDDM *freezing*.

Suggestions?
--
Ah, nostalgia ain't what it used to be.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Carlos E. R.-2
On 30/03/2019 02.14, Anton Aylward wrote:
> Well actually it is KDM problems.
> KDM seems to need KDE4.  See the thread on KDE4/Qt4 removal.
> Well the KDM I have needs KDE4.
> Even though I'm using "5" or KF5 as much as possible.
> But KDM seems problematic.
> maybe its a repository problems.

That means you load two set of libraries.

But there is no KDE4 removal in Leap 42.x, nor on 15.0/15.1, you can
keep using KDM.

> The basic OS is 42.3.
>
> Along the way I keep trying to use SDDM instead, but despite library updates and
> SDDM updates I hit the same problem
>
> The login screen comes up with my name there asking for password.  But if I
> adjust anything, try altering any of the pull-downs or try typing in the
> password everything freezes.  Nothing work, no way to input or delete or
> pull-down.  Cursor moves but nothing works.  no way to log in. NOTHING.
>
> I have to go to a VT term and change /etc/sysconfig/display to lightdm or xdm
> and reboot.
This doesn't work in 15.0, remember. May still work in 42.3.


> Looking that the processes on the hot-keyed VT: no SDDM isn't in a spin loop,
> its just frozen.
>
> Frustrating as I don't even know what to look for next.
> Why shouldn't it work?
> I can imagine kedeinit failing and bumping back to the login manager, but this
> isn't that.  It SDDM *freezing*.
>
> Suggestions?

Dunno. I'm using sddm on 15.0, no problems so far.


--
Cheers / Saludos,

                Carlos E. R.
                (from 15.0 x86_64 at Telcontar)


signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Anton Aylward-2
On 3/30/19 9:39 AM, Carlos E. R. wrote:

> On 30/03/2019 02.14, Anton Aylward wrote:
>> Well actually it is KDM problems.
>> KDM seems to need KDE4.  See the thread on KDE4/Qt4 removal.
>> Well the KDM I have needs KDE4.
>> Even though I'm using "5" or KF5 as much as possible.
>> But KDM seems problematic.
>> maybe its a repository problems.
>
> That means you load two set of libraries.
>
> But there is no KDE4 removal in Leap 42.x, nor on 15.0/15.1, you can
> keep using KDM.

Yes.
To some degree that's the problem with incremental upgrades rathe than a
clean-sheet install, isn't it?

But I seem to have now go so far into using KF5 that a lot of previous stuff is
broken.  And a lot of "5" stuff isn't working right.

=================
anton@main:~> k3b
k3b: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
(required by /usr/lib64/libKF5Declarative.so.5)
==================




>> The basic OS is 42.3.
>>
>> Along the way I keep trying to use SDDM instead, but despite library updates and
>> SDDM updates I hit the same problem
>>
>> The login screen comes up with my name there asking for password.  But if I
>> adjust anything, try altering any of the pull-downs or try typing in the
>> password everything freezes.  Nothing work, no way to input or delete or
>> pull-down.  Cursor moves but nothing works.  no way to log in. NOTHING.
>>
>> I have to go to a VT term and change /etc/sysconfig/display to lightdm or xdm
>> and reboot.
>
> This doesn't work in 15.0, remember. May still work in 42.3.

Yes, I've read the "15" release notes about that. The 'update-alternatives' stuff.

>> Looking that the processes on the hot-keyed VT: no SDDM isn't in a spin loop,
>> its just frozen.
>>
>> Frustrating as I don't even know what to look for next.
>> Why shouldn't it work?

I'm trying myself in knots.


>> I can imagine kedeinit failing and bumping back to the login manager, but this
>> isn't that.  It SDDM *freezing*.
>>
>> Suggestions?
>
> Dunno. I'm using sddm on 15.0, no problems so far.

Yes, but why shouldn't SDDM work on 42.3?


--
We know nothing about motivation. All we can do is write books about it.
   --Peter F. Drucker
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Carlos E. R.-2
On 30/03/2019 14.58, Anton Aylward wrote:

> On 3/30/19 9:39 AM, Carlos E. R. wrote:
>> On 30/03/2019 02.14, Anton Aylward wrote:
>>> Well actually it is KDM problems.
>>> KDM seems to need KDE4.  See the thread on KDE4/Qt4 removal.
>>> Well the KDM I have needs KDE4.
>>> Even though I'm using "5" or KF5 as much as possible.
>>> But KDM seems problematic.
>>> maybe its a repository problems.
>>
>> That means you load two set of libraries.
>>
>> But there is no KDE4 removal in Leap 42.x, nor on 15.0/15.1, you can
>> keep using KDM.
>
> Yes.
> To some degree that's the problem with incremental upgrades rathe than a
> clean-sheet install, isn't it?
>
> But I seem to have now go so far into using KF5 that a lot of previous stuff is
> broken.  And a lot of "5" stuff isn't working right.
>
> =================
> anton@main:~> k3b
> k3b: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
> (required by /usr/lib64/libKF5Declarative.so.5)
> ==================
>
>
>
>
>>> The basic OS is 42.3.
>>>
>>> Along the way I keep trying to use SDDM instead, but despite library updates and
>>> SDDM updates I hit the same problem
>>>
>>> The login screen comes up with my name there asking for password.  But if I
>>> adjust anything, try altering any of the pull-downs or try typing in the
>>> password everything freezes.  Nothing work, no way to input or delete or
>>> pull-down.  Cursor moves but nothing works.  no way to log in. NOTHING.
>>>
>>> I have to go to a VT term and change /etc/sysconfig/display to lightdm or xdm
>>> and reboot.
>>
>> This doesn't work in 15.0, remember. May still work in 42.3.
>
> Yes, I've read the "15" release notes about that. The 'update-alternatives' stuff.
>
>>> Looking that the processes on the hot-keyed VT: no SDDM isn't in a spin loop,
>>> its just frozen.
>>>
>>> Frustrating as I don't even know what to look for next.
>>> Why shouldn't it work?
>
> I'm trying myself in knots.
>
>
>>> I can imagine kedeinit failing and bumping back to the login manager, but this
>>> isn't that.  It SDDM *freezing*.
>>>
>>> Suggestions?
>>
>> Dunno. I'm using sddm on 15.0, no problems so far.
>
> Yes, but why shouldn't SDDM work on 42.3?

Pure 42.3, or some concoction?  :-)

Because 42.3 does not do incremental upgrades, nor does it has problems
with kdm. :-?


--
Cheers / Saludos,

                Carlos E. R.
                (from 15.0 x86_64 at Telcontar)


signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Anton Aylward-2
On 3/30/19 10:08 AM, Carlos E. R. wrote:
>
> Pure 42.3, or some concoction?  :-)
>
> Because 42.3 does not do incremental upgrades, nor does it has problems
> with kdm. :-?

Nor did I until I started clearing out the KDE4 stuff and reprioritizing the
KDF5 repositories.

--
When one find's oneself in a hole of one's own making, it is a good time to
examine the quality of the workmanship.
    --John Renmerde
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Wolfgang Bauer
In reply to this post by Anton Aylward-2
Am Samstag, 30. März 2019, 09:58:28 schrieb Anton Aylward:
> But I seem to have now go so far into using KF5 that a lot of previous stuff
> is broken.  And a lot of "5" stuff isn't working right.
>
> =================
> anton@main:~> k3b
> k3b: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
> (required by /usr/lib64/libKF5Declarative.so.5)
> ==================

You obviously mix incompatible packages from different repos.

To upgrade to the latest Qt5/KF5 versions on Leap, you need these three repos:
KDE:Qt5
KDE:Frameworks5
KDE:Applications

And you need to do a full switch to each of them.
Either use "Switch system packages to the versions in this repo" in YaST (it
does have a text mode interface as well, but I don't know if that actually has
that option), or run something like "zypper dup --from KDE:Qt5 --from
KDE:Frameworks5 --from KDE:Applications" (the actual command depends on how
your repos are named, post the output of "zypper lr -d" for further help).

>
> >> The basic OS is 42.3.
> >> ...
> >> > >> I have to go to a VT term and change /etc/sysconfig/display to
lightdm or
> >> xdm and reboot.
> >
> > This doesn't work in 15.0, remember. May still work in 42.3.

It does indeed still (and only) work that way in 42.3.

> > Dunno. I'm using sddm on 15.0, no problems so far.
>
> Yes, but why shouldn't SDDM work on 42.3?

It certainly does work in general, actually it's used as default (in a KDE
installation at least) since 42.1 already.

Maybe some kind of graphics driver problem (SDDM uses/needs OpenGL, due to its
dependence on QML) or similar. If you're using intel, maybe try to uninstall
xf86-video-intel if it's installed (and try the generic modesetting driver),
or install it if not. Similar things can be tried with other drivers as well
(i.e. uninstall or install xf86-video-ati/xf86-video-nouveau, in the latter
case you could also try to install/uninstall Mesa-dri-nouveau that contains
the 3D/OpenGL part or the proprietary nvidia driver of course)

OTOH, 42.3 is nearly out of support anyway, it will be EOL at the end of this
month IIRC.
I would also suggest sticking to KDM for now, at least while you are still
using 42.3.

Btw, there was a somehow similar bug report recently:
https://bugzilla.opensuse.org/show_bug.cgi?id=1131073
There it was caused by not having xf86-input-evdev installed, but that would
likely affect KDM as well I think.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Anton Aylward-2
On 2019-04-01 6:20 a.m., Wolfgang Bauer wrote:

> Am Samstag, 30. März 2019, 09:58:28 schrieb Anton Aylward:
>> But I seem to have now go so far into using KF5 that a lot of previous stuff
>> is broken.  And a lot of "5" stuff isn't working right.
>>
>> =================
>> anton@main:~> k3b
>> k3b: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
>> (required by /usr/lib64/libKF5Declarative.so.5)
>> ==================
>
> You obviously mix incompatible packages from different repos.
>
> To upgrade to the latest Qt5/KF5 versions on Leap, you need these three repos:
> KDE:Qt5
> KDE:Frameworks5
> KDE:Applications
>
> And you need to do a full switch to each of them.
> Either use "Switch system packages to the versions in this repo" in YaST

Yes, I've done that, and that was where I was coming from sta the start of this
and it gets screwed up.
Many applications fail, mostly for this reason:


anton@main:> kpat
kpat: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
(required by /usr/lib64/libKF5Declarative.so.5)

Please don't think I'm hung op on games; I just use this as a very simple
illustration of my point.  Tis is so common it is frustrating and I haven't the
faintest clue how to deal with it.

Perhaps I should count myself lucky that the GTK applications like Thunderbird
and Firefox don't suffer from KDE5 crippling.

I'm retry using SDDM shortly.
--
Capitalism is the astounding belief that the most wickedest of men will
do the most wickedest of things for the greatest good of everyone.
    --John Maynard Keynes
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Anton Aylward-2
On 2019-04-23 8:36 a.m., Anton Aylward wrote:

> On 2019-04-01 6:20 a.m., Wolfgang Bauer wrote:
>> Am Samstag, 30. März 2019, 09:58:28 schrieb Anton Aylward:
>>> But I seem to have now go so far into using KF5 that a lot of previous stuff
>>> is broken.  And a lot of "5" stuff isn't working right.
>>>
>>> =================
>>> anton@main:~> k3b
>>> k3b: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
>>> (required by /usr/lib64/libKF5Declarative.so.5)
>>> ==================
>>
>> You obviously mix incompatible packages from different repos.
>>
>> To upgrade to the latest Qt5/KF5 versions on Leap, you need these three repos:
>> KDE:Qt5
>> KDE:Frameworks5
>> KDE:Applications
>>
>> And you need to do a full switch to each of them.
>> Either use "Switch system packages to the versions in this repo" in YaST
>
> Yes, I've done that, and that was where I was coming from sta the start of this
> and it gets screwed up.
> Many applications fail, mostly for this reason:
>
>
> anton@main:> kpat
> kpat: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
> (required by /usr/lib64/libKF5Declarative.so.5)
>
> Please don't think I'm hung op on games; I just use this as a very simple
> illustration of my point.  Tis is so common it is frustrating and I haven't the
> faintest clue how to deal with it.
>
> Perhaps I should count myself lucky that the GTK applications like Thunderbird
> and Firefox don't suffer from KDE5 crippling.
>
> I'm retry using SDDM shortly.
>

More on same:  Now I can't use Dolphin
> dolphin
kf5.kservice.sycoca: The service type config file
"kservicetypes5/kmymoney-nationalaccountnumberplugin.desktop"  does not contain
a ServiceType=... entry
kf5.kservice.sycoca: Parse error in
"/home/anton/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" ,
line  1 , col  1 :  "unexpected end of file"
kf5.kio.core: couldn't create slave: "klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/tags.so'."
kf5.kio.core: "Unable to create io-slave. klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/tags.so'."
kf5.kio.core: couldn't create slave: "klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/trash.so'."
kf5.kio.core: "Unable to create io-slave. klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/trash.so'."
kf5.kio.core: couldn't create slave: "klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/file.so'."
kf5.kio.core: couldn't create slave: "klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/file.so'."
kf5.kio.core: couldn't create slave: "klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/file.so'."






--
The Internet is full of cats, because dog people go outside!
        -- Peter Hillier 08/27/2013
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Wolfgang Bauer
In reply to this post by Anton Aylward-2
Am Dienstag, 23. April 2019, 08:36:55 schrieb Anton Aylward:

> On 2019-04-01 6:20 a.m., Wolfgang Bauer wrote:
> > To upgrade to the latest Qt5/KF5 versions on Leap, you need these three
> > repos: KDE:Qt5
> > KDE:Frameworks5
> > KDE:Applications
> >
> > And you need to do a full switch to each of them.
> > Either use "Switch system packages to the versions in this repo" in YaST
>
> Yes, I've done that, and that was where I was coming from sta the start of
> this and it gets screwed up.

No you didn't, at least not properly.

As your error message clearly shows:
> Many applications fail, mostly for this reason:
>
>
> anton@main:> kpat
> kpat: /usr/lib64/libQt5Core.so.5: version `Qt_5.6.2_PRIVATE_API' not found
> (required by /usr/lib64/libKF5Declarative.so.5)

That means that you have the old libKF5Declarative5 5.32.0 package from the
standard 42.3 repos that is compiled with (and requires) Qt 5.6.2, and *not*
the latest one from KDE:Frameworks5.

Actually you need to have told YaST/zypper to ignore dependencies ("break
XXX...") to end up with this error message, as the package does require Qt =
5.6.2 on a package level.

So do an explicit switch again.
And in case you get a conflict, better ask for further help.

> Perhaps I should count myself lucky that the GTK applications like
> Thunderbird and Firefox don't suffer from KDE5 crippling.

GTK applications usually don't use Qt or KDE libraries...

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Anton Aylward-2
On 2019-04-24 4:20 a.m., Wolfgang Bauer wrote:
> So do an explicit switch again.

OK did that, *all* *three* of the mentioned repositories are 'switched to
system'.  That's what I was missing/wasn't clear about.
Now the regular applications mentioned don't produce that error.

I wonder if the same could have been achieved by altering the priories of the
repositories?


I still have to test out SDDM at login time :-?

>
>> Perhaps I should count myself lucky that the GTK applications like
>> Thunderbird and Firefox don't suffer from KDE5 crippling.
>
> GTK applications usually don't use Qt or KDE libraries...

Isn't diversity wonderful!




--
"To be conscious of one's ignorance is the beginning of wisdom".
  -- Sri Ram
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SDDM problems

Wolfgang Bauer
Am Mittwoch, 24. April 2019, 06:30:35 schrieb Anton Aylward:
> On 2019-04-24 4:20 a.m., Wolfgang Bauer wrote:
> > So do an explicit switch again.
>
> OK did that, *all* *three* of the mentioned repositories are 'switched to
> system'.  That's what I was missing/wasn't clear about.

Well, I did write "And you need to do a full switch to each of them." in my
original reply though... ;-)

> I wonder if the same could have been achieved by altering the priories of
> the repositories?

The repo priorities only affect installation of new packages, changing them
will have no effect on what packages are currently installed.
You'd still have to switch them manually.

In this case, giving the repos higher priority isn't really necessary though,
as the packages do have a higher version anyway (that's the whole point of
adding these repos in the first place, isn't it?).

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]