[Bug 2065188] [NEW] GIMP crashed with a fatal error: fatal error: Segmentation fault

2024-05-08 Thread Carlos Alberto Lima dos Santos
Public bug reported:




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 42123 - Thread 42123 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 42160]
[New LWP 42158]
[New LWP 42141]
[New LWP 42138]
[New LWP 42136]
[New LWP 42135]
[New LWP 42134]
[New LWP 42133]
[New LWP 42132]
[New LWP 42131]
[New LWP 42130]
[New LWP 42129]
[New LWP 42128]
[New LWP 42127]
[New LWP 42126]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x75f3eaf1ba9a in __GI___libc_read (nbytes=256, buf=0x7ffd52d83c70, fd=26) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x75f3ea8fb640 (LWP 42123) "gimp-2.10"0x75f3eaf1ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffd52d83c70, fd=26) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x75f3c3e006c0 (LWP 42160) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x75f3c2a006c0 (LWP 42158) "threaded-ml"  0x75f3eaf1b4cd in 
__GI___poll (fds=0x75f3880071a0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x75f3c34006c0 (LWP 42141) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x75f3ccc006c0 (LWP 42138) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x75f3ce0006c0 (LWP 42136) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x75f3daa006c0 (LWP 42135) "gdbus"0x75f3eaf1b4cd in 
__GI___poll (fds=0x75f3ac009770, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x75f3db4006c0 (LWP 42134) "gmain"0x75f3eaf1b4cd in 
__GI___poll (fds=0x55cc4857d400, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x75f3dbe006c0 (LWP 42133) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x75f3e16006c0 (LWP 42132) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x75f3e20006c0 (LWP 42131) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x75f3e2a006c0 (LWP 42130) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x75f3e34006c0 (LWP 42129) "worker"   syscall () at 

[Bug 2059317] Re: [FFe] EC2 fetch metadata every boot

2024-04-29 Thread Alberto Contreras
https://github.com/canonical/cloud-init/issues/5114 represents the cache
invalidation issue.

** Bug watch added: github.com/canonical/cloud-init/issues #5114
   https://github.com/canonical/cloud-init/issues/5114

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

Title:
  [FFe] EC2 fetch metadata every boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2059317/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061562] Re: tried attaching ubuntu pro using terminal

2024-04-25 Thread Alberto Contreras
Per the trace in https://bugs.launchpad.net/ubuntu/+source/ubuntu-
advantage-
tools/+bug/2061562/+attachment/5765702/+files/ubuntu_pro_apt_news.txt:

```
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/uaclient/cli/__init__.py", line 1705, in 
wrapper
return func(*args, **kwargs)
   ^
  File "/usr/lib/python3/dist-packages/uaclient/cli/__init__.py", line 1838, in 
main
return_value = args.action(args, cfg=cfg, extra_args=extra_args)
   ^
  File "/usr/lib/python3/dist-packages/uaclient/cli/__init__.py", line 257, in 
new_f
return f(args, cfg=cfg, **kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/uaclient/cli/__init__.py", line 202, in 
new_f
return f(*args, **kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/uaclient/cli/__init__.py", line 186, in 
new_f
retval = f(*args, cfg=cfg, **kwargs)
 ^^^
  File "/usr/lib/python3/dist-packages/uaclient/cli/__init__.py", line 1305, in 
action_attach
actions.attach_with_token(cfg, token=token, allow_enable=allow_enable)
  File "/usr/lib/python3/dist-packages/uaclient/actions.py", line 65, in 
attach_with_token
new_machine_token = contract_client.add_contract_machine(
^
  File "/usr/lib/python3/dist-packages/uaclient/util.py", line 92, in decorator
return f(*args, **kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 96, in 
add_contract_machine
response = self.request_url(
   ^
  File "/usr/lib/python3/dist-packages/uaclient/http/serviceclient.py", line 
68, in request_url
return http.readurl(
   ^
  File "/usr/lib/python3/dist-packages/uaclient/http/__init__.py", line 364, in 
readurl
resp = _readurl_urllib(req, timeout=timeout)
   ^
  File "/usr/lib/python3/dist-packages/uaclient/http/__init__.py", line 167, in 
_readurl_urllib
resp = request.urlopen(req, timeout=timeout)
   ^
  File "/usr/lib/python3.12/urllib/request.py", line 215, in urlopen
return opener.open(url, data, timeout)
   ^^^
  File "/usr/lib/python3.12/urllib/request.py", line 515, in open
response = self._open(req, data)
   ^
  File "/usr/lib/python3.12/urllib/request.py", line 532, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
 ^^^
  File "/usr/lib/python3.12/urllib/request.py", line 492, in _call_chain
result = func(*args)
 ^^^
  File "/usr/lib/python3.12/urllib/request.py", line 1392, in https_open
return self.do_open(http.client.HTTPSConnection, req,
   ^^
  File "/usr/lib/python3.12/urllib/request.py", line 1348, in do_open
r = h.getresponse()
^^^
  File "/usr/lib/python3.12/http/client.py", line 1428, in getresponse
response.begin()
  File "/usr/lib/python3.12/http/client.py", line 331, in begin
version, status, reason = self._read_status()
  ^^^
  File "/usr/lib/python3.12/http/client.py", line 300, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
```

It looks like the internet connection get lost during the attach
process. Could you please retry to attach?

IMO, this error should be gracefully handled, marking this as triaged to
represent that.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Triaged

** Information type changed from Private to Public

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

Title:
  tried attaching ubuntu pro using terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2061562/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2052437] Re: python-boto: obsolete, replaced by python-boto3

2024-04-17 Thread Alberto Contreras
For the simplestreams target, it was discussed and agreed by paelzer,
paride and aciba that it does not require an FFE because:

> In general a change like this would require an FFe, unless it is the
only viable way to fix a (sufficiently high importance) bug. In this
case the bug is https://bugs.launchpad.net/ubuntu/+source/python-
boto/+bug/2052437 and in my opinion that it is important enough, and
switching to boto3 is the only sensible way to fix it

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

Title:
  python-boto: obsolete, replaced by python-boto3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061902] Re: upgrade to 0.10.1

2024-04-17 Thread Alberto Contreras
** Description changed:

- TODO
+ 
https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750/comments/3

** Changed in: python-s3transfer (Ubuntu)
 Assignee: (unassigned) => Alberto Contreras (aciba)

** Changed in: python-s3transfer (Ubuntu)
   Status: New => In Progress

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

Title:
  upgrade to 0.10.1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)

2024-04-17 Thread Alberto Contreras
New MR including 0.10.1 and tests:
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464461

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

Title:
  [MIR] python-s3transfer as indirect dependency of simplestreams
  (simplestreams -> python-boto3 -> python-s3transfer)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061902] Re: upgrade to 0.10.1

2024-04-16 Thread Alberto Contreras
** Merge proposal linked:
   
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464460

** Merge proposal linked:
   
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464461

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

Title:
  upgrade to 0.10.1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061902] [NEW] upgrade to 0.10.1

2024-04-16 Thread Alberto Contreras
Public bug reported:

TODO

** Affects: python-s3transfer (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  upgrade to 0.10.1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)

2024-04-16 Thread Alberto Contreras
I am working on adding build / autopkg test in
https://code.launchpad.net/~aciba/ubuntu/+source/python-s3transfer/+git/python-s3transfer/+merge/464413
.

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

Title:
  [MIR] python-s3transfer as indirect dependency of simplestreams
  (simplestreams -> python-boto3 -> python-s3transfer)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061751] Re: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python-botocore)

2024-04-16 Thread Alberto Contreras
I am working on adding build / autopkg tests in
https://code.launchpad.net/~aciba/ubuntu/+source/python-
botocore/+git/python-botocore/+merge/464419

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

Title:
  [MIR] python-botocore as indirect dependency of simplestreams
  (simplestreams -> python-boto3 -> python-s3transfer -> python-
  botocore)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061217] Re: [MIR] python-boto3 as a dependency of simplestreams

2024-04-16 Thread Alberto Contreras
I am working on adding build / autopkg test in
https://code.launchpad.net/~aciba/ubuntu/+source/python-
boto3/+git/python-boto3/+merge/464411

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

Title:
  [MIR] python-boto3 as a dependency of simplestreams

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061751] Re: [MIR] python-botocore as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer -> python-botocore)

2024-04-16 Thread Alberto Contreras
** Summary changed:

- [MIR] python-botocore as dependency of python-s3transfer
+ [MIR] python-botocore as indirect dependency of simplestreams (simplestreams 
-> python-boto3 -> python-s3transfer -> python-botocore)

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

Title:
  [MIR] python-botocore as indirect dependency of simplestreams
  (simplestreams -> python-boto3 -> python-s3transfer -> python-
  botocore)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061750] Re: [MIR] python-s3transfer as indirect dependency of simplestreams (simplestreams -> python-boto3 -> python-s3transfer)

2024-04-16 Thread Alberto Contreras
** Summary changed:

-  [MIR] python-s3transfer as dependency of python-boto3
+ [MIR] python-s3transfer as indirect dependency of simplestreams 
(simplestreams -> python-boto3 -> python-s3transfer)

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

Title:
  [MIR] python-s3transfer as indirect dependency of simplestreams
  (simplestreams -> python-boto3 -> python-s3transfer)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061217] Re: [MIR] python-boto3 as a dependency of simplestreams

2024-04-16 Thread Alberto Contreras
** Description changed:

  [Availability]
  The package python-boto3 is already in Ubuntu universe.
  The package python-boto3 build for the architectures it is designed to work 
on.
  They build amd64 only (but binary is arch-all)
  Link to package: https://launchpad.net/ubuntu/+source/python-boto3
  
  [Rationale]
  Simplestreams itself is in main for quite a while since bug 1220427.
  The package python-boto3 is required in Ubuntu main for simplestreams
  The package python-boto3 will not generally be useful for a large part of
  our user base, but is important/helpful still because it is required by 
simplestreams
  Additionally new use-cases enabled by this are demoting python-boto to 
universe because
  the only reverse depency in main is simplestreams and debian is going to drop 
support
  for python-boto, see LP: 2052437
  The package python-boto3 is a new runtime dependency of package simplestreams 
that
  we already support
  python-boto is not compatible with python3.12, the only python supported in 
noble, thus
  to commit to a long term support of simplestreams, it's better to depend on 
dependencies
  that have upstream support
  
  The package python-boto3 is required in Ubuntu main no later than noble is 
released
  due to being required by a new upload of simplestreams in noble-proposed to 
make it
  work on python3.12 and to be able to drop python-boto from noble archives.
  
  python-s3transfer is a binary dependency of python-boto3
  python-botocore is a binary dependency of python-s3transfer
  
  [Security]
  - No CVEs/security issues in this software in the past:
  (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-boto3
  
(0)https://ubuntu.com/security/cves?q==python-boto3===
  (0)https://security-tracker.debian.org/tracker/source-package/python-boto3
  
  No `suid` or `sgid` binaries
  No executables in `/sbin` and `/usr/sbin`
  Package does not install services, timers or recurring jobs
  Packages does not open privileged ports (ports < 1024).
  Package does not expose any external endpoints
  Packages does not contain extensions to security-sensitive software
  (filters, scanners, plugins, UI skins, ...)
  
  [Quality assurance - function/usage]
  The package works well right after install. It's a python library.
  
  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu/Upstream and does
    not have too many, long-term & critical, open bugs
    - Ubuntu (2)https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug
    - Debian (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-boto3
    - Upstream's bug tracker (192)https://github.com/boto/boto3/issues
  Looks normal for the age and impact of these libraries
  - The package does not deal with exotic hardware we cannot support
  
  [Quality assurance - testing]
  - The package does not run a test at build time because it is not configured 
to do so,
  the upstream source code contains unit tests
  - The package does not run an autopkgtest because they are not configured to 
do so.
  
  [Quality assurance - packaging]
  - debian/watch is present and works
  - debian/control defines a correct Maintainer field
  - Lintian does not run as part of the build
    
https://launchpadlibrarian.net/715514166/buildlog_ubuntu-noble-amd64.python-boto3_1.34.46+dfsg-1_BUILDING.txt.gz
+ - Lintian output attached
  - Lintian overrides are present, but ok because they are justified:
  
  # This is a false positive, likely an occurrence of #1019980
  python-boto3 source: source-is-missing [docs/source/_templates/page.html]
  
  - This package does not rely on obsolete or about to be demoted packages.
  - This package has no python2 or GTK2 dependencies
  - The package will not be installed by default
  - Packaging and build is easy, link to debian/rules:
    https://git.launchpad.net/ubuntu/+source/python-boto3/tree/debian/rules
  
  [UI standards]
  - Application is not end-user facing (does not need translation)
  
  [Dependencies]
  - There are further dependencies that are not yet in main, MIR for them
-   is at:
-   - python-s3trasnfer: 
https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750
-   - python-botocore: 
https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751
+   is at:
+   - python-s3trasnfer: 
https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/2061750
+   - python-botocore: 
https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751
  
  [Standards compliance]
  - This package correctly follows FHS and Debian Policy
  
  [Maintenance/Owner]
  - The owning team will be Ubuntu Server and I have their acknowledgement for
-   that commitment
+   that commitment
  - The future owning team is already subscribed to the package
  - This does not use static builds
  - This does not use vendored code
  - This package is not rust based
  
  [Background information]
  The Package description explains the package well
  Upstream 

[Bug 2061750] Re: [MIR] python-s3transfer as dependency of python-boto3

2024-04-16 Thread Alberto Contreras
$ lintian --pedantic python-s3transfer_0.10.0-1.dsc

** Description changed:

- TODO
+ [Availability]
+ The package python-s3transfer is already in Ubuntu universe.
+ The package python-s3transfer build for the architectures it is designed to 
work on.
+ They build amd64 only (but binary is arch-all)
+ Link to package https://launchpad.net/ubuntu/+source/python-s3transfer
+ 
+ [Rationale]
+ The package python-s3transfer is required in Ubuntu main for python-boto3
+ The package python-s3transfer will not generally be useful for a large part of
+ our user base, but is important/helpful still because it is required by 
python-boto3
+ which is in the MIR process as a dependency of simplestreams.
+ python-boto3 MIR link: 
https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217
+ 
+ - The package python-s3transfer is required in Ubuntu main through the
+ same scheduled requested for the python-boto3 promotion, since python-
+ boto3 depends on it.
+ 
+ [Security]
+ - No CVEs/security issues in this software in the past:
+ (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-s3transfer
+ 
(0)https://security-tracker.debian.org/tracker/source-package/python-s3transfer
+ 
(0)https://ubuntu.com/security/cves?q==python-s3transfer===
+ 
+ No `suid` or `sgid` binaries
+ No executables in `/sbin` and `/usr/sbin`
+ Package does not install services, timers or recurring jobs
+ Packages does not open privileged ports (ports < 1024).
+ Package does not expose any external endpoints
+ Packages does not contain extensions to security-sensitive software
+ (filters, scanners, plugins, UI skins, ...)
+ 
+ [Quality assurance - function/usage]
+ The package works well right after install. It's a python library.
+ 
+ [Quality assurance - maintenance]
+ - The package is maintained well in Debian/Ubuntu/Upstream and does
+   not have too many, long-term & critical, open bugs
+   - Ubuntu 
(1)https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bugs
+   - Debian 
(0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-s3transfer
+   - Upstream's bug tracker (24)https://github.com/boto/s3transfer/issues
+ Looks normal for the age and impact of these libraries
+ - The package does not deal with exotic hardware we cannot support
+ 
+ [Quality assurance - testing]
+ - The package does not run a test at build time because it is not configured 
to do so,
+ the upstream source code contains unit tests
+ - The package does not run an autopkgtest because they are not configured to 
do so.
+ 
+ [Quality assurance - packaging]
+ - debian/watch is present and works
+ - debian/control defines a correct Maintainer field
+ - Lintian does not run as part of the build 
https://launchpadlibrarian.net/709963913/buildlog_ubuntu-noble-amd64.python-s3transfer_0.10.0-1_BUILDING.txt.gz
+ - Lintian overrides are not present
+ 
+ - This package does not rely on obsolete or about to be demoted packages.
+ - This package has no python2 or GTK2 dependencies
+ - The package will not be installed by default
+ - Packaging and build is easy, link to debian/rules: 
https://git.launchpad.net/ubuntu/+source/python-s3transfer/tree/debian/rules
+ 
+ [UI standards]
+ - Application is not end-user facing (does not need translation)
+ 
+ [Dependencies]
+ - There are further dependencies that are not yet in main, MIR for them
+   is at:
+   - python-botocore: 
https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/2061751
+ 
+ [Standards compliance]
+ - This package correctly follows FHS and Debian Policy
+ 
+ [Maintenance/Owner]
+ - The owning team will be Ubuntu Server and I have their acknowledgement for
+   that commitment
+ - The future owning team is already subscribed to the package
+ - This does not use static builds
+ - This does not use vendored code
+ - This package is not rust based
+ 
+ [Background information]
+ The Package description explains the package well
+ Upstream Name is s3transfer
+ Link to upstream project https://github.com/boto/s3transfer

** Description changed:

  [Availability]
  The package python-s3transfer is already in Ubuntu universe.
  The package python-s3transfer build for the architectures it is designed to 
work on.
  They build amd64 only (but binary is arch-all)
  Link to package https://launchpad.net/ubuntu/+source/python-s3transfer
  
  [Rationale]
  The package python-s3transfer is required in Ubuntu main for python-boto3
  The package python-s3transfer will not generally be useful for a large part of
  our user base, but is important/helpful still because it is required by 
python-boto3
  which is in the MIR process as a dependency of simplestreams.
  python-boto3 MIR link: 
https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217
  
  - The package python-s3transfer is required in Ubuntu main through the
  same scheduled requested for the python-boto3 promotion, since python-
  boto3 depends on it.
  
  [Security]
  - No CVEs/security issues in this software in the past:
  

[Bug 2061751] Re: [MIR] python-botocore as dependency of python-s3transfer

2024-04-16 Thread Alberto Contreras
$ lintian --pedantic python-botocore_1.34.46+repack-1.dsc
P: python-botocore source: package-uses-old-debhelper-compat-version 12
P: python-botocore source: silent-on-rules-requiring-root [debian/control]

** Description changed:

- TODO
+ [Availability]
+ The package python-botocore is already in Ubuntu universe.
+ The package python-botocore build for the architectures it is designed to 
work on.
+ They build amd64 only (but binary is arch-all)
+ Link to package: https://launchpad.net/ubuntu/+source/python-botocore
+ 
+ [Rationale]
+ The package python-botocore is required in Ubuntu main for python-boto3 as an 
indirect dependency
+ The package python-botocore will not generally be useful for a large part of
+ our user base, but is important/helpful still because it is required by 
python-boto3
+ which is in the MIR process as a dependency of simplestreams.
+ python-boto3 MIR link: 
https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217
+ 
+ - The package python-botocore is required in Ubuntu main through the
+ same scheduled requested for the python-boto3 promotion, since python-
+ boto3 depends on it.
+ 
+ [Security]
+ - No CVEs/security issues in this software in the past:
+ (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-botocore
+ (0)https://security-tracker.debian.org/tracker/source-package/python-botocore
+ 
(0)https://ubuntu.com/security/cves?q==python-botocore===
+ 
+ No `suid` or `sgid` binaries
+ No executables in `/sbin` and `/usr/sbin`
+ Package does not install services, timers or recurring jobs
+ Packages does not open privileged ports (ports < 1024).
+ Package does not expose any external endpoints
+ Packages does not contain extensions to security-sensitive software
+ (filters, scanners, plugins, UI skins, ...)
+ 
+ [Quality assurance - function/usage]
+ The package works well right after install. It's a python library.
+ 
+ [Quality assurance - maintenance]
+ - The package is maintained well in Debian/Ubuntu/Upstream and does
+   not have too many, long-term & critical, open bugs
+   - Ubuntu (4)https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bugs
+   - Debian 
(1)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-botocore
+   - Upstream's bug tracker (112)https://github.com/boto/botocore/issues
+ Looks normal for the age and impact of these libraries
+ - The package does not deal with exotic hardware we cannot support
+ 
+ [Quality assurance - testing]
+ - The package does not run a test at build time because it is not configured 
to do so,
+ the upstream source code contains unit tests
+ - The package does not run an autopkgtest because they are not configured to 
do so.
+ 
+ [Quality assurance - packaging]
+ - debian/watch is present and works
+ - debian/control defines a correct Maintainer field
+ - Lintian does not run as part of the build
+   
https://launchpadlibrarian.net/715514517/buildlog_ubuntu-noble-amd64.python-botocore_1.34.46+repack-1_BUILDING.txt.gz
+ - Lintian overrides are present, but ok because they are justified:
+ 
+ # This is a false positive, likely an occurrence of #1019980
+ python-botocore source: source-is-missing [docs/source/_templates/page.html]
+ 
+ - This package does not rely on obsolete or about to be demoted packages.
+ - This package has no python2 or GTK2 dependencies
+ - The package will not be installed by default
+ - Packaging and build is easy, link to debian/rules:
+   https://git.launchpad.net/ubuntu/+source/python-botocore/tree/debian/rules
+ 
+ [UI standards]
+ - Application is not end-user facing (does not need translation)
+ 
+ [Dependencies]
+ - No further depends or recommends dependencies that are not yet in main
+ 
+ [Standards compliance]
+ - This package correctly follows FHS and Debian Policy
+ 
+ [Maintenance/Owner]
+ - The owning team will be Ubuntu Server and I have their acknowledgement for
+   that commitment
+ - The future owning team is already subscribed to the package
+ - This does not use static builds
+ - This does not use vendored code
+ - This package is not rust based
+ 
+ [Background information]
+ The Package description explains the package well
+ Upstream Name is botocore
+ Link to upstream project https://github.com/boto/botocore

** Description changed:

  [Availability]
  The package python-botocore is already in Ubuntu universe.
  The package python-botocore build for the architectures it is designed to 
work on.
  They build amd64 only (but binary is arch-all)
  Link to package: https://launchpad.net/ubuntu/+source/python-botocore
  
  [Rationale]
  The package python-botocore is required in Ubuntu main for python-boto3 as an 
indirect dependency
  The package python-botocore will not generally be useful for a large part of
  our user base, but is important/helpful still because it is required by 
python-boto3
  which is in the MIR process as a dependency of simplestreams.
  python-boto3 MIR link: 
https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug/2061217

[Bug 2061217] Re: [MIR] python-boto3

2024-04-16 Thread Alberto Contreras
** Description changed:

  [Availability]
- The packages python-boto3, python-s3transfer and python-botocore are already 
in Ubuntu universe.
- The packages python-boto3, python-s3transfer and python-botocore build for 
the architectures it is designed to work on.
+ The package python-boto3 is already in Ubuntu universe.
+ The package python-boto3 build for the architectures it is designed to work 
on.
  They build amd64 only (but binary is arch-all)
- Link to package:
-   - https://launchpad.net/ubuntu/+source/python-boto3
-   - https://launchpad.net/ubuntu/+source/python-s3transfer
-   - https://launchpad.net/ubuntu/+source/python-botocore
+ Link to package: https://launchpad.net/ubuntu/+source/python-boto3
  
  [Rationale]
  Simplestreams itself is in main for quite a while since bug 1220427.
  The package python-boto3 is required in Ubuntu main for simplestreams
  The package python-boto3 will not generally be useful for a large part of
  our user base, but is important/helpful still because it is required by 
simplestreams
  Additionally new use-cases enabled by this are demoting python-boto to 
universe because
  the only reverse depency in main is simplestreams and debian is going to drop 
support
  for python-boto, see LP: 2052437
  The package python-boto3 is a new runtime dependency of package simplestreams 
that
  we already support
  python-boto is not compatible with python3.12, the only python supported in 
noble, thus
  to commit to a long term support of simplestreams, it's better to depend on 
dependencies
  that have upstream support
  
  The package python-boto3 is required in Ubuntu main no later than noble is 
released
  due to being required by a new upload of simplestreams in noble-proposed to 
make it
  work on python3.12 and to be able to drop python-boto from noble archives.
  
  python-s3transfer is a binary dependency of python-boto3
  python-botocore is a binary dependency of python-s3transfer
  
  [Security]
  - No CVEs/security issues in this software in the past:
- 
  (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-boto3
  
(0)https://ubuntu.com/security/cves?q==python-boto3===
  (0)https://security-tracker.debian.org/tracker/source-package/python-boto3
- 
- (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-s3transfer
- 
(0)https://security-tracker.debian.org/tracker/source-package/python-s3transfer
- 
(0)https://ubuntu.com/security/cves?q==python-s3transfer===
- 
- (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-botocore
- (0)https://security-tracker.debian.org/tracker/source-package/python-botocore
- 
(0)https://ubuntu.com/security/cves?q==python-botocore===
  
  No `suid` or `sgid` binaries
  No executables in `/sbin` and `/usr/sbin`
  Package does not install services, timers or recurring jobs
  Packages does not open privileged ports (ports < 1024).
  Package does not expose any external endpoints
  Packages does not contain extensions to security-sensitive software
  (filters, scanners, plugins, UI skins, ...)
  
  [Quality assurance - function/usage]
  The package works well right after install. It's a python library.
  
  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu/Upstream and does
    not have too many, long-term & critical, open bugs
-   - Ubuntu
- - (2)https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug
- - (1)https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bugs
- - (4)https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bugs
-   - Debian
- - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-boto3
- - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-s3transfer
- - (1)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-botocore
-   - Upstream's bug tracker
- - (192)https://github.com/boto/boto3/issues
- - (24)https://github.com/boto/s3transfer/issues
- - (112)https://github.com/boto/botocore/issues
+   - Ubuntu (2)https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug
+   - Debian (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-boto3
+   - Upstream's bug tracker (192)https://github.com/boto/boto3/issues
  Looks normal for the age and impact of these libraries
  - The package does not deal with exotic hardware we cannot support
  
  [Quality assurance - testing]
- - The packages do not run a test at build time because it is not configured 
to do so,
+ - The package does not run a test at build time because it is not configured 
to do so,
  the upstream source code contains unit tests
- - The packages do not run an autopkgtest because they are not configured to 
do so.
+ - The package does not run an autopkgtest because they are not configured to 
do so.
  
  [Quality assurance - packaging]
  - debian/watch is present and works
  - debian/control defines a correct Maintainer field
  - Lintian does not run as part of the build
-   - 

[Bug 2061750] [NEW] [MIR] python-s3transfer as dependency of python-boto3

2024-04-16 Thread Alberto Contreras
Public bug reported:

TODO

** Affects: python-s3transfer (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
   [MIR] python-s3transfer as dependency of python-boto3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061751] [NEW] [MIR] python-botocore as dependency of python-s3transfer

2024-04-16 Thread Alberto Contreras
Public bug reported:

TODO

** Affects: python-botocore (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [MIR] python-botocore as dependency of python-s3transfer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061217] Re: [MIR] python-boto3

2024-04-15 Thread Alberto Contreras
** Description changed:

  [Availability]
- The package python-boto3 is already in Ubuntu universe.
- The package python-boto3 build for the architectures it is designed to work 
on.
- It builds amd64 only (but binary is arch-all)
- Link to package https://launchpad.net/ubuntu/+source/python-boto3
+ The packages python-boto3, python-s3transfer and python-botocore are already 
in Ubuntu universe.
+ The packages python-boto3, python-s3transfer and python-botocore build for 
the architectures it is designed to work on.
+ They build amd64 only (but binary is arch-all)
+ Link to package:
+   - https://launchpad.net/ubuntu/+source/python-boto3
+   - https://launchpad.net/ubuntu/+source/python-s3transfer
+   - https://launchpad.net/ubuntu/+source/python-botocore
  
  [Rationale]
  The package python-boto3 is required in Ubuntu main for simplestreams
  The package python-boto3 will not generally be useful for a large part of
  our user base, but is important/helpful still because it is required by 
simplestreams
  Additionally new use-cases enabled by this are demoting python-boto to 
universe because
  the only reverse depency in main is simplestreams and debian is going to drop 
support
  for python-boto, see LP: 2052437
  The package python-boto3 is a new runtime dependency of package simplestreams 
that
  we already support
  python-boto is not compatible with python3.12, the only python supported in 
noble, thus
  to commit to a long term support of simplestreams, it's better to depend on 
dependencies
  that have upstream support
  
  The package python-boto3 is required in Ubuntu main no later than noble is 
released
  due to being required by a new upload of simplestreams in noble-proposed to 
make it
  work on python3.12 and to be able to drop python-boto from noble archives.
+ 
+ python-s3transfer is a binary dependency of python-boto3
+ python-botocore is a binary dependency of python-s3transfer
  
  [Security]
  - No CVEs/security issues in this software in the past:
  
  (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-boto3
  
(0)https://ubuntu.com/security/cves?q==python-boto3===
  (0)https://security-tracker.debian.org/tracker/source-package/python-boto3
  
  (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-s3transfer
  
(0)https://security-tracker.debian.org/tracker/source-package/python-s3transfer
  
(0)https://ubuntu.com/security/cves?q==python-s3transfer===
  
  (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-botocore
  (0)https://security-tracker.debian.org/tracker/source-package/python-botocore
  
(0)https://ubuntu.com/security/cves?q==python-botocore===
  
  No `suid` or `sgid` binaries
  No executables in `/sbin` and `/usr/sbin`
  Package does not install services, timers or recurring jobs
  Packages does not open privileged ports (ports < 1024).
  Package does not expose any external endpoints
  Packages does not contain extensions to security-sensitive software
  (filters, scanners, plugins, UI skins, ...)
  
  [Quality assurance - function/usage]
  The package works well right after install. It's a python library.
  
  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu/Upstream and does
not have too many, long-term & critical, open bugs
- Ubuntu
  - (2)https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug
  - (1)https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bugs
  - (4)https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bugs
- Debian
  - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-boto3
  - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-s3transfer
  - (1)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-botocore
- Upstream's bug tracker
  - (192)https://github.com/boto/boto3/issues
  - (24)https://github.com/boto/s3transfer/issues
  - (112)https://github.com/boto/botocore/issues
  Looks normal for the age and impact of these libraries
  - The package does not deal with exotic hardware we cannot support
  
  [Quality assurance - testing]
- - The package does not run a test at build time because it is not configured 
to do so,
+ - The packages do not run a test at build time because it is not configured 
to do so,
  the upstream source code contains unit tests
- - The package does not run an autopkgtest because they are not enabled
+ - The packages do not run an autopkgtest because they are not configured to 
do so.
  
  [Quality assurance - packaging]
  - debian/watch is present and works
  - debian/control defines a correct Maintainer field
  - Lintian does not run as part of the build
- 
https://launchpadlibrarian.net/715514166/buildlog_ubuntu-noble-amd64.python-boto3_1.34.46+dfsg-1_BUILDING.txt.gz
- 
https://launchpadlibrarian.net/709963913/buildlog_ubuntu-noble-amd64.python-s3transfer_0.10.0-1_BUILDING.txt.gz
- 

[Bug 2061217] Re: [MIR] python-boto3

2024-04-15 Thread Alberto Contreras
$ lintian --pedantic python-boto3_1.34.46+dfsg-1.dsc
P: python-boto3 source: package-uses-old-debhelper-compat-version 12
P: python-boto3 source: silent-on-rules-requiring-root [debian/contro

$ lintian --pedantic python-s3transfer_0.10.0-1.dsc

$ lintian --pedantic python-botocore_1.34.46+repack-1.dsc 
P: python-botocore source: package-uses-old-debhelper-compat-version 12
P: python-botocore source: silent-on-rules-requiring-root [debian/control]

** Description changed:

- I'm filing this MIR stub for tracking but I am not actively working on
- this MIR.
+ [Availability]
+ The package python-boto3 is already in Ubuntu universe.
+ The package python-boto3 build for the architectures it is designed to work 
on.
+ It builds amd64 only (but binary is arch-all)
+ Link to package https://launchpad.net/ubuntu/+source/python-boto3
  
- See https://launchpad.net/bugs/2052437 for background. I filed a
- separate bug because I think it could be confusing to have a MIR bug
- with too many packages affected.
+ [Rationale]
+ The package python-boto3 is required in Ubuntu main for simplestreams
+ The package python-boto3 will not generally be useful for a large part of
+ our user base, but is important/helpful still because it is required by 
simplestreams
+ Additionally new use-cases enabled by this are demoting python-boto to 
universe because
+ the only reverse depency in main is simplestreams and debian is going to drop 
support
+ for python-boto, see LP: 2052437
+ The package python-boto3 is a new runtime dependency of package simplestreams 
that
+ we already support
+ python-boto is not compatible with python3.12, the only python supported in 
noble, thus
+ to commit to a long term support of simplestreams, it's better to depend on 
dependencies
+ that have upstream support
  
- python-boto only has one current reverse-depends in main: simplestreams.
- simplestreams has now switched to python-boto3 in noble-proposed but is
- blocked because python-boto3 is not in main yet.
+ The package python-boto3 is required in Ubuntu main no later than noble is 
released
+ due to being required by a new upload of simplestreams in noble-proposed to 
make it
+ work on python3.12 and to be able to drop python-boto from noble archives.
  
- Please promote python-boto3 to main so that we can demote python-boto to
- universe once simplestreams migrates out of noble-proposed.
+ [Security]
+ - No CVEs/security issues in this software in the past:
+ 
+ (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-boto3
+ 
(0)https://ubuntu.com/security/cves?q==python-boto3===
+ (0)https://security-tracker.debian.org/tracker/source-package/python-boto3
+ 
+ (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-s3transfer
+ 
(0)https://security-tracker.debian.org/tracker/source-package/python-s3transfer
+ 
(0)https://ubuntu.com/security/cves?q==python-s3transfer===
+ 
+ (0)https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=python-botocore
+ (0)https://security-tracker.debian.org/tracker/source-package/python-botocore
+ 
(0)https://ubuntu.com/security/cves?q==python-botocore===
+ 
+ No `suid` or `sgid` binaries
+ No executables in `/sbin` and `/usr/sbin`
+ Package does not install services, timers or recurring jobs
+ Packages does not open privileged ports (ports < 1024).
+ Package does not expose any external endpoints
+ Packages does not contain extensions to security-sensitive software
+ (filters, scanners, plugins, UI skins, ...)
+ 
+ [Quality assurance - function/usage]
+ The package works well right after install. It's a python library.
+ 
+ [Quality assurance - maintenance]
+ - The package is maintained well in Debian/Ubuntu/Upstream and does
+   not have too many, long-term & critical, open bugs
+   - Ubuntu
+ - (2)https://bugs.launchpad.net/ubuntu/+source/python-boto3/+bug
+ - (1)https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bugs
+ - (4)https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bugs
+   - Debian
+ - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-boto3
+ - (0)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-s3transfer
+ - (1)https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-botocore
+   - Upstream's bug tracker
+ - (192)https://github.com/boto/boto3/issues
+ - (24)https://github.com/boto/s3transfer/issues
+ - (112)https://github.com/boto/botocore/issues
+ Looks normal for the age and impact of these libraries
+ - The package does not deal with exotic hardware we cannot support
+ 
+ [Quality assurance - testing]
+ - The package does not run a test at build time because it is not configured 
to do so,
+ the upstream source code contains unit tests
+ - The package does not run an autopkgtest because they are not enabled
+ 
+ [Quality assurance - packaging]
+ - debian/watch is present and works
+ - debian/control defines a correct Maintainer field
+ - Lintian does not run as part of the build
+   - 

[Bug 2061217] Re: [MIR] python-boto3

2024-04-15 Thread Alberto Contreras
** Also affects: python-botocore (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [MIR] python-boto3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061217] Re: [MIR] python-boto3

2024-04-15 Thread Alberto Contreras
python-botocore is a dependency of python-s3transfer thus it has to be
MIRed too per the same reasoning as
https://bugs.launchpad.net/ubuntu/+source/python-
boto3/+bug/2061217/comments/2

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

Title:
  [MIR] python-boto3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061217] Re: [MIR] python-boto3

2024-04-15 Thread Alberto Contreras
I am going to start working on the MIR template.

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

Title:
  [MIR] python-boto3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy

2024-04-12 Thread Alberto Contreras
DisasteR: difficult to say if it was a change from the cloud-images,
cloud-init or other package without access to the jammy instance. But in
any case, write_files, bootcmd and runcmd are config modules that can
break the system in multiple ways as they give total control to the user
and they have to be used with care.

I do not think Ubuntu can ensure backwards / forwards compatibility of
those cloud-init modules in every case.

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

Title:
  cloud-init cloud-config for ssh broken in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy

2024-04-12 Thread Alberto Contreras
Hi DisasteR, thanks for attaching the logs.

ssh_pwauth gets handled by the set_passwords config module, which runs
as part of the cloud-config stage.

The problem is that cloud-config and cloud-final stages didn't run
because cloud-init is instructed to be disabled.

Some stanza in your user-data, vendor-data, instance-data or system-cfg
instructs the config module write_files, which runs before cloud-config,
to disable cloud-init.

One can see this in the log files and in:

# /run/cloud-init/combined-cloud-config.json
...
 "write_files": [
  {
   "owner": "root:root",
   "path": "/etc/cloud/cloud-init.disabled",
   "permissions": "0644"
  }

One solution, if the disablement is still desired, is to use the defer
subkey[1] of write-files to instruct cloud-init to touch the file as
part of the cloud-final stage, not disturbing the other stages during
the first boot.

[1] https://docs.cloud-init.io/en/latest/reference/modules.html#write-
files

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

Title:
  cloud-init cloud-config for ssh broken in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy

2024-04-11 Thread Alberto Contreras
Hi @DisatesR.

In addition to John's comment, collecting and sharing cloud-init's
logs[1] (making sure no sensitive data is attached) might help us to
triage what's happening.

[1]https://cloudinit.readthedocs.io/en/latest/howto/bugs.html#collect-
logs

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

Title:
  cloud-init cloud-config for ssh broken in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2052437] Re: python-boto: obsolete, replaced by python-boto3

2024-04-10 Thread Alberto Contreras
** Changed in: simplestreams (Ubuntu)
   Status: New => In Progress

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

Title:
  python-boto: obsolete, replaced by python-boto3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heat-cfntools/+bug/2052437/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2052437] Re: python-boto: obsolete, replaced by python-boto3

2024-04-06 Thread Alberto Contreras
** Changed in: simplestreams (Ubuntu)
 Assignee: (unassigned) => Alberto Contreras (aciba)

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

Title:
  python-boto: obsolete, replaced by python-boto3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heat-cfntools/+bug/2052437/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058133] Re: update-manager applet does exit successfully

2024-03-21 Thread Alberto Contreras
Thanks for the logs.

The output of `pro security-status --format=json` and the internal error
look correct, so I'm going to mark the ubuntu-advantage-tools bit as
invalid.

It feels like this is something that should be handled and fixed in
update-manager. https://bugs.launchpad.net/ubuntu/+source/update-
manager/+bug/2049785 sounds very similar to this.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  update-manager applet does exit successfully

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058133/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058158] Re: update-manager crashes when started

2024-03-21 Thread Alberto Contreras
*** This bug is a duplicate of bug 2058133 ***
https://bugs.launchpad.net/bugs/2058133

** Information type changed from Private to Public

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

Title:
  update-manager crashes when started

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058158/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057965] Re: google-startup-scripts runs before cloud-init finished network setup

2024-03-19 Thread Alberto Contreras
Why the patch in https://bugs.launchpad.net/ubuntu/+source/google-guest-
agent/+bug/2057965/comments/5 and Impact description order gga after
cloud-final.service but the merged (temporal) cpc_packaging.extra MRs
order gga after cloud-config.service?

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

Title:
  google-startup-scripts runs before cloud-init finished network setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2057965/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056779] Re: Don't offer realtime on Raspberry Pi

2024-03-15 Thread Alberto Contreras
** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Triaged

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

Title:
  Don't offer realtime on Raspberry Pi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2056779/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056439] Re: Latest cloud-init fails with AttributeError: 'DataSourceVMware' object has no attribute 'rpctool'

2024-03-11 Thread Alberto Contreras
Thanks, Thomas, for reporting this!

Upstream PR fixing this: https://github.com/canonical/cloud-
init/pull/5021

** Changed in: cloud-init (Ubuntu)
   Status: New => In Progress

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Chad Smith (chad.smith)

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

Title:
  Latest cloud-init fails with AttributeError: 'DataSourceVMware' object
  has no attribute 'rpctool'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056439/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055754] Re: Xubuntu Minimal install failed to create usable user

2024-03-04 Thread Alberto Contreras
Attaching subiquity as the installation was driven by it.

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

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

Title:
  Xubuntu Minimal install failed to create usable user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2055754/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet

2024-02-29 Thread Alberto Contreras
cloud-init upstream PR adding test coverage for this issue:
https://github.com/canonical/cloud-init/pull/4982

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

Title:
  netplan/systemd-networkd: route metric not applied to routes to the
  local subnet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2055397/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet

2024-02-29 Thread Alberto Contreras
Attaching cloud-init logs, which include journal logs.

** Attachment added: "cloud-init.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055397/+attachment/5750656/+files/cloud-init.tar.gz

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

Title:
  netplan/systemd-networkd: route metric not applied to routes to the
  local subnet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2055397/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet

2024-02-29 Thread Alberto Contreras
Marking cloud-init as invalid as I think there is no workaround to fix this 
issue.
Adding netplan.io for reference and awareness.

After confirmation from systemd-networkd, I wonder if it would be
feasible / reasonable to backport
https://github.com/systemd/systemd/pull/19344 to focal.

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

Title:
  netplan/systemd-networkd: route metric not applied to routes to the
  local subnet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2055397/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055397] [NEW] netplan/systemd-networkd: route metric not applied to routes to the local subnet

2024-02-29 Thread Alberto Contreras
Public bug reported:

Cloud-init introduced a feature to configure policy routing on AWS EC2 
instances with multiple NICs in
https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb
 targeting v24.1.

Cloud-init generates the following netplan config:

```
$ cat /etc/netplan/50-cloud-init.yaml
network:
ethernets:
ens5:
dhcp4: true
dhcp4-overrides: 
route-metric: 100
dhcp6: true
dhcp6-overrides: *id001
match:
macaddress: 0a:c8:ab:90:c2:fb
set-name: ens5
ens6:
dhcp4: true
dhcp4-overrides:
route-metric: 200
use-routes: true
dhcp6: false
match:
macaddress: 0a:c6:55:a1:dc:3b
routes:
-   table: 101
to: 0.0.0.0/0
via: 192.168.0.1
-   table: 101
to: 192.168.0.0/20
routing-policy:
-   from: 192.168.10.212
table: 101
set-name: ens6
version: 2
```

Which renders the following systemd-networkd config files:

```
$ cat 10-netplan-ens5.link
[Match]
MACAddress=0a:c8:ab:90:c2:fb

[Link]
Name=ens5
WakeOnLan=off


$ cat 10-netplan-ens5.network
[Match]
MACAddress=0a:c8:ab:90:c2:fb
Name=ens5

[Network]
DHCP=yes
LinkLocalAddressing=ipv6

[DHCP]
RouteMetric=100
UseMTU=true


$ cat 10-netplan-ens6.link
[Match]
MACAddress=0a:c6:55:a1:dc:3b

[Link]
Name=ens6
WakeOnLan=off


$ cat 10-netplan-ens6.network
[Match]
MACAddress=0a:c6:55:a1:dc:3b
Name=ens6

[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6

[Route]
Destination=0.0.0.0/0
Gateway=192.168.0.1
Table=101

[Route]
Destination=192.168.0.0/20
Scope=link
Table=101

[RoutingPolicyRule]
From=192.168.10.212
Table=101

[DHCP]
RouteMetric=200
UseMTU=true
```

Which configures the instance with the following state in Ubuntu Focal:

```
$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: ens5:  mtu 9001 qdisc mq state UP group 
default qlen 1000
link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff
inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5
   valid_lft 2087sec preferred_lft 2087sec
inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic 
noprefixroute
   valid_lft 440sec preferred_lft 130sec
inet6 fe80::8c8:abff:fe90:c2fb/64 scope link
   valid_lft forever preferred_lft forever
3: ens6:  mtu 9001 qdisc mq state UP group 
default qlen 1000
link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff
inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6
   valid_lft 2083sec preferred_lft 2083sec
inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link
   valid_lft forever preferred_lft forever


$ ip route show
default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.94 metric 100
default via 192.168.0.1 dev ens6 proto dhcp src 192.168.10.212 metric 200
192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.12.94
192.168.0.0/20 dev ens6 proto kernel scope link src 192.168.10.212
192.168.0.1 dev ens5 proto dhcp scope link src 192.168.12.94 metric 100
192.168.0.1 dev ens6 proto dhcp scope link src 192.168.10.212 metric 200

$ ip rule show
0:  from all lookup local
0:  from 192.168.10.212 lookup 101
32766:  from all lookup main
32767:  from all lookup default


$ ip route show table 101
default via 192.168.0.1 dev ens6 proto static onlink
192.168.0.0/20 dev ens6 proto static scope link
```

The issue here is that the instance is not reachable from the same subnet via 
the private ipv4 of the primary NIC,
packets are routed to egress via ens6 and dropped.

The cause is that interface metrics are not applied to local subnet routes with 
systemd 245 (245.4-4ubuntu3.23).
On newer systemd versions, as in Jammy, the metrics are correctly applied.
Correcting them manually fixes the issue in Focal.


Expected main route table:

default via 192.168.0.1 dev ens5 proto dhcp src 192.168.12.94 metric 100
default via 192.168.0.1 dev ens6 proto dhcp src 192.168.10.212 metric 200
192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.12.94 metric 100
192.168.0.0/20 dev ens6 proto kernel scope link src 192.168.10.212 metric 200
192.168.0.1 dev ens5 proto dhcp scope link src 192.168.12.94 metric 100
192.168.0.1 dev ens6 proto dhcp scope link src 192.168.10.212 metric 200

It looks like the upstream systemd issue and PR fixing this problem are:

https://github.com/systemd/systemd/issues/928
https://github.com/systemd/systemd/pull/19344

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: netplan.io (Ubuntu)
 Importance: Undecided
 Status: 

[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.

2024-02-29 Thread Alberto Contreras
Hello Nobutu. Thanks again for reporting this.

I have been trying to reproduce the error with no success. I tried some
combinations of:

- In lxd container with [jammy, noble]
- [pro downgrade / upgrade targeting 31.1]
- pro enable / disable
- [pro downgrade / upgrade targeting 31.1]
- apt updadate
- apt upgrade

Could you please provide more information about it?

Many thanks.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2055239/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977646] Re: Snap apps launch time are EXTREMELY slow

2022-06-05 Thread Alberto Mardegan
*** This bug is a duplicate of bug 1833004 ***
https://bugs.launchpad.net/bugs/1833004

Thanks Islam for reporting this. I'm going to mark this as a duplicate,
as we already have this issue reported as bug 1833004.

** This bug has been marked a duplicate of bug 1833004
   Application SNAP is slower than DEB at first launch

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

Title:
  Snap apps launch time are EXTREMELY slow

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778375] Re: All snap loops are being output for lsblk, blkid, and fdisk -l.

2022-06-05 Thread Alberto Mardegan
Hi Anthony, thanks for reporting this bug (I just found it accidentally
while browsing through the existing bugs. I'm afraid that there's little
we can do about the fact that these programs also list the mounted snaps
-- there might be even scripts, by now, which rely on this behaviour.

Where I think we could do something, it's about the fact that the same
snap can appear twice, if there are two revisions of it installed; I
guess we could avoid mounting the old one -- I'll check with the rest of
the team to understand if there is a reason why it has to be this way.

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

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

Title:
  All snap loops are being output for lsblk, blkid, and fdisk -l.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975744] Re: purging cloud-init doesn't remove its network configuration files

2022-06-01 Thread Alberto Contreras
Reproduced with:

```sh
$ lxc launch ubuntu:jammy jj
$ lxc exec jj -- cloud-init status --wait
$ lxc exec jj -- cloud-init --version
/usr/bin/cloud-init 22.1-14-g2e17a0d6-0ubuntu1~22.04.5
$ lxc exec jj -- apt purge -y cloud-init
...
dpkg: warning: while removing cloud-init, directory '/etc/cloud' not empty so 
not removed
...
$ lxc exec jj -- ls /etc/cloud
build.info
$ lxc exec jj -- ls /etc/netplan
50-cloud-init.yaml
```

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

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

Title:
  purging cloud-init doesn't remove its network configuration files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1975744/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975922] Re: custom image deploy get failed in cmd-curthooks of DISTROS[DISTROS.index(distname)]

2022-05-31 Thread Alberto Donato
** No longer affects: curtin (Ubuntu)

** Also affects: curtin
   Importance: Undecided
   Status: New

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

Title:
  custom image deploy get failed in cmd-curthooks of
  DISTROS[DISTROS.index(distname)]

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975922] Re: custom image deploy get failed in cmd-curthooks of DISTROS[DISTROS.index(distname)]

2022-05-30 Thread Alberto Donato
Can you please check (and possibly attach) the machine log for errors.
It's under
/var/snap/maas/common/log/rsyslog/$machine_name/$date/messages

** Changed in: maas
   Status: New => Incomplete

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

Title:
  custom image deploy get failed in cmd-curthooks of
  DISTROS[DISTROS.index(distname)]

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975922] Re: custom image deploy get failed in cmd-curthooks of DISTROS[DISTROS.index(distname)]

2022-05-30 Thread Alberto Donato
** Also affects: curtin (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  custom image deploy get failed in cmd-curthooks of
  DISTROS[DISTROS.index(distname)]

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

2022-05-29 Thread Alberto Mardegan
Hi Fernando, and thanks for reporting this bug!

  If, as you wrote in the bug description, you reproduce it when logging
in with your uername and password, then this bug is not related to bug
1593407, which is about the "guest session" (that is the session for
those users who don't have a login in the machine).

There appears to be something wrong with the user session. Are you using
Wayland or Xorg?

Also, can you please attach the output of these commands (you can run
them before opening the troublesome link in firefox, while your session
is still working):

systemctl --user status xdg-document-portal.service
systemctl --user status 
snap.snapd-desktop-integration.snapd-desktop-integration.service
   


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

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

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959417] Re: browsers and other apps packaged as snaps can't read files under ~/.local/share/

2022-05-26 Thread Alberto Mardegan
For the record, I've opened a discussion in the jupiter-notebook forums:
https://github.com/jupyter/notebook/discussions/6436

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

Title:
  browsers and other apps packaged as snaps can't read files under
  ~/.local/share/

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871148] Re: services start before apparmor profiles are loaded

2022-05-25 Thread Alberto Mardegan
Oh, this is interesting! Then, Etienne, my suggestion is the following:
re-enable the snapd.apparmor service, and if that (as I expect) fixes
the bug, let's stop discussing this issue here, and instead open a
separate issue about the service being disabled.

It may be that something went wrong during the upgrade to Jammy. If we
file this as a separate bug, we might be able to see if other people
have met the same issue.

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

Title:
  services start before apparmor profiles are loaded

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871148] Re: services start before apparmor profiles are loaded

2022-05-24 Thread Alberto Mardegan
Oh, thanks Alex, I forgot that we have our own service for loading the
AppArmor profiles of the snaps!

Etienne, could you please show the output of

sudo systemctl status snapd.apparmor

?

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

Title:
  services start before apparmor profiles are loaded

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2022-05-24 Thread Alberto Mardegan
Some updates, while I'm still investigating this on a QEMU running
Ubuntu Core 22.

The "snap auto-import" command is only needed on Ubuntu Core systems, so
the plan is to remove the /lib/udev/rules.d/66-snapd-autoimport.rules
from the snapd deb package (and consequently also from the snapd snap).

We do still need it in UC, but as a matter of fact the script is already
provided by the Ubuntu Core repositories:

- UC22: 
https://github.com/snapcore/core-base/blob/main/static/usr/lib/udev/rules.d/66-snapd-autoimport.rules
- UC20: 
https://github.com/snapcore/core20/blob/master/static/usr/lib/udev/rules.d/66-snapd-autoimport.rules
- UC18: 
https://github.com/snapcore/core18/blob/master/static/lib/udev/rules.d/66-snapd-autoimport.rules
- UC16: **missing**

The file in UC22 seems already correct, in that it does not call
unshare. So the only one left out is UC16, where we will add the udev
rule that we currently have in snapd; after that, we will remove the
rule from snapd and this bug for the desktop will be gone for good.

There is a remaining problem, however: the systemd-udevd.service in
Ubuntu 22 disallows the mount operation, so we'll have to update the
unit file to allow it. I think we'll also need to update the auto-import
command itself, because it appears that all errors while accessing the
devices are silenced, so we would have never known of this problem, if
it wasn't for this bug report.

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2022-05-23 Thread Alberto Mardegan
Thanks Nick for pointing me to this bug; I was working on the same
issue, as reported in a duplicate bug.

As far as the classic desktop is concerned, this bug occurs not because
of the failed mount, but because of "unshare" failing (see the
discussion in bug 1971955); in any case, the analysis by Jiwei Sun is
correct: it's happening because of the added SystemCallFilter entry to
the udev unit file.

** Changed in: snapd
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: snapd
   Importance: Undecided => High

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-23 Thread Alberto Mardegan
*** This bug is a duplicate of bug 1966203 ***
https://bugs.launchpad.net/bugs/1966203

Thanks Nick, indeed! I'm closing this since 1966203 was reported first.

** This bug has been marked a duplicate of bug 1966203
   Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit 
code 1." in Ubuntu 22.04

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972109] Re: [needs-packaging] ipu6-drivers

2022-05-23 Thread Alberto Milone
As with the other package, "Architecture" should be set to amd64 only,
since this is for Intel Alder Lake platforms. Other that this, I could
not find any issues with the package.

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

Title:
  [needs-packaging] ipu6-drivers

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-23 Thread Alberto Mardegan
** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972106] Re: [needs-packaging] ivsc-driver

2022-05-23 Thread Alberto Milone
Maybe "Architecture" should be set to amd64 only, since this is for
Intel Alder Lake platforms. Other that this, I could not find any issues
with the package.

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

Title:
  [needs-packaging] ivsc-driver

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-23 Thread Alberto Mardegan
Hi again Vincent :-)
  Please ignore the part about adding more attributes to the SystemCallFilter 
