[00:44] <CoreDreamSol> Hi friends, I am trying to join the Linux revolution, slowly but surely. :-)
[00:44] <CoreDreamSol> Also good afternoon/evening/morning.
[00:44] <Unit193> Howdy.
[00:45] <CoreDreamSol> I am being told Looking Glass is a good KVM companion so I can use my Nvidia GPU in a VM?
[00:45] <CoreDreamSol> I still need my Steam games and certain Adobe products so I'm forced to use Windows 10 as a vm anyway,
[00:45] <CoreDreamSol> Hi hi
[00:50] <CoreDreamSol> Is it hard to set that up?
[00:50] <CoreDreamSol> I assume I can use either QEMU or VirtualBox, both have KVM
[01:44] <user______> nyess
[01:44] <user______> hollo world
[01:44] <CoreDreamSol> hello
[01:45] <CoreDreamSol> love flybys
[02:02] <GSMarquis> I dropped Windows, Mac OS, for proper Ubuntu and its flavors 8 years ago today. It was a start of a Christmas extended vacation break from work and had the time to play. I boot Windows once a year for Turbo Tax. Other than that, its been an Ubuntu or flavor ever sense.
 4585
[03:03] <joe__> hello
[03:05] <joe__> hhenlo so
[03:07] <joe__> hio
[03:10] <joe__> hello people
[03:11] <juano-M> <juano-M "kdeconnect in Kubuntu is not det"> Ok, I just discover by try and error, it appears that the new company's router may have a hidden firewall. It was installed 2 weeks ago. 😏
[03:50] <magic_ninja> how should I upgrade to 20.10 if packages have been held back?
[03:50] <magic_ninja> Should I just wait until they are not held back anymore?
 What packages are held back?  If the held packages are due to a ppa  package, you may need to  ppa-purge .
[05:12] <Hash> When I click downloaded files in chrome, they don't open in the associated program in KDE. They used to in 18.04
[05:12] <Hash> In 20.04 it no longer works
[05:12] <Hash> How to fix this? Any ideas?
[05:13] <Hash> When I double click archive, I want it to open in ark, not anothe folder in dolphin
[05:13] <Hash> What all changed, this is very annoying
 We Used to Be Friends … https://www.google.com/search?kgmid=/g/1q5jfbj9z&hl=es-ES&q=the+dandy+warhols+we+used+to+be+friends&kgs=d7a81969afd8aee9&shndl=0&source=sh/x/kp/osrp&entrypoint=sh/x/kp/osrp
 216A
