[00:52] <glestrade> hello, I'm trying to install some nvidia drivers onto my machine (running 18.04), and I'm getting the following error:
[00:52] <glestrade> https://paste.ubuntu.com/p/9D8MQh9BMK/
[00:53] <glestrade> does this mean I have to load into a different kernel version?
[00:53] <sarnold> glestrade: probably it just means you've got extra kernel packages installed without matching header packages
[00:53] <sarnold> glestrade: check out the output from dpkg -l 'linux*' | grep ^ii
[00:54] <Bashing-om> glestrade: "kernel headers for this kernel does not seem to be installed." >> what shows ' dpkg -l | grep linux- ' ?
[00:57] <glestrade> output for both was similar -> https://paste.ubuntu.com/p/wj8GYGGg2j/
[00:58] <glestrade> I know for a fact when I rebooted, I couldn't see that the drivers had loaded
[00:59] <glestrade> with nvidia-smi
[00:59] <glestrade> I am following this tutorial: https://towardsdatascience.com/deep-learning-gpu-installation-on-ubuntu-18-4-9b12230a1d31
[01:00] <Bashing-om> glestrade: Please also show ' uname -r ; lsb_release -a ' .
[01:01] <glestrade> https://paste.ubuntu.com/p/RjXxdhxW8y/ <- kernel version & OS
[01:02] <glestrade> was pretty sure on that already, but did the comman
[01:02] <glestrade> *d
[01:04] <Bashing-om> !info linix-image-generic bionic | glestrade
[01:04] <Bashing-om> !info linux-image-generic bionic | glestrade
[01:06] <glestrade> hmm yeah I'm fairly newbish here, I don't know if I have enough context to glean much from that
[01:07] <Bashing-om> glestrade: ^^ ' sudo apt update ; sudo apt full-upgrade ' reboot into the bionic install - now running the latest,4.15.0.151, kernel ?
[01:08] <Bashing-om> glestrade: By the way - a serious CVE is now patched in latest kernels.
[01:08] <glestrade> I didn't see that in the boot menu
[01:09] <Bashing-om> glestrade: Did the full-upgrade ? show us then ' ls -al /boot/ .
[01:09] <glestrade> and I'm not putting much personal data on this OS for now, so if I need an old kernel it's probably safe
[01:09] <glestrade> let me check...
[01:11] <Bashing-om> glestrade: In the event that you are trying to build with the 4.2.0-42-generic kernel - is a fact that the heders are NOT installed.
[01:11] <Bashing-om> headers*
[01:13] <glestrade> Bashing-om: what I tried was something like 'sudo apt-get install linux-image-4.15.0-147-generic'
[01:13] <glestrade> and on the same line for the headers.
[01:14] <glestrade> what should hypothetically work for 4.2...generic... right
[01:14] <Bashing-om> glestrade: Why would you do that - already installed - see your https://paste.ubuntu.com/p/wj8GYGGg2j/ paste :D
[01:15] <Bashing-om> glestrade: I maje a guess that 3.2 series is not supported in the bionic repo . lemme check what the release is.
[01:15] <Bashing-om> make*
[01:16] <Bashing-om> 4.2*
[01:16] <glestrade> First of all I had no coffee today
[01:16] <glestrade> okay so you're saying that 4.15 is in fact installed then?
[01:16] <glestrade> I guess that full-upgrade is to take my kernel version up?
[01:17] <glestrade> which there's no reason not to, it sounds like
[01:17] <Bashing-om> glestrade: Coffeee is a must ! I do not hold myself responsible for anything before my 2nd cup.
[01:18] <glestrade> I'm going to join on my phone so I can reboot when I need to
[01:19] <FaTaL_gg> I dont know a whole lot about snap yet... but can anyone help me troubleshoot the following complaint from syslog:
[01:19] <FaTaL_gg> snapd[1491]: stateengine.go:150: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: dial tcp: lookup api.snapcraft.io on 127.0.0.1:53: server misbehaving
[01:21] <sarnold> FaTaL_gg: what do you get for 'host api.snapcraft.io' or 'resolvectl query api.snapcraft.io'? error messages or reasonable looking output?
[01:21] <FaTaL_gg> api.snapcraft.io has address 91.189.92.20.....
[01:21] <FaTaL_gg> 6 different ips
[01:22] <FaTaL_gg> ohhhh
[01:22] <FaTaL_gg> but....
[01:22] <Bashing-om> glestrade: Uh Huh v4.2-wily/ << long time End_Of_Life !
[01:22] <Bashing-om> !wily | glestrade
[01:22] <FaTaL_gg> I constantly have issues on reboot, where isc-dhcp-server is foobar'd. I need to restart it to get it working
[01:23] <glestrade_> okay joined from my macbook instead. I need a better IRC client on my android
[01:23] <glestrade_> maybe I should write one...
[01:23] <sarnold> FaTaL_gg: oh, hmm, you think your dhcp server is mucking with things?
[01:23] <glestrade_> gonna try those commands and reboot
[01:24] <sarnold> glestrade_: you may have missed: < Bashing-om> glestrade: Uh Huh v4.2-wily/ << long time End_Of_Life ! < ubottu> glestrade: Ubuntu 15.10 (Wily Werewolf) was the 23rd release of Ubuntu. Support ended on July 28th, 2016. See !eol and https://ubottu.com/y/wily
[01:24] <glestrade_> thx
[01:24] <Bashing-om> glestrade: Uh Huh v4.2-wily/ << long time End_Of_Life !
[01:24] <Bashing-om> !wily | glestrade
[01:26] <FaTaL_gg> sarnold,indeed. we have talked before. I never solved it
[01:26] <sarnold> :(
[01:27] <glestrade_> btw, I was also having trouble getting a vnc server up and running before. but I have a sneaking suspicion that it also had to do with the display drivers
[01:27] <FaTaL_gg> I guess its because It thinks I have no interfaces configured.... probably because I disabled ipv6,and isc-dhcp-server insists on running ipv6
[01:27] <glestrade_> it was complaining that there was other Xorg instances I think
[01:28] <glestrade_> *graphics drivers
[01:28] <FaTaL_gg> the whole.... failson boot.... but if I delay its start,or restart it, it works
[01:28] <glestrade_> ooh it added a boot menu entry
[01:28] <glestrade_> I’m going to try it
[01:31] <glestrade> hmm, didn’t see 4.15 on the boot menu, despite it said it had added an “EFI boot menu entry"
[01:35] <Bashing-om> glestrade: Let us back up amd regroup so we are all on the same page and line. for starters on drivers Nvidia says "Note that many Linux distributions provide their own packages of the NVIDIA Linux Graphics Driver in the distribution's native package management format. This may interact better with the rest of your distribution's framework, and you may want to use this rather than NVIDIA's official
[01:35] <Bashing-om> package.".
[01:37] <Bashing-om> glestrade: ^ with the above be aware that Nvidia and Ubuntu have a close working relationship.
[01:38] <glestrade> what I don’t know is which drivers tensorflow will like
[01:39] <glestrade> I think it’s using the default driver now and can’t scale up to the resolution I know this screen has
[01:39] <Bashing-om> glestrade: 1) we want up and booting the latest kernel 2) the driver will be suited to the card 30 have the system install the driver it thinks is correct. // As easy as that :D
[01:42] <glestrade> step 1 appears to be a problem for whatever reason
[01:44] <Bashing-om> glestrade: Hokay .. so we see what is going on getting the latest kernel installed . pastebin ' ls -al /boot/ ' so we see what is installed.
[01:47] <glestrade> https://paste.ubuntu.com/p/cB5XFznffp/
[01:47] <glestrade> looks like it’s “installed”.. grub didn’t see it when I visited tho
[01:51] <Bashing-om> glestrade: Yeah - grub will not pick it up - yet. For example, mine " 24 Jul 21 15:45 vmlinuz.old -> vmlinuz-5.4.0-77-generic ". We got some works cut out for us. // What kernel are you booting ? Maybe if we get rid of that 4.2 version kernel that has *NO* support we can move forward ?
[01:54] <glestrade> I have to boot into a different kernel to do that, yes?
[01:55] <glestrade> I’m in the unsupported one at the moment
[01:55] <glestrade> other on might be older, or deleted
[01:56] <Bashing-om> glestrade: If you are booting that 4.2 kernel - that indeed will present problems as the system then is inconsistent. All that is 18.04 will not talk to a 4.2 kernel :(
[01:58] <glestrade> okay, both kernels available to me on the grub menu on 4.2
[01:58] <glestrade> this was from an old project that needed 14.04 and a very specific kernel version to talk to a specialty wifi card
[01:59] <glestrade> maybe I can downgrade the OS all the way back xD
[01:59] <glestrade> and then upgrade the kernel in a procedural way
[01:59] <glestrade> idk
[02:00] <Bashing-om> glestrade: NO! downgrade - we have no way back button :D
[02:01] <glestrade> so I can’t downgrade, and I can’t change the kernel
[02:02] <Bashing-om> glestrade: Well as the latest kernel is installed - there is a way from grub to boot it - however, I have no UEFI experience to know for sure how. All here I can do is fumble along with you.
[02:03] <glestrade> I think I might have just done something good in this direction. Will update you in a second
[02:05] <glestrade> I always fumbled in Madden NFL, it’s no big deal
[02:07] <glestrade> oof it’s not here
[02:08] <glestrade> I was trying to boot into recovery mode and update the grub
[02:08] <glestrade> it looked like it was going to add an entry
[02:10] <Bashing-om> glestrade: Have you got a 18.04 live desktop installer ? - the boot options have " boot from 1st hard drive" . Might be worth trying :D
[02:19] <glestrade> I’ll keep this in mind. Going to try a few different approaches, I’ll ping this chat if anything works
[02:19] <glestrade> I’m sure if I spend enough time I’ll get that kernel on the boot menu
[02:19] <glestrade> hopefully.
[02:20] <wizzo> hi. i am trying to install ubuntu using the server installer and i need to create an EFI partition but the partitioner doesn't have an option to format as FAT
[02:20] <wizzo> is it going to do this for me or something? i don't get it
[02:22] <wizzo> oh lol nevermind
[02:22] <wizzo> "use as boot device"
[02:24] <Bashing-om> glestrade: Works too from a grub prompt: https://help.ubuntu.com/community/Grub2/ISOBoot to boot the desired kernel.
[02:27] <oops> my remote console will die if i stop action for a while, i have modified "ServerAliveInterval " value  to 6000
[03:40] <glestrade> Bashing-om: my grub was “owned” by another distro
[03:41] <glestrade> so I updated it and now I’m on 4.15
[03:41] <glestrade> had to do so via the other distro
[03:44] <Bashing-om> glestrade: Last installed grub owns grub unless you take other measures. What shows now '
[03:45] <Bashing-om>  glestrade: sudo find / -name "NVIDIA-Linux-*" - and we proceed to install system driver.
[03:45] <glestrade> idk, but I had an arch distro from June and it set up its own grub, and that was the same one I had to use to update grub
[03:46] <glestrade> and the new kernel was booted
[03:46] <Bashing-om> glestrade: Booting ubuntu now ?
[03:46] <glestrade> yes
[03:47] <calamari> According to some instructions I see online, in System Settings > Hardware there should be "Color". I don't see Color on mine. Would someone be willing to open Color and tell me the name of the executable running? Then I can find the appropriate package and install it.
[03:47] <glestrade> running your find command atm
[03:47] <Bashing-om> glestrade: And ya want that ubuntu be in control of grub ?
[03:48] <glestrade> eventually, but it’s not the first priority
[03:48] <glestrade> trying to get tensorflow-gpu up and running
[03:49] <glestrade> find is taking its sweet time
[03:49] <tomreyn> calamari: For me it's    Settings -> Devices > Color    - it will dpends on your Ubuntu release (and desktop, if not the default of gnome-shell/mutter)
[03:50] <calamari> tomreyn: Thanks. Can you tell me which application is running when you open it?
[03:52] <glestrade> Bashing-om: thanks for the help, I’ll let you know what happens next
[03:54] <Bashing-om> glestrade: May not be on here much longer ... getting on toward the witching hour here. Make sure the OEM driver stuff is not present and install what the system thinbks best for the driver.
[03:55] <tomreyn> calamari: gnome-control-center
[03:55] <tomreyn> calamari: i'm on 18.04 LTS, not sure what you are on, though
[03:56] <calamari> tomreyn: 18.03 as well
[03:56] <calamari> *04
[03:57] <tomreyn> ok. so that should work for you
[03:58] <tomreyn> you'll need to have colord installed, i guess, but i think this is a dependency of something ubuntu-desktop depends on, so you should alread yhave it.
[03:58] <tomreyn> colord is still pretty buggy in 18.04, though
[04:02] <calamari> tomreyn: I couldn't get it to load, but thank you for your help anyway!
[04:04] <tomreyn> calamari: if you're hoping to play with color profiles, i think you'll have a better time after upgrading to 20.04. or, differnetly put, i don't think there's a good chance it will work on 18.04.
[04:04] <calamari> I installed a profile using displaycal and I can't figure out how to undo it, haha
[04:17] <LuckyMan> I have this issue on 21.04: if I turn on the computer and don't use it for a while the screen becomes black and the monitor shuts down and after that I can't use the system (which remains on). If I use it right away after turning it on it's fine.
[04:24] <calamari> LuckyMan: Is your goal to fix the wakeup problem, or is your goal to keep the scren from going to sleep in the first place?
[04:25] <LuckyMan> calamari, fix the wake up problem
[04:25] <calamari> LuckyMan: sounds good, unfortunately I don't know how to help with that one, sorry
[04:26] <LuckyMan> the keyboard doesn't seem to work also, I tried ctrl alt F... combinations and CTRL alt DEL and it doesn't respond
[04:27] <LuckyMan> I have to press the power button for 5 secs to shut it down
[04:28] <LuckyMan> this is kind of strange because I have 20.04 on the same HD with no issues
[04:36] <AmR> Hello
[04:36] <AmR> How I can Install full Qt and 5 and 6 ?
[04:38] <alkisg> LuckyMan: try to suspend/resume. If the problem happens then, it's a suspend problem; troubleshooting instructions at: https://wiki.ubuntu.com/DebuggingKernelSuspend
[04:43] <AmR> Any Hellp ?
[04:48] <LuckyMan> Just tried suspension, it worked fine
[04:48] <LuckyMan> also, this is a desktop computer
[04:49] <alkisg> Which graphics card and drivers?
[04:49] <LuckyMan> no graphics cars (I mean other than the processor)
[04:50] <LuckyMan> *card
[04:50] <alkisg> lspci -nn -k | grep -A 2 VGA
[04:51] <LuckyMan> 00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:3e92]
[04:51] <LuckyMan> 	DeviceName: Onboard - Video
[04:51] <LuckyMan> 	Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
[04:52] <alkisg> Which desktop environment, gnome, mate, kde?
[04:52] <LuckyMan> gnome
[04:53] <alkisg> I don't have gnome to tell you exactly, but somewhere in the settings, there will be 3 options for screensaver activation, for monitor blanking, and for suspension
[04:54] <alkisg> Try to set them in different times, e.g. 1 minute, 2 minutes, 3 minutes, to see which one of them is causing the issue
[04:55] <glestrade> anyone here know about vncservers?
[04:55] <alkisg> More specifically?
[04:56] <glestrade> I keep getting “Cannot establish any listening sockets - Make sure an X server isn’t already running
[04:56] <glestrade> I’ve been stuck looking at StackOverflow for about 12 hrs
[04:56] <alkisg> With which server/command?
[04:56] <glestrade> deleted all the lock files people tell you about over and over
[04:56] <alkisg> If you have a question at stackoverflow, paste it here
[04:56] <glestrade> tigervnc
[04:56] <glestrade> I don’t have one, just was browsing
[04:57] <glestrade> vncserver :1 is what I’m doing
[04:57] <alkisg> Do you want to share your screen, or do you want to set up remote logins for many users that do VNC logins separately?
[04:58] <glestrade> share screen over local network
[04:58] <glestrade> for better ergonomics than I can get in this room
[04:58] <alkisg> Sure. So, :1 means display=1, what is your display? Run this command: echo $DISPLAY
[04:58] <glestrade> got the old tendonitis problem
[04:58] <alkisg> Also, are you on xorg or on wayland?
[04:58] <glestrade> kk
[05:00] <glestrade> echo $XDG_SESSION_TYPE
[05:00] <AmR> Any Help ?
[05:00] <glestrade> gives x11
[05:00] <alkisg> And your display is 0 or 1?
[05:00] <glestrade> and display is :1, so I guess I can’t run it there
[05:01] <glestrade> but I’ve tried 0
[05:01] <glestrade> and 2
[05:01] <alkisg> Why is your DISPLAY=:1 instead of :0?
[05:01] <glestrade> 0 says “ a server is already running as 0..."
[05:01] <alkisg> Which desktop environment are you using? Are you logging in normally, or via some other method?
[05:03] <lotuspsychje> !patience AmR
[05:03] <lotuspsychje> !patience
[05:03] <glestrade> it’s a gnome desktop, manual log in
[05:04] <glestrade> and i’m not sure about display, I didn’t configure that
[05:05] <alkisg> glestrade: if you want to do a quick test, run `sudo apt install x11vnc` and then `x11vnc -connect alkisg.ltsp.org`; this will share your screen with me; you can ctrl+c it right after it connects
[05:05] <alkisg> If that works, we can check why tigervnc doesn't; if x11vnc doesn't work; we can check what's wrong with your setup
[05:07] <glestrade> sure, I don’t have any private info on this box
[05:07] <glestrade> hold on
[05:09] <glestrade> working hypothesis is that I improperly closed a vnc session last week (I got it to work once with a different vncserver program)
[05:09] <glestrade> but that one was breaking in the same way
[05:12] <alkisg> glestrade: I think that tigervncserver tries to run in a new display
[05:12] <alkisg> For a new login, not to share your existing screen
[05:12] <LuckyMan> alkisg, tried letting the screen go off with 1 minute, it goes off fine, it wakes up fine. This problem only happens when I start the computer and don't login right away and the screen goes off.
[05:13] <alkisg> glestrade: close x11vnc, then try /usr/bin/x0vnc4server
[05:14] <alkisg> Btw, where are you connecting from? If it's a linux box, maybe you could use epoptes.org, it's very convenient
[05:14] <alkisg> (I ctrl+c'ed the x11vnc command)
[05:14] <alkisg> So that the port is free
[05:15] <alkisg> LuckyMan: ah you mean in the login screen? (gdm3 display manager)
[05:15] <glestrade> are you still connected? I was trying to kill the x11vnc
[05:16] <alkisg> glestrade: no I'm not, I ctrl+c'ed it, I wrote it above
[05:16] <glestrade> okay, my box was crawling for a second there
[05:17] <glestrade> hmm so I think I had used vnc4server
[05:17] <glestrade> and you’re saying that they’re both trying to talk to a different display
[05:18] <glestrade> that is, I used vnc4server last week
[05:18] <alkisg> It's possible that one of these is trying to set up multiple sessions, and it's messing your DISPLAY
[05:18] <alkisg> So maybe all you need to do is uninstall one of them, e.g. tigervncserver or something
[05:19] <glestrade> isn’t display an env variable
[05:19] <glestrade> so if I reset it then...
[05:20] <alkisg> You'll change the result, not the cause
[05:20] <glestrade> hmm yeah
[05:20] <alkisg> I.e. you just won't be able to run graphics programs after that; you won't uninstall the server
[05:21] <glestrade> no I get that
[05:21] <LuckyMan> alkisg, the big question is: what has changed in 21.04 gdm (because it works fine with 20.04)
[05:22] <glestrade> well let’s see what happens when I get rid of the other two vnc server programs
[05:23] <glestrade> I’m on 18.04 if that’s important
[05:23] <alkisg> LuckyMan: probably the kernel
[05:24] <alkisg> I.e. if you install 20.04 and then install the -hwe-edge kernel (5.11), it might happen there too
[05:26] <glestrade> alkisg: I’m about to look this up - does vnc4server have a default socket it uses
[05:27] <glestrade> it seems to believe that it’s already in use
[05:27] <glestrade> I’m curious so I’d like to do this before uninstalling it and tiger
[05:27] <alkisg> glestrade: vnc servers connect to xorg with normal function calls, which use display, which go to /tmp/.X* sockets. There's no point at all in troubleshooting that.
[05:34] <AmR> qt5-default package not in 2x.xx, I need full list if any one have it ?
[07:04] <anonymous> Hello everyone
[07:05] <anonymous> Drone, I would like to ask for rules
[07:05] <anonymous> I am here
[07:05] <anonymous> new*
[07:06] <anonymous> Anything I should know before asking questions?
[07:06] <alkisg> The irc guidelines are on the /topic if you want to read them; otherwise any technical question about ubuntu should be fine
[07:06] <Bashing-om> anonymous: Welcome - rules: read the topic of the channel, please :D
[07:06] <anonymous> alkisg, Thank you
[07:07] <anonymous> Are we allowed to share things unrelated to Ubuntu?
[07:08] <anonymous> *Or ask
[07:08] <guiverc> anonymous, this is a Ubuntu support room, so only Ubuntu support in this room.  Ubuntu off-topic for off-topic talk, Ubuntu discuss for Ubuntu related issues
[07:09]  * guiverc should have used # in but didn't matter
[07:09] <Bashing-om> guiverc: Ya scared him off !
[07:09]  * guiverc smiles
[07:40] <debouncer> Hi, my pc fans works on full speed after woking up from suspend.
[07:40] <debouncer> Any idea how to fix this?
[07:43] <ttkap> start by checking which process might be eating up CPU by running top or htop command
[07:45] <debouncer> Yeah. It was the first thing that I checked out.
[07:46] <debouncer> It is definitely not the case.
[07:46] <lotuspsychje> wich brand is your pc debouncer
[07:46] <debouncer> Wdym? Motherboard?
[07:47] <lotuspsychje> model/make/brand
[07:47] <debouncer> There is no specific brand for each item. It is an assembled pc.
[07:48] <debouncer> *I mean each part has its own brand.
[07:48] <lotuspsychje> debouncer: ok, you might wanna investigate your dmesg and leave a journalctl -f open to see whats going on too
[07:50] <lotuspsychje> feel free to share it in a pastebin so volunteers can take a look for you
[07:55] <debouncer> https://0bin.net/paste/uSIdngaq#eZwYGl1RnE2eQm48b8FrrB2oGIqn5KHyF4lzE1tw0rG
[07:56] <debouncer> Jul 22 10:53:11 orion systemd-sleep[27624]: Failed to restart mbpfan.service: Unit mbpfan.service not found.
[07:56] <debouncer> Jul 22 10:53:11 orion [27620]: /usr/lib/systemd/system-sleep/mbpfan failed with exit status 5.
[08:02] <lotuspsychje> debouncer: thats a package to control fans for macbooks so it seems?
[08:03] <debouncer> yeah, i guess
[08:03] <debouncer> i don't understand why it exists
[08:03] <lotuspsychje> but it works for your system too?
[08:04] <lotuspsychje> debouncer: if you're on 20.04 or higher, you could test out stacer and see if it creates systemd services
[08:04] <debouncer> i don't think so. this pc is not a mbp
[08:04] <lotuspsychje> !info stacer
[08:05] <debouncer> yeah it creates a service at startup
[08:05] <debouncer> I disabled it now.
[08:07] <lotuspsychje> debouncer: you can also consider filing a new bug with: ubuntu-bug mbpfan if you like
[08:08] <debouncer> Sure but this didn't slow down fans' speed
[08:12] <debouncer> Okay now I have an idea.
[08:12] <debouncer> fancontrol.service has stopped working.
[08:28] <[twisti]> im running ubuntu 20, and i noticed the bundled ansible is a pretty old version. what is the apropriate way of getting a current version ?
[08:33] <toddc> [twisti]: stable vs testing are you sure you need the latest?
[08:34] <[twisti]> latest stable, yeah
[08:36] <ApostleInTriumph> Hello. I am trying apt-get update and i face this error. Also, underneath, I've tried a solution that didn't work. how do i fix this https://bpa.st/VVIA
[08:41] <lsrtl> how to install from a file, not .deb ?
[08:45] <toddc> ApostleInTriumph: https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=20.04&target_type=runfile_local both fun file and deb files
[08:45] <ApostleInTriumph> toddc i don't understand?
[08:47] <toddc> wget is a direct download to nividia dev drivers their certs are expired and they are dev file so untested
[08:49] <geirha> ApostleInTriumph: it's saying the signatures are wrong, not that you're missing the key
[08:49] <ApostleInTriumph> geirha so I should delete the signature?
[08:49] <ApostleInTriumph> I tried to sudo apt-key del 6ED91CA3AC1160CD, the apt-get update after that didn't work
[08:50] <geirha> ApostleInTriumph: It means someone has updated the package lists on nvidia's end, but haven't signed the new list properly. Or they've had a break-in and someone tried to inject malicious software
[08:54] <ApostleInTriumph> geirha makes sense.
[08:54] <ApostleInTriumph> now it prevents me from doing apt-get update
[08:54] <ApostleInTriumph> how do I fix this without removing nvidia drivers?
[08:56] <geirha> you can temporarily comment them out from /etc/apt/sources.list
[08:56] <geirha> or if it's in /etc/apt/sources.list.d  rename the file with a .disabled extension
[09:04] <ApostleInTriumph> thanks geirha that worked.
[09:05] <ApostleInTriumph> I'm curious to understand, why would nvidia-container-runtime's key be unsigned all of a sudden?
[09:07] <geirha> not the key, the package list
[09:07] <alkisg> ApostleInTriumph: it's not unsigned; the key has expired on 2021/06/16
[09:08] <alkisg> You need to ping them to renew it, e.g. there: https://github.com/NVIDIA/nvidia-docker/issues/1081
[09:08] <alkisg> Judging from the key contents, they renew it every two years, and they haven't done so for 2021
[09:08] <geirha> ah, so the package list is signed, but with an outdated key
[09:10] <ApostleInTriumph> alkisg I see. where do you find information on when it expired?
[09:11] <alkisg> ApostleInTriumph: you can use gpg or apt to see the key details; I didn't bother finding the exact command for that so I just used the graphical key manager, seahorse
[09:15] <alkisg> Here's one way to examine it using gpg2: https://termbin.com/w7eh
[09:15] <alkisg> The one that apt mentions is this: sub   rsa2048 2019-09-18 [S] [expired: 2021-06-16]
[09:57] <zChrisWrk> When i login to Ubuntu 20.04 it says that i have x amount of updates and y amount are security updates. I want to install only the security updates. How do i do that ?
[10:06] <LuckyMan> zChrisWrk, Why would you install only the security updates?
[10:31] <Bardon> Hello, my server is taking a long time to boot because of systemd-networkd-wait-online.service. Here are its logs https://termbin.com/5kx10. I don't understand what's wrong
[10:31] <Bardon> Even after the server has started, the network is obviously working since I'm logged in through ssh but `sudo systemctl start systemd-networkd-wait-online.service` fails
[10:31] <Bardon> "Job for systemd-networkd-wait-online.service failed because the control process exited with error code."
[10:33] <cbreak> Bardon: why did you enable that?
[10:33] <cbreak> it's disabled on my system, and apparently it's disabled by default
[10:33] <Bardon> cbreak: Did I? I don't remember doing it but it's possible
[10:34] <Bardon> I'll just disble it then :)
[10:34] <Bardon> I'm pretty sure I didn't touch it though. I installed my OS a few days ago and haven't touched many things
[10:34] <cbreak> I have a 21.04 install
[10:34] <Bardon> It's ubuntu server 20.04 LTS
[10:34] <cbreak> upgraded from 20.10, desktop
[10:34] <Bardon> fresh install here
[10:34] <cbreak> maybe it's enabled on servers? :/
[10:35] <Bardon> which would make sense because not having network access is a big concern
[10:35] <Bardon> on servers
[10:35] <cbreak> wonder if it checks for network connectivity, or _internet_ connectivity
[10:36] <cbreak> heh, man systemd-networkd-wait-online works
[10:36] <Bardon> Ah!
[10:36] <cbreak> By default, it will wait for all links it is aware of and which are managed by systemd-networkd.service(8) to be fully configured or failed, and for at least one link to be online
[10:37] <cbreak> (that's C&P)
[10:37] <Bardon> "it will wait for all links it is aware of". There are 7 ports on my server but I just use one
[10:37] <Bardon> ethernet ports
[10:37] <cbreak> maybe you have links that aren't configured?
[10:37] <cbreak> and not explicitly disabled?
[10:37] <Bardon> I'm not sure, I've never disabled such things. I just leave them unplugged
[10:37]  * cbreak has tried to switch to netplan on all servers, it seems quite convenient
[10:38] <Bardon> It seems installed by default
[10:38] <Bardon> /etc/netplan/00-installer-config.yaml has everything set to true
[10:39] <Bardon> cbreak: Is netplan a replacement for the `ip` command?
[10:40] <Bardon> Am I not supposed to do `sudo ip link set dev eno1 down` anymore?
[10:43] <cbreak> I think netplan is more a replacement to other config files
[10:43] <cbreak> not for interactive use
[10:43] <cbreak> changes made with it are somewhat persistent
[10:44] <cbreak> I'm not a real admin, so ... I have limited experience, but if you use netplan, you can fill your yaml file with configuration for the interfaces, then try it out
[10:44] <cbreak> and if it works, keep it. If you get dced, it'll change back after a timeout
[10:46] <Bardon> Hmm, I set everything to false except for the link that I'm using and it still complains
[10:47] <Bardon> (I'm not a real admin either :) )
[10:47] <Bardon> With --any it works
[10:47] <cbreak> you have to somehow enable the netplan / apply it
[10:47] <cbreak> I forgot how
[10:47] <Bardon> Yes I ran sudo netplan apply
[10:48] <Bardon> Ah I need to restart systemd-networkd too
[10:48] <Bardon> hmm lets see
[10:48] <Bardon> Nice :)
[10:48] <Bardon> That's what I was missing
[10:48] <Bardon> cbreak: Thanks a lot :)
[10:49] <cbreak> np :)
[10:54] <BluesKaj> Hi all
[11:05] <zamba> for CVE-2021-33909, do i need to reboot or is it enough to just patch systemd?
[11:05] <zamba> it seems like a kernel vuln?
[11:06] <zChrisWrk> LuckyMan, becouse i dont want to install the other updates
[12:06] <sixwheeledbeast> It's kernel vuln but they also found systemd issues too from that vuln.
[12:06] <lotuspsychje> zamba: ^
[12:06] <sixwheeledbeast> just reboot
[12:06] <sixwheeledbeast> full-upgrade && reboot
[12:15] <Guest38> Hi
[12:16] <Guest38> I was learning about Tiling Window managers recently
[12:17] <Guest38> and I was wondering if there’s a way to use it on Ubuntu without having to installing a VM
[12:17] <Guest38> also, what tiling WM options are there for Ubuntu users?
[12:18] <zChrisWrk> Guest38, You can install most WMs
[12:19] <lotuspsychje> Guest38: see also; apt-cache search tiling
[12:20] <Guest38> But does it cause problems with Gnome?
[12:21] <Guest38> Someone said something about dmenu that went over my head
[12:21] <lotuspsychje> Guest38: window managers you can choose at login base ontop the ubuntu system
[12:22] <lotuspsychje> Guest38: for desktop managers, the more you install other flavours ontop ubuntu, that might give some frankenubuntu mixed system issues
[12:22] <BluesKaj> hehe
[12:22] <sixwheeledbeast> meh tiling. I just make more workspaces.
[12:23] <BluesKaj> or activities
[12:24] <Guest38> I don’t mind workspaces right now. I just wanted to try it
[12:24] <naruto> i can't type my phone number in authy anyone up for help?
[12:24] <Guest38> the concept of the space management intrigued me
[12:24] <Guest38> do you have any recommendations by the way?
[12:25] <sixwheeledbeast> i3 is popular, compiz can do that IIRC
[12:25] <sixwheeledbeast> awesome?
[12:26] <lotuspsychje> Guest38: there's a nice community at https://www.reddit.com/r/unixporn/ where you can grow ideas on WM/DE/ubuntu
[12:26] <Guest38> I’ll check compiz or awesome out then. Thank you for the assistance
[12:27] <naruto> has anyone got a problem where you can't type your phone number in authy?
[12:28] <webchat91> Since Kernel 5.9.0-59.63 and further on, my GRUB after trying to initalise the RAMDisk is only blank. I opened a ticket, https://askubuntu.com/questions/1348180/black-screen-on-boot-on-hp-probook-450-g6-with-5-8-0-59-66-reason-why-delete no reply, I went to this IRC yesterday and the advise was to Grub - Command Line - rmmod tpm to try if TPM is
[12:28] <webchat91> causing the issue. Ive tried the method, and tried updating grub, but the screen stays blank. I am forced to use Kernel 5.8.0-55 and I am quite frustrated with some LTS 20.04 this can happen! Other users report the same issue, so I am desperate for a solution and desperate that since 4 weeks no one was able to help within the ticket. Any
[12:28] <webchat91> recommandations?
[12:28] <webchat91> *5.8.0-59
[12:34] <Duality> hey
[12:34] <lotuspsychje> welcome Duality
[12:34] <Duality> Question how do i install a different version of a gcc cross compiler ?
[12:34] <Duality> i tried gcc-4.8-arm-linux-gnueabihf but it can't be found in the repositories
[12:37] <mathese> Hi
[12:38] <Duality> seems i have to add xenial to sources.list
[12:40] <cart_man> I am planning on running this command in a bash script in a while loop to record CPU and Memory data of the process -> ps -q 18872 -eo %cpu,%mem    . It looks good but the problem is it's output is PU %MEM 0.1% 0.1%  . So the problem is I get a repeat of the value PU % MEM. I need to actually only receive 0.1,0.1
[12:40] <cart_man> beucase I want it to create a CSV file
[12:40] <cart_man> as it monitors the PID
[12:41] <cart_man> Is it possible to ommit them?
[12:43] <msg75> The test case for today's daily shows that I have completed the "live session" tests. I expected that this would be fresh start. Is the live session for this image to be repeated or ignored?
[12:44] <msg75> Xubuntu Desktop amd64 testcases in Impish Daily
[12:44] <Duality> cart_man: maybe you can use the cut command to only get what you need
[12:45] <Duality> cart_man: something like: echo PU %MEM 0.1% 0.1% | cut -d " " -f 3,4
[12:47] <cart_man> ok so what does the -f do?
[12:47] <Duality> selects which indexes form the cut you want
[12:48] <Duality> or rather which parts
[12:50] <Duality> so in this case cut command would chop up "PU %MEM 0.1% 0.1%" into four parts and -f would select the parts in this case the last two being third and fourth element :)
[12:51] <Duality> with -d you can select where to make the cut and since there is a space inbetween the words that is where i cut it
[12:51] <Duality> with " " to select for space
[12:53] <Duality> is the output a single line or multiple lines
[12:53] <Duality> because if it's multiple this solution doesn't work
[12:58] <Duality> you could try something like this cart_man: ps -q 27279 -eo %cpu,%mem | tr '\n' ' ' | tr -s ' ' | cut -d " " -f 3,4
[12:58] <Duality> but there is probably a better way
[13:55] <tuxick> having several problems creating users with autoinstall
[13:56] <tuxick> "identity" doesn't seem to support authorized_keys
[13:56] <tuxick> and user-data: users: seems to get ignored
[13:59] <tuxick> is there documentation about getting this right?
[14:03] <dbungert> tuxick: in subiquity autoinstall, the identity section doesn't have authorized_keys, that's handled in the ssh section https://ubuntu.com/server/docs/install/autoinstall-reference
[14:06] <tuxick> hm
[14:08] <dbungert> if you have an install that you've done manually, that will provide an example at the end at /var/log/installer/autoinstall-user-data
[14:11] <tuxick> yeah used one of those for creating a template
[14:13] <tuxick> tried creating uses in user-data but those ended up disabled :)
[14:13] <tuxick> '!' in shadow
[14:16] <dbungert> tuxick: this example is pretty bare bones but maybe it'll help to compare against?  https://github.com/canonical/subiquity/blob/main/examples/autoinstall-user-data.yaml
[14:22] <tuxick> yeah that's how i tried it
[14:22] <tuxick> tried so many permutations i lost track
[14:23] <tuxick> ssh: authorized_keys this time resulted in "user foo is not configured for ssh_import_id
[14:23] <tuxick> assuming that's why i didn't import key
[14:36] <BT643> Feels like a dumb question, but I've been using Ubuntu 20.04 (with an encrypted drive), and today I wanted to reinstall. I put a 20.04 installtion on a USB stick and booted from it. Installed a fresh version of Ubuntu 20.04 on the drive (full erase and reinstall) but when I went to boot the encryption password wouldn't work. I booted from the Live
[14:36] <BT643> USB again and could access my drive using the password. Rebooted again leaving the USB drive in and was able to get into the main OS (non-live). Removed the USB and rebooted again and it complained again: "cryptsetup: ERROR: sda3_crypt: cryptsetup failed, bad password or options?". Seems I've somehow got the encryption key on the media I used to
[14:36] <BT643> install?
[14:36] <BT643> Hope this makes sense.. is there an easy way for me to resolve this? I can easily just do another reinstall but don't really understand how it's got in this state to avoid it when I do it again?
[15:02] <tuxick> heh, the joys of yaml: any string can be significant or arbitrary
[15:03] <tuxick> ssh: authorized_keys is NOT autorized-keys
[15:04] <tuxick> i'll skip the user-data: users: bit, can leave that to ansible
[15:05] <dbungert> oof, glad you made progress
[16:14] <tuxick> :)
[16:23] <donofrio> tuxick, yah formatting matter in yaml files
[16:34] <tuxick> not just formatting
[16:34] <tuxick> there's no validation
[16:34] <tuxick> "any string anywhere"
[16:35] <tuxick> thank bob yamllint will catch the worst
[16:46] <tuxick> with xml you can simply provide a dtd
[17:01] <sabasedigh> hi
[17:01] <sabasedigh> I want to open an rpm file with archive manager. what package should I install to do that?
[17:02] <sabasedigh> engrampa archive manager won't open it.
[17:02] <sabasedigh> thank you
[17:03] <venividivici1989> adbasedigh: p7zip?
[17:03] <leftyfb> sabasedigh: why?
[17:03] <sabasedigh> p7zip is installed
[17:03] <leftyfb> sabasedigh: it might be easier to just download the source code for the package
[17:04] <venividivici1989> 7z x /path/to/file.cpio -o/path/to/extract/folder/
[17:04] <venividivici1989> *rpm
[17:05] <sabasedigh> venividivici1989: what is the cpio extension?
[17:05] <venividivici1989> a fiel you get when you extract a rpm
[17:05] <venividivici1989> file*
[17:06] <sabasedigh> leftyfb: it would take to long and much hassle not to mention long list of packages as dependencies to install and then start to compile the package
[17:06] <leftyfb> sabasedigh: what is your end goal? Are you trying to install an rpm onto your ubuntu machine? Which package?
[17:07] <sabasedigh> venividivici1989: the thing is; I can't extract the .rpm package. to get that cpio file you saying.
[17:08] <sabasedigh> leftyfb:  to run the software inside the package
[17:08] <leftyfb> sabasedigh: what software?
[17:09] <TJ-> !info alien | sabasedigh
[17:09] <leftyfb> TJ-: I don't think the want to install the rpm for $reasons
[17:09] <sabasedigh> wait .... wait ... something lost in the msg
[17:10] <sabasedigh> I don't want to install the package ..... just extract it. file-roller is saying archive not supported.
[17:10] <sabasedigh> It get this error when I have not installed an archive extension like rar
[17:11] <sabasedigh> what do I need for rpm?????
[17:11] <leftyfb> sabasedigh: You want to extract the rpm package so you can run a binary inside the rpm as opposed to installing the rpm correct? What is the package name?
[17:11] <TJ-> leftyfb: sabasedigh  alien isn't for installing, use it to extract/convert to, for example, a tar.gz
[17:11] <sabasedigh> That is the question here.
[17:11] <sabasedigh> leftyfb: ok thank you
[17:11] <sabasedigh> so i need alien
[17:11] <sabasedigh> now we are cooking ...
[17:12] <leftyfb> sabasedigh: what software?
[17:12] <sabasedigh> the package name is iridium browser
[17:12] <oerheks> https://downloads.iridiumbrowser.de/deb/
[17:12] <oerheks> hopla
[17:12] <leftyfb> https://www.ubuntubuzz.com/2018/05/how-to-install-iridium-browser-on-ubuntu-1804.html
[17:13] <TJ-> sabasedigh: to extract you can do something like "alien --to-deb --generate path/to/rpm
[17:13] <TJ-> sabasedigh: see man-page http://manpages.ubuntu.com/manpages/focal/en/man1/alien.1p.html
[17:13] <leftyfb> sabasedigh: this is why we ask questions. Sometimes we have better solutions to your overall goal as opposed to trying to troubleshoot the way you are approaching it
[17:14] <sabasedigh> TJ-: leftyfb: You are right. and I thank for your help.
[17:14] <sabasedigh> thank you
[17:15] <oerheks> leftyfb, i noticed it is just the key, bo deb anymore
[17:15] <oerheks> c/bo/no
[17:15] <sabasedigh> Oh ; how many dep does it have. :-D
[17:16] <oerheks> sabasedigh, if you try to install that .rpm unpacked, good luck finding dependencies.. not
[17:16] <sabasedigh> talking about deps for alien
[17:16] <sabasedigh> itself
[17:17] <sabasedigh> yay It extracted
[17:18] <leftyfb> sabasedigh: what you are doing is very unsupported. You really should reach out to the iridium-browser project and get them to update the .deb or release a snap package
[17:20] <ice9> I installed ubuntu from a month on ssd it's running very well until now but since a week I noticed that the shutdown time is MUCH slower; how can I find out the reason?
[17:21] <Mekaneck> press ESC to see what's holding up the shutdown process
[17:23] <leftyfb> ice9: https://itsfoss.com/long-shutdown-linux/
[17:23] <leftyfb> ice9: 2nd result on google when searching for "ubuntu shutdown taking a long time"
[17:23] <ice9> thanks leftyfb
[17:34] <webchat23> @Tj- https://askubuntu.com/questions/1348180/black-screen-on-boot-with-5-8-0-59-66-reason-why-delete-kernel tried your Grub command line rmmod tpm hint, had no effect
[17:36] <webchat23> TJ- *seems like I always miss how to tag someone properly with the webclient: https://askubuntu.com/questions/1348180/black-screen-on-boot-with-5-8-0-59-66-reason-why-delete-kern... tried your Grub command line rmmod tpm hint, had no effect
[17:40] <TJ-> webchat23: in which case your next suspect is the initrd.img files created for the newer (failing) kernel versions. It is possible that the older kernel that works does so since its companion initrd.img hasn't been updated (thankfully1) and therefore does not contain some change that has broken things in the later initrd.imgs
[17:41] <ioria> webchat23, have you tried to boot in Recovery mode ?
[17:43] <TJ-> webchat23: you can do some basic testing of one of the failing versions by editing the "linux ..." command line in GRUB when starting, removing "quiet splash" and adding "debug break=premount" and pressing Ctrl+X to boot with that change. if it works you'll be dropped to a busybox shell in the initrd.img before the LUKS unlock stage and can investigate
[17:48] <webchat23> ioria i am not too sure right now, I think I tried it in the beginning but that issue is since a month so Im not too sure. Could perform it later with the restart. TJ- debug break command is so he stops on error? I surely can start without splash screen and see at which module he fails. But I wouldnt know what I should do in some shell command
[17:48] <webchat23> wise. Sounds also like some issue a LTS version shouldnt suffer :( quite desperating, exp. like you can see in my askubuntu ticket that I fear any update may remove the last working kernel as the system seems not to work with flagging kernels as "rc" or "ii" as my tries to remove the newer kernels wasnt successful either. And all this with a
[17:48] <webchat23> machine that is in daily business production ... ohhh boy...
[17:56] <leftyfb> webchat23: do you have the ability to spin up a new machine just for troubleshooting purposes?
[17:58] <webchat23> leftyfb: ... I can use some LiveCD on a second machine if this is suitable, but by the hardware limitations I neither could run a second installation on the machine in question if that was your question?
[17:59] <leftyfb> webchat23: the live cd would not help with troubleshooting. It would need to be an install identical to one of the machines you're having issues with
[18:00] <webchat23> leftyfb I think I dont understand your question: What do you want to do, run a regular LTS 20.04 with the kernel on any other machine and than troubleshoot on that machine? I dont get it
[18:01] <leftyfb> webchat23: new machine, not in production, install the same version of ubuntu as your production machines with all the same software and configurations. Troubleshoot that machine as opposed to your production machines
[18:03] <webchat23> ... leftyfb your suggestion wont be of any help as even if you would set up a regular LTS 20.04 we are talking about, and rerun my bash-history to have the same status, you are still on a different hardware. The issue eitehr has to with HP Bios/Firmware or has to do with Grub/Kernel and is completly seperated of my user software. As I use a regular
[18:03] <webchat23> LTS 20.04 with a regular updated kernel, there is nothing altered that cause this issue!
[18:04] <webchat23> Also, other users report the same issue with similar hardware, and the other user stated it was with a fresh install.
[18:06] <webchat23> BTW, leftyfb, you are welcome to post your suggested solution down here because your overkill attempt for sure wont be your first option ;o) https://askubuntu.com/questions/1348180/black-screen-on-boot-with-5-8-0-59-66-reason-why-delete-kernel
[18:07] <lotuspsychje> webchat23: did you find a relevant bug ID for this yet?
[18:09] <coldsnop> sa
[18:09] <coldsnop> hi
[18:16] <ELFrederich> Does Gnome Terminal not support "overtype" mode when you press insert?... or is my keyboard broken?
[18:16] <webchat23> lotuspsychje I tried looking for some bug reports about 5.8.0-59 on launchpad a month ago, but I got to say Im not an advanced user who reads fluently in the type of text there. I havent found what I looked for (combined of the Kernel version with keywords like Blank Screen, LUKS...). My AskUbuntu Ticket actually was asking to help me determ if
[18:16] <webchat23> that is a bug that should get reported or not, but my bug report wouldnt contain any log at the moment so its worthless :P
[18:19] <mloza> hello, in 18.04, when I ran dpkg-reconfigure -plow unattended-upgrades  doesn't set the unattended upgrade to 0 in /etc/apt/apt.conf.d/20auto-upgrades
[18:24] <donofrio> ELFrederich, #gnome?
[18:31] <tomreyn> webchat23: i may not have followed the full story, but did oyu not say you're able to boot using an older kernel image? or did you delete those that worked fine?
[18:32] <lotuspsychje> tomreyn: his askubuntu thread here https://askubuntu.com/questions/1348180/black-screen-on-boot-with-5-8-0-59-66-reason-why-delete-kernel
[18:33] <tomreyn> lotuspsychje: thanks, i read this one. and wondered whether this is the same issue reported at https://bugs.archlinux.org/task/71003 and at https://gitlab.freedesktop.org/drm/intel/-/issues/3569
[18:35] <tomreyn> if an older kernel is bootable, journalctl -b -1    should provide logs from last but one boot (which could be one that failed with a black screen)
[18:38] <tomreyn> another thing to try would be to disable "secure boot" in bios, to boot with "dis_ucode_ldr" initrd (grub "kernel" line) option, and to change the orde rin which graphics chipsets (integrated (intel), dedicated (nvidia)) are initialized. or disabling the dedicated altogether (just to see whether it helps), if this is possible.
[18:48] <webchat23> tomreyn thanks for the hint the logs. I will try to perform a new kernel boot and than the old, working kernel again and check the logs. Anyways: Secure boot was tried to mitgate with the rmmod tpm, and the machine in question only has an integraged GPU and no dedicated one, so altering the graphic chipset manually is not necessary for
[18:48] <webchat23> troubleshooting.
[18:50] <webchat23> tomreyn and thanks for the links. interesting reports.
[18:55] <tomreyn> webchat23: playing with (disabling, where possible) power saving options for i915 *might* help, too, depending on where it fails. but, first of all, let's see whether you get any logs at all on a failed boot, and if so, which,
[18:56] <webchat23> tomreyn Im not one of the users who suffers issues when coming from a sleeping machine - I suffer the issue with a cold boot.
[18:57] <tomreyn> right, i'm aware
[18:57] <webchat23> was just FYI :)
[18:58] <tomreyn> :)
[19:07] <lotuspsychje> webchat23: can you see if bug #1934647 is similar to yours?
[19:13] <webchat23> lotuspsychje as I do not run a dedicated graphic card I wouldnt compare this case to me. The other links to archlinux cases with Kernel 5.11 and 5.12, but with the proper HP board and Intel i915 iGPU sounds narrowing the problem more precise - but sure, maybe its the same underlying reason with that HP board of your suggested ticket aswell.
[19:14] <lotuspsychje> webchat23: ok, tnx for checking anyway, might be indeed more related to screen panel shutting off like on the threads tomreyn found
[19:14] <webchat23> but I could try to test 5.12.4 like in the ticket
[19:14] <lotuspsychje> yeah worth a shot
[19:18] <tomreyn> see if you can get logs first of all
[19:19] <denza252> hmm, does anything make use of projectm? I thought clementine did but apparently it's disabled in the ubuntu build?
[20:13] <webchat70> hey
[20:14] <webchat70> hi
[20:14] <Mekaneck> !ask | webchat70
[20:14] <Mekaneck> !ot | webchat70
[20:16] <webchat70> lotuspsychje tomreyn performed some more tests, and updated the askubuntu ticket accordingly https://askubuntu.com/questions/1348180/black-screen-on-boot-with-5-8-0-59-66-reason-why-delete-kernel long story short: booting a recovery mode kernel works with graphic output, booting the newer kernels DOES work (I logined blind) just is not starting the
[20:16] <webchat70> GPU/Screen. So its quite the issue as described with https://bugs.archlinux.org/task/71003 or https://gitlab.freedesktop.org/drm/intel/-/issues/3569 or maybe even https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934647
[20:17] <webchat70> TJ- check my previous msg if you like
[20:20] <tomreyn> webchat70: "ticket" sounds like "support request ticket", but what you really did, is ask a question on a self-support community.
[20:22] <tomreyn> webchat70: so you should now be in the position to capture and post two system logs: one of  the system with graphical output, and one without graphical output, those could then be compared (by yourself, or someone you can convince to help you do so).
[20:22] <webchat70> tomreyn well true, but as the first paragraph of my self-support ticket stays: I wont open a bug report on launchpad with some creepy gathered knowledge. That is why I use this as a starting ground, in high hopes to not be a burden on the devs and annoy them on launchpad with them explaining me the basics what they need
[20:23] <tomreyn> that's a good approach for sure.
[20:24] <tomreyn> (i just wanted to make sure you don't have / grow wrong expectations.)
[20:26] <webchat70> tomreyn I actually only followed advices until now, no command I hit into the CLI was out of memory. So yeah, I will be able to look up what logs to compare (the journalctl -b log isnt showing too many details... I guess I have to crank up the log quality for debugging, and than compare two boot logs.... but I dont know the commands and got to
[20:26] <webchat70> google them :P)
[20:27] <tomreyn> "journalctl -b" should output some 1000s of lines
[20:28] <tomreyn> hundreds at least
[20:31] <webchat70> tomreyn ah true. any hint how to better access the data than by terminal journalctl -b as the ubuntu terminal is not allowing commands like CTRL+A to mark the 5000 lines?
[20:32] <tomreyn> webchat70: what do you mean to do with it?
[20:33] <tomreyn> i think there's "Gnome Logs", if you're looking for a GUI.
[20:34] <tomreyn> or pipe the output into xclip
[20:38] <webchat70> hehe not to familiar with command lines "piping" the terminal text somewhere else. So I was just asking for a hint. Anyways, if you like to see the logs: 5.8.0-59 with the screen issue https://pastebin.com/uTAUG6XH and 5.8.0-55 that is working fine https://pastebin.com/6qzCSKPR
[21:06] <viperborg> noidea? Like, at all?
[21:09] <oerheks> webchat70, according to line 292; Jul 22 21:39:15 COMPUTERNAME kernel: PM: RTC time: 19:38:41, date: 2021-07-22
[21:09] <oerheks> did you made that log earlier? or is your system time way off?
[21:10] <webchat70> oerheks the log is 2 hours old, the RTC time maybe is without timezone, or the motherboard has a different time, Im not too sure.
[21:18] <nemo> Appears I just encountered this error from 2020-11-11 on the only ubuntu server at work (20.04 LTS)
[21:18] <nemo> https://www.suse.com/support/kb/doc/?id=000019780
[21:18] <nemo> I was wondering if there's any way to tell if this bug fix has made it into 20.04 backports
[21:18] <nemo> my impression was "no"
[21:18] <nemo> https://packages.ubuntu.com/focal/samba  and https://packages.ubuntu.com/focal-updates/samba changelog don't seem to mention anything like this
[21:23] <rbasak> nemo: looks like the fix is in the kernel, rather than samba?
[21:23] <nemo> rbasak: ah. cifs kernel module. right
[21:24] <rbasak> In any case, with the detailed assessment there, it should be possible to examine the sources to see where/if it has been fixed, and similarly to get a fix landed if required.
[21:25] <nemo> I'm starting in my primitive fashion, by figuring out what kernel package on this system currently provides the cifs module
[21:25] <nemo>  /lib/modules/5.4.0-80-generic/kernel/fs/cifs/cifs.ko
[21:27] <nemo> linux-modules-5.40-80-generic  I guess that should've been obvious :)
[21:27] <nemo> so. I'm on the most recent one
[21:28] <nemo> http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_5.4.0-80.90/changelog  nothing obvious in the changelog
[21:28] <nemo> aight. so I guess I need to find the source package
[21:29] <nemo> rbasak: hm. you seem knowledgeable. what's the best way to do that on debian/ubuntu?  I'm guessing https://packages.ubuntu.com/focal-updates/linux-modules-5.4.0-80-generic  and downloading the orig/diff tar.gz is not the most efficient?
[21:30] <nemo> surely there's a magic "gimme the source package" command ☺
[21:31] <rbasak> For the kernel, it's probably easiest to grab the kernel team's git tree
[21:31] <nemo> hum
[21:31] <sarnold> heh, cloning their git tree takes a metric eternity
[21:31] <nemo> sarnold: times like this I miss svn
[21:31] <rbasak> https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide
[21:31] <nemo> meh. lemme try these packages
[21:31] <rbasak>  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
[21:31] <sarnold> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/log/
[21:31] <rbasak> Yeah it'll take a while, but you'll be able to examine history
[21:32] <nemo> sarnold: that is a lot of cifs commits in the log
[21:32] <nemo> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=6c1f332fa8eaa9e32a62488f59d31cead41148f1  has a promising log message
[21:33] <rbasak> surely there's a magic "gimme the source package" command> apt-get source, except that you need to have deb-src lines in sources.list first, run apt-get update, and also know what source package name you're actually after.
[21:33] <nemo> hm. not quite right trace though
[21:33] <nemo> rbasak: well linux-modules-5.4.0-80-generic ☺
[21:33] <rbasak> That's the binary package name
[21:34] <nemo> hm. welp. I guess I should start by seeing if patch was applied in latest tip
[21:34] <nemo> that should be easy
[21:35] <nemo> man I wish git had mercurial's history trawling tooling
[21:35] <nemo> I guess moot point since I don't want to grab the entire repo in either case ☺
[21:37] <nemo> wish I could find the patch in that SuSE bug
[21:38] <nemo> hm. you know what. false trail
[21:38] <nemo> those are all 4.12 kernels. darn it
[21:38] <nemo> just 'cause the error and symptoms are same, and date was last year, doesn't mean it's the same issue ☺
[21:39] <nemo> I guess can't hurt to check dfs_cache.h though
[21:39] <nemo> or rather connect.c
[21:40] <nemo> hmmm hasn't changed much!
[21:40] <nemo> might still be same thing
[21:49] <toke019> exit
[22:18] <Guest6699> HI using Linux Lubuntu 20.04 LTS
[22:18] <Guest6699> Hi, does 'Apply Full Upgrade' GUI program, fully update my computer?
[22:18] <Guest6699> Or should I also run apt update && apt full-upgrade
[22:19] <tomreyn> webchat70: the only difference i can sopt is that on the first log (with black screen), you have:    gnome-shell[1530]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
[22:21] <webchat70> tomreyn what software did you use for comparing them, or have you done this by hand? i will provide your information to my thread or for later bug reports
[22:21] <tomreyn> webchat70: manually
[22:22] <webchat70> thank you!
[22:23] <oerheks> update gui is fine, AFAIK
[22:24] <webchat70> your findings indicate, together with the other bug reports, that its indeed a kernel problem. kinda odd
[22:26] <tomreyn> webchat70: i would guess that it's a problem with the intel i915 module. but you'd need to kernel bisect to tell for sure.
[22:27] <tomreyn> webchat70: earlier, i said "another thing to try would be to disable 'secure boot' in bios", and you replied "Secure boot was tried to mitgate with the rmmod tpm". what i'm wondering, though, is whether this problem still occurs with "secure boot" disabled. did you try this?
[22:28] <webchat70> tomreyn I havent tried turning off secure boot from the bios firmware side, no. as far as I understand rmmod it deactivates the TPM module of the linux kernel, but I am not even sure if that was permanent until a new command is entered, or just for this one time Grub is initialized ...
[22:30] <tomreyn> webchat70: the logs you posted did not show an attempt to permanently disable tpm support using a kernel command line parameter
[22:31] <webchat70> I saw tpm enabled aswell, yes, so Im not sure if the command worked (the docu says if no error is promted there is no further feedback - there was no error prompted.) so I could try to run the command again and post a log of that too
[22:31] <tomreyn> i do suggest you try booting the latest kernel while secure boot is disabled in 'bios'