Comments

139 Comments

This update addresses quite a number of bugs I had on three very different systems, plus a few more, e.g. #1482354 as well as some other issues for which there were no bugs filed.

BZ#1502303 php-fpm crashed with default SELinux settings
BZ#1513883 SELinux is preventing gnome-shell from 'execute' accesses on the file 2F72756E2F676E6F6D652D696E697469616C2D73657475702F233232343434202864656C6574656429.
BZ#1509502 SELinux is preventing bwrap from nnp_transition, nosuid_transition access on the process2 Unknown.
BZ#1499390 SELinux is preventing ibus-daemon from using the 'signull' accesses on a process.
karma

#1513241 fixed, no regressions noted

BZ#1513241 filezilla: symbol lookup error: filezilla: undefined symbol: _ZN2fz6threadC2Ev

Hello Nicholas,

You were spot on.

Among the directories held by XDG_DATA_DIRS was /usr/local/share/, which did contain glib-2.0/schemas/ and in that directory I found gschemas.compiled and org.gnome.shell.extensions.system-monitor.gschema.xml dating back to 17 Jan 2012. As it turns out, instructions at the time required to add the file there: https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/blob/0dce659308ea46a1ec9fccda0c47ab20a319f262/README.md

That was the reason for the "Settings schema 'org.gnome.shell.extensions.system-monitor' does not contain a key named 'compact-display'" message, the key wasn't there at the time.

I renamed the /usr/local/share/glib-2.0/ folder, disabled and removed my local extension and went on to install yours. After restarting the shell (no need to log out) and enabling the extension via Tweak Tool, everything was working fine.

Thank you so much for your perseverance!

Best regards,

Alex

Looks good to me.

BZ#1503250 Outdated package

Hello Nicolas,

Added a user, switched to a VT, installed the extension, rebooted, logged in to GNOME on X and as soon as I enabled the extension (the only one), gnome-shell crashed.

I decided to let abrt file a report and it turns out I was right about this being #1402492, because my report was added to that bug.

Sorry for taking up so much of your time and thanks for trying to help.

Best regards, Alex

Hi Nicolas,

I guess I should have added those details before you asked, but anyway, I'll do it now.

I am running gnome-shell-3.24.3-2.fc26.x86_64 on X, as I am using nVidia's driver, so I can't run Wayland. I also have gnome-shell-extension-common-3.24.3-1.fc26.noarch. There is only one version of your package for F26 and that would be gnome-shell-extension-system-monitor-applet-0-0.1.20171005git61b0a60.fc26.noarch.

Like I wrote earlier, when I removed the extension from extensions.gnome.org, I checked that ~/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com was indeed removed and it was.

These are my other extensions:

invert-window@maiself
openweather-extension@jenslody.de
places-menu@gnome-shell-extensions.gcampax.github.com
screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com
TopIcons@phocean.net

The only thing I hadn't tried was resetting the dconf settings, which I just did.

So to recap what I did in my latest attempt:

  • I went over to extensions.gnome.org, disabled and then removed the extension, while making sure that its directory under ~/.local/share/gnome-shell/extensions/ was also removed.

  • I reset the dconf settings (I backed them up first).

  • I went on to install gnome-shell-extension-system-monitor-applet (with dnf --enablerepo=*testing install etc.) and verified that gschemas.compiled was regenerated and also that the schema XML file was there too.

  • For good measure, I rebooted the system.

  • I logged into GNOME.

  • I fired up Tweak Tool and enabled the extension.

  • gnome-shell crashed, I'm back at gdm. Every subsequent attempt to login results in gnome-shell crashing.

I was almost certain that it would work this timeā€¦

I looked into the error messages (fresh log) and it seems that when I am using the packaged version of the extension, something is triggering #1402492. Since you have packaged a more recent snapshot of the extension than what's currently on extensions.gnome.org, I expect that when the latter gets the newer code, I will face the same error, unless something is different between the packaged version and the other one.

Unless you have another idea, I'd suggest you ignore my -1 karma and push it to stable when you can. If I encounter the same issue when my version gets updated I will file a bug upstream.

Best regards,

Alex

Hello again,

I gave it another go today, while paying attention to what was happening on the system. I can not open a bug report, as bugzilla does not list gnome-shell-extension-system-monitor-applet among the components.

I had the extension installed from extensions.gnome.org and I uninstalled it using the website. I verified that the extension had disappeared from ~/.local/share/gnome-shell/extensions/, but my settings remained (I checked via dconf-editor).

I installed the packaged version of the extension with dnf and checked if /usr/share/glib-2.0/schemas/gschemas.compiled got regenerated - it did.

I started Tweak Tool to enable the extension, but as soon as that happened, packagekitd crashed and dumped core. I closed Tweak Tool, restarted gnome-shell, reopened Tweak Tool and enabled the extension. At that moment, gnome-shell crashed and I was back at gdm. Every attempt to login failed with a gnome-shell crash, until I removed the extension from a VT with dnf.

I have uploaded a sanitized system log starting right before I removed the extension from extensions.gnome.org, up to the point I had removed the packaged version and logged back in.

Hello Nicolas,

I'll try to repeat the process some time tomorrow and see if I can reproduce the error. The extension was originally installed from extensions.gnome.org. As far as I can tell, when I removed it prior to installing the packaged version, its folder disappeared from ~/.local/share/gnome-shell/extensions/, so I'm guessing there wasn't something left behind.

I didn't think to check gschemas.compiled, I will keep that in mind.

On github, the maintainers state that libgtop2-devel and NetworkManager-glib-devel are required, but in your spec file I see only gettext and glib2 as build dependencies. Is the documentation obsolete?

I will open a new bug in rhbz if I find anything useful.

Best regards,

Alexander

As soon as I enabled the extension in Tweak Tool, gnome-shell crashed and I was thrown to gdm, but I could not log in to GNOME any more. I rebooted, just in case there was a conflict somewhere, still unable to login. Eventually I switched to a VT and removed it, problem solved.

I got these messages:

Oct 14 19:37:57 gnome-shell[15464]: System monitor applet init from /usr/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com
Oct 14 19:37:57 gnome-shell[15464]: Settings schema 'org.gnome.shell.extensions.system-monitor' does not contain a key named 'compact-display'
Oct 14 19:37:57 kernel: traps: gnome-shell[15464] trap int3 ip:7fc1faed0e51 sp:7ffdc147a420 error:0 in libglib-2.0.so.0.5200.3[7fc1fae81000+110000]
Oct 14 19:37:57 audit[15464]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=15464 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=5 res=1
Oct 14 19:37:58 gnome-session[14507]: gnome-session-binary[14507]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Oct 14 19:37:58 gnome-session[14507]: gnome-session-binary[14507]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 14 19:37:58 gnome-session-binary[14507]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 14 19:37:58 gnome-session-binary[14507]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Oct 14 19:37:58 gnome-session-binary[14507]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 14 19:37:58 gnome-session[14507]: Unable to init server: Could not connect: Connection refused
Oct 14 19:37:58 gnome-session-f[15723]: Cannot open display: 
Oct 14 19:37:59 gnome-session[14507]: gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client27' failed to reply before timeout
Oct 14 19:37:59 gnome-session[14507]: gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client28' failed to reply before timeout
Oct 14 19:37:59 gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client27' failed to reply before timeout
Oct 14 19:37:59 gnome-session-binary[14507]: WARNING: Client '/org/gnome/SessionManager/Client28' failed to reply before timeout

I reinstalled from extensions.gnome.org and it's running fine. Does that missing schema key ring any bells?

karma

Everything seems fine save for the CSD workaround for rounded corners, which does look strange. Tested on GNOME running on X.

BZ#1500234 [CSD] Let's include CSD patch from mozbz#1399611 at Firefox 57
Test Case firefox media
Test Case firefox addons
Test Case firefox browse

You are welcome, it took quite some work from several people, but it's finally back!

Finally managed to update my old Athlon MP rig to F27, haven't seen the chronyd issue.

karma

Got confused and tested on i686 but with SSE2 (everything seems fine). Tomorrow I'll test on a non SSE2 system.

BZ#1493535 nss-3.33 is available
karma

Everything seems fine.

BZ#1497932 Plug-Ins for example flash fails because of unresolved symbols.
Test Case firefox browse
Test Case firefox media
Test Case firefox addons
karma

Works as expected, no problems noted.

BZ#1495845 Review Request: zegrapher - Free and opensource math graphing software
karma

Problem solved, everything runs fine.

BZ#1489040 nut needs to be rebuilt for the freeipmi update on F26
karma

Packages get built and installed inside the chroot just fine. I had never used the mock shell before, I tried it now and I got these messages:

sh: cannot set terminal process group (-1): Inappropriate ioctl for device

sh: no job control in this shell

which seem informative and harmless and in any case, I didn't notice any problems while using it.

I have not tried building live media with this version, but I had created a live ISO with 1.4.3-1, so I'm guessing that if there is a problem as reported by Neal, it was introduced with the last version.

karma

Tested on two different machines for a few hours, timeout problem fixed, no other issues.

BZ#1460051 nss-3.31 is available
BZ#1470352 dnf --refresh update broken since 26 update
karma

The patch works, problem fixed with nss-3.31.0-1.1.fc25.

karma

On my laptop it's running fine without any warnings. I'll keep the service disabled on that desktop for now, I've been hunting for some other bugs and I'm trying to keep my system logs on a diet.