[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op

2023-02-03 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
+ An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a
+ system not connected to internet
+ 
+ * Test case
+ 
+ Start software-properties-gtk on a offline system, go to the Ubuntu Pro
+ tab, click 'Enable Ubuntu Pro', check that no error report dialog is
+ displayed
+ 
+ Verify the error track to ensure there is no report with the new version
+ https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699
+ 
+ * Regression potential
+ 
+ The fix is making the magic token request conditional to the
+ connectivity status, if that was wrong we could end up in a situation
+ where we should display a pincode but don't.
+ 
+ --- 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 
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/.
  
  Traceback (most recent call last):
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 
144, in poll_for_magic_token
- response = wait(options)
-   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 57, in wait
- return _wait(options, UAConfig())
-   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 73, in _wait
- wait_resp = contract.get_magic_attach_token_info(
-   File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in 
get_magic_attach_token_info
- response, _ = self.request_url(
-   File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, 
in request_url
- response, headers = util.readurl(
-   File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl
- resp = request.urlopen(req, timeout=timeout)
-   File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen
- return opener.open(url, data, timeout)
-   File "/usr/lib/python3.10/urllib/request.py", line 519, in open
- response = self._open(req, data)
-   File "/usr/lib/python3.10/urllib/request.py", line 536, in _open
- result = self._call_chain(self.handle_open, protocol, protocol +
-   File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain
- result = func(*args)
-   File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open
- return self.do_open(http.client.HTTPSConnection, req,
-   File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open
- r = h.getresponse()
-   File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse
- response.begin()
-   File "/usr/lib/python3.10/http/client.py", line 318, in begin
- version, status, reason = self._read_status()
-   File "/usr/lib/python3.10/http/client.py", line 279, in _read_status
- line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
-   File "/usr/lib/python3.10/socket.py", line 705, in readinto
- return self._sock.recv_into(b)
-   File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into
- return self.read(nbytes, buffer)
-   File "/usr/lib/python3.10/ssl.py", line 1130, in read
- return self._sslobj.read(len, buffer)
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 
144, in poll_for_magic_token
+ response = wait(options)
+   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 57, in wait
+ return _wait(options, UAConfig())
+   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 73, in _wait
+ wait_resp = contract.get_magic_attach_token_info(
+   File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in 
get_magic_attach_token_info
+ response, _ = self.request_url(
+   File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, 
in request_url
+ response, headers = util.readurl(
+   File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl
+ resp = request.urlopen(req, timeout=timeout)
+   File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen
+ return opener.open(url, data, timeout)
+   File "/usr/lib/python3.10/urllib/request.py", line 519, in open
+ response = self._open(req, data)
+   File "/usr/lib/python3.10/urllib/request.py", line 536, in _open
+ result = self._call_chain(self.handle_open, protocol, protocol +
+   File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain
+ result = func(*args)
+   File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open
+ return self.do_open(http.client.HTTPSConnection, req,
+   File 

[Touch-packages] [Bug 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state

2023-02-03 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
+ An error is triggered when fetching a pin from the Ubuntu Pro server is
+ failing
+ 
+ * Test case
+ 
+ Start software-properties-gtk on a system offline or having internet
+ connectivity issue, check that no error report dialog is displayed
+ 
+ Verify the error track to ensure there is no report with the new version
+ https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1
+ 
+ * Regression potential
+ 
+ The fix for that specific issue is to set an initial value to the pin
+ label. If the change of value would confuse some code it would be
+ visible in the Pin section of the Ubuntu Pro tab not reflected the pin
+ code from the server as expected
+ 
+ 
+ ---
+ 
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 
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/.

** Description changed:

  * Impact
  
  An error is triggered when fetching a pin from the Ubuntu Pro server is
  failing
  
  * Test case
  
  Start software-properties-gtk on a system offline or having internet
- connectivity issue, check that no error report dialog is displayed
+ connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro',
+ check that no error report dialog is displayed
  
  Verify the error track to ensure there is no report with the new version
  https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1
  
  * Regression potential
  
  The fix for that specific issue is to set an initial value to the pin
  label. If the change of value would confuse some code it would be
  visible in the Pin section of the Ubuntu Pro tab not reflected the pin
  code from the server as expected
  
- 
  ---
- 
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 
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/.

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_radio_toggled:update_state

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  * Impact

  An error is triggered when fetching a pin from the Ubuntu Pro server
  is failing

  * Test case

  Start software-properties-gtk on a system offline or having internet
  connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu
  Pro', check that no error report dialog is displayed

  Verify the error track to ensure there is no report with the new version
  https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1

  * Regression potential

  The fix for that specific issue is to set an initial value to the pin
  label. If the change of value would confuse some code it would be
  visible in the Pin section of the Ubuntu Pro tab not reflected the pin
  code from the server as expected

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 
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/software-properties/+bug/2004245/+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 2004634] Re: Disable Ubuntu Pro registration when not online

2023-02-03 Thread Sebastien Bacher
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Committed

** Description changed:

  * Impact
  
  The current UI allows the user to try to register to Ubuntu Pro even
  when the system isn't online, which eventually leads to an error since
  the client fails to contact the server. The updated design disable the
  registration UI in those cases and inform the user they need to get
  online to be able to register which is a better experience.
  
  * Test Case
  
  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed
  
  - disconnect the system, using for example the top panel indicator
  
  - start software-properties-gtk and select the Ubuntu Pro tab
  
  - click 'Enable Ubuntu Pro'
  
  - The dialog controls should be disabled and a string 'Unable to connect
  to Ubuntu Pro servers. Check your internet connection.' displayed at the
  bottom
  
  - reconnect the system
  
  - the dialog control should become active and the label be removed
  
  - register to Ubuntu Pro, that should be working
  
- 
  * Regression potential
  
  If the connectivity check was wrong or not reliable it could be that the
  dialog controls would be disabled even if the system is online, or that
  it would fail to detect that the system isn't connected and let the user
  try to register anyway.
+ 
+ The change also adds a new translatable string. Since currently we don't
+ include translations for that new UI it isn't really a regression. We
+ still plan to fix that by the next languagepack update.

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

Title:
  Disable Ubuntu Pro registration when not online

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  * Impact

  The current UI allows the user to try to register to Ubuntu Pro even
  when the system isn't online, which eventually leads to an error since
  the client fails to contact the server. The updated design disable the
  registration UI in those cases and inform the user they need to get
  online to be able to register which is a better experience.

  * Test Case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - disconnect the system, using for example the top panel indicator

  - start software-properties-gtk and select the Ubuntu Pro tab

  - click 'Enable Ubuntu Pro'

  - The dialog controls should be disabled and a string 'Unable to
  connect to Ubuntu Pro servers. Check your internet connection.'
  displayed at the bottom

  - reconnect the system

  - the dialog control should become active and the label be removed

  - register to Ubuntu Pro, that should be working

  * Regression potential

  If the connectivity check was wrong or not reliable it could be that
  the dialog controls would be disabled even if the system is online, or
  that it would fail to detect that the system isn't connected and let
  the user try to register anyway.

  The change also adds a new translatable string. Since currently we
  don't include translations for that new UI it isn't really a
  regression. We still plan to fix that by the next languagepack update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 2004634] [NEW] Disable Ubuntu Pro registration when not online

2023-02-03 Thread Sebastien Bacher
Public bug reported:

* Impact

The current UI allows the user to try to register to Ubuntu Pro even
when the system isn't online, which eventually leads to an error since
the client fails to contact the server. The updated design disable the
registration UI in those cases and inform the user they need to get
online to be able to register which is a better experience.

* Test Case

- ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
$ pro status
and `$ pro detach` if needed

- disconnect the system, using for example the top panel indicator

- start software-properties-gtk and select the Ubuntu Pro tab

- click 'Enable Ubuntu Pro'

- The dialog controls should be disabled and a string 'Unable to connect
to Ubuntu Pro servers. Check your internet connection.' displayed at the
bottom

- reconnect the system

- the dialog control should become active and the label be removed

- register to Ubuntu Pro, that should be working


* Regression potential

If the connectivity check was wrong or not reliable it could be that the
dialog controls would be disabled even if the system is online, or that
it would fail to detect that the system isn't connected and let the user
try to register anyway.

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

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

Title:
  Disable Ubuntu Pro registration when not online

Status in software-properties package in Ubuntu:
  New

Bug description:
  * Impact

  The current UI allows the user to try to register to Ubuntu Pro even
  when the system isn't online, which eventually leads to an error since
  the client fails to contact the server. The updated design disable the
  registration UI in those cases and inform the user they need to get
  online to be able to register which is a better experience.

  * Test Case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - disconnect the system, using for example the top panel indicator

  - start software-properties-gtk and select the Ubuntu Pro tab

  - click 'Enable Ubuntu Pro'

  - The dialog controls should be disabled and a string 'Unable to
  connect to Ubuntu Pro servers. Check your internet connection.'
  displayed at the bottom

  - reconnect the system

  - the dialog control should become active and the label be removed

  - register to Ubuntu Pro, that should be working

  
  * Regression potential

  If the connectivity check was wrong or not reliable it could be that
  the dialog controls would be disabled even if the system is online, or
  that it would fail to detect that the system isn't connected and let
  the user try to register anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 2004629] Re: /usr/bin/software-properties-gtk:dbus.exceptions.DBusException(org.freedesktop.DBus.Error.TimedOut):activate_name_owner:get_name_owner:call_blocking:/usr/bin/softwar

2023-02-03 Thread Sebastien Bacher
@Nathan, Ccing you as a FYI but I don't think it's something wrong from
our side but rather a problem with the service

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  /usr/bin/software-properties-
  
gtk:dbus.exceptions.DBusException(org.freedesktop.DBus.Error.TimedOut):activate_name_owner:get_name_owner:call_blocking:/usr/bin/software-
  properties-
  
gtk@100:__init__:init_ubuntu_pro:__init__:get_object:__init__:activate_name_owner:start_service_by_name:call_blocking

Status in software-properties package in Ubuntu:
  New

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.99.27, the problem page at 
https://errors.ubuntu.com/problem/de0fd44b666af99030f3b74b33495cf6586f5a86 
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/software-properties/+bug/2004629/+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 2004629] Re: /usr/bin/software-properties-gtk:dbus.exceptions.DBusException(org.freedesktop.DBus.Error.TimedOut):activate_name_owner:get_name_owner:call_blocking:/usr/bin/softwar

2023-02-03 Thread Sebastien Bacher
Checking individual reports,
https://errors.ubuntu.com/oops/843ca2aa-a161-11ed-abae-fa163e55efd0 as
an example has this in the journal

 dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name
'com.canonical.UbuntuAdvantage': no such name

according to the Depends info ubuntu-advantage-desktop-daemon
1.9~22.04.1 is installed though, which would suggest a local
installation issue?

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

Title:
  /usr/bin/software-properties-
  
gtk:dbus.exceptions.DBusException(org.freedesktop.DBus.Error.TimedOut):activate_name_owner:get_name_owner:call_blocking:/usr/bin/software-
  properties-
  
gtk@100:__init__:init_ubuntu_pro:__init__:get_object:__init__:activate_name_owner:start_service_by_name:call_blocking

Status in software-properties package in Ubuntu:
  New

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.99.27, the problem page at 
https://errors.ubuntu.com/problem/de0fd44b666af99030f3b74b33495cf6586f5a86 
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/software-properties/+bug/2004629/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

2023-02-02 Thread Sebastien Bacher
@Andrzej, right, but the issue is that your session is closing and
that's a probably in a key component as the shell, session manager and
graphical server. Resolving the fact that 'ubuntu-bug', the bug report
helper is being hit by the session closing would not solve your issue.
You should for other .crash reports on your system and probably submit
those

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  Invalid
Status in gtk+3.0 source package in Focal:
  Triaged
Status in apport source package in Lunar:
  Invalid
Status in gtk+3.0 source package in Lunar:
  Triaged

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Stack trace
  ---

  Python:

  ```
File "apport-gtk", line 703, in 
  app = GTKUserInterface(sys.argv)
File "apport-gtk", line 68, in GTKUserInterface.__init__
  self.widgets.add_from_file(
  os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui")
  )
  ```

  StacktraceTop:
   _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319
   gtk_css_value_icon_theme_compute (icon_theme=, 
property_id=, provider=, style=, 
parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84
   gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, 
parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:237
   _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, 
provider=provider@entry=0x0, style=style@entry=0x1e7c320, 
parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
   gtk_css_static_style_new_compute (provider=provider@entry=0x0, 
matcher=matcher@entry=0x0, parent=parent@entry=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:195

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  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: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 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/apport/+bug/1842439/+subscriptions


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

[Touch-packages] [Bug 2004482] Re: /usr/bin/software-properties-gtk:ModuleNotFoundError:/usr/bin/software-properties-gtk@37:/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.

2023-02-01 Thread Sebastien Bacher
** Package changed: software-properties (Ubuntu) => ubuntu-advantage-
tools (Ubuntu)

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

Title:
  /usr/bin/software-properties-
  gtk:ModuleNotFoundError:/usr/bin/software-properties-
  gtk@37:/usr/lib/python3/dist-
  
packages/softwareproperties/gtk/SoftwarePropertiesGtk.py@57:/usr/lib/python3/dist-
  packages/softwareproperties/gtk/UbuntuProPage.py@27:/usr/lib/python3/dist-
  packages/softwareproperties/gtk/DialogUaAttach.py@25

Status in ubuntu-advantage-tools package in Ubuntu:
  New

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.99.9.10, the problem page at 
https://errors.ubuntu.com/problem/4b05d8835016bb4e877825ae6aff4814cbfccabf 
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/ubuntu-advantage-tools/+bug/2004482/+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 2004459] Re: /usr/bin/software-properties-gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection:g

2023-02-01 Thread Sebastien Bacher
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/bin/software-properties-
  
gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection:getaddrinfo:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:get_magic_attach_token_info:request_url:poll_for_magic_token:wait:_wait:_wait:get_magic_attach_token_info

Status in software-properties package in Ubuntu:
  Confirmed

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.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/52f13b0d1d5c75b8a964d28dbe58d616be9fa781 
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/software-properties/+bug/2004459/+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 2004246] Re: /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin/software-properties-gtk@100:__init__:init_ubuntu_pro:__init__

2023-01-31 Thread Sebastien Bacher
Hum, it seems some users don't have a gdk pixbuf loader for svg? Unsure
how can that happens since libgtk-3-0 Depends on librsvg

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

Title:
  /usr/bin/software-properties-
  gtk:gi.repository.GLib.GError:/usr/bin/software-properties-
  gtk@100:__init__:init_ubuntu_pro:__init__

Status in software-properties package in Ubuntu:
  New

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.99.27, the problem page at 
https://errors.ubuntu.com/problem/cbfb777fc32a715242821bd3e89ccae2411c5d94 
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/software-properties/+bug/2004246/+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 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state

2023-01-31 Thread Sebastien Bacher
Nathan, any idea what's going on there?

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_radio_toggled:update_state

Status in software-properties package in Ubuntu:
  New

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.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 
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/software-properties/+bug/2004245/+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 1999299] Re: filename cannot be changed in the "save" dialogue

2023-01-30 Thread Sebastien Bacher
Thank you for the bug report. Do you change the directory as described
on bug #1878076?

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  filename cannot be changed in the "save" dialogue

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Minimum required condition for recreation.

  Ubuntu 20.04
  kernel 5.15.0-53-generic
  Model XPS-13
  Chrome 07.0.5304.121 (Official Build) (64-bit)

  NOTE: that this occurs not just in chrome, but any application that
  uses the system's default save dialogue.

  For example, in Google Chrome, I press Control-S to save a webpage.
  When doing so, a save dialogue appears for specifying the name and
  directory of the file.

  When I press any key to modify the name of a file, a letter is
  inserted into a search window instead of the filename section.

  It occurs in any web browsers or software which use this system's
  default save dialogue for specifying a filename and directory.

  I thought it is a bug in the filesystem (Nautilus). I'm reporting it
  here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1999299/+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 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op

2023-01-27 Thread Sebastien Bacher
** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  /usr/bin/software-properties-
  
gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read

Status in software-properties package in Ubuntu:
  New

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.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 
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/software-properties/+bug/2003996/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

2023-01-26 Thread Sebastien Bacher
Clarifying from a Desktop perspective. Upstream isn't going to care
about the issue because GTK3 isn't actively maintained at this point and
it's not a 'real world issue' in the sense of it's an error that is hit
when the session closes in an unprompted manner, which means no user
would see a visible consequence if it wasn't the crash handler catching
it.

It's a situation that should ideally be resolved and Robert tried to fix
it but the patch needs more work and it's lower priority than other
items so we didn't get to investigate more yet.

One other way would be to teach apport to ignore issues on session
closing (which I think was done some years ago but maybe that isn't
working anymore?)

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  Invalid
Status in gtk+3.0 source package in Focal:
  Triaged
Status in apport source package in Lunar:
  Invalid
Status in gtk+3.0 source package in Lunar:
  Triaged

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Stack trace
  ---

  Python:

  ```
File "apport-gtk", line 703, in 
  app = GTKUserInterface(sys.argv)
File "apport-gtk", line 68, in GTKUserInterface.__init__
  self.widgets.add_from_file(
  os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui")
  )
  ```

  StacktraceTop:
   _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319
   gtk_css_value_icon_theme_compute (icon_theme=, 
property_id=, provider=, style=, 
parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84
   gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, 
parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:237
   _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, 
provider=provider@entry=0x0, style=style@entry=0x1e7c320, 
parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
   gtk_css_static_style_new_compute (provider=provider@entry=0x0, 
matcher=matcher@entry=0x0, parent=parent@entry=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:195

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  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: apport-gtk crashed 

[Touch-packages] [Bug 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one

2023-01-25 Thread Sebastien Bacher
I've tested 0.96.24.32.20 on 18.04, activating ubuntu pro through the
magic workflow, detachig and activating again using the manual token
one, it works as expected, marked as verified on B

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal
** Tags added: verification-done verification-done-bionic 
verification-done-focal

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - until the service is in production to try the magic workflow, edit 
/etc/ubuntu-advantage/uaclient.conf to set
  contract_url: https://contracts.staging.canonical.com
  then 'ua refresh config')
  and use the non staging for token registration

  - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
  (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar

  * Regression Potential

  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one

2023-01-25 Thread Sebastien Bacher
The bionic upload failed to include a recent fix and failed
verification, I uploaded 0.96.24.32.20 to address the problem now

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - until the service is in production to try the magic workflow, edit 
/etc/ubuntu-advantage/uaclient.conf to set
  contract_url: https://contracts.staging.canonical.com
  then 'ua refresh config')
  and use the non staging for token registration

  - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
  (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar

  * Regression Potential

  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one

2023-01-25 Thread Sebastien Bacher
I've tested 0.99.9.10 on 20.04, activating ubuntu pro through the magic
workflow, detachig and activating again using the manual token one, it
works as expected, marked as verified on F

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - until the service is in production to try the magic workflow, edit 
/etc/ubuntu-advantage/uaclient.conf to set
  contract_url: https://contracts.staging.canonical.com
  then 'ua refresh config')
  and use the non staging for token registration

  - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
  (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar

  * Regression Potential

  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one

2023-01-25 Thread Sebastien Bacher
I've tested  0.99.22.5 on 22.04, activating ubuntu pro through the magic
workflow, detachig and activating again using the manual token one, it
works as expected, marked as verified on J

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - until the service is in production to try the magic workflow, edit 
/etc/ubuntu-advantage/uaclient.conf to set
  contract_url: https://contracts.staging.canonical.com
  then 'ua refresh config')
  and use the non staging for token registration

  - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
  (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar

  * Regression Potential

  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one

2023-01-23 Thread Sebastien Bacher
Thanks Steve for the reviews and for pointing out that the strings were
outdated in Lunar, we had some recent tweaks in the Vcs not uploaded to
the archive yet. I've updated the package now, which resolves the 'Enter
code on ubuntu.com/pro/attach' vs 'Log in with Ubuntu One'

We also somehow missed cherrypicking the commit that made 'FIPS 140-2'
not-translatable to stable series. I don't think change that is worth an
upload though since the only problem it could create is if some
translators went out of their way to translate it in a stable serie to
something that doesn't make sense and we can also resolve it by manually
editing the template and reuploading the .pot to launchpad, no need of a
package upload.

I've emailed the translators list to let them know about the new strings
https://lists.ubuntu.com/archives/ubuntu-translators/2023-January/007865.html

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - until the service is in production to try the magic workflow, edit 
/etc/ubuntu-advantage/uaclient.conf to set
  contract_url: https://contracts.staging.canonical.com
  then 'ua refresh config')
  and use the non staging for token registration

  - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
  (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar

  * Regression Potential

  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one

2023-01-20 Thread Sebastien Bacher
** Description changed:

  * Impact
  
  We want desktop integration with Ubuntu Pro, that will also replace the
  custom registration code we had for Livepatch which is integrated with
  the new service
- 
  
  * Test case
  
  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro deteach` if needed
  
- $ software-properties-gtk
+ - until the service is in production to try the magic workflow, edit 
/etc/ubuntu-advantage/uaclient.conf to set
+ contract_url: https://contracts.staging.canonical.com
+ then 'ua refresh config')
+ and use the non staging for token registration
+ 
+ - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'
  
  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have
  other controls inactive
  
  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option
  
  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode
  
  - click 'Confirm'
  -> you should get an authentification prompt
  
  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
- -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
+ -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled 
+ (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)
  
  - check that the '$ pro status' output matches the UI one
  
  - try enabling/disable options
  -> verify that the 'pro status' change accordingly
  
  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore
  
  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar
  
- 
  * Regression Potential
  
  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro deteach` if needed

  - until the service is in production to try the magic workflow, edit 
/etc/ubuntu-advantage/uaclient.conf to set
  contract_url: https://contracts.staging.canonical.com
  then 'ua refresh config')
  and use the non staging for token registration

  - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled 
  (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 

[Touch-packages] [Bug 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one

2023-01-20 Thread Sebastien Bacher
The changes in Lunar,
https://bugs.launchpad.net/ubuntu/+source/software-properties/0.99.30
(with some extra tweaks in the vcs pending upload)

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Released

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  
  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro deteach` if needed

  $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar

  
  * Regression Potential

  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] [NEW] Replace the Livepatch tab by an Ubuntu Pro one

2023-01-20 Thread Sebastien Bacher
Public bug reported:

* Impact

We want desktop integration with Ubuntu Pro, that will also replace the
custom registration code we had for Livepatch which is integrated with
the new service


* Test case

- ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
$ pro status
and `$ pro deteach` if needed

$ software-properties-gtk
-> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

The Ubuntu Pro tab should state 'This machine is not covered by an
Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have
other controls inactive

- click 'Enable Ubuntu Pro'
-> A dialog 'Enable Ubuntu Pro' opens
-> the first option 'Enter code on ubuntu.com/pro/attach' is selected
-> a pincode is displayed under the option

- go to http//ubuntu.com/pro/attach and enter the pincode
-> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

- click 'Confirm'
-> you should get an authentification prompt

- enter your password
-> a spinner starts animating instead of the 'Valid token' label
-> once the attachment job is done the dialog is autoclosed
-> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM 
Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled

- check that the '$ pro status' output matches the UI one

- try enabling/disable options
-> verify that the 'pro status' change accordingly

- Click 'Disable Ubuntu Pro'
-> you get asked for confirmation and password
-> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

- Go through the testcase again but selecting the 'Or add token
manually' option, the steps should be similar


* Regression Potential

There could be problems in the UI
The new service could be not working as expected
Strings are new and currently have no translations

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: Fix Released

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

Title:
   Replace the Livepatch tab by an Ubuntu Pro one

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro, that will also replace
  the custom registration code we had for Livepatch which is integrated
  with the new service

  
  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro deteach` if needed

  $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch'

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps should be similar

  
  * Regression Potential

  There could be problems in the UI
  The new service could be not working as expected
  Strings are new and currently have no translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

2023-01-13 Thread Sebastien Bacher
Let's SRU that change to 22.10

** Description changed:

+ * Impact
+ 
+ Eog can't open high resolution jpg files
+ 
+ * Test Case
+ 
+ - download 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg
+ - try to open the image in eog
+ 
+ * Regression potential
+ 
+ The change increase the memory usage limit for loading jpg, it could
+ lead to put the system under memory pressure. The limit has been added
+ in 22.10 though so it isn't a regression compared to the previous
+ version of Ubuntu
+ 
+ -
+ 
+ 
  Hi,
  
  22.10. Just try to open some .jpg files from my usual storage.
  
  Error interpreting jpeg file ( Backing store not supported. )
  
  Those same pictures open in other OSes ( 22.04, 20.04 and else. )
  
  Can't use those pictures as backgrounds.
  
  But able to open them in Gimp or Shotwell.
  
  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Fix Released
Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  * Impact

  Eog can't open high resolution jpg files

  * Test Case

  - download 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg
  - try to open the image in eog

  * Regression potential

  The change increase the memory usage limit for loading jpg, it could
  lead to put the system under memory pressure. The limit has been added
  in 22.10 though so it isn't a regression compared to the previous
  version of Ubuntu

  -

  
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eog/+bug/1998263/+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 2002212] Re: Outdated version of libglib2.0-dev in Ubuntu Jammy

2023-01-13 Thread Sebastien Bacher
Thank you for your bug report. Updating to a new major serie of glib isn't 
going to be done as a stable update because that wouldn't be a safe update and 
might create build or runtime issues for existing software. 
You probably want to update your code to be compatible with older version of 
glib since that's what most users will still have today, use 
G_APPLICATION_FLAGS_NONE instead of the new default flag for example

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: glib2.0 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Outdated version of libglib2.0-dev in Ubuntu Jammy

Status in glib2.0 package in Ubuntu:
  Won't Fix

Bug description:
  The version of libglib2.0-dev that is currently included in the
  repositories for Ubuntu is 2.72.1-1, which is outdated and missing
  important features and bug fixes. In particular, the
  G_APPLICATION_DEFAULT_FLAGS macro, which was added in GTK+ 3.22, is
  not available in this version of libglib2.0-dev. This is causing
  issues with my application, which requires the use of this macro.

  I request that the package be updated to the latest version (currently
  2.74) in order to resolve this issue.

  Steps to reproduce:
1. Install libglib2.0-dev version 2.72.1-1 on an Ubuntu system
2. Attempt to compile an application that uses the 
G_APPLICATION_DEFAULT_FLAGS macro
3. Observe the compilation error due to the missing macro

  Expected result:
  The application compiles successfully and can be run.

  Actual result:
  The application fails to compile due to the missing 
G_APPLICATION_DEFAULT_FLAGS macro.

  Release:
Description:Ubuntu 22.04.1 LTS
Release:22.04

  Using version:
  2.72.1-1

  Requested version:
  2.74(+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2002212/+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 1915910] Re: evince does not print (apparmor, pxgsettings)

2022-12-14 Thread Sebastien Bacher
could those having the issue also share output of
$ echo $DESKTOP_SESSION
?

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

Title:
  evince does not print (apparmor, pxgsettings)

Status in evince package in Ubuntu:
  Fix Released
Status in libproxy package in Ubuntu:
  Invalid
Status in evince source package in Kinetic:
  Fix Committed
Status in evince package in Debian:
  New

Bug description:
  * Impact

  Evince hangs when opening the printing dialog for some users with a
  remote printer configured and connected

  * Test case

  - configure a remote printer and turn it on
  - open a pdf
  - try to print the document

  the print dialog shouldn't freeze the viewer

  * What could go wrong

  The change is only allowing access to one extra system binary from the
  apparmor profile so shouldn't really have an impact on the software
  behaviour. If the syntax or content of the change was incorrect it
  could make the apparmor profile not been loaded anymore or block
  access to thing that should be allowed, so ensure that opening
  documents, printing and thumbnailing are still working

  --

  
  audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  It seems that evince has no rights to print if I understand this
  correctly

  Printing the same pdf-file from the same origin/folder works with
  OCULAR

  The error is reproduceable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

2022-12-13 Thread Sebastien Bacher
The 1.20 components have been uploaded to the 22.04 SRU queue now.

@oem it would be nice if you could improve the bug description to have a
more detailed testcase and regression potential section

** Description changed:

  * Impact
  
  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.
  
  * Test case
  
- Try connecting to 5G using a FM350 modem
+ - install modemmanager, libmbim, and libqmi from -proposed
+ - reboot and try WWAN function to see if any regression there.
+ - perform dogfooding of its reverse dependencies (network-
+    manager, gnome-control-center etc.)
+ 
+ The verification should be done on FM350 to ensure it's correctly
+ handled but also on other hardware to verify that there are no
+ regressions
  
  * Regression potential
  
  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are no
  regression.
  
- 
  ---
- 
  
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]
  
  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  
  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:
  
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

** Changed in: modemmanager (Ubuntu)
   Importance: Undecided => High

** Changed in: modemmanager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm 

[Touch-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

2022-12-13 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
+ Fibocom FM350 modems aren't working with the current version of
+ modemmanager in 22.04.
+ 
+ * Test case
+ 
+ Try connecting to 5G using a FM350 modem
+ 
+ * Regression potential
+ 
+ The SRU does an update to new modemmanager serie so we should do a
+ complete round of testing on different hardware and confirm there are no
+ regression.
+ 
+ 
+ ---
+ 
+ 
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]
  
  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  
  Modemmanager requires >= 1.19.1, the detail info is in
- lp:1962525 
+ lp:1962525
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:
  
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  Try connecting to 5G using a FM350 modem

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  
  ---

  
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE 

[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)

2022-12-07 Thread Sebastien Bacher
Ok, fix uploaded to Lunar and 22.04 now

** Description changed:

- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED"
- operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-
- gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x"
- denied_mask="x" fsuid=1000 ouid=0
+ * Impact
+ 
+ Evince hangs when opening the printing dialog for some users with a
+ remote printer configured and connected
+ 
+ * Test case
+ 
+ - configure a remote printer and turn it on
+ - open a pdf
+ - try to print the document
+ 
+ the print dialog shouldn't freeze the viewer
+ 
+ * What could go wrong
+ 
+ The change is only allowing access to one extra system binary from the
+ apparmor profile so shouldn't really have an impact on the software
+ behaviour. If the syntax or content of the change was incorrect it could
+ make the apparmor profile not been loaded anymore or block access to
+ thing that should be allowed, so ensure that opening documents, printing
+ and thumbnailing are still working
+ 
+ --
+ 
+ 
+ audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
  
  It seems that evince has no rights to print if I understand this
  correctly
  
  Printing the same pdf-file from the same origin/folder works with OCULAR
  
  The error is reproduceable

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

Title:
  evince does not print (apparmor, pxgsettings)

Status in evince package in Ubuntu:
  Fix Committed
Status in libproxy package in Ubuntu:
  Invalid
Status in evince package in Debian:
  New

Bug description:
  * Impact

  Evince hangs when opening the printing dialog for some users with a
  remote printer configured and connected

  * Test case

  - configure a remote printer and turn it on
  - open a pdf
  - try to print the document

  the print dialog shouldn't freeze the viewer

  * What could go wrong

  The change is only allowing access to one extra system binary from the
  apparmor profile so shouldn't really have an impact on the software
  behaviour. If the syntax or content of the change was incorrect it
  could make the apparmor profile not been loaded anymore or block
  access to thing that should be allowed, so ensure that opening
  documents, printing and thumbnailing are still working

  --

  
  audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  It seems that evince has no rights to print if I understand this
  correctly

  Printing the same pdf-file from the same origin/folder works with
  OCULAR

  The error is reproduceable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1915910] Re: evince does not print (apparmor, pxgsettings)

2022-12-07 Thread Sebastien Bacher
** Changed in: libproxy (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: evince (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: evince (Ubuntu)
   Importance: Undecided => Low

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

Title:
  evince does not print (apparmor, pxgsettings)

Status in evince package in Ubuntu:
  Fix Committed
Status in libproxy package in Ubuntu:
  Invalid
Status in evince package in Debian:
  New

Bug description:
  audit: type=1400 audit(1613557537.646:81): apparmor="DENIED"
  operation="exec" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500
  comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  It seems that evince has no rights to print if I understand this
  correctly

  Printing the same pdf-file from the same origin/folder works with
  OCULAR

  The error is reproduceable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1990200] Re: goa-daemon crashed with SIGABRT

2022-12-07 Thread Sebastien Bacher
it seems installed correctly from that dpkg log yes, thanks for testing!

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

Title:
  goa-daemon crashed with SIGABRT

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in librest package in Ubuntu:
  Fix Released
Status in librest source package in Kinetic:
  Fix Committed

Bug description:
  * Impact

  The gnome-online-accounts sometime crash after resuming from suspend

  * Test case

  Install the librest update, restart your system and verify that
  configured online accounts keep working. Taking a Google account
  example, calendar events should show in gnome-calendar and the top
  panel widget, evolution should list your email account and nautilus
  should be able to browse your gdrive folder.

  We should also confirm that error reports stop with the library update

  * Regression potential

  The patch makes the code better handle an empty payload. The librest
  rdepends in the archive are gnome-initial-setup/gnome-online-
  accounts/gnome-maps so we should verify that those keep working as
  expected.

  -

  Unknown cause of this crash.  Was alerted to it after waking the
  system from sleep mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.45.2-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Mon Sep 19 19:26:29 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2022-09-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+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 1997360] Re: Update from git snapshot to stable 1.20

2022-12-07 Thread Sebastien Bacher
Yes they have hardware that will be used for the verification, thanks!

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

Title:
  Update from git snapshot to stable 1.20

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Kinetic:
  Fix Committed
Status in libqmi source package in Kinetic:
  Fix Committed
Status in modemmanager source package in Kinetic:
  Fix Committed

Bug description:
  * Impact

  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and
  fixing some issues found during the serie stabilization.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection

  The testing should be done on a variety of hardware from 3G to 5G
  modems.

  * Regression potential

  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.

  Details of the changes in libqmi
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775

  Details of the changes in libmbim
  
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571

  Details of the changes in modemmanager
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5

  The Kinetic SRU is an intermediate step, the goal is to update 22.04
  from 1.18 to 1.20 as part of new hardware enablement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken

2022-12-06 Thread Sebastien Bacher
@Stephan, thanks for the update. I'm not going to close it as invalid
because as pointed out by people previously it seems the font didn't
have the issue in past series, even if the setting is non standard and
the priority low as a result there might still be an issue there.

** Changed in: gnome-font-viewer (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: fonts-dejavu (Ubuntu)
   Importance: Undecided => Low

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Invalid

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+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 1988230] Re: glib 2.73 breaks modemmanager

2022-12-06 Thread Sebastien Bacher
** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  glib 2.73 breaks modemmanager

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Invalid
Status in modemmanager package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  I'm filing this bug in case we want to fix it before letting glib 2.73
  in to kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1988230/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken

2022-12-02 Thread Sebastien Bacher
Could someone perhaps try to report the problem on
https://github.com/fontforge/fontforge/issues ?

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+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 1844897] Re: wifi icon has question mark in it even though network is fine

2022-12-02 Thread Sebastien Bacher
There was some issues with the connectivity server returning
inconsistent statuses, that has been fixed now, could you check if that
resolves the flaky indicator issue for you maybe?

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

Title:
  wifi icon has question mark in it even though network is fine

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After experiencing some "turbulence" in my wifi (I rebooted my primary
  wifi router, which caused my laptop to fallback onto a secondary
  access point which didn't have full connectivity until the primary
  router finished rebooting, then I rebooted the primary router a second
  time), the wifi icon in my top bar stayed as the question-mark icon
  (i.e., the icon that shows when Network Manager doesn't think you have
  full connectivity) even after everything was back up and in fact my
  connectivity was fine.

  Turning wifi off and back on did not cause the question mark to go
  away. Restarting Network Manager did not cause the question mark to go
  away. Switching to a different wifi network and then back to the
  previous one didn't cause the question mark to go away. I had to
  reboot my laptop to get the question mark to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  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: Sat Sep 21 18:35:48 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.2   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/1844897/+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 1997569] Re: Merge alsa-utils 1.2.7 from Debian unstable

2022-12-02 Thread Sebastien Bacher
Thanks Nathan, I've uploaded now (rebased on 1.2.8 which was uploaded to
Debian while that request was waiting for review)

** Changed in: alsa-utils (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Merge alsa-utils 1.2.7 from Debian unstable

Status in alsa-utils package in Ubuntu:
  Fix Committed

Bug description:
  Please merge alsa-utils 1.2.7 from Debian unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1997569/+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 1086783] Re: New PolicyKit 0.106 changes configuration file format

2022-12-02 Thread Sebastien Bacher
Removing the block tag since we agreed to move forward with updating now
that there is a duketap backend

** Tags removed: version-blocked

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

Title:
  New PolicyKit 0.106 changes configuration file format

Status in policykit-1 package in Ubuntu:
  Triaged
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  From the NEWS file:

  This is polkit 0.106. There's a major change in this release which is
  a switch from .pkla files (keyfile-format) to .rules files
  (JavaScript).

  We may want to hold off on the new version because it requires
  rewriting the configuration files, and adds a dependency on mozjs185,
  which will need a MIR (and getting a MIR may be problematic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+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 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed

2022-11-28 Thread Sebastien Bacher
Thanks, the upstream bug reference is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1147

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1147
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1147

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1147
   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/1997553

Title:
  network-manager fails to trigger dispatcher scripts with action
  dhcp4-change when dhcp lease is renewed

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  We rely on network-manager dispatcher scripts on our desktop and
  laptop computers. The dispatcher scripts are used to update DNS
  records with nsupdate when the dhcp lease is renewed.

  With jammy this is not working anymore. It seems that dispatcher
  scripts are run only when the interface comes up (with action 'up')
  and with the initial dhcp lease (with action 'dhcp4-change'), but when
  the lease is renewed, the dispatcher scripts are not run with any
  action. The only action the dispatcher scripts are run regularly with
  is 'connectivity-change', which seems to occur twice in a row every
  few hours.

  I have made a simple script to log how the dispatcher scripts are run:
  /etc/NetworkManager/dispatcher.d/99-test:
  #!/bin/bash
  PATH='/bin:/sbin:/usr/bin:/usr/sbin'

  echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log

  This script proves that action 'dhcp4-change' only occurs when I
  manually restart NetworkManager.service or unplug and replug the
  ethernet cable.


  network-manager version: 1.36.6-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1997553/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

2022-11-28 Thread Sebastien Bacher
Thank you for your bug report but that's the Ubuntu tracker, report Mint
issues to them

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

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not and not from anything 
I count identify that I did.

  inxi -EbA

  System:
Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed

2022-11-25 Thread Sebastien Bacher
Thank you for your bug report, could you report it upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues ?

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

Title:
  network-manager fails to trigger dispatcher scripts with action
  dhcp4-change when dhcp lease is renewed

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  We rely on network-manager dispatcher scripts on our desktop and
  laptop computers. The dispatcher scripts are used to update DNS
  records with nsupdate when the dhcp lease is renewed.

  With jammy this is not working anymore. It seems that dispatcher
  scripts are run only when the interface comes up (with action 'up')
  and with the initial dhcp lease (with action 'dhcp4-change'), but when
  the lease is renewed, the dispatcher scripts are not run with any
  action. The only action the dispatcher scripts are run regularly with
  is 'connectivity-change', which seems to occur twice in a row every
  few hours.

  I have made a simple script to log how the dispatcher scripts are run:
  /etc/NetworkManager/dispatcher.d/99-test:
  #!/bin/bash
  PATH='/bin:/sbin:/usr/bin:/usr/sbin'

  echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log

  This script proves that action 'dhcp4-change' only occurs when I
  manually restart NetworkManager.service or unplug and replug the
  ethernet cable.


  network-manager version: 1.36.6-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1997553/+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 1844897] Re: wifi icon has question mark in it even though network is fine

2022-11-24 Thread Sebastien Bacher
could you check what's the output of

$ nmcli networking connectivity check

while you see the issue?


do you get the problem while using a VPN to only access some resources? 

if so it might be fixed with
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/e6dac4f0

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

Title:
  wifi icon has question mark in it even though network is fine

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After experiencing some "turbulence" in my wifi (I rebooted my primary
  wifi router, which caused my laptop to fallback onto a secondary
  access point which didn't have full connectivity until the primary
  router finished rebooting, then I rebooted the primary router a second
  time), the wifi icon in my top bar stayed as the question-mark icon
  (i.e., the icon that shows when Network Manager doesn't think you have
  full connectivity) even after everything was back up and in fact my
  connectivity was fine.

  Turning wifi off and back on did not cause the question mark to go
  away. Restarting Network Manager did not cause the question mark to go
  away. Switching to a different wifi network and then back to the
  previous one didn't cause the question mark to go away. I had to
  reboot my laptop to get the question mark to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  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: Sat Sep 21 18:35:48 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.2   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/1844897/+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 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep

2022-11-24 Thread Sebastien Bacher
It's not likely that we can build pandoc on i386, it would require
starting building the haskell stack there, someone probably needs to
patch flac to not build with pandoc on i386

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

Title:
  flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing
  pandoc build dep

Status in flac package in Ubuntu:
  New

Bug description:
  flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing
  pandoc build dep which is not built in Ubuntu for i386

  https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410

  Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as
  B-D"

  This prevents migration of flac (if/once tests succeed), and will
  block migration of packages that now build in proposed and depend on
  the bumped libs in flac 1.4 (libflac++10 and libflac12)

  https://people.canonical.com/~ubuntu-archive/proposed-
  migration/update_excuses.html#flac

  e.g.amongst several others so far

  https://people.canonical.com/~ubuntu-archive/proposed-
  migration/update_excuses.html#kwave

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+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 1997338] Re: libdbus-1-3 uninstallable on autopkgtest

2022-11-23 Thread Sebastien Bacher
** Changed in: dbus (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  libdbus-1-3 uninstallable on autopkgtest

Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz

  Starting pkgProblemResolver with broken count: 9
  Starting 2 pkgProblemResolver with broken count: 9
  Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib >
  Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 
@un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32
Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32
  Investigating (0) libqt5dbus5:i386 < none -> 5.15.6+dfsg-1 @un puN Ib >
  Broken libqt5dbus5:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 
@un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4
Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4
  Investigating (0) libpulse0:i386 < none -> 1:16.1+dfsg1-1ubuntu3 @un puN Ib >
  Broken libpulse0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 
@un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4
Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4
  Investigating (0) libavahi-client3:i386 < none -> 0.8-6ubuntu1 @un puN Ib >
  Broken libavahi-client3:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2
Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2
  Investigating (0) libatspi2.0-0:i386 < none -> 2.46.0-3 @un puN Ib >
  Broken libatspi2.0-0:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0
Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0
  Investigating (0) vlc-plugin-base:i386 < none -> 3.0.17.4-5 @un puN Ib >
  Broken vlc-plugin-base:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0
Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0
  Investigating (0) libfluidsynth3:i386 < none -> 2.2.8-1 @un puN Ib >
  Broken libfluidsynth3:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0
Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0
  Investigating (0) libatk-bridge2.0-0:i386 < none -> 2.46.0-3 @un puN Ib >
  Broken libatk-bridge2.0-0:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0
Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0
  Investigating (0) libdebuginfod1:i386 < none -> 0.187-4 @un puN Ib >
  Broken libdebuginfod1:i386 Depends on libcurl3-gnutls:i386 < none | 7.85.0-1 
@un uH > (>= 7.28.0)
Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0
Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0
  Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is 
not going to be installed
   libatspi2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
   libavahi-client3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
   libdebuginfod1:i386 : Depends: libcurl3-gnutls:i386 (>= 7.28.0) but it is 
not going to be installed
   libfluidsynth3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
   libpulse0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going 
to be installed
   libqt5dbus5:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going 
to be installed
   libvlccore9:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going 
to be installed
   vlc-plugin-base:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.
  autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt 
install on test deps directly for further data about failing dependencies in 
test logs
  

[Touch-packages] [Bug 1997338] Re: libdbus-1-3 uninstallable on autopkgtest

2022-11-22 Thread Sebastien Bacher
The issue is that the current base image was built on kinetic and
included dbus binaries from kinetic-security which are newer than what
is in lunar, or the lunar env doesn't enable proposed anymore. We are
talking to the autopkgtest team about regenerating an image on lunar

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

Title:
  libdbus-1-3 uninstallable on autopkgtest

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz

  Starting pkgProblemResolver with broken count: 9
  Starting 2 pkgProblemResolver with broken count: 9
  Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib >
  Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 
@un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32
Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32
  Investigating (0) libqt5dbus5:i386 < none -> 5.15.6+dfsg-1 @un puN Ib >
  Broken libqt5dbus5:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 
@un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4
Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4
  Investigating (0) libpulse0:i386 < none -> 1:16.1+dfsg1-1ubuntu3 @un puN Ib >
  Broken libpulse0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 
@un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4
Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4
  Investigating (0) libavahi-client3:i386 < none -> 0.8-6ubuntu1 @un puN Ib >
  Broken libavahi-client3:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2
Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2
  Investigating (0) libatspi2.0-0:i386 < none -> 2.46.0-3 @un puN Ib >
  Broken libatspi2.0-0:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0
Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0
  Investigating (0) vlc-plugin-base:i386 < none -> 3.0.17.4-5 @un puN Ib >
  Broken vlc-plugin-base:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0
Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0
  Investigating (0) libfluidsynth3:i386 < none -> 2.2.8-1 @un puN Ib >
  Broken libfluidsynth3:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0
Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0
  Investigating (0) libatk-bridge2.0-0:i386 < none -> 2.46.0-3 @un puN Ib >
  Broken libatk-bridge2.0-0:i386 Depends on libdbus-1-3:i386 < none | 
1.14.0-2ubuntu2 @un uH > (>= 1.9.14)
Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0
Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0
  Investigating (0) libdebuginfod1:i386 < none -> 0.187-4 @un puN Ib >
  Broken libdebuginfod1:i386 Depends on libcurl3-gnutls:i386 < none | 7.85.0-1 
@un uH > (>= 7.28.0)
Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0
Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0
  Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is 
not going to be installed
   libatspi2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
   libavahi-client3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
   libdebuginfod1:i386 : Depends: libcurl3-gnutls:i386 (>= 7.28.0) but it is 
not going to be installed
   libfluidsynth3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
   libpulse0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going 
to be installed
   libqt5dbus5:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going 
to be installed
   libvlccore9:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going 
to be installed
   vlc-plugin-base:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
  E: Unable to correct 

[Touch-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT

2022-11-22 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ 
+ The gnome-online-accounts sometime crash after resuming from suspend
+ 
+ 
+ * Test case
+ 
+ Install the gnome-online-accounts update, restart your system and verify
+ that configured online accounts keep working. Taking a Google account
+ example, calendar events should show in gnome-calendar and the top panel
+ widget, evolution should list your email account and nautilus should be
+ able to browse your gdrive folder.
+ 
+ 
+ * Regression potential
+ 
+ The patch makes the code better handle an empty payload. The librest
+ rdepends in the archive are gnome-initial-setup/gnome-online-
+ accounts/gnome-maps so we should verify that those keep working as
+ expected.
+ 
+ -
+ 
  Unknown cause of this crash.  Was alerted to it after waking the system
  from sleep mode.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.45.2-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Mon Sep 19 19:26:29 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2022-09-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
-  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  () at /lib/x86_64-linux-gnu/librest-1.0.so.0
-  rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
-  () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
+  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /lib/x86_64-linux-gnu/librest-1.0.so.0
+  rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
+  () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

** Description changed:

  * Impact
  
  The gnome-online-accounts sometime crash after resuming from suspend
  
- 
  * Test case
  
- Install the gnome-online-accounts update, restart your system and verify
- that configured online accounts keep working. Taking a Google account
+ Install the librest update, restart your system and verify that
+ configured online accounts keep working. Taking a Google account
  example, calendar events should show in gnome-calendar and the top panel
  widget, evolution should list your email account and nautilus should be
  able to browse your gdrive folder.
- 
  
  * Regression potential
  
  The patch makes the code better handle an empty payload. The librest
  rdepends in the archive are gnome-initial-setup/gnome-online-
  accounts/gnome-maps so we should verify that those keep working as
  expected.
  
  -
  
  Unknown cause of this crash.  Was alerted to it after waking the system
  from sleep mode.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.45.2-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Mon Sep 19 19:26:29 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2022-09-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

** Description changed:

  * Impact
  
  The gnome-online-accounts sometime crash after resuming from suspend
  
  * Test case
  
  Install the librest update, restart your system and verify that
  configured online accounts keep working. Taking a Google account
  example, calendar events should show in 

[Touch-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT

2022-11-22 Thread Sebastien Bacher
** Also affects: librest (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: librest (Ubuntu)
   Importance: Undecided => High

** Changed in: librest (Ubuntu)
   Status: New => Fix Committed

** Changed in: librest (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  goa-daemon crashed with SIGABRT

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in librest package in Ubuntu:
  Fix Committed

Bug description:
  Unknown cause of this crash.  Was alerted to it after waking the
  system from sleep mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.45.2-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Mon Sep 19 19:26:29 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2022-09-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+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 1997360] Re: Update from git snapshot to stable 1.20

2022-11-22 Thread Sebastien Bacher
** Description changed:

  * Impact
  
  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and fixing
  some issues found during the serie stabilization.
  
  * Test case
  
  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection
  
  The testing should be done on a variety of hardware from 3G to 5G
  modems.
  
  * Regression potential
  
  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.
  
  Details of the changes in libqmi
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775
  
  Details of the changes in libmbim
  
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571
+ 
+ Details of the changes in modemmanager
+ 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5
+ 
+ The Kinetic SRU is an intermediate step, the goal is to update 22.04
+ from 1.18 to 1.20 as part of new hardware enablement

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

Title:
  Update from git snapshot to stable 1.20

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and
  fixing some issues found during the serie stabilization.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection

  The testing should be done on a variety of hardware from 3G to 5G
  modems.

  * Regression potential

  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.

  Details of the changes in libqmi
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775

  Details of the changes in libmbim
  
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571

  Details of the changes in modemmanager
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/compare/90fb43ff...d4fcb2a5

  The Kinetic SRU is an intermediate step, the goal is to update 22.04
  from 1.18 to 1.20 as part of new hardware enablement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] Re: Update from git snapshot to stable 1.20

2022-11-22 Thread Sebastien Bacher
** Description changed:

  * Impact
  
  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and fixing
  some issues found during the serie stabilization.
  
  * Test case
  
  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection
  
  The testing should be done on a variety of hardware from 3G to 5G
  modems.
  
  * Regression potential
  
  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.
  
  Details of the changes in libqmi
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775
+ 
+ Details of the changes in libmbim
+ 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571

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

Title:
  Update from git snapshot to stable 1.20

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and
  fixing some issues found during the serie stabilization.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection

  The testing should be done on a variety of hardware from 3G to 5G
  modems.

  * Regression potential

  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.

  Details of the changes in libqmi
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775

  Details of the changes in libmbim
  
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/compare/f9ea6778...3c2f2571

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] Re: Update from git snapshot to stable 1.20

2022-11-22 Thread Sebastien Bacher
** Description changed:

  * Impact
  
  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and fixing
  some issues found during the serie stabilization.
  
  * Test case
  
  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection
  
  The testing should be done on a variety of hardware from 3G to 5G
  modems.
  
  * Regression potential
  
  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.
+ 
+ Details of the changes in libqmi
+ 
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775

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

Title:
  Update from git snapshot to stable 1.20

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and
  fixing some issues found during the serie stabilization.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection

  The testing should be done on a variety of hardware from 3G to 5G
  modems.

  * Regression potential

  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.

  Details of the changes in libqmi
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/compare/c40cd273...d0973775

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] Re: Update from git snapshot to stable 1.20

2022-11-22 Thread Sebastien Bacher
** Also affects: libqmi (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libqmi (Ubuntu)
   Status: New => Fix Released

** Changed in: libqmi (Ubuntu)
   Importance: Undecided => High

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

** Changed in: libmbim (Ubuntu)
   Importance: Undecided => High

** Changed in: libmbim (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update from git snapshot to stable 1.20

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and
  fixing some issues found during the serie stabilization.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection

  The testing should be done on a variety of hardware from 3G to 5G
  modems.

  * Regression potential

  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1997360/+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 1997360] [NEW] Update from git snapshot to stable 1.20

2022-11-22 Thread Sebastien Bacher
Public bug reported:

* Impact

We did a git snapshot before Kinetic feature freeze on oem request to
add support for newer hardware but upstream didn't roll out stable
tarballs before release. The stable release is available now and fixing
some issues found during the serie stabilization.

* Test case

- install modemmanager, libmbim, and libqmi from -proposed
- restart the system
- try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection

The testing should be done on a variety of hardware from 3G to 5G
modems.

* Regression potential

The stack is limited to modems handling so if there is a regression it
is to be in the handling of those devices.

** Affects: modemmanager (Ubuntu)
 Importance: High
 Status: Fix Released

** Changed in: modemmanager (Ubuntu)
   Status: New => Fix Released

** Changed in: modemmanager (Ubuntu)
   Importance: Undecided => High

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

Title:
  Update from git snapshot to stable 1.20

Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  We did a git snapshot before Kinetic feature freeze on oem request to
  add support for newer hardware but upstream didn't roll out stable
  tarballs before release. The stable release is available now and
  fixing some issues found during the serie stabilization.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - restart the system
  - try to connect from GNOME using a SIM card, ensure the top bar indicator 
reflects the status and that the settings panel shows the correct properties 
for the connection

  The testing should be done on a variety of hardware from 3G to 5G
  modems.

  * Regression potential

  The stack is limited to modems handling so if there is a regression it
  is to be in the handling of those devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1997360/+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 1997201] Re: BlueZ 5.66 release

2022-11-22 Thread Sebastien Bacher
** Tags added: upgrade-software-version

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

Title:
  BlueZ 5.66 release

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Release to Lunar:

  http://www.bluez.org/release-of-bluez-5-66/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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 1815036] Re: uri defined for connectivity check does not have IPv6 address

2022-11-17 Thread Sebastien Bacher
The connectivity server does handle IPv6 now

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  uri defined for connectivity check does not have IPv6 address

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  As per subject. This package defines the file
  /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which
  defines the uri for the connectivity check to be http://connectivity-
  check.ubuntu.com

  This hostname does not resolve to an IPv6 address. Therefore, even if
  the user has fully working IPv6, the connectivity check for IPv6 will
  fail. As a result, the IPv6 default routes will be heavily
  deprioritised (ie: having 2 added to the metric) rendering them
  effectively inoperable absent a deliberate effort to use IPv6-only
  addresses.

  NB: This was discovered by-the-by during reporting of bug #1814262
  upstream at
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448

  It seems to be irrelevant to the main thrust of that bug, which is
  that IPv4 wired routes are not being identified as working correctly.
  In fact, when I switch to network-manager-config-connectivity-debian,
  the hostname defined there *does* have a working IPv6 address, and the
  issue actually being reported in that other bug does not affect the
  IPv6 routes, only the IPv4 ones.

  The bug here probably doesn't need any change made to the package
  itself, but rather to the networking of the actual target URL. It
  needs an IPv6 () DNS record, and for it to function on that
  address.

  I note in passing the debian connectivity check URL resolves to
  several IP addresses - four IPv4 addresses and 3 IPv6 addresses,
  presumably geographically diverse. (It's actually a CNAME to
  static.debian.org) This looks like it would be a more reliable target
  for connectivity checks. The ubuntu URL only resolves to a single IPv4
  address.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager-config-connectivity-ubuntu 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 12:35:24 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (148 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 100 
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-01-13 (24 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.15.2   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/1815036/+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 1995891] Re: look utility failing

2022-11-08 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1971425 ***
https://bugs.launchpad.net/bugs/1971425

thank you for the bug report, it seems the same issue than bug #1971425

** This bug has been marked a duplicate of bug 1971425
   The "look" cli dictionary only sees capitalized words

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

Title:
  look utility failing

Status in util-linux package in Ubuntu:
  New

Bug description:
  The look utility has more or less stopped working, i.e. it finds
  results for some words but not others.

  Example: look answ, among many others, returns nothing while a grep of
  /usr/share/dict/words returns matches.

  All the links to /usr/share/dict/words appear to be correct.

  This happens on Ubuntu 22.04.1 LTS on both X86_64 and aarch64 for
  bsdextrautils 2.37.2-4ubuntu3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1995891/+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 1993870] Re: WiFi setting has no visible networks (Intel Wireless-AC 9560)

2022-11-07 Thread Sebastien Bacher
Thank you for your bug report, could you give the output of

$ dpkg -l wpasupplicant iwd

also could you add the 'journalctl -b 0' log from a session showing the
issue?

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  WiFi setting has no visible networks (Intel Wireless-AC 9560)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  With ubuntu 22.10, I can not see any AP in WiFi setting. It's ok on
  previous versions. The driver is okay since I can scan with iwlist
  tool. Below are more details.

  $ sudo lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.10
  Release:  22.10
  Codename: kinetic

  $ ifconfig
  enx5e80011fa4e9: flags=4163  mtu 1500
  inet 192.168.42.116  netmask 255.255.255.0  broadcast 192.168.42.255
  inet6 fe80::cd60:eccc:f8d7:21e6  prefixlen 64  scopeid 0x20
  ether 5e:80:01:1f:a4:e9  txqueuelen 1000  (Ethernet)
  RX packets 432320  bytes 621981996 (621.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 186680  bytes 22769110 (22.7 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 11354  bytes 24889535 (24.8 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 11354  bytes 24889535 (24.8 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  wlp0s20f3: flags=4099  mtu 1500
  ether 18:1d:ea:ed:34:16  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  $ sudo iwlist wlp0s20f3 scan
  wlp0s20f3  Scan completed :
    Cell 01 - Address: D0:79:80:DA:4F:F3
  Channel:1
  Frequency:2.412 GHz (Channel 1)
  Quality=29/70  Signal level=-81 dBm
  Encryption key:on
  ESSID:"CMCC-7S6H"
  Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
  Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
  Mode:Master
  Extra:tsf=00e793b8a899
  Extra: Last beacon: 2164ms ago
  IE: Unknown: 0009434D43432D37533648
  IE: Unknown: 010882848B962430486C
  IE: Unknown: 030101
  IE: Unknown: 23021100
  IE: Unknown: 2A0104
  IE: Unknown: 32040C121860
  IE: IEEE 802.11i/WPA2 Version 1
  Group Cipher : CCMP
  Pairwise Ciphers (1) : CCMP
  Authentication Suites (1) : PSK
  IE: Unknown: 0B0539
  IE: Unknown: 7F0804000840
  IE: Unknown: 
DD7E0050F204104A0001101044000102103B000103104700105D2DBCBB9D644948047E083B1A419A72102100094669626572686F6D65102300094669626572686F6D651024000631323334353610420004313233341054000800060050F20400011011000B4669626572686F6D6541501008000220081049000600372A000120
  IE: Unknown: DD0A001018020C01
  IE: WPA Version 1
  Group Cipher : CCMP
  Pairwise Ciphers (1) : CCMP
  Authentication Suites (1) : PSK
  IE: Unknown: 
DD180050F20201018C0003A227A442435E0062322F00
    Cell 02 - Address: FC:DD:65:2B:6B:52
  

  $ sudo dmesg | grep iwl
  [2.816274] iwlwifi :00:14.3: WRT: Overriding region id 0
  [2.816285] iwlwifi :00:14.3: WRT: Overriding region id 1
  [2.816289] iwlwifi :00:14.3: WRT: Overriding region id 2
  [2.816293] iwlwifi :00:14.3: WRT: Overriding region id 3
  [2.816297] iwlwifi :00:14.3: WRT: Overriding region id 4
  [2.816300] iwlwifi :00:14.3: WRT: Overriding region id 6
  [2.816304] iwlwifi :00:14.3: WRT: Overriding region id 8
  [2.816307] iwlwifi :00:14.3: WRT: Overriding region id 9
  [2.816311] iwlwifi :00:14.3: WRT: Overriding region id 10
  [2.816314] iwlwifi :00:14.3: WRT: Overriding region id 11
  [2.816318] iwlwifi :00:14.3: WRT: Overriding region id 15
  [2.816322] iwlwifi :00:14.3: WRT: Overriding region id 16
  [2.816326] iwlwifi :00:14.3: WRT: Overriding region 

[Touch-packages] [Bug 1995761] Re: Xorg crash

2022-11-07 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Display suddenly goes black and ubuntu restarts and logins back to
  desktop screen

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Nov  5 22:11:42 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0]
  MachineType: ASUSTeK COMPUTER INC. UX310UAK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX310UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX310UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX310UAK.312:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX310UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  xserver.bootTime: Sat Nov  5 22:03:57 2022
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:21.1.3-2ubuntu2.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995761/+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 1995761] Re: Xorg crash

2022-11-07 Thread Sebastien Bacher
Is there steps you can follow to trigger the issue?

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Display suddenly goes black and ubuntu restarts and logins back to
  desktop screen

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Nov  5 22:11:42 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0]
  MachineType: ASUSTeK COMPUTER INC. UX310UAK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX310UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX310UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX310UAK.312:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX310UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  xserver.bootTime: Sat Nov  5 22:03:57 2022
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:21.1.3-2ubuntu2.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995761/+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 1995766] Re: X server segfault when starting youtube videos

2022-11-07 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  X server segfault when starting youtube videos

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This is an intermittent bug; happens perhaps 1-3 times a week. Always
  when just starting to play a youtube videos (I haven't seen it playing
  videos on other sites, or locally, but the sample size is skewed.) I'm
  using Nvidia drivers with a 6GB 1060 GTX running three monitors.
  Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around
  5 or 6% usage. System RAM is 16GB, also not stressed (10-15%).

  Stack trace in Xorg.0.log.old is always the same:

  [  1890.850] (EE) 
  [  1890.850] (EE) Backtrace:
  [  1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9]
  [  1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x7f40d5da5520]
  [  1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) 
[0x558c41efb1e9]
  [  1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) 
[0x558c41efcc85]
  [  1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) 
[0x558c41efd183]
  [  1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) 
[0x558c41efe183]
  [  1890.853] (EE) 6: /usr/lib/xorg/Xorg 
(InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d]
  [  1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) 
[0x558c42006e4c]
  [  1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) 
[0x558c4121]
  [  1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) 
[0x558c4200011e]
  [  1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60]
  [  1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) 
[0x558c4205fee8]
  [  1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) 
[0x558c41ef0257]
  [  1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524]
  [  1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_init_first+0x90) [0x7f40d5d8cd90]
  [  1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0x80) [0x7f40d5d8ce40]
  [  1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5]
  [  1890.855] (EE) 
  [  1890.855] (EE) Segmentation fault at address 0x7ffec8965000
  [  1890.855] (EE) 
  Fatal server error:
  [  1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.141.03  Thu Jun 30 
18:45:31 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Nov  5 10:27:18 2022
  DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 

[Touch-packages] [Bug 1995783] Re: Nightlight fails after suspend

2022-11-07 Thread Sebastien Bacher
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Nightlight fails after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Nightlight activates when turned on in settings but after closing the
  lid or otherwise suspending and then resuming power nightlight fails
  to change the color temperature.  Settings still indicates that
  nightlight is on.  If nightlight setting is cycled nightlight works
  again until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.154  Wed Jun 22 04:50:54 
UTC 2022
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1)
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  5 22:03:14 2022
  DistUpgraded: 2022-10-29 22:31:31,858 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/390.154, 5.15.0-52-generic, x86_64: installed
   nvidia/390.154, 5.19.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:212b]
   NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:1247] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 635M [1043:212b]
  InstallationDate: Installed on 2019-01-15 (1390 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUSTeK Computer Inc. N55SL
  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.19.0-23-generic 
root=UUID=47b67201-d4ee-44d7-adec-9d457d3c9b5c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (6 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SL.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SL
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN55SL.204:bd10/24/2012:br4.6:svnASUSTeKComputerInc.:pnN55SL:pvr1.0:rvnASUSTeKComputerInc.:rnN55SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
  dmi.product.family: N
  dmi.product.name: N55SL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995783/+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 1957909] Re: NetworkManager connectivity check fails

2022-11-07 Thread Sebastien Bacher
Could be transient issues with one of the servers as described in
https://discourse.ubuntu.com/t/network-manager-connectivity-check-
problem/ though we haven't got reports of the problem recently...

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  NetworkManager connectivity check fails

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I randomly receive "No internet connection available" notification,
  even if my internet connection is stable. (Not the exact term)

  In /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf the endpoint 
  http://connectivity-check.ubuntu.com./
  is used. I manually pinged the endpoint.
  I live in europe and the server is located in the US. The latency is about 
160ms. Usually I have an approximate latency of 15ms.
  It is not a problem of my ISP, I receive this notification on different 
locations in Germany and Switzerland.

  I propose to use another endpoint or provide another server for the same 
endpoint for europe.
  So the DNS servers in europe provide the IP of a server located in europe.

  The config comes from the package "network-manager-config-
  connectivity-ubuntu" version 1.32.12-0ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1957909/+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 1995650] Re: Trivial: Unclosed tag in distro.py

2022-11-04 Thread Sebastien Bacher
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Trivial: Unclosed  tag in distro.py

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Hi, distro.py, line: 37 starts with a  tag but does not close it.

  The code is here:

  
  return(_("To improve the user experiece of Debian please take "
   "part in the popularity contest. If you do so the list of "
   "installed software and how often it was used will be "
   "collected and sent anonymously to the Debian project.\n\n"
   "The results are used to optimise the layout of the "
   "installation CDs."))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995650/+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 1993785] Re: Wrong loader path defined in pkgconfig

2022-11-01 Thread Sebastien Bacher
Installing libgdk-pixbuf-2.0-dev 2.42.8+dfsg-1ubuntu0.2

$ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders

$ ls -lh /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
-rwxr-xr-x 1 root root 15K říj 21 09:26 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders

The pixbuf loaders are still working as expected in for example the
filemanager or viewer

Marked as verified

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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

Title:
  Wrong loader path defined in pkgconfig

Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  The .pc references to a wrong location for the loaders binary. That's
  because the file is moved from the packaging .install which the build
  system doesn't know about.

  
  * Testcase

  $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0

  should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-
  query-loaders' matching where the file is installed

  
  * What could go wrong

  The change is only patching the .pc there is no code change. If the
  patch was wrong the path returned could still not match the actual
  binary location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 1993785] Re: Wrong loader path defined in pkgconfig

2022-10-21 Thread Sebastien Bacher
The bug has already been fixed in Debian and Kinetic
https://tracker.debian.org/news/1349533/accepted-gdk-pixbuf-2428dfsg-2-source-into-unstable/

** Changed in: gdk-pixbuf (Ubuntu)
   Importance: Undecided => Low

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Fix Released

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

Title:
  Wrong loader path defined in pkgconfig

Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The .pc references to a wrong location for the loaders binary. That's
  because the file is moved from the packaging .install which the build
  system doesn't know about.

  
  * Testcase

  $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0

  should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-
  query-loaders' matching where the file is installed

  
  * What could go wrong

  The change is only patching the .pc there is no code change. If the
  patch was wrong the path returned could still not match the actual
  binary location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 1993785] [NEW] Wrong loader path defined in pkgconfig

2022-10-21 Thread Sebastien Bacher
Public bug reported:

* Impact

The .pc references to a wrong location for the loaders binary. That's
because the file is moved from the packaging .install which the build
system doesn't know about.


* Testcase

$ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0

should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-
query-loaders' matching where the file is installed


* What could go wrong

The change is only patching the .pc there is no code change. If the
patch was wrong the path returned could still not match the actual
binary location

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Low
 Status: Fix Released

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

Title:
  Wrong loader path defined in pkgconfig

Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The .pc references to a wrong location for the loaders binary. That's
  because the file is moved from the packaging .install which the build
  system doesn't know about.

  
  * Testcase

  $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0

  should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-
  query-loaders' matching where the file is installed

  
  * What could go wrong

  The change is only patching the .pc there is no code change. If the
  patch was wrong the path returned could still not match the actual
  binary location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 1993037] Re: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course

