http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #714694|text/x-rpm-spec |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c7 Dieter Jurzitza changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dieter.jurzitza@t | |-online.de) | --- Comment #7 from Dieter Jurzitza --- Hello, isn't this https://lists.x.org/archives/xorg-devel/2016-August/050713.html what you are asking for? I can work only empirically. I had tgif on the whole day now, working continuously on a drawing - and I had no more issues. Last week was a horror compared to this. Ž I do not know whether this "plaster" is kind of wrong, this needs someone with much more experience regarding C - programming language and xorg - sources. But I can tell that the stability of _my_ leap 42.2 has significantly increased. My two cents, thank you for looking into this, regards Dieter Jurzitza -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c9 Dieter Jurzitza changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dieter.jurzitza@t | |-online.de) | --- Comment #9 from Dieter Jurzitza --- Please take a look to #2 and #3. The patch against glamor_dash.c stems from me and fixes the problems I observed with tgif. The other patch stems from Michel Dänzer, the corresponding discussion is shown in the link I posted this morning (#7). I wrote an email to xorg-devel saying that there is a problem on Friday (parallel to opening this bug, as readily stated). I had no solution at that time. Yesterday I found the solution (IMHO) by patchnig glamor_dash.c and posted this as well. Moreover I prepared a patch against the latest xserver from openSUSE leap 42.2, attached to this report. So far no one replied to my posts on xorg-devel, however, it has not been a long time since the posts can be found on the mailing list. According to the suggestion of Michel Dänzer I forwarded the email to Mr. Anholt as well, that's about all I can do. Hope this clarifies things, regards Dieter Jurzitza -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c11 --- Comment #11 from Marcus Meissner --- I see on in OBS graphics/tgif -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c13 Max Staudt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS CC| |mstaudt@suse.com --- Comment #13 from Max Staudt --- Dieter, thank you for identifying a potential solution and for posting it to [xorg-devel] for upstream discussion, great work! For everyone's reference, here is the thread concerning hunk #1 of your patch: https://lists.x.org/archives/xorg-devel/2017-February/052774.html In general, we try to wait for upstream to validate a patch before backporting it. Since you've already rebuilt Xorg with your patch, I suppose we can wait for a few more days. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c15 --- Comment #15 from Dieter Jurzitza --- Hello folks, I will not send any more reports upstream. So, if someone volunteers for playing the upstream game, feel free to post the bug report in a shape being accepted there. I am out of that business. Dieter Jurzitza -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c17 --- Comment #17 from Dieter Jurzitza --- Hello Max, I didn't talk about upstream 1.19 xorg. I have been discussing "downstream" 1.18.1 xorg as distributed with leap 42.2. There my patch definitively fixes the bug and I haven't seen any "odd" results since then, making heavy usage of tgif (with many dashed lines as I use this program to create technical drawings). I cannot comment on 1.19 and never intended to do so. I was aiming to find a plaster for my problem what could potentially hurt others, too. If you are to say that you can crash 1.18.1 as distributed with leap 42.2 this way, then I would have to look again - I was not able to. If 1.19 is crashing with tgif and this bug applied then there are still other things going wrong - would be interesting to see what is actually written into Xorg.0.log in this case - because the initial error "pos undeclared" cannot be an issue any more because it is definitively declared given that the patch is applied. My two cents Dieter Jurzitza -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c19 --- Comment #19 from Stefan Dirsch --- Dieter, I was also using your patch on top of Xserver patches for openSUSE 42.2, i.e. xserver 1.18.1. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c21 --- Comment #21 from Dieter Jurzitza --- Hello Stefan, hello Max, well, then there is an additional 1.19 - issue someone has to look at that differs from the problem showing with 1.18.1 (and I consider this to happen "prior" to the "'pos' undeclared problem", as the address remains stable with and without the patch). This is apparent to me not only because of Stefan and I are having the same findings but because your failures show at identical positions, the adresses you published in #16 are identical (apart from the final "^" what appears to be a typo (?) to me ....) Regards Dieter -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c23 --- Comment #23 from Dieter Jurzitza --- Well, ... and the erratic snipplets of code were introduced in a format that is honoured with attention on xorg-devel ... IMHO it would be an improvement for now to apply the patch I posted including the patch from Michel on 42.2 as both of them appear to reduce the risc for crashes for *this specific* version. What regards "upstream" there is a need for someone having both the knowledge and the time to really look into the problem and find a solution. If something towards the right direction shows requesting a moderate change in 1.18.1 let me know, I am more than willing to test. I will not update since I depend on my system for my daily work - expecially tgif is a must for me :-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 Max Staudt changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=97300, | |https://bugs.freedesktop.or | |g/show_bug.cgi?id=99943, | |https://bugs.freedesktop.or | |g/show_bug.cgi?id=100039 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c26 --- Comment #26 from Max Staudt --- Dieter, could you please try this X server for Leap 42.2? https://build.opensuse.org/package/show/home:mstaudt:1021803boo-glamor-xdraw... There, I have disabled the GLAMOR acceleration that draws your 0-width lines in unexpected ways. If you have any comments on performance, I would greatly appreciate them, too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c28 --- Comment #28 from Max Staudt --- Whoops, I forgot to publish the build. You can now install the new X server as follows: sudo zypper ar https://download.opensuse.org/repositories/home:/mstaudt:/1021803boo-glamor-... sudo zypper refresh sudo zypper dup Once you're done testing: sudo zypper removerepo home_mstaudt_1021803boo-glamor-xdrawline sudo zypper refresh sudo zypper dup -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c30 --- Comment #30 from Max Staudt --- Great, looking forward to your feedback! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c32 --- Comment #32 from Dieter Jurzitza --- Hello Max, sorry for the late reply, I simply did not find the time to work that much with tgif as I had had wanted to. Nevertheless I could not realize one single problem when working with tgif since I switched to the server you provided recently, so, from my point of view it is ok to use this one. Even loading / modifying the crashx11.obj file has no consequences. Dieter Jurzitza -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1025985 http://bugzilla.opensuse.org/show_bug.cgi?id=1025985#c35 --- Comment #35 from Max Staudt --- The wrong dashing in GLAMOR is now resolved. See boo#1021803. -- You are receiving this mail because: You are on the CC list for the bug.