list; I don't think it's a road we want to follow.

What would be more important for me to know, is whether things work if
you change the RUN line to just

RUN+="/usr/bin/snap auto-import --mount=/dev/%k"

Please let me know if this works. :-)

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-23 Thread Alberto Mardegan
Thanks Vincent. I think I got some hints: I downloaded the package from
Jammy, I unpacked it and then ran a diff on the systemd unit file for
the udev service (since in the documentation of udev[1] it's written
that programs are executed in a sandbox) from the version in Focal:

==
--- /lib/systemd/system/systemd-udevd.service   2022-04-21 15:54:39.0 
+0300
+++ lib/systemd/system/systemd-udevd.service2022-04-07 22:28:15.0 
+0300
@@ -1,4 +1,4 @@
-#  SPDX-License-Identifier: LGPL-2.1+
+#  SPDX-License-Identifier: LGPL-2.1-or-later
 #
 #  This file is part of systemd.
 #
@@ -8,7 +8,7 @@
 #  (at your option) any later version.
 
 [Unit]
-Description=udev Kernel Device Manager
+Description=Rule-based Manager for Device Events and Files
 Documentation=man:systemd-udevd.service(8) man:udev(7)
 DefaultDependencies=no
 After=systemd-sysusers.service systemd-hwdb-update.service
