http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 Sebastian Kuhne changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Basesystem -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 Sebastian Kuhne changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Community User -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c1 Sebastian Kuhne changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Sebastian Kuhne --- Many thanks for fixing that with Tumbleweed 20180812! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c3 Frank Kruger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger@mailbox.org --- Comment #3 from Frank Kruger --- (In reply to Sebastian Kuhne from comment #2)

With Tumbleweed 20180818 the same issue again, unfortunately.

This has been also reported in mailing list "opensuse-factory": https://lists.opensuse.org/opensuse-factory/2018-08/msg00220.html

If there is a hint how to solve that manually - please advise.

Best regards Sebastian

I do not experience the above-mentioned issue with TW20180818 and KDE-Plasma 5.13.4. Anyway, does "zypper in -f gsettings-desktop-schemas" solve your problem? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c5 --- Comment #5 from Frank Kruger --- (In reply to Sebastian Kuhne from comment #4)

Many thanks, Frank, for your reply. Indeed, that works for me! I just did the "zypper in" as you suggested but I haven't checked before what was installed originally. Not sure what is the actual root cause - I did the update via "zypper dup" as known to the Tumbleweed users. However, closing this issue based on your help.

Best regards Sebastian

I am glad to hear that it solved your problem. The question of the reason for this issue still remains. Do you have additional repos enabled? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 Frank Kruger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c8 Craig Andersen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ace6zip@gmail.com --- Comment #8 from Craig Andersen --- Prior to the workaround yesterday the following was observed, may be already reported. Firefox and Chrome were crashing, at the same place in glib library. Aug 21 15:31:25 hydrax kernel: traps: firefox[5674] trap int3 ip:7f4d4ff31d35 sp:7ffc77641520 error:0 in libglib-2.0.so.0.5600.1[7f4d4fedd000+116000] Aug 21 15:31:25 hydrax systemd-coredump[5687]: Process 5674 (firefox) of user 1002 dumped core. Aug 21 14:42:45 hydrax kernel: traps: chrome[2781] trap int3 ip:7fbfd4db5d35 sp:7fff8ddbe060 error:0 in libglib-2.0.so.0.5600.1[7fbfd4d61000+116000] Aug 21 14:42:45 hydrax systemd-coredump[2798]: Resource limits disable core dumping for process 2781 (chrome). I believe skype was having issues also since it was not in the tray. During this time my system log was being filled with large amounts of the following which I could not prove to be correlated. Aug 21 15:33:35 hydrax plasmashell[6611]: QPainter::setOpacity: Painter not active Aug 21 15:33:35 hydrax plasmashell[6611]: QPainter::setWorldTransform: Painter not active Aug 21 15:33:35 hydrax plasmashell[6611]: QPainter::restore: Unbalanced save/restore Aug 21 15:33:35 hydrax plasmashell[6611]: QPainter::end: Painter not active, aborted -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c10 --- Comment #10 from Frank Kruger --- (In reply to Sebastian Kuhne from comment #9)

Thanks for reopening.

Maybe another hint: Also LibreOffice didn't work. The only browser working was Konqueror. So, it seems to be an issue with non-KDE software or with GTK software?

Also one more thing, assuming that gsettings-desktop-schemas was installed already (is this right?), the proposed -f option did force an update. So, if I am not totally wrong, the actual issue could be that zypper dup did not update gsettings-desktop-schemas properly, and we had to force the update manually.

Is that the issue we should focus on?

Frank, another question I have: Why did you know that zypper in -f gsettings-desktop-schemas could be the workaround?

It was just a guess. In fact, since gsettings-desktop-schemas is installed on my system with KDE Plasma and given the error message “No GSettings schemas are installed on the system“ it could well be that the corresponding path was not set/updated properly. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c12 --- Comment #12 from Frank Kruger --- (In reply to Sebastian Kuhne from comment #11)

After the update to TW 20180829 the same issue appeared again. Only "zypper in -f gsettings-desktop-schemas" did solve the issue.

Is there someone which could fix that?

Since I am a mere user, we have to wait for the maintainer/developer to step in. For the time being, however, could you i) force to reinstall the gtk2-/gtk3-packages that were updated with TW20180829; ii) provide "echo $XDG_DATA_DIRS"; iii) if the issue appears, please apply the above-mentioned workaround and provide "echo $XDG_DATA_DIRS" again. Thx. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c14 --- Comment #14 from Sebastian Kuhne --- (In reply to Sebastian Kuhne from comment #13)

(In reply to Frank Kruger from comment #12)

...

(In reply to Sebastian Kuhne from comment #11)

...

After the update to TW 20180829 the same issue appeared again. Only "zypper in -f gsettings-desktop-schemas" did solve the issue.

Is there someone which could fix that?

Since I am a mere user, we have to wait for the maintainer/developer to step in. For the time being, however, could you i) force to reinstall the gtk2-/gtk3-packages that were updated with TW20180829; ii) provide "echo $XDG_DATA_DIRS"; iii) if the issue appears, please apply the above-mentioned workaround and provide "echo $XDG_DATA_DIRS" again. Thx.

Many thanks, and i) and ii) done according to your indication.

Output: see Attachment

The output is exactly the same before and after forcing to reinstall the gtk2-/gtk3-packages.(In reply to Frank Kruger from comment #12)

...

(In reply to Sebastian Kuhne from comment #11)

...

After the update to TW 20180829 the same issue appeared again. Only "zypper in -f gsettings-desktop-schemas" did solve the issue.

Is there someone which could fix that?

Since I am a mere user, we have to wait for the maintainer/developer to step in. For the time being, however, could you i) force to reinstall the gtk2-/gtk3-packages that were updated with TW20180829; ii) provide "echo $XDG_DATA_DIRS"; iii) if the issue appears, please apply the above-mentioned workaround and provide "echo $XDG_DATA_DIRS" again. Thx.

Many thanks - and i) and ii) done according to our indication.

Output: See attachment.

The output was exactly the same before and after forcing to reinstall the gtk2-/gtk3-packages.

Attachments don't work - so here is the output: /home/sebastian/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c16 --- Comment #16 from Sebastian Kuhne --- (In reply to Frank Kruger from comment #15)

(In reply to Sebastian Kuhne from comment #14)

...

Attachments don't work - so here is the output: /home/sebastian/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/ share:/usr/local/share:/usr/share

So, the $XDG_DATA_DIRSis set correctly. Do you have as user any other special environment variables set? The issue does not appear as root, right?

No, I don't have any other special environment variables set. All is set as given by the standard installation. The issue appears only as standard user, as root I can start the applications. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1103835 http://bugzilla.opensuse.org/show_bug.cgi?id=1103835#c18 --- Comment #18 from Sebastian Kuhne --- Same issue again after update to TW20181001. Is there anyone of the developers could looking after this please? -- You are receiving this mail because: You are on the CC list for the bug.