! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Nothing is shown on login aside of mouse cursor
Status:
RESOLVED: MOVED

Comments

Description mirh 2020-01-10 20:42:49 CET
Created attachment 9371 
Glxinfo

I'm running a GeForce 7100 with the last 304.137 nvidia closed drivers (and X.org 1.19). 
After three days of rolling back my whole system, finding it was xfwm4, fighting against the git tree and the tarballs being pretty messy with files at least around 4.13.2, and whatnot.. I could only come up with e07574d6e7a2dbaa08c3ba4765c6306073d9493e as the offending commit. 
... Which promptly made me realize I just needed to switch vblank mode as per bug 15325...

So long story short GLX is not working. 
Now, putting aside that I wouldn't really know whether that would result in better results than Xpresent or not

I choose this title for the bug report because it wouldn't be bad to get that fixed..
But if not at least some mechanism could be put in place for people not ending up with a broken desktop. 

There are no relevant messages at all in the usual places (dmesg, x.org.0, xsession-errors) so that's why I cannot give away any more "tangible data". 
After giving a quick look at the source code, one wonder that came to my mind is whether, being this hardware limited to GL 2.1 (and you not using any shader/glsl), you aren't just forgetting to call glEnable(GL_TEXTURE_2D) on init.
Comment 1 mirh 2020-01-12 13:28:32 CET
Created attachment 9375 
Xfwm4 debug log

After compiling a debug build, I got this.
Comment 2 Olivier Fourdan editbugs 2020-01-14 10:42:37 CET
> Now, putting aside that I wouldn't really know whether that would result in better results than
> Xpresent or not
NVidia close source driver does not support Xpresent as far as I know, so you would get tearing with Xpresent with that driver.

> So long story short GLX is not working. 
Most likely a GL error indeed (which doesn't show in debug logs). I unfortunately do not have the hardware to test.

> After giving a quick look at the source code, one wonder that came to my mind is whether, being
> this hardware limited to GL 2.1 (and you not using any shader/glsl), you aren't just forgetting to
> call glEnable(GL_TEXTURE_2D) on init.
Plausible, since you know how to build from source, best would be for you to try and post a patch if that works, that would be great!
Comment 3 mirh 2020-01-14 13:20:48 CET
I mean, I know how to build
But for the dear love of me I wouldn't know where (and how) to throw instructions at

And for the records, it doesn't really seem like I'm getting tearing.
Comment 4 Git Bot editbugs 2020-05-29 12:33:43 CEST
-- GitLab Migration Automatic Message --

This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/xfwm4/-/issues/371.

Please create an account or use an existing account on one of our supported OAuth providers. 

If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests

Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev

Bug #16367

Reported by:
mirh
Reported on: 2020-01-10
Last modified on: 2020-05-29

People

Assignee:
Olivier Fourdan
CC List:
0 users

Version

Version:
4.13.2

Attachments

Glxinfo (8.58 KB, text/plain)
2020-01-10 20:42 CET , mirh
no flags
Xfwm4 debug log (5.75 KB, application/octet-stream)
2020-01-12 13:28 CET , mirh
no flags

Additional information