=== brainwash_ is now known as brainwash [01:39] hello [01:41] I want help about lirc [14:02] Hello, I am doing a new installation of xubuntu and installing windows alongside. I can't resize the partition more than 32 mb. Why is this? [14:04] djtravz, first install win then xubuntu [14:05] I will need to resize the partitions after I install windows [14:05] So I want to make sure that I can before I go through with too much effort in installation [14:07] install win the from win with the help of easeus partition manager create free space. [14:09] Once I have them both installed, if I need more space in either one of them I want to make sure that I can still resize both of their partitions === RedSoxFan08 is now known as RedSoxFan07 === dreamon__ is now known as dreamon [16:18] got an old computer from 2005 running 17.10, a couple of months ago an update made the start menu and desktop icons disappear [16:19] i tested 18.04 in live, and 18.04 is also affected [16:19] it's running an ancient nvidia GPU, i tested both the nvidia legacy gpu driver and the X-org driver, didn't make a difference [16:21] hans_, and the question is? [16:21] any idea how to make the start-menu visible again? [16:22] (and the desktop icons) [16:22] by start menu you mean whisker menu? [16:22] sure, the 1 that opens when you press the windows button [16:23] right click on the panel > panel > add new item and look for whisker menu there [16:23] https://i.imgur.com/LvpgAmD.png [16:24] its configured, it's there according to the panel configuration thing [16:24] ... but it's not visible [16:24] i guess it crash while attempting to start or something [16:24] in terminal run: sudo apt intstall -f [16:25] 0 everything, 0 to update 0 errors ~ [16:26] then you got no broken packages, i's assume it's some misconfigs and a good start would be if you create a new user and login as the new use and see if everything works there. [16:27] i don't think that will make a difference as the xubuntu live system was also affected, but ok i will check [16:28] i've never had a problem with the live system. [16:28] ok i made a new user and logged in, same issue. [16:28] (did n't [16:28] (didn't make a difference) [16:29] share your ~/.xsession-errors log file via a pastebin service [16:31] https://paste.ubuntu.com/p/Q524SCWm5G/ [16:31] (that's from the brand new user, first time login) [16:34] is xfce4-panel running as process? or xfdesktop [16:35] yes both of them, according to ps -A | grep -i xfce4 [16:35] both of them are running [16:38] ohh. the panel should be running, you only miss the menu. [16:38] those wrapper-2.0 entries in the log file are related to whiskermenu [16:38] (i miss the desktop icons as well) [16:39] desktop icons are handled by xfdesktop [16:39] open a terminal window and run "killall xfdesktop; xfdesktop" [16:39] see if that gives any output [16:40] as root or as logged in user? [16:40] as user [16:41] you can try with xfdesktop --enable-debug too [16:41] that will print additional debug output [16:41] error: no protocol specified [16:41] (without --enable-debug) [16:41] it said more than that but the rest is localized to norwegian [16:41] .. should i try to translate that back to english? [16:42] roughly translated: could not understand the arguments: could not open the screen [16:43] for that you can use LC_ALL=C [16:44] like this: LC_ALL=C xfdesktop [16:44] set that as an enviorment variable before starting xfdesktop? [16:44] or export it beforehand [16:44] kk [16:47] now it said (xfdesktop:2679): Gtk-WARNING **: Locale not supported by C library. \n Using the fallback 'C' locale. \n Failed to parse arguments: Cannot open display: (blank, but i get the feeling that it would put a display name/identifier here if it had 1) [16:47] oh sorry [16:47] i forgot a line [16:48] it also said: No protocol Specified [16:48] mmh [16:48] on the line before it said "Failed to parse arguments" [16:48] can you make it work by specifying the display? [16:48] DISPLAY=:0 xfdesktop [16:49] yup [16:49] now it started but gave a lot of errors (but still running) [16:50] errors or just warning? [16:50] warnings [16:51] I think xfdesktop tends to print quite some theming related warnings [16:51] https://paste.ubuntu.com/p/sQQrtWDcNn/ [16:52] that's what i got (but it's still running) [16:53] I guess the next step would be to see what the xfce settings daemon does [16:53] XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon [16:54] it's responsible for setting up the environment [16:55] sorry busy a bit, checking if Lubuntu 18.10 is affected [16:55] lubuntu? [16:55] yes, much like Xubuntu it's an ubuntu-based distro based on... LXDE, iirc [16:56] (its [16:56] I know that [16:56] but why not check with xubuntu 18.10 or 19.04 (dev)? [17:00] because now i know that it's not XFCE-specific and not Xubuntu-specific: original Xubuntu 17.10 is not affected, fully up-to-date 17.10 is affected, Xubuntu 18.04 is affected, and Lubuntu 18.10 is affected [17:03] probably not that easy to go back and try to reproduce the bug again [17:03] as 17.10 is not supported anymore [17:03] right, but 18.04 is also affeccted [17:03] is Xubuntu 16.04 supported? [17:04] the update history of the 17.10 installation could be useful [17:05] Xubuntu 16.04 is supported for 3 years [17:06] meaning support ended like a couple of days ago? [17:06] pretty much I would guess [17:06] the Ubuntu core (main repository) has support for 5 years [17:08] so, you need to somehow pinpoint the update which breaks the desktop [17:09] also, the output of this command may give a hint: [17:09] XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon [17:11] update history is located in /var/log/apt/ [17:11] if still present [17:12] is it normal that it use a long time to execute? xfsettingsd [17:12] it has printed a lot of info but then just kinda froze [17:12] still running but not outputting anything [17:15] here is what it has printed so far, but it's still running: http://paste.ubuntu.com/p/rHM2xX5n2B/ [17:16] it should keep running [17:17] can you start xfdesktop now from another terminal window? [17:17] without DISPLAY [17:18] killall xfdesktop; xfdesktop [17:19] in the middle of a reboot but once it starts, sure [17:20] I mean after starting xfsettingsd manually [17:20] it seemed to launch fine according to the output [17:20] yup will do [17:21] with that I assume that xfdesktop should launch without issues also [17:23] got no output when running xfdesktop [17:23] i assume it daemonized [17:23] yup its running in the background [17:24] with icons visible? [17:25] no [17:25] icons are still invisible [17:25] / not present [17:25] maybe another [17:25] killall xfdesktop; xfdesktop [17:27] i added -w to that command, but nothing [17:27] no output and no icons [17:27] (i have confirmed with thunar that there is a text file on the desktop that should be a dedicated icon, if nothing else) [17:28] (thunar can see the files there as it should, when running thunar from the terminal) [17:30] btw a long time ago i learned that as a general rule of thumb, it's a good habit to add -w to your killall command, because by default killall does not wait until it's actually dead, that's what the -w flag does, and commands like `killall xfdesktop; xfdesktop` may try to start a new instance of xfdesktop before the previous has exited [17:32] (reminds me of "avoiding race conditions" in multithreaded programs :p) [17:32] not really sure what to suggest at this point [17:33] any luck with checking the update history? [17:33] 17.10 is dead, so it's not easy to check for changes online [17:33] as info about that release has been removed mostly [17:36] other than that, you could do some testing with a different distribution [17:37] you mentioned that the computer is from 2005 [17:40] |-/var/log/apt/term.log: text/plain: https://paste.fedoraproject.org/paste/TIMQhYSyRG7lQ8j2ATvXhA/raw?password=FmzCPPTd1FESETA82_zv [17:40] |-/var/log/apt/history.log: text/plain: https://paste.fedoraproject.org/paste/2YBhC~dq7OqCy3ba2NKy2A/raw?password=iFdnhC6RkoKWRO05GiIz [17:41] here is a list of everything in the folder but with a lot of noise.. i can decompress everything if there's interest: https://paste.fedoraproject.org/paste/owozYhTHLDyctYJtEaMKoA/raw?password=-mW7Op8iqY4JKY37x2Ck&fbclid=IwAR3-KlfQOLk-pL_ZjtTM-dJMQIOOAjEoMUjlqx7dMX8yHMz-u5gyfUxxeCM [17:41] but.. [17:42] both of those logs on show stuff after the problem occured, i have to decompress the other stuff and maybe it's in there [17:42] (logs from when the problem ocurred) [17:42] indeed [17:42] 2019-04-14 [17:42] that's not relevant [17:43] .. is there a command to just decompress every .gz file in a folder? [17:43] hans_: `for file in *.gz; do gunzip "${file}"; done` [17:43] ur `gunzip *.gz` should also work, I see... [17:44] 17.10 was supported until july 2018 [17:45] that should be the last date for updates [17:46] you installed a bunch of remaining updates today [17:46] so, when was the last time you applied updates? [17:47] I would assume before july 2018 [17:56] yeah i installed all remaining updates today, hoping that would fix everything; it didn't [17:57] here is links to most of the logs if anyone is curious, but i cba atm, testing if debian is affected. https://paste.fedoraproject.org/paste/IGOUTuG37a3enuS8t2-~xw/raw?password=sXcjp3c7aefDTRx476H4&fbclid=IwAR2oe2ZH9Cdvv2oJalQZ-cMYxJUwbBAwfaQCVJF8Dd2l6NuE9DEccyKEABs [18:03] history.log.1 2018-11-17 [18:04] the first thing I would try it to boot with an older kernel version [18:04] from the grub boot menu [18:05] i will try that, it has a lot of older kernels unpurged [18:05] but right now it's busy resizing the ext4 partition [18:07] (.. to be fair, it said "this operation may take a long time, are you sure?") [18:08] okay [18:08] but why do that while still debugging the problem? [18:11] because i'm making a dedicated partition for a debian installation to see if debian is also affected. i was probably stupid to not just try the debian-live system, but i couldn't find a live-version of the "non-free/cd-including-firmware/"-builds of debian and.. stuff [18:13] ok the resize is finished and i aborted the installation and booted back to xubuntu, but it's either set to hide the ask-for-kernel-menu (yes, it's an option to hide the menu while still having a countdown, and on some ubuntu distros that's even the default behaviour, which i find.. stupid), or it's set to 0-second-timeout (instant boot without asking), i'm not sure which yet [18:14] you have to press Shift after the BIOS phase [18:14] Shift, gotcha [18:14] well, hold it [18:15] great now it asked me [18:16] got -16 -17 -19 -21 -25 -32 -39 -46 [18:16] before that they are all 4.13.0- [18:16] and after that they are all -generic then 50% of them are (recovery mode) [18:16] guess i should just try -16 then? [18:16] -46 was installed on 2018-11-17 [18:17] should be the one that potentially broke the desktop [18:18] furthermore, intel-microcode was pulled in on that day too [18:18] that could be related, it has an intel cpu iirc (don't remember which) [18:19] Intel Core 2 6300 @ 1.86GHz according to /proc/cpuinfo [18:21] removing intel-microcode may be something worth testing also [18:21] oddly the reboot sequence got noticably slower after the partition resize [18:22] (i didn't remove space from the start, i removed space from the end of the partition) [18:22] I think it was added automatically in 2018 due to the recent intel vulnerabilities [18:22] but that CPU is way too old for any new patches anyway [18:23] uhm [18:23] does the older kernel make the desktop work? [18:25] is this a bad time to add that i added "nokaslr nopti" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub a long time ago? (long before the desktop broke) [18:26] not quite sure what those two change [18:26] take away some of the overhead of the KAISER/SPECTRE mitigations, iirc [18:26] .. but is unsafe [18:27] (as in, makes it easier for a hacker trying to exploit those vulnerabilities) [18:27] but for that mitigation to have any effect you would need the proper cpu firmware, no? [18:28] i think they're software solutions to hardware problems, unrelated to firmware [18:28] anyway, both the -16 kernel and the -39 kernel are affected still, they make no difference :( [18:28] hello, I need to install an old kernel ( ex 4.8 ) but apt-cache gives me only 4.15 and so [18:28] brainwash, should i try `apt remove intel-microcode` ? [18:28] (and reboot?) [18:29] hans_: sure. it's possible that the initramfs for -16 was updated to include the new microcode. [18:29] but it would be pretty odd if that's the reason for the breakage [18:30] running that it wants to also remove linux-generic and linux-image-generic [18:30] indeed [18:30] "the following additional blah blah" [18:30] should i continue? [18:30] it's a new dependency [18:30] you can reinstall linux-generic and linux-image-generic later [18:30] those are meta packages [18:30] kk [18:30] ok i removed them, should i reboot now or [18:31] right [18:31] kadiro: why do you need 4.8? [18:31] i also removed the custom kernel boot options (on the basis that, as non-default configurations they're probably less tested) [18:31] brainwash, for a specific module that was working but the new kernel replaced it [18:32] kadiro, named? [18:32] hans_, lirc_serial was replaced with serial_ir [18:33] I don't think that using an unsupported kernel version is the way to go [18:34] brainwash, come to think of it, the nopti option is automatically applied if the kernel bugs flags say they don't need it, iirc [18:34] brainwash, the problem that i fellow all the guides, docs, helps without success [18:34] .. removing intel-microcode and the custom boot options did nothing, problem is still present :( [18:34] i tried ir-keytable to replace lirc but nothing happen [18:34] brainwash, kernel cpu bugs flags* [18:35] ok, i guess i should go back to the debian test? [18:35] probably [18:36] I was thinking that my remote control is no longer work but the command mode2 still gives result also cat /dev/lirc0 and using my remote gives output and tested on windows just work out of a box [18:37] I lost my mind [18:37] you probably need to contact the module devs [18:38] installing 4.8 in ubuntu 18.04 may be possible, but it may be a bad idea [18:39] especially when you have that system connected to the internet [18:39] yeah i know that but i have no choice [18:40] 3 days without sleep trying to solve that problem and still no success [18:40] thank you brainwash for your help [18:42] In the docs they say that the new kernels can talk directly with any devices using ir-keytable but i can't make it happen [18:44] kadiro: did you find this? https://ubuntuforums.org/showthread.php?t=2403337 [18:46] brainwash, yes i did [19:26] brainwash, in case you're curious, Debian 9.8 with xfce desktop was also affected [19:27] kernel version? [19:28] is there some easy-ish way to check from the kernel? [19:28] err, check from the iso* [19:28] internet says 4.9 [19:30] probably correct [19:30] found references to Package: btrfs-modules-4.9.0-8-686-di [19:30] in the iso [19:30] so 4.9 yeah [19:31] ok found this in the iso: Depends: kernel-image-4.9.0-8-686-di, crc-modules-4.9.0-8-686-di, md-modules-4.9.0-8-686-di [19:33] not sure how much more time you want to invest into this [19:33] you could test with a non debian based distro [19:33] or with something from before 2018 [19:34] and then apply updates step by step [20:51] Morning/Evening All. I have a Atom Intel stick. It's a 32 bit UEFI and a 64bit CPU. I managed to get the OS to live boot by adding the 32bit EFI files to the USB however it's failing to install grub during the install process. I have manually added pool\main\g\grub2\grub-efi-ia32_2.02+dfsg1-5ubuntu8_i386 to try and resolve the issue but installer fails. Any ideas/advice on how to get this installed? Thanks :) [21:02] you're installing ubuntu to a usb stick? [21:02] (well, xubuntu) [21:02] KernelP8901, ^ [21:02] @hans_ from [21:03] Install media is USB and storage is EMMC [21:04] have you tried 32bit xubuntu btw? does that install cleanly? (xubuntu still has 32bit systems) [21:05] (probabky not what you want but it'd still be interesting) [21:06] That's the ISO I was using. I am now trying the AMD64 Xubuntu Beta (19.04) and this time I was lucky enough to find my USB3 to HDMI, VGA, Ethernet, USB 2.0 adapter so it can get online and download packages not included in the ISO