[00:00] Its commented out in the file though. [00:00] Right now the nvidia driver version installed is 440.62 [00:03] Are you abele to boot with the nouveau driver (maybe need to use nomodeset on the command line)? [00:05] Can you provide guidance on trying that? [00:05] sudo apt purge nvidia-driver-440 [00:06] then try rebooting. If black screen, then reboot again and go into grub. [00:06] You might need to hit Esc to open the grub menu if not multi-boot setup. [00:06] Ok, standby [00:07] will do. [00:08] You might want to try the nvidia-driver-430 or 435 drivers until bug you encountered is fixed. [00:12] FWIW, I have 2 NVidia systems here running fine with the 440.64.00 driver, and the 5.4.0-26 and 5.4.0-37 kernels. (1080 and 960M models resp). [00:13] I've purged nvidia-driver-440, what whas the nomodeset ? [00:14] For the record, I was running 440.82 with 5.4.0-33 kernel before this situation. [00:14] try to reboot. If you get a black screen, then reboot again and tap the Esc key until the grub menu appears. [00:15] Ok... [00:16] I've rebooted, entered encryption pw, and now just the Lenovo image again... originally it'd just go to a black screen, this "lenovo image" thing has been prevalent since I did the `ubuntu-drivers install` command. [00:16] will do the reboot now, and go to grub menu [00:17] Oh, I read somewhere about `kstart5 plasmashell`, is this relevant? Because when I go to TTY2 and login and enter that command, it gives errors about `qt.qpa.xcb` and `qt.qpa.plugin`. [00:18] i'm at `grub>` prompt now [00:18] I think you are fighting graphic driver at the moment. How did you install Kubuntu? [00:18] Select the top line [00:19] There's nothing to select, its a prompt. [00:19] just a "grub>" prompt? [00:19] yes i had the selectable menu before that but hitting ESC brought me to this prompt [00:19] No text menu with kenerel selection options? [00:20] it was on screen before ESC, show sup every boot [00:20] can i get back to that without rebooting, can i exit `grub>` prompt? [00:20] nvm, just rebooting [00:20] Oh, Ok on the selection menu, ensure the top line is selected and hit the "e" key to edit [00:20] 1st option is "ubuntu", 2nd option is "Advanced options" [00:20] yes [00:21] ok done [00:21] https://www.dell.com/support/article/en-us/sln306327/manual-nomodeset-kernel-boot-line-option-for-linux-booting?lang=en [00:21] Let me know if more explanation is needed. === xrootx is now known as schiz [00:21] ok put the `nomodeset`, reading [00:22] EYYY login screen! [00:22] also remove the quiet option to enable the viewing of the boot steram [00:22] didn't remove quiet, but i 'm on my desktop now [00:22] cool! [00:23] so i presume this is a temp solution? [00:23] no need to remove quiet [00:23] that was just to reveal any monsters that may be preventing boot. [00:23] gotcha, [00:23] yes, temp solution. So now try installing the 430 or 435 driver. [00:24] how about 440.82? i still have that DLed [00:25] Sure, git it a try. [00:25] The steps above will restore you back to a system where you can try the other drivers if needed. [00:27] So if 440.82 black screen, ctrl-alt-f2 for the tty, sudo apt purge nvidia-driver-*, boot with nomodeset via grub, and try another driver. [00:27] says i'm missing nvidia-installer-cleanup when i run dpkg -i on the 440.82 driver [00:30] is the 440.82 driver from the nvdia-ppa or downloaded from NVidia? [00:31] downloaded [00:32] the 440.82 driver is weird, says `nvidia-driver-440/focal 440.82+really.440.64-0ubuntu6 amd64` [00:32] Yes, the ppa website is equally mixed.... [00:32] https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa?field.series_filter=focal [00:33] there's still a considerable amount of nvidia things showing when I run `apt list -i | grep nvidia` [00:33] Try enabling the PPA and then run "sudo apt install nvidia-driver-440" [00:34] grep for nvidia-driver-440 and report the version... [00:35] ok.... that's where I see `nvidia-driver-440/focal 440.82+really.440.64-0ubuntu6 amd64` [00:35] I just installed it, since it came from PPA, i don't have to manually sign it fore secureboot do i? [00:35] apt list nvidia-driver-440 -a [00:36] correct, no manual signing will be necessary. [00:36] alright when I run that cmd, another one shows up [00:36] `nvidia-driver-440/focal 440.82-0ubuntu0-0.20.04.1 amd64` [00:36] that's what I see here also. [00:37] i read a reddit threat discussing why the "really" one is there. [00:37] And apt says: nvidia-driver-440/focal,now 440.82+really.440.64-0ubuntu6 amd64 [installed] [00:38] is there a way to force the 440.82 (actual) install via apt since it shows up with `apt list -a`? [00:38] Oh, still have the link? I do not know why we have 2 options. [00:38] no idea... [00:38] https://www.reddit.com/r/linux_gaming/comments/g3mrex/why_did_ubuntus_graphics_ppa_push_a_downgrade_to/ [00:39] is it a terrible idea to `apt purge *nvidia*` and start over? [00:39] nope, apt purge should work fine. [00:40] for *nvidia*... or just nvidia*? [00:40] I have used it myself several times before my hybrid laptop was properly supported. [00:40] nvidia-* is fine [00:41] Uploaded file: https://uploads.kiwiirc.com/files/26c058fb2e3c3b37399c2a1106159f9e/pasted.txt [00:41] ^ that's the output from `apt list -i | grep nvidia` [00:41] There's a bunch of "libnivida-*" things in there [00:42] yes, all of those will be cleaned up as they depends of the main driver... [00:42] Assuming the packages are setup properly. [00:42] run the purge and check again. [00:42] ahh ok [00:44] this is weird, i type `sudo apt purge nvidia-*` and it says "unable to locate package nvidia-*" [00:45] try sudo apt purge nvidia* [00:45] doing the same thing [00:46] sudo apt purge nvidia-driver-440 [00:46] that' worked. [00:46] guess you cant wildcard that [00:47] ok, so the driver isn't in the `list -i` anymore... but everything else still is [00:47] ahh, need to do `autoremove` i think [00:47] do you have any nvidia files in you current directory? I have seen where apt will try to act on any files in your current directory when the wild card is used (very strange and unexpected behavior). [00:48] try sudo apt autoremove [00:48] I did that now there's only 4 left... [00:48] Uploaded file: https://uploads.kiwiirc.com/files/9612ed0994b4c465fcb1db792cdd9c08/pasted.txt [00:49] should i purge those too? [00:49] yes, I would [00:49] the linux modules one too? [00:50] i presume i'm going to have to sign the 440.82 driver if i do it from .deb [00:50] Yes, if you use the deb route, I suspect manual signing may be required. [00:51] i've got the whole list nuked. [00:51] can i force apt to use the "actual" 440.82 driver? [00:52] i think i can [00:52] I have no idea how to force the 440.82 only driver. [00:52] How did you do it? [00:53] `apt install nvidia-driver-440=440.82-0ubuntu0-0.20.04.1 [00:53] https://askubuntu.com/questions/428772/how-to-install-specific-version-of-some-package [00:53] cool! [00:53] getting complaints about unmet dependencies though [00:53] like what? [00:53] Uploaded file: https://uploads.kiwiirc.com/files/5f49a51e5e39a4c59db4eb21bc6a8a16/pasted.txt [00:54] i'm going to get castrated if i don't go eat dinner with the fam right now... lol i'll come back to this if you're still here. I greatly appreciate your help/guidance! [00:55] what if you try sudo apt install —fix-broken [00:55] very good :) [00:56] this should fix the issue: sudo apt install nvidia-driver-440=440.82-0ubuntu0-0.20.04.1 xserver-xorg-video-nvidia-440 [00:56] ooh pizza night, have a few mins before its ready [00:57] I have had to explicitly specify the xorg server version when installing bleeding edge drivers. [00:57] I typed that and got the same output... about dependencies. [00:58] is `--fix-broken` cmd by itself, or add to apt install? [00:58] i'm going to install from .deb and sign it. [00:58] keep adding the files in the depends.... [00:58] i don't want it installing this "really440.64" stuff [00:58] ok [00:59] i have quick scripts to generate and sign for kernel updates... have to do it for vmware workstation too [01:00] my packages seem to be the 82 version even though the 64 package is installed: https://pastebin.com/7FZKfeie [01:01] that's how mine was, i interpret that as saying the 440.64 driver is actually installed [01:02] nm, yes i agree.. seems to be the 64 packages. [01:02] what's in 82 that you need? [01:04] Well installing the 440-82(really440.64) drivers i don't get login screen remember? [01:04] we had to do `nomodeset` [01:04] so i think reinstalling this won't do much good [01:04] i mean, i can try [01:05] yeah i'm going to let that rip [01:05] I am not sure if the deb installed all the necessary deps. But at least you know how to recover now to try other stuff. [01:05] i do, thank you! I can tinker around and if I come up with a solution i'll chime in. [01:06] Excellent, yes please let me know what works. [01:06] going to copy the install log [01:07] Yikes.. yeah errors... [01:07] Uploaded file: https://uploads.kiwiirc.com/files/8745b6ab3e2fb6aa8c28e8230eab7433/pasted.txt [01:08] note sure why it says secureboot not enabled, it absolutely is [01:09] hmmm, that is strange.... [01:21] hmm, errors might be nothing... says things are already found in kernel [02:47] DarinMiller oddly enough I'm even getting the issue with all nvidia drivers purged [02:48] ... but now my tty2 was flashing too... tf [03:41] @DarinMiller - I'm up and running with `nvidia-driver-435` and kernel 5.4.0-37. Over the 440 driver for now, haha too much time lost. [03:42] tets [03:42] test [03:42] test complete? [03:43] Seems so. ;) [03:43] yes [03:43] this works [03:43] didnt know if this worked as this is my firt time using IRC [03:46]

