-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it work with gnome-shell 3.36 #564
Conversation
Thank you! this works! |
For some reason, I can't access the preferences anymore. neither is there a logo of the extension in applications. How do i fix that? |
Are you using Ubuntu Focal Fossa development? Because right now,
preferences currently doesn't work for any extension on focal.
I filed a bug report here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866146
…On Thu, Mar 5, 2020 at 4:26 AM Rishabh Patel ***@***.***> wrote:
For some reason, I can't access the preferences anymore. neither is there
a logo of the extension in applications. How do i fix that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#564?email_source=notifications&email_token=AANHL3T62633TX2LJUAZ3OLRF22QVA5CNFSM4LAMERG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEN2CZOI#issuecomment-594816185>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANHL3VGOCVXK7HSR2J4FHTRF22QVANCNFSM4LAMERGQ>
.
|
Thanks works here on Arch! Also can't access preferences from the context menu though. I can access preferences of other extensions through their context menus, and I access the system-monitor extension's preferences through gnome-tweaks. |
I don't think the problem with the preferences is related to the host. I can access the preferences of system-monitor with the new 'Extensions' app. Thanks for the work. |
Confirmed. This works on Arch. Thanks! |
You can mark this PR as resolving #559. |
Thanks for this PR! I am waiting for it. |
Preferences menu should work now. I tested it on GNOME 3.36.0. |
Confirmed. Preference menu works from widget after update! @shemgp, thanks a lot! |
@vltr It does remember the values for me and upon looking at the code, it should too. Perhaps you could try resetting the system-monitor folder in dconf-editor, or running |
@shemgp did that (from your branch), no luck 😬 my extension is installed locally. I'll play around with some other extensions to see if any of them may be causing this ... Because, well, I just got "Gnome'd" again 😅 |
@shemgp update: it does work properly if compact display is off. When on, it gives me the behavior I mentioned earlier. Weird ... |
@vltr Compact display compacts the width by 1.5 so maybe like me, you thought it's not remembering it, when actually it's just compacting it. Try putting, eg., 100 on only one of them and see that it's still wider than the others even in compact mode and when restarted. |
@shemgp wrong assumption made by me, then. All I thought it did was appending |
@vltr I confirm that the behaviour appears to have changed as you though. In gnome 3.34, the non-compact mode looks like this (bar and text): Now in gnome 3.36, the compact mode starts like this in the bar: |
@suiryc, I made the resize ([+] and [-]) work the same as when loading, for this PR anyway, as I think that's the intention of the original developers: To compact the width too when compact is set. It's just that on resize, they forgot to make it compute the compacted width. If you want to have the same width as the non-compact mode when on compact mode, you'll just have to multiply the size by 1.5. |
Maybe. I am not sure either of what the majority of people using this extension expect when dealing with 'graph width' and 'refresh rate'. Depending on the intent the new behaviour makes it a bit harder to configure. |
I was using the version from this PR for some time (ever since gnome-shell 3.36 started rolling out on archlinux) and everything was quite fine up until today when it stopped working. The error I get is
I would be thrilled to help (I can't imagine life without this extension), if instructed because I know literally nothing about how gnome-shell extensions work and how are they developed. I'm running on gnome-shell 3.36.0 on wayland on archlinux. |
@zegkljan There's no more |
@shemgp Sorry, I'm an idiot. I did not checkout the correct branch. Everything works. |
I'm getting the following on F32 beta with gnome-shell-3.36.1-2.fc32.x86_64: |
@DmitryBurstein Please make sure you |
The Makefile I run was inside ~/gnome-shell-system-monitor-applet-gnome-shell-3.36/, so I hope it was the right one. |
@DmitryBurstein Here's how to install this PR: git clone https://github.com/shemgp/gnome-shell-system-monitor-applet.git
cd gnome-shell-system-monitor-applet
git checkout gnome-shell-3.36
make install Then restart gnome-shell. |
Great, thanks a lot! Now, after a log off/on cycle, everything is working again. Many thanks for your help! |
This PR is beginning to devolve into a howto manual for installing this branch rather than fixing an incompatibility. What exactly is the hold up for pushing this out to extensions.gnome.org? |
I second this - since installing manually also has the problem that I'd have to deactivate automatic updates - otherwise the extension is reverted to the old non-functioning one after each reboot. |
@AllesMeins, I personally used a quick and dirty fix for this by making |
@AllesMeins @ElSenor64 this seems to work for me and I think is better than changing file permissions. |
I'd like to again point out that the immediately preceding two comments— that (1) any discussion about developing this PR quickly devolves into instructions for manually installing it, and (2) the people who do install it manually seem to report no continued incompatibilities— seem to illustrate both that there is a considerable user demand for pushing this into the main branch and that it is ready to be released from there. |
And there will be even more in less then ten days when Ubuntu 20.04 is released and the current version of the extension will break for everybody doing the upgrade. |
Rebased and merged. It would be great if additional testing could be done, for feedback. In case any regression might have sneaked in. |
could you please make a release that contains this fix? 🙏 |
@AlexWayfer should be fixed by #576 |
Thank you! |
...Does anyone know who maintains the upload on Aside from the lack of automatic updating, requiring a separate manual installation also fragments the userbase, and has already confused many people and will likely soon confuse many more if a new Ubuntu release is indeed going to imminently break this extension for hundreds or thousands of users. |
@will-ca and everyone: @chrisspen is taking care of this, and offers his time for free to do so responsibly. So let's please be patient. Every time there is a new Gnome Shell release, lots of bugs pop up everywhere, with mixed reports. It's hard to track all the possible configuration mishaps (distros, versions, patched distros, etc.) To address this, look at some of the work he is proposing in the Whenever this new version will be ready for shipping, it's better to get it right. Believe me, I do understand the frustration: I use myself other extensions and am in the same position as you. Cheers everyone. And thank you @chrisspen for maintaining this extension for a few years already. |
Yes, this works for me :-) |
Finally this method has worked correctly. Thanks to the developers. However, this is not yet available from the GNOME extension panel web page. A greeting. |
Fixing "TypeError: this.actor.reparent is not a function", with reference from paradoxxxzero/gnome-shell-system-monitor-applet#564 "Make it work with gnome-shell 3.36"
Well actually it's for GNOME Shell 3.35.91 still, but hopefully no more changes required for 3.36.
References for where I got hints for the fixes:
TipItem
error (Tried to construct an object without a GType): http://gjs.guide/guides/gjs/transition.html#extending-gobject-classesraise_top
: GNOME 3.35.2 Compatibility paperwm/PaperWM#212TableLayout
: https://mail.gnome.org/archives/commits-list/2014-August/msg01899.html