=== ph_afk is now known as ph
=== ph is now known as Guest61356
[02:25] <bess> Hi Guys, I have a problem instsalling ubuntu gnome the installer somehow crashes when I choose the custom partition install
[06:51] <sgo11> darkxst, hi, do you have time?
[06:53] <sgo11> darkxst, I added "xrandr --output VGA-0 --off" to /sbin/prime-offload. lightdm resolution problem is fixed. but gdm and gnome-shell still have the same problems. gdm is flickering and fails to start. gnome-shell is a black off screen when login with lightdm. Maybe these problems are not related to my non-existent display?
[07:06] <darkxst> sgo11, hey
[07:06] <sgo11> darkxst, hi. I am here. just added a comment in launchpad.
[07:07] <darkxst> yes saw
[07:08] <Noskcaj> Can i have a link to the ubuntu-gnome 3.10 transition tracker?
[07:08] <darkxst> so the flickering only happens on second display for me, which means probably gdm is displayed on non-existent display
[07:08] <Noskcaj> That did exist didn't it?
[07:08] <darkxst> https://launchpad.net/ubuntu-gnome/+milestone/trusty
[07:09] <darkxst> buts its incomplete
[07:09] <darkxst> really
[07:09] <darkxst> also a few of those are PPA bugs for 3.12
[07:09] <darkxst> had hoped the QA team would take over triaging and tagging bugs, but that hasnt really happened
[07:10] <darkxst> sgo11, and not really surprised setting a second primary during a running session, crashes X!
[07:10] <darkxst> sgo11, you absolutely must only ever have one primary
[07:12] <sgo11> darkxst, ok. do you mean I should try "xrandr --output LVDS-1-0 --primary" in /sbin/prime-offload? can I put both "xrandr --output VGA-0 --off" and  "xrandr --output LVDS-1-0 --primary" in that file? thanks.
[07:12] <darkxst> sgo11, sure try that
[07:12] <darkxst> just put the --off command before the --primary one
[07:13] <sgo11> darkxst, ok. got it. I will try that now. I am using that laptop now. so I will have to quit IRC first. brb. thanks.
[07:13] <Noskcaj> darkxst, I have triage rights if you need anything
[07:16] <darkxst> Noskcaj, well I want all significant gnome-shell/mutter/gjs bugs etc tagged under Ubuntu gnome
[07:16] <darkxst> I will add you to that project so you can actually tag them though
[07:16] <Noskcaj> ty
[07:21] <darkxst> Noskcaj, done, so add project ubuntu-gnome to bug, then you should be able to select milestone trusty
[07:21] <sgo11> darkxst, just tried that. gdm is still flickering. the only difference is when I switch to VT1 and back to VT7, there is no pupup window "could not set the configuration for CRTC 652". when switching back to VT7, the screen is not updated, thus it still shows screen VT1 image.
[07:21] <Noskcaj> ok
[07:22] <darkxst> sgo11, you get the gdm grey background during flickering state though?
[07:22] <sgo11> darkxst, then, I tried to switch to lightdm. what I see this time is a popup window "The system is running in low-graphics mode" title.
[07:23] <sgo11> darkxst, yeah, gdm grey background flickering between grey and black (off).
[07:23] <darkxst> sgo11, first is odd, second means gdm is loaded but displayed on the other display
[07:23] <darkxst> sgo11, let me see if I can revert the config change in gpu-manager
[07:24] <sgo11> darkxst, in lightdm, it shows "Your screen , graphics card, and input device settings could not be detected correctly. You will need to configure these yourself". that is the content of that title.
[07:24] <Noskcaj> Actually, i need to update d-conf
[07:26] <darkxst> sgo11, yeh I know that popup, anyway undo those changes and try with the updated ubuntu-drivers-common which is building now on the ppa
[07:28] <sgo11> darkxst, when you say undo those changes, do you mean removing two lines "xrandr --output VGA-0 --off" and "xrandr --output LVDS-1-0 --primary" in /sbin/prime-offload ? thanks.
[07:28] <darkxst> sgo11, perhaps try just remove the '--primary' first
[07:28] <darkxst> but if that still doesnt work, then remove the other one
[07:29] <sgo11> darkxst, ok. got it. when the building is complete, please let me know. I will do update. thanks.
[07:29] <darkxst> I suspect you can't actually make an offloaded display primary
[07:29] <darkxst> sgo11, I'm off to cook dinner, it should take 20mins or so
[07:29] <sgo11> darkxst, got it. thanks a lot. I will try that.
[07:30] <darkxst> sgo11, if the ppa is still enabled, then just run an update in half, it should pick it up by then
[07:30] <sgo11> darkxst, ok. cheers. :) enjoy your dinner.
[08:15] <sgo11> darkxst, I tried ubuntu-drivers-common 1:0.2.91.2~trusty3. with and without "xrandr --output VGA-0 --off" in /sbin/prime-offload. The problem still remains the same. gdm is flickering.
[08:46] <darkxst> sgo11, is xrandr -q/--listproviders correct now?
[08:51] <sgo11> darkxst, hi, I was about to update the bug. I found a workaround.
[08:52] <sgo11> darkxst, I removed all the changes from /sbin/prime-offload. added Section "Monitor" Identifier "VGA-0" Option "Ignore" "True" EndSection in xorg.conf. both gdm and gnome-shell works. I still can see problem detected once gnome-shell logged in. but that is harmless. I don't see any problems at all.
[08:58] <sgo11> added a comment to the bug for reference.
[09:01] <sgo11> darkxst, sorry, I haven't tried "xrandr -q" without the modification of xorg.conf. I don't think that is correct, because turnning off VGA-0 in xorg.conf solve all the problems.
[09:02] <sgo11> do you want me to try "xrandr -q" without xorg.conf manual modification?
[09:09] <sgo11> PS: I removed all files in /var/crash/* and reboot the system. No "problem detected" popup window anymore.
[09:10] <sgo11> in current workaround, nvidia-settings become useless because it can only detect CRT-0 (VGA-0) which is disabled by xorg.conf.
[09:24] <darkxst> sgo11, sorry this is way out of my realm!
[09:25] <darkxst> I think you workaround does confirm that the 'non-existent' display is what causing the issues
[09:25] <darkxst> but I really I have no idea where it is coming from
[09:25] <sgo11> darkxst, yeah, "non-existent" does cause the issue. that is what I think too.
[09:26] <darkxst> my guess was the updated ubuntu-drivers-common would remove the issue, but it didn't so its a regression somewhere else
[09:26] <sgo11> darkxst, since I can use gdm and gnome-shell with nvidia-driver now, there is another small problem. gnome-tweak-tool shows workspaces are dynamics. but I can only see one workspace. the second workspace is never created.
[09:27] <darkxst> sgo11, in tweak tool? or gnome-shell
[09:28] <sgo11> darkxst, in gnome-shell, the second workspace is never created. I always have one workspace.
[09:29] <darkxst> sgo11, that is probably fallout from not having a primary monitor, you should file an upstream bug for that
[09:29] <sgo11> darkxst, in bug #1296020, there is a new comment or status which says "no longer affects: ubuntu-drivers-common". I don't know what it means. maybe it means this issue is from somewhere else.
[09:29] <ubot5> bug 1296020 in xorg (Ubuntu) "[Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)" [Undecided,New] https://launchpad.net/bugs/1296020
[09:30] <darkxst> sgo11, probably just means the triager had not much clue, but given your recent findings he got lucky and was right!
[09:31] <sgo11> I don't know how to fire an upstream bug. from what you say, that means the workspace issue should be fixed if "non-existent display" gets fixed by ubuntu.
[09:32] <darkxst> sgo11, https://bugzilla.gnome.org/, and not exactly I suspect workspace creation is tied in with the primary display
[09:33] <darkxst> if you don't have a primary you might not be able to get a new workspace
[09:33] <darkxst> (although it has been sometime since I looked at that code, so could be off here)
[09:34] <sgo11> darkxst, oh. I figured it out. there is an option in gnome-tweak-tool. Workspaces --> "Workspaces only on primary display". that is set to ON by default. After setting it to OFF, I can see the second workspace.
[09:34] <darkxst> sgo11, still a bug!
[09:35] <darkxst> all the logic in that stuff assumes you actually have a primary display
[09:35] <darkxst> and apparently that doesnt happen with off-loaded displays
[09:37] <sgo11> ok. anyway. I am very happy today. I found a workaround solution, and I can use gdm and gnome-shell in my laptop now. Hopefully, the "non-existent" display issue can be fixed later.
=== makije|away is now known as makije
[09:37]  * darkxst has to disappear for the night, please do file an upstream bug about this (against gnome-shell)
[09:38] <sgo11> darkxst, ok. I will try to fire one. never did this. let me see. thank you very much for your help!
[09:41] <sgo11> darkxst, sorry to interrupt. I am a newbie and bad in English. if possible, can you tell me what should be the title of this bug? "Workspaces can not be dynamically added when there is no primary display." ?
=== makije is now known as makije|away
[10:11] <sgo11> darkxst, anyway, I fired the bug: https://bugzilla.gnome.org/show_bug.cgi?id=726914
[10:11] <ubot5> Gnome bug 726914 in overview "Workspaces can not be dynamically added when there is no primary display (ubuntu trusty)" [Normal,Unconfirmed]
=== Robbilie_ is now known as Robbilie
=== Guest61356 is now known as ph_afk
=== makije|away is now known as makije
=== makije is now known as makije|away
=== FJKong is now known as FJKong_afk
=== back is now known as Guest16731
=== Guest16731 is now known as bakc
[18:04] <ljunggren> Hi
[18:05] <ljunggren> Thanks, 1 question since google could not help me : i have found numerous guides to install gnome 3.10 on ubuntu 13.10 but that just sounds like problems. Would following that guide but in Ubuntu-gnome be more error free? since it does not come packed with unity etc?
[18:05] <ljunggren> have someone tried it?
=== ceed^_ is now known as ceed^
=== makije|away is now known as makije
=== makije is now known as makije|away
=== jackson is now known as Guest99380
=== Guest99380 is now known as Noskcaj
[22:26] <junkanoo> anyone here
[22:46] <darkxst> !ask
[22:46] <ubot5> Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience