openSUSE LEAP 42.3 KDE - Oyranos-compat-gnome segfault entry in dmesg

3toedsloth · August 18, 2017, 3:54am

Hi all,

I’m requesting help regarding a clean install of openSUSE LEAP 42.3 KDE in which I installed kolor-manager so that my monitor can properly utilize its colour profile. kolor-manager has various Oyranos dependancies and one of them is causing a segfault message in dmesg:

   59.037179] oyranos-compat-[2283]: segfault at 0 ip           (null) sp 00007fff794fc678 error 14 in oyranos-compat-gnome[400000+3000]

The colour correction is working properly and everything else seems to work but I’d also like to find out the cause of the segfault.

Thanks in advance.

3toedsloth · August 24, 2017, 10:53pm

Hi all,

Thought I would reply with what I think is a better solution. Instead of kolor-manager,

zypper install colord-kde

this will place a module in System Settings > Hardware > Color Corrections where you can load your profile. You can also install, if you wish, gnome-color-manager which will let you calibrate your monitor if you have an appropriate calibration device.

As an aside, I think this should be included in the default openSUSE LEAP KDE install, then it would have the same “out of box” monitor color calibration as the Gnome desktop but now I know and maybe this will help some other people.

Cheers.

dcurtisfra · August 25, 2017, 10:32am

“kolor-manager” is a KDE4 Plasma application – with a normal user’s CLI use “zypper info --requires kolor-manager” to notice that “kdebase4-runtime >= 4.14.0” is required.

“kolor-manager” is not a KDE Plasma 5 (KF5) application . . .

[HR][/HR]Yes, “colord-kde” (the KDE front end to “colord”) is a KF5 application – “requires”: ‘libKF5Service.so.5()(64bit)’ for example.

Thanks for the hint: I was about to re-investigate the KDE Colour Management world for KF5 – up until now I’ve been manually adjusting the colour balance in the System Settings “Monitor Gamma settings”.

3toedsloth · August 25, 2017, 8:23pm

Thanks for the reply and info. When I run:

jack@linux-umu3:~> zypper info --requires kolor-manager
Loading repository data...
Reading installed packages...


Information for package kolor-manager:
--------------------------------------
Repository     : openSUSE-Leap-42.3-Oss            
Name           : kolor-manager                     
Version        : 1.1.0-1.1                         
Arch           : x86_64                            
Vendor         : openSUSE                          
Installed Size : 106.2 KiB                         
Installed      : No                                
Status         : not installed                     
Source package : kolor-manager-1.1.0-1.1.src       
Summary        : Colour Management Frontend for KDE
Description    :                                   
    The KDE5 systemsettings modules provide cross desktop Oyranos Color Management System settings.
Requires       : [20]                              
    libc.so.6()(64bit)
    libc.so.6(GLIBC_2.2.5)(64bit)
    libstdc++.so.6()(64bit)
    libstdc++.so.6(GLIBCXX_3.4)(64bit)
    libstdc++.so.6(CXXABI_1.3)(64bit)
    libQt5Core.so.5()(64bit)
    libQt5Core.so.5(Qt_5)(64bit)
    libQt5Core.so.5(Qt_5.6)(64bit)
    libQt5Widgets.so.5()(64bit)
    libQt5Widgets.so.5(Qt_5)(64bit)
    libKF5CoreAddons.so.5()(64bit)
    libKF5I18n.so.5()(64bit)
    libKF5ConfigWidgets.so.5()(64bit)
    oyranos
    libOyranosCore.so.0()(64bit)
    icc-examin
    libOyranosSynnefo.so.1()(64bit)
    rpmlib(CompressedFileNames) <= 3.0.4-1
    rpmlib(PayloadFilesHavePrefix) <= 4.0-1
    rpmlib(PayloadIsLzma) <= 4.4.6-1

My requirements do not list “kdebase4-runtime >= 4.14.0”. Strange. Maybe I’m reading this wrong?

wolfi323 · August 26, 2017, 5:32pm

No, you read it correctly.
dcurtisfra is wrong, kolormanager has been ported to Qt5/KF5 in 42.3.

That’s unrelated to the crash (of oyranos-compat-gnome) anyway though, which you can just ignore (if everything is working) I suppose.

dcurtisfra · August 28, 2017, 9:57am

Oh! I was inspecting “kolor-manager” from this Leap 42.2 system plus the openSUSE Software URLs – missed that the version change from 1.0.2 to 1.1.0 included the KF5 port.
[HR][/HR]Whoever does things, occasionally breaks something . . .

ajohnw · August 28, 2017, 3:14pm

I’ve been having some problems with KDE5 colour management on 42.2. I use displaycal for calibration and found that after I installed it and oyranus that displaycalc was timing out when it informed the kde management about a new profile. Oyranus and the now user local settings went fine.

