09-22-2018, 04:45 PM
[member=2]Jerry[/member]
1) Well I did go through the shell code and the dpkg logs and it all looked pretty nice to me, and running from the CLI did not error but stalled/hung, so finally last night I compared it to another running system and it matched perfectly. System log was next and that's where the errors showed up, several others in fact, including settings that were not passed on reboots. As I said the shell code seemed without error, so rather than immediately conclude the system was borked, I realized it could be the disk, and there it was, several bad sectors at the head of the disk, of course multiplying themselves with each change requiring a reboot to take effect. What was actually happening was when I ran lite-tweaks the changes were taking so long to initialize because of the bad sectors that they were not recorded in time for the reboot. Replaced the disk, installed again from the same USB, and all is well now.
2) I am curious if gksu is the best way to go here with the lite-tweaks code. I'm assuming that's because of the specific UI call.
3) Also it might make more sense to require sudo for h/s buttons option as the log-off screen window setting would then be the same on multi-user setups. That makes more sense because skilled users would know how to use the CLI anyway, and the options would then be hidden from dilettante users.
I enjoyed the journey anyway, and this was the last of any older Intel machines I have on hand until next month, so what's left around here is only Debian and AMD cpus. Feels a little empty, but kinda refreshing too.Thanks again for the reply.
TC
1) Well I did go through the shell code and the dpkg logs and it all looked pretty nice to me, and running from the CLI did not error but stalled/hung, so finally last night I compared it to another running system and it matched perfectly. System log was next and that's where the errors showed up, several others in fact, including settings that were not passed on reboots. As I said the shell code seemed without error, so rather than immediately conclude the system was borked, I realized it could be the disk, and there it was, several bad sectors at the head of the disk, of course multiplying themselves with each change requiring a reboot to take effect. What was actually happening was when I ran lite-tweaks the changes were taking so long to initialize because of the bad sectors that they were not recorded in time for the reboot. Replaced the disk, installed again from the same USB, and all is well now.
2) I am curious if gksu is the best way to go here with the lite-tweaks code. I'm assuming that's because of the specific UI call.
3) Also it might make more sense to require sudo for h/s buttons option as the log-off screen window setting would then be the same on multi-user setups. That makes more sense because skilled users would know how to use the CLI anyway, and the options would then be hidden from dilettante users.
I enjoyed the journey anyway, and this was the last of any older Intel machines I have on hand until next month, so what's left around here is only Debian and AMD cpus. Feels a little empty, but kinda refreshing too.Thanks again for the reply.
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.