- User Since
- Oct 14 2017, 8:34 AM (100 w, 2 d)
Fri, Sep 13
Aug 3 2019
Hello, I'm the maintainer of rustup in Solus.
I have to admit that I am quite unexperienced with Solus packaging. However, I am willing to learn :)
May 28 2019
This task is a duplicate of T565, which has not been accepted.
May 24 2019
May 5 2019
May 2 2019
Abandoning the issue since I haven't found any way to fix it under Solus and haven't enough skills to fix Firefox's source code.
May 1 2019
Fixes release number.
- Bump to rustup 1.18.1
Apr 22 2019
Ooops sorry guys
Mar 24 2019
Thank you for your answer.
As far as I know, it is not urgent to upgrade.
I just wanted some feedback because I was wandering why it wasn't accepted.
Any thoughts about this diff?
Mar 19 2019
No. Gnome stack 3.32 may require some changes in budgie. As such, it will land later in the repository (see The Roadmap)
Mar 16 2019
Remove an useless pipe.
This fixes pspec_x86_64.xml's License section.
Mar 15 2019
Abandoning the revision since this does not resolve the problem.
Fixes wrong repository.
Mar 14 2019
Jan 18 2019
Ow sorry, I just wanted to help you :(
So I confirm that a rebuild for rustup should be triggered each time rust is updated
Sorry, I will try to provide the patches the way you want them tomorrow.
(I don't know what happened in my head, but I was thinking about rust 1.32)
Jan 3 2019
Maybe hardware acceleration can be automatically activated on installation if there is no NVIDIA hardware? (maybe using usysconf)
Dec 27 2018
Fixed binary file permissions. Thanks @Girtablulu
The script now has a normal behavior. Thank you @livingsilver94
You are right, this is not the cleanest way.
I'm working on it (compiling rustup and then moving it to the appropriate location)
Merged build step and install step
For cargo, it's the same.
Removed useless dependencies
Fixed component. Thanks @DataDrake
Dec 25 2018
Closing this since it seems to be an upstream issue.
Dec 24 2018
Dec 22 2018
Dec 11 2018
You're right, by default, --new-tab has a strange behaviour.
However, if you run firefox --new-tab about:newtab, it runs as excepted.
Dec 10 2018
Assigning JoshStrobl to investigate and triage. Referencing T7289.
Dec 6 2018
Nov 18 2018
Resolved by D4374.
So we now know that enabling layers.acceleration.force-enabled is no longer an issue on Nvidia hardware using both linux-current and linux-lts.
So can we enable it by default?
It seems it has already been changed with recent update to firefox 63.0.3 (see this Differential Revision).
Nov 14 2018
You're right: as pointed before, gfx.xrender.enabled has nothing to do with scrolling glitches.
I was quoting this answer because @Girtablulu said Firefox runs well with layers.acceleration.force-enabled on Nvidia hardware and Linux LTS, not because of the xrender part.
Nov 12 2018
Thank you for your comment, I'll report it in T7127.
Your issue seems to be related to T7127. Devs said they will enable it if someone tests layers.acceleration.force-enabled using linux-lts with an Nvidia graphic card. Maybe you can check it yourself. It would resolve this task and T7127.
Oct 30 2018
I have no computer with Nvidia graphic card in it, so I can't test for layers.acceleration.force-enabled with Nouveau.
Oct 20 2018
Last time I was so amazed by an update was when Budgie 10 was released. Very nice idea !
Sep 30 2018
It seems this functionality is back with gnome 3.30 (see here). So this review may not be necessary.
Sep 16 2018
Thank you for your response.
May 12 2018
In fact I noticed it closes faster if you have a more powerful computer.
I'm now using a very recent computer and it closes as fast as it does with other applications, but when I use my seven years old netbook, Firefox seems to freeze and closing after one second or two seconds.
As far as I saw, it does not depend on the number of tabs opened.
I have the same issue here: I have to wait a bit when I hit ctrl + q or when I click on the close button.
May 5 2018
Please do not apologize : everyone do errors, that normal, since we are humans (although I am convinced you are more than human ^^), and you fixed it in 17 minutes. This is the fastest response I have ever seen. Please don't apologize
Have a nice day!
May 2 2018
May 1 2018
When I connect to a VPN with gnome-control-center, there is a console output:
(gnome-control-center:2699): network-cc-panel-WARNING **: 10:09:12.646: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.freedesktop.ModemManager1.service not found.
And the network-manager-applet crashes.
Hope it helps
I have the same issue here.
I have disabled auto-connection to VPNs, so that I haven't to rollback and it will be easier to provide you logs etc.
As far as I understood, it is not network-manager-applet's fault, because when I try to connect from the gnome-control-center with a VPN, it fails.
Mar 24 2018
Will there be new wallpapers for this release ?
I'm asking because my sister wants to submit some...
Jan 7 2018
Dec 27 2017
Sorry, I'm a bit late because of Santa ^^
Thank you very much, this issue is resolved.
Have a nice day.
Nov 26 2017
Nov 3 2017
Today I installed my HP printer using hplip and scanning works fine : no need to add user to group or to modify udev rules. I'm able to scan without root using simple-scan.
Therefore, maybe gnome-control-center doesn't "fully" install the printer.
Nov 2 2017
I had this problem too. I had to add my user to the scanner group (about one month ago).
I hope it help you.
Oct 16 2017
Versioned tarballs at https://sourceforge.net/projects/tilp/files/tilp2-linux/tilp2-1.18/
Thank you ! I've updated the manifest task.
Oct 15 2017
I have just compiled it using this script provided by the project's website. The most difficult part was to find dependencies. I think it would not be difficult for an experienced packager to package it.
Oct 14 2017
Thank you for your answers, it works well right now.
sudo eopkg dr Unstable
sudo eopkg ur
sudo eopkg up
It removed the Unstable repo and tried to upgrade the system (no package were upgraded because the system was already up to date).
I have got the same error. I tried to enable unstable repo this morning.
The output of eopkg lr is :
Solus [active] https://packages.solus-project.com/shannon/eopkg-index.xml.xz Unstable [active] https://packages.solus-project.com/unstable/eopkg-index.xml.xz