did you succeed with your driver install? [03:47] I'm up and running with `nvidia-driver-435` and kernel 5.4.0-37. Over the 440 driver for now, haha too much time lost [03:47] understood. [03:47] I purged all things nvidia again and rebooted, was able to get on both .33 and .37 kernels with nouveau [03:47] used app to install 435 and here i am. [03:48] i'd like to get up to 440 but i think i'll wait for the ppa version of "actual" 440.82 [03:48] apt* [03:48] Yes, I agree. If you discover another solution please post here. And I will do likewise. [03:49] i def will, but might be better to contact direct since i don't idle here on IRC or telegram [03:49] that would be fine also [03:50] Looks like IRC bot can't do /msg between IRC and telegram, sec [03:50] I opened konversation [03:51] dereksmiley was added by: dereksmiley [03:52] sent you msg on telegram [04:45] AlejandroCastro was added by: AlejandroCastro [04:52] Hi, I am having a problem triyng to run hexter on Kubuntu 20.04 … I update and upgrade packages … After runnning "jack-dssi-host /usr/lib/x86_64-linux-gnu/dssi/hexter" in a terminal I got the error "Gtk-WARNING **: Unable to locate theme engine in module_path: 'adwaita'" so I installed gnome-themes-standard and gnome-themes-extra. Now hexter starts and even I can se it in qjackctl connections panels, but ui does not show. [04:52] suggestion? [04:58] I have never run hexter. Look like it needs a jack server to run... === robert_ is now known as Guest76378 [04:59] You might want to ask on the ubuntu studio channel as they should more audio experience then the general audience here. [04:59] yes, I tryed running jack before. Nothing change. … If i do not that then jackd starts anyway [05:00] ok, I thought it is a problem related to GTK apps in Kubuntu. [05:01] Is there a popular GTK app that I can test in Kubuntu to limit the problem? [05:01] studio is in the process of converting to KDE, so they may have encountered and possibly solved the problem. In fact, quite a few of the Devs already run KDE. [05:02] gimp? [05:02] but its gtk 2.xx [05:06] well, I am going to test Gimp. I am a Kubuntu user since ~2016 I think. Hexter works fine in plasma for 17.04 and 19.10 version of Kubuntu [05:06] Thanks [05:06] This channel is great [05:08] Gimp works perfectly 😩 [05:08] I wonder if it runs on regular ubuntu..... have you asked if anyone in the Ubuntu channel is successfully running on 20.04? [05:11] That is a good idea. Let me check [05:13] "Hi i am an user of another distro but i need your help" … hahahaha [05:13] :) [05:23] Morning everyone. [05:23] (Photo, 800x536) https://irc-attachments.kde.org/gPdyIIjN/file_31972.jpg Every time I install a flatpak from discover - I get this crash notification: [05:40] @AlejandroCastro, This should solve the adwaita issue: sudo apt install gnome-themes-standard [05:41] Then run hexter as follows: pasuspender jack-dssi-host /usr/lib/*/dssi/hexter.so [05:41] you may need to manually kill any residual jack sessions. [05:42] however, on my system, I see this error: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) [05:44] @DarinMiller, this is due you must add your user name to audio group, and allow audio group to run in real-time [05:44] Did the above fix hextor for you? [05:47] however, I think this is a problem in my system, There are a weird behaviour with hexter deamon. It shows the message: … jack-dssi-host: OSC URL is: … osc.udp://abc:16301/dssi//usr/lib/x86_64-linux-gnu/dssi/hexter/hexter/chan00 … but abc does not mean nothing in my system … dismiss my request for now, I will tell what is happening if I let it work [05:47] ok, thanks! [05:48] pffff, thanks to you [05:52] More fun stuff on the way: https://pointieststick.com/2020/06/12/this-week-in-kde-plasma-5-20-features-start-landing/ [08:30] sigAIO: I don't know if you're online, but I managed (without doing anything) to get the same speed as I did before... I now have 890Mbps on Fast.com [08:30] Also performed a test on Speedtest.net: https://www.speedtest.net/result/9598271786 [08:31] I removed the connection from the list, and perhaps a reboot is what solved it. === jds is now known as Guest34339 === michael_ is now known as BBQBun71 [09:55] hi === josh is now known as Guest3281 === Lord_of_Life_ is now known as Lord_of_Life === richard is now known as Guest16840 [11:29] 'Morning folks [11:30] Hi there, from time I get disconnected from wifi and prompted for the password, however my router is stable and not going down, signal is strong and good quality and the password is stored on the system (for all users, non encrypted). My battery is not low and I disabled wifi power management for good measure. This has been happening with Kubuntu (and any other KDE Plasma based systems), but not with other DEs, using the same setup and also [11:30] networkmanager. Does anybody have this same problem or know why this is happening? Running 20.04 but happening since 18.04. === richard is now known as richard__ [11:32] This is happening on my three laptops with different wifi chips, by the way - so I would rule out drivers or hardware failures... [11:38] erts, one thing to check is your wifi channel on your router and check the auto option if there is one, if not change the default wifi channel from 6 to one which is less busy. Most wifi users on windows don't do this, but channel 6 can get very crowded in some environments that have alot of users nearby which can cause dropouts. [11:41] And it happened again... [11:42] BluesKaj: yep I tested that but didn't notice a difference. Still, even if I get micro-cuts I shouldn't be asked for a password every single time...there's something going on with Plasma [11:42] Every time I get prompted, I hit cancel and then connect manually through the NM plasmoid and I don't get the password prompt === erts__ is now known as erts [11:54] erts, so if I understand correctly you're having issues with WiFi on Kubuntu 20.04? If so, you're not alone... I also had issues since 18.04. Had no issues with Linux Mint but they appeared when I installed Kubuntu. [11:55] Dakeiiz: nice to hear I'm not alone, and I'm sorry to hear that...this is so annoying... :P [11:55] Did you do any troubleshooting or have any findings so far? [11:56] I've experienced these problems with any distro using Plasma, actually... [11:56] I'm afraid to say that I've given up using WiFi whatsoever... It's not a big deal for me because I have easy access to wired ethernet. [11:56] Ah I see. It's always a bit hard to say whether it comes from the kernel, the distro or the DE [11:57] Smart decision, not an option for me though.... :( [11:58] Yeah checking the logs it just seems like the connection drops and that's it. I do expect micro-cuts, or in some environments to have unstable wifi and have to re-connect (not at home, but in other places). However it doesn't make sense to me that I keep being prompted for the password! [11:59] It's like Plasma itself forgets it has the password stored in NM, and when I click cancel and re-connect manually, it gets it fine [11:59] where I can search for code related to the System Settings -> Online Accounts? [11:59] Maybe it's because the connection is getting "reset" (removed/re-added), so Plasma thinks it's a new connection. [12:00] According to the logs, no sign of that... NM does try to reconnect several times in a row though, so maybe the router is doing some kind of throttling and Plasma thinks the stored password is incorrect... [12:00] I wonder if there's a way to slow down the re-connection attempts [12:01] Then I could go on to troubleshoot the stability of my router, maybe I was wrong about that. Still very weird behaviour to annoy me asking for passwords that are stored [12:08] You've said you had the same problem with all distro running Plasma, so I assume you've tried with a completely different DE? Did it work as expected? === luca is now known as luc4 [12:29] Hello! Anyone running nvidia drivers on nvidia Quadro by any chance? [13:19] Hello [13:30] @Swift110, hi === _heavyarms is now known as heavyarms [13:44] How r u [13:48] @Swift110, no textspeak here please, use full words [13:48] but I'm fine, how about you? [14:03] Laurel.Canyon.S01E01.Part.1.1080p.AMZN.WEBRip.DDP5.1.x264-NTb[TGx] [14:03] oops === sebastian_ is now known as ThxGiving [14:10] does kubuntu have anything that will display hardware info, kind of like everest? Kinfocenter doesn't display any hardware information. [14:10] And it seems like my cpu fans are running at 100%. This wasn't an issue on 19.04 [14:10] or 19.10 [14:20] madeti_, run lspci in the konsole [14:21] oops [14:21] no patience [15:23] RandomPaulTelegram was added by: RandomPaulTelegram [15:24] How is it possible to install the latest Plasma on Kubuntu 20.10 beta? === lex is now known as Guest2592 === lex is now known as Guest49495 === TheMetamorphosis is now known as Metamorphosis === lex is now known as Guest98579 === lex is now known as Guest95099 [18:10] can someone help me with clonezilla? I asked on their IRC channel but it seems it's dead [18:10] Maybe is also related with Kubuntu because it can't find my NIC when I try to use it to create an image via ssh === custom_ is now known as custom__ === TheMetamorphosis is now known as Metamorphosis [21:04] (Photo, 1280x720) https://irc-attachments.kde.org/mD100z07/file_32045.jpg Please can anyone help me with this error in kdenlive? It's unable to export.. [21:05] My 6 hours wasted 🤦 can't even export now .. any help please === gurmble is now known as grumble [22:45] hello? [22:50] AlejandroCastro was added by: AlejandroCastro [22:55] (Photo, 800x600) https://irc-attachments.kde.org/NYok0v0b/file_32050.jpg Same problem on Ubuntu liveUSB. I will keep looking. [22:58] @AlejandroCastro that sounds like a failing drive [22:58] I would back up NOW everything you want to keep [23:01] Valorie, Alejandro is trying to run hexter. I can reproduce the problem on my machine. He was testing regular Ubuntu to bisect the issue. Apparently its a packaging problem in 20.04 not specific to KDE. [23:01] ah, OK [23:01] thanks @DarinMiller [23:02] How are things out your way? [23:02] I am very well, thanks. :) [23:02] cool and damp here [23:02] And you? [23:02] Same here. [23:02] people are calling it Junauary [23:02] :-) [23:02] I don't mind it a bit [23:02] oops, Junuary [23:03] Perfect [23:03] I'm good, got my gardening in when it was less damp [23:03] and the flowers don't mind cool and damp one bit === Lord_of_Life_ is now known as Lord_of_Life