[02:54] hello all [02:54] why does kamoso segfault on me very quickly after i start it? === himcesjf_ is now known as him-cesjf [06:27] Marty_the_wolf was added by: Marty_the_wolf [06:34] Is it still the case that the Kubuntu backports deliver every Plasma version to interim releases of Kubuntu but only deliver the LTS versions of Plasma to the LTS versions of Kubuntu? [06:35] 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 [06:35] the boot about 2 minutes long. … So? You think it could be fixed somehow? I don't want to install back Nouveau display drivers though(with them it was working, but I couldn't download anything from Discover) [06:50] @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 [06:50] development release and less invasive backports. [06:51] Roey: reporting a bug would be good [06:54] @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 [06:57] @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. [07:01] @acheronuk, Hi Rik! Thanks for the quick answer! My question was actually in fear of the opposite! I of course would like improvements that make sense (discover!), but I would not trade that for stability. So if you had told me that the Kubuntu backports nowadays push every plasma release (like 5.13 etc.) to Kubuntu LTS, I would not consider activating the backports. [07:03] @acheronuk, What I actually would live would be a way to only get the last point releases of every Plasma version so the little quirks have been ironed out before it reaches my computers. [07:03] @acheronuk, Live=like [07:08] 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] 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? [08:52] From my perspective (pure user and non professional in the IT field), something like that would be a very worthy use of resources with the adoption of Plasma in mind! After two years in Linux I have the impression that KDE and Plasma are the most functional and versatile DE/technique. Just in the end user friendlyness (stability and documentation) there remains a lot to be done. [08:52] @acheronuk, Phil Linux: … From my perspective (pure user and non professional in the IT field), something like that would be a very worthy use of resources with the adoption of Plasma in mind! After two years in Linux I have the impression that KDE and Plasma are the most functional and versatile DE/technique. Just in the end user friendlyness (stability and documentation) there remains a lot to be done. [08:53] @acheronuk, Makes sense to focus such efforts on distros like Kubuntu LTS. Maybe then Barcelona might have chosen Kubuntu instead of Ubuntu. ;-) [08:55] @Phil Linux, For Bionic LTS, that would still require a big Qt and Frameworks backport. New plasma usually = new minimum dependencies [08:56] @acheronuk, Mind, I really like Plasma, it is my Desktop environment of choice. KDE seems a project so very good in terms of combining innovation and sustainability that I really want to see it thrive! [08:56] @acheronuk, I understand that now. [08:57] @acheronuk, But isn't it almost the same as the upcoming release of Neon will be? 18.04 base + Plasma 5.14 on top? [08:59] @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. [09:00] That's a pity. [09:00] Kubuntu as a flavour of Ubuntu needs to keep a bigger scope of concern in not breaking things with backports [09:01] Current LTS Plasma and stability would be an unbeatable product. What Ubuntu on Plasma instead of gnome could have been... [09:03] 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 [09:03] sadly not to be.... [09:05] My biggest regret in the linux world... [11:59] Howdy folks [14:34] 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] haven't heard of that issue before daum ..sudo adduser username group? [14:37] 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] BluesKaj, that command for example notes i'm already in the group [14:38] he user `daum' is already a member of `docker'. [14:40] BluesKaj, example of what i'm seeing: https://pastebin.com/xAtzBGtz [14:58] 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] hm what do you mean? [15:00] 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] ohh [15:12] but what am i changing the permissions on? [15:15] think I added to user to / === himcesjf_ is now known as him-cesjf [15:56] daum: What is the output of `groups` and what should it be? [15:56] lordievader, https://pastebin.com/xAtzBGtz [15:57] oh doh [15:57] that got delted one sec [15:57] https://pastebin.com/Wzb1jHgY [15:58] daum: What is the output of `cat /etc/group|grep daum`? [15:59] groups from after the sudo [16:00] Do you see all the groups when you login to a tty? [16:03] lordievader, yah [16:04] lordievader, however if i open a konsole/xterm for example inside of kde it does have the proper groups. [16:07] xterm too? [16:07] What happens when you open another konsole from your sudo'ed shell? [16:07] Do you get all groups that way? [16:24] lordievader, yep xterm too (launched from kde)... if i open a konsole from my sudo'd shell it have the proper groups === himcesjf_ is now known as him-cesjf [16:52] Then it is likely kded/plasmashell (whatever the init process of KDE is) which is learning the groups wrongly. [16:55] lordievader, any idea where i would try to figure out how to troubleshoot that [17:06] Err, not really. Sorry. Maybe acheronuk can help you further. If he is around. === Blubberbop is now known as phoenixz