[Touch-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-shell - 40.2-1ubuntu6

---
gnome-shell (40.2-1ubuntu6) impish; urgency=medium

  * d/rules:
- Drop dh_translations workaround. gettext used by LP has been
  updated (LP: #1756547).
- Fix Lintian warning about DEB_HOST_ARCH assignment

gnome-shell (40.2-1ubuntu5) impish; urgency=medium

  * Fix translation issues (LP: #1941954):
- Really fix translation import problem as reported in LP: #1756547
- Add libgtk-3-bin to Build-Depends for dh_translations

gnome-shell (40.2-1ubuntu4) impish; urgency=medium

  * debian/rules:
- Skip tests when building for ppc64el to fix FTBFS (LP: #1941792)

gnome-shell (40.2-1ubuntu3) impish; urgency=medium

  [ Daniel van Vugt ]
  * Add layout-Make-starting-in-the-overview-optional.patch:
- So that extensions like Ubuntu Dock have the option of preventing
  the shell starting in the overview. (LP: #1940925)

gnome-shell (40.2-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * Add workspace-Remove-skip-taskbar-windows-while-the-over.patch to stop the
desktop icons window appearing like an app window in the overview on
startup (LP: #1936643)

 -- Gunnar Hjalmarsson   Wed, 01 Sep 2021 15:44:38
+0200

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in gettext package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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


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


[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package protobuf - 3.12.4-1ubuntu3

---
protobuf (3.12.4-1ubuntu3) impish; urgency=medium

  * No-change rebuild to build with gcc-11 (LP: #1939413)

 -- Gunnar Hjalmarsson   Thu, 12 Aug 2021 12:38:56
+0200

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

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

Title:
  /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version
  9.2 instead of the expected 11.0

Status in mozc package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

Bug description:
  When trying to build package mozc for arm64 the following error popped
  up:

  lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux-
  gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the
  expected 11.0

  Why does the library contain LTO information at all?

  Best regards

  Heinrich

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


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


[Touch-packages] [Bug 1940070] Re: fpc: FTBFS with glibc 2.34

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package fpc - 3.2.2+dfsg-1ubuntu2

---
fpc (3.2.2+dfsg-1ubuntu2) impish; urgency=medium

  * Adjust startup code for glibc 2.34 (LP: #1940070)

 -- Graham Inggs   Fri, 20 Aug 2021 12:07:31 +

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

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

Title:
  fpc: FTBFS with glibc 2.34

Status in binutils package in Ubuntu:
  Invalid
Status in fpc package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Invalid

Bug description:
  fpc FTBFS with glibc 2.34

  
  See also:

  https://lists.freepascal.org/pipermail/fpc-
  devel/2021-August/043957.html

  https://gitlab.com/freepascal.org/fpc/source/-/issues/39295

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


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


[Touch-packages] [Bug 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package icu - 67.1-7ubuntu1

---
icu (67.1-7ubuntu1) impish; urgency=high

  * Merge from Debian unstable (LP: #1939728). Remaining changes:
- update-tz-tests.patch. This fixes a test failure caused by Ubuntu's
  tzdata bundling icu-data, while Debian's does not

icu (67.1-7) unstable; urgency=high

  * Backport upstream security fix for CVE-2021-30535: crash caused by locale
assign/move operators.

 -- William 'jawn-smith' Wilson   Thu, 12
Aug 2021 12:39:01 -0600

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30535

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

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  Fix Released

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

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


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


[Touch-packages] [Bug 1940634] Re: needs rebuild for GCC 11

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package xapian-core - 1.4.18-3build1

---
xapian-core (1.4.18-3build1) impish; urgency=medium

  * No-change rebuild against GCC 11 (LP: #1940634).

 -- Logan Rosen   Fri, 20 Aug 2021 23:56:14 -0400

** Changed in: xapian-core (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  needs rebuild for GCC 11

Status in xapian-core package in Ubuntu:
  Fix Released

Bug description:
  libxapian-dev needs to be rebuilt with GCC 11 in impish, otherwise it
  emits warnings when you try to compile other things with the now-
  default GCC 11 with it:

  ...
  [9/61] c++ -Itest/library.p -I/usr/include/x86_64-linux-gnu 
-I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Werror 
-std=c++11 -g -O2 
'-ffile-prefix-map=/<>/libkiwix-10.0.0+git202108071333.83e757a~impish=.'
 -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DGTEST_HAS_PTHREAD=1 
-pthread -MD -MQ test/library.p/library.cpp.o -MF 
test/library.p/library.cpp.o.d -o test/library.p/library.cpp.o -c 
../test/library.cpp
  [10/61] c++ -Isrc/libkiwix.so.10.0.0.p -Isrc -I../src -Iinclude -I../include 
-I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
-I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Werror 
-std=c++11 -g -O2 
'-ffile-prefix-map=/<>/libkiwix-10.0.0+git202108071333.83e757a~impish=.'
 -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libkiwix.so.10.0.0.p/library.cpp.o -MF 
src/libkiwix.so.10.0.0.p/library.cpp.o.d -o 
src/libkiwix.so.10.0.0.p/library.cpp.o -c ../src/library.cpp
  FAILED: src/libkiwix.so.10.0.0.p/library.cpp.o 
  c++ -Isrc/libkiwix.so.10.0.0.p -Isrc -I../src -Iinclude -I../include 
-I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
-I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Werror 
-std=c++11 -g -O2 
'-ffile-prefix-map=/<>/libkiwix-10.0.0+git202108071333.83e757a~impish=.'
 -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libkiwix.so.10.0.0.p/library.cpp.o -MF 
src/libkiwix.so.10.0.0.p/library.cpp.o.d -o 
src/libkiwix.so.10.0.0.p/library.cpp.o -c ../src/library.cpp
  In file included from /usr/include/xapian.h:44,
   from ../src/library.cpp:35:
  /usr/include/xapian/version.h:29:2: error: #warning The C++ ABI version of 
compiler you are using does not exactly match [-Werror=cpp]
 29 | #warning The C++ ABI version of compiler you are using does not 
exactly match
|  ^~~
  /usr/include/xapian/version.h:30:2: error: #warning that of the compiler used 
to build the library. If linking fails [-Werror=cpp]
 30 | #warning that of the compiler used to build the library. If linking 
fails
|  ^~~
  /usr/include/xapian/version.h:31:2: error: #warning due to missing symbols, 
this is probably the reason why. [-Werror=cpp]
 31 | #warning due to missing symbols, this is probably the reason why.
|  ^~~
  /usr/include/xapian/version.h:32:2: error: #warning The Xapian library was 
built with g++ 10.2.1 [-Werror=cpp]
 32 | #warning The Xapian library was built with g++ 10.2.1
|  ^~~
  cc1plus: all warnings being treated as errors
  [11/61] c++ -Isrc/libkiwix.so.10.0.0.p -Isrc -I../src -Iinclude -I../include 
-I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
-I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Werror 
-std=c++11 -g -O2 
'-ffile-prefix-map=/<>/libkiwix-10.0.0+git202108071333.83e757a~impish=.'
 -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libkiwix.so.10.0.0.p/downloader.cpp.o -MF 
src/libkiwix.so.10.0.0.p/downloader.cpp.o.d -o 
src/libkiwix.so.10.0.0.p/downloader.cpp.o -c ../src/downloader.cpp
  [12/61] c++ -Isrc/libkiwix.so.10.0.0.p -Isrc -I../src -Iinclude -I../include 
-I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu 
-I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Werror 
-std=c++11 -g -O2 
'-ffile-prefix-map=/<>/libkiwix-10.0.0+git202108071333.83e757a~impish=.'
 -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libkiwix.so.10.0.0.p/reader.cpp.o -MF 

[Touch-packages] [Bug 1939640] Re: libvpx FTBFS with LTO enabled

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package libvpx - 1.9.0-1ubuntu1

---
libvpx (1.9.0-1ubuntu1) impish; urgency=medium

  * d/rules: Disable LTO and fix FTBFS when building with GCC 11.
(LP: #1939640)

 -- Sergio Durigan Junior   Wed, 11 Aug
2021 22:25:45 -0400

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

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

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Fix Released
Status in lto-disabled-list package in Ubuntu:
  Fix Released

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

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


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


[Touch-packages] [Bug 1939544] Re: Merge the 1.1.1k version from Debian

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.1.1k-1ubuntu1

---
openssl (1.1.1k-1ubuntu1) impish; urgency=low

  * Merge from Debian unstable (LP: #1939544). Remaining changes:
- Replace duplicate files in the doc directory with symlinks.
- debian/libssl1.1.postinst:
  + Display a system restart required notification on libssl1.1
upgrade on servers, unless needrestart is available.
  + Use a different priority for libssl1.1/restart-services depending
on whether a desktop, or server dist-upgrade is being performed.
  + Skip services restart & reboot notification if needrestart is in-use.
  + Bump version check to to 1.1.1.
  + Import libraries/restart-without-asking template as used by above.
- Revert "Enable system default config to enforce TLS1.2 as a
  minimum" & "Increase default security level from 1 to 2".
- Reword the NEWS entry, as applicable on Ubuntu.
- Cherrypick s390x SIMD acceleration patches for poly1305 and chacha20
  and ECC from master.
- Use perl:native in the autopkgtest for installability on i386.
- Set OPENSSL_TLS_SECURITY_LEVEL=2 as compiled-in minimum security
  level. Change meaning of SECURITY_LEVEL=2 to prohibit TLS versions
  below 1.2 and update documentation. Previous default of 1, can be set
  by calling SSL_CTX_set_security_level(), SSL_set_security_level() or
  using ':@SECLEVEL=1' CipherString value in openssl.cfg.
- Import https://github.com/openssl/openssl/pull/12272.patch to enable
  CET.
- Add support for building with noudeb build profile.
  * Dropped changes, superseded upstream:
- SECURITY UPDATE: NULL pointer deref in signature_algorithms processing
  -> CVE-2021-3449
- SECURITY UPDATE: CA cert check bypass with X509_V_FLAG_X509_STRICT
  -> CVE-2021-3450

openssl (1.1.1k-1) unstable; urgency=medium

  * New upstream version.
- CVE-2021-3450 (CA certificate check bypass with X509_V_FLAG_X509_STRICT).
- CVE-2021-3449 (NULL pointer deref in signature_algorithms processing).

 -- Simon Chopin   Wed, 11 Aug 2021 13:00:48
+0200

** Changed in: openssl (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3449

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3450

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

Title:
  Merge the 1.1.1k version from Debian

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Impish currently ships with a version based on the upstream 1.1.1j,
  while Debian bullseye/sid has 1.1.1k. Let's merge!

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


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


[Touch-packages] [Bug 1940712] Re: binutils-common contains several zero-byte manpages

2021-09-03 Thread Launchpad Bug Tracker
This bug was fixed in the package binutils - 2.37-5ubuntu1

---
binutils (2.37-5ubuntu1) impish; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.37-5) unstable; urgency=medium

  * Update from the binutils 2.37 branch:
- [GOLD] PowerPC64 relocation overflow for -Os register save/restore funcs.
  * Update libctf0 and libctf-nobsd0 symbols files.
  * Rebuild man pages, included as empty files in the upstream tarball.
Closes: #992323. LP: #1940712.

binutils (2.37-4) unstable; urgency=medium

  * Update from the binutils 2.37 branch:
- Revert the ld script expression parsing changes.

 -- Matthias Klose   Mon, 30 Aug 2021 10:59:38 +0200

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

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

Title:
  binutils-common contains several zero-byte manpages

Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  binutils-common 2.37-1ubuntu1 contains several zero-byte manpages
  (those showing up with 20 bytes when packed with gzip):

  $ dpkg-query -L binutils-common | grep /usr/share/man/man1/ | xargs ls -Sl
  -rw-r--r-- 1 root root 6707 Jul 19 08:20 /usr/share/man/man1/ld.gold.1.gz
  -rw-r--r-- 1 root root  622 Jul 19 08:20 /usr/share/man/man1/dwp.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/addr2line.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/ar.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/as.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/c++filt.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/elfedit.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/gprof.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/ld.bfd.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/nm.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/objcopy.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/objdump.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/ranlib.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/readelf.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/size.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/strings.1.gz
  -rw-r--r-- 1 root root   20 Jul 19 08:20 /usr/share/man/man1/strip.1.gz
  lrwxrwxrwx 1 root root   12 Jul 19 08:20 /usr/share/man/man1/gold.1.gz -> 
ld.gold.1.gz
  lrwxrwxrwx 1 root root   11 Jul 19 08:20 /usr/share/man/man1/ld.1.gz -> 
ld.bfd.1.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: binutils-common 2.37-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Aug 20 21:15:08 2021
  Dependencies:
   
  InstallationDate: Installed on 2016-11-26 (1728 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  RebootRequiredPkgs:
   linux-image-5.13.0-14-generic
   linux-base
  SourcePackage: binutils
  UpgradeStatus: Upgraded to impish on 2021-08-08 (12 days ago)

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


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


[Touch-packages] [Bug 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf

2021-09-03 Thread Brian Murray
** Tags added: rls-ii-incoming

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

Title:
  systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on
  armhf

Status in glibc package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on
  armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd-
  test.py) and netplan.io (test-name=ethernets) tests on armhf.

  Reproducer:
  * Setup an armhf container, e.g. via:
  autopkgtest systemd --test-name=networkd-test.py --shell -U 
--apt-pocket=proposed=src:systemd,src:glibc -s -- lxd 
autopkgtest/ubuntu/impish/armhf
  * It will fail and drop you into the shell
  * cd test/ && apt install python3-nose
  * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py

  
  This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would 
fail on all architectures, not just armhf.

  It still passes inside an amd64 LXD container, so it is also not related to 
armhf being tested inside a container. But it shows the difference between 
armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and 
therefore DHCPREPLY) messages, as can be seen from the dnsmasq log:
  dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 
00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 
  dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 
00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf

  The issue is most probably the same that causes the currently failing
  netplan.io/ethernets autopkgtest on armhf, if tested against glibc
  2.34-0ubuntu1.

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


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


[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

2021-09-03 Thread Hayden Clark
Ok, did it.
That's freed up a load of space.
Where would I file the bug about having two sets of kernels?

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1942623] Re: [Wishlist] systemctl CLI UI should allow glob expansion throughout the service name

2021-09-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [Wishlist] systemctl CLI UI should allow glob expansion throughout the
  service name

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When attempting to craft a command to query and/or restart all
  services with name 'something-*-else', such as 'neutron-*-agent' to
  match [neutron-l3-agent, neutron-openvswitch-agent, and neutron-dhcp-
  agent], I've found that no services are returned from globs in the
  middle of the string.  The only supported glob seems to be a * at the
  end of the service name. Also, single character globbing with ? is not
  honored (as in the last example).

  To provide an example, I expect each of these commands to return the
  dbus.socket and dbus.service, but only 'systemctl status dbu*' shows
  the proper return.

  drew@grimoire:~$ systemctl status dbus
  ● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static)
   Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
  TriggeredBy: ● dbus.socket
 Docs: man:dbus-daemon(1)
 Main PID: 1357 (dbus-daemon)
Tasks: 1 (limit: 57290)
   Memory: 4.9M
   CGroup: /system.slice/dbus.service
   └─1357 @dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only

  Warning: some journal files were not opened due to insufficient permissions.
  drew@grimoire:~$ systemctl status *bus
  drew@grimoire:~$ systemctl status '*bus'
  drew@grimoire:~$ systemctl status 'dbu*'
  ● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static)
   Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
  TriggeredBy: ● dbus.socket
 Docs: man:dbus-daemon(1)
 Main PID: 1357 (dbus-daemon)
Tasks: 1 (limit: 57290)
   Memory: 5.0M
   CGroup: /system.slice/dbus.service
   └─1357 @dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only

  Warning: some journal files were not opened due to insufficient permissions.
  ● dbus.socket - D-Bus System Message Bus Socket
   Loaded: loaded (/lib/systemd/system/dbus.socket; static)
   Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
 Triggers: ● dbus.service
   Listen: /run/dbus/system_bus_socket (Stream)
  drew@grimoire:~$ systemctl status 'db*s'
  drew@grimoire:~$ systemctl status 'dbu?'

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


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


[Touch-packages] [Bug 1942623] [NEW] [Wishlist] systemctl CLI UI should allow glob expansion throughout the service name

2021-09-03 Thread Drew Freiberger
Public bug reported:

When attempting to craft a command to query and/or restart all services
with name 'something-*-else', such as 'neutron-*-agent' to match
[neutron-l3-agent, neutron-openvswitch-agent, and neutron-dhcp-agent],
I've found that no services are returned from globs in the middle of the
string.  The only supported glob seems to be a * at the end of the
service name. Also, single character globbing with ? is not honored (as
in the last example).

To provide an example, I expect each of these commands to return the
dbus.socket and dbus.service, but only 'systemctl status dbu*' shows the
proper return.

drew@grimoire:~$ systemctl status dbus
● dbus.service - D-Bus System Message Bus
 Loaded: loaded (/lib/systemd/system/dbus.service; static)
 Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
TriggeredBy: ● dbus.socket
   Docs: man:dbus-daemon(1)
   Main PID: 1357 (dbus-daemon)
  Tasks: 1 (limit: 57290)
 Memory: 4.9M
 CGroup: /system.slice/dbus.service
 └─1357 @dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only

Warning: some journal files were not opened due to insufficient permissions.
drew@grimoire:~$ systemctl status *bus
drew@grimoire:~$ systemctl status '*bus'
drew@grimoire:~$ systemctl status 'dbu*'
● dbus.service - D-Bus System Message Bus
 Loaded: loaded (/lib/systemd/system/dbus.service; static)
 Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
TriggeredBy: ● dbus.socket
   Docs: man:dbus-daemon(1)
   Main PID: 1357 (dbus-daemon)
  Tasks: 1 (limit: 57290)
 Memory: 5.0M
 CGroup: /system.slice/dbus.service
 └─1357 @dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only

Warning: some journal files were not opened due to insufficient permissions.
● dbus.socket - D-Bus System Message Bus Socket
 Loaded: loaded (/lib/systemd/system/dbus.socket; static)
 Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
   Triggers: ● dbus.service
 Listen: /run/dbus/system_bus_socket (Stream)
drew@grimoire:~$ systemctl status 'db*s'
drew@grimoire:~$ systemctl status 'dbu?'

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

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

Title:
  [Wishlist] systemctl CLI UI should allow glob expansion throughout the
  service name

Status in systemd package in Ubuntu:
  New

Bug description:
  When attempting to craft a command to query and/or restart all
  services with name 'something-*-else', such as 'neutron-*-agent' to
  match [neutron-l3-agent, neutron-openvswitch-agent, and neutron-dhcp-
  agent], I've found that no services are returned from globs in the
  middle of the string.  The only supported glob seems to be a * at the
  end of the service name. Also, single character globbing with ? is not
  honored (as in the last example).

  To provide an example, I expect each of these commands to return the
  dbus.socket and dbus.service, but only 'systemctl status dbu*' shows
  the proper return.

  drew@grimoire:~$ systemctl status dbus
  ● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static)
   Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
  TriggeredBy: ● dbus.socket
 Docs: man:dbus-daemon(1)
 Main PID: 1357 (dbus-daemon)
Tasks: 1 (limit: 57290)
   Memory: 4.9M
   CGroup: /system.slice/dbus.service
   └─1357 @dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only

  Warning: some journal files were not opened due to insufficient permissions.
  drew@grimoire:~$ systemctl status *bus
  drew@grimoire:~$ systemctl status '*bus'
  drew@grimoire:~$ systemctl status 'dbu*'
  ● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static)
   Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
  TriggeredBy: ● dbus.socket
 Docs: man:dbus-daemon(1)
 Main PID: 1357 (dbus-daemon)
Tasks: 1 (limit: 57290)
   Memory: 5.0M
   CGroup: /system.slice/dbus.service
   └─1357 @dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only

  Warning: some journal files were not opened due to insufficient permissions.
  ● dbus.socket - D-Bus System Message Bus Socket
   Loaded: loaded (/lib/systemd/system/dbus.socket; static)
   Active: active (running) since Mon 2021-08-30 23:41:27 CDT; 3 days ago
 Triggers: ● dbus.service
   Listen: /run/dbus/system_bus_socket (Stream)
  drew@grimoire:~$ systemctl status 'db*s'
  drew@grimoire:~$ systemctl status 'dbu?'

To manage notifications about this 

[Touch-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2021-09-03 Thread Colin Watson
Launchpad intentionally imports even obsolete messages, although they're
tagged internally as obsolete and filtered out for various purposes.  I
think this is so that they can be used as suggestions in some cases (for
example, a similar message might still be used in another context).  For
that sort of purpose it can still be useful to know that the messages
don't parse correctly, because they couldn't be used directly as
suggestions without fixing the mistakes.

This is likely part of some work that was never completed, e.g.
https://bugs.launchpad.net/launchpad/+bug/281165 and
https://blueprints.launchpad.net/launchpad/+spec/rosetta-fuzzy-merge.

(Note that I'm reverse-engineering this from the code and from my
general understanding of translations, rather than with direct
information from the people who wrote the code.)

I can see that it might be useful to at least exclude errors about
obsolete messages like this from translation import failure emails.  If
you agree, could you file a separate bug about that?

** Changed in: ubuntu-translations
   Status: Triaged => Fix Released

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

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in gettext package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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


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


[Touch-packages] [Bug 1942599] [NEW] KDE Volume not matching alsa volume in ALC294 (Asus Zenbook UM431D)

2021-09-03 Thread LukasThyWalls
Public bug reported:

Hello.

I posted  some weeks ago in pulseaudio bugtracker
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1249 about
an issue, but i was thinking it should be better have here the issue too
because maybe is related with other components in (K)Ubuntu system.

I will go to a copy paste, because it self explanatory:

---

* Context:

OS: KUbuntu 21.04 with kernel 5.14.0rc4 mainline.
Laptop: Asus Zenbook UMD431D with ALC294
pa-info: pa-info.txt (attached)

Also recently was fixed an issue with alsa about the 4 speakers volume
(two of them weren't affected by it
https://bugzilla.kernel.org/show_bug.cgi?id=212547) however, this
doesn't seems related to that. (That's why i use 5.14.0rc4, because 5.14
are the first with the patch).

* Issue behaviour and description

The main issue can be seen in the next video:
https://www.youtube.com/watch?v=eBrHi1f9bck

Summarizing, when you go up and down the KDE volume, if you compared the
desired volume in the slider with alsamixer doesn't match. But the issue
is when you reach below 9%, with that the Master volume in alsamixer is
0%, so there isn't any sound, and between 1%~8% it's changing the
"Speaker" slider, doing nothing. It's like the "Speaker" slider is
stacked below the "Master", but that doesn't make any sense in practice.

Changing the volume in the KDE volume slider is not "linear", between
50%~100% it's more or less and the volume "feels" right, but below that,
the volume goes down way faster. For example, having the volume at 25%,
the sound is almost noticiable unless you put you ears near the
speakers, something like this should be at 10%, but at the real 10% you
have a barely noticiable sound in the speakers when you have your ears
directly in them.

* Expected Results

The general volume slider should match the Master Volume in alsa, and
only change that slider.

Thanks!

---

Offtopic: Also i found doing testing for the kernel bug noted above,
that changing to some alsa model in this laptop, then appears in the
volume/audio configurator a selection of output and input what can
overrides the headphone plug status, and i see it very useful,
especially because if i plug a headphone without microphone i can't use
the laptop built-in microphone and the only thing i can do is not use
headphone. But using some models (dell-headset-multi, for example) i can
do that, however, it brings the issue with the volume in the back
speakers. How pulseaudio can be do this? it can be done for my laptop?

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

** Attachment added: "pa-info"
   
https://bugs.launchpad.net/bugs/1942599/+attachment/5522765/+files/pa-info.txt

** Description changed:

  Hello.
  
  I posted  some weeks ago in pulseaudio bugtracker
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1249 about
  an issue, but i was thinking it should be better have here the issue too
  because maybe is related with other components in (K)Ubuntu system.
  
  I will go to a copy paste, because it self explanatory:
  
  ---
  
  * Context:
  
  OS: KUbuntu 21.04 with kernel 5.14.0rc4 mainline.
  Laptop: Asus Zenbook UMD431D with ALC294
  pa-info: pa-info.txt (attached)
- Also recently was fixed an issue with alsa about the 4 speakers volume (two 
of them weren't affected by it 
https://bugzilla.kernel.org/show_bug.cgi?id=212547) however, this doesn't seems 
related to that. (That's why i use 5.14.0rc4, because 5.14 are the first with 
the patch).
+ 
+ Also recently was fixed an issue with alsa about the 4 speakers volume
+ (two of them weren't affected by it
+ https://bugzilla.kernel.org/show_bug.cgi?id=212547) however, this
+ doesn't seems related to that. (That's why i use 5.14.0rc4, because 5.14
+ are the first with the patch).
  
  * Issue behaviour and description
  
- The main issue can be seen in the next video: 
https://www.youtube.com/watch?v=eBrHi1f9bck
- Summarizing, when you go up and down the KDE volume, if you compared the 
desired volume in the slider with alsamixer doesn't match. But the issue is 
when you reach below 9%, with that the Master volume in alsamixer is 0%, so 
there isn't any sound, and between 1%~8% it's changing the "Speaker" slider, 
doing nothing. It's like the "Speaker" slider is stacked below the "Master", 
but that doesn't make any sense in practice.
- Changing the volume in the KDE volume slider is not "linear", between 
50%~100% it's more or less and the volume "feels" right, but below that, the 
volume goes down way faster. For example, having the volume at 25%, the sound 
is almost noticiable unless you put you ears near the speakers, something like 
this should be at 10%, but at the real 10% you have a barely noticiable sound 
in the speakers when you have your ears directly in them.
+ The main issue can be seen in the next video:
+ https://www.youtube.com/watch?v=eBrHi1f9bck
+ 
+ Summarizing, when you go up and down the KDE volume, if you compared 

[Touch-packages] [Bug 1942597] [NEW] I only have 640x480 resolution and cant use gdm3

2021-09-03 Thread Mohi
Public bug reported:

I believe there is something wrong with my graphic driver

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 
5.11.0-7633.35~1630100930~20.04~ae2753e~dev-generic 5.11.22
Uname: Linux 5.11.0-7633-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Fri Sep  3 14:47:31 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd G96C [GeForce 9500 GT] [1458:34a9]
InstallationDate: Installed on 2021-09-01 (1 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-7633-generic 
root=UUID=428abc01-2e2d-4a8f-bfae-e5c776022a84 ro nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2009
dmi.bios.release: 8.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0403
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL/EPU
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd06/17/2009:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuToBeFilledByO.E.M.:rvnASUSTeKComputerINC.:rnP5KPL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Fri Sep  3 14:25:47 2021
xserver.configfile: default
xserver.errors:
 [drm] Failed to open DRM device for pci::01:00.0: -19
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.11-1ubuntu1~20.04.2

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu

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

Title:
  I only have 640x480 resolution and cant use gdm3

Status in xorg package in Ubuntu:
  New

Bug description:
  I believe there is something wrong with my graphic driver

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.11.0-7633.35~1630100930~20.04~ae2753e~dev-generic 5.11.22
  Uname: Linux 5.11.0-7633-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Fri Sep  3 14:47:31 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G96C [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G96C [GeForce 9500 GT] [1458:34a9]
  InstallationDate: Installed on 2021-09-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-7633-generic 
root=UUID=428abc01-2e2d-4a8f-bfae-e5c776022a84 ro nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2009
  dmi.bios.release: 8.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL/EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1639408] Re: udev misidentifies usb headset as xbox gamepad from same manufacturer

2021-09-03 Thread Davernos
Having the same problem with PDPGaming LVL50 Wireless for XboxOne
(Dongle) on Ubuntu 20.04.3 LTS.

[776440.522405] usb 1-10: new full-speed USB device number 6 using xhci_hcd
[776440.672101] usb 1-10: New USB device found, idVendor=0e6f, idProduct=0234, 
bcdDevice= 0.02
[776440.672106] usb 1-10: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[776440.672109] usb 1-10: Product: PDPGaming LVL50 Wireless for XboxOne (Dongle)
[776440.672112] usb 1-10: Manufacturer: Performance Designed Products
[776440.672115] usb 1-10: SerialNumber: D1A4CAEC2C2A
[776440.721767] input: Generic X-Box pad as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/input/input20
[776440.721875] usbcore: registered new interface driver xpad

dongle is being recognized as a game controller.

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

Title:
  udev misidentifies usb headset as xbox gamepad from same manufacturer

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have a USB wireless Afterglow AG9+ Wireless headset that is being
  misidentifed as a generic xbox pad.

  This is actually a generic usb sound card

  [  931.178869] usb 5-5: new full-speed USB device number 3 using ohci-pci
  [  931.373967] usb 5-5: New USB device found, idVendor=0e6f, idProduct=0157
  [  931.373971] usb 5-5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  931.373975] usb 5-5: Product: Afterglow AG9+ Wireless HS for XboxOne 
(Dongle)
  [  931.373977] usb 5-5: Manufacturer: Performance Designed Products
  [  931.373979] usb 5-5: SerialNumber: 2D53FFD0FBE9
  [  931.376306] input: Generic X-Box pad as 
/devices/pci:00/:00:13.0/usb5/5-5/5-5:1.0/input/input18

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov  5 02:00:10 2016
  InstallationDate: Installed on 2016-11-05 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=e0481110-c70f-4b94-a8e8-a32cf885ffd1 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: 970 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd07/31/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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