![]() |
Lite Tweaks issue - Printable Version +- Linux Lite Forums (https://www.linuxliteos.com/forums) +-- Forum: General (https://www.linuxliteos.com/forums/forumdisplay.php?fid=4) +--- Forum: On Topic (https://www.linuxliteos.com/forums/forumdisplay.php?fid=14) +--- Thread: Lite Tweaks issue (/showthread.php?tid=9135) Pages:
1
2
|
Lite Tweaks issue - Valtam - 05-05-2024 Is anyone else having issues with Lite Tweaks when choosing any option? Make sure you run Updates before checking, thank you. Re: Lite Tweaks issue - stevef - 05-05-2024 No problem apparent on a couple of systems (5.8 and 6.6) The 5.8 system is fully updated and upgraded, while the 6.6 system reports distro-info-data kept back. Re: Lite Tweaks issue - Valtam - 05-05-2024 It's odd. No matter what I choose, nothing works on both 6.6 and 7.0 (rc1). Re: Lite Tweaks issue - trinidad - 05-05-2024 6.6 fully updated here on my main machine and Lite Tweaks works fine. The only thing I can think of (heard something about file permissions or security updates to Chrome that borked some distro specific stuff somewhere) which wouldn't affect my machine because I have Chrome removed. I'll test the other two (both 6.6) and get back to you. Odd. I use Lite Tweaks regularly. Okay. Tested my second machine on hardware. Latest update: cpio, less, and Linux firmware. Lite Tweaks works fine after update. Cleaned package cache and logs no problem. Okay updated LL6.6 running in MS hyper-v. Same set of updates plus MS Edge stable update. Lite Tweaks worked fine after update. Cleaned package cache and logs no problem. Maybe restart Chrome and reset it as default browser? TC Re: Lite Tweaks issue - Valtam - 05-05-2024 Thanks TC. Sent from my Mobile phone using Tapatalk Re: Lite Tweaks issue - bonnevie - 05-05-2024 Same as TC and Stevef, no problem with any of Lite Tweaks options on my updated 6.6 VM Re: Lite Tweaks issue - Valtam - 05-06-2024 Thanks for that. Perhaps we'll catch something in the RC release - hope not ![]() Re: Lite Tweaks issue - Şerban S. - 05-06-2024 Lite Tweaks issue
[size=medium]Tested Today (06-05-2024) [L06-05-2024 ora 13:20] I ran today the updater: The following packages will be upgraded: distro-info-data Procedure went smooth. Nothing seems wrong, so far (13:20, GMT+3) The only issue with Lite Tweaks, is the same old one, relate to the Kernel Removal section. The removal program, looks like exiting with some unknown error and breaks the program at the point of removing the initial kernel (5.15.0-86 I guess). I belive that is somehow GRUB related. Maybe there is some kind of built-in safeguard that somehow leads to this result. You can reproduce this, running multiple times the same removal procedure, with or without restarting (cold boot). Lite Tweaks Config I ran the App with the following configuration: Autoremove Packages; Kernel Remover; Log Archives; Package Cache; SystemD Log Cleaner; Except for the Kernel Remover, the rest of the options are pretty much the same everytime I do some cleaning for whatever reason. At first run, the kernel list is: “linux-image-unsigned-5.15.0-82-generic”. My current kernel is “linux-image-5.15.0-89-lowlatency” and the specification is “5.15.0-89.99 Signed kernel image lowlatency”. At SECOND run, (after rebooting!) the kernel list is: “linux-image-5.15.0-82-generic”. Says “Successfully…”. At THIRD run, (after the second reboot!) the kernel list is: “linux-image-unsigned-5.15.0-82-generic”. Says, again (!!!) “Successfully…”. This goes on and on, indefinitely. I tested once a number of eight reboots then gave it up. I even removed the said kernels manually until searching returned an empty string, yet, this weird thing gets back. [L06-05-2024 ora 14:20] After one hour from the update, still nothing suspect. I’ll probably publish this and eventually, update it after some hours (days) of uptime and some “heavy weigths lifting”: Audio work (JACK, QTractor & the like). At this moment, all looks good. After 5 hours... [size=medium][L06-05-2024 ora 18:40] As I said above, I did some demanding tasks: I’ve been working on a track for an album. After closing the Audio Session, I ran again Lite Tweaks: Kernel Remover; Package Cache; SystemD Log Cleaner. Kernel Remover: the kernel list is: “linux-image-5.15.0-82-generic”. So, as I said above, in fact, it did nothing although it reported “Successfully…”. As for the rest of tasks, still OK. Given the fact that the system was changed from the default installation (another kernel, JACK + some other pro-audio Apps), I guess that if it were to crush for a reason residing inside the system installation, this should be somehow “visible”. Best regards, Șerban. Re: Lite Tweaks issue - trinidad - 05-07-2024 On LL 7.0 the error message when starting Lite Tweaks in the terminal is: (zenity:11739): dbind-WARNING **: 11:31:37.757: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0.0: Permission denied However on LL 6.6 I get no warnings starting Lite Tweaks from the terminal. TC Re: Lite Tweaks issue - Şerban S. - 05-07-2024 Hi! I tried the suggestion of LL-User: (05-07-2024, 03:22 PM)LL-user link Wrote: Hi TC,I checked and the directory is writeable by the user. I could save a dummy text and reopen it. Here is the output: Code: sudo lite-tweaks I find it weird, since it was running as Root (see code above). (I never did this before). Further more, my intuition regarding the removal routine, seems to be correct. I'll do my best to check the LL 7.0, same procedure, CLI. The only idea that comes in mind, is a string variable wrong formatted and passed to the next code snippet. The routine that interprets the content of the variable, for some reason breaks the routine without a code error or something >> 10,000. That makes the program flow go sideways. I'll see what comes out. Another idea crossed my mind: Code: pluma /tmp/ltlogs.log I get a lot of these <Gtk-Message: 21:22:59.086: Failed to load module "xapp-gtk3-module">. When I need DoubleCmd as Root, for one. Anyway, the file /tmp/ltlogs.log is really missing. If it is created runtime and as Root, it seems that the privileges are lost somewhere for some reason (Time out?). Since Kernel Remover runs as Root, it is possible, but how? As long as REMKERNELS runs as Root, it should be able to write/read anything anywhere. What really means that: "/tmp/ltlogs.log: Permission denied" For who? For Root?! is the sudo time-out set too low? Sometimes, kernel removal takes a long time, even on Dell T1700. Best regards, Șerban. |