[00:24] <tsimonq2> nacc_: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1752198
[00:43] <nacc_> tsimonq2: i see
[00:48] <tsimonq2> nacc_: One thing to note is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889987#38 ftr
[00:49] <nacc_> tsimonq2: sorry, to note what?
[00:49] <nacc_> tsimonq2: afaict, my new pacakge (reupload of s2tc) can be rejected as your merge goes in
[00:49] <tsimonq2> nacc_: Right, because as that bug comment says, it should have been merged into mesa
[00:49] <tsimonq2> nacc_: (We're on the same page here.)
[00:49] <nacc_> tsimonq2: ack
[01:57] <FurretUber> Hi, I've done a clean install of Lubuntu 18.04 (from yesterday) on a pendrive and I'm using it. I've noticed the grub menu has that strange graphical problem of the options "jumping" too
[01:57] <FurretUber> Also, I've noticed Lubuntu was the only one I could install on the 8 GB pendrive, as all others (even Lubuntu Next and Xubuntu) asked for 8,6 GB of space
[02:03] <FurretUber> On this clean install, virtual machines have full network connectivity. What may be causing trouble on the upgraded install?
[05:14] <wolf4914> What's the deal with nvidia again? Any tweaks to config file may help? 
[05:14] <lotuspsychje> wolf4914: nvidia and wayland are a no-go
[05:15] <lotuspsychje> wolf4914: try xorg + nouveau instead
[05:16] <wolf4914> lotuspsychje: where do I switch the options ?
[05:17] <lotuspsychje> wolf4914: xorg & wayland are choosable at your gdm login screen
[05:20] <wolf4914> I don't have gdm screen - I've upgraded from 17.10 and all I can get is grub by force and then it logs me in tty1. Anywhere in configs I can switch that?
[05:21] <lotuspsychje> wolf4914: check wich drivers active with sudo lshw -C video first
[05:22] <wolf4914> yeah it pops out nvidia
[05:23] <wolf4914> all detected
[05:23] <lotuspsychje> wolf4914: at bottom driver=?
[05:23] <wolf4914> nope
[05:23] <wolf4914> last line is resources'
[05:23] <lotuspsychje> hmm
[05:24] <lotuspsychje> chipset gives: unclaimed perhaps?
[05:24] <wolf4914> no chipset either
[05:25] <lotuspsychje> hmm weird
[05:25] <lotuspsychje> wolf4914: you got hybrid graphics or so?
[05:25] <wolf4914> description product vendor physical Id bus info version width clock capabilities conf and resources
[05:26] <wolf4914> No the older version nvidia
[05:26] <wolf4914> that's all it gets me
[05:26] <lotuspsychje> wolf4914: how about ubuntu-drivers list
[05:27] <lotuspsychje> see what drivers available
[05:28] <wolf4914> how do I output them?
[05:28] <lotuspsychje> tell me here, not a big list right
[05:28] <wolf4914> no I mean a command lol
[05:29] <wolf4914> pastebin is all good but nvidia-drivers errors out for some reason
[05:30] <lotuspsychje> no in terminal: ubuntu-drivers list
[05:30] <wolf4914> that's what I did 
[05:30] <wolf4914> lemme try again
[05:31] <wolf4914> nvidia-340 and nvidia-driver-390
[05:31] <wolf4914> that's all
[05:32] <lotuspsychje> try a nomodeset and enter the xorg session
[05:32] <lotuspsychje> perhaps install nvidia-340
[05:33] <wolf4914> will do - have to run now thanks a lot lotuspsychje
[05:33] <wolf4914> I'll let you know 
[05:34] <lotuspsychje> kk
[09:15] <gnomethrower> Getting issues running apt update
[09:15] <gnomethrower> could not get lock, error 11
[09:16] <gnomethrower> resource temporarily unavailable
[09:16] <gnomethrower> Not running anything, just a fresh boot
[09:22] <gnomethrower> resolved now
[09:42] <gnomethrower> I didn't really do anything other than wait :)
[11:23] <notsgnik> With the last daily image I can't manage to pass the "who are you?" Screen for installation
[11:24] <notsgnik> And wen I use a daily from 2 days ago, as soon as I install the Nvidia drivers I can't manage to boot again
[11:26] <notsgnik> When I'm at booting screen I can push "Ctrl+alt+Fx" witch prompt a try screen witch freeze after couple of seconds using it :/
[11:26] <notsgnik> ( memory leak ? )
[11:27] <notsgnik> ( I'm on a web interface btw, so sorry for my interactions )
[11:30] <notsgnik> I don't know how to give you more clue of what's happening but I'll be glad to help
[11:40] <notsgnik> Also, since we are at the pre LTS, can the prompt for credentials ask for the root credentials wen the current user is not able to run sudo?
[11:41] <notsgnik> Lot of programs break just because of that
[12:43] <tomreyn> notsgnik: did you verify your downloaded copy (?) of the latest daily ISO image against its checksum?
[12:47] <tomreyn> gnomethrower: this error is caused by a background process running by the same time you started apt / dpkg. on your second run, the background process will have ended, so you could run it fine then.
[12:48] <tomreyn> i think this is being handled as a bug (I seem to recall that searching the error message on the web got me some existing bug report)
[12:55] <notsgnik> I didn't but I've did use a DD command ending like this conv=fdatasync && sync 
[12:55] <notsgnik> Made sure that the led on the flash drive was off
[12:56] <notsgnik> Each time with the same daily it crash at the same moment even if I used the key for other pupouse
[12:57] <notsgnik> My gnome Ubuntu 16.04 seems tu run pretty fine using the same method 
[12:57] <notsgnik> And key
[13:00] <notsgnik> tomreyn, I haven't checked against checksum yet it seems unlikely to be due to a bad copy
[13:02] <tomreyn> somewhat unlikley, but easily ruled out, and easy to fix, if it turns out to be an issue.
[13:23] <BluesKaj> Hi folks
[15:41] <FurretUber> Finally I have discovered why my guests had some of their connectivity problems: the iptables rules are working differently now
[15:44] <FurretUber> From Xenial to Artful, it was not needed to set the host's IP in the PREROUTING rules, so the destination of the created rule was 0.0.0.0/0. This no longer works in Bionic: I have to set the host's IP
[17:52] <donofrio_> what do these messages mean to you folks?  (aka what channel should I go ask) (wrapper-1.0:202): Gtk-WARNING **: 00:32:30.749: Unable to locate theme engine in module_path: "pixmap",
[19:32] <hggdh> donofrio_: you may be missing the package gtk2-engines-pixbuf
[19:47] <mceier> Hi, on bionic 18.04, I want to use amdgpu but glxinfo shows "OpenGL vendor string: VMWare, Inc., OpenGL renderer string: llvmpipe [...]" no matter what I do (tried uninstalling/reinstalling packages with amd, ati or radeon in name).... how can I switch X11 to amdgpu ?
[20:16] <tomreyn> mceier: whats your hardware?
[20:17] <mceier> tomreyn: R9 Fury X
[20:19] <tomreyn> and does it work on 16.04?
[20:19] <tomreyn> the amdgpu driver, that is
[20:21] <mceier> I'm not sure... I didn't note the issues I had in 16.04 that I decided to upgrade to the latest version of ubuntu...
[20:25] <tomreyn> mceier: well the latest released version is 17.10, with 16.04 being the latest LTS. upgrading to a non-released (alpha) version is not a good strategy to solve issues.
[20:28] <tomreyn> mceier: check: sudo lspci -knnv | grep -A30 VGA 
[20:28] <tomreyn> this should list the 'kernel driver in use'
[20:29] <tomreyn> also have look at /var/log/Xorg*.log for errors (indicated by '(EE)') and warnings (indicated by '(WW)')
[20:30] <mceier> lspci shows amdgpu driver
[20:30] <mceier> in Xorg.0.log I see: "AMDGPU(0): glamor detected, failed to initialize EGL." and "GLX: Initialized DRISWRAST GL provider for screen 0" also 
[20:31] <mceier> "AIGLX: reverting to software rendering"
[20:32] <tomreyn> mceier: are you running the default kernel without manually added kernel boot parameters?
[20:32] <mceier> yes
[20:33] <mceier> I just updated the packages and didn't touch any files
[20:34] <tomreyn> hmm dunno then. maybe you have some zombie packages which cause issues. you could try this script to identify them: https://github.com/tomreyn/scripts -> foreign_packages
[20:34] <mceier> ok, I will try the script
[20:36] <tomreyn> it's just a wild guess though, but it wont hurt running it
[20:37] <tomreyn> unfortunately i can't stay to help diagnosing the output, if any. but do make sure you look into those packages it reports, if any. since normally it hsould not report any at all.
[20:37] <mceier> there are few foreign packages, but none of them seem to be related to drivers (gdk, php, poppler)
[20:38] <mceier> thanks either way ;)
[20:39] <tomreyn> hmm, probably not the cause, then.
[20:39] <tomreyn> bbl
[20:39] <tomreyn> oh an check these if you haven't https://help.ubuntu.com/community/AMDGPU-Driver
[20:40] <tomreyn> https://www.x.org/wiki/RadeonFeature/
[22:22] <FurretUber> mceier: I had this problem with a Intel HD Graphics 520. The issue were a few packages. One of them was libopengl0. From what I've read from a Red Hat page, one of these "vendor neutral GL dispatch library" breaks the modesetting, making the system fall back to CPU rendering. One choice would be to create a xorg.conf file with the correct setting to your video card at /etc/X11/ (not the best) The other alternative (the best, if possi
[22:22] <FurretUber> e) is to find which package broke the modesetting (libGL.so and/or libEGL.so)