/srv/irclogs.ubuntu.com/2019/02/08/#ubuntu-x.txt

* alkisg got access to one of the schools with black screens, let's see... i5-6400, HD Graphics 530 [8086:1912] (rev 06)06:29
alkisgUpdating from ppa: libegl-mesa0 libegl1-mesa libgbm1 libgl1-mesa-dri libgl1-mesa-glx  libglapi-mesa libglx-mesa0 libosmesa6 libwayland-egl1-mesa libxatracker2  mesa-va-drivers mesa-vdpau-driver06:30
alkisgtjaalton: sorry for the direct ping; I updated to the mesa from the PPA, and lightdm still fails. Anything else I can try? Any logs to keep, while the server is booted without nomodeset?07:13
tjaaltonboot an earlier kernel07:14
alkisg.44 or .29?07:15
* alkisg tries with this first: vmlinuz-4.15.0-44-generic07:15
tjaalton-44 is broken07:15
alkisgOK, 29 then, from the repositories07:15
alkisg4.15.0.20.23 50007:15
alkisgSorry I meant that one, that is available from the stock repositories07:16
tjaaltonthat's the metapackage07:16
alkisgapt install linux-image-4.15.0-20-generic linux-modules-4.15.0-20-generic linux-modules-extra-4.15.0-20-generic07:16
tjaaltonthat should do it07:16
alkisgGRUB_DEFAULT='gnulinux-advanced-00d0b350-2f42-4574-8abe-b53ede7da033>gnulinux-4.15.0-20-generic-advanced-00d0b350-2f42-4574-8abe-b53ede7da033'; update-grub; reboot07:23
alkisgtjaalton: the same. `uname -r` = 4.15.0-20-generic, gput-manager, lightdm ==> failed07:25
alkisgXorg.log reports success even though it fails: https://termbin.com/6l2b07:26
alkisgPlain `xinit` reports: i965: Failed to submit batchbuffer: Invalid argument07:26
tjaaltondowngrade mesa then07:26
alkisgI'll need a bit of help on that, which packages does it involve, any handy commands? Trying...07:27
tjaaltonyou just mentioned the list of packages that got updated..07:27
tjaaltonapt install foo=ver07:27
alkisgThat was the updates from the ppa, not the whole list07:27
alkisgecho $(dpkg -l '*mesa*' | awk '/^ii/ { print $2 }')07:28
alkisglibegl-mesa0:i386 libegl1-mesa:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:i386 libglapi-mesa:i386 libglu1-mesa:i386 libglx-mesa0:i386 libosmesa6:i386 libwayland-egl1-mesa:i386 mesa-utils mesa-va-drivers:i386 mesa-vdpau-drivers:i38607:28
tjaaltonapt-cache policy libgl1-mesa-dri for instance will show that the original version is still there07:28
alkisgAre those enough, to downgrade?07:28
tjaaltonmaybe, and it'll complain if there are more dependencies07:28
alkisgTy, trying07:28
alkisgI'll try 18.0.0~rc5-1ubuntu107:28
tjaaltonthat's what main has07:29
tjaaltonand bionic shipped with07:29
alkisgI have those available: 18.2.8-0ubuntu0~18.04.1~ppa1,  18.2.2-0ubuntu1~18.04.1, 18.0.0~rc5-1ubuntu107:29
alkisgWhich one should I try? I think the first 2 failed07:29
tjaaltonthe last07:30
alkisgSo I guess, try with the stock bionic? Yup.07:30
alkisgapt install libegl-mesa0:i386=18.0.0~rc5-1ubuntu1 libegl1-mesa:i386=18.0.0~rc5-1ubuntu1 libgl1-mesa-dri:i386=18.0.0~rc5-1ubuntu1 libgl1-mesa-glx:i386=18.0.0~rc5-1ubuntu1 libglapi-mesa:i386=18.0.0~rc5-1ubuntu1 libglx-mesa0:i386=18.0.0~rc5-1ubuntu1 libosmesa6:i386=18.0.0~rc5-1ubuntu1 libwayland-egl1-mesa:i386=18.0.0~rc5-1ubuntu1 mesa-va-drivers:i386=18.0.0~rc5-1ubuntu1 mesa-vdpau-drivers:i386=18.0.0~rc5-1ubuntu1 libgbm1=18.0.0~rc5-1ubunt07:36
alkisgu1 libegl1-mesa=18.0.0~rc5-1ubuntu1 libegl1=1.0.0-2ubuntu2 libglvnd0=1.0.0-2ubuntu2 libgl1-mesa-glx=18.0.0~rc5-1ubuntu1 libgl1=1.0.0-2ubuntu2 libglx0=1.0.0-2ubuntu207:36
alkisg...a long list there, probably cut by irc :D07:36
tjaaltonwhy would it want to downgrade libegl1 et al07:36
alkisgVersion mismatches07:37
tjaaltonhuh?07:37
tjaaltonah ok07:37
tjaaltonnevermind07:37
tjaaltondoesn't matter07:37
alkisgI build all this list slowly, because each one complained about some other package version mismatch,07:37
alkisgnow it wants to remove vlc and kio etc, but I don't know how else to do it07:37
alkisgThe following packages will be REMOVED:  kinit kio kolourpaint libgles2 libkf5kdelibs4support5  libkf5kdelibs4support5-bin libkf5notifications5 libkf5parts-plugins  libkf5parts5 libkf5sane5 libkf5wallet-bin libkf5wallet5 libkwalletbackend5-5   libwayland-egl1 phonon4qt5 phonon4qt5-backend-vlc vlc   vlc-plugin-video-output07:39
alkisgI can put them back on after we test, shall I continue?07:39
tjaaltondowngrade wayland07:40
tjaaltontoo07:40
alkisgThey're using MATE, so I hope it won't even load wayland07:41
tjaaltonand libgles207:41
alkisgapt install libgles2=1.0.0-2ubuntu2 ; reboot07:42
alkisgtjaalton: that worked07:44
tjaaltondowngrade fixed it?07:44
alkisgYes07:44
tjaaltonok, file a bug upstream and on lp07:44
alkisgThank you, doing so07:45
tjaaltonwondering if it's lightdm which is triggering it07:45
alkisgMaybe MATE as well07:46
alkisgBut plain xinit doesn't work either07:46
alkisgI.e. it's possible that ubuntu gnome users don't even see that, I don't know07:46
tjaaltonhow did you run xinit if it didn't have any display?07:46
alkisgFrom something like ssh07:46
alkisg(epoptes, remote control)07:47
tjaaltonk07:47
tjaaltondoes xubuntu use the same bits?07:48
tjaaltonprobably not07:49
alkisgUnfortunately I don't have a hardware that fails locally, and it's very hard to test other distros than mate remotely07:49
alkisgI'll try to find some affected hardware tomorrow07:49
tjaaltonubuntu mate07:50
tjaaltonI'll try that on snb07:50
alkisgI file it in https://bugs.freedesktop.org/enter_bug.cgi under Drivers/DRI/i915? It warns "that's the old driver"07:50
tjaaltoni96507:50
alkisgTy07:50
tjaaltonunless it's migrated to gitlab, not sure07:51
alkisgThey also have a 18.3 there, can I try that in Ubuntu?07:51
alkisgxorg-edgers or something?07:51
tjaaltonI can push that to x-swat updates07:53
alkisglspci => 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694] Kernel modules: i91507:58
tjaaltondoes dmesg have anything btw?07:58
tjaaltonit's sandybridge07:58
alkisgtjaalton: i915?07:58
tjaaltonyes07:58
alkisgAnd I should report it under i965?07:59
tjaaltonthe dri driver is i96507:59
alkisgty07:59
alkisgdmesg is clean07:59
alkisghttps://termbin.com/ip4e07:59
tjaaltonhmm08:00
tjaaltonit's skylake actually08:01
alkisgA mail was just sent to ltsp-discuss, "black screen on cinnamon"08:01
alkisgI think they're using lightdm too08:01
tjaaltonk08:03
alkisghttps://bugs.freedesktop.org/show_bug.cgi?id=10958308:04
ubottuFreedesktop bug 109583 in Drivers/DRI/i965 "Black screen on skylake after 18.0 => 18.2 update" [Normal,New]08:04
alkisgFiling in launchpad now...08:04
tjaaltoncheck lightdm logs btw08:05
tjaaltonif they have the same error08:05
alkisgI don't think systemd even starts lightdm as it depends on gpu-manager08:06
alkisgAh, I can try restarting gpu-manager, I think that allows systemd to start lightdm and let it fail there..08:06
tjaaltonso how does it fail then?08:06
tjaaltonand what's failing..08:07
tjaaltonso you're running 32bit on skylake?08:08
alkisggpu-manager, with some error message about not able to initialize the cards etc08:08
alkisgYes. Hmm, I'll try to see if 64bit installations are affected08:08
alkisgLet me update mesa so that I see the errors again08:09
tjaaltonjust run full dist-upgrade08:09
alkisgYeah that's the easy one :)08:09
alkisgLaunchpad bug: https://bugs.launchpad.net/mesa/+bug/181517208:10
ubottuLaunchpad bug 1815172 in mesa (Ubuntu) "Black screen on skylake after 18.0 => 18.2 update" [Undecided,New]08:10
tjaaltongreat08:10
tjaaltoni wonder if that xinit is doing the right thing, or if it's trying to use remote x somehow08:15
alkisgtjaalton: nah I use it a lot of times, it works great for troubleshooting08:15
tjaaltonok then08:15
alkisgI can even get remote access after that, I know that step08:15
alkisg*remote xorg, with vnc08:15
alkisgsystemctl status gpu-manager: https://termbin.com/kkix08:16
tjaalton18.3.3 test build on cosmic fine, now bionic08:16
alkisgThanks08:16
alkisggidarakos: could you tell the school to leave the server open for the whole weekend?08:17
alkisg*running08:17
tjaaltontseliot: ^08:17
tjaaltontseliot: the gpu-manager error08:17
alkisgsystemctl status lightdm: https://termbin.com/ybev08:17
tjaaltoncheck it's logs then08:18
tjaaltontseliot: probably nothing08:18
alkisgClean lightdm.log, after doing: systemctl start gpu-manager; systemctl start lightdm: https://termbin.com/ssrb08:20
alkisggpu-manager runs for a bit, and allows the lightdm service to run without dependency issues, then enter the failed state08:20
tjaaltonthen look at the x log08:20
tjaalton[+0.18s] DEBUG: XServer 0: X server stopped08:20
tjaaltonit was respawning every 0.2s08:21
alkisgLast xorg.log: https://termbin.com/92rx08:21
tjaaltonhuh08:21
alkisgI never see any issues in xorg log in these tests08:22
tjaaltonso it's a client crashing that takes the server down without leaving a trace in the log08:22
tjaaltonenable apport, check /var/crash08:22
alkisgIsn't xinit a simpler test there?08:23
tjaaltonmaybe08:23
alkisgAs it doesn't involve lightdm and anything?08:23
alkisgxinit again gives a clean xorg.log, with just this in stderr: i965: Failed to submit batchbuffer: Invalid argument | xinit: giving up | xinit: unable to connect to X server: Connection refused | xinit: server error08:24
tjaaltonok08:24
alkisgApport is enabled afaik, but nothing in /var/crash08:25
alkisghttps://wiki.ubuntu.com/Apport#How_to_enable_apport08:25
tjaaltonalright08:26
tjaaltonuploaded 18.3.3 to ppa:ubuntu-x-swat/updates08:29
alkisgTy, adding...08:29
tjaaltonnot built yet08:30
gidarakosalkisg: Ok, I'll ask for it and I'll let you know..08:31
alkisg18.2.8-0ubuntu0~18.04.1~ppa1 500 for now, waiting08:31
alkisgThank gidarakos08:31
gidarakosalkisg: you are welcome! :)08:33
alkisgAnother school that has the issue, said: 64bit installation, Intel Corporation HD Graphics 530 [8086:1912] (rev 06)   Subsystem: Dell HD Graphics 530 [1028:06b7]08:47
alkisgSo fortunately it doesn't just happen on 32bit systems :)08:47
tjaaltonk08:47
alkisgUpgrading to 18.3..09:06
alkisgSame issue09:08
tjaaltoncool09:10
tjaaltonno need to bisect09:10
alkisgEh, unless we end up needing to bisect between 18.0 and 18.2, to pinpoint the issue :D09:11
tjaaltonnah09:11
tjaaltonwhat does xinit try to run, btw?09:12
alkisgtjaalton: would it make sense to try with a -hwe kernel, something newer than 4.15?09:12
alkisgxinit runs xterm09:12
tjaaltonk09:12
alkisgWhen not provided any params09:12
tjaaltonright09:13
tseliottjaalton: is that a hybrid system?09:33
tjaaltonno09:33
alkisgDebug log: https://termbin.com/6n1209:34
tseliotthen I doubt the error is fatal09:34
alkisgAfter: echo 0xf > /sys/module/drm/parameters/debug; xinit; dmesg09:34
tjaaltonright, it didn't prevent lightdm from starting09:34
tjaaltonalkisg: chris (ickle) is also on #intel-3d09:44
tjaaltonhum, should ubuntu mate support efi boot?09:57
tjaaltonprobably not09:58
tjaaltondoesn't have an EFI dir09:58
tjaaltontrying it on a kabylake10:00
tjaaltonseems to hang10:02
tjaaltonhmm no, it was probably respawning the desktop and didn't accept any input other than power button10:05
tjaaltonyep, works with nomodesest10:07
tjaalton-set10:07
tjaaltonoh right, 32bit doesn't support efi..10:11
tjaaltonalkisg: try with the hwe kernel10:17
tjaaltonlinux-image-4.18.0-14-generic10:19
tjaaltonand the modules10:19
tjaaltonalkisg: try the kernel from proposed10:27
tjaaltonalkisg: nevermind10:28
tjaaltonbut try hwe kernel10:28
tjaalton64bit daily image seems to work fine here10:41
tjaaltonalkisg: I'm running 64bit mate with stock bionic kernel & X and things work fine :/11:03
alkisgBack11:23
alkisgtjaalton: AFAIK all ubuntu CDs have the EFI dir, but in the fat special file system, not in the iso9xx noe11:24
alkisg*one11:24
alkisgI do have MATE installed under EFI11:24
alkisgAh 32 bit, ok, yeah11:24
* alkisg tries with -hwe11:24
alkisgapt install linux-generic-hwe-18.0411:26
tjaaltonI'll install 32bit version next11:27
alkisgtjaalton: Does it run with 4.15 for you?11:28
tjaalton64bit did11:28
alkisgWhich card, the same as the schools?11:28
tjaaltonkabylake, same gen9 as skylake11:28
alkisgMaybe it depends on the specific model?11:29
alkisgRebooting with 4.18...11:29
alkisg4.18.0-14-generic => failed11:31
tjaaltonk11:31
tjaaltonskl gt2 is pretty much the same as kbl gt2, which this is11:32
alkisgA school did report failure with their 64bit installation, so I don't know what  to say11:33
tjaaltoncould be something else11:33
tjaaltonmeh, installing 32bit messed up grub/efi11:44
alkisgDo you get the rescue prompt?12:08
tjaaltonyes12:11
alkisgset root=(hd0,gpt1)12:11
alkisgconfigfile /boot/grub/grub.cfg12:11
alkisgI think this should work...12:11
alkisgPoint it to your 64bit instalaltion12:11
alkisgAfter it boots, run grub-install /dev/sda12:11
tjaaltonso what after configfile?12:12
tjaaltonit just clears the screen12:12
alkisgOuch, it should have displayed the grub menu12:13
alkisgset root=(hd0,gpt  ==> tab there for autocompletion12:13
alkisgIf you installed in 2 partitions, select the other one12:13
tjaaltonnah12:14
alkisgEh, then manually load linux/initrd12:15
alkisglinux /boot/vmlinuz root=/dev/sda112:15
alkisginitrd /boot/initrd.img12:15
alkisgboot12:15
alkisgAnd if grub.cfg was empty,you'll need `update-grub` as well, to generate a proper one12:15
tjaaltoni'll just fix it from a live session12:16
tjaaltonha, was able to boot the 32bit install after all, and it works fine12:26
alkisgAnother affected school has a slightly different card: 12:39
alkisg root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04)         Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]         Kernel driver in use: i91512:39
tjaaltonthat's kbl gt2, which I have12:44
alkisgHrm. Stranger and stranger.12:45
alkisgShould I mention in the bug report that we're using modesetting instead of the intel driver? (the Ubuntu defaults)13:04
tjaaltonno13:04
tjaaltonit's seen on the X log13:04
alkisgOK, ty13:04
alkisgtjaalton: you can boot an efi installation from grub-rescue-cd, by typing that "configfile" command above, if you feel like spending the time to test that...13:22
tjaaltonyeah I fixed it already13:54
* alkisg tests with linux-image-4.20.7-042007-generic_4.20.7-042007.201902061234_i386.deb ...14:16
tjaaltonoh right, I was about to push mesa 19.0rc2 somewhere..14:18
alkisgThey're asking me for the output of `/usr/bin/glxinfo -B`, how should I provide that, with nomodeset or with AccelMethod=none?14:20
alkisgI don't have a display without those, and I guess no glx in either case?14:20
tjaaltonyou should probably get the hw on your desk14:21
tjaaltonotherwise it'll be painful14:21
tjaaltonas it is14:21
alkisgI only have one so far in my city, and it's the school  server... I'll see if I can replace the server with something else, and keep the disk maybe...14:22
alkisgThe others are in other cities14:22
tjaaltonyou don't have skylake?14:24
tjaaltonI guess legacy bios is the key14:25
tjaaltonbut I can't wipe my machines14:25
alkisgI only have this in my office: 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)14:25
tjaaltonthese machines14:25
alkisgWait, I think it works fine with 4.2014:25
alkisgLet me reboot without xorg.conf...14:25
tjaaltonthat's a haswell14:26
tjaaltongen7 gpu14:26
alkisgI don't have anything more recent here :(14:26
alkisgBut I tried 4.20 in the remote school, and I think it works, I'll be sure after the reboot14:26
tjaaltoncool14:26
alkisgNot sure how that will help us for a "real" solution, but it's surely progress14:26
alkisgYup, it seems to work ifne14:28
alkisgfine14:28
tjaaltonit's a kernel bug then14:29
tjaaltonfixed between 4.18..4.2014:30
tjaaltonickle might have ideas.. post to the upstream bug14:30
tjaaltonlooking at changes to i915_gem_execbuffer.c gives some hints14:30
alkisgSo, mesa=18.0 works, mesa=18.2 breaks, yet it's a kernel issue? :D14:32
alkisgMeh these programmers! :P14:32
* alkisg has been a programmer / sysadmin for 25 years now...14:32
tjaaltonneeds a newer kernel :)14:35
tjaaltonalkisg: you could bisect the kernel by using mainline builds between 4.18 and .2014:50
tjaaltonalkisg: if you're still around, boot v4.19.0, then .315:03
tjaalton.3 has plenty of changes for i91515:03
alkisgtjaalton: thanks, will do15:06
alkisgtjaalton: so the end result will probably be a kernel cherrypick for 4.15 in bionic?15:06
tjaaltones15:07
tjaaltonyes15:07
alkisgty15:07
alkisgtjaalton: if you do build a kernel, please build both 32bit and 64bit, so that schools test both of them...16:28
tjaaltonalkisg: need to push to a ppa16:28
tjaaltonbut can do16:28
tjaaltonppa with tons of space, I have that16:28
alkisgGreat, even better than wget16:29
tjaaltoncould probably cross-build locally, but meh16:33
tjaaltonI'll verify the build first as 64bit16:33
tjaaltonlocally, then upload16:33
tjaaltonalkisg: maybe I'll just revert softpin support from mesa, as ickle suggested.. more likely to get in the release16:41
alkisgSure, whatever is easier16:41
alkisgI can test mesa then,if you want me to16:41
tjaaltonyes, getting late, maybe not today, we'll see16:45
tjaaltonI'll check the code first how to disable it16:46
alkisgnp, take your time, thanks for all the help16:46
tjaaltonmust be this https://pastebin.com/tAeRSD1v17:01
tjaaltonso I'll revert that17:01
tjaaltonalkisg: I've pushed it to https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging17:15
tjaaltonand closed the upstream bug17:18
alkisgtjaalton: thanks, will test when it builds. It's 18.2 with that line reverted?17:18
tjaaltonyeah17:18
alkisgGreat, ty17:18
tjaaltonthe kernel patches will be backported later17:18
tjaaltonalkisg: i386 seems to be built18:00
alkisgty,testing...18:06
* alkisg hopes he didn't mess up grub this time :D18:10
tjaaltonmesa doesn't touch it18:10
tjaaltonkernel update does18:10
alkisgThe hard part is configuring grub to boot an older kernel18:11
alkisgFrom 4.19 back to 4.1518:11
tjaaltonuninstall 4.1918:11
alkisgNot good when it's running, apt refuses18:11
tjaaltoncomplains18:11
alkisgHmm maybe that changed from the last time I tried18:11
alkisgtjaalton: success!18:12
alkisgCan I copy this to the schools ppa, for everyone to get?18:12
tjaaltonsure18:12
janesmatjaalton: Mesa i965 was hitting consistent deadlocks with userptr, so we switched entirely to softpin recently18:12
alkisgI assume it'll be overriden by the next stable update, right?18:12
tjaaltonit'll be in proposed soon18:12
janesmaalkisg: you reported that this happened with 64bit systems too?  18:13
tjaaltonjanesma: well, changing the kernel takes more time than rolling a revert via mesa18:13
alkisgjanesma: yes, a school said it saw it on a 64bit system18:13
janesmayep18:13
tjaaltonand kernel won't get changed for 18.04.2 image which is next week18:13
janesmawhy wouldn't see the same thing with upstream mesa 18.3.3 and linux 4.18.2, on a 64bit system?18:15
alkisgThe same card?18:15
alkisgtjaalton didn't see it either, I don't know why18:16
tjaaltonbeats me, but this was with legacy bios18:16
janesmait was a skylake machine...  I think all of this should be the same for gen918:16
tjaaltonwhich might or might not play a part18:16
tjaaltonI tested on a kbl laptop18:16
janesmayeah, gen9 has the same feature set (skylake kabylake coffeelake)18:17
janesma100% symmetry in the mesa regressions18:17
janesmawe don't test different boot configurations (legacy/uefi), and I can't see how that would affect graphics....  but if it does then we have a new validation problem.18:17
tjaaltonI'll test next week on hw that I can wipe clean18:18
janesmaI'm hoping that this is down to running a 32bit kernel.18:18
tjaaltonI managed to boot that too, still worked18:19
janesmaI'd like to figure out how to reproduce this and make sure we aren't missing something in Mesa CI.18:21
janesmaI think disabling softpin will cause intermittent hangs under load for ubuntu users.  Not nearly as bad as a black screen.18:22
tjaaltonthat's a good tradeoff for now18:22
alkisgIt's not configurable by kernel cmdline or xorg.conf, right?18:22
janesmamesa 19.0 has the switch to softpin, in 731c4adcf9b1118:24
janesmanot sure what that will do to oibaf/padoka users.  I guess they will be getting newer kernel and mesa, so they won't suffer.18:25
tjaaltonalkisg: bionic will get 18.2.2 + the revert soon, 18.2.8 will follow after 18.04.2 is released18:38
tjaaltonalkisg: are you still able to verify this build?18:42
alkisgtjaalton: I only have access to one server now, and it works with this build, yes18:42
tjaaltonremove 18.2.8 with ppa-purge, then enable proposed and install the new update from there, then verify bionic for the bug18:43
alkisgSchools will need it on monday anyway, so if it'll get the build until then, I can do the verification done step18:43
alkisgWill do18:43
tjaaltonit just got accepted, so the build takes a while again18:43
alkisgTomorrow is fine18:43
tjaaltonhttps://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.04.218:43
tjaaltonalready building18:44
tjaaltonyeah tomorrow is fine I guess18:44
tjaaltonthanks for everything so far18:45
tjaaltonalmost 2100, time to grab a beer18:45
alkisgThank you too!18:45
tjaaltontoo late to go out for a run18:45
alkisgOh, same timezone, where are you?18:45
tjaaltonespoo, finland18:45
* alkisg ran 10 km earlier18:45
alkisgAh, greece here, so yeah same timezone18:45
tjaaltonyup, I remember18:46
* alkisg sends a virtual beer to tjaalton :)18:46
tjaaltonhope we'll get to crete again next year18:46
tjaaltonthough it's a tourist trap but we like it18:46
alkisgHere's a nice trick I found to revert to the stock versions, even when ppa-purge can't do it; google translate needed: http://alkisg.mysch.gr/steki/index.php?topic=7370.018:47
alkisgYeah I spent 5 of my best months in crete18:47
tjaaltonwhat happened ?-)18:47
alkisgNah, just talking in general, nothing happened here18:48
alkisgI had to research it for schools with veeery broken installations18:48
alkisgthat were installing .debs from wherever they could find them18:48
tjaaltonI mean in crete, why only 5mo :)18:48
alkisgHaha18:48
alkisgI was in the army then18:48
tjaaltonah right18:49
alkisgFor 23 months, 5 in crete18:49
alkisgAnd even though the army generally isn't a good period.... crete was soooo nice....18:49
tjaaltonI remember f-16 flyovers18:49
alkisgand many tourist women too :D18:49
tjaaltonyes yes, very receptive18:49
tjaaltonI assume18:49
janesmatjaalton: if you find a way to reproduce this locally, can you update me?19:04
alkisgSo to only update mesa from proposed, I guess this will do it (after apt sources + pinning):19:07
alkisgapt update libegl-mesa0:i386 libglapi-mesa:i386 libxatracker2:i386 libegl1-mesa:i386 libx11-6:i386 libgbm1:i386 libwayland-egl1-mesa:i386 libx11-data:i386 libgl1-mesa-dri:i386 libosmesa6:i386 libgl1-mesa-glx:i386 mesa-vdpau-drivers:i386 libx11-xcb1:i386 mesa-va-drivers:i386 libglx-mesa0:i38619:07
alkisgI don't know why these libx11 things were in the upgraded-from-the-ppa list previously though...19:08
alkisgtjaalton, janesma: apt policy libegl-mesa0:i386 => 18.2.8-0ubuntu0~18.04.1 from bionic-proposed/main19:11
alkisgHow can you upload 18.2.2 when it has 18.2.8?19:11
alkisgAh, maybe standard repository rules don't apply to the proposed queue :)19:12
tjaaltonalkisg: 18.2.8 got removed19:33
tjaaltonjanesma: hope I can, next week19:33
alkisgyup, proposed works, i'll comment in launchpad21:04
alkisgHmm it'll be hard to do the cosmic verification21:09
tjaaltondon't worry about that21:09
tjaaltonthanks for testing21:10
alkisg:)21:10
alkisgThanks for the package :)21:10
tjaaltonalkisg: and released to updates :)21:57
tjaaltonnow 18.2.8 back in21:57
alkisgYey!!!! :)22:09
tomreynis there a change to get vega20 fimwares from agd5f into disco before release?23:36
tomreyn*chanCe23:36

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!