 ubuntu-bug-ubiquity
 Help
[01:03] <linuxnoob> hello
 How do I fix this bug
[01:22] <guiverc> @Reagan, try `ubuntu-bug ubiquity`  (ubuntu-bug is the program, ubiquity the package that is an option for ubuntu-bug)
 I am confused, I'm new too Linux and don't know anything
[02:19] <valorie> @Reagan using `ubuntu-bug ubiquity` is the easiest way to report a bug
 Yes but has there been a solution to it
[02:19] <valorie> it gathers automatically the information the many bug reports leave out, that the devels need to test
[02:20] <valorie> how do you know there has been a solution?
 I am asking if there is a solution
[02:20] <valorie> how would we know?
[02:20] <valorie> you have not said what the problem is
[02:21] <valorie> and a proper bug report is the way to report the problem
[02:21] <valorie> the people in this channel are not ubuiquty devels
[02:21] <valorie> this chan is for neon development
[02:22] <valorie> this has nothing to do with linux -- all software has bugs, and reporting them is the way to get them fixed
[02:23] <valorie> just open your terminal application or the actual term and type that: ubuntu-bug ubiquity
[02:23] <valorie> to paste that: control-shift V after you copy
[02:24] <valorie> then do what the instructions say
[02:24] <valorie> it will open in a browser and that's where you say what problem you are experiencing
[07:49] <lordievader> Good morning
[09:58] <maxgt1> Hello, i am new here so please feel free to point out any mistakes.
[10:01] <maxgt1> I have a problem whenever i do updates, i get the error "Package failed to install Error while installing package: installed rtl8812au-dkms package post-installation script subprocess returned error exit status 10
[10:25] <yossarianuk>  hi - i am trying to use either tmux or screen to start a session, then logout (via SSH) and re able to reconnect later
[10:25] <yossarianuk>  however, when i logout of ssh I lose the session
[10:25] <yossarianuk>  i.e - i can detach and re-attach to screen session fine - until I logout of ssh
[10:25] <yossarianuk> when i re-login to ssh i cannot reattach (and there is no screen/SCREEN pid)
[10:44] <lordievader> Are you disconnecting from your screen/tmux session or exiting?
[10:54] <yossarianuk> lordievader: I was detaching first then logging out of ssh
[10:54] <yossarianuk> and it kills tmux or/and screen sessions on ssh logout
[10:54] <lordievader> Does it list your session after detaching?
[10:55] <yossarianuk> no  - no session available
[10:55] <yossarianuk> its fine
[10:55] <yossarianuk> until i logout of ssh
[10:55] <yossarianuk> however - i have found a solution
[10:55] <yossarianuk> it's a systemd/logind issue (the machine I aqm connecting to is kde neon - from a kubuntu desktop..)
[10:55] <yossarianuk>  https://unix.stackexchange.com/questions/490267/prevent-logoff-from-killing-tmux-session
[10:56] <yossarianuk>  # systemd-run --scope --user tmux  = solution
[10:56] <yossarianuk> that works..
[10:58] <yossarianuk> so i'm happy now...
[11:05] <yossarianuk> lordievader: thank you for your help anyway
[11:06] <yossarianuk> one other thing - i am running kubuntu 20.04 - will there ever be a later version of KDE in backports PPA ?
[11:06] <yossarianuk> or not due to QT version ?
[13:01] <BluesKaj> 'morning folks
 @BluesKaj, Good Evening from India !
[13:50] <BluesKaj> @ri5h46h, good morning from Canada :-)
 @BluesKaj, 😀
[14:42] <AnDrEs4> Over 40.000$ BitCoin https://cryptotabbrowser.com/16879401 Earn Your BitCoin Now!!!
 7439
 6691
[17:24] <user|93327> Yesterday my 20.04 system updates showed the 5.8 kernel (5.8.0-34).
[17:24] <user|93327> After updating, my system would not boot.  It stopped at a prompt initramfs.
[17:24] <user|93327> So I booted back with my older 5.4.0-59, which still worked OK.
[17:24] <user|93327> Today Updates showed a mixture of files, 5.8 and 5.4, which seems confusing.
[17:24] <user|93327> I tried selecting just 5.8 again.  This time 5.8.0-36.
[17:24] <user|93327> There were lots of nvidia updates (some marked as 5.8 nvidia) that I did Not Select.
[17:24] <user|93327> Again it would not boot, after updating.  It stopped at the prompt initramfs again.
[17:40] <Maik> user|93327: enter grub and try to boot from the older 5.4 kernel. Al lot users seem to have issues with 5.8 on 20.04.1. AFAIK that kernel shouldn't even come with regular updates as of yet.
[17:41] <Maik> i have a Ubuntu MATE 20.04.1 which runs with 5.4.0-60 as of today, i didn't get 5.8 at all. I guess you guys enabled HWE too early?
[17:42] <user|93327> I've booted to an older 5.4 kernel.  I am seeking advice on how best to repair my system.
[17:43] <user|93327> Should I try updating to 5.4.0-60, to see if that helps?
[17:50] <Maik> user|93327: you could try it...
[17:51] <Maik> and remove the 5.8 kernel too while your at it if it works with the 5.4 kernel
[19:16] <user|5519> OLa
[19:16] <user|5519> instalar adaptador wi fi
[19:17] <Quantos> Running KUbuntu 20.4.1 LTS x64, in term I can no longer make a ~ it comes out as ¬ and it won't work
[19:48] <Quantos> Running KUbuntu 20.4.1 LTS x64, in term I can no longer make a ~ it comes out as ¬ and it won't work
[19:49] <Quantos> It worked the day before yesterday, but now it's all messed up