[00:02] <genii> Having it still able to use internet through whatever alternate method for the time being means it becomes easier to directly investigate the issue, which is good
[00:03] <nano2> I cand send pastebins (Code: 0) There was an error with TheP(aste)B.in!
[00:03] <valorie> try pastebinit from the commandline if you need it
[00:04] <genii> !pastebinit | nano2
[00:04] <ubottu> nano2: pastebinit is the command-line equivalent of !pastebin - Command output, or other text can be redirected to pastebinit, which then reports an URL containing the output - To use pastebinit, install the « pastebinit » package from a package manager - Simple usage: command | pastebinit
[00:04] <valorie> !pastebinit
[00:04] <valorie> lol
[00:04]  * genii slides valorie a stronger coffee
[00:04] <genii> ;)
[00:04] <valorie> rofl
[00:06] <genii> nano2: So in this case, you'll want to open up konsole and keep it handy. The first thing in there to probably to and make sure things are up-to-date is: sudo apt-get update and then: sudo apt-get install pastebinit
[00:07] <genii> if the package called lshw is not installed, install that as well with: sudo apt-get install lshw
[00:07] <nano> I found the driver of that wireless card and put it in / lib / firmware /, I already restarted but I think that's not all there is to do
[00:08] <genii> ...
[00:09] <genii> It's better to investigate the issue first before copying stray driver files into the root filesystem :)
[00:09] <nano> Pastebinit is already in its most recent version (1.5-2).
[00:10] <genii> The first issue to tackle is wifi
[00:10] <genii> lshw is useful for this because it can tell us what devices are unclaimed by a driver
[00:11] <nano> (Code: 0) There was an error with TheP(aste)B.in!  again
[00:12] <genii> I'm not certain what that error is about, possibly some 3rd-party pastebin URL is being used
[00:13] <genii> But if we pipe command output to the application pastebinit, it should not matter
[00:14] <genii> If you can please run: sudo lshw -C network | pastebinit    ...and then let us know the URL it gives you we can start there
[00:15] <nano> http://paste.ubuntu.com/p/2CSCs36HrF/
[00:16] <genii> Yes, so there we see the second netowrk device is unclaimed by a driver
[00:17] <nano> Yes
[00:18] <genii> Next, please: lspci -nn|grep Network|pastebinit
[00:18] <genii> This will give us the Vendor:Device code
[00:18] <genii> ..so 8086:something
[00:20] <nano> http://paste.ubuntu.com/p/fX3Dy8tMR2/
[00:21] <nano> Drver is here
[00:21] <nano> https://www.intel.la/content/www/xl/es/support/articles/000005511/network-and-i-o/wireless-networking.html
[00:21] <nano> Intel® Wi-Fi 6 AX200 160MHz
[00:22] <genii> Please be patient, I am examining a bug right now regarding this issue ( https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1828133 )
[00:22] <ubottu> Launchpad bug 1828133 in linux-firmware (Ubuntu Bionic) "Intel CyclonePeak wifi firmware" [Undecided,Fix released]
[00:24] <genii> Seems like the correct driver may now be in the package linux-firmware repository bionic-proposed if you are on 18.04
[00:25] <genii> nano2: What version of *buntu does the command: cat /etc/issue   ..tell you?
[00:27] <nano> Ubuntu 18.04.3 LTS \n \l
[00:31] <genii> I would suggest then to enable the "proposed" repository, then run : sudo apt-get update ... then after: sudo apt-get upgrade
[00:31] <genii> !proposed
[00:31] <ubottu> The packages in Kubuntu are divided into various sections. See https://help.ubuntu.com/community/Repositories/Kubuntu - See https://wiki.ubuntu.com/RecommendedSources for the recommended way to set up your repositories
[00:33] <genii> linux-firmware is a package which should already be installed by default, but to make sure, the command: apt-cache policy linux-firmware  ..should tell you for certain, also what repository the one you are using came from, or the ones which different versions reside
[00:34] <nano> http://paste.ubuntu.com/p/G34gfnGnSQ/
[00:39] <genii> Since we do not see the bionic-proposed repository there, you should enable that and then follow the instructions I outlined earlier, just above
[00:40] <nano> I'm in the origins of the software and I don't see proposed repositories
[00:41] <nano> How I enable proposed repositories?
[00:42] <genii> Hm, the !proposed factoid seems hopelessly out of date
[00:44] <nano> how I can install the driver?
[00:44] <genii> nano: In this case, simplest is to: echo "deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted main multiverse universe" | sudo tee -a /etc/apt/sources.list
[00:44] <genii> ..and then do the steps earlier described
[00:45] <nano> But proposed repositories is out of date
[00:47] <genii> No, proposed repositories contain newer versions than what are available in the main repositories. They are generally put in proposed if it is planned to later put them into the main ones after being tested
[00:48] <genii> ( and then approved for inclusion )
[00:52] <genii> nano: ..and to answer the question of "how I can install the driver?" , what I am trying to guide you to accomplish is: by having the proper firmware files installed, these should load when the system sees the device, and then the iwlwifi driver should automatically be in use afterwards
[00:53] <genii> The firmware file gets pushed to the wifi adapter, driver loads, wifi works ... is the objective currently
[00:53] <nano> I need restart
[00:55]  * genii quietly sips his coffee
[01:07] <nano> Hello again, I have done everything commenting, 8 packages and 3 new linux kernel headers were installed but everything remains the same
[01:11] <genii> nano: Does: sudo lshw -C network  ...still show the adapter as unclaimed?
[01:12] <nano> http://paste.ubuntu.com/p/j7GFSC6JCP/
[01:14] <genii> ..so yes, still unclaimed
[01:15] <nano> yes
=== root is now known as Guest42930
[01:18] <genii> nano: does: lsmod| grep iwlwifi  ...show a result?
[01:20] <nano> nope
[01:23] <genii> nano: I am curious now to see if manually loading the driver does anything. So please: sudo modprobe iwlwifi     ...and then: lsmod | grep iwlwifi    ... to see if the second number is a zero ( meaning no device is using it, even though it is loaded) or a different number
[01:26] <nano> iwlwifi               311296  0
[01:26] <nano> cfg80211              675840  1 iwlwifi
[01:26] <swift110> hmm
[01:27] <swift110> hey nano
[01:27] <swift110> hey genii
[01:27] <genii> So now something is using it
[01:28] <genii> ..sorry, no, zero there
[01:29] <swift110> oh ok
[01:29] <nano> Did you mean: No reconoce nada aun network mánager
[01:29] <nano> 36/5000
[01:29] <nano> Do not recognize anything even network manager
[01:36] <genii> Hm, Intel AX200/201 seems to require kernel 5.1 onwards
[01:36]  * genii pokes around some more
[01:46] <genii> nano: So I think I have discovered that the issue is that if you have a lesser kernel version than 5.1 ( and the latest kernel version available in 18.04 is linux-image-generic-hwe-18.04 which is version 5.0.0.25.82 ) then the driver must be backported as described here:  https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release#how_to_install_the_driver    ...for this you will need to istall the package git
[01:49] <genii> !info linux-image-generic disco
[01:49] <ubottu> linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 5.0.0.25.26 (disco), package size 2 kB, installed size 15 kB
[01:49] <genii> Hm
[01:50] <genii> !info linux-image-generic-hwe-19.04 disco
[01:50] <ubottu> Package linux-image-generic-hwe-19.04 does not exist in disco
[01:50] <genii> !info linux-image-generic-hwe disco
[01:50] <ubottu> Package linux-image-generic-hwe does not exist in disco
[01:51] <nano> Can't fix it then?
[01:51] <genii> !info linux-image-generic eoan
[01:51] <ubottu> linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 5.2.0.13.14 (eoan), package size 2 kB, installed size 15 kB
[01:55] <genii> nano: It can be fixed, by the backporting of the driver as I said just earlier. But yes, this is not ideal. The iwlwifi driver should work out of the box right now with eoan ( Ubuntu/Kubuntu 19.10 but it is not officially released yet) or else later on when higher kernel versions are made available to Bionic ( 18.04 )
[01:56] <genii> ..but if it requires working immediately on the system you currently have, then compiling it manually is the only way
[01:58] <nano> For now I only have to connect with cable in kubuntu?
[01:59] <genii> nano: If you install the package called git first with: sudo apt-get install git   ...and then follow exactly the instructions given here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release#how_to_install_the_driver  then it SHOULD work
[02:00] <genii> ..but as I have not performed this myself or have direct firsthand knowledge this is only an educated guess
[02:03] <nano> have installed got but without configurate
[02:03] <genii> This is based on my reading of this thread https://forums.linuxmint.com/viewtopic.php?t=297284 and a couple other similar ones
[02:05] <nano> it's only 3 steps
[02:05] <genii> Another tactic would be to install a mainline kernel in your existing 18.04 but I would not recommend this
[02:06] <genii> nano: Yes, just the 3 steps
[02:07] <genii> git clone https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git   then: make defconfig-iwlwifi-public && sed -i 's/CPTCFG_IWLMVM_VENDOR_CMDS=y/# CPTCFG_IWLMVM_VENDOR_CMDS is not set/' .config && make -j4    then: sudo make install
[02:09] <genii> Since build-essential is installed by default already, it would only require installing git first before attempting
=== feodoran is now known as Guest34627
=== feodoran_ is now known as feodoran
[02:46] <nano> make defconfig-iwlwifi-public
[02:46] <nano> No hay ninguna regla para construir el objetivo 'defconfig-iwlwifi-public'.  Alto.
[02:46] <nano> 82/5000
[02:46] <nano> There is no rule to build the goal 'defconfig-iwlwifi-public'. Stop.
[02:47] <nano> show me that
[02:47] <nano> I continue?
[02:50] <genii> No
[02:50] <nano> Ok
[02:52] <genii> nano: Give me a couple minutes, I am going to try duplicating the instructions here myself on this 18.04 machine
[02:52] <nano> ok, I think I should enter the backport-iwlwifi folder before putting that command
[02:53] <genii> Probably :)
[02:53] <nano> Yeah I need do that lol
[02:56] <genii> nano: Within the backport-iwlwifi directory all the commands so far have executed successfully for me, it is working now on the actual compiling of the make -j4 command
[02:56] <nano> Done, no problems, I need reboot
[02:56] <genii> nano: I shall hope to see you here soon and hear of the results
[03:01] <genii> Yep, one of those... 8086:2723, can't recall which AX2xx but one of those series
[03:01] <genii> rb25girl: ^
[03:01] <rb25girl> ah okay
[03:02] <rb25girl> I have an AX200 so
=== lex is now known as Guest82598
[03:14] <nano> Heyyy geniii wifi is aliveeeeeeeeeeeeeee
[03:14] <nano> Really you re a genni
[03:14] <genii> Yay!
[03:15] <nano> Thank you so much
[03:15] <genii> nano: If you require further help tomorrow with your NVidia I will be here again also
[03:15] <valorie> nano: \o/
[03:15] <nano> Thank you so much
[03:16] <genii> ..but at this time I want to go have a beer and relax :)
[03:16] <genii> nano: Glad to assist
[03:16] <valorie> you have earned it tonight, genii!
[03:16] <nano> Really thank you
[03:16] <genii> valorie: :)
[03:17] <valorie> :-)
[03:17] <nano> I would never have found the solution without you
[03:18] <genii> nano: The main thing is not to despair quickly, and methodically approach the problem, and a solution will normally be found
[03:18]  * genii wanders off for beer
[03:19] <nano> It is what I see of you, which was methodical from the beginning to locate the problem, but to be methodical you have to have knowledge
[03:19] <nano> Thank you again genniii
[03:34] <IrcsomeBot> Marian Schaller was added by: Marian Schaller
[03:34] <IrcsomeBot> <Marian Schaller> (Photo, 200x200) https://irc-attachments.kde.org/D70ikaT0/file_17470.jpg
[03:34] <IrcsomeBot> <Marian Schaller> hxsoj hpziga ttsx db
[03:40] <IrcsomeBot> <bauchhaus> (Document) https://irc-attachments.kde.org/riPigunU/file_17471.mp4
[04:14] <IrcsomeBot> <Swift110> Hmm
[04:53] <valorie> blocked the spammer
[05:00] <swift110> good
[06:33] <lordievader> Good morning
=== wodencafe is now known as christopherbryan
=== christopherbryan is now known as ChristopherBryan
[06:57] <viewer|54> hallo
[07:00] <viewer|54> what is the best possibility to export only a few bookmarks in firefox?
[07:01] <viewer|54> what is the best possibility to export only a few bookmarks in firefox in Kubuntu?
[07:02] <viewer|54> no response?
[08:43] <paul__> hello all, so yesterday i was here asking for elp because my hdmi socket on my laptop wasnt working. You guys told me to go away and do a fresh install of kubuntu 19.04 that didnt work so after a few more atempts at installing 18.04 i finally have it installed. However there are still problems i cant solve the first being the hdmi still dosnt work i still get the message no external monitor detected
[08:47] <paul__> anyone
[08:48] <diogenes_> paul__, what did you do/install after the fresh install?
[08:49] <paul__> i have done nothing this is the fresh install i just clicked update that is all i have done nothing else
[08:50] <diogenes_> paul__, now run: sudo apt update && sudo apt upgrade
[08:52] <paul__> https://paste.ubuntu.com/p/hSBP8wRZ2d/
[08:53] <diogenes_> paul__, now run: lsb_release -a
[08:54] <paul__> https://paste.ubuntu.com/p/tQrSGBRbzx/
[08:54] <diogenes_> paul__, so how 19.04 didn't work?
[08:54] <diogenes_> why you are back to 18.04?
[08:56] <paul__> 19.04 just kept on crashing i tried about 5 times thats why i am back today and not yesterday even this install isnt right i dont think because i get a message when i power up the machine
[08:56] <lordievader> paul__: What is the output of `xrandr` and `xrandr --listproviders`?
=== MANIAC is now known as Guest33115
[08:59] <paul__> https://paste.ubuntu.com/p/NTkFqmdQCD/
[08:59] <lordievader> Laptop with two video cards?
[09:00] <paul__> i think so
[09:00] <lordievader> Could you pastebin the output of  `sudo lspci -k`?
[09:01] <paul__> https://paste.ubuntu.com/p/73cXRVvSV9/
[09:08] <paul__> any ideas why its not working??
[09:10] <lordievader> Yes, you have two competing modules. How did you install the nvidia driver?
[09:11] <paul__> i never i havent installed anything this OS was installed completly fresh this morning then updated thats all i personally havent installed anything
[09:12] <lordievader> Interesting. What does `dpkg -l|grep -e nouveau  -e nvidia` give?
[09:13] <paul__> https://paste.ubuntu.com/p/79Tj5nXstg/
[09:14] <paul__> i just want to be able to have the screen on my TV
[09:14] <lordievader> Run `sudo apt purge \*nvidia\*` and reboot.
[09:30] <viewer|64> hi guys its paul again my laptop has crashed again when I restarted after doing the purge command, when I start the laptop up I gat a message say bios contains wgds but not wrds will this have something to do with it crashing all the time ]
[09:31] <viewer|64> would secure boot cause the laptop problems as well, it was working fine before I done the fresh install it was literally just the hdmi that didn't work
[09:33] <lordievader> Crashed how?
[09:34] <lordievader> Black screen, boot loop, etc?
[09:35] <viewer|64> when I enter my password the main screen with the logo comes up and that's it it freezes
[09:36] <viewer|64> the part were it says in the bottom right plasma made by kde
[09:37] <viewer|64> this is becoming very frustrating do you think its something to do with the bios
[09:37] <lordievader> Could you switch to a tty at that point and check how many kernel modules are loaded for your nvidia card?
[09:38] <viewer|64> I cant do anything I done thepurge command that all worked then I rebooted and its crashed
[09:38] <lordievader> You just mentioned you can get to the login screen.
[09:39] <viewer|64> but to be fair I don't think its because of the purge command because it was doing this yesterday I couldn't get it to work at all I think its something to do with the bios maybe the secure boot or the file system I dint know
[09:40] <viewer|64> yes I can get to the log in screen all the time
[09:40] <IrcsomeBot> Kathy Woods was added by: Kathy Woods
[09:40] <IrcsomeBot> <Kathy Woods> (Photo, 400x400) https://irc-attachments.kde.org/WZekmdsm/file_17474.jpg
[09:40] <IrcsomeBot> <Kathy Woods> y btlxguy
[09:40] <lordievader> So at the login screen switch to a tty and check if multiple kernel modules are loaded for your nvidia card.
[09:41] <viewer|64> tty?
[09:41] <lordievader> Ctrl + alt + f3, switches you to tty3. Login there and you get a command prompt.
[09:42] <viewer|64> nothing is happening when I do that
[09:43] <lordievader> Did it freeze at the login screen? Can you still move the mouse cursor?
[09:43] <viewer|64> not any more now it has froze since I donte that
[09:43] <lordievader> What?
[09:43] <viewer|64> the mouse has disappeared
[09:45] <lordievader> Hrmm, perhaps you want to boot with `nomodeset` to try and fix this mess: https://askubuntu.com/a/38834
[09:46] <viewer|64> I thought a fresh install would fix it all to be fair
[09:46] <lordievader> Those dual graphics setup laptops have nowadays are always troublesome under Linux.
[09:46] <viewer|64> should boot mode in the bios be uefi
[09:47] <viewer|64> really don't want to go back to windows
[09:48] <lordievader> Preferably
[09:48] <lordievader> Did the live environment work for you?
[09:49] <viewer|64> yesit worked in the live environment the hdmi didn't
[09:49] <lordievader> Hrmm, the hdmi didn't?
[09:50] <lordievader> https://askubuntu.com/questions/1078964/driver-for-ubuntu-18-04-lts-that-supports-gtx-1050-ti-graphics-card
[09:54] <viewer|64> thanks for the help lordievader
[11:02] <BluesKaj> Hey folks
[11:11] <viewer|64> hello
[11:18] <IrcsomeBot> <Swift110> Hello as well
=== Paradisee is now known as Paradiseeee
=== Paradiseeee is now known as Paradisee
[11:52] <lordievader> Hey BluesKaj, swift110
[11:57] <BluesKaj> hey lordievader
=== matthew_ is now known as Guest42780
[13:35] <satria> hola
=== lordievader is now known as Guest78197
=== tux is now known as Areador
[14:39] <Areador> hello, my kubuntu does recognize the microphone, on volume -> applications too, but when i use a programm which uses the micro it does not process any acoustic, does somebody know this problem?
=== adam_ is now known as b34r
[16:16] <MoPac> Hello. I'm wondering if there is a standard way to disable the sddm lock screen's displaying of a description of the currently open browser tab. It feels sort of...opposite...to what my instinct says a lock screen should be doing.
[16:23] <RikMills> Screen locking in systemsettings > Appearance > untick Show media controls
[16:23] <RikMills> I would imagine that is why it is showing
[16:26] <MoPac> Ah, I had seen people talking about media controls, but I figured this was different, or part of browser integration.
[16:27] <MoPac> I actually don't have that menu flow that you described, but I'll try unticking show media controls by > kcmshell5 screenlocker
[16:29] <MoPac> ...which works, in the sense that now there's nothing there. I guess it would have been nice to keep the media controls for actual media, but c'est la vie
[16:29] <MoPac> thanks
[16:33]  * genii fiddles with the VLC controls on his phone's KDE Connect as the lock screen just sits there showing nothing incriminating
[16:36] <MoPac> hah, well I've had to disable kdeconnect completely because of a bug that causes it to crash my sessions
[16:36] <MoPac> receiving a call spams my desktop with hundreds, nay thousands, of notifications
[16:37] <genii> Yes, I had this issue previously with it
[16:39] <MoPac> genii did you do something specific to alleviate the problem, or did it resolve with an update?
[16:40] <genii> I just disabled showing notifications in the KDE Connect control panel settings on the computer side
[16:41] <genii> ( this is under Xenial, I'm running Bionic now )
[16:43] <genii> I primarily use it for photo transfer and controlling whatever is plaing on VLC on the computer
[16:43] <genii> playing
=== himcesjf_ is now known as him-cesjf
=== OvermindDL1_ is now known as OvermindDL1
=== juboxi is now known as jubo2
[18:36] <fni> peeuuh
=== Guest78197 is now known as lordievader
=== tim is now known as Guest62431
=== kubuntu is now known as Guest85779
=== wodencafe is now known as ChristopherBryan