=== arraybolt3 is now known as JoeBk === JoeBk is now known as ArrayBolt3 [12:19] Will lubuntu 24.04 make the full transition from X11 to wayland utilizing lwqt? [14:30] Currently the LXQT developers have no ETA on when LWQT will arrive. There's a really big and messy GitHub bug report that has the discussion about it that I can find. Once that happens, it will be possible for us to consider transitioning over (which I know is something the devs are interested in once possible). [14:31] Guest38: ^ [14:32] https://github.com/lxqt/lxqt/issues/10 [14:32] Issue 10 in lxqt/lxqt "Wayland support" [Open] [14:32] Guest38: ^ [14:47] Is there an option to enable trusting .desktop files by default? [14:50] Not that I'm aware of. [14:52] you meaning right click and "trust this executable"? [14:53] any ideas my rebooting/shutdown problem? [14:53] Yea. I just want to trust executables by default. Feels silly to have to do that with the qterminal the distro came with. [14:54] don't need to do that on qterminal [14:54] I put a shortcut on the desktop (22.04.1) and I had to trust it. [14:55] Tiberi: Sorry, I don't know what's happening with the rebooting/shutdown problem, and I'm not even sure where to start looking. :( [14:56] Isn't trust executable the same thing as doing chmod +x in the terminal? [14:58] how about right click desktop file on desktop and that way? [14:59] someone said that they installed nvidia drivers, but don't know how to do that [15:00] Tiberi: i can look over your log if you like, but would need to see it fully. you can output the first and last 1000 lines of a boot where the system failed to shut down properly online like this: journalctl --list-boots then look for which is the right boot ID. assuming it is ID "-3": journalctl -b -3 | head -n1000 | nc termbin.com 9999; journalctl -b -3 | tail -b 1000 | nc termbin.com 9999 [15:01] ok [15:01] Tiberi: To install NVIDIA drivers, open "Software Sources" from the application menu, then click Additional Drivers, and select the NVIDIA driver of your choice (probably the one marked as being recommended). Then you can install it from there. [15:04] I have another question: What is the name of the screen locker that lubuntu uses by default. Arch wiki says it uses slock or XScreenSaver. I just want to know what lubuntu picked. [15:06] tomreyn tail: cannot open '1000' for reading : no such file or directory? [15:07] Tiberi: sorry, i had a typo, this is correct: [15:08] journalctl -b -3 | head -n1000 | nc termbin.com 9999; journalctl -b -3 | tail -n 1000 | nc termbin.com 9999 [15:08] note, again, the "-3" is just an example here [15:08] yeah but i think it is right one?? [15:09] https://termbin.com/5jo4x [15:09] i could/would not know [15:09] https://termbin.com/ayf6 [15:11] !acpi_osi | Tiberi: this is another approach you can try [15:11] Tiberi: this is another approach you can try: If your system is unstable or power management does not work well and logs show ACPI issues, you can try to make the Linux kernel pretend it was Windows during boot (which can help on hardware which was only tested with Windows): http://iam.tj/prototype/enhancements/Windows-acpi_osi.html [15:13] ACPI Warning: SystemIO range 0x0000000000004E00-0x0000000000004E3F conflicts with OpRegion 0x0000000000004E00-0x0000000000004E3F (\_SB.PCI0.SM00) (20210730/utaddress-204) [15:14] ACPI: OSL: Resource conflict; ACPI support missing from driver? [15:14] this *may* be an issue, not sure [15:15] also this: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [15:16] how i do that? [15:17] !bootparm [15:17] !bootparam [15:17] sorry, let me find the right trigger [15:18] !kernelparm | Tiberi [15:18] Tiberi: To add a one-time or permanent kernel boot parameter see https://wiki.ubuntu.com/Kernel/KernelBootParameters [15:21] this is old hardware with an nvidia graphics chipset. if there are problems which can be graphics related, and the (currently used) open source nouveau driver does not work well with it, maybe you can find a proprietary driver which still works with it. [15:28] this looks unrelated but wrong: NetworkManager[762]: [1660767579.0958] failed to open /run/network/ifstate [15:28] networkd-dispatcher[771]: No valid path found for iw [15:30] also this looks wrong: snapd[784]: snapmgr.go:363: cannot read snap info of snap "gtk-common-themes" at revision 1535: cannot find installed snap "gtk-common-themes" at revision 1535: missing file /snap/gtk-common-themes/1535/meta/snap.yaml [15:32] Tiberi: oh, looks like your ata1.00 port HDD is just broken. no surprise on a 13y+ old device [15:33] nice [15:33] how that effect on shutting down? [15:34] well that has effects on any data that needs to be written, and sometimes also read, to / from disk. during shutdown, usually more data is written to disk than during standard operation [15:34] but somehow works kind of well. some little stucks, but.. [15:35] well, backup asap what you can [15:35] why i does that thing allways? [15:35] it is just installed and i dosen't have anything [15:35] are you asking me why you're trying to run a 13+yr old computer? [15:36] just thinking why it stuck every time and same place on shutting down [15:37] get a new computer, or at least a mediocre ssd, it will still be a much better experience than it is now. [15:37] also this is just going to fail soon [15:42] i got new ssd on it [15:55] Tiberi: the WDC WDS240G2G0A seems to be what's broken [15:56] hmm.. [15:57] WDC WDS240G2G0A-00JH30 specifically [15:58] first log says: ata1.00: ATA-9: WDC WDS240G2G0A-00JH30, UF510000, max UDMA/133 [15:58] second log says: [15:58] systemd[1019]: Starting Virtual filesystem service... [15:59] kernel: ata1.00: exception Emask 0x10 SAct 0x300000 SErr 0x400000 action 0x6 frozen ... interface fatal error [15:59] it could also be a broken sata cable, though [16:00] laptop so it dosen't have sata cable [16:00] or loose connector [16:00] maybe solderings is bad? [16:01] then you'd always had this issue [16:03] even then i dosen't rebooted when i installed linux on usb stick [16:09] i don't know what should i try that i could only shutdown [16:15] https://support-en.wd.com/app/products/product-detailweb/p/279 provides a windows firmware updater for your ssd. this might be worth a try, too [16:20] how that works without windows? [16:21] ok i put it on my windows pc [16:23] or don't know how that works on windows [16:55] hi [16:55] tp link connection to my lap keeps disconnecting [16:56] but other wifi connects good [16:56] can anyone help? [16:56] Tiberi: https://wddashboarddownloads.wdc.com/wdDashboard/DashboardSetup.exe [16:57] yea i need to first put it on my windows pc [16:57] Tiberi: once you have it running, it should be pretty self-explanatory. there will be some "update" or "FW upgrade" section or button, and then it should already select the right firmware [16:58] hope it work coz i dosen't have "windows" partitions [16:59] on the ssd? that wont matter [17:12] tristan_: try disabling power saving: https://gist.github.com/jcberthon/ea8cfe278998968ba7c5a95344bc8b55 [17:12] i did it [17:13] if i restart router, wifi is working for some time [17:14] only laptop has disconnection problem [17:14] android phones working well with wifi [17:14] if restart network manager it will connect for few seconds [17:15] then keeps disconnect until restart router again [17:15] other wifi with same laptop working fine [17:15] i am using lubuntu 18.04 [17:20] tristan_: Lubuntu 18.04 is EOL and unsupported. You might have better luck if you upgrade to the latest supported release, Lubuntu 22.04. [17:21] (Back up your data before beginning an upgrade since upgrades can go wonky.) [17:22] is 22.04 comes with lxde? [17:23] Lubuntu upgraded to LXQt, which is a port of LXDE to the Qt toolkit. It looks pretty nice, but is a significantly different look and feel. (LXDE is being sunset in favor of LXQt by the upstream developers.) [17:24] is lxqt fast like lxde? [17:24] From my experience, yes. Works very well on systems with 2 GB of RAM or more. [17:25] i need to take backup, i don't want to break anything. [17:25] Very important. Definitely do that first. [17:26] Oh, one more thing - do you know if your system is 32-bit or 64-bit? [17:26] 64bit [17:26] Nice, then you're good to go. [17:26] i3 6th gen [17:27] Oh wow. Yeah, that will work extremely well. I'm on i5 3rd gen over here and Lubuntu works awesome for me. [17:27] s/will/should/ (since there's always a possibility of things going wrong, but that's why we're here to help fix that.) [17:28] i liked lubuntu a lot [17:28] easy ui [17:32] firmware was up to date [17:32] and healt was 99% [17:35] lubuntu runs on old and new pcs [17:35] probably with minimal specs too, but I haven't tried latey [17:36] ? [17:36] If you really want to, it will probably run on low specs, the trouble with turn when streaming videos, youtube, gaming, ...., [17:37] dragon2: Welcome to the Lubuntu tech support channel! If you don't mind, we're mid support session. However, #ubuntu-discuss and #lubuntu-offtopic would be fantastic spots for this conversation. [17:37] Tiber: Did you try the acpi-osi thingy yet? [17:38] no [17:38] what's that? [17:38] Lemme find it again... [17:38] !acpi_osi [17:38] If your system is unstable or power management does not work well and logs show ACPI issues, you can try to make the Linux kernel pretend it was Windows during boot (which can help on hardware which was only tested with Windows): http://iam.tj/prototype/enhancements/Windows-acpi_osi.html [17:39] That describes exactly the problems you're running into IIUC, and gives a possible fix. [17:39] ok i will try that [17:46] damn... that should have step by step instructions for me [17:47] Oh... OK, download the acpi_osi.sh script. [17:49] Then open a terminal in the Downloads folder, and run "chmod +x ./acpi_osi.sh && ./acpi_osi.sh". [17:49] Er, wait... [17:50] chmod +x ./acpi_osi.sh && sudo ./acpi_osi.sh [17:50] Tiber: ^ [17:53] ok and that's it? [18:23] not shutting down [18:29] Tiber: it cannot have any effect until *after* the next reboot [18:34] https://termbin.com/u2p2 https://termbin.com/69re [18:34] is this looking right? [18:35] some one got same laptop as i and he speaked something about nvidia drivers [18:36] now i can't see errors [18:37] i should have nvidia 340 drivers [18:41] https://unix.stackexchange.com/questions/623159/ubuntu-shutdown-does-not-power-off-tried-other-solutions [18:41] that last one got same laptop as i [18:43] https://termbin.com/69re has the same error messages [18:43] ... as before [18:43] was the firmware upgraded? [18:44] did you run a health check? [18:45] it's entirely possible that the symptoms you described and the disk freezing are separate issues, though [18:46] it could also be that the ssd is just running too hot [18:47] 13yo laptops would have veeeery dirty /crammed fans unless you cleared those recently [18:48] i have [18:49] and firmware was upgraded and healt was 99% [18:51] i have changed pii things and cpu is still being hot on windows 10 [18:51] now on linux it's going kind of quiet [18:56] i was going to use that laptop on pc osciloscop and maybe arduino ide [18:57] windows 7 was last windows that i have actually used that [19:09] to detect thermal sensors, install lm-sensors and run sensors-detect. [20:03] i think i make i right but everything is no [20:31] how i can install nvidia-legacy-340 ? [20:32] GPG error: http://deb.debian.org/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY DCC9EFBF77E11517 [20:35] something that i don't know? [20:36] or i don't know anything actually === drkokandy_ is now known as drkokandy