[Touch-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1865300

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gtk/issues/2457

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.2, the problem page at 
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1874262

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

Status in gdm3 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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"

Status in gdm3 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2020-02-20 Thread El jinete sin cabeza
** No longer affects: nautilus

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/gtk/issues/2457
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gtk/issues/2457

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2020-02-20 Thread El jinete sin cabeza
Moved to:
https://gitlab.gnome.org/GNOME/gtk/issues/2457

** Description changed:

- https://gitlab.gnome.org/GNOME/nautilus/issues/1190
+ https://gitlab.gnome.org/GNOME/gtk/issues/2457
  
  ---
  
  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2457
   https://gitlab.gnome.org/GNOME/gtk/issues/2457

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gtk/issues/2457

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report

2019-11-20 Thread El jinete sin cabeza
** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1848064

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Eoan:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848064/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2019-11-13 Thread El jinete sin cabeza
** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.2, the problem page at 
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2019-10-29 Thread El jinete sin cabeza
** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1190

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1843706] [NEW] Privacy of information collected with apport in the gnome-shell package

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

After using apport to report a problem in gnome-shell in the file
'ShellJournal.txt' private information appears, such as the name of the
Notebook.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu7
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 12 09:08:45 2019
InstallationDate: Installed on 2018-12-02 (283 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1843706

Title:
  Privacy of information collected with apport in the gnome-shell
  package

Status in apport package in Ubuntu:
  New

Bug description:
  After using apport to report a problem in gnome-shell in the file
  'ShellJournal.txt' private information appears, such as the name of
  the Notebook.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 12 09:08:45 2019
  InstallationDate: Installed on 2018-12-02 (283 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843706/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()

2019-09-11 Thread El jinete sin cabeza
https://gitlab.gnome.org/GNOME/evolution/issues/616

** Information type changed from Private to Public

** Description changed:

+ https://gitlab.gnome.org/GNOME/evolution/issues/616
+ 
+ ---
+ 
  I don't know what happened.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:41:26 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2018-12-02 (282 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
-  LANG=es_CL.UTF-8
-  LANGUAGE=es_CL:es
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=es_CL.UTF-8
+  LANGUAGE=es_CL:es
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  SegvAnalysis:
-  Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
-  PC (0x7f36355653ae) ok
-  source "(%r8)" (0x7f36) not located in a known VMA region (needed 
readable region)!
-  destination "%rsi" ok
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
+  PC (0x7f36355653ae) ok
+  source "(%r8)" (0x7f36) not located in a known VMA region (needed 
readable region)!
+  destination "%rsi" ok
+  Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
-  tcache_get (tc_idx=) at malloc.c:2937
-  __GI___libc_malloc (bytes=32) at malloc.c:3051
-  g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  tcache_get (tc_idx=) at malloc.c:2937
+  __GI___libc_malloc (bytes=32) at malloc.c:3051
+  g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

** Bug watch added: gitlab.gnome.org/GNOME/evolution/issues #616
   https://gitlab.gnome.org/GNOME/evolution/issues/616

** Also affects: evolution-data-server via
   https://gitlab.gnome.org/GNOME/evolution/issues/616
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1843627

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server:
  Unknown
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/evolution/issues/616

  ---

  I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:41:26 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2018-12-02 (282 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f36355653ae) ok
   source "(%r8)" (0x7f36) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=32) at malloc.c:3051
   g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions

-- 

[Touch-packages] [Bug 1839211] Re: Please upgrade to 2.2.1-1(Debian)

2019-09-04 Thread El jinete sin cabeza
See LP #1842118

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1839211

Title:
  Please upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1839211] Re: Please upgrade to 2.2.1-1(Debian)

2019-09-04 Thread El jinete sin cabeza
See LP: #1842118

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1839211

Title:
  Please upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1839211] Re: Please upgrade to 2.2.1-1(Debian)

2019-09-04 Thread El jinete sin cabeza
See LP 1842118

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1839211

Title:
  Please upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1839211] Re: Please upgrade to 2.2.1-1(Debian)

2019-09-04 Thread El jinete sin cabeza
Please, close report. New version in eoan:
https://launchpad.net/ubuntu/+source/tracker/2.2.99.0-1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1839211

Title:
  Please upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1839211] Re: Please upgrade to 2.2.1-1(Debian)

2019-09-04 Thread El jinete sin cabeza
Please close report.  New version in eoan:
https://launchpad.net/ubuntu/+source/tracker/2.2.99.0-1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1839211

Title:
  Please upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1840915] Re: tracker-store crashed with SIGSEGV in tracker_events_add_delete()

2019-08-21 Thread El jinete sin cabeza
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1840915

Title:
  tracker-store crashed with SIGSEGV in tracker_events_add_delete()

Status in tracker package in Ubuntu:
  Invalid