I fixed this by installing from development section of the web software search page by installing from wolfie’s repo. This caused some confusion as I had just installed a new monitor and had done a 2nd profile. Color Management in settings didn’t seem to retain the change it and the apply button was greyed out. Logging out of kde and back in picked up the correct one though.

My image editors were clearly using the correct profile but I had problems with some image viewers. Gwenview wasn’t using it so have switched to Ristretto. I still need to get that to retain it’s settings.

John

wolfi323 · August 28, 2017, 4:33pm

I wouldn’t recommend that, unless you install everything from my repo.

Better use the “official” version from multimedia:color_management.

But this thread is about 42.3, not 42.2, which comes with the latest version anyway.

ajohnw · August 29, 2017, 12:19am

I did try the official version and posted because anyone running 42.3 wouldn’t read the post I made about problems on 42.2. Just to warn about checking that image viewers are working correctly. I noticed because I happened to be working on fairly gaudy shot of a church window and noticed a significant drop in saturation which might also be down to an increase in brightness or some combination of the two. An odd problem to have.

John

user · April 22, 2018, 9:05pm

I keep getting the exact same segfault as the OP. It has been happening for quite some time.

Shouldn’t that be reported as a bug?

wolfi323 · April 23, 2018, 11:23am

And why do you even ask?
Report it if you think it should be fixed.

Personally I don’t care, as I don’t even have oyranos installed.

user · April 23, 2018, 12:55pm

Because I don’t want to report things which may be non-bugs

Report it if you think it should be fixed.

OK, I will.

wolfi323 · April 23, 2018, 3:48pm

A crash is a crash.

Whether it impacts you or not is a different question though, which you probably can only answer yourself anyway.

As I already wrote, I think it is “harmless” (i.e. it shouldn’t break anything), although systemd-coredump may slow down your system considerably while it creates the coredump.
(btw, systemd-coredump will be disabled by default in Leap 15 again…)

PS: Now that I come to think about it, oyranos may actually be the cause for at least one of the gwenview “bugs” you reported, I suppose… (probably not this crash though)

user · April 23, 2018, 5:52pm

I didn’t know that was a sign of a crash. Thanks for the info. Then I guess the bug report I filed was a good idea.

PS: Now that I come to think about it, oyranos may actually be the cause for at least one of the gwenview “bugs” you reported, I suppose… (probably not this crash though)

In case you mean the report about the non-color managed thumbs I am not so sure. I tried installing colord-kde instead but it didn’t change anything.

wolfi323 · April 23, 2018, 6:30pm

Yes, a segfault (access to an invalid memory location) causes a program to be terminated, i.e. it is a crash.

coredumpctl should list the crashes too, and should allow you to get a backtrace about the crash (which might be a good thing to add to the bug report).

In case you mean the report about the non-color managed thumbs I am not so sure. I tried installing colord-kde instead but it didn’t change anything.

Well, both are somehow related to color management IIRC, but the other one (about oversaturated thumbs) even more so I think.

user · April 23, 2018, 6:46pm

I have never heard about coredumpct until now. Reading the man page I see that there is a ‘dump’ command but I am afraid not to compromise the security of the system by sharing such info as I am really unaware of what this binary output contains.

wolfi323 · April 23, 2018, 7:08pm

Well, a dump contains a full memory image at the point when the application crashed.
Shouldn’t compromise your system’s security in this case though, as it contains only the application’s memory areas and I doubt that oyranos-compat-gnome will handle any sensitive data like passwords or so…

The backtrace would be more interesting though, as it shows where it crashed in the code.
A full dump is normally only necessary if the crash is not reproducible and the backtrace doesn’t show enough information.

I.e. run “coredumpctl gdb xxx”, and then type “bt” to get the backtrace.

Or wait whether you are actually asked for a backtrace. If the crash happens on every login anyway, nobody needs a backtrace from your system to reproduce/investigate it.

malcolmlewis · April 23, 2018, 7:09pm

On Mon 23 Apr 2018 04:56:02 PM CDT, heyjoe wrote:

wolfi323;2863565 Wrote:
> coredumpctl should list the crashes too, and should allow you to get a
> backtrace about the crash (which might be a good thing to add to the
> bug report).
I have never heard about coredumpct until now. Reading the man page I
see that there is a ‘dump’ command but I am afraid not to compromise the
security of the system by sharing such info as I am really unaware of
what this binary output contains.

Hi
But you can see what it contains with coredumpctl dump <some_pid_from_list>?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3|GNOME 3.20.2|4.4.126-48-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

user · April 23, 2018, 7:16pm

Thanks wolfi!
BTW - amazing memory I wonder how you remember such old bug reports and form posts of mine.

wolfi323 · May 2, 2018, 7:48pm

Well, I got notifications when you reopened the bug reports and/or added comments because I am subscribed to the corresponding mailing lists.

I do have quite a good memory though, but I don’t always remember all details.