[04:48] <billybigrigger> can someone tell me which nvidia driver i should be using for a laptop?
[05:17] <alkisg> billybigrigger: run `software-properties-gtk` and go to the drivers tab, and see
[05:36] <billybigrigger> is that the gui window for proprietary drivers?
[05:36] <billybigrigger> where you pick software sources and update/upgrade options? alkisg
[05:36] <alkisg> billybigrigger: yes
[05:37] <billybigrigger> if so, there's 2 nvidia options
[05:37] <alkisg> And which one says "recommended"?
[05:37] <billybigrigger> i installed 18.04 on a buddies laptop, and he just called and said he can't switch to hdmi audio output, i assume its because i never installed nvidia drivers...but i do remember seeing 2 options
[05:38] <billybigrigger> they were both the same release version...i can't remember the difference...but i remember being confused about the descriptions, and left it with the default drivers
[05:39] <alkisg> That's why it says "recommended" there, to know which one to use
[05:39] <billybigrigger> i dont think there was a recommended, that's why i was confused
[05:39] <billybigrigger> i was looking for recommended
[05:41] <billybigrigger> https://askubuntu.com/questions/1031463/whats-the-difference-between-nvidia-driver-metapackage-and-nvidia-binary-driver/1039385
[05:41] <billybigrigger> that looks familiar
[05:41] <alkisg> OK, you'd need to check again, and if indeed there isn't, to send the output of lspci -nn -k and the output of ubuntu-drivers list
[05:41] <billybigrigger> closedsource tested and closed source
[05:41] <billybigrigger> except they were both driver version 390
[05:43] <billybigrigger> that post is why i was confused, whats the difference between meta pkg and binary? is the binary just a straight download from nvidia.com? because i thought that method was deprecated long ago
[05:44] <billybigrigger> sorry, i don't run ubuntu as a daily driver on my machines, it's either arch or freebsd for me...
[05:45] <billybigrigger> the only answer on that post doesn't make sense to me, because if both options are pulling from the same source, why is there a need for 2 options? and yes i'm positive both driver versions were 390.xxxx
[05:46] <billybigrigger> i remember back when i ran ubuntu that gui driver selection page always gave me hell, hence why i stuck with noveau and then did a face palm when he called asking why he had no hdmi audio options
[05:47] <billybigrigger> if they are both the same binary driver, pulled from the same source, but one is labeled tested...then why in the hell list the 2 "untested" option?
[05:47] <billybigrigger> basically what is the difference in the two
[05:49] <alkisg> nvidia-340/bionic 340.106-0ubuntu3 amd64  NVIDIA binary driver - version 340.106
[05:49] <alkisg> xserver-xorg-video-nvidia-390/bionic 390.48-0ubuntu3 amd64  NVIDIA binary Xorg driver
[05:49] <alkisg> These is what I see in apt, I don't have nvidia to see with software-properties-gtk
[05:50] <alkisg> They're not the same version
[05:51] <billybigrigger> well i swear they were both the same version or i wouldnt have been confused...i would have picked 390.xx over 340.xx and not thought twice about it
[05:52] <alkisg> Personally I'd need input from you being there and showing output/screenshots/specific names then
[05:52] <alkisg> Can't help without specific input
[05:52] <alkisg> You could also wait and see if anyone has nvidia to test
[06:44] <gnugr> billybigrigger: there's a package in debian which helps to find what nvidia driver is needed 'nvidia-legacy-check', also as for 390xx, a new pkg exists in debian/sid https://ftp-master.debian.org/new/nvidia-graphics-drivers-legacy-390xx_390.48-4.html
[06:45] <gnugr> https://packages.debian.org/sid/nvidia-legacy-check
[06:49] <billybigrigger> ty
[07:31] <arwenvd> hello
[07:32] <diogenes_> hello
[07:32] <arwenvd> Hi
[07:33] <arwenvd> I am here to seek assistance
[07:33] <diogenes_> !ask | arwenvd
[07:35] <arwenvd> I cannot find the Screen Share option anywhere in ubuntu mate 18.04, also cannot launch vino-preferences, like previous versions. Once installing Gnome, in it I found the settings for Screen Share, but in Mate it is not available.\
[07:53] <alkisg> arwenvd: did you install vino?
[07:53] <alkisg> Different desktop environment use different programs; afaik mate doesn't have vino preinstalled, but of course you can install it
[08:04] <arwenvd> i have installed vino, then after not working i have purged it, and installed it again
[08:04] <arwenvd> no vino and no vino-preferences in terminal
[08:13] <alkisg> arwenvd: https://packages.ubuntu.com/search?searchon=contents&keywords=vino-preferences&mode=exactfilename&suite=bionic&arch=any
[08:13] <alkisg> vino-preferences doesn't exist in any package in 18.04
[08:13] <alkisg> It does exist in 16.04: https://packages.ubuntu.com/search?suite=xenial&arch=any&mode=exactfilename&searchon=contents&keywords=vino-preferences
[08:14] <arwenvd> Yes i know. I wonder how can i use vino with 18.04?
[08:14] <alkisg> The vino package has these: https://packages.ubuntu.com/bionic/amd64/vino/filelist
[08:14] <arwenvd> I can configure it in Gnome, but in mate there is no configuration
[08:14] <alkisg> arwenvd: which command configures it in gnome?
[08:15] <alkisg> Open the configuration, and run ps aux in the terminal, to find out the command
[08:15] <arwenvd> It is in System Settings panel
[08:15] <alkisg> The vino package contents are: https://packages.ubuntu.com/bionic/amd64/vino/filelist
[08:15] <alkisg> That doesn't help. What about the command?
[08:16] <alkisg> Also, there are other servers that you can use, like x11vnc, tigervncserver etc
[08:19] <alkisg> arwenvd: here it says you can also edit its settings through dconf-editor: https://forums.bunsenlabs.org/viewtopic.php?id=1411
[08:19] <alkisg> It sounds like gnome doesn't want vino to be easily reusable in other desktop environments :)
[08:19] <arwenvd> i am going to try and find out the command in 5 minutes. I would like to use vino, because i already have 600 pcs running different ubuntu installations and all are with vino. It would be inconvenient for us to use two different remote connect servers on that ammount of computers.
[08:20] <alkisg> Eeeh, have you seen epoptes.org?
[08:20] <alkisg> For that amount of workstations, it would be waaaay easier to manage them with epoptes
[08:34] <arwenvd> I have made my network very understandable with bind configuration, so if i want to connect to someone, i just type vncviewer 101 and i go there. I just need to make it work with 18.04
[09:03] <arwenvd> Okay, so, the settings for the screen share on gnome are in gnome-control-center --overview
[09:08] <alkisg> arwenvd: the options I see for you are (1) apt install --no-install-recommends gnome-control-center => nah, don't do that on MATE, (2) use dconf-editor to change vino settings as mentioned in the URL I pasted above, or (3) use another server like epoptes
[09:09] <alkisg> epoptes is much easier than "vncviewer 101". It's: I see all client thumbnails, and I click "monitor" or "assist" user to get access
[09:09] <alkisg> And of course logoff, shutdown, right click properties, right click open terminal and a lot others
[09:09] <alkisg> And it needs less than 1 MB RAM on the clients, it's extremely light
[09:10] <gnugr> alkisg: might 'dconf-tools' could help for remote access, but no idea if it's candidate (exists in d/sid)
[09:11] <alkisg> gnugr: dconf-tools is the package that provides dconf-editor, what I proposed, yes
[09:14] <gnugr> dconf-tools don't ship with dconf-editor
[09:14] <gnugr> but sure it allows remote access for everything
[09:16] <alkisg> gnugr: check this: https://packages.ubuntu.com/bionic/dconf-tools
[09:16] <alkisg> Or just run `apt show dconf-tools`
[09:16] <alkisg> You'll see that dconf-tools is a transitional package that installs dconf-editor
[09:16] <alkisg> Don't confuse the users please
[09:18] <gnugr> aaahh OK difers in ubuntu
[09:18] <alkisg> This is the #ubuntu-mate channel :)
[09:18] <gnugr> differs* even
[09:19] <alkisg> It's the same in debian though, https://packages.debian.org/stretch/dconf-tools
[09:19] <alkisg> Again a transitional package that install dconf-editor
[09:32] <gnugr> alkisg: ah yes, dconf-tools not exists in d/testing, that was my mistake
[11:51] <mate|40118> hi all
[11:53] <diogenes_> hi
[12:39] <Hello> hi?
[12:45] <diogenes_> hi
[15:19] <mate|75205> Hey I am Russell in Salem Oregon trying the chat feature out
[15:24] <mate|1499> Russell here trying this chat feature out
[19:20] <mate|93990> 18.04 LTS, button on the panel to log out/restart/shut down has stopped working; how to log out or restart?
[19:21] <sixwheeledbeast^> shutdown now in a terminal would work. but i would investigate why your panel has an issue too.
[19:22] <vkareh> mate|93990: Ctrl+Alt+BackSpace to get the logout menu, Ctrl+Alt+Delete to get the shutdown/restart menu
[19:27] <mate|93990> vkareh
[19:27] <mate|93990> vkareh
[19:27] <mate|93990> vkareh: Ctrl+Alt+BackSpace doesn't do anything; Ctrl+Alt+Delete OK
[19:27] <vkareh> mate|93990: ah, okay maybe I have a custom shortcut on my side :P
[19:29] <mate|93990> vkareh: thanks
[19:29] <vkareh> you're welcome!