Bug description:
  I don't know how it happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.9-050209-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 21 08:28:15 2019
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2018-12-02 (261 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x56172bf3c22d :
mov0x10(%rax),%rdi
   PC (0x56172bf3c22d) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   tracker_events_add_delete ()
   ()
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
  Title: tracker-store crashed with SIGSEGV in tracker_events_add_delete()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (261 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1840915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1839545

Title:
  Graphic environment slows down and then returns to normal

Status in mesa package in Ubuntu:
  New

Bug description:
  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
  

[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2019-08-08 Thread El jinete sin cabeza
** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1190

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1839211] Re: Upgrade to 2.2.1-1

2019-08-06 Thread El jinete sin cabeza
** Attachment added: "Captura de pantalla de 2019-08-06 16-20-51.png"
   
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+attachment/5281307/+files/Captura%20de%20pantalla%20de%202019-08-06%2016-20-51.png

** Summary changed:

- Upgrade to 2.2.1-1
+ Upgrade to 2.2.1-1(Debian)

** Summary changed:

- Upgrade to 2.2.1-1(Debian)
+ Please upgrade to 2.2.1-1(Debian)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1839211

Title:
  Please upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  New

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1839211] [NEW] Upgrade to 2.2.1-1(Debian)

2019-08-06 Thread El jinete sin cabeza
Public bug reported:

I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher.
[0] https://wiki.gnome.org/Apps/Music/Resources

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: tracker 2.1.8-2
Uname: Linux 5.2.6-050206-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  6 16:10:43 2019
InstallationDate: Installed on 2018-12-02 (247 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: tracker
UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

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


** Tags: amd64 apport-bug eoan upgrade-software-version wayland-session

** Description changed:

- I am testing gnome-music night, and request tracker version 2.2.0 or
- higher.
+ I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
+ [0] https://wiki.gnome.org/Apps/Music/Resources
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1839211

Title:
  Upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  New

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1837937] Re: CRASH

2019-07-26 Thread El jinete sin cabeza
** Description changed:

- Description:  Ubuntu Eoan Ermine (development branch)
- Release:  19.10
- gnome:
-   Installed: (none)
-   Candidate: 1:3.30+1ubuntu1
-   Version table:
-  1:3.30+1ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages
- The screen froze but the mouse was still moving then it all froze and said 
systemd-journal not able to write entry. I had to press the power button.
+ The screen froze but the mouse was still moving then it all froze and
+ said systemd-journal not able to write entry. I had to press the power
+ button.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-9-generic 5.2.0-9.10
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  Uname: Linux 5.2.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  administrator   2068 F pulseaudio
-  /dev/snd/controlC0:  administrator   2068 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  administrator   2068 F pulseaudio
+  /dev/snd/controlC0:  administrator   2068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:11:47 2019
  InstallationDate: Installed on 2019-06-05 (50 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.2.0-9-generic N/A
-  linux-backports-modules-5.2.0-9-generic  N/A
-  linux-firmware   1.181
+  linux-restricted-modules-5.2.0-9-generic N/A
+  linux-backports-modules-5.2.0-9-generic  N/A
+  linux-firmware   1.181
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  administrator   2852 F pulseaudio
-  /dev/snd/controlC0:  administrator   2852 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  administrator   2852 F pulseaudio
+  /dev/snd/controlC0:  administrator   2852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-05 (51 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  RelatedPackageVersions:
-  linux-restricted-modules-5.2.0-9-generic N/A
-  linux-backports-modules-5.2.0-9-generic  N/A
-  linux-firmware   1.181
+  linux-restricted-modules-5.2.0-9-generic N/A
+  linux-backports-modules-5.2.0-9-generic  N/A
+  linux-firmware   1.181
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.2.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  

[Touch-packages] [Bug 1837937] Re: CRASH

2019-07-26 Thread El jinete sin cabeza
Please execute the following command:

$ apport-collect -p linux 1837937

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837937

Title:
  CRASH

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10
  gnome:
Installed: (none)
Candidate: 1:3.30+1ubuntu1
Version table:
   1:3.30+1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages
  The screen froze but the mouse was still moving then it all froze and said 
systemd-journal not able to write entry. I had to press the power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-9-generic 5.2.0-9.10
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  Uname: Linux 5.2.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2068 F pulseaudio
   /dev/snd/controlC0:  administrator   2068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:11:47 2019
  InstallationDate: Installed on 2019-06-05 (50 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-9-generic N/A
   linux-backports-modules-5.2.0-9-generic  N/A
   linux-firmware   1.181
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1837937] Re: CRASH

2019-07-26 Thread El jinete sin cabeza
Please attach what this command returns:

journalctl -b-5 > journalctl_-b-5_LP1837937.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837937

Title:
  CRASH

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10
  gnome:
Installed: (none)
Candidate: 1:3.30+1ubuntu1
Version table:
   1:3.30+1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages
  The screen froze but the mouse was still moving then it all froze and said 
systemd-journal not able to write entry. I had to press the power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-9-generic 5.2.0-9.10
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  Uname: Linux 5.2.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2068 F pulseaudio
   /dev/snd/controlC0:  administrator   2068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:11:47 2019
  InstallationDate: Installed on 2019-06-05 (50 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-9-generic N/A
   linux-backports-modules-5.2.0-9-generic  N/A
   linux-firmware   1.181
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1837944] Re: systemd-journal failed to write entry read only mode

2019-07-25 Thread El jinete sin cabeza
*** This bug is a duplicate of bug 1837937 ***
https://bugs.launchpad.net/bugs/1837937

** This bug has been marked a duplicate of bug 1837937
   CRASH

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837944

Title:
  systemd-journal failed to write entry read only mode

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Description: Ubuntu Eoan Ermine (development branch)
  Release: 19.10
  systemd:
Installed: 240-6ubuntu10
Candidate: 240-6ubuntu10
Version table:
   *** 240-6ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   240-6ubuntu9 500
  500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages
  systemd-journal failed to write entry read only mode

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 240-6ubuntu10
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  Uname: Linux 5.2.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:26:39 2019
  InstallationDate: Installed on 2019-06-05 (50 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837944/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1837937] Re: CRASH

2019-07-25 Thread El jinete sin cabeza
The version installed on your system is: "linux-image-5.2.0-9-generic
5.2.0-9.10" and this version is not yet released.

** Attachment added: "linux.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+attachment/5279290/+files/linux.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837937

Title:
  CRASH

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10
  gnome:
Installed: (none)
Candidate: 1:3.30+1ubuntu1
Version table:
   1:3.30+1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages
  The screen froze but the mouse was still moving then it all froze and said 
systemd-journal not able to write entry. I had to press the power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-9-generic 5.2.0-9.10
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  Uname: Linux 5.2.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2068 F pulseaudio
   /dev/snd/controlC0:  administrator   2068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:11:47 2019
  InstallationDate: Installed on 2019-06-05 (50 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-9-generic N/A
   linux-backports-modules-5.2.0-9-generic  N/A
   linux-firmware   1.181
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1837938] [NEW] Incorrect: "python3 /usr/lib/software-properties/software-properties-dbus"

2019-07-25 Thread El jinete sin cabeza
Public bug reported:

Incorrect:
root 13608 1  0 09:29 ?00:00:00 python3 
/usr/lib/software-properties/software-properties-dbus

YES:
root 13608 1  0 09:29 ?00:00:00 /usr/bin/python3 
/usr/lib/software-properties/software-properties-dbus

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: software-properties-common 0.98.5
Uname: Linux 5.2.2-050202-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 25 15:26:25 2019
InstallationDate: Installed on 2018-12-02 (235 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to eoan on 2018-12-02 (234 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1837938

Title:
  Incorrect: "python3 /usr/lib/software-properties/software-properties-
  dbus"

Status in software-properties package in Ubuntu:
  New

Bug description:
  Incorrect:
  root 13608 1  0 09:29 ?00:00:00 python3 
/usr/lib/software-properties/software-properties-dbus

  YES:
  root 13608 1  0 09:29 ?00:00:00 /usr/bin/python3 
/usr/lib/software-properties/software-properties-dbus

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-common 0.98.5
  Uname: Linux 5.2.2-050202-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:26:25 2019
  InstallationDate: Installed on 2018-12-02 (235 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (234 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1837938/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1837245] [NEW] Failed to bump fs.file-max, ignoring: Invalid argument

2019-07-19 Thread El jinete sin cabeza
Public bug reported:

$ journalctl -b

[...]

[3.786804] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid
argument

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: systemd 240-6ubuntu9
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 19 13:44:43 2019
InstallationDate: Installed on 2018-12-02 (228 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.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

 2 overridden configuration files found.
UpgradeStatus: Upgraded to eoan on 2018-12-02 (228 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

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


** Tags: amd64 apport-bug eoan third-party-packages wayland-session

** Description changed:

  $ journalctl -b
  
  [...]
  
- systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
+ [3.786804] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid
+ argument
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 240-6ubuntu9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 19 13:44:43 2019
  InstallationDate: Installed on 2018-12-02 (228 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.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
-  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
-  [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
-  
-  2 overridden configuration files found.
+  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
+  [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
+ 
+  2 overridden configuration files found.
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (228 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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837245

Title:
  Failed to bump fs.file-max, ignoring: Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  $ journalctl -b

  [...]

  [3.786804] systemd[1]: Failed to bump fs.file-max, ignoring:
  Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 240-6ubuntu9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 19 13:44:43 2019
  InstallationDate: Installed on 2018-12-02 (228 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 

[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2019-07-12 Thread El jinete sin cabeza
** Tags removed: rls-ee-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.2, the problem page at 
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2019-07-12 Thread El jinete sin cabeza
** Tags added: rls-ee-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.2, the problem page at 
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1825981] Re: /usr/lib/tracker/tracker-extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1825981

Title:
  /usr/lib/tracker/tracker-
  
extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload

Status in tracker package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
tracker.  This problem was most recently seen with package version 2.1.6-1, the 
problem page at 
https://errors.ubuntu.com/problem/b99e01aacdc0c848c2170270ddbb577546a03a73 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825981/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1829417] Re: When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a lot

2019-05-30 Thread El jinete sin cabeza
** Description changed:

  [Impact]
  'tracker-miner-f' works a lot when I download with chrome
  
  [Fix]
  tracker-miner-f work with much less intencity
  
  [Test Case]
  1. Open Chrome
- 2. Download 
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso
+ 2. Download 
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso 
(This is happening to me with any .iso file)
  3. Open gnome-terminal and run top
  4. While the download of OI-hipster-gui-20190511.iso occurs, 
'tracker-miner-f' works constantly and intentionally
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.1.2-050102-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 12:47:13 2019
  InstallationDate: Installed on 2018-12-02 (164 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1829417

Title:
  When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a
  lot

Status in tracker package in Ubuntu:
  New

Bug description:
  [Impact]
  'tracker-miner-f' works a lot when I download with chrome

  [Fix]
  tracker-miner-f work with much less intencity

  [Test Case]
  1. Open Chrome
  2. Download 
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso 
(This is happening to me with any .iso file)
  3. Open gnome-terminal and run top
  4. While the download of OI-hipster-gui-20190511.iso occurs, 
'tracker-miner-f' works constantly and intentionally

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.1.2-050102-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 12:47:13 2019
  InstallationDate: Installed on 2018-12-02 (164 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1829417/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1830631] [NEW] After updating I can not connect to my favorite SSID

2019-05-27 Thread El jinete sin cabeza
Private bug reported:

Update network-manager I can not connect

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.18.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May 27 11:11:00 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-12-02 (175 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 default via 10.24.44.1 dev wlx98ded0105daf proto dhcp metric 600 
 10.24.44.0/24 dev wlx98ded0105daf proto kernel scope link src 10.24.44.243 
metric 600 
 169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to eoan on 2018-12-02 (175 days ago)
nmcli-dev:
 DEVICE   TYPE  STATE IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION 
CON-UUID  CON-PATH  
 
 wlx98ded0105daf  wifi  connected full  limited 
  /org/freedesktop/NetworkManager/Devices/2  UNAP-Funcionarios  
32974ec7-e22a-4560-894f-816bf7608ace  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 p2p-dev-wlx98ded0105daf  wifi-p2p  disconnected  none  none
  /org/freedesktop/NetworkManager/Devices/3  -- --  
  -- 
 lo   loopback  unmanaged unknown   unknown 
  /org/freedesktop/NetworkManager/Devices/1  -- --  
  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.18.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

** Information type changed from Public to Private

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1830631

Title:
  After updating I can not connect to my favorite SSID

Status in network-manager package in Ubuntu:
  New

Bug description:
  Update network-manager I can not connect

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.18.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 27 11:11:00 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-12-02 (175 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.24.44.1 dev wlx98ded0105daf proto dhcp metric 600 
   10.24.44.0/24 dev wlx98ded0105daf proto kernel scope link src 10.24.44.243 
metric 600 
   169.254.0.0/16 dev wlx98ded0105daf scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (175 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION 
CON-UUID  CON-PATH  
 
   wlx98ded0105daf  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  UNAP-Funcionarios  
32974ec7-e22a-4560-894f-816bf7608ace  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   p2p-dev-wlx98ded0105daf  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  -- --
-- 
   lo   loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  -- --
--
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.18.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1830631/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1826222] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/eoan

2019-05-16 Thread El jinete sin cabeza
** Changed in: python-apt (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1826222

Title:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources(): Error:
  could not find a distribution template for Ubuntu/eoan

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  The 'Configuration' button of update-manager does not work.

  [Test Case]
  $ sudo update-manager
  Traceback (most recent call last):
    File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
    File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1829417] [NEW] When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a lot

2019-05-16 Thread El jinete sin cabeza
Public bug reported:

[Impact]
'tracker-miner-f' works a lot when I download with chrome

[Fix]
tracker-miner-f work with much less intencity

[Test Case]
1. Open Chrome
2. Download 
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso
3. Open gnome-terminal and run top
4. While the download of OI-hipster-gui-20190511.iso occurs, 'tracker-miner-f' 
works constantly and intentionally

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: tracker 2.1.8-2
Uname: Linux 5.1.2-050102-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 16 12:47:13 2019
InstallationDate: Installed on 2018-12-02 (164 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: tracker
UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1829417

Title:
  When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a
  lot

Status in tracker package in Ubuntu:
  New

Bug description:
  [Impact]
  'tracker-miner-f' works a lot when I download with chrome

  [Fix]
  tracker-miner-f work with much less intencity

  [Test Case]
  1. Open Chrome
  2. Download 
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso
  3. Open gnome-terminal and run top
  4. While the download of OI-hipster-gui-20190511.iso occurs, 
'tracker-miner-f' works constantly and intentionally

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.1.2-050102-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 12:47:13 2019
  InstallationDate: Installed on 2018-12-02 (164 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1829417/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()

2019-04-30 Thread El jinete sin cabeza
** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1827154

Title:
  gnome-control-center crashed with SIGSEGV in
  _gdk_event_queue_handle_motion_compression()

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503

  ---

  [Impact]
  When I try to set the pen on my touch screen. gnome-control-center crashes.

  [Fix]
  That you can configure the pencil to later occupy it with my touch screen.

  [Test Case]
  1. Open gnome-control-center
  2. Click on Wacom tablet
  3. Press the buttons of the pencil, touching the screen
  4. gnome-control-center crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.32.1-1ubuntu5
  Uname: Linux 5.1.0-050100rc7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 19:28:42 2019
  InstallationDate: Installed on 2018-12-02 (149 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1826222] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/eoan

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

- The 'Configuration' button of update-manager does not work
+ software-properties-gtk crashed with 
aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not 
find a distribution template for Ubuntu/eoan

** Description changed:

- $ sudo update-manager 
+ The 'Configuration' button of update-manager does not work.
+ 
+ $ sudo update-manager
  Traceback (most recent call last):
-   File "/usr/bin/software-properties-gtk", line 100, in 
- app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
- SoftwareProperties.__init__(self, options=options, datadir=datadir)
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
- self.reload_sourceslist()
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
- self.distro.get_sources(self.sourceslist)
-   File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
- (self.id, self.codename))
+   File "/usr/bin/software-properties-gtk", line 100, in 
+ app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
+ SoftwareProperties.__init__(self, options=options, datadir=datadir)
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
+ self.reload_sourceslist()
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
+ self.distro.get_sources(self.sourceslist)
+   File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
+ (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

** Description changed:

+ [Impact]
  The 'Configuration' button of update-manager does not work.
  
+ [Test Case]
  $ sudo update-manager
  Traceback (most recent call last):
    File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
    File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1826222

Title:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources(): Error:
  could not find a distribution template for Ubuntu/eoan

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  The 'Configuration' button of update-manager does not work.

  [Test Case]
  $ sudo update-manager
  Traceback (most recent call last):
    File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",

[Touch-packages] [Bug 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread El jinete sin cabeza
@Sebastien

> Does https://bugs.launchpad.net/ubuntu/+source/python-
apt/1.9.0~alpha0~ubuntu1 fix your issue?

Yes, Now it works correctly.

** Attachment added: "$ dpkg -l | grep python-apt"
   
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+attachment/5258649/+files/dpkg_-l_-_grep_python-apt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1826222

Title:
  The 'Configuration' button of update-manager does not work

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread El jinete sin cabeza
See LP: #1825738

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1826222

Title:
  The 'Configuration' button of update-manager does not work

Status in software-properties package in Ubuntu:
  New

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1826222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1826222] [NEW] The 'Configuration' button of update-manager does not work

2019-04-24 Thread El jinete sin cabeza
Public bug reported:

$ sudo update-manager 
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
self.reload_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
  File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: software-properties-gtk 0.97.11
Uname: Linux 5.1.0-050100rc6-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 10:21:47 2019
InstallationDate: Installed on 2018-12-02 (142 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1826222

Title:
  The 'Configuration' button of update-manager does not work

Status in software-properties package in Ubuntu:
  New

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1826222/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1825822] Re: $ ubuntu-bug /var/crash/.crash not work

2019-04-23 Thread El jinete sin cabeza
1. Which .crash file name did you pass to ubuntu-bug?

$ ubuntu-bug /var/crash/_usr_bin_gnome-control-center.1000.crash


2. What did you expect to happen that did not?

That the .crash upload to be processed and open the launchpad.net page.
And then, I will generate the BackTrace with the symbols of the packages
that are intervening.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1825822

Title:
  $ ubuntu-bug /var/crash/.crash not work

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  When trying to send a report manually, you can not
   
  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash does not work

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.10-0ubuntu27
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 07:50:37 2019
  InstallationDate: Installed on 2018-12-02 (140 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (140 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1825822/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1825822] [NEW] $ ubuntu-bug /var/crash/.crash not work

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

[Impact]
When trying to send a report manually, you can not
 
[Test Case]
Start Ubuntu
Open terminal
$ ubuntu-bug /var/crash/.crash does not work

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.10-0ubuntu27
Uname: Linux 5.1.0-050100rc6-generic x86_64
ApportLog:
 
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 07:50:37 2019
InstallationDate: Installed on 2018-12-02 (140 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2018-12-02 (140 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1825822

Title:
  $ ubuntu-bug /var/crash/.crash not work

Status in apport package in Ubuntu:
  New

Bug description:
  [Impact]
  When trying to send a report manually, you can not
   
  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash does not work

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.10-0ubuntu27
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 07:50:37 2019
  InstallationDate: Installed on 2018-12-02 (140 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (140 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1825822/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287

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

Status in GStreamer:
  Unknown
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
    

[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287

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

Status in GStreamer:
  New
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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;
    }
  ---

  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287

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

Status in GStreamer:
  Unknown
Status in Mesa:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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;
    }
  ---

  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287

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

Status in GStreamer:
  Unknown
Status in Mesa:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  

[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287

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

Status in GStreamer:
  Unknown
Status in Mesa:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  

[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287

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

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.freedesktop.org/show_bug.cgi?id=110452
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract

2019-04-15 Thread El jinete sin cabeza
** Tags removed: 100 cpu
** Tags added: disco

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1815089

Title:
  100% CPU / usr / lib / tracker / tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  The / usr / lib / tracker / tracker-extract is using almost 100% CPU
  resources see attached image

  After updates on today's date 07/02/2019 has improved the crashes, but
  the hunger for CPU continues.

  **

  O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos
  da CPU vide imagem em anexo

  Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
  mas a fome por CPU continua.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-04-15 Thread El jinete sin cabeza
** Description changed:

+ The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center. This problem was most recently seen with package version 
1:3.30.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b90090b3330514b0e5d6f1ed58c2260a77b8e5e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
+ If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ 
+ ---
+ 
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
  
  ---
  
  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.
  
  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.
  
  [Potential Regression]
  I think it's not a potential regression.
  
  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1810316

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center. This problem was most recently seen with package version 
1:3.30.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b90090b3330514b0e5d6f1ed58c2260a77b8e5e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  ---

  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   

[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-04-14 Thread El jinete sin cabeza
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #342
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342

** Description changed:

- https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
+ https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
  
  ---
  
  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.
  
  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.
  
  [Potential Regression]
  I think it's not a potential regression.
  
  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

** No longer affects: gnome-control-center

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1810316

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  Unknown
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions

-- 
Mailing 

[Touch-packages] [Bug 1822587] Re: wifi service stops occasionally.

2019-04-13 Thread El jinete sin cabeza
Something similar happens to me. LP: #1824665

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1822587

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1822587/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1824665] [NEW] Disconnects from WiFi (SSID)

2019-04-13 Thread El jinete sin cabeza
Private bug reported:

[Impact]
I am working with several programs at the same time. Like the web browser, 
Transmission, and others. And it has happened to me twice today. The led of my 
USB Wifi adapter is always on and there is no packet transfer. Then the 
NetworkManager asks me for the password. Suggesting me in the small window with 
hidden characters. Press 'OK' and ask me again. 'I forget' the password and add 
it again. And I do not accept it either. I had to change the USB Wifi adapter 
several times in USB ports. And suddenly it works again.
 
[Test Case]
- Turn on the Notebook
- Open programs that use WiFi intensely (Transmission)
- Wait a few hours
- Internet traffic is blocked
- NetworkManager requests the password of the SSID that I use
- Login password
- Does not accept the password
- I forgot SSID data
- Context the SSID that I use
- Ask for a password again
- Does not accept Password
- Change USB ports with my WiFi USB adapter
- And after a few minutes, it is correctly connected again.

Others:
Attach: $_journalctl_-f.txt When this happens

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.16.0-0ubuntu2
Uname: Linux 5.0.7-050007-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 19:36:13 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-12-02 (132 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to disco on 2018-12-02 (132 days ago)
nmcli-dev:
 DEVICE   TYPE  STATE IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH 
 wlx98ded0105daf  wifi  disconnected  limited   limited 
  /org/freedesktop/NetworkManager/Devices/2  --  ----   
 p2p-dev-wlx98ded0105daf  wifi-p2p  disconnected  none  none
  /org/freedesktop/NetworkManager/Devices/3  --  ----   
 lo   loopback  unmanaged unknown   unknown 
  /org/freedesktop/NetworkManager/Devices/1  --  ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.16.0   disconnected  started  limited   enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "$ journalctl -f"
   
https://bugs.launchpad.net/bugs/1824665/+attachment/5255532/+files/%24_journalctl_-f.txt

** Summary changed:

- Disconnects from WiFi
+ Disconnects from WiFi (SSID)

** Information type changed from Public to Private

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1824665

Title:
  Disconnects from WiFi (SSID)

Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]
  I am working with several programs at the same time. Like the web browser, 
Transmission, and others. And it has happened to me twice today. The led of my 
USB Wifi adapter is always on and there is no packet transfer. Then the 
NetworkManager asks me for the password. Suggesting me in the small window with 
hidden characters. Press 'OK' and ask me again. 'I forget' the password and add 
it again. And I do not accept it either. I had to change the USB Wifi adapter 
several times in USB ports. And suddenly it works again.
   
  [Test Case]
  - Turn on the Notebook
  - Open programs that use WiFi intensely (Transmission)
  - Wait a few hours
  - Internet traffic is blocked
  - NetworkManager requests the password of the SSID that I use
  - Login password
  - Does not accept the password
  - I forgot SSID data
  - Context the SSID that I use
  - Ask for a password again
  - Does not accept Password
  - Change USB ports with my WiFi USB adapter
  - And after a few minutes, it is correctly connected again.

  Others:
  Attach: $_journalctl_-f.txt When this happens

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  Uname: Linux 5.0.7-050007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:36:13 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-12-02 (132 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   

[Touch-packages] [Bug 1824637] [NEW] Full load

2019-04-13 Thread El jinete sin cabeza
Public bug reported:

It always happens when I start the notebook. I must close it with 'kill
-u ProcessNumber'

Please indicate that more information is needed to repair this error.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: tracker 2.1.8-2
Uname: Linux 5.0.7-050007-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 12:42:44 2019
InstallationDate: Installed on 2018-12-02 (131 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: tracker
UpgradeStatus: Upgraded to disco on 2018-12-02 (131 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1824637

Title:
  Full load

Status in tracker package in Ubuntu:
  New

Bug description:
  It always happens when I start the notebook. I must close it with
  'kill -u ProcessNumber'

  Please indicate that more information is needed to repair this error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  Uname: Linux 5.0.7-050007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 12:42:44 2019
  InstallationDate: Installed on 2018-12-02 (131 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2018-12-02 (131 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1824637/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1824526] Re: It does not send .crash reports manually

2019-04-12 Thread El jinete sin cabeza
** Summary changed:

- It does not send .crash reports manually.
+ It does not send .crash reports manually

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1824526

Title:
  It does not send .crash reports manually

Status in apport package in Ubuntu:
  New

Bug description:
  When executing:
  /var/crash$ ubuntu-bug _usr_bin_nautilus.1000.crash

  It does not send a report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apport 2.20.10-0ubuntu27
  Uname: Linux 5.0.7-050007-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 08:33:57 2019
  InstallationDate: Installed on 2018-12-02 (130 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to disco on 2018-12-02 (130 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824526/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1824526] [NEW] It does not send .crash reports manually.

2019-04-12 Thread El jinete sin cabeza
Public bug reported:

When executing:
/var/crash$ ubuntu-bug _usr_bin_nautilus.1000.crash

It does not send a report.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: apport 2.20.10-0ubuntu27
Uname: Linux 5.0.7-050007-generic x86_64
ApportLog:
 
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 12 08:33:57 2019
InstallationDate: Installed on 2018-12-02 (130 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to disco on 2018-12-02 (130 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1824526

Title:
  It does not send .crash reports manually.

Status in apport package in Ubuntu:
  New

Bug description:
  When executing:
  /var/crash$ ubuntu-bug _usr_bin_nautilus.1000.crash

  It does not send a report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apport 2.20.10-0ubuntu27
  Uname: Linux 5.0.7-050007-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 08:33:57 2019
  InstallationDate: Installed on 2018-12-02 (130 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to disco on 2018-12-02 (130 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824526/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1824152] Re: /usr/share/apport/whoopsie-upload-all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport/whoopsie-upload-all@166:colle

2019-04-10 Thread El jinete sin cabeza
Excellent guys!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1824152

Title:
  /usr/share/apport/whoopsie-upload-
  
all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport
  /whoopsie-upload-all@166:collect_info:process_report

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu26, the problem page at 
https://errors.ubuntu.com/problem/069eb695cd341ac71e40453596403139bc245c08 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824152/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1822092

Title:
  FFe: Mesa 19.0.1 for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1822092/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-27 Thread El jinete sin cabeza
@Till

I do not see it crashing:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432#note_475636

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1810316

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread El jinete sin cabeza
** Attachment added: "$ ll /var/crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810316/+attachment/5249520/+files/ll_var-crash.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1810316

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread El jinete sin cabeza
** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
- https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 
(moved of freedesktop to GNOME)
+ https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
  
  ---
  
  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.
  
  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.
  
  [Potential Regression]
  I think it's not a potential regression.
  
  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1810316

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

Status in gnome-control-center:
  New
Status in NetworkManager:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

  ---

  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.

  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.

  [Potential Regression]
  I think it's not a potential regression.

  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [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
Touch seeded packages, 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.

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://github.com/intel/intel-vaapi-driver/issues/451
  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:

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://github.com/intel/intel-vaapi-driver/issues/451
  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:

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in Mesa:
  Unknown
Status in Totem:
  New
Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://github.com/intel/intel-vaapi-driver/issues/451
  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:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in Mesa:
  Unknown
Status in Totem:
  New
Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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, 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:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in Mesa:
  Unknown
Status in Totem:
  New
Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in Mesa:
  Unknown
Status in Totem:
  New
Status in intel-vaapi-driver package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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: 

[Touch-packages] [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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1821318

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1821318

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1821318

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1821318

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1821318

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1821318

Title:
  FFe: Wayland 1.17 for disco

Status in wayland package in Ubuntu:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1821318/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1820361] Re: Unable to mount USB hard drive

2019-03-16 Thread El jinete sin cabeza
https://github.com/systemd/systemd/issues/12019#issuecomment-473578815

"Please, close report. The hard disc, it had no format."

** Bug watch added: github.com/systemd/systemd/issues #12019
   https://github.com/systemd/systemd/issues/12019

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1820361

Title:
  Unable to mount USB hard drive

Status in systemd package in Ubuntu:
  New

Bug description:
  https://github.com/systemd/systemd/issues/12019

  ---

  The USB hard drive does not appear in Nautilus.

  The error that appears in journalctl is:
  systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 
2.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1820361] Re: Unable to mount USB hard drive

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

+ https://github.com/systemd/systemd/issues/12019
+ 
+ ---
+ 
  The USB hard drive does not appear in Nautilus.
  
  The error that appears in journalctl is:
  systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 
2.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
  
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1820361

Title:
  Unable to mount USB hard drive

Status in systemd package in Ubuntu:
  New

Bug description:
  https://github.com/systemd/systemd/issues/12019

  ---

  The USB hard drive does not appear in Nautilus.

  The error that appears in journalctl is:
  systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 
2.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1820361] Re: Unable to mount USB hard drive

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

- systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 
2.
+ Unable to mount USB hard drive

** Description changed:

  The USB hard drive does not appear in Nautilus.
+ 
+ The error that appears in journalctl is:
+ systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 
2.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
-  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
-  [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
-  
-  2 overridden configuration files found.
+  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
+  [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
+ 
+  2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1820361

Title:
  Unable to mount USB hard drive

Status in systemd package in Ubuntu:
  New

Bug description:
  The USB hard drive does not appear in Nautilus.

  The error that appears in journalctl is:
  systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 
2.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1820361] Re: systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 2.

2019-03-16 Thread El jinete sin cabeza
# /etc/udev/udev.conf
#
# udev_log=debug

$ journalctl -f

** Attachment added: "journalctl_-f_v2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+attachment/5246716/+files/journalctl_-f_v2.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1820361

Title:
  systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with
  exit code 2.

Status in systemd package in Ubuntu:
  New

Bug description:
  The USB hard drive does not appear in Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1820361] [NEW] systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 2.

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

The USB hard drive does not appear in Nautilus.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: systemd 240-6ubuntu1
Uname: Linux 5.0.2-050002-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 15 20:26:26 2019
InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
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

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


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

** Attachment added: "$ journalctl -f"
   
https://bugs.launchpad.net/bugs/1820361/+attachment/5246626/+files/journalctl_-f.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1820361

Title:
  systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with
  exit code 2.

Status in systemd package in Ubuntu:
  New

Bug description:
  The USB hard drive does not appear in Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 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.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818516

Title:
  FFe: Mesa 19.0.x for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.0 will be soon released, and we should get that for disco,
  and then follow point-releases until the last one is released (roughly
  next July, will need an SRU).

  We'll also migrate it to use LLVM 8.

  New features according to upstream release notes:

  GL_AMD_texture_texture4 on all GL 4.0 drivers.
  GL_EXT_shader_implicit_conversions on all drivers (ES extension).
  GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension).
  GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension).
  GL_EXT_render_snorm on gallium drivers (ES extension).
  GL_EXT_texture_view on drivers supporting texture views (ES extension).
  GL_OES_texture_view on drivers supporting texture views (ES extension).
  GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only).
  Shader-based software implementations of GL_ARB_gpu_shader_fp64, 
GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot 
on i965.
  VK_ANDROID_external_memory_android_hardware_buffer on Intel
  Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV
  VK_EXT_scalar_block_layout on Intel and RADV
  VK_KHR_depth_stencil_resolve on Intel
  VK_KHR_draw_indirect_count on Intel
  VK_EXT_conditional_rendering on Intel
  VK_EXT_memory_budget on RADV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1819277

Title:
  I see stripes plomas in full screen mode

Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818516

Title:
  FFe: Mesa 19.0.x for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.0 will be soon released, and we should get that for disco,
  and then follow point-releases until the last one is released (roughly
  next July, will need an SRU).

  We'll also migrate it to use LLVM 8.

  New features according to upstream release notes:

  GL_AMD_texture_texture4 on all GL 4.0 drivers.
  GL_EXT_shader_implicit_conversions on all drivers (ES extension).
  GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension).
  GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension).
  GL_EXT_render_snorm on gallium drivers (ES extension).
  GL_EXT_texture_view on drivers supporting texture views (ES extension).
  GL_OES_texture_view on drivers supporting texture views (ES extension).
  GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only).
  Shader-based software implementations of GL_ARB_gpu_shader_fp64, 
GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot 
on i965.
  VK_ANDROID_external_memory_android_hardware_buffer on Intel
  Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV
  VK_EXT_scalar_block_layout on Intel and RADV
  VK_KHR_depth_stencil_resolve on Intel
  VK_KHR_draw_indirect_count on Intel
  VK_EXT_conditional_rendering on Intel
  VK_EXT_memory_budget on RADV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818516

Title:
  FFe: Mesa 19.0.x for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.0 will be soon released, and we should get that for disco,
  and then follow point-releases until the last one is released (roughly
  next July, will need an SRU).

  We'll also migrate it to use LLVM 8.

  New features according to upstream release notes:

  GL_AMD_texture_texture4 on all GL 4.0 drivers.
  GL_EXT_shader_implicit_conversions on all drivers (ES extension).
  GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension).
  GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension).
  GL_EXT_render_snorm on gallium drivers (ES extension).
  GL_EXT_texture_view on drivers supporting texture views (ES extension).
  GL_OES_texture_view on drivers supporting texture views (ES extension).
  GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only).
  Shader-based software implementations of GL_ARB_gpu_shader_fp64, 
GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot 
on i965.
  VK_ANDROID_external_memory_android_hardware_buffer on Intel
  Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV
  VK_EXT_scalar_block_layout on Intel and RADV
  VK_KHR_depth_stencil_resolve on Intel
  VK_KHR_draw_indirect_count on Intel
  VK_EXT_conditional_rendering on Intel
  VK_EXT_memory_budget on RADV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1818516

Title:
  FFe: Mesa 19.0.x for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.0 will be soon released, and we should get that for disco,
  and then follow point-releases until the last one is released (roughly
  next July, will need an SRU).

  We'll also migrate it to use LLVM 8.

  New features according to upstream release notes:

  GL_AMD_texture_texture4 on all GL 4.0 drivers.
  GL_EXT_shader_implicit_conversions on all drivers (ES extension).
  GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension).
  GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension).
  GL_EXT_render_snorm on gallium drivers (ES extension).
  GL_EXT_texture_view on drivers supporting texture views (ES extension).
  GL_OES_texture_view on drivers supporting texture views (ES extension).
  GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only).
  Shader-based software implementations of GL_ARB_gpu_shader_fp64, 
GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot 
on i965.
  VK_ANDROID_external_memory_android_hardware_buffer on Intel
  Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV
  VK_EXT_scalar_block_layout on Intel and RADV
  VK_KHR_depth_stencil_resolve on Intel
  VK_KHR_draw_indirect_count on Intel
  VK_EXT_conditional_rendering on Intel
  VK_EXT_memory_budget on RADV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1819359] Re: [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all

2019-03-10 Thread El jinete sin cabeza
Thanks for helping build a better Ubuntu. Could you run the following
command in the terminal?

$ sudo apt-get install --install-recommends linux-generic-hwe-18.04
xserver-xorg-hwe-18.04

Restart your computer, and tell us if it works now.

Thanks.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1819359

Title:
  [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Internal speakers work, only having trouble with the headphone output,
  (I have had this problem in every distrobution I´ve tried)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   yoyo   1917 F...m pulseaudio
   /dev/snd/pcmC0D1p:   yoyo   1917 F...m pulseaudio
   /dev/snd/controlC0:  yoyo   1917 F pulseaudio
   /dev/snd/controlC1:  yoyo   1917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 18:44:38 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac 
(20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 82.0.0.0.0
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1819359/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1819277

Title:
  I see stripes plomas in full screen mode

Status in mesa package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1819277

Title:
  I see stripes plomas in full screen mode

Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, which is subscribed to libdrm 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.

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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 

[Touch-packages] [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
Touch seeded packages, 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.

Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815236/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [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
Touch seeded packages, 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.

Status in mesa package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815236/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1814885] Re: packagekitd crashed with SIGABRT in std::terminate()

2019-02-06 Thread El jinete sin cabeza
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1814885

Title:
  packagekitd crashed with SIGABRT in std::terminate()

Status in packagekit package in Ubuntu:
  Invalid

Bug description:
  I do not know how this happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: packagekit 1.1.12-1ubuntu1
  Uname: Linux 5.0.0-05rc5-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Wed Feb  6 07:34:02 2019
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2018-12-02 (65 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/sh
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT in std::terminate()
  UpgradeStatus: Upgraded to disco on 2018-12-02 (65 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1814885/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp