[00:04] <AssociateX> One of the worst things about a new install is dialing in everything. Sheesh!
[00:04] <Thr0r> Do you have any info of this topic unit193?
[00:06] <Unit193> I'm not precisely sure why you pinged me on this.
[00:07] <Thr0r> You are Staff member here? not? I asked a question no one else replied to so I tried you - hoping you would know the issue?
[00:07] <Unit193> Oh, for the freenode IRC network, not Kubuntu.  Sorry.
[00:08] <Thr0r> well - Freenode / Kubuntu
[00:09] <Thr0r> just let me know if you are not able to help.. I'll move on
[00:11] <Unit193> I mean I can't, but that doesn't mean someone won't be active in time that can.
[00:12] <Thr0r> ok, thanks
 @Thr0r, Screen management with respect to widget placement has in improved on 20.04 where changing resolutions do not scatter the widgets near often as it used to  (using X).
[00:26] <Thr0r> Ok - To who and what server and channel would it be best to adress this dual screen management issue that does never seem to be resolved in Kubuntu? #KDE? is there a place outside freenode? ..you know unit193?
[00:27] <Unit193> In here or #kde would seem logical to me, sure.
[00:27] <Thr0r> ok thanks
[10:47] <alterjsive> how can i stop the display manager so I can install the patched nvidia drivers (kernel 5.6)? https://aur.archlinux.org/pkgbase/linux-nitrous/#comment-737274
[10:54] <alterjsive> sudo service sddm stop
[11:30] <BluesKaj> Howdy folks
 Hello BluesKaj
[11:34] <BluesKaj> Hi Franzpow
 @ahillio, Have you tried flameshot?
[15:44] <lsd> guys where/how to Enable mouse while typing to 1
[15:44] <lsd> i dont want to do it everytime throught xinput every restart
[15:44] <lsd> from KDE menu is there option
[15:44] <lsd> ?
 whever I boot into OS now the screen is zoomed in and I have to hit shift-alt-f12 to get back to normal screen. any time I change settings in compositer it also does the same zooming effect. I have also lost the ability to have opacity settting on terminal window set. I get error - "the background transparency setting will not be used because your destkop does not appear to support transparent windows"
 anybody have any ideas what would be causing this..
 @Barika, Which version of Kubuntu and do you have backports installed?
[17:19] <zimmedon> @Barika the zooming is likely a compositor effect, so I would check under Desktop Effects. Also that hotkey (Shift+Alt+F12) is used to toggle the compositor on/off. By turning off the compositor, I think you just lose the ability to have transparency without the old school fallback in the days before compiz and all that.
[17:20] <zimmedon> actually yeah, Zoom appears to be enabled by default with [Meta =] and [Meta -] as the hotkeys to control zoom.
[17:22] <zimmedon> so you could either disable zoom or try hitting [Meta -] a few times until it's back to normal. Meta key also being known as the super key (or Windows key).
 Older versions of plasma will crash and while the desktop still works the compositor will not run until plasma is restarted.  On older plasma, run killall plasmashell for a terminal.  Then run "plasmashell &"  to restart.
 New plasma versions  crash less often, but can be restarted with "plasmashell —replace &"
 Ok I turned off zoom. Wondering now how to get blur effect working.
 I will reboot see if this helps.
 removing zoom worked and fixed blur even
 When plasma partial crashes, sometime compositing is set to xrender (System settings -> Display and Monitor -> Compositor -> Rendering backend.  Manually restarting plasma and setting Rendering backend to OpenGL  (sometime restarting plasma again) will fix the issue.
[17:56] <sigNeon> any idea why k Driver Manager only shows drivers for my iwlwifi and nothing for my gpu?
[18:06] <karol> hello
[18:07] <karol> it is now
[18:13] <BluesKaj> sigNeon, which gpu do have ...intel is most likely loaded so it won't show iirc
[18:14] <sigNeon> BluesKaj: yeah it is the i915 driver
[18:15] <BluesKaj> dunno why it doesn't
[18:19] <BluesKaj> sigNeon,try, lspci -nnk | grep -i vga -A3 | grep 'in use' ..include the quotes
[18:19] <sigNeon> I used: sudo -E hw-probe -all -upload
[18:20] <sigNeon> linuxhw probe tool
[18:20] <sigNeon> works nicely :)
[18:20] <sigNeon> https://linux-hardware.org/
[18:22] <BluesKaj> dont have that utlity so command not found here
[18:22] <sigNeon> very handy actually
[18:22] <sigNeon> just found it
[18:22] <sigNeon> "hw-probe
[18:22] <sigNeon> "hw-probe"
[18:23] <vadi01> https://pasteboard.co/J3v5o5q.png
[18:24] <vadi01> states loading and nothing
[18:24] <vadi01> anyreason why?
[18:24] <sigNeon> vadi01: ?
[18:24] <vadi01> running kde-neon btw
[18:24] <sigNeon> bad connection maybe?
[18:24] <vadi01> just installed kde-neon and am getting issues loading wallpapers
[18:24] <sigNeon> close it and try again
[18:27] <BluesKaj> vadi01, have you asked in #kde-neon
[18:28] <BluesKaj> kubuntu and kde-neon aren't the same
[18:28] <sigNeon> ubuntu core LTS with a rolling KDE Desktop
[18:29] <sigNeon> I use it
[18:29] <vadi01> BluesKaj: yep posted it. silent people there
[18:29] <sigNeon> similar enough that most general stuff is the same other than if you don't use pkcon you have to use "dist-upgrade" in place of "upgrade"
[18:33] <vadi01> sigNeon: thnaks worked
[18:33] <sigNeon> :)
[19:53] <karol> its now
[19:54] <karol> helo vadi01
[19:55] <vadi01> ah much better. Had to remove neon and get to kubuntu. (not that neon was bad. just my preference)
[19:55] <vadi01> karol: hello
[19:55] <karol> hello
[19:56] <vadi01> at least irc channel here is awake :)
[19:58] <vadi01> guys am on plasmashell 5.16.5
[19:59] <vadi01> how to upgrade to latest plasma 5.18?
[20:13] <nc_> ls
[21:55] <xqs> hi guys,i am using kubuntu 20.04 and find that the kontact app ver. is still 19.04.3,,why not update it to 19.12.3? thanks.
[22:16] <mparillo> vadi01: https://kubuntu.org/news/plasma-5-18-1-for-kubuntu-19-10-available-in-backports-ppa/
[22:16] <mparillo> For even newer, https://kubuntu.org/news/testing-for-the-beta-help-needed/
 Is there a difference between shutting down my pc via "Shutdown now" or via kubuntu desktop?
[23:22] <mparillo> For a test, you can try to create a document (say in kate) and try both approaches. I know using the GUI shutdown it will tell you kate has an unsaved document in its buffer. I am not so sure about the terminal command. P.S. I usually do a systemctl poweroff instead, but generally only when the GUI is unresponsive.
 That's interesting.
 mparillo: does using the terminal way causes data loss?
[23:56] <Dragnslcr> You might lose unsaved data, but using the shutdown command will definitely write saved data to disk if necessary
[23:57] <Dragnslcr> So it isn't like just pulling out the power cable