@@ -16,8 +16,10 @@
 ConditionPathIsReadWrite=/sys
 
 [Service]
+DeviceAllow=block-* rwm
+DeviceAllow=char-* rwm
 Type=notify
-# Note that udev also adjusts the OOM score internally and will reset the 
value internally for its workers
+# Note that udev will reset the value internally for its workers
 OOMScoreAdjust=-1000
 Sockets=systemd-udevd-control.socket systemd-udevd-kernel.socket
 Restart=always
@@ -27,11 +29,14 @@
 KillMode=mixed
 TasksMax=infinity
 PrivateMounts=yes
+ProtectClock=yes
 ProtectHostname=yes
 MemoryDenyWriteExecute=yes
 RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
 RestrictRealtime=yes
 RestrictSUIDSGID=yes
+SystemCallFilter=@system-service @module @raw-io bpf
+SystemCallErrorNumber=EPERM
 LockPersonality=yes
 IPAddressDeny=any
 WatchdogSec=3min
==

I need to double-check, but I suspect that the SystemCallFilterAddition
might be causing problems.

Vince, can you please make a backup copy of /lib/systemd/system/systemd-
udevd.service, then remove the two SystemCallFilter and
SystemCallErrorNumber lines, reboot and see if the errors are gone?

If they are, then please restore the original file, and try adding
"@process" to the SystemCallFilter list; then reboot and see if it
helped. Or you can have a look at the possible values here [2] and try
understanding which ones are necessary. Though if you don't have time,
don't worry too much with this: it's something that we should be able to
determine ourselves.

[1]: https://www.freedesktop.org/software/systemd/man/udev.html
[2]: 
https://www.freedesktop.org/software/systemd/man/systemd.exec.html#SystemCallFilter=

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968878] Re: systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper add ... /class/video4linux 0:0' failed with exit code 1.

2022-05-23 Thread Alberto Mardegan
Hi Paul and Laurent, thanks for your bug report. Can you please check
what happens when you manually run tha same commands that you see as
failed?

For example, from Laurent's log:

sudo /usr/lib/snapd/snap-device-helper add snap_brave_brave
/class/video4linux 0:0 && echo ok

Also, if you don't mind, please attach the syslog when such error occurs
(by the way, do they happen at every boot, or irregularly?)

sudo journalctl -b

I suspect that this and bug 1971955 might be related.

** Changed in: snapd (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper
  add ... /class/video4linux 0:0' failed with exit code 1.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871148] Re: services start before apparmor profiles are loaded

2022-05-23 Thread Alberto Mardegan
Thanks Etienne, this is a bit surprising! Do I understand correctly,
that on the slower machine (where you are seeing this bug) you will not
be able to start firefox until you have run that apparmor_parser
command? Not even if you try starting firefox well after the login?

It's strange, because your logs show that the apparmor.service unit was
started can you please also attach the output of these commands:

sudo systemctl status apparmor
sudo journalctl -b _SYSTEMD_UNIT=apparmor.service + SYSLOG_IDENTIFIER=audit

And then also this (make sure you haven't previously started firefox in
this boot):

SNAPD_DEBUG=1 firefox

And after that, let's have a look at the full system log (I have no
clear idea what to look for, actually, but maybe I'll spot something
suspicious):

sudo journalctl -b

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

Title:
  services start before apparmor profiles are loaded

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-20 Thread Alberto Mardegan
Mmm... I'm running out of ideas! Mayve it's something with the
environment?

Vincent, can you try changing the rule to

RUN+="/bin/bash -c 'set > /tmp/set.log'"

and attach set.log here?

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

2022-05-20 Thread Alberto Mardegan
Hi Jeffrey and Erik!
  You are being heard :-) But this is not an easy task, and the amount of work 
required to support the case of home directories nested somewhere deeper inside 
/home is very different (read: lower) than that required to support home 
directories located elsewhere in the system.

We are first tackling the first problem, and this bug will be closed
once that part is fixed. The bug that best describe your use-case is
https://bugs.launchpad.net/snappy/+bug/1620771, so I recommend you to
subscribe to that one.

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973300] Re: NVIDIA CVE-2022-{28181|28183|28184|28185|28191|28192}

2022-05-17 Thread Alberto Milone
** Information type changed from Private Security to Public Security

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

Title:
  NVIDIA CVE-2022-{28181|28183|28184|28185|28191|28192}

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

2022-05-16 Thread Alberto Mardegan
** Changed in: snapd
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: snapd
   Status: Confirmed => In Progress

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-05-16 Thread Alberto Mardegan
Hi Erik, I see now what's the problem (this is specific to your setup --
this probably does not concern other people who commented here): your
home directories are under /staff, whereas currently snaps only support
the traditional /home// scheme.

Please subscribe to https://bugs.launchpad.net/snapd/+bug/1776800, we
are working on it :-)

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

Title:
  snapd is not autofs aware and fails with nfs home dir

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-16 Thread Alberto Mardegan
Vincent, maybe the udev rules are running under a user lacking some
privileges?

Can you please try changing the rule to

RUN+="/bin/bash -c 'id > /tmp/id.log'"

and then paste here the output of id.log? (hopefully I didn't mess up
the quoting in the command :-) )

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-05-16 Thread Alberto Mardegan
Thanks Erik and Andrew for the logs!

It looks like we have more than one bug here:

1) Andrew's logs show that after restarting the snapd service, NFS was
correctly detected and there are no more AppArmor denials on that. But
on Erik's machine, for some reason, that did not happen.

2) Even if the network rules are added, snaps still fail to start; I
believe that the root cause is the same as in
https://bugs.launchpad.net/bugs/1973321 (despite the fact that that bug
is about sshfs)

I will continue investigating the first issue here. Whereas, for the
second one, Andrew, can you please check if snaps start once you "cd" to
another directory, like "/snap"?

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

Title:
  snapd is not autofs aware and fails with nfs home dir

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871148] Re: services start before apparmor profiles are loaded

2022-05-16 Thread Alberto Mardegan
Hi Etienne, can you be a bit more explicit about what is the issue that
you are seeing? What are the services which are not starting?

Also please attach the SVG file generated by "sudo systemd-analyze
plot", it might help us.

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

Title:
  services start before apparmor profiles are loaded

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-05-13 Thread Alberto Mardegan
I believe that this is a duplicate of bug 1884299.

A few questions to people affected by this bug:

1) are you using autofs?

2) can you please try running "sudo systemctl restart snapd" after
logging in into your $HOME, and then try running a snap again?

3) If that still fails, can you paste the journal logs here (from the
time that snapd was restarted)?

** Changed in: snapd (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  snapd is not autofs aware and fails with nfs home dir

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-13 Thread Alberto Mardegan
Hi Vincent, if I understand it correctly, this command scans the
inserted media for snapd assertions and imports them.

It's still not clear to me what's happening: even if you are running on
a classic system, the "auto-import is disabled on classic" is just a
notification and not an error: the program still exits with a 0 exist
status. Yet, in the logs you provided, it appears as if the exist status
is 1. Could it be that the error is not coming from "snap auto-import",
but rather from the "unshare" command?

Can you please try to manually edit the file (after making a copy of
it!) and change the RUN line into

RUN+="/usr/bin/unshare -m /bin/echo hello"

and see if you still get those errors in the log?

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"

2022-05-12 Thread Alberto Mardegan
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [SRU] Please support group manipulation with "extrausers"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"

2022-05-12 Thread Alberto Mardegan
Hi Brian,
  I finally tested the new packages on Ubuntu Core 18 (with the bionic 
packages) and Ubuntu Core 20 (with the focal ones). I first tried to reproduce 
the issue in Ubuntu Desktop, by making /etc/groups and /etc/passwd read-only 
and indeed I couldn't add my user to a group, but unfortunately then I couldn't 
get the extrausers database setup correctly, so I gave up and just ran a quick 
smoke test to verify that the new binaries work as expected and instead focused 
on Ubuntu Core, that's where we initially had the issue.

The only problem is that I didn't test the entire deb packages, since
the root FS in UC is read-only and not debian-based, but I just extrated
the binaries from the passwd deb package and bind-mounted them over the
original UC ones. Then I was able to add my user to a group, without
needing to specify the --extrausers parameter.

I hope that this is good enough as a verification.


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

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

Title:
  [SRU] Please support group manipulation with "extrausers"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967721] Re: Laptop never resuming from standby

2022-05-11 Thread Alberto Donato
I've also tested more recent versions than 5.15 from the mainline PPA
(5.16 and 5.17), they all fail to resume.

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

Title:
  Laptop never resuming from standby

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967721] Re: Laptop never resuming from standby

2022-05-11 Thread Alberto Donato
On my laptop
 5.13 -> always suspends/resume correctly (battery and power)
 5.15 -> always fails to resume (battery and power)

fwupdate doesn't report any update available.

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

Title:
  Laptop never resuming from standby

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662552] Re: snaps don't work with NFS home

2022-05-11 Thread Alberto Mardegan
We did some progress in investigating this, and it appears that a
problem still exists: if the system is using autofs and snapd is started
before any NFS home directory is mounted, snapd will fail to detect the
fact that the system is using autofs (or NFS), and will not grant snap-
confine those permissions needed to use the network.

Given that this bug is old and that indeed a (partial) fix landed, I
suggest to keep it closed; I noticed that someone else filed a new bug
which explicitly mentions the autofs case, so I suggest continuing the
discussion there:

https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1884299

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

Title:
  snaps don't work with NFS home

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884299] Re: Chromium snap won't run with nfs home drive

2022-05-11 Thread Alberto Mardegan
A similar issue was discussed in the forums:

https://forum.snapcraft.io/t/cannot-open-path-of-the-current-working-
directory-permission-denied-bis/28704

If the system is using autofs and snapd is started before any NFS home
directory is mounted, snapd will fail to detect the fact that the system
is using autofs (or NFS), and will not grant snap-confine those
permissions needed to use the network.

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

Title:
  Chromium snap won't run with nfs home drive

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-11 Thread Alberto Mardegan
Hi Vincent, thanks for reporting this. There should be some message
printed by the "snap auto-import" command when it fails.

Can you please try to manually run (as root) the command

/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239

and paste here the output?

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

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

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971479] Re: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)

2022-05-10 Thread Alberto Milone
As per the attachment, I can't really reproduce the problem in my bionic
chroot using the 390 driver from the archive, and Linux 4.15.0-178.187
from the CKT PPA.

** Attachment added: "390-non-failure.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+attachment/5588191/+files/390-non-failure.txt

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

Title:
  ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1949075] Re: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 22.04

2022-05-10 Thread Alberto Donato
** Summary changed:

- [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on 
power-on on 21.10
+ [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on 
power-on on 22.04

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

Title:
  [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not
  autoconnecting on power-on on 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967727] Re: [Lenovo ThinkPad X260] Random screen blanks with "CPU pipe B FIFO underrun" error

2022-05-09 Thread Alberto Donato
Daniel,

yes I'm using an external monitor via DP. This is the same setup I've
been using for a long time with no issue. I've reverted to the Impish
kernel (mainly because of an other kernel issue preventing
suspend/resume) and that makes the issue disappear.

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

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

Title:
  [Lenovo ThinkPad X260] Random screen blanks with "CPU pipe B FIFO
  underrun" error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897454] Re: [snap] Chromium has Wayland support disabled

2022-05-06 Thread Luis Alberto Pabón
It feels pretty sluggish to use. Not sure if it's a packaging issue or
chromium issue.

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

Title:
  [snap] Chromium has Wayland support disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897454] Re: [snap] Chromium has Wayland support disabled

2022-05-06 Thread Luis Alberto Pabón
It works for me on 102.0.5005.40 (latest/beta channel) but with the
following GPU error messages:

```
[2005781:2005781:0506/130903.210912:ERROR:gpu_init.cc(481)] Passthrough is not 
supported, GL is egl, ANGLE is 
WARNING: Kernel has no file descriptor comparison support: Operation not 
permitted
[2005575:2005810:0506/130906.160463:ERROR:udev_watcher.cc(98)] Failed to begin 
udev enumeration.
```

And thousands of

```
[2008866:20:0506/131316.160676:ERROR:client_native_pixmap_dmabuf.cc(227)] 
Failed to mmap dmabuf: Permission denied (13)
```

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

Title:
  [snap] Chromium has Wayland support disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970451] Re: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy

2022-05-05 Thread Alberto Milone
** Changed in: linux-restricted-modules (Ubuntu Bionic)
 Assignee: (unassigned) => Ian May (ian-may)

** Changed in: linux-restricted-modules (Ubuntu Focal)
 Assignee: (unassigned) => Ian May (ian-may)

** Changed in: linux-restricted-modules (Ubuntu Impish)
 Assignee: (unassigned) => Ian May (ian-may)

** Changed in: linux-restricted-modules (Ubuntu Jammy)
 Assignee: (unassigned) => Ian May (ian-may)

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic)
 Assignee: (unassigned) => Ian May (ian-may)

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal)
 Assignee: (unassigned) => Ian May (ian-may)

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish)
 Assignee: (unassigned) => Ian May (ian-may)

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Jammy)
 Assignee: (unassigned) => Ian May (ian-may)

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

Title:
  Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal,
  Impish,  and Jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970265] Re: My Eevee and Vulpix cursors are not respected in almost all Snap programs, DMZ-White appears

2022-05-04 Thread Gustavo Alberto Peña Oliva
Here I have images that tell the truth about my Eevee and Vulpix cursors
in Snap Apps that DMZ-White appears instead

Using Firefox Snap for the sample

https://i.stack.imgur.com/dtoC0.jpg

https://i.stack.imgur.com/FiZTH.jpg

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

Title:
  My Eevee and Vulpix cursors are not respected in almost all Snap
  programs, DMZ-White appears

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971479] Re: ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)

2022-05-04 Thread Alberto Milone
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  ADT failure to apply buildfix on Bionic (390.147-0ubuntu0.18.04.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1971479/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969842] Re: No font available after installing in user space

2022-05-04 Thread Alberto Mardegan
Access to the "$HOME/.local/share/fonts/" is provided by the "desktop"
interface. The libreoffice snap should add this interface to its plugs,
and then fonts from this location should become usable.

I'm marking this bug as invalid for snapd (since it does not appear that
we need to do anything there about it), whereas the bug stays valid for
libreoffice.

** Changed in: snapd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No font available after installing in user space

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967721] Re: Laptop never resuming from standby

2022-05-01 Thread Alberto Donato
I tested by installing the kernel from impish (linux-
image-5.13.0-40-generic) on jammy, suspend works correctly with that
one.

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

Title:
  Laptop never resuming from standby

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970265] Re: My Eevee and Vulpix cursors are not respected in almost all Snap programs, DMZ-White appears

2022-04-29 Thread Gustavo Alberto Peña Oliva
** Also affects: snapcraft
   Importance: Undecided
   Status: New

** Also affects: snapcraft.io
   Importance: Undecided
   Status: New

** No longer affects: snapcraft.io

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

Title:
  My Eevee and Vulpix cursors are not respected in almost all Snap
  programs, DMZ-White appears

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970265] Re: My Eevee and Vulpix cursors are not respected in almost all Snap programs, DMZ-White appears

2022-04-28 Thread Gustavo Alberto Peña Oliva
** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: firefox (Ubuntu)

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

** No longer affects: snapcraft (Ubuntu)

** No longer affects: snapd (Ubuntu)

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

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

Title:
  My Eevee and Vulpix cursors are not respected in almost all Snap
  programs, DMZ-White appears

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970265] Re: My Eevee and Vulpix cursors are not respected in almost all Snap programs, DMZ-White appears

2022-04-27 Thread Gustavo Alberto Peña Oliva
Yep cursors are not provided in https://snapcraft.io/gtk-common-themes I
hope that one day the Snap problems with my cursors will be solved
especially when Ubuntu is just Snap and no more APT For now I will use
Flatpak since they respect my cursors until this conflict of my cursors
with Snap and DMZ-White is solved

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

Title:
  My Eevee and Vulpix cursors are not respected in almost all Snap
  programs, DMZ-White appears

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970265] Re: My Eevee and Vulpix cursors are not respected in almost all Snap programs, DMZ-White appears

2022-04-26 Thread Gustavo Alberto Peña Oliva
** Also affects: snapd
   Importance: Undecided
   Status: New

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

Title:
  My Eevee and Vulpix cursors are not respected in almost all Snap
  programs, DMZ-White appears

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970164] Re: add new device IDs in the support list of nvidia-driver-510 package

2022-04-26 Thread Alberto Milone
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  add new device IDs in the support list of nvidia-driver-510 package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970164/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970265] [NEW] My Eevee and Vulpix cursors are not respected in almost all Snap programs, DMZ-White appears

2022-04-25 Thread Gustavo Alberto Peña Oliva
Public bug reported:

I clarified this and made it clear in
https://askubuntu.com/questions/1373356/no-eevee-cursor-on-snap-programs
Almost all Snap programs (except Blender and Android Studio) don't
recognize my Eevee and Vulpix cursors instead DMZ-White appears and it
looks very ugly with my desktop themes

A month ago i discovered that my cursor packs were not in the
/usr/share/icons folders of most snap programs in the Snap folder try
adding it but discovered that it is read-only protected by SquashFS
making it impossible to add them to the icon folder

Link of my cursors in Pling
https://www.gnome-look.org/p/1660518

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


** Tags: cursors

** Tags added: cursors

** Description changed:

  I clarified this and made it clear in
  https://askubuntu.com/questions/1373356/no-eevee-cursor-on-snap-programs
  Almost all Snap programs (except Blender and Android Studio) don't
  recognize my Eevee and Vulpix cursors instead DMZ-White appears and it
- looks very ugly with my desktop themes A month ago
+ looks very ugly with my desktop themes A
  
- I discovered that my cursor packs were not in the /usr/share/icons folders of 
most snap programs in the Snap folder but it turns out that it is read-only 
protected by SquashFS
- and it is impossible to add my cursors to those folders that unfortunately is 
read only
+ month ago i discovered that my cursor packs were not in the
+ /usr/share/icons folders of most snap programs in the Snap folder try
+ adding it but discovered that it is read-only protected by SquashFS
+ making it impossible to add them to the icon folder
  
  
  Link of my cursors in Pling
  https://www.gnome-look.org/p/1660518

** Description changed:

  I clarified this and made it clear in
  https://askubuntu.com/questions/1373356/no-eevee-cursor-on-snap-programs
  Almost all Snap programs (except Blender and Android Studio) don't
  recognize my Eevee and Vulpix cursors instead DMZ-White appears and it
- looks very ugly with my desktop themes A
+ looks very ugly with my desktop themes
  
