| jbicha | fes_: did you used to be able to use GNOME on Wayland on this computer with nouveau? | 00:02 |
|---|---|---|
| fes_ | With earlier versions of Ubuntu, for example 16.10? Yes I was. | 00:05 |
| jbicha | I looked at the journal errors that ubuntu-bug added to your bug report | 00:06 |
| jbicha | it says that GDM is using X | 00:07 |
| jbicha | but it normally uses Wayland by default, so whatever is causing it to use X is probably the same thing that isn't giving you a Wayland option | 00:07 |
| jbicha | do you want to try using Intel by default instead of nouveau? | 00:09 |
| jbicha | if so, see what happens if you install the amd64 deb from https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+sourcepub/7541961/+listing-archive-extra | 00:09 |
| jbicha | (I'm hoping to get switcheroo-control into Ubuntu before 17.04 is released) | 00:09 |
| jbicha | reboot after installing that | 00:10 |
| fes_ | how do I use intel instead of nouveau? This is a hybrid graphics laptop with both intel GPU and nvidia GPU. | 00:18 |
| fes_ | I will install that package you mentioned. Is there anything I should take notice of to use that package to its full potential or just to get it to make a difference? | 00:20 |
| fes_ | Do you want me to install both the debug package and the ordinary package or is the ordinary (switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb) enough? | 00:21 |
| fes_ | I have installed it and I will restart not to see if it makes a difference. | 00:24 |
| fes | it did not make a difference. I am still not able to use wayland session. | 00:28 |
| jbicha | so switcheroo-control is supposed to default you to using the integrated graphics card | 00:28 |
| jbicha | but if you right-click on an app launcher in GNOME Shell, you can launch it using the dedicated, more powerful graphics card | 00:29 |
| jbicha | you don't need the dbgsym package | 00:30 |
| jbicha | could you open Settings>Details and paste what you see in the Graphics line? | 00:33 |
| fes | that works! | 00:33 |
| fes | sure... | 00:33 |
| fes | Graphics: Intel® Sandybridge Mobile / Intel® Sandybridge Mobile | 00:33 |
| fes | Weird that it mentions intel twice, right? | 00:34 |
| jbicha | hmm | 00:34 |
| jbicha | I don't think it's supposed to mention the same thing twice | 00:34 |
| jbicha | I have a simple Intel-only laptop | 00:35 |
| fes | would you like to use teamviewer or some other remote service to check out my system? I am open to letting you do that so that thiscan be solved. | 00:37 |
| fes | what is also weird is that if I execute "DRI_PRIME=1 glxinfo" I get intel's GPU information when I in earlier Ubuntu's got the NVIDIA information. | 00:43 |
| fes | I am updating the package right now and I see that there's drivers updates. I will restart when the upgrade has finished and see if it makes a difference. | 00:45 |
| jbicha | it might be suggesting that you install the NVIDIA proprietary drivers | 00:46 |
| fes | among the files where libdrm packages fror nouveau2, intel, etc. | 00:49 |
| jbicha | ok, could you try rebooting? | 00:54 |
| fes | Will reboot soon and come back here... | 00:54 |
| fes | the upgrade made no difference. | 00:59 |
| jbicha | I don't really know then, I commented on your bug and asked if you could report this to GNOME | 01:01 |
| fes | I have asked in #gnome over at GIMPNet and hope that someone will reply. | 01:08 |
| fes | Thanks for helping out, jbicha | 01:08 |
| fes | jbicha, there was wayland and mesa updates five minutes and now when I restarted.. IT WORKED! I AM NOW USING WAYLAND :D | 02:14 |
| fes | Did you have something to do with this? ;) | 02:14 |
| jbicha | lol, I didn't touch anything! | 02:18 |
| fes | :D | 02:19 |
| jbicha | does the Launch using Dedicated Graphics Card option work? http://www.hadess.net/2016/10/dual-gpu-integration-in-gnome.html | 02:21 |
| jbicha | you can close your bug by setting the Status to Fix Released | 02:22 |
| === Schnabeltierche- is now known as Schnabeltierchen | ||
| gnubuntu | why is scrolling so terrible in firefox | 05:00 |
| darkxst | gnubuntu, what do you mean? its fine here | 05:09 |
| darkxst | tearing? lagging? | 05:09 |
| gnubuntu | both | 05:11 |
| darkxst | what gpu/drivers? | 05:11 |
| gnubuntu | radeon free | 05:12 |
| gnubuntu | 16.10 btw | 05:12 |
| darkxst | I don't have radeon, but generally tearing seems worst with nvidia proprietry under X | 05:13 |
| darkxst | is it only firefox? | 05:13 |
| gnubuntu | i think so | 05:13 |
| darkxst | file a bug | 05:14 |
| gnubuntu | on launchpad? | 05:15 |
| darkxst | yep | 05:15 |
| gnubuntu | i noticed 2 other things - firefox scrollbars are 1px away from the edge of the screen when maximised or fullscreen | 05:16 |
| gnubuntu | makes it hard and tiring to grab it - you cant just move the pointer to the right | 05:17 |
| gnubuntu | 2/ i wanted to use ub-gn on a c2d laptop but the fan was kicking too much so i echo'd the conservative governor to replace ondemand | 05:20 |
| darkxst | you mean the actual scrollbar is only 1px wide? | 05:20 |
| gnubuntu | no | 05:20 |
| gnubuntu | the scrollbar is double in wide size i think this is intentional, i saw a bug about this iirc | 05:21 |
| gnubuntu | there is 1px space between the scrollbar and the screen edge / end of window on the right or bottom | 05:21 |
| gnubuntu | so if you move your pointer right to grab it you cant - its just empty scroll space | 05:22 |
| gnubuntu | about the cpu governor - something kept one of the cpu cores obove min frequency which prevented the fan from going quiet, for no visible reason - no task active | 05:24 |
| gnubuntu | as if it was stuck on a higher freq | 05:24 |
| gnubuntu | 05:53 | |
| === Schnabeltierche- is now known as Schnabeltierchen | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!