[Bug 1840236]

2019-09-14 Thread Bugs-i
Likely identical, especially if disabling fbc from command line works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840236 Title: Horizontal corrupted line at top of screen caused by framebuffer

[Bug 1785912]

2019-05-30 Thread Bugs-i
Oh well, worth a shot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785912 Title: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV To manage notification

[Bug 1785912]

2019-05-28 Thread Bugs-i
Working (fastset at boot): [3.494890] [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m: 6213395, gmch_n: 8388608, link_m: 517782, link_n: 524288, tu: 64 Broken (modeset): [ 192.531640] [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m: 6213395, gmch_n: 8388608, link_m

[Bug 1523088]

2015-12-19 Thread Bugs-i
You're missing the error lines before the pipe state mismatch. Also looks like a separate bug.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523088 Title: WARN_ON(!wm_changed) warning and stacktra

[Bug 1307701]

2014-05-09 Thread Bugs-i
Created attachment 98694 xorg-integration-tests testcase try 2 Ok so I've finally isolated the problem. The problem is the XIGrabDevice on the slave pointer, which is only removed after the touch ends. When this happens the ButtonRelease call for pointer emulation is never generated, leading to th

[Bug 1242572]

2014-05-09 Thread Bugs-i
Created attachment 98456 Missing PC_SUPER_LEVEL2 definition. It looks like the PC_SUPER_LEVEL2 definition is missing from the commit, I've attached it as diff. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net

[Bug 1242572]

2014-05-01 Thread Bugs-i
Created attachment 98299 add grp:win_space_toggle to allow meta keys to switch keyboard layout I've attached my patch. But I have no clue about xkb-data, so I don't know if it's correct or not. Could this be reviewed? -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1197921]

2013-11-21 Thread Bugs-i
Fixed in commit 2f876cf86718d3dd9b3b04ae9552530edafe58a1 in pixman. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197921 Title: LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing e

[Bug 1247607]

2013-11-09 Thread Bugs-i
Well, pedantically gcc-4.7 behavior is this: u32 *ptr = push->cur; *ptr = func(); push->cur++; But since func only reads push->cur it's the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247607

[Bug 1247607]

2013-11-09 Thread Bugs-i
http://cgit.freedesktop.org/mesa/drm/commit/?id=482abbfafb56cbceaf5355c026434e638cddd0f1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247607 Title: Libdrm compiled with gcc 4.8 makes card hang on

[Bug 1247607]

2013-11-09 Thread Bugs-i
Because the function also increments the push->cur pointer, it's a subtle but real difference: gcc-4.7: u32 ret = func(); // May change push->cur ptr *push->cur = ret; push->cur++; gcc-4.8: u32 *ptr = push->cur; push->cur++; *ptr = func(); // Already sees the push->cur ptr I'm not a language

[Bug 1247607]

2013-11-09 Thread Bugs-i
Created attachment 88817 hack to force defined behavior As I feared, recompiling only pushbuf.c with gcc-4.7 fixes this bug. So something in pushbuf.c is miscompiled. Unfortunately it's also the biggest abuser of post increment ops. A simple workaround seems to be this patch. -- You received th

[Bug 1247607]

2013-11-09 Thread Bugs-i
while gcc-4.7 evaluates it as: void nouveau_pushbuf_reloc(struct nouveau_pushbuf *push, struct nouveau_bo *bo, uint32_t data, uint32_t flags, uint32_t vor, uint32_t tor) { *push->cur = pushbuf_krel(push, bo, data, flags, vor, tor); push->cur++; } -- You rece

[Bug 1247607]

2013-11-09 Thread Bugs-i
Oops, so gcc is broken here after all, look at this.. 3860 : 3860: 53 push %rbx 3861: 48 8b 5f 30 mov0x30(%rdi),%rbx 3865: 48 8d 43 04 lea0x4(%rbx),%rax 3869: 48 89 47 30 mov%

[Bug 1247607]

2013-11-09 Thread Bugs-i
Compiled code with this patch: 15b0 : 15b0: 55 push %rbp 15b1: 48 8b 6f 30 mov0x30(%rdi),%rbp 15b5: 53 push %rbx 15b6: 48 89 fbmov%rdi,%rbx 15b9: e8 42 ea

[Bug 1247607]

2013-11-09 Thread Bugs-i
Wow this is definitely a weird interesting bug. It affects suspend-to-mem on my pci-e nv43 too. [ 40.107810] nouveau E[ PGRAPH][:01:00.0] ERROR nsource: DATA_ERROR nstatus: BAD_ARGUMENT [ 40.108059] nouveau E[ PGRAPH][:01:00.0] ch 3 [0x000f7000 compiz[1713]] subc 2 class 0x0039

[Bug 1244324]

2013-11-06 Thread Bugs-i
Created attachment 88619 fixup picture in SetWindowPixmap I found a fix, if I update the pixmap in SetWindowPixmap the testcase doesn't crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244324 Ti

[Bug 1244324]

2013-11-06 Thread Bugs-i
Some more poking, it seems someone is changing drawable around.. create picture 0x1cd457e0, with drawable 0x1327d1f0 (some log spam removed, involving correct picture and drawable) destroy picture 0x1cd457e0, with drawable 0x1cd65820 and private 0x1cd658e0 0 (nil) Then finally, at the end when v

[Bug 985202]

2013-08-30 Thread Bugs-i
Seems to be fixed by commit 4e4bbb85499cff052ce03e173b88f1083ba83f86 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985202 Title: libx11 causes kwin to crash on login (over NX protocol) To manage no

[Bug 235602]

2012-08-06 Thread Libreoffice-bugs-i
(In reply to comment #8) > I understand the why now, but I fear that the average user will not understand > this. In his/her view the conditional formatting of cell(s) is damaged when > inserting row(s)/column(s). I must be the average user you mention, because I'm afraid that the current behavio