[Ubuntu-x-swat] [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-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1523088

Title:
  WARN_ON(!wm_changed) warning and stacktrace in kernel log

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1523088/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1242572

Title:
  xkeyboard-config, console-setup, and ubiquity should use Super+Space
  for switching keyboard layouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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 the 'stuck button' bug.

Modifying qt to listen to touch events on the master fixes it and
removes the need for the XIGrabDevice call. The grab was originally done
to prevent pointer emulation events, but these won't get generated when
we listen for touch events on the master, solving both problems.

But this is still a bug in xorg-server, regardless. :)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1307701

Title:
  xserver mouse pointer emulation from touch breaks with QML app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1242572

Title:
  xkeyboard-config, console-setup, and ubiquity should use Super+Space
  for switching keyboard layouts

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1247607]

2013-11-09 Thread Bugs-i 
Oops, so gcc is broken here after all, look at this..

3860 nouveau_pushbuf_reloc:
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%rax,0x30(%rdi)
386d:   e8 3e ea ff ff  callq  22b0 pushbuf_krel
3872:   89 03   mov%eax,(%rbx)
3874:   5b  pop%rbx
3875:   c3  retq   

Source:

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);
}

gcc-4.8 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++;
*push-cur[-1] = pushbuf_krel(push, bo, data, flags, vor, tor);
}

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1247607]

2013-11-09 Thread Bugs-i 
Compiled code with this patch:

15b0 nouveau_pushbuf_reloc:
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 ff ff  callq  0 pushbuf_krel
15be:   89 45 00mov%eax,0x0(%rbp)
15c1:   48 83 43 30 04  addq   $0x4,0x30(%rbx)
15c6:   5b  pop%rbx
15c7:   5d  pop%rbp
15c8:   c3  retq   

Without:
1650 nouveau_pushbuf_reloc:
1650:   48 89 5c 24 f0  mov%rbx,-0x10(%rsp)
1655:   48 89 6c 24 f8  mov%rbp,-0x8(%rsp)
165a:   48 83 ec 10 sub$0x10,%rsp
165e:   48 8b 6f 30 mov0x30(%rdi),%rbp
1662:   48 89 fbmov%rdi,%rbx
1665:   e8 96 e9 ff ff  callq  0 pushbuf_krel
166a:   89 45 00mov%eax,0x0(%rbp)
166d:   48 83 c5 04 add$0x4,%rbp
1671:   48 89 6b 30 mov%rbp,0x30(%rbx)
1675:   48 8b 1c 24 mov(%rsp),%rbx
1679:   48 8b 6c 24 08  mov0x8(%rsp),%rbp
167e:   48 83 c4 10 add$0x10,%rsp
1682:   c3  retq   

It seems that the nouveau_pushbuf_reloc difference is harmless. Code is
equivalent, except that without the patch applied it uses another temp
variable causing less optimal code generation.

Remaining candidates: pushbuf_validate, nouveau_pushbuf_data,
nouveau_pushbuf_del.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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.

after resume from suspend to memory
[   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 mthd 0x0314 data 0x0051f000
(error repeats)

I can confirm that rebuilding only libdrm-nouveau2 with the raring
toolchain fixes it.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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 received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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 expert, so no idea if I'm right, but it seems the updated 
gcc-4.8 behavior is wrong here.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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 this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1247607

Title:
  Libdrm compiled with gcc 4.8 makes card hang on resume from s2disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1247607/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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 valgrind blows up, I get this:

Obtaining format for pixmap 0x1327d1f0 and picture 0x1cd457e0
==7989== Invalid read of size 4
==7989==at 0x8CAA0CA: glamor_get_tex_format_type_from_pixmap 
(glamor_utils.h:1252)
==7989==by 0x8CAD1B7: glamor_download_sub_pixmap_to_cpu 
(glamor_pixmap.c:1074)
==7989==by 0x8CA8BB7: _glamor_get_image (glamor_getimage.c:66)
==7989==by 0x8CA8D2F: glamor_get_image (glamor_getimage.c:92)
==7989==by 0x29AEF2: miSpriteGetImage (misprite.c:413)
==7989==by 0x1E7674: compGetImage (compinit.c:148)
==7989==by 0x1F5E5B: ProcShmGetImage (shm.c:684)
==7989==by 0x1F686F: ProcShmDispatch (shm.c:1121)
==7989==by 0x15D00D: Dispatch (dispatch.c:432)
==7989==by 0x14C569: main (main.c:298)
==7989==  Address 0x1cd457f0 is 16 bytes inside a block of size 120 free'd
==7989==at 0x4C2B60C: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7989==by 0x228897: FreePicture (picture.c:1477)
==7989==by 0x228B23: PictureDestroyWindow (picture.c:73)
==7989==by 0x234C19: damageDestroyWindow (damage.c:1646)
==7989==by 0x1E92C0: compDestroyWindow (compwindow.c:590)
==7989==by 0x20FF85: DbeDestroyWindow (dbe.c:1389)
==7989==by 0x185D46: FreeWindowResources (window.c:907)
==7989==by 0x1889A7: DeleteWindow (window.c:975)
==7989==by 0x17EBF1: doFreeResource (resource.c:873)
==7989==by 0x17FC1B: FreeClientResources (resource.c:1139)
==7989==by 0x15C4DE: CloseDownClient (dispatch.c:3402)
==7989==by 0x2AB843: CheckConnections (connection.c:1008)
==7989== 
(II) fail to get matched format for dfdfdfdf 

I guess the method of obtaining pixmap from a window drawable may result
in not always returning the same pixmap, causing this bug...

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to glamor-egl in Ubuntu.
https://bugs.launchpad.net/bugs/1244324

Title:
  glamor-egl crashes when running autopilot tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/glamor/+bug/1244324/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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-X,
which is subscribed to glamor-egl in Ubuntu.
https://bugs.launchpad.net/bugs/1244324

Title:
  glamor-egl crashes when running autopilot tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/glamor/+bug/1244324/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [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-X,
which is subscribed to libxrandr in Ubuntu.
https://bugs.launchpad.net/bugs/985202

Title:
  libx11 causes kwin to crash on login (over NX protocol)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/985202/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp