[Ubuntu-x-swat] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()

2020-05-26 Thread El jinete sin cabeza
** Tags added: groovy

-- 
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/1543192

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("no screens found") from dix_main()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for zw

2020-05-23 Thread El jinete sin cabeza
** Tags added: groovy

-- 
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/1746656

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log() ["wl_display@1:
  error 1: invalid arguments for
  zwp_relative_pointer_manager_v1@15.get_relative_pointer\n"]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746656/+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 1874262] Re: User session does not start: Problem with chrome-remote-desktop

2020-04-22 Thread El jinete sin cabeza
** Summary changed:

- User session does not start: xkbcomp "Internal error: Could not resolve 
keysym Invalid"
+ User session does not start: Problem with chrome-remote-desktop

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

Title:
  User session does not start: Problem with chrome-remote-desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+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 1874262] Re: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"

2020-04-22 Thread El jinete sin cabeza
https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14

** Also affects: xorg (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gdm3 (Ubuntu)
   Status: New => Invalid

** Description changed:

+ https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593
  
  ---
  
  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm and
  to be able to enter.
  
  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server
  
  Attached log of the attempt to log in.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Bug watch added: gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues #14
   https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14

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

Title:
  User session does not start: xkbcomp "Internal error: Could not
  resolve keysym Invalid"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+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 1865144] Re: Characters in Spanish in the web browser do not work correctly

2020-02-29 Thread El jinete sin cabeza
I just updated the package x11-xkb-utils (7.7+4) to 7.7+5, and I have
restarted Ubuntu 20.04(development). After this, the character encoding
works correctly in Firefox and Chrome.

** Also affects: x11-xkb-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: x11-xkb-utils (Ubuntu)
   Status: New => Fix Released

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  Characters in Spanish in the web browser do not work correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1865144/+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 1797820] Re: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_c

2019-12-19 Thread El jinete sin cabeza
** Tags added: focal

-- 
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/1797820

Title:
  Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture →
  glamor_set_composite_texture → glamor_composite_set_shader_blend →
  glamor_composite_with_shader → glamor_composite_clipped_region

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1797820/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()

2019-12-17 Thread El jinete sin cabeza
** Tags added: focal

-- 
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/1543192

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("no screens found") from dix_main()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1839545] [NEW] Graphic environment slows down and then returns to normal

2019-08-08 Thread El jinete sin cabeza
Private bug reported:

After updating the mesa, the management of my graphic environment is no
longer as fluid.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libegl-mesa0 19.1.4-1ubuntu1
Uname: Linux 5.2.7-050207-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  8 16:46:39 2019
DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.10, 5.2.7-050207-generic, x86_64: installed
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
InstallationDate: Installed on 2018-12-02 (249 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.7-050207-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: Upgraded to eoan on 2018-12-02 (249 days ago)
dmi.bios.date: 04/29/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.34
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.1.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan regression single-occurrence ubuntu 
wayland-session

** Information type changed from Public to Private

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

Title:
  Graphic environment slows down and then returns to normal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1839545/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()

2019-07-06 Thread El jinete sin cabeza
** Tags added: eoan

-- 
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/1543192

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("no screens found") from dix_main()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for zw

2019-06-14 Thread El jinete sin cabeza
** Tags added: eoan

-- 
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/1746656

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler() from wl_log() ["wl_display@1:
  error 1: invalid arguments for
  zwp_relative_pointer_manager_v1@15.get_relative_pointer\n"]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746656/+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 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()

2019-06-12 Thread El jinete sin cabeza
** Tags added: eoan

-- 
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/1751508

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("Couldn't add screen\n") from InitOutput()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1751508/+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 1797820] Re: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_c

2019-06-10 Thread El jinete sin cabeza
Maybe this update corriga this error:

xorg-server: 1.20.5

https://lists.x.org/archives/xorg-announce/2019-May/002993.html

-- 
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/1797820

Title:
  Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture →
  glamor_set_composite_texture → glamor_composite_set_shader_blend →
  glamor_composite_with_shader → glamor_composite_clipped_region

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1797820/+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 1797820] Re: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_c

2019-06-10 Thread El jinete sin cabeza
** Tags added: eoan

-- 
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/1797820

Title:
  Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture →
  glamor_set_composite_texture → glamor_composite_set_shader_blend →
  glamor_composite_with_shader → glamor_composite_clipped_region

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1797820/+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 1546541] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from CreateWellKnownSockets()

2019-06-06 Thread El jinete sin cabeza
** Tags added: eoan

-- 
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/1546541

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from CreateWellKnownSockets()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1546541/+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 1731261] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler(msg="Error sending request: Broken pipe\n...")

2019-06-03 Thread El jinete sin cabeza
** Tags added: eoan

-- 
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/1731261

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler(msg="Error sending request: Broken
  pipe\n...")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731261/+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 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()

2019-05-30 Thread El jinete sin cabeza
New xorg publication corrects this bug:
https://lists.x.org/archives/xorg-announce/2019-May/002993.html

-- 
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/1821385

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy() from
  wl_callback_destroy() from xwl_present_sync_callback() from
  ffi_call_unix64()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1821385/+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 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()

2019-05-23 Thread El jinete sin cabeza
The shock was brutal, all my applications were closed. And then GDM
appears.

-- 
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/1821385

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy() from
  wl_callback_destroy() from xwl_present_sync_callback() from
  ffi_call_unix64()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1821385/+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 1830264] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy()

2019-05-23 Thread El jinete sin cabeza
*** This bug is a duplicate of bug 1821385 ***
https://bugs.launchpad.net/bugs/1821385

** Description changed:

- I was moving tabs on google chrome.
+ I was moving tabs on chrome.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: xwayland 2:1.20.4-1ubuntu3
  Uname: Linux 5.1.4-050104-generic x86_64
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 23 13:33:49 2019
  DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.8, 5.1.4-050104-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
-  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
+  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
  InstallationDate: Installed on 2018-12-02 (171 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcEnviron:
-  LANGUAGE=es_CL:es
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=es_CL.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=es_CL:es
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=es_CL.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.1.4-050104-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
-  ?? ()
-  ffi_call_unix64 () at ../src/x86/unix64.S:76
-  ffi_call (cif=, fn=, rvalue=, 
avalue=) at ../src/x86/ffi64.c:525
-  ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
+  wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
+  ?? ()
+  ffi_call_unix64 () at ../src/x86/unix64.S:76
+  ffi_call (cif=, fn=, rvalue=, 
avalue=) at ../src/x86/ffi64.c:525
+  ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in wl_proxy_destroy()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (171 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:
-  
+ 
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

-- 
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/1830264

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1830264/+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 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** Project changed: totem => gstreamer

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+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 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

** Description changed:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---
  
  I.e. bug is in what is given to Mesa, not what Mesa does.
  
  -> NOTOURBUG
  
  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** No longer affects: gstreamer

** Also affects: totem via
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
   Importance: Unknown
   Status: Unknown

** Description changed:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE 
OF:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
+ 
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
    

[Ubuntu-x-swat] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** No longer affects: mesa

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+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 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** Changed in: totem (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+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 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #153
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153

** Also affects: gstreamer via
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
   Importance: Unknown
   Status: Unknown

** Description changed:

+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
-if (gc) {
-   /* Attempt to bind the context.  We do this before mucking with
-* gc and __glXSetCurrentContext to properly handle our state in
-* case of an error.
-*
-* If an error occurs, set the Null context since we've already
-* blown away our old context.  The caller is responsible for
-* figuring out how to handle setting a valid context.
-*/
-   if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
-  __glXSetCurrentContextNull();
-  __glXUnlock();
-  __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
- False);
-  return GL_FALSE;
-   }
+    if (gc) {
+   /* Attempt to bind the context.  We do this before mucking with
+    * gc and __glXSetCurrentContext to properly handle our state in
+    * case of an error.
+    *
+    * If an error occurs, set the Null context since we've already
+    * blown away our old context.  The caller is responsible for
+    * figuring out how to handle setting a valid context.
+    */
+   if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+  __glXSetCurrentContextNull();
+  __glXUnlock();
+  __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+  return GL_FALSE;
+   }
  ---
  
  I.e. bug is in what is given to Mesa, not what Mesa does.
  
  -> NOTOURBUG
  
- 
- To me it looks something that could happen when Totem is exiting, gst-vaapi 
is trying to use resources that have already been freed, and X catching that 
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do 
CommonMakeCurrent().
+ To me it looks something that could happen when Totem is exiting, gst-
+ vaapi is trying to use resources that have already been freed, and X
+ catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
+ ask libglvnd to do CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+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 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** Changed in: mesa (Ubuntu)
   Status: New => Invalid

** Description changed:

- https://bugs.freedesktop.org/show_bug.cgi?id=110452
+ https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  totem crashed with signal 5
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
- totem crashed with signal 5
+ Backtrace goes through:
+ 
+ totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
+ (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
+ (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
+ (MakeContextCurrent) -> Xlib (XError)
+ 
+ Ubuntu bug doesn't say anything about what's the use-case / when this
+ happens and whether it's reproducible (is it e.g. timing related), it
+ seems just some random crash that Apport collects.
+ 
+ In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
+ ---
+if (gc) {
+   /* Attempt to bind the context.  We do this before mucking with
+* gc and __glXSetCurrentContext to properly handle our state in
+* case of an error.
+*
+* If an error occurs, set the Null context since we've already
+* blown away our old context.  The caller is responsible for
+* figuring out how to handle setting a valid context.
+*/
+   if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+  __glXSetCurrentContextNull();
+  __glXUnlock();
+  __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+  return GL_FALSE;
+   }
+ ---
+ 
+ I.e. bug is in what is given to Mesa, not what Mesa does.
+ 
+ -> NOTOURBUG
+ 
+ 
+ To me it looks something that could happen when Totem is exiting, gst-vaapi 
is trying to use resources that have already been freed, and X catching that 
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do 
CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Also affects: gstreamer (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gstreamer (Ubuntu)

** Also affects: gstreamer-vaapi (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat

[Ubuntu-x-swat] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-16 Thread El jinete sin cabeza
https://bugs.freedesktop.org/show_bug.cgi?id=110452

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: freedesktop.org Bugzilla #110452
   https://bugs.freedesktop.org/show_bug.cgi?id=110452

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=110452
   Importance: Unknown
   Status: Unknown

** Description changed:

  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
+ 
+ ---
+ 
+ https://bugs.freedesktop.org/show_bug.cgi?id=110452
  
  ---
  
  totem crashed with signal 5
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

+ https://bugs.freedesktop.org/show_bug.cgi?id=110452
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
- 
- ---
- 
- https://bugs.freedesktop.org/show_bug.cgi?id=110452
  
  ---
  
  totem crashed with signal 5
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1758287/+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 1822092] [NEW] FFe: Mesa 19.0.1 for disco

2019-03-28 Thread El jinete sin cabeza
Public bug reported:

Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0
release.

Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
used. Some drivers don't support all the features required in OpenGL
4.5. OpenGL 4.5 is only available if requested at context creation.
Compatibility contexts may report a lower version depending on each
driver.

https://www.mesa3d.org/relnotes/19.0.1.html

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0
  release.
  
  Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
  glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
  glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being
  used. Some drivers don't support all the features required in OpenGL
  4.5. OpenGL 4.5 is only available if requested at context creation.
  Compatibility contexts may report a lower version depending on each
  driver.
+ 
+ https://www.mesa3d.org/relnotes/19.0.1.html

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

Title:
  FFe: Mesa 19.0.1 for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1822092/+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 1818862] Re: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]

2019-03-25 Thread El jinete sin cabeza
See LP: #1821525

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

Title:
  Totem player hangs when seeking video due to [gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]

To manage notifications about this bug go to:
https://bugs.launchpad.net/libva/+bug/1818862/+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 1818862] Re: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]

2019-03-25 Thread El jinete sin cabeza
See LP:#1821525

** Tags added: disco

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

Title:
  Totem player hangs when seeking video due to [gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]

To manage notifications about this bug go to:
https://bugs.launchpad.net/libva/+bug/1818862/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-25 Thread El jinete sin cabeza
See LP: #1818862

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-25 Thread El jinete sin cabeza
** No longer affects: totem

** No longer affects: mesa

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-25 Thread El jinete sin cabeza
** Changed in: mesa (Ubuntu)
   Status: New => Invalid

** Description changed:

  https://github.com/intel/intel-vaapi-driver/issues/451
- https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
  
  ---
  
  Watching movie 4k, forward and back.
- 
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-24 Thread El jinete sin cabeza
** Description changed:

  https://github.com/intel/intel-vaapi-driver/issues/451
  https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
  
  ---
  
- Watching movie 4k.
+ Watching movie 4k, forward and back.
+ 
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-24 Thread El jinete sin cabeza
** Description changed:

+ https://github.com/intel/intel-vaapi-driver/issues/451
  https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
  https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
  
  ---
  
  Watching movie 4k.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-24 Thread El jinete sin cabeza
** Description changed:

- https://gitlab.gnome.org/GNOME/totem/issues/315
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://gitlab.gnome.org/GNOME/totem/issues/315 (Not totem)
  
  ---
  
  Watching movie 4k.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: freedesktop.org Bugzilla #110232
   https://bugs.freedesktop.org/show_bug.cgi?id=110232

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=110232
   Importance: Unknown
   Status: Unknown

** Changed in: totem (Ubuntu)
   Status: New => Invalid

** Description changed:

  https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
- https://gitlab.gnome.org/GNOME/totem/issues/315 (Not totem)
+ https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
  
  ---
  
  Watching movie 4k.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  Uname: Linux 5.0.4-050004-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 24 11:18:37 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (111 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", 
file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 
"gen9_mfd.c", line=649, function=0x7f06b29b23e0 
"gen9_hcpd_get_reference_picture_frame_id") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2
  Title: totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-24 Thread El jinete sin cabeza
** Summary changed:

- totem assert failure: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
+ totem assert failure: totem: totem: gen9_mfd.c:649: 
gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

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

Title:
  totem assert failure: totem: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/1821525/+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 1821525] Re: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.

2019-03-24 Thread El jinete sin cabeza
** Also affects: intel-vaapi-driver (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  totem assert failure: totem: gen9_mfd.c:649:
  gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se
  cumple.

To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/1821525/+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 1821318] Re: FFe: Wayland 1.17 for disco

2019-03-23 Thread El jinete sin cabeza
Sorry.

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

Title:
  FFe: Wayland 1.17 for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+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 1821318] Re: FFe: Wayland 1.17 for disco

2019-03-23 Thread El jinete sin cabeza
ok I understand.

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

Title:
  FFe: Wayland 1.17 for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+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 1821318] Re: FFe: Wayland 1.17 for disco

2019-03-23 Thread El jinete sin cabeza
@Timo:

And for publicity?

Ubuntu 19.04 works with:
* Kernel 5
* GNOME 3.32
* Wayland 1.17

Not everything is technical. Big Boss...

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

Title:
  FFe: Wayland 1.17 for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+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 1821318] Re: FFe: Wayland 1.17 for disco

2019-03-23 Thread El jinete sin cabeza
@Timo:

And for publicity?

Ubuntu 19.04 works with:
Kernel 5
GNOME 3.32
Wayland 1.17

Not everything is technical. Big Boss,,,

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

Title:
  FFe: Wayland 1.17 for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+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 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy()

2019-03-22 Thread El jinete sin cabeza
** Description changed:

- https://bugzilla.freedesktop.org/show_bug.cgi?id=110226
+ https://gitlab.freedesktop.org/wayland/wayland/issues/85
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110226 (Moved to 
gitlab.freedesktop.org)
  
  ---
  
  I do not know what happened.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: xwayland 2:1.20.4-1ubuntu2
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 10:31:56 2019
  DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.19.30-041930-generic, x86_64: 
installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-7-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-8-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.3-050003-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1552033916
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
  InstallationDate: Installed on 2018-12-02 (109 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcCwd: /home/caravena
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.3-050003-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  UpgradeStatus: Upgraded to disco on 2018-12-02 (109 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:
  
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** No longer affects: xorg-server

-- 
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/1821385

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821385/+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 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy()

2019-03-22 Thread El jinete sin cabeza
** Bug watch added: freedesktop.org Bugzilla #110226
   https://bugs.freedesktop.org/show_bug.cgi?id=110226

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=110226
   Importance: Unknown
   Status: Unknown

** Description changed:

+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110226
+ 
+ ---
+ 
  I do not know what happened.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: xwayland 2:1.20.4-1ubuntu2
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 10:31:56 2019
  DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
-  rtl8812au, 4.3.8.12175.20140902+dfsg, 4.19.30-041930-generic, x86_64: 
installed
-  rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-7-generic, x86_64: installed
-  rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-8-generic, x86_64: installed
-  rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.3-050003-generic, x86_64: installed
+  rtl8812au, 4.3.8.12175.20140902+dfsg, 4.19.30-041930-generic, x86_64: 
installed
+  rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-7-generic, x86_64: installed
+  rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.0-8-generic, x86_64: installed
+  rtl8812au, 4.3.8.12175.20140902+dfsg, 5.0.3-050003-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1552033916
  GraphicsCard:
-  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
+  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
  InstallationDate: Installed on 2018-12-02 (109 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcCwd: /home/caravena
  ProcEnviron:
-  LANGUAGE=es_CL:es
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=es_CL.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=es_CL:es
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=es_CL.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.3-050003-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
-  ?? ()
-  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
+  wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
+  ?? ()
+  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  UpgradeStatus: Upgraded to disco on 2018-12-02 (109 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:
-  
+ 
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

-- 
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/1821385

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy()

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : 

[Ubuntu-x-swat] [Bug 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy()

2019-03-22 Thread El jinete sin cabeza
** Information type changed from Private to Public

-- 
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/1821385

Title:
  Xwayland crashed with SIGABRT in wl_proxy_destroy()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1821385/+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 1821318] Re: FFe: Wayland 1.17 for disco

2019-03-22 Thread El jinete sin cabeza
> Is there anything that's useful for disco?
> I don't see it.

August 24, 2018 -> Wayland 1.16
March 20, 2019 -> Wayland 1.17

~6.8 months of work.

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

Title:
  FFe: Wayland 1.17 for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+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 1821318] [NEW] FFe: Wayland 1.17 for disco

2019-03-22 Thread El jinete sin cabeza
Public bug reported:

https://wayland.freedesktop.org/releases.html
https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html

---

Please upload the new version of Wayland (1.17) published on March 20,
2019, as it is complementary in the graphic, if there are usability
problems you can stop using changing the configuration in GDM3. From
Wayland to Xorg.

** Affects: wayland (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 disco wayland-session

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

Title:
  FFe: Wayland 1.17 for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+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 1818516] Re: FFe: Mesa 19.0.x for disco

2019-03-14 Thread El jinete sin cabeza
@Timo

1) Close LP: #1819277
2) For me, this new version of 'mesa' works well

Thanks!

** Attachment added: "$ dpkg -l | grep mesa | grep 19"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+attachment/5246287/+files/mesa_19.0.0-1ubuntu1.txt

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

Title:
  FFe: Mesa 19.0.x for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1819277] Re: I see stripes plomas in full screen mode

2019-03-14 Thread El jinete sin cabeza
mesa (19.0.0-1ubuntu1) disco; urgency=medium

  * Merge from Debian. (LP: #1818516)
  * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889)

 -- Timo Aaltonen   Thu, 14 Mar 2019 18:48:18 +0200

** Changed in: mesa (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  I see stripes plomas in full screen mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+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 1818516] Re: FFe: Mesa 19.0.x for disco

2019-03-12 Thread El jinete sin cabeza
@lain:

https://bugs.freedesktop.org/show_bug.cgi?id=109535

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

Title:
  FFe: Mesa 19.0.x for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1818516] Re: FFe: Mesa 19.0.x for disco

2019-03-12 Thread El jinete sin cabeza
@laney:

https://bugs.freedesktop.org/show_bug.cgi?id=109535

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

Title:
  FFe: Mesa 19.0.x for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1818516] Re: FFe: Mesa 19.0.x for disco

2019-03-12 Thread El jinete sin cabeza
@Iain:

https://bugs.freedesktop.org/show_bug.cgi?id=109535

** Bug watch added: freedesktop.org Bugzilla #109535
   https://bugs.freedesktop.org/show_bug.cgi?id=109535

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

Title:
  FFe: Mesa 19.0.x for disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-03-11 Thread El jinete sin cabeza
I am looking for if the patch was included before the release of mesa
"19.0.0-rc7"

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815236/+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 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-03-11 Thread El jinete sin cabeza
They could pass to [1]mesa_19.0.0~rc7
[1] 
https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_19.0.0~rc7-1_changelog

https://bugs.freedesktop.org/show_bug.cgi?id=109535
The error is corrected in master.

** Bug watch added: freedesktop.org Bugzilla #109535
   https://bugs.freedesktop.org/show_bug.cgi?id=109535

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815236/+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 1819277] Re: I see stripes plomas in full screen mode

2019-03-09 Thread El jinete sin cabeza
https://gitlab.gnome.org/GNOME/totem/issues/307#note_455803

"Bug in mesa, duplicate of #264 (closed)"

** Description changed:

  https://gitlab.gnome.org/GNOME/totem/issues/307
  
  ---
  
  When I open a movie in totem, it looks like a window. But then I enlarge
  it to full screen. It is seen in the lower part, a strip of lead.
  
  Attached screenshot image.
+ 
+ The problem occurs with wayland, in xorg it looks good.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 12:12:52 2019
  InstallationDate: Installed on 2018-12-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: totem
  UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago)

** No longer affects: wayland (Ubuntu)

** Changed in: totem (Ubuntu)
   Status: New => Invalid

** Description changed:

  https://gitlab.gnome.org/GNOME/totem/issues/307
  
  ---
  
  When I open a movie in totem, it looks like a window. But then I enlarge
  it to full screen. It is seen in the lower part, a strip of lead.
  
  Attached screenshot image.
  
- The problem occurs with wayland, in xorg it looks good.
+ The problem occurs with wayland, in Xorg it looks good.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 12:12:52 2019
  InstallationDate: Installed on 2018-12-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: totem
  UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago)

** Changed in: mesa (Ubuntu)
   Status: New => Confirmed

** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #307
   https://gitlab.gnome.org/GNOME/totem/issues/307

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

Title:
  I see stripes plomas in full screen mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+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 1819277] [NEW] I see stripes plomas in full screen mode

2019-03-09 Thread El jinete sin cabeza
Public bug reported:

https://gitlab.gnome.org/GNOME/totem/issues/307

---

When I open a movie in totem, it looks like a window. But then I enlarge
it to full screen. It is seen in the lower part, a strip of lead.

Attached screenshot image.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: totem 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  9 12:12:52 2019
InstallationDate: Installed on 2018-12-02 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: totem
UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago)

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: totem (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: wayland (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco wayland-session

** Attachment added: "Captura de pantalla de 2019-03-09 12-11-28.png"
   
https://bugs.launchpad.net/bugs/1819277/+attachment/5244952/+files/Captura%20de%20pantalla%20de%202019-03-09%2012-11-28.png

** Description changed:

+ https://gitlab.gnome.org/GNOME/totem/issues/307
+ 
+ ---
+ 
  When I open a movie in totem, it looks like a window. But then I enlarge
  it to full screen. It is seen in the lower part, a strip of lead.
  
  Attached screenshot image.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  9 12:12:52 2019
  InstallationDate: Installed on 2018-12-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: totem
  UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago)

** Also affects: wayland (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  I see stripes plomas in full screen mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+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 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-02-20 Thread El jinete sin cabeza
** No longer affects: libdrm (Ubuntu)

** No longer affects: xserver-xorg-video-intel (Ubuntu)

** Bug watch added: freedesktop.org Bugzilla #109594
   https://bugs.freedesktop.org/show_bug.cgi?id=109594

** Also affects: totem via
   https://bugs.freedesktop.org/show_bug.cgi?id=109594
   Importance: Unknown
   Status: Unknown

** Project changed: totem => mesa

** Description changed:

- https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
- 
- ---
- 
  https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME)
  
  ---
  
  I'm not sure, but this happened after updating to gstreamer 1.15.1, I
  have problems when I maximize totem.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815236/+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 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-02-08 Thread El jinete sin cabeza
** Also affects: libdrm (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

+ https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel)
+ 
+ ---
+ 
  https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
  
  ---
  
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
  I'm not sure, but this happened after updating to gstreamer 1.15.1
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

  https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel)
  
  ---
  
  https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
  
  ---
  
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
- I'm not sure, but this happened after updating to gstreamer 1.15.1
+ I'm not sure, but this happened after updating to gstreamer 1.15.1.  The
+ problem occurs when I maximize totem.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

- https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel)
- 
- ---
- 
  https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
  
  ---
  
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
  I'm not sure, but this happened after updating to gstreamer 1.15.1.  The
  problem occurs when I maximize totem.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from 

[Ubuntu-x-swat] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-02-08 Thread El jinete sin cabeza
** Description changed:

+ https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
+ 
+ ---
+ 
  https://gitlab.gnome.org/GNOME/totem/issues/297
  
  ---
  
  I'm not sure, but this happened after updating to gstreamer 1.15.1
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815236/+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 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-02-08 Thread El jinete sin cabeza
https://gitlab.gnome.org/GNOME/totem/issues/297#note_432608

Bastien Nocera:
"Looks like a crash inside the application side intel driver inside Mesa. It's 
going to be a driver problem rather than something that totem can deal with."

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815236/+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