[Bug 1131761] New: searhorse won't start (after recent 'zypper up')

older
[Bug 1132458] jack_control crashes...

bugzilla_noreply＠novell.com

6 Apr 2019 6 Apr '19

20:52

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 Bug ID: 1131761 Summary: searhorse won't start (after recent 'zypper up') Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening@forge.provo.novell.com Reporter: forumino@riseup.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I am using KDE Plasma and seahorse has always worked. But now: [~]: seahorse (process:26265): GLib-GIO-ERROR **: No GSettings schemas are installed on the system Trace/breakpoint trap (core dumped) This has been happening since a 'zypper up' ran yesterday during which the following packages were updated: rawtherapee libMagickCore-7_Q16HDRI6 libcaca0 libgd3 libmspack0 libnettle6 libnettle6-32bit libopenssl1_1 libpackagekitqt5-0 libwavpack1 os-prober libMagickWand-7_Q16HDRI6 gd libhogweed4 libhogweed4-32bit openssl-1_1 ntp ImageMagick libnettle-devel libopenssl-1_1-devel transcode -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 2.7 KB)

Show replies by date

bugzilla_noreply＠novell.com

12 Apr 12 Apr

11:55

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 http://bugzilla.opensuse.org/show_bug.cgi?id=1131761#c1 Suse User changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Critical --- Comment #1 from Suse User --- Raising severity because the program doesn't start at all. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:02

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 http://bugzilla.opensuse.org/show_bug.cgi?id=1131761#c2 --- Comment #2 from Suse User --- The issue might be related to /usr/share/glib-2.0/schemas/gschemas.compiled which I noticed to have 600 root:root permission and ownership. Changing its permissions to 644 fixes the issue. Speculation: Might be a result of root user having a 0077 umask which may have influenced (incorrectly) the file permissions of this particular file during update. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:58

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

...

The issue might be related to /usr/share/glib-2.0/schemas/gschemas.compiled which I noticed to have 600 root:root permission and ownership. Changing its permissions to 644 fixes the issue.

Speculation:

Might be a result of root user having a 0077 umask which may have influenced (incorrectly) the file permissions of this particular file during update.

This is absolutely correct - all programs running during update are running as 'root' and the environment of this user is thus taken into account. Having a special umask is causing such issues. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:09

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 http://bugzilla.opensuse.org/show_bug.cgi?id=1131761#c4 --- Comment #4 from Suse User --- I think this is incorrect behavior. This is the first time I see something like this. Correct ownership and permissions must not depend on root's umask. Would you agree? -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15 Apr 15 Apr

06:17

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 http://bugzilla.opensuse.org/show_bug.cgi?id=1131761#c5 Yifan Jiang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yfjiang@suse.com Flags| |needinfo?(dimstar@opensuse. | |org) --- Comment #5 from Yifan Jiang --- Hi Dominique, It looks the %ghost directly relies on umask: %ghost %{_datadir}/glib-2.0/schemas/gschemas.compiled Since this is the first time I handle file attribute to %ghost directive in OBS, it would be great to have your insight. Do you think this change is sufficient and safe when an environment has a random umask? https://build.opensuse.org/package/rdiff/home:yfjiang:branches:GNOME:Factory/glib2?opackage=glib2&oproject=GNOME%3AFactory&rev=2 Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:12

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 http://bugzilla.opensuse.org/show_bug.cgi?id=1131761#c6 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #6 from Dominique Leuenberger --- (In reply to Yifan Jiang from comment #5)

...

Hi Dominique,

It looks the %ghost directly relies on umask:

%ghost %{_datadir}/glib-2.0/schemas/gschemas.compiled

Since this is the first time I handle file attribute to %ghost directive in OBS, it would be great to have your insight. Do you think this change is sufficient and safe when an environment has a random umask?

This is not fixable in the .spec file - the problem is that /usr/bin/glib-compile-schemas creates a new file while compiling the schemas and this takes umask into account -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:14

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 http://bugzilla.opensuse.org/show_bug.cgi?id=1131761#c7 --- Comment #7 from Dominique Leuenberger --- (In reply to Suse User from comment #4)

...

I think this is incorrect behavior. This is the first time I see something like this.

Seen other cases - definitively not the first

...

Correct ownership and permissions must not depend on root's umask. Would you agree?

This is debatable - if you have your user configured for a special umask, programs started as that user should respect it (and rpm installation IS started as root). It's always a fine line between breaking what should work and following user configurations. in case of glib-compile-schema, it's probably best to ignore user configuration though and set hardcode mode 644 -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:32

New subject: [Bug 1131761] searhorse won't start (after recent 'zypper up')

http://bugzilla.opensuse.org/show_bug.cgi?id=1131761 http://bugzilla.opensuse.org/show_bug.cgi?id=1131761#c8 --- Comment #8 from Suse User --- I mean: If root updates some software (as this is obviously happened after a 'zypper up') it is not expected programs which are user accessible to break suddenly due to change of permissions related to root's umask. Otherwise a 0077 umask followed by an update may disrupt the usability of the whole system. -- You are receiving this mail because: You are on the CC list for the bug.

1845

Age (days ago)

1854

Last active (days ago)

List overview

Download

8 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 1131761] New: searhorse won't start (after recent 'zypper up')

tags

participants (1)