=== launchd is now known as l === M4he is now known as mahe [01:35] kernel: BUG: unable to handle page fault for address. [01:35] Full logs: http://sprunge.us/tToAun [01:35] Any thoughts? [01:36] man, I installed DeepinDD just to check it out and now even though I've removed it I get nothing but a tonne of "system has ecountered an error" messages asking me to report them [01:48] Diagon: nothing comes to mind immediately; I think, file a bug report against the kernel: ubuntu-bug linux [01:49] sarnold - thanks. could this be hardware? any way to investigate that? [01:49] Diagon: it's possible, but feels a bit unlikely to me for reasons I have trouble articulating.. [01:50] Diagon: memtest86 or memtest86+ might be able to help suggest if you've got memory failing.. maybe there's more notes elsewhere in dmesg about hardware problems [01:51] I checked dmesg, but nothing ... [01:52] Alright, will file bug, thanks. === keypushe- is now known as keypusher [02:07] Reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949247 [02:07] Launchpad bug 1949247 in linux (Ubuntu) "kernel: BUG: unable to handle page fault for address" [Undecided, New] [02:08] woot, thanks [02:12] Diagon: maybe run a memtest, i found two reports for native_queued_spin_lock_slowpath where hardware problems seems to be the cause. [02:13] Hello I’m trying to install Ubuntu on an old macOS’s [02:14] after the boot, I get a “check file systems” which I cancel with control C and then I’m stuck with the logo [02:14] let it check filesystems [02:14] Is there some background process going on? I can’t tell if I’m supposed to wait for something [02:14] I’m going to erase the whole disk though, why check? [02:15] its checking the USB [02:15] Why does it say file not found then? [02:16] for a bunch of files it was checking, it would just say that they’re not found [02:16] because the installer was not properly written to the installer media [02:16] Hmm is there something special I need to do for macOS? I used dad [02:16] try using balena etcher, it verifies proper writes [02:16] dd [02:17] dd also works, but it wont verify the data written [02:17] Ok thank you, I must’ve been unlucky I guess [02:17] it seems that no file is found, everything was “not fiund” [02:17] that it checked [02:18] https://unix.stackexchange.com/questions/75483/how-to-check-if-the-iso-was-written-to-my-usb-stick-without-errors [02:18] that's your CLI alternative for verifying correct writes [02:18] Nice thank you [02:18] also check the iso you downloaded has a correct checksum [02:19] (do this first) [02:19] I’ll try again tomorrow, my friend over video is tied [02:19] tired [02:19] right, thank you === M4he is now known as mahe [02:22] When creating/using column and bar chart,, how can I select wich 'data series' is a column and wich 'data series' is a line ? [02:23] you might need to name the application you're referring to there [02:26] oups!!! tomreyn, tought a was in libreoffice room [02:26] that's the other cubicle down the alley [02:27] lol [02:36] tomreyn - thanks, will do.... [02:38] Diagon: if this is a uefi booting system or recent hardware, you may want to use memtest86.com rather than memtest86 (which is in ubuntu and available from grub when bios booting) [02:39] * rather than memtest86+ [02:39] :thumbs-up: [02:53] <[itchyjunk]> Hi, when trying to use apt, i get an error. is it safe to run the command being recommended to fix the issue? [02:53] <[itchyjunk]> E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. [02:54] that's probably the right command to use, yeah [02:54] depending upon what happened before, you might *also* need to do something else, but running that command now should give you a good idea of what needs to be done [02:55] <[itchyjunk]> ty === brutex is now known as Guest8089 [03:37] Hi all. I've recently started using KDE/plasma. And it looks and feels great! However, I have encountered one issue: some applications have unreadable dialogues. This is a dialogue presented by GIMP: https://imgur.com/4xn8swo [03:38] There is actually text in the fields 'Template', 'Width' and 'Height'. But in these dialogues the text is black on a very dark brown. So the text is just about entirely invisible [03:51] bobdobbs: could it be a theme flaw perhaps? [03:51] lotuspsychje: I guess? But I'm not even sure what that means. [03:51] bobdobbs: try testing another theme, see if you can reproduce that [03:52] ok [03:53] lotuspsychje: k, I've switched from 'Breeze Dark' to 'Kubuntu'. The issue persists. [03:54] Problem persists if I switch to 'Breeze' [03:56] bobdobbs: tnx for testing, i dont seem to find bugs under template right away on gimp; https://bugs.launchpad.net/ubuntu/+source/gimp/+bugs?orderby=importance&start=0 [03:56] lotuspsychje: I'm installing a bunch of themes now from the Global Themes UI. I didn't know that there were so many! [03:57] bobdobbs: so are you claiming switching themes, you cant read the text because too dark? [03:57] lotuspsychje: I should add: I've had this issue over the years - pretty much every time I've switched from Gnome to KDE. I've just never tried to deal with it before, because I've never settled into KDE [03:58] lotuspsychje: that's rught, yes [03:59] bobdobbs: maybe you could talk to the kubuntu crew first, but if you cant solve it, you could file a new !bug [04:01] lotuspsychje: At this point I'm assuming it's not a bug. I figure it's more likely to be an issue that can be solved by tweaking a setting. I think that basicaly I'm running an app built for Gnome within a KDE environment. So maybe the GIMP UI's are picking up some UI settings from Gnome, some from KDE.. [04:01] I dunno. That's a wild guess really [04:02] But... where can I talk to the kubuntu folks? Do they have an irc channel? [04:02] bobdobbs: if something isnt working by default, i would assume its a bug [04:02] bobdobbs: #kubuntu and #kde [04:02] thanks === Hash is now known as EnchanterTim === rexbinary_ is now known as rexbinary === EnchanterTim is now known as HAsh === HAsh is now known as Hash [05:48] anyone else use linux and unix? === henry404082 is now known as henry40408 [06:11] ciao a tutti === mjt is now known as m === m is now known as mjt [06:17] what are the most used commands on ubuntu? [06:17] ls [06:17] cd === henry404081 is now known as henry40408 [06:18] nano! [06:18] i tried nano once and it was kinda fresh for me [06:18] ctrol + buttons to control stuff [06:18] ls, cd... [06:18] thank you [06:18] vi? [06:19] yukiup: do you know about vi [06:19] yes [06:19] but i like nano [06:19] there is also grep [06:19] yeah i see people prefer nano [06:19] nano and vi [06:19] oh [06:19] grep! i have seen it before :D [06:19] less [06:19] rm [06:20] man [06:22] sudo, apt [06:24] manual? [06:24] oh yes [06:24] sudo su === henry404086 is now known as henry40408 [06:24] :p your not supposed to use su! [06:25] chmod [06:26] TJ-, If you have any time today, I' d love to discuss my ubuntu 20.04 setup using your article: https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019. I have started my VM linked to my physical SSD and I'm in Busybox, since grub is unable to find /dev/vgubuntu-lvroot [06:45] list [06:46] !list [06:46] artu59: No warez here! This is not a file sharing channel (or network); read the channel topic. If you're looking for information about me, type « /msg ubottu !bot ». If you're looking for a channel, see « /msg ubottu !alis ». [06:51] * dodocrypto hi all back [07:03] Hello. I've used dd to write Hiren's BootCD onto USB... but how to make it bootable? [07:04] Startup Disk Creator won't accept the ISO. [07:13] I have a weird problem with Ubuntu 20.04, probably more an issue with my onboard Intel gigabit NIC. I have a ROG Strix I think, on this system, and periodically, randomly, the (wired) network just stops. [07:13] Local network, everything, then it starts working again after a bit. [07:15] Any suggestion on where to start? I can't see any immediate solution other than rebuilding kernel and seeing if I can get specific with an intel nic driver, since I'm using the latest update for 20.04. [07:23] l0de [07:24] |shark| [07:26] unixbeard: do you have any other ubuntu devices on the same network? Does the problem happen on them? If so, it would be an issue with the dhcp renewals [07:26] If not, check the output of the `dmesg` command for kernel warnings/errors [07:27] And, what's the output of `ip a` when the issue happens.... [07:38] I want to shutdown my VMs at reboot or shutdown and switch them back on when the machine boots. Where can I insert these commands? Or do i have to write a systemd service for it? [07:40] pycurious: you can type `sudo crontab -e` and add an "@reboot command" line there [07:40] Or of course you can add a systemd unit [07:52] alkisg: I do, and the problem does not happen with them. I have the same hardware (sans video card) on another computer running windows 10, and it doesn't seem to have this problem. [07:52] Nitrigaur: I'm just waking up; need a coffee [07:52] TJ-, Enjoy :-) [07:52] alkisg: All the static systems have long leases, and I checked with pfsense (had similar thoughts...) but maybe that is somehow an issue. [07:53] unixbeard: ok, start with `dmesg` and `ip a` when the issue happens [07:54] alkisg: frustratingly I don't get any issues from dmesg. [07:54] unixbeard: and `ip a` shows that the ip/lease are still active? [07:54] alkisg: I double checked my mac address in pfsense and the system has a static lease. [07:54] Well, I will try that soon when it randomly drops. [07:55] A static reservation doesn't always mean an infinite lease lifetime [07:55] It might mean "just give it the same ip when it asks again" [07:55] OK, let's see then [07:55] I have not been enjoying new hardware; my monitor doesn't detect activity on this workstation, but I think it was in sleep mode? I installed caffeine to just disable it even though I thought I disabled all sleep related crud on here. [07:56] Okay, yeah, I am not sure. It shows no start/end time for lease on static assigned stuff, but that's pfsense/bsd and I'm not sure how the dhcpd works on there. [07:56] The non-static lease stuff does have start/end times listed for lease. [07:56] You can check the monitor status over ssh, without waking it up locally [07:56] On the local network, ssh/ping dies inbound/out on that system. [07:57] So I tried to ssh to it from my nearby windows system, and ping it, and it is effectively dead after it goes to sleep. I can ssh to another ubuntu system with mostly similar hardware upstairs. [07:57] When monitor goes off? [07:57] Or when the intel issue happens? [07:57] Ah if the system goes to sleep, its a completely different thing than if the monitor goes to sleep [07:57] Suspend/resume might be buggy due to a lot of kernel drivers or system hooks [07:57] Well the monitor is another PITA, it's a curved gaming monitor and I have it plugged into a power switch because it has a hardware problem (samsung g7?) [07:59] So I just power cycle it when I need a display, otherwise it will not 'wake up' and detect either system if it's been idle long enough. There's actually a hardware issue there ... I declined having it repaired, anyway. [07:59] Nitrigaur: OK, I'm (almost all) here although brain may be slow! Your summary about being it booting into the busybox shell would mean GRUB stage was fine but the initialramfs has a problem [08:04] unixbeard: what precise Intel device is it? what does this report? "lspci -nnk -d ::200" === gggpkm__ is now known as gggpkm [08:05] unixbeard: sounds like an issue we see mostly with I219-V I think is the model, and its EEE power saving modes [08:08] TJ-, Well, in my busybox (VM) I can only see /sda devices, no nvme* at all [08:09] TJ-, My girlfriend just PM'd me that she's coming down and she expects a breakfast. So, I have to tend to that first. [08:10] Nitrigaur: unless you're doing pass-through / VFIO that is what I'd expect the hypervisor to do. Which hypervisor are you using? [08:11] Nitrigaur: this is why we use UUIDs and file-system labels rather than absolute device names - for portability. Device names can change between boots depending on when the kernel sees the device and intialises the device relative to other similar devices [08:18] TJ-, I'm using KVM [08:18] TJ-, update: Bread is in the oven, so breakfast is sorted ;-) [08:20] TJ-, I do see a /cryptroot, so that's encouraging, isn't ? [08:23] TJ-, inside that cryptroot is a crypttab with only 1 byte in it. That's a bit strange [08:25] Nitrigaur: that's the problem then! [08:26] TJ-, Should I chroot into the vgubuntu-lvroot from my terminal to see what's going on, or to test some more? [08:26] Nitrigaur: find the crypt device so you can manually unlock it [08:26] (from inside the busybox shell) [08:26] Nitrigaur: try "blkid" in busybox [08:28] TJ-, I see it and it does have the same UUID as mentioned as in grub, so that went well. Strange that it is not mounting properly from grub [08:30] TJ-, I have successfully opened both crypted devices and I can see them in my /dev/mapper [08:30] Nitrigaur: at this stage it has /nothing/ to do with GRUB; GRUB is long gone. Now it is a problem created by the crytpsetup hooks when update-initramfs was called [08:30] Nitrigaur: good, so now try "vgchange -ay" [08:30] Nitrigaur: that should if not already, detect the VG and activate the LVs [08:31] TJ-, Yes, it did :-) [08:31] now 'exit' and the init should resume and boot [08:32] That's right, I'm in now. So how do I go about fixing my initramfs permanently? [08:33] TJ-, ^ [08:33] Nitrigaur: first check the real /etc/crypttab is valid. Best to pastebin it for me so I can be sure there's no weird syntax that'll trip up the cryptsetup hook scripts [08:35] TJ-, I will in a bit, but I'm going to join my Girl Friend first for some Breakfast. Can't keep her waiting ;-) . Thank you so much again. I'll return after breakfast. [08:36] TJ-, I' ll pastebin my crypttab first though [08:39] TJ-, Here you go and thanks in advance for your analysis: https://paste.ubuntu.com/p/5m7jwSCcRT/ [08:43] Nitrigaur: that looks fine, so when you're back we can test what update-initramfs is doing, with "sudo update-initramfs -v -u -k $(uname -r) |& tee /tmp/initrd.log" and then "T=$(mktemp -d); pushd $T; sudo unmkinitramfs /boot/initrd.img-$(uname -r) . ; cat ./main/cryptroot/crypttab " === gggpkm__ is now known as gggpkm [09:08] def a hardware/kernel problem [09:09] unixbeard: did you see my earlier comments? [09:09] TJ-: no, I am running in a screen now so I won't lose text again. [09:09] unixbeard: sounds like an issue we see mostly with I219-V I think is the model, and its EEE power saving modes [09:09] I went looking at my old dmesg and /var/crash to find (among other things) a potential issue with my video card. [09:09] unixbeard: what precise Intel device is it? what does this report? "lspci -nnk -d ::200" [09:09] Oh! I also saw that, eeepc stuff (hah) [09:10] One sec. [09:10] TJ-: This caught my eye: kernel: eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTS ? [09:11] TJ-: using igc, Ethernet controller [0200]: Intel Corporation Device [8086:15f3] (rev 02) [09:12] TJ-, btw, on this machine I'm working on 21.10 instead, though that *should* not make much of a difference [09:12] ...but like I said, I also *just* got a crash in gnome-shell related to nvidia I guess, so I'm using v. 470 over 460. Hopefully that takes care of that particular issue. [09:12] unixbeard: check the eee state with ethtool [09:13] unixbeard: also, I'd suspect the mobo's firmware ACPI since that affects power-saving configuration before OS starts [09:13] unixbeard: can you share the complete kernel log? " journalctl -k | nc termbin.com 9999 " [09:14] TJ-: Maybe, sec. [09:14] TJ-: I don't see anything about EEE state using ethtool on my device. [09:15] EEE status: disabled <- sorry [09:15] for others who are interested: "ethtool --show-eee " [09:16] TJ-, I have executed both the mkinitramfs and the extraction of the initramfs image [09:16] Whats the recommended way to copy over a dead project to a new distro? [09:16] ie an app that was in your existing install but likewly won't be in the new ubuntu since project appears dead [09:17] unixbeard: so now we need to know *exactly* what the symptoms are when it fails. does the link goto state DOWN, does it just lose its DHCP lease, does "tcpdump -vvni " still show two-way traffic [09:17] pikapika, does that package have source code? In that case, you could just compile it yourself [09:17] I'll have to see if it does [09:17] Nitrigaur: does the ./main/cryptroot/crypttab have the correct entry? [09:19] TJ-: Hmm, can I message the termbin link to you? [09:20] TJ-, I' ll check to see if the UUID's match, just a sec... [09:20] unixbeard: it's OK to share here, it's only the kernel log [09:20] I should save up the source before it vanishes [09:20] or even worse if it becomes some paid close source thing [09:21] pikapika: you can always fetch the most recent source from the archive and do a dpkg-buildpackage locally [09:21] Oh right, yeah good point that the Ubuntu repos themselves would have a source code [09:21] TJ-, Yes, it does :-) [09:21] TJ-: https://termbin.com/sz7t [09:21] so I could save up the stuff from my current ubuntu [09:21] and copy it over in case the new ubuntu has removed it [09:22] Nitrigaur: OK, so now do another boot attempt with what we know is a known-good configuration. Ensure you're booting the exact same kernel version so it used this initrd-img we've just checked. [09:22] TJ-, aye. Rebooting now... [09:24] unixbeard: 1st thing I'd do is update the mobo firmware to the lateset version. Currently it is on 0805 7/1/2020 but latest is 2423 26/8/21 [09:25] unixbeard: and there are a few "Improve system performance" generic isses listed in the various version changelogs https://rog.asus.com/uk/motherboards/rog-strix/rog-strix-b550-e-gaming-model/helpdesk_bios [09:25] TJ-, works straight away :-) [09:25] Nitrigaur: so that somehow got corrupted [09:26] TJ-, I'll try booting from the latest kernel now, to see if that works as well. What I noticed is that I got two shim-related lines, that I did not see during the previous boot. [09:29] unixbeard: also, there may be a microcode update in those firmware updates that may fix the "__common_interrupt: 1.55 No irq handler for vector" happening on each core [09:30] unixbeard: and related to the GPU: 2pci 0000:07:00.0: 32.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x16 link at 0000:00:03.1 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)" [09:31] TJ-, I have made a screenshot. Do you want to see that (btw.: The new kernel boots up fine as well ;-) ) What I' m really curious about is what went wrong. I would like to preserve this setup along with an ansible-script so I can recreate my machine from scratch should I need a new machine or when I decide to scrap everything )except my data of course and start with a fresh machine. [09:32] TJ-: it just did it again, the network indicator in the upper right of my dekstop had a question mark over it, ip a said the link state as up though. [09:32] Nitrigaur: no idea how the crypttab got corruped that way and it'd be very hard to track down unless you can reproduce it [09:33] unixbeard: arghh, and I sent you some messages! [09:33] unixbeard: what was the last you saw from me? [09:33] TJ-: I'll update the firmware, yeah. [09:33] TJ-: I'm running in a screen so no problems. [09:33] unixbeard: oh yeah, you did say :) [09:34] Also it didn't go down long enough to end the session. [09:34] TJ-, I have already reproduced it on a 20.04 based VM on my work PC. This machine had exactly the same flaw as my last setup. i.e.: It dropped to Busybox. [09:34] unixbeard: when it dies next time have a "sudo tcpdump -vvni enp6s0" ready to go and see if there's two-way traffic still (broadcasts and multicast traffic most likely) [09:35] Nitrigaur: and you're doing this via ansible playbook and scripts? [09:35] TJ-: queued up, thank you! [09:35] TJ-, Not yet, but I plane to ;-) [09:35] TJ-, plane -> plan [09:35] I am thinking at this point it's problem a problem that will wind up being resolved in firmware. [09:35] it's probably a problem even [09:35] Nitrigaur: so this has happened twice but with you building the installs manually? [09:36] TJ-, Yes [09:36] Nitrigaur: I have to point the finger at you then :D [09:36] TJ-, Fair enough :-D [09:37] Nitrigaur: the only way I can see that happening is if update-initramfs is run before /etc/crypttab has been fully configured [09:37] TJ-, I *did* follow your instructions though. [09:37] Nitrigaur: lots of people have done that and it has worked so there is likely something in your workflow that causes this [09:37] TJ-, Let me check in my post-setup.bash script... [09:38] TJ-, update-initramfs is all the way at the bottom, so it is not sequence related. [09:39] just upgraded to Ubuntu 20.04.3 LTS and now OpenDKIM will not start up Here is the output from sudo systemctl start opendkim and journalctl -xe https://dpaste.com/DN92JDJE3.txt [09:40] Nitrigaur: let me state some facts. 1. as initrd.img has a /cryptroot/crypttab that tells us cryptsetup-initramfs hooks were triggered when "update-initramfs" ran. That means they saw an entry in /etc/crypttab that is a container for the root-fs. The hook script then should read /etc/crypttab line that matches, then write a modified form of that line to the /tmp/.mkinitramfs/cryptroot/crypttab file [09:40] in the initrd.img it is assembling. [09:40] sorry if I missed a previous response [09:40] Nitrigaur: from that you can see that either the 'write' process failed or, when the system boots, somehow that file is corrupted within the initrd-img, which seems more unlikely [09:41] I'm using OpenDKIM Filter v2.11.0 [09:41] I can't seem to find an OpenDKIM channel [09:41] Nitrigaur: in your script you need to add a step to use unmkinitramfs and inspect the /cryptroot/crypttab to ensure it was written correctly, like we did manually earlier [09:42] TJ-, I'll postbin my exact setup-script. Note that I'm running this line by line, by copy-pasting from it into the terminal, or I cannot enter my LUKS keys. [09:43] Nitrigaur: ok :) [09:43] BCB: check "journalctl -u opendkim.service -n 300" for more clues [09:43] TJ- will do. thank you [09:44] TJ-, Here you go: https://paste.ubuntu.com/p/B2CQvxWGn9/ [09:44] BCB: locate the most recent "Starting ..." and hopefully you'll get a clue [09:45] TJ-, It's probably just a typo somewhere. It mostly is ;-) [09:45] TJ- Nitrigaur "opendkim: milter socket must be specified" [09:48] TJ-, I cannot thank you enough for walking me through this. Very much appreciated :-D IT was my first taste at actually fixing things from Busybox and I have been running Linux for about 24 years now. [09:48] Nitrigaur: nothing obvious there, so as I said check the actual content of the created initrd.img-$version using unmkinitramfs === denningsrogue9 is now known as denningsrogue [09:52] TJ-, I will. I'll restart my laptop proper this time to see if it works outside my VM as well. Thanks again and have a lovely Weekend :-) [10:00] TJ- mail.log is reporting: key data is not secure: /etc/opendkim is writeable and owned by uid 106 which is not the executing uid [10:00] TJ- private key is set to: -rw------- 1 opendkim opendkim 887 Dec 28 2016 default.private [10:00] ??? [10:01] TJ- Oct 30 05:52:40 server opendkim[33759]: vital: key data is not secure: /etc/opendkim is writeable and owned by uid 106 which is not the executing uid (0) [10:02] BCB: the messages says "/etc/opendkim" not "/etc/opendkim/default.private" [10:02] BCB: so secure the directory correctly [10:02] BCB: also it sounds the process is starting as UID 0 rather than its expected ID? [10:03] BCB: is 106 opendkim ? === stoned is now known as EnchanterTim [10:03] TJ-: Got a broken pipe ... argh. [10:03] TJ- how do I tell [10:03] BCB: "getent passwd opendkim" [10:04] unixbeard: call a plumber! :P [10:04] TJ- opendkim:x:106:115::/var/run/opendkim:/bin/false [10:04] do I chmod 600 the opendkim folder [10:04] BCB: so that is the 106 mentioned. [10:05] BCB: I think you need to figure out why opendkim service is reporting the UID issue [10:06] BCB: generally what happens with system services is, they're initially started as root but then once they're done essential things that require UID 0, they switch to a less privileged user, which in this case will be opendkim (106) to run as [10:07] BCB: you said this is an upgrade to 20.04.3 ... what was the previous release version? this looks like a letover from the previous version [10:08] TJ- 16.04.7 LTS [10:08] I upgraded twice [10:08] this week [10:14] BCB: that is likely the cause then. Also, the package is untouched by Ubuntu, it is imported directly from Debian, so maybe there are some Debian bug reports about this [10:20] TJ- I'm reviewing an installation guide for OpenDKIM on Ubuntu 20 [10:23] ubuntu error [10:24] ubuntu error === jordan is now known as Alabalistic [10:51] Hello, I'm on 21.10, I'd like to use Eclipse to run some java code. I did sudo snap install eclipse --classic, then I believe I did sudp apt install default-jre (but it was a long time ago so I'm note sure). At least I have "default-jre/impish,now 2:1.11-72build1 amd64" installed [10:51] But when I try to run the code, it says "ava.lang.UnsupportedClassVersionError: Main has been compiled by a more recent version of the Java Runtime (class file version 59.0), this version of the Java Runtime only recognizes class file versions up to 55.0" [10:51] So, can I just class file version 59.0 on Ubuntu? [10:54] I have "OpenJDK Runtime Environment (build 11.0.12+7-Ubuntu-0ubuntu3)" and "openjdk version "11.0.12" 2021-07-20" [10:57] TJ- it was a permission issue. Khepra in ##email suggested chmod and chown cmds. All set now. Thank you. [10:57] I tried installing openjdk-18-jre but it doesn't seem to fix it [11:00] BCB: it looked that way, glad it is solved [11:08] Is it possible to get the icons below my favorites on the dock (bar on left side of the screen) from re-arranging themselves? I find it very distracting. === mmebsd is now known as linsux [12:30] <_ganapathi_> In some cases building debian file might required dsc file. is there any way to generate dsc automatically ?. like generating tar file and adding checksum into dsc file . [12:41] _ganapathi_: "dpkg-source --build ..." [12:45] <_ganapathi_> Ok. Thanks. [12:49] Hi folks [12:53] <_ganapathi_> dsc have checksum. its mandatory ?. or optional. [12:59] ? [12:59] ! [13:05] <_ganapathi_> debian build have dsc file. some builder required dsc file. usually dsc file have checksum of tar.xz file . so am asking here as checksum line on dsc file is mandatory for build or not [13:14] _ganapathi_: there'a at least one channel related to debian packaging on oftc, this may be a better place to get help with it. [13:22] There's a weird problem with my Ubuntu 20.04. When I first turn on the laptop, it is extremely laggy for about 10 minutes. I mean, so bad that the mouse pointer will barely work and the keyboard will barely type letters. All of the windows take much longer to open, etc. So virtually unusable. When I leave the laptop alone for 10-15 minutes. This strange lagginess goes away. Has anyone encountered this problem before? [13:26] Andy_Flatline: is this a fresh 20.04 installation, or did you upgrade? which cpu and how much RAM? [13:27] to answer the last two questions and enable us to look for hardware / firmware related problems, you could run this to share the first 1000 lines of your system log: journalctl -b | nc termbin.com 9999 post the url it reports here === Hash is now known as OpenSores [13:29] No, it's been on this laptop for about 6 weeks. The CPU is an Intel Core i5-5200U. I have 8GB of ram. [13:30] that should be fine, so it has to be something else (and the logs might help) [13:32] the symptoms you're discussing would match "tracker", a file indexer (not user tracking), but this is not usually noticable unless you're short of ram or with a slow cpu [13:36] The command you gave me for the log isn't doing anything [13:40] Hi. Is it okay that stopping and disabling snapd breaks apparmor systemd unit? [13:40] yes [13:40] but take snapshots before doing that [13:40] too late [13:41] thats okay [13:41] you should always take backup [13:42] no point, I don't know how to restore [13:42] app armor sounds like something important for security or something [13:42] kind of [13:42] but you can restore it [13:42] shouldn't I just delete the conflicting /etc/apparmor.d/usr.lib.snapd.snap-confine.real? [13:43] nope [13:43] why? I disabled snapd [13:43] and that file has snapd in its name [13:43] so it's a metastasis of that snapd cancer [13:43] you should take that file and rename it. [13:43] okay [13:43] Andy_Flatline: try this: dmesg | nc termbin.com 9999 [13:44] Andy_Flatline: it wont work if the system is offline, though? [13:47] how does apparmor know about /var/lib/snapd/apparmor/? [13:47] found new metastases [13:49] snapd uses apparmor a lot for confinement, it's logical to me that there are many relations between the two. [13:49] I disabled snapd [13:49] apparmor now fails to start [13:49] it's not logincal that if snapd uses apparmor that apparmor might break when snapd is disabled [13:50] probably not, but i don't know what the error message is or what ubuntu version you're referring to. and i don't really want to support snap, so... [13:51] no one wants to support snap [13:51] not true, some people do so regularly here [13:51] `apt list --installed | grep snap` says I have `gir1.2-snapd`, `libsnapd-glib1` and `libsnappy1v5` [13:53] well, moved that cancer away from those locations and apparmor now starts fine [13:53] dunno what it does though [13:54] that might be part of the problem [13:59] just found out that linux mint is basically ubuntu-snap+cinnamon and if cinnamon is something like xfce (or can be replaced with it) - then I finally found what to migrate to (currently stuck with ubuntu 18.04 and it's support gets slowly dropped by the world) [14:44] Hello I'm trying to install kubuntu on an old mac, from usb. I see the Kubuntu splash logo, I cancel the filesystem check, and then it gets "stuck" in the splash screen. Is something supposed to happen? [14:45] euouae, most of the times, is a graphic issue; you might use 'nomodeset' ; what's your video card ? [14:46] I'm not sure [14:46] How to set nomodeset? [14:46] !nomodeset [14:46] Systems with certain graphics chipsets may not boot properly out of the box. "Temporarily Add a Kernel Boot Parameter for Testing" as discussed at https://wiki.ubuntu.com/Kernel/KernelBootParameters to add the "nomodeset" parameter there. [14:49] It has `quiet splash ---` [14:49] What's that --- doing there? Write nomodeset after it? [14:50] yes [14:51] no, i mean before --- , just after splash [14:51] got it [14:59] ioria It still seems to be 'stuck' in the splash [14:59] Is there a way to look at what happens in the background? [14:59] euouae, esc iirc [15:00] euouae, how did you do the usb ? [15:00] I just flashed it with balena etcher [15:00] I didn't do the disk util preparation step with the partition. Maybe I should try that [15:01] euouae, how much ram do you have ? [15:01] I think it's 2GB [15:01] euouae, for kubuntu it's not enough [15:01] Do you think it's a ram issue then? [15:02] but it should install anywys [15:02] nope [15:02] euouae, 2G is good forlubuntu nowadays [15:03] esc doesn't do anything [15:04] euouae, alt+f1 (or fx) [15:04] alt+f1 doesn't do it [15:05] neither ctrl/cmd/option +f1 [15:05] euouae, i suggest you make the usb again (maybe try with lubuntu) [15:06] okay, thank you [15:06] ok [15:08] Does lubuntu have ftp releases? [15:08] I can't download https downloads because the certs on macOS are invalid and the download interrupts for some reason [15:09] euouae, torrents ? [15:11] euouae: there are also plain http mirrors [15:13] http://cdimage.ubuntu.com/lubuntu/releases/ [15:13] thanks! [15:14] you're welcome [15:28] Ok currently looking at the lubuntu splash screen and waiting [15:30] euouae: tap Esc to see what splash is hiding :) [15:30] good idea, it works this time :) [15:31] something about correcting GPT PMBR size mismatch by "write". 16+0 records in, 16+0 records out, and that's where the cursor is blinking [15:34] yeah nothing else is happening [15:37] This is roughly what I'm looking at, https://paste.debian.net/1217384/ I wasn't able to make out everything from the picture I took [15:38] I think I need to do the step where I set up the partitions right before I flash the medium [15:41] euouae, try rufus with the default settings : https://rufus.ie/en/ === diskin is now known as Guest6822 === diskin_ is now known as diskin [15:57] I've tried with disk utility, I still get the same messages except one more that talks of the 4th partition having an ext4 filesystem [16:00] euouae: what are you trying to flash? which iso? [16:00] the amd64 one [16:00] I've tried with kubuntu and lubuntu [16:00] The 21.04 version === yuta is now known as QueiQuomuro [16:00] euouae, if you are on a unix-like system, you can also use 'dd' [16:03] I guess there's something I'm forgetting to do or something is going wrong but I don't know what exactly [16:07] I'll use rufus. Disk Utility didn't work out... I'm wondering if the hardware is 32bit? I doubt it but not sure [16:08] oh wait, things are happening all of the sudden! [16:08] Sometimes the installer really hangs for ages [16:10] But you should really install 21 [16:10] 10 [16:10] Support for non LTS releases is not long and you will need to update soon [16:10] So better start with a current release [16:11] wait, isn't 21.04 the LTS? [16:12]