[02:54] <Roey> hello all
[02:54] <Roey> why does kamoso segfault on me very quickly after i start it?
 I have a small problem. It started after installing recommended drivers(Nvidia binary driver - version 340.106) for my Nvidia 210. … When I boot up the system it takes a lot of time. First kubuntu logo shows in 800x600resolution(that's some basic resolution I think) and then the screen gets black. After that shows nvidia logo but in the native screen resolution. … The system works when it's booted up, just this thing is mak
 @Phil Linux, We backport what is practical and safe to do, given times and resourses. For LTS releases the fallback postion is relying on the released LTS stack (Qt version etc) though we may make an exception. I assume the context of this is wanting new Plasma on Bionic? That requires newer Qt than Bionic has, so is non trivial and quite some work to backport. We are looking at doing that, but focus is inevitabley on the
 Roey: reporting a bug would be good
 @Marty_the_wolf, depends why it is happening. if there is something new staring up that is slow, it might be resloved. if it is something hardware releated throwing errors to logs, then could be more complicated.  'systemd-analyze blame' & 'systemd-analyze critical-chain' may point to something
 @acheronuk, It started happening on each boot up since I installed Nvidia x server drivers. It looks like Nvidia driver is setting up for the monitor each time when booting and it doesn't save the current setting.
 Maybe something to think about when it is actually do-able. At the moment, that would not apply until we reach plasma 5.14.5 and could do taht for Cosmic
[07:27] <Jussi> so I have a mobile phone headset/headphones I want to use with skype. However, the mic crackles crazy, so I want to use the built in mic on my laptop. anyone  know where the setting is to achieve this?
 @Phil Linux, For Bionic LTS, that would still require a big Qt and Frameworks backport. New plasma usually = new minimum dependencies
 @Phil Linux, No, as they have newer Qt and frameworks than the bionic base, and don't particularly care if that results in non KDE things in the ubuntu archive being broken as a result, as long as their KDE things work.
 Kubuntu as a flavour of Ubuntu needs to keep a bigger scope of concern in not breaking things with backports
 Yes, if Canonical had put the effort /resourses into Plasma desktop, it would have been great. Plasma is already very good, but with the weight of main Ubuntu behind polishing and bugfixing etc, it could have been truly amazing
 sadly not to be....
[11:59] <BluesKaj> Howdy folks
[14:34] <daum> anyone here have any ideas after my 16->18 upgrade, when i for example open up konsole my user doesn't have the proper groups, if i sudo -umyuser -s it picks up the proper groups.  i haven't had any luck figuring out what may be causing it
[14:37] <BluesKaj> haven't heard of that issue before daum ..sudo adduser username group?
[14:37] <daum> BluesKaj,  https://www.reddit.com/r/kde/comments/91jc80/help_when_opening_konsole_my_user_will_not_have/  seems to be really similar
[14:38] <daum> BluesKaj, that command for example notes i'm already in the group
[14:38] <daum> he user `daum' is already a member of `docker'.
[14:40] <daum> BluesKaj, example of what i'm seeing: https://pastebin.com/xAtzBGtz
[14:58] <BluesKaj> daum, afraid I don't know how to help you on this one, unless you just change permissions from root to user, and then i'mnot sure that would help
[14:58] <daum> hm what do you mean?
[15:00] <BluesKaj> I had to change my external drive from root to user the other day, dunno why it became root in the first place
[15:12] <daum> ohh
[15:12] <daum> but what am i changing the permissions on?
[15:15] <BluesKaj> think I added to user to /
[15:56] <lordievader> daum: What is the output of `groups` and what should it be?
[15:56] <daum> lordievader, https://pastebin.com/xAtzBGtz
[15:57] <daum> oh doh
[15:57] <daum> that got delted one sec
[15:57] <daum> https://pastebin.com/Wzb1jHgY
[15:58] <lordievader> daum: What is the output of `cat /etc/group|grep daum`?
[15:59] <daum> groups from after the sudo
[16:00] <lordievader> Do you see all the groups when you login to a tty?
[16:03] <daum> lordievader, yah
[16:04] <daum> lordievader, however if i open a konsole/xterm for example inside of kde it does have the proper groups.
[16:07] <lordievader> xterm too?
[16:07] <lordievader> What happens when you open another konsole from your sudo'ed shell?
[16:07] <lordievader> Do you get all groups that way?
[16:24] <daum> lordievader, yep xterm too (launched from kde)... if i open a konsole from my sudo'd shell it have the proper groups
[16:52] <lordievader> Then it is likely kded/plasmashell (whatever the init process of KDE is) which is learning the groups wrongly.
[16:55] <daum> lordievader, any idea where i would try to figure out how to troubleshoot that
[17:06] <lordievader> Err, not really. Sorry. Maybe acheronuk can help you further. If he is around.