[01:00] <Aydin> Hello can someone help me with something
[01:00] <wxl> !ask
[01:00] <ubottu> Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience
[01:03] <Aydin> Ah okay sorry, Can someone help me install nvidia 390 legacy driver, my notebook currently runs nvidia 820m, which i'd assume the recent one supported is the legacy 390 one, also using the additional drivers tool installs either the 450 or the 340 which both reboot into a blackscreen
=== george is now known as Guest60269
=== andrej is now known as Guest68120
[08:44] <lubot> kynnad was added by: kynnad
[10:01] <lubot> <Fairnandes> How can I split screen?
[10:02] <lubot> <Fairnandes> All I tried to create the shortcut Super+Left/Right doesn't work
[11:42] <guiverc> @Fairnandes, https://manual.lubuntu.me/stable/F/keyboard_shortcuts.html provides a list of the Keyboard shortcuts in Lubuntu 20.04 LTS/20.10 ; you didn't provide release details.
[12:06] <lubot> <Fairnandes> Right, but none of these have the effect of splitting screen horizontally.
[12:06] <lubot> <Fairnandes> For former versions, the following workaround doesn't fit
[12:06] <lubot> <kc2bez> @Fairnandes [Right, but none of these have the effect of splitting screen horizontally.], Which version of Lubuntu do you have?
[12:06] <lubot> <Fairnandes> http://v1chak.blogspot.com/2013/03/lubuntu-openbox-keybind-to-split-screen.html
[12:08] <lubot> <Fairnandes> 20.04.1
[12:13] <lubot> <kc2bez> The faux tiling was removed since it conflicts with the super key bindings. You can add that back into the openbox configuration but you should change the keybind.
[12:15] <lubot> <Fairnandes> How do I do that?
[12:30] <lubot> <kc2bez> You have to add them back into the `lxqt-rc.xml` file. https://paste.ubuntu.com/p/jn2NgFXTc5/
[12:31] <lubot> <kc2bez> You will want to change the `W` for something else though.
[12:38] <lubot> <Fairnandes> Tried it, but is not working though
[12:48] <lubot> <kc2bez> You will have to log out and back in if you haven't done that.
[15:17] <lubot> <Michaël Van Bogaert> guys … how do I start troubleshooting this?
[15:17] <lubot> <Michaël Van Bogaert> systemctl --failed …   UNIT                 LOAD   ACTIVE SUB    DESCRIPTION                                 … ● cups-browsed.service loaded failed failed Make remote CUPS printers available locally … LOAD   = Reflects whether the unit definition was properly loaded. … ACTIVE = The high-level unit activation state, i.e. ge
[15:17] <lubot> neralization of SUB. … SUB    = The low-level unit activation state, values depend on unit type. … 1 loaded units listed.
[15:17] <lubot> <Michaël Van Bogaert> i'll upload a picture too
[15:17] <lubot> <Michaël Van Bogaert> (Photo, 805x194) https://i.imgur.com/00VyNyZ.jpg
[15:18] <lubot> <Michaël Van Bogaert> I can't print
[15:20] <kc2bez> what happens if you try to start it manually?
[15:24] <lubot> <Michaël Van Bogaert> @kc2bez [<kc2bez> what happens if you try to start it manually?], how do I do this?
[15:25] <kc2bez> `systemctl start cups-browsed.service`
[15:26] <lubot> <teward001> *throws a sudo into the mix*
[15:26] <kc2bez> It should prompt you
[15:26] <lubot> <teward001> i'm picky ;)
[15:26] <kc2bez> Either way
[15:26] <lubot> <Michaël Van Bogaert> ok, trying to print something now
[15:28] <lubot> <Michaël Van Bogaert> (Photo, 1280x455) https://i.imgur.com/XonNmjn.jpg
[15:28] <lubot> <Michaël Van Bogaert> @kc2bez [<kc2bez> `systemctl start cups-browsed.service`], nee feedback from terminal
[15:29] <lubot> <Michaël Van Bogaert> @Michaël Van Bogaert [<reply to image>], I still get this result
[15:31] <lubot> <Michaël Van Bogaert> (Photo, 409x396) https://i.imgur.com/JWC0yEF.jpg
[15:40] <kc2bez> `systemctl status cups-browsed.service` Will let you know if the start was successful.
[15:43] <kc2bez> `journalctl -u cups-browsed.service` will show you log messages for that systemd unit.
[15:49] <lubot> <Michaël Van Bogaert> (Photo, 1034x187) https://i.imgur.com/wi5tZdJ.jpg
[15:49] <lubot> <Michaël Van Bogaert> @kc2bez [<kc2bez> `journalctl -u cups-browsed.service` will show you log messages for tha …], the log  … that's what we need :)
[15:51] <lubot> <Michaël Van Bogaert> @kc2bez [<kc2bez> `journalctl -u cups-browsed.service` will show you log messages for tha …], https://paste.ubuntu.com/p/wcTVRZbb5G/
[15:56] <lubot> <Michaël Van Bogaert> "this is not a systemd bug but an iotedge bug" … according to this post
[15:56] <lubot> <Michaël Van Bogaert> https://github.com/systemd/systemd/issues/13574
[15:57] <kc2bez> That is a different service. There are some cups logs in `/var/log/cups/` that might help as well.
[16:01] <lubot> <Michaël Van Bogaert> (Photo, 510x781) https://i.imgur.com/VKpaBGx.jpg I think you mean these  … but mind you those are BIG
[16:02] <lubot> <Michaël Van Bogaert> 9 and 15mb :s … and all it contains is text😨
[16:02] <lubot> <teward001> i should point out that what you're seeing is a cups-browsed coredump.  that SUGGESTS a segfault somewhere
[16:02] <lubot> <teward001> which is a Bad Thing
[16:02] <lubot> <teward001> just my 2 cents
[16:03] <lubot> <Michaël Van Bogaert> segfault … I saw this somewhere appearing in the terminal  … Would it be solved if I reinstall this laptop?
[16:04] <lubot> <Michaël Van Bogaert> @teward001 [just my 2 cents], I had to Google this idiom 😂
[16:04] <lubot> <teward001> `segmentation fault (Core dumped)` is usually the indication you've got something going haywire with a program.
[16:05] <lubot> <teward001> but the cause of segfaults could be irrelevant from a reinstall
[16:05] <lubot> <teward001> is this a fresh install you did, or did you upgrade from an older release?
[16:05] <lubot> <teward001> just asking because sometimes that is a relevant bit
[16:05] <lubot> <teward001> kc2bez: unrelated: I hate segfaults >.<
[16:05] <kc2bez> Yeah, that is bad stuff.
[16:05] <lubot> <Michaël Van Bogaert> @teward001 [just asking because sometimes that is a relevant bit], today I did a release upgrade to Lubuntu 20.10 … before that printing worked just fine
[16:06] <lubot> <teward001> from 20.04?
[16:06] <lubot> <Michaël Van Bogaert> @teward001 [from 20.04?], I do believe so
[16:06] <lubot> <teward001> kc2bez: something to add to the QA tests in development side of things.  ^^
[16:06] <lubot> <teward001> Michaël you could ATTEMPT a fresh install of 20.10 after backing up the data you want to keep
[16:06] <lubot> <teward001> and MAYBE it'd work (there could be leftovers from 20.04 that broke things)
[16:07] <lubot> <teward001> but if you do that and get the segfaults still then you should probably open a bug, so the devs can dig deeper
[16:07] <lubot> <teward001> any CUPS components segfaulting is a Bad Thing
[16:07] <kc2bez> I upgraded my box here to 20.10 and I don't have a CUPS issue.
[16:07] <lubot> <Michaël Van Bogaert> I remember the upgrader asking me what config I wanted  … and I answerd 'keepr the old one'  … something in those words
[16:07] <lubot> <teward001> kc2bez: could be unique to their system.  Keeping the old config could cause the breakages too
[16:07] <lubot> <teward001> esp. if CUPS has things it *needs* during the upgrade.
[16:07] <kc2bez> Right
[16:08] <lubot> <Michaël Van Bogaert> @teward001 [kc2bez: could be unique to their system.  Keeping the old config could cause the …], can I remove it?
[16:09] <lubot> <Michaël Van Bogaert> I already did a cups things purge  … and reinstalled it  … but that solved nothing 🤷🏽‍♂️
[16:10] <lubot> <Michaël Van Bogaert> I'm back in about half an hour
[16:44] <lubot> <Leokolb> @kc2bez [<kc2bez> I upgraded my box here to 20.10 and I don't have a CUPS issue.], I have done many upgrades to 20,10 and tested printing - never had a CUPS issue (mostly HP printers)
[17:09] <lubot> <Michaël Van Bogaert> @teward001 [kc2bez: could be unique to their system.  Keeping the old config could cause the …], is there any way that I can remove the old config file?
[17:14] <lubot> <teward001> you can probably find and remove the config file and then reinstall / regenerate but I don't have the steps for it right now (little busy with work)
[17:21] <lubot> <FedeBosio> @teward001 [kc2bez: unrelated: I hate segfaults >.<], you're not the only one (stupid pointers... 😆)
[17:22] <lubot> <teward001> lol
[17:29] <lubot> <Michaël Van Bogaert> thank you all guys for the help I already recieved
=== lubuntu is now known as Guest84760
=== lubuntu is now known as Guest42601
[19:19] <lubuntu_> ll
[23:14] <Doggie> luwubuntu