[09:33] <jansb000> Problem with changing screen resolution since applying updates from last week.
[09:34] <jansb000> Screen reolution seems now fixed to 1078x756
[09:34] <jansb000> before (upto last week) I could resize to one of the other (higer) resolutions that my monitor supports
[09:35] <jansb000> now i can go to monitor preferences, and it correctly lists the available resolution, but they do not apply when I select them
[09:37] <jansb000> any suggestions?
[10:50] <leszek> jansb000: sounds strange. What driver are you using ?
[11:08] <noobSaibot> hello how to reinstall grub with chroot when lubuntu is on /dev/sda5 in @ folder
[11:30] <mxmgg> bonjour à tous, une petite question ? peut on installer lubuntu 14.04 sur un pc non pae ?
[11:34] <hateball> !fr | mxmgg
[11:34] <mxmgg> thank's
[11:48] <Snake57> Does anyone know why my attempted 14.04 Lubuntu VM install is saying - Boot failed "Could not read from CDROM" when attempting to boot?
[11:53] <Snake57> I'll stay in this channel for some time, if anyone sees this any help is very much appreciated!
[12:11] <jansb000> leszek: What driver - uuuh - I just hooked up a monitor to a default installation of lubuntu. My computer is a HP-DL380-G6.
[12:13] <jansb000> it has an ATI ES1000 graphics chip
[12:13] <leszek> jansb000: can you check that with a hardware monitoring tool or lspci -vnn | grep VGA -A10 in a terminal ?
[12:14] <leszek> I assume it is using radeon but just to be sure
[12:14] <jansb000> ok, one moment
[12:16] <jansb000> Kernel driver in use: radeon
[12:19] <jansb000> leszek: Kernel driver in use: radeon
[12:20] <leszek> jansb000: do you still know if the last weeks update did upgrade the kernel =
[12:20] <leszek> ?
[12:26] <jansb000> leszek: unfortunately no - i just, once per week, update the system with whatever updates are available. Every 2 weeks I reboot the system and manually set the resolution.
[12:27] <leszek> jansb000: If the kernel was upgraded next time you boot try to choose one of the older kernels that still should be listed there. Maybe the problem is solved with that older kernel then
[12:29] <jansb000> leszek: ok i will try that - will have to wait till weekend as current processes are not supposed to be interrupted
[12:29] <jansb000> thank you for your help
[12:29] <leszek> np :)
[15:22] <NOOB> hello lubuntu.  i am having ssh_agent starting automagicallt and i would like it to stop.  can you help?
[15:24] <leszek> NOOB: ssh_agent* process you mean ? I think it is started with policykit when you login
[15:24] <leszek> I am not sure it can be disabled
[15:24] <leszek> or you you mean openssh-server aka sshd ?
[15:25] <NOOB> ssh_agent
[15:26] <NOOB> the ssh guys tell me the gnome keyring is being confused and loosing my eys upon reboot cause i have two agents
[15:26] <NOOB> leszek:
[15:26] <NOOB> loosing my keys
[15:26] <leszek> NOOB: ah yeah it is part of the gnome-keyring. If you prevent gnome-keyring from starting it should not start aswell. Though it sounds a bit strange to me alltogether
[15:28] <NOOB> when i import a key into seahorse it fails
[15:29] <NOOB> well it does not fail
[15:29] <NOOB> it suceeds, but does not do it
[15:29] <NOOB> it asks for pass code and comes in and tells me the size and algorithm, but then does not sho in seahorse
[15:30] <leszek> weird issue. First time I heard about it
[15:30] <NOOB> i went to the ssh guys trying to get it fixed
[15:30] <NOOB> and they said i had ssh_agent starting and that needed to stop
[15:31] <NOOB> meh, i'll just wipe thetro
[15:32] <leszek> NOOB: before you wipe anything just try taking gnome-keyring from the autostart entry
[15:37] <NOOB> it not thre
[15:37] <NOOB> there
[15:37] <NOOB> and neither is ssh key agent
[15:37] <NOOB> leszek:
[15:47] <LargePrime> leszek:
[15:47] <LargePrime> crashed
[15:47] <LargePrime> wad i miss
[15:47] <leszek> nothing