2022-10-18 Thread Sebastien Bacher
Thank you for your bug report, the description fails to mention the
Ubuntu serie you are using? assuming it's 22.04 but please either use
ubuntu-bug or include details in the futur

** Tags added: rls-jj-incoming

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

Title:
  Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-
  cron in the course

Status in debianutils package in Ubuntu:
  New
Status in systemd-cron package in Ubuntu:
  New

Bug description:
  package debianutils keeps run-parts executable in /usr/bin/
  while package systemd-cron tries to find it in /bin/

  $ which run-parts
  /usr/bin/run-parts

  $ dpkg -S `which run-parts`
  debianutils: /usr/bin/run-parts

  $ grep =/bin/run /lib/systemd/system/cron*
  /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report 
/etc/cron.daily
  /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report 
/etc/cron.hourly
  /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report 
/etc/cron.monthly
  /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report 
/etc/cron.weekly

  Because of that, cron-daily.serice gets info "failed" state soon after
  system reboot.

  Please resolve the problem to make systemd-cron more usable. 
  Thanks in advance for your help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+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 1993215] Re: google account dont works, freeze in gnome login.

2022-10-18 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Incomplete

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

Title:
  google account dont works, freeze in gnome login.

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  google account dont works, freeze in gnome login. cursor dont work,
  cant write.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Oct 17 18:43:27 2022
  InstallationDate: Installed on 2022-10-17 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=es_AR:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1993215/+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 1992968] Re: nmcli disconnect leads to segmentation fault

2022-10-17 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  nmcli disconnect leads to segmentation fault

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Disconnecting the WLAN on riscv64 (LicheeRV with driver licheerv-
  rtl8723ds-dkms) leads to a segmentation fault:

  $ sudo nmcli -a d  disconnect
  Interface(s): wlan0
  Segmentation fault

  Oct 14 12:17:48 ubuntu kernel: [ 5672.571893] nmcli[6918]: unhandled signal 
11 code 0x1 at 0x002af65cb856 in libc.so.6[3f80746000+126000]
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571971] CPU: 0 PID: 6918 Comm: nmcli 
Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571988] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 14 12:17:48 ubuntu kernel: [ 5672.571997] epc : 003f807bca18 ra : 
003f809221e4 sp : 003feebe7550
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572011]  gp : 002ac9a46b48 tp : 
003f8004d780 t0 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572024]  t1 : 003f808dc74c t2 : 
001a s0 : 002af4f3e420
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572036]  s1 : 002af4f3e410 a0 : 
002af65cb85e a1 : 002af4eac010
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572047]  a2 : 002af4f3f760 a3 : 
0002 a4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572059]  a5 :  a6 : 
002af4f3e410 a7 : fc164803c80b4e4b
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572070]  s2 : 002af4f14290 s3 : 
0001 s4 : 003feebe75a4
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572082]  s5 : 002af4f1fb00 s6 : 
002af4f02e80 s7 : 0001
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572093]  s8 : 002ac99fefe8 s9 : 
002af4f3e410 s10: 003f80c73d30
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572105]  s11: 003f809b4368 t3 : 
003f807bca14 t4 : 
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572117]  t5 : 0020 t6 : 
000a
  Oct 14 12:17:48 ubuntu kernel: [ 5672.572126] status: 80026020 
badaddr: 002af65cb856 cause: 000d
  Oct 14 12:20:19 ubuntu wpa_supplicant[661]: wlan0: WPA: Group rekeying 
completed with 2c:91:ab:91:c5:77 [GTK=CCMP]
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IpRoute:
   default via 192.168.123.254 dev enx00e04d680306 proto dhcp src 
192.168.123.75 metric 100 
   default via 192.168.123.254 dev wlan0 proto dhcp src 192.168.123.76 metric 
600 
   192.168.123.0/24 dev enx00e04d680306 proto kernel scope link src 
192.168.123.75 metric 100 
   192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.76 metric 
600 
   192.168.123.254 dev enx00e04d680306 proto dhcp scope link src 192.168.123.75 
metric 100
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: network-manager 1.40.0-1ubuntu2
  PackageArchitecture: riscv64
  PciNetwork:
   
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-allwinner 5.17.15
  RebootRequiredPkgs: Error: path contained symlinks.
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-10-14T12:28:44.227533
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   rxuZdtJmykLvLBiu  29060cbf-0727-4904-813c-5a7e54055c80  wifi  1665749804  
Fri Oct 14 12:16:44 2022  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/rxuZdtJmykLvLBiu.nmconnection
  

[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

2022-10-17 Thread Sebastien Bacher
** Changed in: gnome-font-viewer (Ubuntu)
   Status: Incomplete => New

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fonts-dejavu package in Ubuntu:
  Invalid
Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1993067] Re: Missing dependency of network-manager to iwd

2022-10-17 Thread Sebastien Bacher
Thank you for your bug report. The issue there is probably that you got
iwd installed and removed but not purged and the conffile it provides to
make itself default for n-m stayed around, which was fixed recently in
https://launchpad.net/ubuntu/+source/iwd/1.30-1ubuntu2

I'm closing the bug but reopen if that still doesn't resolve your issue

** Package changed: network-manager (Ubuntu) => iwd (Ubuntu)

** Changed in: iwd (Ubuntu)
   Status: New => Fix Released

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

Title:
  Missing dependency of network-manager to iwd

Status in iwd package in Ubuntu:
  Fix Released

Bug description:
  It seems that the current network-manager in Ubuntu 22.10 would like
  to use iwd per default after the upgrade.

  However, there's no dependency to the iwd package resulting in a lack
  of wifi support after the upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1993067/+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 1990200] Re: goa-daemon crashed with SIGABRT

2022-10-17 Thread Sebastien Bacher
** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #228
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/228

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/228
   Importance: Unknown
   Status: Unknown

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

Title:
  goa-daemon crashed with SIGABRT

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Unknown cause of this crash.  Was alerted to it after waking the
  system from sleep mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.45.2-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Mon Sep 19 19:26:29 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2022-09-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+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 1991008] Re: goa-daemon crashed with SIGABRT in g_assertion_message_expr()

2022-10-17 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1990200 ***
https://bugs.launchpad.net/bugs/1990200

** This bug is no longer a duplicate of private bug 1990123
** This bug has been marked a duplicate of bug 1990200
   goa-daemon crashed with SIGABRT

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

Title:
  goa-daemon crashed with SIGABRT in g_assertion_message_expr()

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  crashed after login to desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.46.0-1
  ProcVersionSignature: Ubuntu 5.19.0-17.17-generic 5.19.7
  Uname: Linux 5.19.0-17-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Wed Sep 28 01:34:46 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2020-06-25 (823 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '--priority=warning', '--since=@1664300076', 
'--until=@1664300096'] failed with exit code 1: Hint: You are currently not 
seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/libexec/goa-daemon
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (155 days ago)
  UserGroups: nordvpn sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1991008/+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 1991787] Re: goa-daemon crashed with SIGABRT in g_assertion_message_expr()

2022-10-17 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1990200 ***
https://bugs.launchpad.net/bugs/1990200

** This bug is no longer a duplicate of private bug 1990123
** This bug has been marked a duplicate of bug 1990200
   goa-daemon crashed with SIGABRT

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

Title:
  goa-daemon crashed with SIGABRT in g_assertion_message_expr()

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I turned off wired ethernet connection and switched on Wifi, all
  connected ok but received an error.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.46.0-1
  Uname: Linux 6.0.0-06-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  5 12:32:16 2022
  ExecutablePath: /usr/libexec/goa-daemon
  JournalErrors:
   Oct 05 12:32:15 hostname org.gnome.OnlineAccounts[4066]: **
   Oct 05 12:32:15 hostname org.gnome.OnlineAccounts[4066]: 
Rest:ERROR:../rest/rest-proxy-call.c:628:finish_call: assertion failed: 
(payload)
   Oct 05 12:32:18 hostname geoclue[3654]: Failed to query location: No WiFi 
networks found
   Oct 05 12:32:25 hostname gnome-shell[4054]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1991787/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken

2022-10-14 Thread Sebastien Bacher
the issue is not likely in the font nor the viewer but in the rendering
stack, I can't confirm here either. Could you give a bit more details on
the desktop environment/fonts settings/locale you are using and include
the output of

$ gsettings list-recursively org.gnome.desktop.interface | grep font

?

** Changed in: gnome-font-viewer (Ubuntu)
   Status: New => Incomplete

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fonts-dejavu package in Ubuntu:
  Invalid
Status in gnome-font-viewer package in Ubuntu:
  Incomplete

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1990200] Re: goa-daemon crashed with SIGABRT

2022-10-13 Thread Sebastien Bacher
error tracker entry is
https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e

** Tags added: rls-kk-incoming

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

Title:
  goa-daemon crashed with SIGABRT

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  Unknown cause of this crash.  Was alerted to it after waking the
  system from sleep mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-online-accounts 3.45.2-3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Mon Sep 19 19:26:29 2022
  ExecutablePath: /usr/libexec/goa-daemon
  InstallationDate: Installed on 2022-09-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917)
  ProcCmdline: /usr/libexec/goa-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0
   () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1992822] Re: /usr/libexec/goa-daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync

2022-10-13 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1990200 ***
https://bugs.launchpad.net/bugs/1990200

** This bug has been marked a duplicate of bug 1990200
   goa-daemon crashed with SIGABRT

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

Title:
  /usr/libexec/goa-
  
daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-online-accounts.  This problem was most recently seen with package 
version 3.46.0-1, the problem page at 
https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e 
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/gnome-online-accounts/+bug/1992822/+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 1811937] Re: shows network profiles on wrong device

2022-10-12 Thread Sebastien Bacher
the fix landed upstream now in https://gitlab.gnome.org/GNOME/gnome-
control-center/-/commit/118de73b

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Invalid

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

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/353
   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/1811937

Title:
  shows network profiles on wrong device

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I have two network ports (ens 34 and ens 37) I'm able to create per
  port its own named profile where it is defined if this used profile
  should use DHCP, use manual DNS and others.

  But if I connect my android Smartphone with USB tethering all named
  Profiles are showing below the new network Port (USB Ethernet) and not
  any more below their defined port. (visual error only) That should
  only happened if a profile is not active but in this case I would
  prefer a separate profile menu where I could choose one and add to a
  specific port.

  Sometimes the network manager entry in the menu also shows confusing
  or empty entries. See print screen attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1811937/+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 1992303] Re: [BOD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card. I have "dummy audio@ outout and no inputs. Please help

2022-10-10 Thread Sebastien Bacher
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but it is better to raise problems you are having in the
support tracker at https://answers.launchpad.net/ubuntu if you are
uncertain if they are bugs. If you would prefer live chat support, you
can find an IRC support channel for your flavor of Ubuntu here:
https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with
your problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs.

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  [BOD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails
  to detect card. I have "dummy audio@ outout and no inputs. Please help

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I've tried some updates and upgrades but nothing changed. Accroding to
  forrums this question is not solved for my audiocard

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bari   1635 F pipewire-media-
   /dev/snd/seq:bari   1634 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  9 20:55:47 2022
  InstallationDate: Installed on 2022-10-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Digital Out, HDMI
  Title: [BOD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails 
to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2022
  dmi.bios.release: 2.29
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 2.29
  dmi.board.asset.tag: N/A
  dmi.board.name: BOD-WXX9-PCB-B3
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1010
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1010
  dmi.ec.firmware.release: 2.29
  dmi.modalias: 
dmi:bvnHUAWEI:bvr2.29:bd04/21/2022:br2.29:efr2.29:svnHUAWEI:pnBOD-WXX9:pvrM1010:rvnHUAWEI:rnBOD-WXX9-PCB-B3:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC171:
  dmi.product.family: MateBook D
  dmi.product.name: BOD-WXX9
  dmi.product.sku: C171
  dmi.product.version: M1010
  dmi.sys.vendor: HUAWEI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992303/+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 1992306] Re: Problem with default a2dp codec for bluethooth headset

2022-10-10 Thread Sebastien Bacher
Thank you for your bug report, could you also register the problem
upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/ ? that's
probably a better place to suggest a such change

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

** Summary changed:

- Problem with default a2dp codec for bluethooth headset
+ Default to a2dp ldac_hq codec for bluethooth headset and sound distorted

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

Title:
  Default to a2dp ldac_hq codec for bluethooth headset and sound
  distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had some trouble getting my bluetooth headphones to work and I
  believe the culprit is the default codec that pulseaudio chooses. It
  appears to work ok when having no other Bluetooth devices connected,
  but when connecting a bluetooth mouse the audio gets distorted and
  begins to stutter. The offending codec is ldac_hq. I did some
  investigating today and found out you can change the codec in
  pavucontrol. Selecting ldac_sq seems to work without any issue.

  I don't know what the problem with ldac_hq is, maybe bandwidth? Wasn't
  able to find any obvious problems in the logs, even when enabling
  debugging in bluez.

  While investigating this I noticed others having the same issue, and
  it was difficult to find a way to change the codec, so maybe ldac_hq
  shouldn't be chosen as default?

  Headphones: Sony WF-1000XM
  Mouse: Logitech M590
  Computer: 
https://www.asus.com/Laptops/For-Home/Zenbook/Zenbook-S-UX391/techspec/

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5201 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
  Bus 001 Device 002: ID 13d3:56b9 IMC Networks USB2.0 HD UVC WebCam
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  description: Bluetooth wireless interface
 product: Bluetooth wireless interface
 vendor: Intel Corp.
 physical id: 8
 bus info: usb@1:8
 version: 0.10
 capabilities: bluetooth usb-2.00
 configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  Ubuntu 22.04.1 LTS
  pulseaudio: 1:15.99.1+dfsg1-1ubuntu1
  bluez: 5.64-0ubuntu1
  pavucontrol: 5.0-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992306/+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 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-10-07 Thread Sebastien Bacher
** Package changed: network-manager (Ubuntu) => iwd (Ubuntu)

** Changed in: iwd (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in iwd package in Ubuntu:
  Fix Committed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1990891/+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 1990448] Re: Show Ubuntu Pro settings

2022-10-07 Thread Sebastien Bacher
** Description changed:

+ Assuming that it doesn't require a FFe for Kinetic since the code is
+ only active on LTS series.
+ 
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of
  just Livepatch.

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  Incomplete
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  Assuming that it doesn't require a FFe for Kinetic since the code is
  only active on LTS series.

  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+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 1991525] Re: vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”

2022-10-05 Thread Sebastien Bacher
no problem, glad that you figured it out!

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

Title:
  vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open
  shared object file”

Status in vim package in Ubuntu:
  Invalid

Bug description:
  After upgrading a system running Ubuntu 20.04 to 22.04, vim.gtk3 no
  longer runs:

    $ vim.gtk3
    vim.gtk3: error while loading shared libraries: libpng12.so.0: cannot open 
shared object file: No such file or directory

  (vim.basic still runs fine).

  These are the vim packages we have installed, and their versions:

    vim:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-gtk3:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-gui-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-runtime:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-tiny:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate

  Previously I did have a PPA of Vim installed from
  http://ppa.launchpad.net/jonathonf/vim/ubuntu — but that has been
  purged, and as you can see all the vim packages now installed are
  official Ubuntu jammy versions.

  libpng12 isn't in Ubuntu any more, so I think the problem is that vim
  is trying to use it, not that it's missing.

  Attached is strace output of the failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1991525/+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 1990113] Re: Increase timeout on test doc-check for RISC-V

2022-10-05 Thread Sebastien Bacher
thanks

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

Title:
  Increase timeout on test doc-check for RISC-V

Status in json-glib package in Ubuntu:
  Incomplete

Bug description:
  The doc-check test fails on RISC-V because it is a very slow
  architecture: fix this by increasing the timeout on this specific
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1991525] Re: vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”

2022-10-05 Thread Sebastien Bacher
could you share the output of

$ which vim.gtk3

$ ldd -r `which vim.gtk3`

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

Title:
  vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open
  shared object file”

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  After upgrading a system running Ubuntu 20.04 to 22.04, vim.gtk3 no
  longer runs:

    $ vim.gtk3
    vim.gtk3: error while loading shared libraries: libpng12.so.0: cannot open 
shared object file: No such file or directory

  (vim.basic still runs fine).

  These are the vim packages we have installed, and their versions:

    vim:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-gtk3:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-gui-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-runtime:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
    vim-tiny:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate

  Previously I did have a PPA of Vim installed from
  http://ppa.launchpad.net/jonathonf/vim/ubuntu — but that has been
  purged, and as you can see all the vim packages now installed are
  official Ubuntu jammy versions.

  libpng12 isn't in Ubuntu any more, so I think the problem is that vim
  is trying to use it, not that it's missing.

  Attached is strace output of the failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1991525/+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 1990113] Re: Increase timeout on test doc-check for RISC-V

2022-10-04 Thread Sebastien Bacher
@Alexandre, is that actually been an issue on our builder or what's the
motivation for the change if not? Also the package is currently in sync
with Debian and it would be nice to keep it this way so if it makes
sense to have it could you propose the change upstream and/or to Debian?

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

Title:
  Increase timeout on test doc-check for RISC-V

Status in json-glib package in Ubuntu:
  Incomplete

Bug description:
  The doc-check test fails on RISC-V because it is a very slow
  architecture: fix this by increasing the timeout on this specific
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1990448] Re: Show Ubuntu Pro settings

2022-10-03 Thread Sebastien Bacher
** Merge proposal linked:
   
https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+merge/430260

** Changed in: software-properties (Ubuntu Kinetic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  Incomplete
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+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 1990448] Re: Show Ubuntu Pro settings

2022-10-03 Thread Sebastien Bacher
@Dan, the design is available on
https://app.zeplin.io/project/6319abf25548b04abcee1b5f/dashboard

The Kinetic target is correct, even if the service isn't available on
non LTS serie we need the code to be merged in the current serie before
being backported by SRU rules

The corresponding PR is https://code.launchpad.net/~robert-
ancell/software-properties/+git/software-properties/+merge/430260

** Changed in: software-properties (Ubuntu Kinetic)
   Status: New => Fix Committed

** Changed in: software-properties (Ubuntu Kinetic)
   Importance: Undecided => Low

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  Incomplete
Status in software-properties source package in Kinetic:
  Fix Committed

Bug description:
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+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 1972790] Re: Can't connect to hotspot created on ubuntu

2022-09-30 Thread Sebastien Bacher
which firewall did you disable to workaround the issue?

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-09-27 Thread Sebastien Bacher
you can uninstall wpasupplicant instead of disabling it but if they
conflict we need to resolve it differently than by adding iwd as we did

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

2022-09-20 Thread Sebastien Bacher
the stacktrace is similar to
https://gitlab.gnome.org/GNOME/gtk/-/issues/3310

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

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

Status in apport package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Triaged
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  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: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 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/apport/+bug/1842439/+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 1989572] Re: libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0

2022-09-15 Thread Sebastien Bacher
Thanks for the report, that should be fixed now

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  This maybe has to be reassigned to affect 'ddeb-retriever', but the
  web form doesn't allow setting it as package for reporting.

  'libglib2.0-0' was updated in the bionic-updates repository, but
  'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs
  repository:

  # apt-cache policy libglib2.0-0
  libglib2.0-0:
    Installed: 2.56.4-0ubuntu0.18.04.9
    Candidate: 2.56.4-0ubuntu0.18.04.9
    Version table:
   *** 2.56.4-0ubuntu0.18.04.9 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.56.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  # apt-cache policy libglib2.0-0-dbgsym
  libglib2.0-0-dbgsym:
    Installed: (none)
    Candidate: 2.56.1-2ubuntu1
    Version table:
   2.56.1-2ubuntu1 500
  500 http://ddebs.ubuntu.com bionic/main amd64 Packages

  Due to this, the package 'libglib2.0-0-dbgsym' is not installable with
  apt-get:

  # apt-get update && apt-get install libglib2.0-0-dbgsym
  [...]
  The following packages have unmet dependencies:
   libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 
2.56.4-0ubuntu0.18.04.9 is to be installed
  E: Unable to correct problems, you have held broken packages.

  Using `--force-yes` or `--allow-downgrades` does not make any
  difference.

  These are the ddebs repositories in use:

  # cat /etc/apt/sources.list.d/ddebs.list
  deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
  deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse
  deb http://ddebs.ubuntu.com bionic-proposed main restricted universe 
multiverse

  System is Ubuntu 18.04 Bionic:

  # lsb_release -rd
  Description:Ubuntu 18.04.6 LTS
  Release:18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1989572/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-14 Thread Sebastien Bacher
** Changed in: poppler (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  New

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-14 Thread Sebastien Bacher
The description of the patch explains why the current behavior is buggy
and not just different in a way users would be relying on the difference
of behavior. It's not that it works differently, it is that it reports
wrong information.

The patch didn't apply directly so I've adapted it and verified that a
build of the package with it  matched the new expected behavior before
uploading.

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-14 Thread Sebastien Bacher
@Robie, the patch description has details on the change. The github
report also discuss why the patch was broken and not just doing what is
intended and why the revert is right.

I'm not involved in iputils and will not be able to provide more
information that was in there. Note that the revert is part of 22.04.

I was mostly trying to help landing a fix we were getting request on.
I'm fine updating the testcase if that's enough to unblock the SRU but
otherwise please reject my upload, I'm not wanting to spend the time
needed to prove that upstream can be trusted on that one.

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-13 Thread Sebastien Bacher
and I've uploaded a focal SRU candidate to the review queue now

** Changed in: iputils (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: iputils (Ubuntu Focal)
   Status: New => Fix Committed

** Description changed:

+ = Impact =
+ 
+ the ping statistics are incorrect when dealing with truncated packets
+ 
+ = Test case =
+ 
+ $ ping -c 1 -s 1200 8.8.8.8
+ 
+ should list truncated replies and received packets
+ 
+ = Regression potential =
+ 
+ the changes are limited to the ping source any regression would impact
+ that utility, check that responses are correctly handled and statistics
+ reflecting what is expected
+ 
+ --
+ 
  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.
  
  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722
  
  Could this patch be added for a Focal update please?
  
  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)
  
  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  
  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms
  
  4)
  
  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)
  
  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Fix Committed

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-13 Thread Sebastien Bacher
The issue is fixed in the version available in the current Ubuntu serie

** Changed in: iputils (Ubuntu)
   Importance: Undecided => Low

** Changed in: iputils (Ubuntu)
   Status: New => Fix Released

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  New

Bug description:
  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1988667] Re: Quito isn't displayed as choice for time zone

2022-09-08 Thread Sebastien Bacher
Thank you for your bug report, the choice of the city to display for
Ecuador is coming from tzdata, you can see an old similar report on
https://bugzilla.redhat.com/show_bug.cgi?id=131320 for example

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

** No longer affects: systemsettings (Ubuntu)

** Bug watch added: Red Hat Bugzilla #131320
   https://bugzilla.redhat.com/show_bug.cgi?id=131320

** Package changed: gnome-control-center (Ubuntu) => tzdata (Ubuntu)

** Changed in: tzdata (Ubuntu)
   Status: New => Opinion

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

Title:
  Quito isn't displayed as choice for time zone

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  On Ubuntu 22.04.1 (and 20.04.x) there is no option available for
  Quito.

  On GNOME
  

  Settings > Date & Time > (A map is displayed)

  Type Quito on the search field.

  There are no matches.

  
  On KDE
  ==

  System Settings > Regional Settings > Date & Time > Time Zone

  When searching for the time zone I enter:

  Quito

  There are no matches.

  
  The entries for Ecuador are Galapagos Islands and Guayaquil. Quito is the 
capital city of Ecuador, whereas Guayaquil is the second biggest. It makes no 
sense for the capital not to be displayed in the city list, but to have the 
second.

  It is akin to have Marseille as the main choice for France instead of
  Paris.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1988667/+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 1988667] Re: Quito isn't displayed as choice for time zone

2022-09-08 Thread Sebastien Bacher
if you want to report it upstream the right place would be
https://mm.icann.org/mailman/listinfo/tz

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

Title:
  Quito isn't displayed as choice for time zone

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  On Ubuntu 22.04.1 (and 20.04.x) there is no option available for
  Quito.

  On GNOME
  

  Settings > Date & Time > (A map is displayed)

  Type Quito on the search field.

  There are no matches.

  
  On KDE
  ==

  System Settings > Regional Settings > Date & Time > Time Zone

  When searching for the time zone I enter:

  Quito

  There are no matches.

  
  The entries for Ecuador are Galapagos Islands and Guayaquil. Quito is the 
capital city of Ecuador, whereas Guayaquil is the second biggest. It makes no 
sense for the capital not to be displayed in the city list, but to have the 
second.

  It is akin to have Marseille as the main choice for France instead of
  Paris.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1988667/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

2022-09-08 Thread Sebastien Bacher
could you clean /var/crash, trigger the issue again and resubmit the
crash? the bot failing to recover debug information on the current
report

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  occurred when toggle darkmode

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.39.90-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Fri Sep  2 15:34:33 2022
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2020-06-25 (799 days ago)
  InstallationMedia:
   
  IpRoute:
   default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 
20600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 
metric 600
  JournalErrors: -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
  UserGroups: N/A
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.39.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time

2022-09-07 Thread Sebastien Bacher
And I cherrypicked the fixes for a SRU to 22.04 now

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

Title:
  Kubuntu 22.04, Bluetooth Headphones connect automatically, then
  immediately disconnect; pulseautio crashes every time

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  On a fresh install of Kubuntu 22.04, when I turn my properly paired
  bluetooth headphones on they automatically connect to the system, then
  immediately disconnect again. The headphones thus have to be manually
  're-connected' every time.

  * Test case

  Connect a bluetooth headset to the computer, try to change the active
  profile. The selection should be reflected and the quality match, the
  pairing and service should be stable

  * Regression potential

  The changes are in the bluetooth a2dp/sbc functions so any potential
  regression would impact the connectivity with bluetooth devices using
  an a2dp profile (aptX, SBC, AAC). Check with different devices using
  the previously listed profiles.

  
  

  Best as I understand it from the logs (appended below), pulseaudio showing up 
killed just after the headphones turn up as an unregistered sender ...
  4/30/22 7:33 PM   systemd pulseaudio.service: Main process exited, 
code=killed, status=8/FPE

  ... is responsible for the observed problem, i.e. the disconnect, probably 
triggered when pulseaudio restarts ...
  4/30/22 7:33 PM   systemd pulseaudio.service: Scheduled restart job, 
restart counter is at 2.

  So it seems either an internal pulseaudio problem, or a problem triggered by 
the division by 0 in the bluetooth module ...
  4/30/22 7:33 PM   kernel  traps: bluetooth[8884] trap divide error 
ip:7f862dc68490 sp:7f862498cc30 error:0 in 
module-bluez5-device.so[7f862dc66000+9000]

  or some combination of the two ... but again, I'm only guessing here.

  
___

  System Logs after switching headphones on:

  4/30/22 7:33 PM   kernel  input: Nat's Flex (AVRCP) as 
/devices/virtual/input/input31
  4/30/22 7:33 PM   systemd-logind  Watching system buttons on 
/dev/input/event19 (Nat's Flex (AVRCP))
  4/30/22 7:33 PM   bluetoothd  
/org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready
  4/30/22 7:33 PM   rtkit-daemonSupervising 0 threads of 0 processes of 
0 users.
  4/30/22 7:33 PM   rtkit-daemonSuccessfully made thread 8884 of 
process 3426 owned by '1000' RT at priority 5.
  4/30/22 7:33 PM   rtkit-daemonSupervising 1 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   kernel  traps: bluetooth[8884] trap divide error 
ip:7f862dc68490 sp:7f862498cc30 error:0 in 
module-bluez5-device.so[7f862dc66000+9000]
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_453
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_453
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_512
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_512
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_552
  4/30/22 7:33 PM   systemd pulseaudio.service: Main process exited, 
code=killed, status=8/FPE
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_552
  4/30/22 7:33 PM   systemd pulseaudio.service: Failed with result 'signal'.
  4/30/22 7:33 PM   systemd pulseaudio.service: Consumed 2min 20.027s CPU 
time.
  4/30/22 7:33 PM   acpid   input device has been disconnected, fd 20
  4/30/22 7:33 PM   systemd pulseaudio.service: Scheduled restart job, 
restart counter is at 2.
  4/30/22 7:33 PM   systemd Stopped Sound Service.
  4/30/22 7:33 PM   systemd pulseaudio.service: Consumed 2min 20.027s CPU 
time.
  4/30/22 7:33 PM   systemd Starting Sound Service...
  4/30/22 7:33 PM   rtkit-daemonSuccessfully made thread 8889 of 
process 8889 owned by '1000' high priority at nice level -11.
  4/30/22 7:33 PM   rtkit-daemonSupervising 1 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   pulseaudio  Stale PID file, overwriting.
  4/30/22 7:33 PM   rtkit-daemonSupervising 1 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   rtkit-daemonSuccessfully made thread 8890 of 
process 8889 

[Touch-packages] [Bug 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time

2022-09-07 Thread Sebastien Bacher
The is in pulseaudio 16.0+ which is in kinetic

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => High

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

** Description changed:

+ * Impact
+ 
  On a fresh install of Kubuntu 22.04, when I turn my properly paired
  bluetooth headphones on they automatically connect to the system, then
  immediately disconnect again. The headphones thus have to be manually
  're-connected' every time.
+ 
+ * Test case
+ 
+ Connect a bluetooth headset to the computer, try to change the active
+ profile. The selection should be reflected and the quality match, the
+ pairing and service should be stable
+ 
+ * Regression potential
+ 
+ The changes are in the bluetooth a2dp/sbc functions so any potential
+ regression would impact the connectivity with bluetooth devices using an
+ a2dp profile (aptX, SBC, AAC). Check with different devices using the
+ previously listed profiles.
+ 
+ 
+ 
  
  Best as I understand it from the logs (appended below), pulseaudio showing up 
killed just after the headphones turn up as an unregistered sender ...
  4/30/22 7:33 PM   systemd pulseaudio.service: Main process exited, 
code=killed, status=8/FPE
  
  ... is responsible for the observed problem, i.e. the disconnect, probably 
triggered when pulseaudio restarts ...
  4/30/22 7:33 PM   systemd pulseaudio.service: Scheduled restart job, 
restart counter is at 2.
  
  So it seems either an internal pulseaudio problem, or a problem triggered by 
the division by 0 in the bluetooth module ...
  4/30/22 7:33 PM   kernel  traps: bluetooth[8884] trap divide error 
ip:7f862dc68490 sp:7f862498cc30 error:0 in 
module-bluez5-device.so[7f862dc66000+9000]
  
  or some combination of the two ... but again, I'm only guessing here.
  
  
___
  
  System Logs after switching headphones on:
  
  4/30/22 7:33 PM   kernel  input: Nat's Flex (AVRCP) as 
/devices/virtual/input/input31
  4/30/22 7:33 PM   systemd-logind  Watching system buttons on 
/dev/input/event19 (Nat's Flex (AVRCP))
  4/30/22 7:33 PM   bluetoothd  
/org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready
  4/30/22 7:33 PM   rtkit-daemonSupervising 0 threads of 0 processes of 
0 users.
  4/30/22 7:33 PM   rtkit-daemonSuccessfully made thread 8884 of 
process 3426 owned by '1000' RT at priority 5.
  4/30/22 7:33 PM   rtkit-daemonSupervising 1 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   kernel  traps: bluetooth[8884] trap divide error 
ip:7f862dc68490 sp:7f862498cc30 error:0 in 
module-bluez5-device.so[7f862dc66000+9000]
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_453
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_453
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_512
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_512
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSink/sbc_xq_552
  4/30/22 7:33 PM   systemd pulseaudio.service: Main process exited, 
code=killed, status=8/FPE
  4/30/22 7:33 PM   bluetoothd  Endpoint unregistered: sender=:1.126 
path=/MediaEndpoint/A2DPSource/sbc_xq_552
  4/30/22 7:33 PM   systemd pulseaudio.service: Failed with result 'signal'.
  4/30/22 7:33 PM   systemd pulseaudio.service: Consumed 2min 20.027s CPU 
time.
  4/30/22 7:33 PM   acpid   input device has been disconnected, fd 20
  4/30/22 7:33 PM   systemd pulseaudio.service: Scheduled restart job, 
restart counter is at 2.
  4/30/22 7:33 PM   systemd Stopped Sound Service.
  4/30/22 7:33 PM   systemd pulseaudio.service: Consumed 2min 20.027s CPU 
time.
  4/30/22 7:33 PM   systemd Starting Sound Service...
  4/30/22 7:33 PM   rtkit-daemonSuccessfully made thread 8889 of 
process 8889 owned by '1000' high priority at nice level -11.
  4/30/22 7:33 PM   rtkit-daemonSupervising 1 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   pulseaudio  Stale PID file, overwriting.
  4/30/22 7:33 PM   rtkit-daemonSupervising 1 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   rtkit-daemonSuccessfully made thread 8890 of 
process 8889 owned by '1000' RT at priority 5.
  4/30/22 7:33 PM   rtkit-daemonSupervising 2 threads of 1 processes of 
1 users.
  4/30/22 7:33 PM   rtkit-daemonSupervising 2 threads of 1 

  1   2   3   4   5   6   7   8   9   10   >