- month ago i discovered that my cursor packs were not in the
+ A month ago i discovered that my cursor packs were not in the
  /usr/share/icons folders of most snap programs in the Snap folder try
  adding it but discovered that it is read-only protected by SquashFS
  making it impossible to add them to the icon folder
  
- 
  Link of my cursors in Pling
  https://www.gnome-look.org/p/1660518

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

Title:
  My Eevee and Vulpix cursors are not respected in almost all Snap
  programs, DMZ-White appears

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897454] Re: [snap] Chromium has Wayland support disabled

2022-04-25 Thread Alberto Donato
This still fails with Chromium 100.0.4896.127 (snap 1967) on 22.04:

$ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[261783:261783:0425/123646.322058:ERROR:wayland_connection.cc(209)] Failed to 
connect to Wayland display
[261783:261783:0425/123646.322098:ERROR:ozone_platform_wayland.cc(226)] Failed 
to initialize Wayland platform
[261783:261783:0425/123646.322105:ERROR:env.cc(225)] The platform failed to 
initialize.  Exiting.

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

Title:
  [snap] Chromium has Wayland support disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969584] Re: Evolution does not allow editing email content on Wayland

2022-04-25 Thread Luis Alberto Pabón
I upgraded the following to 3.44.0-1ubuntu1 from jammy-proposed:

evolution evolution-common evolution-plugin-bogofilter evolution-plugin-
pstimport evolution-plugins libevolution

I can also confirm I can compose messages and replies.

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

Title:
  Evolution does not allow editing email content on Wayland

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967721] Re: Laptop never resuming from standby

2022-04-24 Thread Alberto Donato
Also, probably related, after the system has entered standby (the power
led pulsates slowly), the fan keeps running for a while. I've never seen
this behavior before with previous releases.

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

Title:
  Laptop never resuming from standby

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967721] Re: Laptop never resuming from standby

2022-04-24 Thread Alberto Donato
After force-rebooting the machine and looking at the previous boot dmesg
(journalctl -k -b -1) I noticed this:


Apr 03 23:10:55 arrakis kernel: wlp4s0: deauthenticating from 1e:e8:29:9b:9e:c5 
by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 03 23:10:56 arrakis kernel: PM: suspend entry (deep)
Apr 03 23:10:56 arrakis kernel: Filesystems sync: 0.289 seconds
Apr 03 23:11:16 arrakis kernel: Freezing user space processes ... 
Apr 03 23:11:16 arrakis kernel: Freezing of tasks failed after 20.009 seconds 
(1 tasks refusing to freeze, wq_busy=0):
Apr 03 23:11:16 arrakis kernel: task:systemd-detect- state:D stack:0 
pid:99860 ppid: 99853 flags:0x4224
Apr 03 23:11:16 arrakis kernel: Call Trace:
Apr 03 23:11:16 arrakis kernel:  
Apr 03 23:11:16 arrakis kernel:  __schedule+0x23d/0x590
Apr 03 23:11:16 arrakis kernel:  schedule+0x4e/0xb0
Apr 03 23:11:16 arrakis kernel:  request_wait_answer+0xa6/0x210
Apr 03 23:11:16 arrakis kernel:  ? wait_woken+0x70/0x70
Apr 03 23:11:16 arrakis kernel:  fuse_simple_request+0x1b1/0x360
Apr 03 23:11:16 arrakis kernel:  fuse_readlink_page+0xa4/0x130
Apr 03 23:11:16 arrakis kernel:  fuse_get_link+0x6d/0xd0
Apr 03 23:11:16 arrakis kernel:  pick_link+0x366/0x3f0
Apr 03 23:11:16 arrakis kernel:  ? fuse_symlink_readpage+0x40/0x40
Apr 03 23:11:16 arrakis kernel:  step_into+0x246/0x3b0
Apr 03 23:11:16 arrakis kernel:  walk_component+0x70/0x1b0
Apr 03 23:11:16 arrakis kernel:  link_path_walk.part.0.constprop.0+0x23b/0x360
Apr 03 23:11:16 arrakis kernel:  ? path_init+0x2bc/0x3e0
Apr 03 23:11:16 arrakis kernel:  path_openat+0xb5/0x2b0
Apr 03 23:11:16 arrakis kernel:  do_filp_open+0xb2/0x150
Apr 03 23:11:16 arrakis kernel:  ? __check_object_size+0x19/0x20
Apr 03 23:11:16 arrakis kernel:  ? alloc_fd+0x53/0x170
Apr 03 23:11:16 arrakis kernel:  do_sys_openat2+0x9b/0x160
Apr 03 23:11:16 arrakis kernel:  __x64_sys_openat+0x55/0x90
Apr 03 23:11:16 arrakis kernel:  do_syscall_64+0x5c/0xc0
Apr 03 23:11:16 arrakis kernel:  ? exit_to_user_mode_prepare+0x92/0xb0
Apr 03 23:11:16 arrakis kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
Apr 03 23:11:16 arrakis kernel:  ? irqentry_exit+0x19/0x30
Apr 03 23:11:16 arrakis kernel:  ? sysvec_reschedule_ipi+0x78/0xe0
Apr 03 23:11:16 arrakis kernel:  ? asm_sysvec_reschedule_ipi+0xa/0x20
Apr 03 23:11:16 arrakis kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Apr 03 23:11:16 arrakis kernel: RIP: 0033:0x7ffa48243f58
Apr 03 23:11:16 arrakis kernel: RSP: 002b:7ffcf6a80468 EFLAGS: 0287 
ORIG_RAX: 0101
Apr 03 23:11:16 arrakis kernel: RAX: ffda RBX: 7ffcf6a806cf 
RCX: 7ffa48243f58
Apr 03 23:11:16 arrakis kernel: RDX: 0008 RSI: 7ffcf6a804d0 
RDI: ff9c
Apr 03 23:11:16 arrakis kernel: RBP: 7ffcf6a804c0 R08: 0008 
R09: 7ffcf6a804d0
Apr 03 23:11:16 arrakis kernel: R10:  R11: 0287 
R12: 7ffa48254190
Apr 03 23:11:16 arrakis kernel: R13: 7ffcf6a804d0 R14: 7ffcf6a806e0 
R15: 7ffcf6a804d0
Apr 03 23:11:16 arrakis kernel:  
Apr 03 23:11:16 arrakis kernel: 
Apr 03 23:11:16 arrakis kernel: OOM killer enabled.
Apr 03 23:11:16 arrakis kernel: Restarting tasks ... done.
Apr 03 23:11:16 arrakis kernel: thermal thermal_zone2: failed to read out 
thermal zone (-61)
Apr 03 23:11:17 arrakis kernel: PM: suspend exit
Apr 03 23:11:17 arrakis kernel: PM: suspend entry (s2idle)
Apr 03 23:19:44 arrakis kernel: Filesystems sync: 0.198 seconds
Apr 03 23:19:44 arrakis kernel: Freezing user space processes ... (elapsed 
0.049 seconds) done.
Apr 03 23:19:44 arrakis kernel: OOM killer disabled.
Apr 03 23:19:44 arrakis kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
Apr 03 23:19:44 arrakis kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
Apr 03 23:19:44 arrakis kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Apr 03 23:19:44 arrakis kernel: sd 1:0:0:0: [sda] Stopping disk
Apr 03 23:19:44 arrakis kernel: e1000e: EEE TX LPI TIMER: 0011
Apr 03 23:19:44 arrakis kernel: ACPI: EC: interrupt blocked
Apr 03 23:19:44 arrakis kernel: ACPI: EC: interrupt unblocked
Apr 03 23:19:44 arrakis kernel: pcieport :00:1c.0: Intel SPT PCH root port 
ACS workaround enabled
Apr 03 23:19:44 arrakis kernel: pcieport :00:1c.2: Intel SPT PCH root port 
ACS workaround enabled
Apr 03 23:19:44 arrakis kernel: sd 1:0:0:0: [sda] Starting disk
Apr 03 23:19:44 arrakis kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 
SControl 300)
Apr 03 23:19:44 arrakis kernel: ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
FEATURES) succeeded
Apr 03 23:19:44 arrakis kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:a0 
(SECURITY FREEZE LOCK) filtered out
Apr 03 23:19:44 arrakis kernel: ata2.00: ACPI cmd ef/10:09:00:00:00:a0 (SET 
FEATURES) succeeded
Apr 03 23:19:44 arrakis kernel: ata2.00: supports DRM functions and may not be 
fully accessible
Apr 03 23:19:44 arrakis kernel: ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
FEATURES) succeeded
Apr 03 23:19:44 arrakis 

[Bug 1969529] Re: snapd slow to seed firefox on Pi 400

2022-04-22 Thread Alberto Mardegan
Hi Dave, I did not see any I/O errors from the kernel, but in your first
boot log
(https://errors.ubuntu.com/oops/fa9433d0-c022-11ec-8ae0-fa163e993415)
there are plenty of errors which might be related to missing files:

===
Apr 19 21:46:38 localhost.localdomain pulseaudio[841]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="platform-fef05700.hdmi" 
card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
avoid_resampling=no card_properties="module-udev-detect.discovered=1""): 
initialization failed.
...
Apr 19 21:46:42 localhost.localdomain udisksd[985]: failed to load module 
mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or 
directory
...
Apr 19 21:53:20 miss-piggy pipewire-media-session[840]: ms.core: error id:0 
seq:701 res:-32 (Broken pipe): connection error
Apr 19 21:53:21 miss-piggy accounts-daemon[934]: failed to check if user 'oem' 
in cache dir is present on system: No such file or directory
Apr 19 21:53:21 miss-piggy tracker-miner-f[970]: Could not delete 
'.meta.isrunning': No such file or directory
...
Apr 19 21:53:31 miss-piggy pulseaudio[34513]: Failed to open cookie file 
'/var/lib/gdm3/.config/pulse/cookie': No such file or directory
===

plus plenty of driver initialization errors; but on the other hand, it
may be that all of that is normal -- I just wanted to make sure that we
don't have to deal with a corrupted image.

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

Title:
  snapd slow to seed firefox on Pi 400

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings

2022-04-21 Thread Alberto Milone
** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

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

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

Title:
  software-properties-gtk crashed with TypeError in
  on_driver_selection_changed(): Expected a string or a pair of strings

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969529] Re: snapd failing to seed firefox on Pi 400

2022-04-20 Thread Alberto Mardegan
Hello again, Dave! Looking at the logs, it doesn't seem that your
problem is related to bug 1969162.

What I'm left to suspect is a storage issue, since there are many errors about 
files failing to load in the logs. I've had similar issues with a RPi3, where I 
had to flash the same Ubuntu image over the SD card a couple of times before 
the boot succeeded. Would you mind trying the same?
That is, just reflash the image a couple of times, and only afterwards you try 
booting.

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

Title:
  snapd failing to seed firefox on Pi 400

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >