- User Since
- Oct 30 2017, 2:30 PM (144 w, 4 d)
Feb 14 2020
Asus G752VS laptop:
Feb 13 2020
Lenovo Y700-17ISK laptop:
Wow, I didn't even know that in Linux it is possible to enjoy this important feature :)
Feb 1 2020
Hello, does the upgrade to GNOME 3.36 includes Nautilus upgrade?
Dec 7 2019
@DataDrake wrote on 18.11.2019: "we aren't in testing mode for a new ISO, so patching the installer isn't a high priority right now".
Nov 2 2019
System fully updated, but unfortunately, Solus keeps resetting screen brightness to maximal 100% on every restart.
So today I made an experiment. Within my Solus there are more than one backlight controls:
Sep 28 2019
I hope this long-standing problem will be fixed before the releasing of new Solus ISO
Jun 22 2019
The same thing here, when changing volume with a fullscreen Youtube video (Nvidia GeForce GTX 1070).
Jun 21 2019
Ok - no problem, sorry I didn't know...
The Latest Linux Kernel 5.1.12 Appears To Be Causing Connectivity Issues For Steam
A number of Steam Linux users are reporting of connection troubles when upgrading to the latest Linux kernel releases...
Jun 12 2019
08.06.2019 update kernel to 5.1.7.
11.06.2019 kernel 5.1.9 is out
I am an old computer user who never used a computer without a firewall. I am very happy that my Espon L365 printer/scanner works ok in a WiFi mode, but not without firewall being turned off. I don't accept that in 2019 my firewall is not smart enough to understand that my Espon L365 printer/scanner is a friend and not an enemy :(
Mar 16 2019
New fresh instalattion on Asus and Lenovo laptops - still have the same Gedit / LibreOffice Writer problem.
Jan 21 2019
Solus long standing Epson L365 scanning problem finally solved.
Searching the internet for a solution, I accidentally found "gscan2pdf". It works great.
Jan 16 2019
Hello, please reopen this task.
Few dasy ago I made a fresh, clean installation of Solus 3.9999-Budgie. With all defualt settings, Epson L365 scanning does not work. Once again I have the same problem: with using utsushi, scan itself is processing but no image is saved.
Furthermore, links for old but working version of utsushi and graphicsmagick are not working too: //(https://www.dropbox.com/sh/3jwzz3ncfm4unuf/AAD58e1cFr5QlY-UYEmvL-JDa/utsushi-3.32.0-4-1-x86_64.eopkg?dl=0 and https://www.dropbox.com/sh/j3yo6sm0epnm0ko/AAAsgifGnZaxfalF52o6VVu2a/graphicsmagick-1.3.26-12-1-x86_64.eopkg?dl=0)//.
Dec 6 2018
is the "nvidia.NVreg_EnableBacklightHandler=1" option now applied by default in Nvidia drivers within Solus repo?
Another question if remembering brightness setting is eventualy an unsolvable problem: it's been a long time since I added "xbacklight -dec 30" to autostart in Budgie. In order to avoid unnecessary and potentially harmful mixing of different stuff, since with "nvidia.NVreg_EnableBacklightHandler=1" brightness control works - is there any Nvidia command with which I can replace the xbacklight command? Thanks...
Asus and Lenovo SSD equipped laptops here. Important question: whatever fix arrives, will it require a new Solus installation or not? Thanks...
Nov 12 2018
Thank you for your reply. This is the initial description of the problem: "since the update of nvidia-glx-driver to 410.X my system is using llvmpipe instead of the Nvidia driver" - could you please clarify if this problem is fixed now?
If the answer is positive, is this the correct procedure to return to 410 driver:
Kernel 4.19.2 is coming tomorrow (Tue Nov 13) with 361 patches :)
Oct 27 2018
Done. I'm not receiving any system message about available updates - is my system going to be updated automatically to the next 410 driver release, or I will must to intervene manually (how)?
Thank you, can you please give a step-by-step guide how to switch back to nvidia-390-glx-driver-current?
Oct 20 2018
'sudo journalctl --vacuum-size=50M --vacuum-time=30days' implemented until now in my and few other computers. Having something similar by default is very ok, thank you :)
Oct 13 2018
Oct 12 2018
Oct 9 2018
I have noticed that most of the times the new kernels are released on wednesday. The following is an example of something that happens very often during the last months: DataDrake - update kernel to 4.18.12 on tuesday 9 October; Greg Kroah Hartman - kernel 4.18.13 will be released on wednesday 10 October...
Oct 5 2018
This is my post on Nvidia Linux forum from 5 minutes ago:
Oct 4 2018
Hello, one year has passed since I reported at Nvidia Linux forum that on my notebook Asus G752VS (Nvidia GeForce GTX 1070) brightness control doesn't work - regardless if I try to change screen brightness with the slider within Pover options or by using keyboard FN keys //(https://devtalk.nvidia.com/default/topic/1025559/linux/solus-nvidia-gtx-1070-brightness-control-not-working/)//. I would like to kindly ask if there's any way I can somehow try acpilight? By the way, regarding this problem, I am also waiting for the arrival of X.Org server 1.20.1 into the Solus...
A month and a half has passed since updating the suspicious kernel version. I haven't encountered any problem from then. At this point, I would say that you can close this maniphest as solved.
Aug 21 2018
Yesterday, 20.08.2018 I noticed an interesting info: "The Next Challenge For Fwupd / LVFS Is Supporting NVMe SSD Firmware Updates". Shortly said, Richard Hughes at Red Hat is hoping for Linux users with NVMe drives to send him the id-ctrl identification data on their drives - this data will be useful so he knows what drives/models are most popular but also for how the firmware revision string is advertised across drives and vendors:
Aug 18 2018
So far - during this last 10 days in which I have implemented new Solus updates already two times - no problem. Strange, isn't it, if CMOS battery is eventually dead or near death? Thanks in advance for any your opinion :)
Aug 8 2018
Thank you very much for your reply - I will try to ask on Asus forum if this is a dead CMOS battery problem.
Aug 6 2018
Written by me (Lenovo Y700-17ISK): "...at the end, I installed Windows 10 alongside with Ubuntu 16.04 only because of BIOS updating..."
Jun 8 2018
Users are still experiencing many problems in Windows. The fact is that they "accept" mentioned situation because it mostly happens on the complex level. On the other hand, Linux is very great on the complex level but it "sucks" on the very basic level - and that my friend for 7 billions of newbies is not acceptable at all.
Maybe you haven't noticed but we all expecting Formula 1; it is totally unimportant if Formula 1 problem on the very basic level is upstream or not if one leaves Formula 1 before he even learn what does upstream means.
PS. please don't get me wrong, I expressed this thoughts with best wishes and intentions - if Solus is already fantastic it doesn't mean that it can't be even better :)
During the last year, Solus OS has been developed into a very hospitable ambience to coexist with computing machines. Congratulations to the entire team. The moment we have all been excitingly waiting for quite a while is very very near. In my opinion, if new users must do a battle to get a simple basic things done - the big chance for Solus 4 to attract many new Internauts and become best of the best Linux distributions will be lost. You've been working very hard in our interest, please don't miss that great opportunity. So, in this sense here it is regarding simple basic operations... NR.1: some applications (normal/snap/flatpak) still can't be pinned to additional left panel (LibreOffice for example). NR.2: change of log-in screen background is inadmissibly complicated. NR.3: in many cases the screen brightness is still unadjustable (for example Nvidia without Optimus) in a normal way without complicating with 'xbacklight'. NR.4: It would be great if during the installation process user can set the performance level, privacy level and updating strategy (all packages or only the choosen ones). NR.5: X.Org Server 1.20 should be a must have, or not?
Apr 7 2018
The newest version has jus been released: 1.1.6 (alsa-lib, alsa-oss, alsa-tools, alsa-utils, alsa-tools, alsa-plugins and others).
Mar 2 2018
So this issue (graphicsmagick related) is now defintelly solved, thank you all you guys for yur help.
However, there's a new little problem: https://dev.solus-project.com/T5967
Feb 23 2018
sorry but since i'm not a technician - I don't have a clue if the cause of the problem lies somewhere in Solus or in program itself. kyrios and sunnyflunk have started to help me in October 2017 through the Solus forum - but unfortunately without success. Sorry once again if I made any mistake by reporting this problem upstream.
I noticed that Solus use graphicsmagick 1.3.27 while the latest available version is 1.3.28 (released on 20 January 2017).
I reported this bug at graphicsmagick website:
Feb 19 2018
Will this fix the T4163 issue "graphicsmagick cannot find decode delegates for any image format"?
Feb 15 2018
Hello, is there any chance to fix this annoying old issue before the soon coming Solus 4 that promises to be a fantastic release?
Jan 24 2018
Hello, Epson L365 scanning is broken again. The same old problem: with using utsushi, once again scan itself is processing, but no image is saved.
Jan 11 2018
After few latest updates, my smartphone (Lenovo Vibe Shot) remains present in Nautilus left bar even after I disconnect it.
Nov 23 2017
Problem completely solved, my Epson L365 scanner now works ok in Solus:
Nov 22 2017
On my original internal "NVMe SSD" drive I created now two new files in my "Dowloads" folder: "blabah_1" (11 bytes) and "blabah_2" (11 bytes). They both content just one single word: "blabah". If I open only one of them, everything is ok - but if I open both two files, cursor rotates for around 10-15 seconds: rotating cursor is visible only if I move the cursor over the left dock panel or at the top of the screen over the file name. Cursor continue to rotate even after closing both two files and Nautilus too.
Nov 18 2017
Hi DataDrake, i don't know nothing about that.
Nov 17 2017
Is Epson (all-in-one) L365 scanner on the list of the devices supported by this software?
I can't get my Epson L365 scanner to work in any way:
Nov 7 2017
I'm experiencing the same problem when opening two or more gedit windows/files (Asus and Lenovo powerful laptops).