[11:33] <tomreyn> ?
[11:52] <BluesKaj> Hi folks
[12:02] <kab0m> Hi everyone. My sister accientally deleted th package wireless-regdb and panically shutdown her laptop with ubuntu while processing. after that the laptop stays black after the grub prompt. i booted via liveusb and did a "apt dist-upgrade". Now i can only boot via rescue mode and acpi=off, no audio device is found, no network device is found and the touchpad does not work...how can i fix this machine? Thanks in advance
[12:08] <tomreyn> reinstalling the package may help
[12:09] <tomreyn> if it has ethernet, this may work without this package installed.
[12:11] <kab0m> @tomreyn i only have ethernet via liveusb, and i already reinstalled that package, but nothing chnaged...still no network devices, audio devices and touchpad.
[12:12] <kab0m> i have no idea what has gone wrong with this machine. is there a way to "fix" or reinstall ALL packages without reinstalling the whole system?
[12:14] <tomreyn> kab0m: reinstalling all packages could be done, but this doesn'T really serve any purpose. if you are having data loss due to a broken storage you should replace the storage and do a full new installation instead.
[12:15] <kab0m> tomreyn: im not so sure about a real data loss, as i can still boot in rescue mode with acpi=off flag.
[12:15] <tomreyn> kab0m: if just reinstalling this package didn'T fix the problem then something else is wrong, or you made additional changes after it broke which you have not yet reverted.
[12:15] <tomreyn> i would start yby taking a look at the logs.
[12:16] <tomreyn> if you want to share them: journalctl -b | nc termbin.com 9999
[12:18] <kab0m> tomreyn: i did a "apt dist-upgrade" and a "apt full-upgrade" in a booted live-usb when chrooted into the system.
[12:19] <tomreyn> that's fine with me.
[12:19] <kab0m> tomreyn: should i run the journal command at any time when the system is running in rescue mode?
[12:20] <tomreyn> journalctl -b    displays what was logged by your system (kernel and systemd, the init system / process manager) and the running processes since the latest boot.
[12:21] <tomreyn> it doesn't matter whether or not this was a rescue boot, unless /var/log/journal wasn't made writable, then there's be no logs.
[12:21] <tomreyn> actually there's still be logs, but just from memory,
[12:22] <tomreyn> not about previous boots, as systemd-journald normally provides.
[12:25] <kab0m> ok. how can i export the logs to a file so i can transfer it via usb from the machine that has no network device?
[12:26] <tomreyn> journalctl -b > /path/to/logfile 2>&1
[12:27] <kab0m> tomreyn: ok, thank you ;)
[12:28] <tomreyn> you're welcome
[12:36] <kab0m> Ok, here is the logfile: https://paste.ubuntu.com/p/3XWkNsRFSD/ i dont really what i should look out for.
[12:46] <kab0m> when i try to boot "normally" (non rescue mode) the boot process always stops at "hid-generic 0003:048D:C100.0002: input,hiddev0,hidraw0: USB HID v1.10 Keyboard [ITE Tech. Inc. ITE Device(8910)] on usb-0000:00:14.0-9/input0"
[12:58] <tomreyn> can you boot into rescue without acpi=off though?
[12:58] <tomreyn> it seems the nvidia driver doesn't like this option too much
[13:00] <tomreyn> you have a service called "pipewire-pulse.service" which tried to run software that ios not available ("Failed at step EXEC spawning /usr/bin/pipewire-pulse: No such file or directory")
[13:04] <tomreyn> in line 2014 you see network-manager starting but failing to do so since another copy of its DBus service is already active.
[13:05] <tomreyn> in line 961, NetworkManager starts the first time
[13:07] <tomreyn> it seems like no wireless device is detected by network manager, and probably the kernel as a whle.
[13:07] <tomreyn> you should run    lspci -knnv    and see whether there is one listed
[13:08] <tomreyn> kab0m: ^
[13:10] <kab0m> tomreyn: when i try to boot in to rescue mode without acpi=off the screen stays black and nothing happens after grub.
[13:13] <tomreyn> kab0m: hmm, maybe try without "acpi=off" but with "nomodeset" or "nvidia.modeset=0"
[13:16] <tomreyn> actally i thinkt he latter should be "nvidia.drm.modeset=0"
[13:16] <tomreyn> (instead of "nvidia.modeset=0")
[13:17] <tomreyn> so this looks like an nvidia issue to me, not one related to the wireless regdb
[13:18] <kab0m> tomreyn: did not work. none of them...hmmm
[13:18] <tomreyn> kab0m: did you do an "apt update" before the "apt dist-upgrade"?
[13:19] <tomreyn> and did you have initrds rewritten?
[13:19] <kab0m> tomreyn: i tried but kde was telling me: in kde neon please use pkcon instead of apt update
[13:20] <kab0m> tomreyn: i did a "update-grub and "update-initramfs -u -k all"
[13:20] <tomreyn> okay, and did you run pkcon?
[13:21] <kab0m> tomreyn: pkcon did not work in the chroot environment because o any service missing...it was a real pain haha
[13:22] <tomreyn> it's usually better not to update *all* initrds in such situations so you 'll still have older kernels with their older initrds available.
[13:22] <kab0m> ohhhh
[13:22] <tomreyn> thats just a suggestion for next time you'rein this situation
[13:23] <kab0m> tomreyn: thank you ;)
[13:24] <kab0m> should i try to uninstall the nvidia driver in live usb mode? maybe it boots with the default nuoveau driver
[13:24] <tomreyn> it would be good to see a log from when the screen remained black, if you can produce this and make it available.
[13:24] <tomreyn> maybe temporarily uninstalling the nvidia driver could help, yes. or disabling secure boot is thats enabled
[13:25] <kab0m> tomreyn: i dint know how i should produce a logfile from the state of a blackscreen.
[13:26] <tomreyn> you boot into the blkackscreen, wait a while for it to boot up fully, then ctrl-alt-f to switch toi a tty, then ctrl-alt-del to trigger a reboot. journalctl -b -1 should then have the previous log.
[13:26] <tomreyn> i'm afraid i need to leave it there for a bit, i need an hour of beauty sleep ;-)
[13:26] <tomreyn> good luck.
[13:35] <kab0m> tomreyn: thank you very much for your help so far. Sleep well ;_)
[13:35] <kab0m> ;-)
 hello everyone. single ssd with win10 and kubuntu and leap. opensuse's grub recognizes and install all 3 OSs. kubuntu 's grub only itself and win10. my mistake, or bug? regards
 @Max, I have seen issues with Kubuntu install failing to find all boot devices.  This video may help fix it: https://www.youtube.com/watch?v=r7meKJsjqfY
 👍 tnx
 Kdeconnect is amazing. I even have it on my macbook
 @DarinMiller, can't we use os-prober for that ?
 Yes, OS prober should work.  We need to fix the installer so no repair is required, However, I don't test multiple non-*buntu installations very often, so this issue misses our normal test procedures.
 (Photo, 513x745) https://irc-attachments.kde.org/XW5vRTgb/file_39793.jpg
 @Ren Will, What kind of stuffs?
[22:56] <joe_schmoe> sup faggots
[23:09] <joe_schmoe> hello
[23:10] <voxeltek> hey
[23:10] <joe_schmoe> how are you
[23:10] <voxeltek> good
[23:10] <joe_schmoe> that's good
[23:11] <joe_schmoe> do you have discord
[23:11] <voxeltek> yep
[23:11] <joe_schmoe> what is it
[23:11] <voxeltek> uhh
[23:11] <voxeltek> id prefer not to reveal it just yet
[23:11] <joe_schmoe> y
[23:11] <joe_schmoe> add meh
[23:11] <joe_schmoe> INfoUpgraders#0001
[23:14] <joe_schmoe> hi
[23:17] <joe_schmoe> hi
[23:20] <joe_schmoe> hello
[23:21] <joe_schmoe> hi
[23:22] <voxeltek_> hey
[23:22] <joe_schmoe> y
[23:22] <joe_schmoe> o