[Touch-packages] [Bug 890916] Re: Login shell not sourcing /etc/profile and ${HOME}/.bashrc

[Bug Watch Updater]

** Changed in: bash (Debian)
   Status: Unknown => New

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

Title:
  Login shell not sourcing /etc/profile and ${HOME}/.bashrc

Status in bash package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  New

Bug description:
  bash does not source /etc/profile and ${HOME}/.bashrc for login
  shells, ignoring some settings done within these files. Additionally
  aliases are set while sourcing /etc/profile and ${HOME}/.bashrc
  overwriting each other. Aliases shall be read at one place only from
  one source if possible. Not from /etc/profile.d/aliases.sh, from
  within /etc/profile and from ${HOME}/.bashrc there is to much
  posibility you'll change aliases overwritten by other parts while
  executing login leading to different command behaviour later on. This
  can be something really bad: assume one awaiting "rm" aliased to "rm
  -i" kicking of "rm -r *" assuming this set because he/she is used to
  it from xterm, but it isn't set this way login in from somewhere else
  via ssh or ssh+screen and having again a different behaviour logging
  in with xterm+byobu or ssh+byobu enabled!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: bash 4.2-0ubuntu4
  Uname: Linux 3.0.9 x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 16 00:37:49 2011
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.bash.bashrc: 2011-10-19T21:08:11.823309

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/890916/+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 2021929] Re: upgrade to exiv2 0.28.0

[Bug Watch Updater]

** Changed in: exiv2 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  upgrade to exiv2 0.28.0

Status in exiv2 package in Ubuntu:
  Triaged
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  The latest release is 0.28.0 and fixes some bugs I've encountered

  https://github.com/Exiv2/exiv2/releases/tag/v0.28.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/2021929/+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 2083302] Re: lvm2 ftbfs against autoconf 2.72

[Bug Watch Updater]

** Changed in: lvm2 (Debian)
   Status: Unknown => New

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

Title:
  lvm2 ftbfs against autoconf 2.72

Status in lvm2 package in Ubuntu:
  New
Status in lvm2 package in Debian:
  New

Bug description:
  excerpt from the logs [1]
  -

  [GEN] command-count.h
  [GEN] command-lines-input.h
  gcc -E -P cmdnames.h 2> /dev/null | \
@EGREP@ -v '^ 
*(|#.*|config|devtypes|dumpconfig|formats|fullreport|help|lastlog|lvmchange|lvpoll|pvdata|segtypes|systemid|tags|version)
 *$' > .commands
  \
  ( cat ./license.inc && \
echo "/* Do not edit. This file is generated by the Makefile. */" && \
printf "static const char _command_input[] =\n\n\"" && \
mawk 'BEGIN {ORS = "\\n\"\n\""} !/^#/ && !/---/ && !/^$/' 
./command-lines.in && \
printf '\\n\\n";\n' \
  ) > command-lines-input.h
  \
  ( cat ./license.inc && \
echo "/* Do not edit. This file is generated by the Makefile. */" && \
printf "#define COMMAND_COUNT " && \
@GREP@ -c '^ID:' command-lines.in \
  ) > command-count.h
  /bin/bash: line 2: @EGREP@: command not found
  [LN] man-generator.c
  ln -s -f command.c man-generator.c
  /bin/bash: line 5: @GREP@: command not found
  make[3]: *** [Makefile:172: command-count.h] Error 127
  make[3]: *** Deleting file 'command-count.h'
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** [Makefile:166: .commands] Error 127
  make[3]: *** Deleting file '.commands'
  make[3]: Leaving directory '/<>/debian/build/build_deb/tools'


  excerpt from autoconf 2.72 release notes [2]
  

  *** All internal uses of AC_EGREP_CPP and AC_EGREP_HEADER have been removed.
These macros look for text matching a regular expression in the
output of the C preprocessor.  Their use has been discouraged for
many years, as they tend to be unreliable; it is better to find a
way to use AC_COMPILE_IFELSE or AC_PREPROC_IFELSE instead.  We have
finally taken our own advice.

This change might break configure scripts that expected probes for
‘grep’ and/or the C preprocessor to happen as a side effect of an
unrelated operation.  Such scripts can be fixed by adding
AC_PROG_EGREP and/or AC_PROG_CPP in an appropriate place.

The macros affected by this change are AC_C_STRINGIZE,
AC_C_VARARRAYS, AC_FUNC_GETGROUPS, AC_FUNC_GETLOADAVG,
AC_HEADER_TIOCGWINSZ, AC_PROG_GCC_TRADITIONAL, AC_TYPE_GETGROUPS,
AC_TYPE_UID_T, and AC_XENIX_DIR. Many of these macros are themselves
obsolete; if your configure script uses any of them, check whether
it is actually needed.

  analysis
  

  There is an upstream patch for lvm2:
  
https://gitlab.com/lvmteam/lvm2/-/commit/635df7486f2d6045c8fc085192b036d78b309907

  [1] 
https://launchpadlibrarian.net/749244995/buildlog_ubuntu-oracular-amd64.lvm2_2.03.22-1ubuntu1_BUILDING.txt.gz
  [2] 
https://lists.gnu.org/archive/html/autotools-announce/2023-12/msg3.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2083302/+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 2083158] Re: Sync python-testtools 2.7.2-2 (main) from Debian unstable (main) to fix FTBFS on oracular

[Bug Watch Updater]

** Changed in: python-testtools (Debian)
   Status: Unknown => Fix Released

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

Title:
  Sync python-testtools 2.7.2-2 (main) from Debian unstable (main) to
  fix FTBFS on oracular

Status in python-testtools package in Ubuntu:
  New
Status in python-testtools package in Debian:
  Fix Released

Bug description:
  Please sync python-testtools 2.7.2-2 (main) from Debian unstable
  (main)

  python-testtools 2.7.2-1 currently in oracular FTBFS because the
  build-time test-suite fails. This is addressed by Debian debbug
  1082697.

  Changelog entries since current oracular version 2.7.2-1:

  python-testtools (2.7.2-2) unstable; urgency=medium

    * Disable failing twisted tests (Closes: #1082697):
  - TestAsynchronousDeferredRunTest.test_log_in_details
  - TestAsynchronousDeferredRunTest.test_log_to_twisted

   -- Thomas Goirand   Wed, 25 Sep 2024 09:59:04 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/2083158/+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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)

[Bug Watch Updater]

** Changed in: sysvinit (Debian)
   Status: Incomplete => Fix Released

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

Title:
  Network is brought down before network filesystems are unmounted (CIFS
  timeout at shutdown)

Status in dbus package in Ubuntu:
  Fix Released
Status in dhcdbd package in Ubuntu:
  Invalid
Status in netbase package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Fix Released
Status in dhcdbd source package in Lucid:
  Invalid
Status in dhcdbd source package in Natty:
  Invalid
Status in sysvinit package in Debian:
  Fix Released

Bug description:
  IMPORTANT: this bug has enough information; please don't post
  _anything_ unless a developer asks for specific feedback! By posting
  to this bug you only make it harder for a developer to spot the gem
  comments. Please use the "me too feature" of launchpad to signal that
  you are affected and would like to see this fixed.

  I installed smbfs,and then put some entries into /etc/fstab, so they 
automount on startup. An example of this is here:
  ///  /home/hamish/  cifs  
credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
  0  0

  ** note the use of "cifs" in the lines above **

  (The username and password are in the .smbcredentials file)

  On startup, for each entry in the /etc/fstab file, I get the following in 
dmesg:
  [   70.495504]  CIFS VFS: Error connecting to IPv4 socket. Aborting operation
  [   70.495569]  CIFS VFS: cifs_mount failed w/return code = -101
  But the shares are mounted, and a nautilus session opens up (which is also 
annoying...)

  Also logging off with CIFS shares mounted in /etc/fstab, it sits with an 
error message:
  CIFS VFS: server not responding
  CIFS VFS: no response for cmd 50 mid 
  And takes about 2 minutes to timeout. This also happened with Gutsy

  Should the timing of the mounting and dismounting be changed so that
  it works? It is related to the starting of network-manager and CIFS
  shares trying to connect on startup *before* the network is up, and
  dismounting the shares *after* network-manager is stopped.

  Hamish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+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 2077892] Re: Two different values for /run/lock

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Unknown => Fix Released

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

Title:
  Two different values for /run/lock

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  There are conflicting values for /run/lock (1755 and 0755) in
  /usr/lib/tmpfiles.d

  Log line:

  systemd-tmpfiles[139060]: /usr/lib/tmpfiles.d/legacy.conf:13:
  Duplicate line for path "/run/lock", ignoring.

  
  /usr/lib/tmpfiles.d$ grep "d /run/lock " *
  debian.conf:d /run/lock1777 root root -   -
  legacy.conf:d /run/lock 0755 root root -

  ii  systemd256.4-2ubuntu1 amd64system and service
  manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2077892/+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 2081329] Re: kbd FTBFS on Oracular

[Bug Watch Updater]

** Changed in: kbd (Debian)
   Status: Confirmed => Fix Released

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

Title:
  kbd FTBFS on Oracular

Status in kbd package in Ubuntu:
  New
Status in kbd package in Debian:
  Fix Released

Bug description:
  This bug is used to track kbd FTBFS on Oracular

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2081329/+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 2081329] Re: kbd FTBFS on Oracular

[Bug Watch Updater]

** Changed in: kbd (Debian)
   Status: Unknown => Confirmed

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

Title:
  kbd FTBFS on Oracular

Status in kbd package in Ubuntu:
  New
Status in kbd package in Debian:
  Confirmed

Bug description:
  This bug is used to track kbd FTBFS on Oracular

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2081329/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)

[Bug Watch Updater]

** Changed in: gnome-online-accounts
   Status: New => Fix Released

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

Title:
  Nextcloud account added to Online Accounts does not populate Calendar
  apps (WebDAV file sharing does work)

Status in gnome-online-accounts:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  My Nextcloud server was working fine with previous versions of Ubuntu,
  but on the 20.04 daily when I add my Nextcloud account it does not
  populate my Calendars or todo lists. It does give me file access via
  WebDAV. Server is working fine as far as I'm aware. Going to Settings
  -> Administration - Overview shows me any configuration issues it can
  detect, currently the only error there is related to background job
  execution (which is only relevant to the News app if I'm not
  mistaken).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 23:59:55 2020
  InstallationDate: Installed on 2020-04-03 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+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 2081110] Re: FTBFS for oracular 2:4.35-1.1ubuntu1

[Bug Watch Updater]

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1904395.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-06-24T17:58:55+00:00 Jschanck wrote:

When building with clang-18, I get
```
../../../pr/tests/testfile.c:576:31: error: incompatible function pointer types 
passing 'PRInt32 (void *)' (aka 'int (void *)') to parameter of type 'void 
(*)(void *)' [-Wincompatible-function-pointer-types]
  576 |   DirTest, &thrarg,
  |   ^~~
../../../pr/tests/testfile.c:93:36: note: passing argument to parameter 'start' 
here
   93 | void (*start)(void *arg),
  |^
```

I took a crack at fixing it, but the test itself is in pretty rough
shape---I'm not sure it's useful, or even correct, as is.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2081110/comments/0


On 2024-07-03T21:14:57+00:00 Mh+mozilla wrote:

Same with GCC 14.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2081110/comments/1


On 2024-07-10T12:14:20+00:00 Release-mgmt-account-bot wrote:

The severity field is not set for this bug.
:KaiE, could you have a look please?

For more information, please visit [BugBot
documentation](https://wiki.mozilla.org/BugBot#workflow.2Fno_severity.py).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2081110/comments/2


On 2024-07-16T09:22:02+00:00 Kai Engert wrote:

Created attachment 9412960
Bug 1904395 - Fix incompatible native thread start type. r=jschanck

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2081110/comments/3


On 2024-07-16T09:22:37+00:00 Kai Engert wrote:

What do you think about my patch?
It tries to fix the pointer types.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2081110/comments/4


On 2024-07-25T10:25:17+00:00 Kai Engert wrote:

Created attachment 9414815
Bug 1904395 - Fix incompatible native thread start type. r=jschanck

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2081110/comments/5


On 2024-07-30T08:00:45+00:00 Kai Engert wrote:

https://hg.mozilla.org/projects/nspr/rev/e178d3d9b47b2479f22f208d6225eda81918dae1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/2081110/comments/6


** Changed in: nspr
   Status: Unknown => Fix Released

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

Title:
  FTBFS for oracular 2:4.35-1.1ubuntu1

Status in NSPR:
  Fix Released
Status in nspr package in Ubuntu:
  In Progress
Status in nspr package in Debian:
  Confirmed

Bug description:
  nspr currently fails to build in oracular with the following:

  testfile.c:126:41: error: passing argument 3 of ‘pthread_create’ from
  incompatible pointer type

  This should be fixed upstream with
  
https://hg.mozilla.org/projects/nspr/rev/e178d3d9b47b2479f22f208d6225eda81918dae1

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1904395
  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075322

To manage notifications about this bug go to:
https://bugs.launchpad.net/nspr/+bug/2081110/+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 2081110] Re: FTBFS for oracular 2:4.35-1.1ubuntu1

[Bug Watch Updater]

** Changed in: nspr (Debian)
   Status: Unknown => Confirmed

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

Title:
  FTBFS for oracular 2:4.35-1.1ubuntu1

Status in NSPR:
  Unknown
Status in nspr package in Ubuntu:
  In Progress
Status in nspr package in Debian:
  Confirmed

Bug description:
  nspr currently fails to build in oracular with the following:

  testfile.c:126:41: error: passing argument 3 of ‘pthread_create’ from
  incompatible pointer type

  This should be fixed upstream with
  
https://hg.mozilla.org/projects/nspr/rev/e178d3d9b47b2479f22f208d6225eda81918dae1

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1904395
  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075322

To manage notifications about this bug go to:
https://bugs.launchpad.net/nspr/+bug/2081110/+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 2080940] Re: unattended-upgrades broken by python-upgrade

[Bug Watch Updater]

** Changed in: python
   Status: Unknown => New

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

Title:
  unattended-upgrades broken by python-upgrade

Status in Python:
  New
Status in python3.10 package in Ubuntu:
  Confirmed
Status in python3.12 package in Ubuntu:
  Confirmed
Status in python3.8 package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Won't Fix
Status in python3.12 package in Debian:
  Confirmed

Bug description:
  at least focal and jammy are affected
  automatic updates installed "python3.10:amd64 3.10.12-1~22.04.6" tonight. 
This updated does not contain functions/classes required by unattended-upgrade. 
It resulted in broken status-emails for me, otherwise I would not have seen.

  One could argue that the bug is with python3.10, since there should be
  no breaking changes in LTS.

  Sep 17 06:05:01 xxx systemd[1]: Starting Daily apt upgrade and clean 
activities...
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: Traceback (most recent call 
last):
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/bin/unattended-upgrade", line 2005, in main
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: 
send_summary_mail(res.pkgs, res.success, res.result_str,
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/bin/unattended-upgrade", line 1509, in send_summary_mail
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: ret = 
_send_mail_using_sendmail(from_email, to_email, subject, body)
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/bin/unattended-upgrade", line 1408, in _send_mail_using_sendmail
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: 
sendmail.stdin.write(msg.as_string())
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/lib/python3.10/email/message.py", line 151, in as_string
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: from email.generator 
import Generator
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/lib/python3.10/email/generator.py", line 17, in 
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: from email.errors import 
HeaderWriteError
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: ImportError: cannot import 
name 'HeaderWriteError' from 'email.errors' 
(/usr/lib/python3.10/email/errors.py)

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/2080940/+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 2080940] Re: unattended-upgrades broken by python-upgrade

[Bug Watch Updater]

** Changed in: python3.12 (Debian)
   Status: Unknown => Confirmed

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

Title:
  unattended-upgrades broken by python-upgrade

Status in Python:
  Unknown
Status in python3.10 package in Ubuntu:
  Confirmed
Status in python3.12 package in Ubuntu:
  Confirmed
Status in python3.8 package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Won't Fix
Status in python3.12 package in Debian:
  Confirmed

Bug description:
  at least focal and jammy are affected
  automatic updates installed "python3.10:amd64 3.10.12-1~22.04.6" tonight. 
This updated does not contain functions/classes required by unattended-upgrade. 
It resulted in broken status-emails for me, otherwise I would not have seen.

  One could argue that the bug is with python3.10, since there should be
  no breaking changes in LTS.

  Sep 17 06:05:01 xxx systemd[1]: Starting Daily apt upgrade and clean 
activities...
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: Traceback (most recent call 
last):
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/bin/unattended-upgrade", line 2005, in main
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: 
send_summary_mail(res.pkgs, res.success, res.result_str,
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/bin/unattended-upgrade", line 1509, in send_summary_mail
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: ret = 
_send_mail_using_sendmail(from_email, to_email, subject, body)
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/bin/unattended-upgrade", line 1408, in _send_mail_using_sendmail
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: 
sendmail.stdin.write(msg.as_string())
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/lib/python3.10/email/message.py", line 151, in as_string
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: from email.generator 
import Generator
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]:   File 
"/usr/lib/python3.10/email/generator.py", line 17, in 
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: from email.errors import 
HeaderWriteError
  Sep 17 06:05:24 xxx apt.systemd.daily[1894012]: ImportError: cannot import 
name 'HeaderWriteError' from 'email.errors' 
(/usr/lib/python3.10/email/errors.py)

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/2080940/+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 1915358] Re: sound hdmi 5.1 subwoofer always disabled

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: New => Fix Released

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

Title:
  sound hdmi 5.1 subwoofer always disabled

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In System Sound Settings, I chose HDMI 5.1 audio, but there is no
  sound from my subwoofer in any audio application.

  The System Sound Settings for HDMI 5.1 always shows a disabled
  subwoofer slider. When I open the test window and hit the subwoofer
  icon button, no sound is produced.

  
  But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), 
all show mid-volume on the slider except for subwoffer.  But the subwoofer 
slider is enabled.  So I slide it to mid-volume, and go back to System Sound 
Settings -> test window and hit the subwoofer icon button, I hear my subwoofer 
is working fine.

  I also then hear the subwoofer in all audio applications.

  If I were to touch the System Sound Slider for the subwoofer, it
  immediately stops working again.

  I can fix it again in Pulse Audio Volumne Control again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 10 19:47:38 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2021-01-25 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1915358/+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 2080620] Re: Semitransparency of Plasma panel/widgets broken using llvmpipe on x11 since 24.2.2

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  Semitransparency of Plasma panel/widgets broken using llvmpipe on x11
  since 24.2.2

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

Bug description:
  Version: 24.2.2-1ubuntu1
  Release: oracular 24.10

  After upgrade to mesa 24.2.2-1ubuntu1 in oracular, semitransparency of
  Plasma panel/widgets broken using llvmpipe on x11.

  This is particularly prominent for testers trying our live ISO session
  (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc
  with no acceleration. With the 24.10 beta coming in less than a weeks
  time, this is bad timing.

  An issue has been opened upstream by a user/developer on Mandriva with
  the same issue.

  https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top

  Screen shots can be seen there of the impact. I have commented and
  added screenshots from Kubuntu 24.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2080620/+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 2060933] Re: QUECTEL 4G SIM, Invalid Transition Error on ThinkPad X1 Carbon Gen 12 with Ubuntu 24.04

[Bug Watch Updater]

** Changed in: network-manager
   Status: Unknown => New

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

Title:
  QUECTEL 4G SIM, Invalid Transition Error on ThinkPad X1 Carbon Gen 12
  with Ubuntu 24.04

Status in NetworkManager:
  New
Status in modemmanager package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Logs :

  ```
  2024-04-11T10:56:08.865232+02:00 0001 ModemManager[1212]:  [modem0] 
simple connect started...
  2024-04-11T10:56:08.865289+02:00 0001 ModemManager[1212]:  [modem0] 
simple connect state (3/10): enable
  2024-04-11T10:56:08.865309+02:00 0001 ModemManager[1212]:  [modem0] 
state changed (disabled -> enabling)
  2024-04-11T10:56:08.883819+02:00 0001 ModemManager[1212]:  [modem0] 
simple connect started...
  2024-04-11T10:56:08.883857+02:00 0001 ModemManager[1212]:  [modem0] 
simple connect state (4/10): wait to get fully enabled
  2024-04-11T10:56:10.785939+02:00 0001 ModemManager[1212]:  [modem0] Busy
  2024-04-11T10:56:10.789923+02:00 0001 ModemManager[1212]:  [modem0] Busy
  2024-04-11T10:56:10.789962+02:00 0001 ModemManager[1212]:  [modem0] 
couldn't enable interface: 'Invalid transition'
  2024-04-11T10:56:10.845974+02:00 0001 ModemManager[1212]:  [modem0] 
failed enabling modem: Invalid transition
  2024-04-11T10:56:10.846047+02:00 0001 ModemManager[1212]:  [modem0] 
state changed (enabling -> disabled)
  2024-04-11T10:56:10.846078+02:00 0001 ModemManager[1212]:  [modem0] 
failed waiting for enabled state: disabled
  2024-04-11T10:56:10.846747+02:00 0001 NetworkManager[1172]:   
[1712825770.8464] device (wwan0mbim0): state change: prepare -> disconnected 
(reason 'user-requested', sys-iface-state: 'managed')
  2024-04-11T10:56:10.847007+02:00 0001 NetworkManager[1172]:   
[1712825770.8469] policy: auto-activating connection 'Orange Orange Internet 1' 
(cddfb4fd-cbc0-4655-b4ad-5db26d9751ee)
  2024-04-11T10:56:10.847323+02:00 0001 NetworkManager[1172]:   
[1712825770.8472] device (wwan0mbim0): Activation: starting connection 'Orange 
Orange Internet 1' (cddfb4fd-cbc0-4655-b4ad-5db26d9751ee)
  2024-04-11T10:56:10.847374+02:00 0001 NetworkManager[1172]:   
[1712825770.8473] device (wwan0mbim0): state change: disconnected -> prepare 
(reason 'none', sys-iface-state: 'managed')
  ```

  Description:
  I am experiencing a problem with ModemManager on my ThinkPad X1 Carbon Gen 12 
running Ubuntu 24.04. The issue occurs when attempting to establish a mobile 
broadband connection. The modem enters an enable sequence but fails with an 
"Invalid transition" error, leading to a failure in enabling the modem and thus 
preventing the connection.

  Steps to Reproduce:

  Start or restart Ubuntu 24.04 on a ThinkPad X1 Carbon Gen 12.
  Attempt to connect to a mobile broadband network using the default Network 
Manager GUI.
  Observe the failure in the connection process "/var/log/syslog".

  Expected Result:
  The modem successfully transitions through its enable sequence, allowing the 
mobile broadband connection to be established without errors.

  Actual Result:
  The modem fails to enable, logging an "Invalid transition" error. This 
results in the modem being stuck in a disabled state, and the connection 
process is halted. The specific error messages from the ModemManager log are as 
follows:

  ModemManager initiates the simple connect process, moving through states to 
enable the modem.
  The modem state changes from disabled to enabling.
  Shortly after, warnings of "Busy" are logged, followed by "couldn't enable 
interface: 'Invalid transition'" and "failed enabling modem: Invalid 
transition."
  Eventually, the modem transitions back to the disabled state, and 
NetworkManager logs indicate a fallback to a disconnected state due to a 
'user-requested' action.
  System Information:

  Device: ThinkPad X1 Carbon Gen 12
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  
  Solution for the community :) :

  After further investigation and testing, I have found a workaround
  that successfully resolves the issue with ModemManager not being able
  to enable the modem, which was preventing the establishment of mobile
  broadband connections.

  Solution Description:
  The solution involves two main steps:

  - Creating Symbolic Links for FCC Unlock Settings: This step ensures
  that ModemManager has the necessary permissions and configurations to
  manage the modem's FCC lock state.

  - Directly Setting the Radio State to 'On' Using mbimcli: This command
  directly interacts with the modem to enable its radio, bypassing the
  limitations encountered with the Network Manager command-line
  interface (CLI) or graphical user interface (GUI).

  
  Steps to Apply the Solution:

  Create symbolic links for FCC unlock settings by run

[Touch-packages] [Bug 1872474] Re: Missing gpgme-json prevents use of popular Mailvelope browser extension

[Bug Watch Updater]

** Changed in: gpgme1.0 (Debian)
   Status: New => Fix Released

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

Title:
  Missing gpgme-json prevents use of popular Mailvelope browser
  extension

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Focal:
  New
Status in gpgme1.0 package in Debian:
  Fix Released

Bug description:
  As described at the Mailvelope GitHub repository wiki here
   users are able to use their local GPG keyring via gpgme-
  json (rather than the included Openpgp.js library) with several
  popular webmail services, provided that the gpgme-json binary is
  available to the browser process. I reviewed the file lists for the
  binary packages produced from this source package and found no mention
  of it. Upon closer inspection of the packaging files, the d/rules has
  an override for dh_missing for the file and a note in the changelog
  from 2018, but there was no mention of what the circumstances were
  that necessitated that decision.

  If it's possible to correct the conditions that led to the file's
  exclusion I think it would be well worth pursuing as e-mail becomes
  evermore commercialized on top of an infrastructure that never did
  place much of a premium on privacy.

  I'm running the dev release of Kubuntu 20.04 LTS "Focal Fossa" with
  version 1.13.1-7ubuntu2 of the libgpgme11 package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1872474/+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 2068056] Re: Just ran "w -s" and is segfaults, doesnt matter what arguments I pass as long as it has "-s" it segfaults.

[Bug Watch Updater]

** Changed in: procps (Debian)
   Status: Unknown => Confirmed

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

Title:
  Just ran "w -s" and is segfaults, doesnt matter what arguments I pass
  as long as it has "-s" it segfaults.

Status in procps package in Ubuntu:
  Confirmed
Status in procps package in Debian:
  Confirmed

Bug description:
  if I run "/usr/bin/w" with any arguments + "-s" it segfaults, segfaults even 
if I only do "w -s"
  fresh ubuntu 24.04 install

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: procps 2:4.0.4-4ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Jun  4 21:14:05 2024
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2068056/+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 2079477] Re: rust-gstreamer-video autopkgtest failure on s390x

[Bug Watch Updater]

** Changed in: gst-plugins-base
   Status: Unknown => New

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

Title:
  rust-gstreamer-video autopkgtest failure on s390x

Status in gst-plugins-base:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  Triaged
Status in rust-gstreamer-video package in Ubuntu:
  Triaged

Bug description:
  I'm working with upstream on this issue.

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7412

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-base/+bug/2079477/+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 2021929] Re: upgrade to exiv2 0.28.0

[Bug Watch Updater]

** Changed in: exiv2 (Debian)
   Status: New => Confirmed

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

Title:
  upgrade to exiv2 0.28.0

Status in exiv2 package in Ubuntu:
  Triaged
Status in exiv2 package in Debian:
  Confirmed

Bug description:
  The latest release is 0.28.0 and fixes some bugs I've encountered

  https://github.com/Exiv2/exiv2/releases/tag/v0.28.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/2021929/+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 2077965] Re: mesa 24.2 broke gst-plugins-base1.0 build tests

[Bug Watch Updater]

** Changed in: mesa (Debian)
   Status: New => Fix Released

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

Title:
  mesa 24.2 broke gst-plugins-base1.0 build tests

Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Debian:
  Fix Released

Bug description:
  gst-plugins-base1.0 fails to build on amd64 (the only architecture
  where build test failures are currently not ignored)

  https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.24.7-1

  The build completes successfully in a PPA where oracular-proposed is
  not enabled. I believe this failure is because of mesa 24.0.2 which is
  currently in oracular-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/2077965/+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 2021929] Re: upgrade to exiv2 0.28.0

[Bug Watch Updater]

** Changed in: exiv2 (Debian)
   Status: Unknown => New

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

Title:
  upgrade to exiv2 0.28.0

Status in exiv2 package in Ubuntu:
  Triaged
Status in exiv2 package in Debian:
  New

Bug description:
  The latest release is 0.28.0 and fixes some bugs I've encountered

  https://github.com/Exiv2/exiv2/releases/tag/v0.28.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/2021929/+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 2076912] Re: broken initrd.img after upgrade to 24.04

[Bug Watch Updater]

** Changed in: linux (Debian)
   Status: Unknown => Confirmed

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

Title:
  broken initrd.img after upgrade to 24.04

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Debian:
  Confirmed

Bug description:
  I had to upgrade a system from 22.04 to 24.04. So far, so good. Only
  after the reboot I realized I was unable to start the system.
  Debugging it was very cumbersome because it was over a slow link
  including character duplication issues when typing.

  Anyways, I tried to dig into it after a reinstall, and found that the
  initrd.img got regenerated (which also led to being unable to boot
  into the old kernel, not just the new one of 24.04). So another
  reinstall later I made sure to copy away the working initrd.img from
  22.04, and compare it to the one (re)generated by 24.04. It contained
  about 500 less lines in the output of lsinitramfs.

  The system contains hardware raid. grub is able to see the disks, only
  the (broken) initrd.img isn't able to see the disks anymore. blkid
  gives no output at all in the shell I'm dropped into.

  The server is needed for production purposes, so I had reinstalled
  once again to 22.04 to continue working. I have copied off both of the
  initrd.img files for the 5.15.0-118-generic kernel, both the one that
  was generated for 22.04, and the one that was re-generated in the
  upgrade process to 24.04.

  If you need more information, please let me know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2076912/+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 2077965] Re: mesa 24.2 broke gst-plugins-base1.0 build tests

[Bug Watch Updater]

** Changed in: mesa (Debian)
   Status: Unknown => New

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

Title:
  mesa 24.2 broke gst-plugins-base1.0 build tests

Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mesa package in Debian:
  New

Bug description:
  gst-plugins-base1.0 fails to build on amd64 (the only architecture
  where build test failures are currently not ignored)

  https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.24.7-1

  The build completes successfully in a PPA where oracular-proposed is
  not enabled. I believe this failure is because of mesa 24.0.2 which is
  currently in oracular-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/2077965/+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 11544] Re: Single click doesn't work in file chooser dialog box

[Bug Watch Updater]

** Changed in: gtk
   Status: New => Fix Released

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

Title:
  Single click doesn't work in file chooser dialog box

Status in GTK+:
  Fix Released
Status in One Hundred Papercuts:
  In Progress
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  when you select single click in file management it works for nautilus and the
  desktop but not for applications that use the "file chooser dialog box" to 
open
  files, i.e. you have to double click to open directories even with single 
click
  selected as the gnome default.

  http://bugzilla.gnome.org/show_bug.cgi?id=121113:
  http://bugzilla.gnome.org/show_bug.cgi?id=121113

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/11544/+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 2077918] Re: librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing dependencies

[Bug Watch Updater]

** Changed in: librsvg (Debian)
   Status: New => Fix Released

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

Title:
  librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing
  dependencies

Status in librsvg package in Ubuntu:
  Fix Committed
Status in librsvg package in Debian:
  Fix Released

Bug description:
  librsvg 2.58.93+dfsg-4 in oracular-proposed causes FTBFS due to
  missing dependencies.

  Also fails it's autopkgtest build test for the same reasons.

  ***

  Example FTBFS: https://launchpad.net/ubuntu/+source/kio-
  extras/4:23.08.5-0ubuntu7

  -- Importing target librsvg via pkg-config (librsvg-2.0, shared)
  -- Checking for module 'librsvg-2.0'
  --   Package 'harfbuzz', required by 'librsvg-2.0', not found
  Package 'libxml-2.0', required by 'librsvg-2.0', not found
  Package 'pangocairo', required by 'librsvg-2.0', not found
  Package 'pangoft2', required by 'librsvg-2.0', not found
  CMake Error at /usr/share/cmake-3.30/Modules/FindPkgConfig.cmake:645 
(message):
    The following required packages were not found:

     - librsvg-2.0

  ***

  stdout of the failed build test autopkgtest

  1..1
  Package harfbuzz was not found in the pkg-config search path.
  Perhaps you should add the directory containing `harfbuzz.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'harfbuzz', required by 'librsvg-2.0', not found
  Package 'libxml-2.0', required by 'librsvg-2.0', not found
  Package 'pangocairo', required by 'librsvg-2.0', not found
  Package 'pangoft2', required by 'librsvg-2.0', not found
  simple.c:1:10: fatal error: glib-object.h: No such file or directory
  1 | #include 
    |  ^~~
  compilation terminated.

  ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2077918/+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 2077918] Re: librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing dependencies

[Bug Watch Updater]

** Changed in: librsvg (Debian)
   Status: Unknown => New

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

Title:
  librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing
  dependencies

Status in librsvg package in Ubuntu:
  New
Status in librsvg package in Debian:
  New

Bug description:
  librsvg 2.58.93+dfsg-4 in oracular-proposed causes FTBFS due to
  missing dependencies.

  Also fails it's autopkgtest build test for the same reasons.

  ***

  Example FTBFS: https://launchpad.net/ubuntu/+source/kio-
  extras/4:23.08.5-0ubuntu7

  -- Importing target librsvg via pkg-config (librsvg-2.0, shared)
  -- Checking for module 'librsvg-2.0'
  --   Package 'harfbuzz', required by 'librsvg-2.0', not found
  Package 'libxml-2.0', required by 'librsvg-2.0', not found
  Package 'pangocairo', required by 'librsvg-2.0', not found
  Package 'pangoft2', required by 'librsvg-2.0', not found
  CMake Error at /usr/share/cmake-3.30/Modules/FindPkgConfig.cmake:645 
(message):
    The following required packages were not found:

     - librsvg-2.0

  ***

  stdout of the failed build test autopkgtest

  1..1
  Package harfbuzz was not found in the pkg-config search path.
  Perhaps you should add the directory containing `harfbuzz.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'harfbuzz', required by 'librsvg-2.0', not found
  Package 'libxml-2.0', required by 'librsvg-2.0', not found
  Package 'pangocairo', required by 'librsvg-2.0', not found
  Package 'pangoft2', required by 'librsvg-2.0', not found
  simple.c:1:10: fatal error: glib-object.h: No such file or directory
  1 | #include 
    |  ^~~
  compilation terminated.

  ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2077918/+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 2077862] Re: adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10 proposed

[Bug Watch Updater]

** Changed in: fink
   Status: Unknown => New

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

Title:
  adduser autopkgtests failed due to shadow 1:4.15.3-3ubuntu2 in 24.10
  proposed

Status in adduser package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  New
Status in Fink:
  New

Bug description:
  ADT of adduser fails due to the merge of shadow on 24.10 to the
  version 1:4.15.3-3ubuntu2 in 24.10

  Logs of the ADT :
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  oracular/oracular/amd64/a/adduser/20240814_214718_33c7b@/log.gz

  The failing tests:
  ---

  650s Test Summary Report
  650s ---
  650s debian/tests/f/valid_username.t (Wstat: 5120 (exited 20) Tests: 
669 Failed: 20)
  650s   Failed tests:  209-212, 214-217, 245-248, 250-253, 321-324
  650s   Non-zero exit status: 20
  650s Files=20, Tests=2631, 142 wallclock secs ( 0.44 usr  0.11 sys + 79.95 
cusr 41.69 csys = 122.19 CPU)
  650s Result: FAIL

  Logs:
  ---

  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/\}' --allow-all-names '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: \}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/\}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/\}' '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: \}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/\}'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home '\}''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/DOMAIN\user' 
--allow-all-names 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home '/home/DOMAIN\user' 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/DOMAIN\user'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 176.
  670s
  670s #   Failed test 'command success: /usr/sbin/deluser --quiet 
--remove-home 'DOMAIN\user''
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '12'
  670s # expected: '0'
  670s
  670s #   Failed test 'command success: /usr/sbin/adduser --quiet --ingroup 
nogroup --system --disabled-password --home "/home/'c4\$h\\M0n3y\"'==>@" 
--allow-all-names "'c4\$h\\M0n3y\"'==>@"'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 50.
  670s #  got: '82'
  670s # expected: '0'
  670s
  670s #   Failed test 'user exists: 'c4$h\M0n3y"'==>@'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm line 247.
  670s #  got: undef
  670s # expected: anything else
  670s
  670s #   Failed test 'path exists: /home/'c4$h\M0n3y"'==>@'
  670s #   at debian/tests/lib/AdduserTestsCommon.pm 

[Touch-packages] [Bug 2076865] Re: curl: autopkgtests fail due to libssh-dev dependency

[Bug Watch Updater]

** Changed in: curl (Debian)
   Status: Unknown => New

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

Title:
  curl: autopkgtests fail due to libssh-dev dependency

Status in curl package in Ubuntu:
  Fix Released
Status in curl package in Debian:
  New

Bug description:
  When doing merge of curl 8.9.1-1, the autopkgtests failed[1] due to
  the dependency on libssh in d/rules but on libssh2 in d/control.

  This was done in Debian[2] due to libssh2 not included in main.

  libssh2-dev is in main since noble[3] so this part can be dropped from
  d/rules.


  [1] 
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-vpa1977-plusone/oracular/amd64/c/curl/20240813_014738_94100@/log.gz
  [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888449
  [3] https://launchpad.net/ubuntu/+source/libssh2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2076865/+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 2067250] Re: /usr/bin/w -s segfaults

[Bug Watch Updater]

** Changed in: procps-ng
   Status: Unknown => Fix Released

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

Title:
  /usr/bin/w -s segfaults

Status in procps-ng:
  Fix Released
Status in procps package in Ubuntu:
  Triaged
Status in procps package in Debian:
  Confirmed

Bug description:
  procps 2:4.0.4-4ubuntu3

  Just running "w -s" segfaults:

  # w -s
   07:55:26 up 8 min,  3 users,  load average: 0.00, 0.03, 0.02
  USER TTY  FROM  IDLE WHAT
  Segmentation fault (core dumped)

  I see if I can get a backtrace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/procps-ng/+bug/2067250/+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 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127

[Bug Watch Updater]

** Changed in: dpkg (Debian)
   Status: New => Fix Committed

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

Title:
  dpkg: conffile difference visualizer subprocess returned error exit
  status 127

Status in dpkg package in Ubuntu:
  Invalid
Status in less package in Ubuntu:
  Fix Released
Status in smartmontools package in Ubuntu:
  Invalid
Status in dpkg source package in Focal:
  Invalid
Status in less source package in Focal:
  Fix Released
Status in smartmontools source package in Focal:
  Invalid
Status in dpkg source package in Groovy:
  Invalid
Status in less source package in Groovy:
  Fix Released
Status in smartmontools source package in Groovy:
  Invalid
Status in dpkg package in Debian:
  Fix Committed
Status in less package in Debian:
  Fix Released

Bug description:
  [Impact]
  During a release upgrade to Ubuntu 20.04 LTS some users are not able to view 
the differences made to a configuration file during the upgrade process. This 
creates a bad user experience and leads to extra crash reports.

  [Test Case]
  1) Upgrade from a not usr-merged system (Ubuntu 16.04 LTS) to Ubuntu 18.04 LTS
  2) Install the smartmontools package
  3) Edit /etc/default/smartmontools (it's enough to just add a comment in 
there)
  4) Upgrade to Ubuntu 20.04 LTS (this requires do-release-upgrade -d as 
20.04.1 is not out yet so release upgrades are not enabled)

  To test the fix in the version of less from focal-proposed some
  hackery of the release upgrader code will be necessary as it disables
  proposed during the upgrade process. After enabling -proposed for
  bionic you'll want to run do-release-upgrade -d, then cancel the
  upgrade. After which you can cd to /tmp/ubuntu-release-
  upgrader-$MKTMPDIR and edit DistUpgradeController.py and the if
  statement around line 641 re "Disable proposed on upgrade to a
  development release". Then run 'sudo ./focal'.

  [Regression Potential]
  None, as we are just calling update-alternatives in the preinst of less.

  
  Issue occurred on upgrade from 19.10 to 20.04

  ProblemType: PackageDistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 21:33:08 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2011-06-18 (3233 days ago)InstallationMedia: 
Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2SourcePackage: smartmontools
  Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)
  mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375
  mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+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 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail

[Bug Watch Updater]

** Changed in: heimdal (Debian)
   Status: Unknown => Fix Committed

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

Title:
  missing includedir snippet in krb5.conf causes GSSAPI to fail

Status in heimdal package in Ubuntu:
  New
Status in kerberos-configs package in Ubuntu:
  In Progress
Status in sssd package in Ubuntu:
  Fix Released
Status in heimdal source package in Jammy:
  New
Status in kerberos-configs source package in Jammy:
  New
Status in sssd source package in Jammy:
  In Progress
Status in heimdal source package in Mantic:
  Won't Fix
Status in kerberos-configs source package in Mantic:
  Won't Fix
Status in sssd source package in Mantic:
  Fix Released
Status in heimdal source package in Noble:
  New
Status in kerberos-configs source package in Noble:
  New
Status in sssd source package in Noble:
  Fix Released
Status in heimdal source package in Oracular:
  New
Status in kerberos-configs source package in Oracular:
  In Progress
Status in sssd source package in Oracular:
  Fix Released
Status in heimdal package in Debian:
  Fix Committed
Status in kerberos-configs package in Debian:
  New

Bug description:
  sssd is missing a vital line in /etc/krb5.conf
  includedir /var/lib/sss/pubconf/krb5.include.d

  Without this passwordless login using GSSAPI via SSH is not possible to a 
Ubuntu 22.04 machine.
  The solution was found here: 
https://github.com/PowerShell/Win32-OpenSSH/issues/1875
  It was fixed for rpm distributions here 
https://github.com/SSSD/sssd/issues/5893 but apparently never made it into 
Ubuntu.

  This is on Ubuntu 22.04.2 LTS with sssd 2.6.3-1ubuntu3.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2037321/+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 2029930] Re: wget crash when printing download rate

[Bug Watch Updater]

** Changed in: wget (Debian)
   Status: Confirmed => Fix Released

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

Title:
  wget crash when printing download rate

Status in wget package in Ubuntu:
  Confirmed
Status in wget source package in Noble:
  Confirmed
Status in wget package in Debian:
  Fix Released

Bug description:
  
  All supported versions of Ubuntu suffer from crashes in wget in printing of 
the download speed. I've been getting this on various servers. It's been fixed 
upstream and should probably be included in 'updates' of all supported Ubuntu 
versions.

  https://git.savannah.gnu.org/git/wget.git
  Commit 04ab35666997fbb3cd5d72497415fb3dfd62dcc5

  https://lists.gnu.org/archive/html/bug-wget/2023-08/msg1.html

  Patch attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2029930/+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 2077142] Re: iproute2: removing /sbin/ip link breaks other packages and possibly user scripts

[Bug Watch Updater]

** Changed in: vlan (Debian)
   Status: New => Fix Released

** Changed in: vlan (Debian)
   Importance: Undecided => Unknown

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

Title:
  iproute2: removing /sbin/ip link breaks other packages and possibly
  user scripts

Status in iproute2 package in Ubuntu:
  New
Status in vlan package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1078721:

  Package: iproute2
  Version: 6.10.0-1
  Severity: critical
  Justification: breaks the whole system

  The first time I rebooted after iproute2 removed the /sbin/ip link, my system
  failed to boot. I eventually discovered this was because /sbin/vconfig (from
  the "vlan" package) calls /sbin/ip and when that failed the network was not
  configured. This meant having to boot into single user mode for diagnostics
  because systemd hung forever waiting for the network.

  My ideal solution would be to revert 1064795 and mark it "wontfix" as there's
  no way to know how many users have locally written scripts that call ip via
  what used to be a perfectly valid path (and because removing the symlink buys
  exactly nothing as far as I can tell).

  A less satisfactory solution would be to add a versioned Breaks and a version
  of the vlan package with a different path to /sbin/ip. (And, of course, any
  other package that might have broken, not including local scripts which we
  can't possibly identify.)

  -- System Information:
  Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 6.10.4-amd64 (SMP w/12 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages iproute2 depends on:
  ii  debconf [debconf-2.0]  1.5.87
  ii  libbpf11:1.4.5-1
  ii  libc6  2.39-6
  ii  libcap21:2.66-5
  ii  libcap2-bin1:2.66-5
  ii  libdb5.3t645.3.28+dfsg2-7
  ii  libelf1t64 0.191-2
  ii  libmnl01.0.5-2+b1
  ii  libselinux13.5-2+b4
  ii  libtirpc3t64   1.3.4+ds-1.3
  ii  libxtables12   1.8.10-4

  iproute2 recommends no packages.

  Versions of packages iproute2 suggests:
  ii  python3  3.12.5-1

  -- debconf information excluded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2077142/+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 2076988] Re: GLib-GIO-WARNING **: 09:27:12.186: Error creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)

[Bug Watch Updater]

** Changed in: glib
   Status: Unknown => Fix Released

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

Title:
  GLib-GIO-WARNING **: 09:27:12.186: Error creating IO channel for
  /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  The issue is described here along with the fix for it.

  From my journalctl :
  Aug 14 13:56:32 envy tracker-miner-fs-3[18836]: (tracker-extract-3:18836): 
GLib-GIO-WARNING **: 13:56:32.833: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
  Aug 14 13:56:44 envy tracker-miner-fs-3[18855]: (tracker-extract-3:18855): 
GLib-GIO-WARNING **: 13:56:44.480: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
  Aug 14 13:56:58 envy tracker-miner-fs-3[18869]: (tracker-extract-3:18869): 
GLib-GIO-WARNING **: 13:56:58.941: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
  Aug 14 13:57:10 envy tracker-miner-fs-3[18894]: (tracker-extract-3:18894): 
GLib-GIO-WARNING **: 13:57:10.936: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
  Aug 14 13:57:23 envy tracker-miner-fs-3[18911]: (tracker-extract-3:18911): 
GLib-GIO-WARNING **: 13:57:23.009: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
  Aug 14 13:57:33 envy tracker-miner-fs-3[18918]: (tracker-extract-3:18918): 
GLib-GIO-WARNING **: 13:57:33.771: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
  Aug 14 13:57:47 envy tracker-miner-fs-3[18943]: (tracker-extract-3:18943): 
GLib-GIO-WARNING **: 13:57:47.573: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
  Aug 14 13:57:58 envy tracker-miner-fs-3[18953]: (tracker-extract-3:18953): 
GLib-GIO-WARNING **: 13:57:58.553: Error creating IO channel for 
/proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)

  https://gitlab.gnome.org/GNOME/localsearch/-/issues/315 and
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4021/diffs

  Best Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libglib2.0-0t64 2.80.0-6ubuntu3.1
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 14 13:56:08 2024
  InstallationDate: Installed on 2024-07-04 (41 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2076988/+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 2076542] Re: FTBFS with autoconf 2.72

[Bug Watch Updater]

** Changed in: heimdal (Debian)
   Status: New => Fix Released

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

Title:
  FTBFS with autoconf 2.72

Status in heimdal package in Ubuntu:
  In Progress
Status in heimdal package in Debian:
  Fix Released

Bug description:
  checking for gcc  options needed to detect all undeclared functions... cannot 
detect
  configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal':
  configure: error: cannot make gcc  report undeclared builtins
  See 'config.log' for more details

  
  and

  
  configure:19563: gcc  -c -g -O2  -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer 
-ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection 
-fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1
  -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= 
-D_FILE_OFFSET_BITS= conftest.c >&5
  In file included from 
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
   from /usr/include/limits.h:26,
   from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210,
   from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7,
   from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34,
   from conftest.c:50:
  /usr/include/features.h:398:52: error: operator '&&' has no right operand
398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64
|^~
  conftest.c:41:16: error: duplicate 'unsigned'
 41 | #define size_t unsigned int
|^~~~
  conftest.c:41:25: error: two or more data types in declaration specifiers
 41 | #define size_t unsigned int
| ^~~

  Looks like _FILE_OFFSET_BITS is empty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2076542/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Bug Watch Updater]

** Changed in: gnubash
   Status: New => Confirmed

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  Confirmed
Status in bash package in Ubuntu:
  Fix Released

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2076542] Re: FTBFS with autoconf 2.72

[Bug Watch Updater]

** Changed in: heimdal (Debian)
   Status: Unknown => New

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

Title:
  FTBFS with autoconf 2.72

Status in heimdal package in Ubuntu:
  In Progress
Status in heimdal package in Debian:
  New

Bug description:
  checking for gcc  options needed to detect all undeclared functions... cannot 
detect
  configure: error: in '/home/ubuntu/git/packages/heimdal/heimdal':
  configure: error: cannot make gcc  report undeclared builtins
  See 'config.log' for more details

  
  and

  
  configure:19563: gcc  -c -g -O2  -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer 
-ffile-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection 
-fdebug-prefix-map=/home/ubuntu/git/packages/heimdal/heimdal=/usr/src/heimdal-7.8.git20221117.28daf24+dfsg-7ubuntu1
  -fno-builtin -Wdate-time -D_FORTIFY_SOURCE=3 -D_LARGE_FILES= 
-D_FILE_OFFSET_BITS= conftest.c >&5
  In file included from 
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
   from /usr/include/limits.h:26,
   from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:210,
   from /usr/lib/gcc/x86_64-linux-gnu/14/include/syslimits.h:7,
   from /usr/lib/gcc/x86_64-linux-gnu/14/include/limits.h:34,
   from conftest.c:50:
  /usr/include/features.h:398:52: error: operator '&&' has no right operand
398 | #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64
|^~
  conftest.c:41:16: error: duplicate 'unsigned'
 41 | #define size_t unsigned int
|^~~~
  conftest.c:41:25: error: two or more data types in declaration specifiers
 41 | #define size_t unsigned int
| ^~~

  Looks like _FILE_OFFSET_BITS is empty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2076542/+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 2075332] Re: FTBFS with gcc-14

[Bug Watch Updater]

** Changed in: cyrus-sasl2 (Debian)
   Status: New => Fix Released

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

Title:
  FTBFS with gcc-14

Status in cyrus-sasl2 package in Ubuntu:
  Fix Committed
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/741628620/buildlog_ubuntu-oracular-
  amd64.cyrus-sasl2_2.1.28+dfsg1-6_BUILDING.txt.gz

  In file included from ../../include/hmac-md5.h:7,
   from ../../include/saslplug.h:11,
   from ../../lib/common.c:60:
  /usr/include/openssl/md5.h:49:27: note: declared here
 49 | OSSL_DEPRECATEDIN_3_0 int MD5_Init(MD5_CTX *c);
|   ^~~~
  ../../lib/common.c:2034:19: error: assignment to ‘void (*)(MD5_CTX *)’ {aka 
‘void (*)(struct MD5state_st *)’} from incompatible pointer type ‘int 
(*)(MD5_CTX *)’ {aka ‘int (*)(struct MD5state_st *)’} 
[-Wincompatible-pointer-types]
   2034 |   utils->MD5Init  = &MD5_Init;
|   ^
  ../../lib/common.c:2035:3: warning: ‘MD5_Update’ is deprecated: Since OpenSSL 
3.0 [-Wdeprecated-declarations]
   2035 |   utils->MD5Update= &MD5_Update;
|   ^
  /usr/include/openssl/md5.h:50:27: note: declared here
 50 | OSSL_DEPRECATEDIN_3_0 int MD5_Update(MD5_CTX *c, const void *data, 
size_t len);
|   ^~
  ../../lib/common.c:2035:19: error: assignment to ‘void (*)(MD5_CTX *, const 
unsigned char *, unsigned int)’ {aka ‘void (*)(struct MD5state_st *, const 
unsigned char *, unsigned int)’} from incompatible pointer type ‘int 
(*)(MD5_CTX *, const void *, size_t)’ {aka ‘int (*)(struct MD5state_st *, const 
void *, long unsigned int)’} [-Wincompatible-pointer-types]
   2035 |   utils->MD5Update= &MD5_Update;
|   ^
  ../../lib/common.c:2036:3: warning: ‘MD5_Final’ is deprecated: Since OpenSSL 
3.0 [-Wdeprecated-declarations]
   2036 |   utils->MD5Final = &MD5_Final;
|   ^
  /usr/include/openssl/md5.h:51:27: note: declared here
 51 | OSSL_DEPRECATEDIN_3_0 int MD5_Final(unsigned char *md, MD5_CTX *c);
|   ^
  ../../lib/common.c:2036:19: error: assignment to ‘void (*)(unsigned char *, 
MD5_CTX *)’ {aka ‘void (*)(unsigned char *, struct MD5state_st *)’} from 
incompatible pointer type ‘int (*)(unsigned char *, MD5_CTX *)’ {aka ‘int 
(*)(unsigned char *, struct MD5state_st *)’} [-Wincompatible-pointer-types]
   2036 |   utils->MD5Final = &MD5_Final;
|   ^
  ../../lib/common.c: In function ‘_sasl_find_verifyfile_callback’:
  ../../lib/common.c:2165:5: warning: cast between incompatible function types 
from ‘int (*)(void *, char *, int)’ to ‘int (*)(void)’ [-Wcast-function-type]
   2165 | (sasl_callback_ft)&_sasl_verifyfile,
| ^
  make[5]: *** [Makefile:608: common.lo] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2075332/+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 2073816] Re: Corrupted AV1 video decoding on AMD with Mesa 24.1.4

[Bug Watch Updater]

** Changed in: mesa
   Status: New => Fix Released

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

Title:
  Corrupted AV1 video decoding on AMD with Mesa 24.1.4

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  New

Bug description:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/11533

  For distribution packagers, to resolve this you can do the following:

  Revert b0d6e58d (not recommended)
  Apply !30255 (merged) to your Mesa package on top of v24.1.4 (recommended)

  Either of those will resolve this issue without requiring patching
  packages, though patching ffmpeg packages is also recommended. For
  that, you should backport this and this patch from upstream ffmpeg
  source. Both will apply cleanly to ffmpeg 6.x and ffmpeg 7.x source,
  the second patch patch however will not apply cleanly to 4.4.x source
  (here is a backport with the conflicts resolved for that). The
  vendored ffmpeg in Firefox also needs to be patched, here is the patch
  for that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  Uname: Linux 6.9.10-geoknyda x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 20:07:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6950 XT] 
[1002:73a5] (rev c0) (prog-if 00 [VGA controller])
 Subsystem: XFX Limited Navi 21 [XFX Speedster MERC319 Radeon RX 6950 XT] 
[1eae:6950]
  InstallationDate: Installed on 2024-05-06 (77 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.9.10-geoknyda 
root=UUID=7b9db191-b5b7-4594-ba6e-95f0fbfce262 ro quiet splash 
split_lock_detect=off mitigations=off nowatchdog vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2024
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5013
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5013:bd03/22/2024:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2024-07-09T14:26:59.883134
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.1.4~kisak1~n
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2073816/+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 2074113] Re: pymdown-extensions: FTBFS: AssertionError: False is not true

[Bug Watch Updater]

** Changed in: pymdown-extensions (Debian)
   Status: New => Fix Released

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

Title:
  pymdown-extensions: FTBFS: AssertionError: False is not true

Status in pymdown-extensions package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in pymdown-extensions package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1076907:

  Package: src:pymdown-extensions
  Version: 10.8.1-1
  Severity: serious
  Tags: ftbfs

  Dear maintainer:

  During a rebuild of all packages in unstable, your package failed to
  build:

  

  [...]
debian/rules binary
  dh binary --buildsystem=pybuild
  dh_update_autotools_config -O--buildsystem=pybuild
  dh_autoreconf -O--buildsystem=pybuild
  dh_auto_configure -O--buildsystem=pybuild
  dh_auto_build -O--buildsystem=pybuild
  I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
module
  I: pybuild base:311: python3.12 -m build --skip-dependency-check 
--no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_pymdownx
  * Building wheel...
  Successfully built pymdown_extensions-10.8.1-py3-none-any.whl
  I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with 
"installer" module
  dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:311: cd 
/<>/.pybuild/cpython3_3.12_pymdownx/build; python3.12 -m pytest 
tests
  = test session starts 
==
  platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0
  rootdir: /<>/.pybuild/cpython3_3.12_pymdownx/build
  configfile: pyproject.toml
  collected 532 items

  tests/test_extensions/test_arithmatex.py ..  [  
1%]
  tests/test_extensions/test_b64.py .  [  
2%]
  tests/test_extensions/test_betterem.py ..[  
3%]
  tests/test_extensions/test_blocks/test_admonitions.py    [  
6%]
  tests/test_extensions/test_blocks/test_definition.py .   [  
7%]
  tests/test_extensions/test_blocks/test_details.py ...[  
9%]
  tests/test_extensions/test_blocks/test_general_blocks.py ... [ 
12%]
  .[ 
15%]
  tests/test_extensions/test_blocks/test_html.py   [ 
18%]
  tests/test_extensions/test_blocks/test_legacy_tab.py [ 
20%]
  tests/test_extensions/test_blocks/test_tab.py ...[ 
22%]
  tests/test_extensions/test_details.py ...[ 
25%]
  tests/test_extensions/test_emoji.py ..   [ 
25%]
  tests/test_extensions/test_escapeall.py  [ 
26%]
  tests/test_extensions/test_highlight.py FF   [ 
32%]
  tests/test_extensions/test_inlinehilite.py ...FF [ 
36%]
  tests/test_extensions/test_keys.py . [ 
36%]
  tests/test_extensions/test_legacy_slugs.py ..[ 
37%]
  tests/test_extensions/test_magiclink.py  [ 
42%]
  tests/test_extensions/test_pathconverter.py  [ 
47%]
  .[ 
51%]
  tests/test_extensions/test_saneheaders.py .. [ 
53%]
  tests/test_extensions/test_slugs.py  [ 
54%]
  tests/test_extensions/test_smartsymbols.py ...   [ 
56%]
  tests/test_extensions/test_snippets.py . [ 
62%]
  .[ 
65%]
  tests/test_extensions/test_striphmtl.py .[ 
66%]
  tests/test_extensions/test_superfences.py .. [ 
71%]
   [ 
77%]
  tests/test_extensions/test_tabbed.py .   [ 
81%]
  tests/test_extensions/test_tabbed_alternate.py . [ 
84%]
  tests/test_syntax.py ... [ 
94%]
   [ 
96%]
  tests/test_targeted.py . [ 
99%]
  tests/test_versions.py   
[100%]

  === FAILURES 
===
   TestHighlightGuess.test_guess 
_

  self =

[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Bug Watch Updater]

** Changed in: jupyter-client (Debian)
   Status: Confirmed => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  Fix Released
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Fix Released
Status in cython-legacy package in Debian:
  Fix Released
Status in ipykernel package in Debian:
  Fix Released
Status in jupyter-client package in Debian:
  Fix Released
Status in numpy package in Debian:
  Fix Released
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Fix Released
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

[Bug Watch Updater]

** Changed in: wayland (Debian)
   Status: New => Fix Released

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

Title:
  libwayland: breaks plasma desktop start after last upgrade to version
  1.23.0-1

Status in wayland package in Ubuntu:
  New
Status in wayland package in Debian:
  Fix Released

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2074059/+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 2074059] Re: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1

[Bug Watch Updater]

** Changed in: wayland (Debian)
   Status: Unknown => New

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

Title:
  libwayland: breaks plasma desktop start after last upgrade to version
  1.23.0-1

Status in wayland package in Ubuntu:
  New
Status in wayland package in Debian:
  New

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2074059/+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 2064025] Re: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session)

[Bug Watch Updater]

** Changed in: ibus
   Status: Unknown => New

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

Title:
  Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in
  X11 session)

Status in ibus:
  New
Status in gnome-text-editor package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Triaged

Bug description:
  In the GNOME text editor, after typing an accent (e.g., "~"), the
  symbol remains visible at the cursor location instead of disappearing
  after subsequent character input.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-text-editor 46.1-1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.498
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 28 16:47:16 2024
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/2064025/+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 2064350] Re: pam_userdb.so is missing

[Bug Watch Updater]

** Changed in: pam (Debian)
   Status: Unknown => Fix Released

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

Title:
  pam_userdb.so is missing

Status in pam package in Ubuntu:
  In Progress
Status in pam source package in Noble:
  New
Status in pam package in Debian:
  Fix Released

Bug description:
  The file is missing from libpam-modules.
  This breaks, for example, existing vsftp configs if it is configured to use 
pam_userdb.so

  Log:

  vsftpd: PAM unable to dlopen(pam_userdb.so): /usr/lib/security/pam_userdb.so: 
cannot open shared object file: No such file or directory
  vsftpd: PAM adding faulty module: pam_userdb.so

  Apparently there was a change which removed this in the past, and it
  might be the removal has not been undone, while the package has been
  released nevertheless.

  
http://changelogs.ubuntu.com/changelogs/pool/main/p/pam/pam_1.5.3-5ubuntu5/changelog

    * For now remove libdb-dev so that libdb-dev can undergo time_t
  transition.  That means this version of pam does not include
  pam_userdb, which makes pam unsuitable for release.


  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 24.04 LTS
  Release:24.04

  $ apt-cache policy libpam-modules
  libpam-modules:
Installed: 1.5.3-5ubuntu5
Candidate: 1.5.3-5ubuntu5
Version table:
   *** 1.5.3-5ubuntu5 500
  500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064350/+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 2064360] Re: libpam-doc: doc-base reports missing files

[Bug Watch Updater]

** Changed in: pam (Debian)
   Status: New => Fix Released

** Changed in: pam (Debian)
   Importance: Undecided => Unknown

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

Title:
  libpam-doc: doc-base reports missing files

Status in pam package in Ubuntu:
  New
Status in pam package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1065064:

  Package: libpam-doc
  Version: 1.5.3-4
  Severity: normal

  An upgrade reported:

Error in `/usr/share/doc-base/libpam-doc.pam-admin-guide', line 14: all 
`Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-applications-guide', line 17: 
all `Format' sections are invalid.
Error in `/usr/share/doc-base/libpam-doc.pam-modules-guide', line 14: all 
`Format' sections are invalid.

  This is true; all of /usr/share/doc/libpam-doc/html/Linux-PAM_SAG.html,
  /usr/share/doc/libpam-doc/html/sag-*.html,
  /usr/share/doc/libpam-doc/txt/Linux-PAM_SAG.txt.gz,
  /usr/share/doc/libpam-doc/html/Linux-PAM_ADG.html,
  /usr/share/doc/libpam-doc/html/adg*.html,
  /usr/share/doc/libpam-doc/txt/Linux-PAM_ADG.txt.gz,
  /usr/share/doc/libpam-doc/html/Linux-PAM_MWG.html,
  /usr/share/doc/libpam-doc/html/mwg*.html, and
  /usr/share/doc/libpam-doc/txt/Linux-PAM_MWG.txt.gz are listed in those
  doc-base files but are in fact missing.  I don't know whether this is
  intentional (in which case the doc-base registrations should be removed
  to match), or an accidental build issue that should be fixed.

  -- System Information:
  Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)

  Kernel: Linux 6.6.0-14-generic (SMP w/4 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE
  Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
  Shell: /bin/sh linked to /usr/bin/dash
  Init: unable to detect

  -- no debconf information

  -- 
  Colin Watson (he/him)  [cjwat...@debian.org]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2064360/+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 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

** Changed in: plymouth
   Status: New => Fix Released

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

Title:
  Frequent boot to black display

Status in Plymouth:
  Fix Released
Status in SDDM:
  New
Status in systemd:
  New
Status in plymouth package in Ubuntu:
  Incomplete
Status in sddm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/2063143/+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 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

** Changed in: linux
   Status: New => Fix Released

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

Title:
  Frequent boot to black display

Status in Linux:
  Fix Released
Status in Plymouth:
  New
Status in SDDM:
  New
Status in systemd:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete
Status in sddm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2063143/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

[Bug Watch Updater]

** Changed in: gnome-shell-extension-appindicator
   Status: Unknown => Fix Released

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu jammy and previous releases, right clicking on appindicator
  icons brings up the menu below the appindicator with appropriate gnome
  theming. In ubuntu noble, right clicking on some appindicator icons
  (example: barrier) results in the menu appearing on the left side of
  the screen without proper theming.

  See attached image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2063257] Re: Noble: default pam config for login tries do load non-existent pam_lastlog.so

[Bug Watch Updater]

** Changed in: shadow (Debian)
   Status: Unknown => New

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

Title:
  Noble: default pam config for login tries do load non-existent
  pam_lastlog.so

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Noble:
  New
Status in shadow package in Debian:
  New

Bug description:
  pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still
  there in the code, but not built by default.

  And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2)
  does.

  This does not prevent console logins, but generates an error in the logs:
  Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): 
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file 
or directory
  Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so

  Debian's shadow package is also still shipping this config[2].

  If you think we should re-enable pam_lastlog, then this becomes a bug
  in the src:pam package, but keep in mind upstream is keen on removing
  it, and we might be better off switching to an alternative, perhaps
  pam_lastlog2[3].

  1. 
https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65
  2. 
https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82
  3. https://wiki.debian.org/PamLastlog2
  4. 
https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816

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


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

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

[Bug Watch Updater]

** Changed in: gnome-online-accounts
   Status: New => Fix Released

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

Title:
  goa-daemon crashed with SIGABRT

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

Bug description:
  * Impact

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

  * Test case

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

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

  * Regression potential

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

  -

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+subscriptions


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

[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Bug Watch Updater]

** Changed in: cython (Debian)
   Status: Confirmed => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Fix Released
Status in cython-legacy package in Debian:
  Fix Released
Status in ipykernel package in Debian:
  Fix Released
Status in jupyter-client package in Debian:
  Confirmed
Status in numpy package in Debian:
  Fix Released
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Fix Released
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.webkit.org/show_bug.cgi?id=272827.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-04-17T15:47:22+00:00 Webkitbug wrote:

Created attachment 470961
Image of the artifacts.

All pages do not render properly in both the Eiphany and surf browsers
(see attached example). This is on a Raspberry Pi 4, running NixOS.
Here's the output of webkit://gpu in the Eiphany browser:

```
{
"Version Information": {
"WebKit version": "WebKitGTK 2.44.1 (tarball)",
"Operating system": "Linux 6.1.63 #1-NixOS SMP Tue Jan  1 00:00:00 UTC 
1980 aarch64",
"Desktop": "XFCE",
"Cairo version": "1.18.0 (build) 1.18.0 (runtime)",
"GStreamer version": "1.22.9 (build) GStreamer 1.22.9 (runtime)",
"GTK version": "4.12.5 (build) 4.12.5 (runtime)"
},
"Display Information": {
"Identifier": "1",
"Type": "X11",
"Screen geometry": "0,0 1920x1080",
"Screen work area": "0,27 1920x1053",
"Depth": "24",
"Bits per color component": "8",
"DPI": "96",
"VBlank type": "Timer",
"VBlank refresh rate": "60Hz",
"DRM Device": "/dev/dri/card0",
"DRM Render Node": "/dev/dri/renderD128"
},
"API": "OpenGL ES 2 (libepoxy)",
"Hardware Acceleration Information": {
"Policy": "always",
"WebGL enabled": "Yes",
"Renderer": "DMABuf (Supported buffers: Hardware, Shared Memory)",
"Native interface": "None"
},
"Hardware Acceleration Information (Render process)": {
"Platform": "GBM",
"GL_RENDERER": "V3D 4.2.14",
"GL_VENDOR": "Broadcom",
"GL_VERSION": "OpenGL ES 3.1 Mesa 24.0.3",
"GL_SHADING_LANGUAGE_VERSION": "OpenGL ES GLSL ES 3.10",
"GL_EXTENSIONS": "GL_EXT_blend_minmax GL_EXT_multi_draw_arrays 
GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_s3tc 
GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc 
GL_EXT_texture_format_BGRA GL_OES_compressed_ETC1_RGB8_texture 
GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap 
GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 
GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float 
GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float 
GL_EXT_draw_instanced GL_EXT_texture_sRGB_decode GL_OES_EGL_image 
GL_OES_depth_texture GL_AMD_performance_monitor GL_OES_packed_depth_stencil 
GL_EXT_texture_type_2_10_10_10_REV GL_NV_conditional_render 
GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer 
GL_EXT_read_format_bgra GL_NV_pack_subimage GL_EXT_frag_depth 
GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync 
GL_OES_vertex_array_object G
 L_ANGLE_pack_reverse_row_order GL_ANGLE_texture_compression_dxt3 
GL_ANGLE_texture_compression_dxt5 GL_EXT_occlusion_query_boolean 
GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer 
GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_APPLE_sync 
GL_EXT_draw_buffers GL_EXT_instanced_arrays GL_EXT_map_buffer_range 
GL_KHR_debug GL_KHR_texture_compression_astc_ldr GL_NV_generate_mipmap_sRGB 
GL_NV_pixel_buffer_object GL_OES_depth_texture_cube_map 
GL_OES_required_internalformat GL_OES_surfaceless_context 
GL_EXT_color_buffer_float GL_EXT_debug_label GL_EXT_sRGB_write_control 
GL_EXT_separate_shader_objects GL_EXT_shader_implicit_conversions 
GL_EXT_shader_integer_mix GL_EXT_base_instance 
GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_copy_image 
GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex 
GL_EXT_polygon_offset_clamp GL_EXT_primitive_bounding_box 
GL_EXT_shader_io_blocks GL_EXT_texture_border_clamp 
GL_EXT_texture_cube_map_array GL_EXT_textur
 e_view GL_KHR_context_flush_control GL_NV_image_formats 
GL_NV_shader_noperspective_interpolation GL_OES_copy_image 
GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex 
GL_OES_primitive_bounding_box GL_OES_shader_io_blocks 
GL_OES_texture_border_clamp GL_OES_texture_cube_map_array 
GL_OES_texture_stencil8 GL_OES_texture_storage_multisample_2d_array 
GL_OES_texture_view GL_EXT_buffer_storage GL_EXT_float_blend 
GL_EXT_geometry_point_size GL_EXT_geometry_shader GL_KHR_no_error 
GL_KHR_texture_compression_astc_sliced_3d GL_OES_EGL_image_external_essl3 
GL_OES_geometry_point_size GL_OES_geometry_shader GL_OES_shader_image_atomic 
GL_EXT_clear_texture GL_EXT_texture_compression_s3tc_srgb 
GL_MESA_shader_integer_functions GL_EXT_color_buffer_half_float 
GL_EXT_texture_mirror_clamp_to_edge GL_KHR_parallel_shader_compile 
GL_EXT_EGL_image_storage GL_MESA_framebuffer_flip_y GL_EXT_texture_query_lo

[Touch-packages] [Bug 1530142] Re: [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all playback write error (DMA or IRQ trouble?)

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=112721.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-02-20T18:02:16+00:00 sapjsm wrote:

Hi Folks,

new laptop (Dell 5559), new installation.

No sound, either on headphones or internal speakers. Have been all over
forums, tried every fix I can find.

Sound is not muted, and I believe the settings are correct, but it's
hard to be sure, as each answer I find seems to have slightly differing
advice, albeit a lot in common.

Submitted bug to Canonical, and they have requested I raise it with you.

Information:

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: john 2107 F pulseaudio
CurrentDesktop: Unity
Date: Wed Dec 30 14:25:38 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-12-24 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_AlsaPlaybackTestStderr:
 W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r
  x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o 
r
  T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: john 2107 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Inspiron 5559, Realtek ALC255, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.6
dmi.board.name: 0664DJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/5


On 2016-02-20T20:24:28+00:00 tiwai wrote:

The kernel is way too old.  Try the latest 4.4.x or 4.5-rc kernel at
first.

If it still doesn't work, give alsa-info.sh output for further analysis.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/6


On 2016-02-21T21:35:31+00:00 sapjsm wrote:

(In reply to Takashi Iwai from comment #1)
> The kernel is way too old.  Try the latest 4.4.x or 4.5-rc kernel at first.
> 
> If it still doesn't work, give alsa-info.sh output for further analysis.

Hi,

you're saying that the kernel for the current long-term release of
Ubuntu, version 14.04 (Trusty Tahr) is too old?

Does that mean I have to upgrade to Ubuntu 15.04?  Or can I just do a
kernel upgrade?

Best regards,

John

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/7


On 2016-02-22T09:52:53+00:00 tiwai wrote:

(In reply to John M from comment #2)
> (In reply to Takashi Iwai from comment #1)
> > The kernel is way too old.  Try the latest 4.4.x or 4.5-rc kernel at first.
> > 
> > If it still doesn't work, give alsa-info.sh output for further analysis.
> 
> Hi,
> 
> you're saying that the kernel for the current long-term release of Ubuntu,
> version 14.04 (Trusty Tahr) is too old?

Yes.

> Does that mean I have to upgrade to Ubuntu 15.04?  Or can I just do a kernel
> upgrade?

At best, build the kernel by yourself.  If the problem is still seen
with the latest upstream kernel, report back here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/8


On 2016-02-22T20:29:33+00:00 sapjsm wrote:

Created attachment 204351
Screen capture after attempted upgrade

Screen capture after attempted upgrade to 4.5-rc

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1530142/comments/9


On 2016-02-22T20:33:49+00:00 sapjsm wrote:

Hi there Iwai,

I tried upgrading to 4.5-rc, but got errors.  I followed the
instructions for 64-bit at:

https://websetnet.com/install-linux-
kerne

[Touch-packages] [Bug 2062146] Re: MiniBrowser crashed with SIGSEGV

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  MiniBrowser crashed with SIGSEGV

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  MiniBrowser crashed immediately on Raspberry Pi 400.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libwebkit2gtk-4.1-0 2.44.0-2
  ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1
  Uname: Linux 6.8.0-1002-raspi aarch64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:32:12 2024
  ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser
  JournalErrors: -- No entries --
  ProcCmdline: ./MiniBrowser
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: webkit2gtk
  StacktraceTop:
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /lib/aarch64-linux-gnu/libgbm.so.1
   ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0
  Title: MiniBrowser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2062146/+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 2061708] Re: Yubikey stopped working after noble upgrade

[Bug Watch Updater]

** Changed in: archlinux-lp
   Status: Unknown => Fix Released

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

Title:
  Yubikey stopped working after noble upgrade

Status in Arch Linux on Launchpad:
  Fix Released
Status in gnupg2 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
  since upgrading to Noble I get the following trying to access it.

  $ gpg --card-status
  gpg: selecting card failed: No such device 
  gpg: OpenPGP card not available: No such device

  If I run this as root it works:

  $ sudo gpg --card-status
  Reader ...: 1050:0407:X:0
  Application ID ...: D27600012401000609082616
  Application type .: OpenPGP
  Version ..: 2.1
  Manufacturer .: Yubico
  Serial number : 
  Name of cardholder: [not set]
  Language prefs ...: [not set]
  Salutation ...: 
  URL of public key : [not set]
  Login data ...: [not set]
  Signature PIN : not forced
  Key attributes ...: rsa4096 rsa4096 rsa2048
  Max. PIN lengths .: 127 127 127
  PIN retry counter : 10 0 10
  Signature counter : 1172
  UIF setting ..: Sign=off Decrypt=off Auth=off
  Signature key : 
created : 
  Encryption key: 
created : 
  Authentication key: [none]
  General key info..: [none]

  If I manually run pcscd.service then it stops working both as root and
  a user.

  $ sudo pkill -9 scdaemon
  $ sudo systemctl start pcscd.service
  $ gpg --card-status
  gpg: selecting card failed: No such device
  gpg: OpenPGP card not available: No such device
  $ sudo gpg --card-status
  gpg: selecting card failed: No such device
  gpg: OpenPGP card not available: No such device

  It might be worth mentioning I'm accessing the machine over SSH, so I
  also did experiment with a polkit rule like this:

  polkit.addRule(function(action, subject) {
  if (action.id == "org.debian.pcsc-lite.access_card" &&
  subject.isInGroup("sudo")) {
  return polkit.Result.YES;
  }
  });
  polkit.addRule(function(action, subject) {
  if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
  subject.isInGroup("sudo")) {
  return polkit.Result.YES;
  }
  });

  Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
  polkit.service in case this was a polkit issue, but this didn't do
  anything.

  
  Versions in noble:
  pcscd: 2.0.3-1build1
  libpcslite1: 2.0.3-1build1
  gnupg: 2.4.4-2ubuntu17
  scdaemon: 2.4.4-2ubuntu17

To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+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 2061584] Re: Rendering issues in VirtualBox with 3d on (GTK ngl backend)

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

** Changed in: gtk
   Status: Unknown => New

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

Title:
  Rendering issues in VirtualBox with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Triaged
Status in mesa source package in Noble:
  Triaged

Bug description:
  GTK4 apps are rendering very badly with Ubuntu 24.04 LTS Beta when ran
  in VirtualBox.

  This includes the Welcome to Ubuntu app (gnome-initial-setup), gnome-
  text-editor, and drawing the background (which uses gnome-shell-
  extension-desktop-icons-ng on Ubuntu).

  This issue was triggered by GTK4's switch to ngl as the default
  renderer instead of gl.

  However, some other similar issues (LP: #2061118, LP: #2060679) are
  being fixed in mesa instead of in gtk4 itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2061584/+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 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

[Bug Watch Updater]

** Changed in: gtk
   Status: Unknown => New

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

Title:
  Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in gtk4 source package in Noble:
  Triaged
Status in mesa source package in Noble:
  Triaged
Status in open-vm-tools source package in Noble:
  Invalid

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2061118/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Bug Watch Updater]

** Changed in: cython-legacy (Debian)
   Status: New => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Confirmed
Status in cython-legacy package in Debian:
  Fix Released
Status in ipykernel package in Debian:
  Fix Released
Status in jupyter-client package in Debian:
  Confirmed
Status in numpy package in Debian:
  Fix Released
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Fix Released
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

Status in GTK+:
  Fix Released
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in gtk4 source package in Noble:
  Triaged
Status in mesa source package in Noble:
  Triaged
Status in open-vm-tools source package in Noble:
  Invalid

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2061118/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Bug Watch Updater]

** Changed in: wike
   Status: Unknown => New

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  New

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2060319] Re: tracker failing autopkgtest on noble

[Bug Watch Updater]

** Changed in: tracker
   Status: New => Fix Released

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

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Confirmed

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/tracker/+bug/2060319/+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 2060676] Re: login: remove pam_lastlog.so from config

[Bug Watch Updater]

** Changed in: shadow (Debian)
   Importance: Undecided => Unknown

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

Title:
  login: remove pam_lastlog.so from config

Status in shadow package in Ubuntu:
  New
Status in shadow package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1068229:

  Package: libpam-modules
  Version: 1.5.3-6
  Severity: normal

  I noticed the following line in my logs:

  login[2449]: PAM unable to dlopen(pam_lastlog.so):
  /usr/lib/security/pam_lastlog.so: cannot open shared object file: No
  such file or directory

  I looked in the deb files from snapshot.debian.org, and noticed the last 
version
  that had it was 1.5.2-9.1 - starting from 1.5.3-1 it disappeared.

  Maybe it's fallout from the time_t transition and you're already aware of it, 
in
  which case feel free to close.

  Thanks,

  -- M

  -- System Information:
  Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386, arm64

  Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
  Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)

  Versions of packages libpam-modules depends on:
  ii  debconf [debconf-2.0]  1.5.86
  ii  libaudit1  1:3.1.2-2.1
  ii  libc6  2.37-15.1
  ii  libcrypt1  1:4.4.36-4
  ii  libpam-modules-bin 1.5.3-6
  ii  libpam0g   1.5.3-6
  ii  libselinux13.5-2
  ii  libsystemd0255.4-1+b1

  libpam-modules recommends no packages.

  libpam-modules suggests no packages.

  -- debconf information excluded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2060676/+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 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

** Changed in: gst-python1.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Debian:
  Fix Released

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2060319] Re: tracker failing autopkgtest on noble

[Bug Watch Updater]

** Changed in: tracker (Debian)
   Status: Unknown => Confirmed

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

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  New
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Confirmed

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/tracker/+bug/2060319/+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 2060319] Re: tracker failing autopkgtest on noble

[Bug Watch Updater]

** Changed in: tracker
   Status: Unknown => New

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

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  New
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Unknown

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/tracker/+bug/2060319/+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 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

** Changed in: pygobject
   Status: New => Fix Released

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Confirmed

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/2057836/+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 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  [regression] Windows flicker to black when resizing (Intel Apollo
  Lake)

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I see the black zones, small windows breaks. For additional details, I use 
eoan-proposed and eoan-backports packages.
  You can see this problem in my video: 
https://photos.app.goo.gl/3rvLkqJj6hZwSscw9

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  5 13:39:13 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (3 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1835521/+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 2059856] Re: gdb 10.0 fails to examine any global variables in D programs

[Bug Watch Updater]

** Changed in: gdb
   Status: Confirmed => Fix Released

** Bug watch added: Sourceware.org Bugzilla #30276
   https://sourceware.org/bugzilla/show_bug.cgi?id=30276

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

Title:
  gdb 10.0 fails to examine any global variables in D programs

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * GDB 10.0 introduced a regression where it cannot inspect any global 
variables in any D programs compiled by any D compiler.
   * LDC2 and GDC upstream stated Focal does not have such a problem and stuck 
to this release for their test images.

  [ Test Plan ]

  Considering the following D program:

  ```
  module t;

  class uv {
  int i;
  }

  __gshared uv i;
  int main() {
  i = new uv();
  return 0; // #break
  }
  ```

  If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
  run the GDB using the following commands ...

  ```
  b t.d:10
  p t.i
  ```

  ... you will notice GDB will complain that "'t.i' has unknown type;
  cast it to its declared type."

  [ Where problems could occur ]

    * The fix consists of a single line change to the demangler. The worst-case 
scenario would be breaking the demangling functionality of other programming 
languages. However, the newer D ABI uses a symbol mangling scheme that is very 
difficult to confuse with other programming languages.
    * Incorrect symbol de-mangling may also cause user confusion. However, the 
patch fixed a fundamental usability issue.

  [ Other Info ]

* Initial discussion in the LDC2 bug tracker:
  https://github.com/ldc-developers/ldc/issues/4389

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+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 2060073] Re: folks build test failures with glib 2.80

[Bug Watch Updater]

** Changed in: libfolks
   Status: Unknown => New

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

Title:
  folks build test failures with glib 2.80

Status in libfolks:
  New
Status in folks package in Ubuntu:
  Triaged

Bug description:
  folks build tests are failing.

  I reported this issue upstream. It appears to be triggered by glib
  2.80 and gobject-introspection 1.80.

  We worked around this issue for Ubuntu 24.04 LTS by ignoring build
  test failures because it was essential that we build folks to clear
  transitions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfolks/+bug/2060073/+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 2059856] Re: gdb 10.0 fails to examine any global variables in D programs

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=31580.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-03-30T00:23:30+00:00 Zixing Liu wrote:

Created attachment 15447
Minimal reproducible example (D source code)

Hi there,

I have discovered a D class type resolution regression since GDB 10 (it
was working properly in GDB 9).

Please find the reproducer in the file attached. You can compile the
source code using either GDC or LDC2 (both can reproduce this issue):

gdc -g -O0 t.d -o t

To reproduce the bug, set the breakpoint to t.d:10 and examine the `i`
global variable (using `p t.i`). GDB will then complain that "'t.i' has
unknown type; cast it to its declared type."

I found a workaround to this problem by using `p (uv*)_D1t1iCQf2uv`, but
obviously, this is non-ideal: the developer may not know the mangled
variable name easily.

Since this looks like a regression, I did a simple `git bisect` that led
me to this commit: https://sourceware.org/git/?p=binutils-
gdb.git;a=commit;h=727b7b1864973c2645a554727afd0eaf1303673a. I am unsure
how demangle changes could affect the type resolution (maybe it's
because GDB got confused about which entity to decode?)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/0


On 2024-03-30T19:30:45+00:00 Tromey-b wrote:

Computing the "physname" decides that the symbol should be named:

(top-gdb) p physname
$37 = 0x2c70490 "_D1t1iCQf2uv"

... which is plainly wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/1


On 2024-03-30T19:36:27+00:00 Tromey-b wrote:

Ok, so while gdb's symbol reader is still really wrong here --
this physname stuff is pretty broken -- the root cause of this
particular bug is also that libiberty does not auto-demangle
D symbols.

You can see this on the command line:

prentzel. c++filt  _D1t1iCQf2uv
_D1t1iCQf2uv
prentzel. c++filt -s dlang  _D1t1iCQf2uv
t.i

To my eye this seems to be an oversight in cplus-dem.c,
where the D code follows some earlier code; but perhaps
the author didn't realize that the reason the Ada
code does not check AUTO_DEMANGLING is that the
Ada encoding isn't unambiguous in the way the D encoding is.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/2


On 2024-03-30T19:49:00+00:00 Tromey-b wrote:

Testing a patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/3


On 2024-03-30T20:10:51+00:00 Tromey-b wrote:

https://sourceware.org/pipermail/gdb-patches/2024-March/207686.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/4


** Changed in: gdb
   Status: Unknown => Confirmed

** Changed in: gdb
   Importance: Unknown => Medium

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

Title:
  gdb 10.0 fails to examine any global variables in D programs

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  New

Bug description:
  Summary:

   * GDB 10.0 introduced a regression where it cannot inspect any global 
variables in any D programs compiled by any D compiler.
   * LDC2 and GDC upstream stated Focal does not have such a problem and stuck 
to this release for their test images.

  Reproduce steps:

  Considering the following D program:

  ```
  module t;

  class uv {
  int i;
  }

  __gshared uv i;
  int main() {
  i = new uv();
  return 0; // #break
  }
  ```

  If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
  run the GDB using the following commands ...

  ```
  b t.d:10
  p t.i
  ```

  ... you will notice GDB will complain that "'t.i' has unknown type;
  cast it to its declared type."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+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 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

[Bug Watch Updater]

** Changed in: mesa (Debian)
   Status: Confirmed => Fix Released

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Fix Released

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 2059258] Re: conntrack-tools: FTBFS: configure: error: Package requirements (libtirpc) were not met

[Bug Watch Updater]

** Changed in: conntrack-tools (Debian)
   Status: New => Fix Released

** Changed in: conntrack-tools (Debian)
   Importance: Undecided => Unknown

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

Title:
  conntrack-tools: FTBFS: configure: error: Package requirements
  (libtirpc) were not met

Status in conntrack-tools package in Ubuntu:
  Triaged
Status in kmod package in Ubuntu:
  New
Status in conntrack-tools package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1066476:

  Source: conntrack-tools
  Version: 1:1.4.8-1
  Severity: serious
  Justification: FTBFS
  Tags: trixie sid ftbfs
  User: lu...@debian.org
  Usertags: ftbfs-20240313 ftbfs-trixie

  Hi,

  During a rebuild of all packages in sid, your package failed to build
  on amd64.

  
  Relevant part (hopefully):
  > checking for byacc... no
  > checking for pkg-config... /usr/bin/pkg-config
  > checking pkg-config is at least version 0.9.0... yes
  > checking for rpc/rpc_msg.h... no
  > checking for libtirpc... no
  > configure: error: Package requirements (libtirpc) were not met
  > 
  > Package 'libtirpc', required by 'virtual:world', not found
  > 
  > Consider adjusting the PKG_CONFIG_PATH environment variable if you
  > installed software in a non-standard prefix.
  > 
  > Alternatively, you may set the environment variables LIBTIRPC_CFLAGS
  > and LIBTIRPC_LIBS to avoid the need to call pkg-config.
  > See the pkg-config man page for more details.
  > tail -v -n \+0 config.log

  
  The full build log is available from:
  http://qa-logs.debian.net/2024/03/13/conntrack-tools_1.4.8-1_unstable.log

  All bugs filed during this archive rebuild are listed at:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
  or:
  
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

  A list of current common problems and possible solutions is available at
  http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

  If you reassign this bug to another package, please mark it as 'affects'-ing
  this package. See https://www.debian.org/Bugs/server-control#affects

  If you fail to reproduce this, please provide a build log and diff it with 
mine
  so that we can identify if something relevant changed in the meantime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/2059258/+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 2041496] Re: btmgmt --index broken in Mantic

[Bug Watch Updater]

** Changed in: bluez
   Status: Unknown => Fix Released

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

Title:
  btmgmt --index broken in Mantic

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/2041496/+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 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

[Bug Watch Updater]

** Changed in: glibc
   Status: New => Invalid

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in GLibC:
  Invalid
Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting is wrong:

  LC_NUMERIC=nb_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>
  LC_NUMERIC=nn_NO.UTF-8
  < 1>
  <   100>
  <   1 000>
  <  10 000>
  < 100 000>
  <1 000 000>
  <10 000 000>

  I reproduced the issue with coreutils-8.32-4.1ubuntu1.1 (Ubuntu 22.04)
  as well as coreutils-9.3-5.fc39.x86_64 (Fedora 39).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: coreutils 8.32-4.1ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Mar 22 21:33:13 2024
  InstallationDate: Installed on 2022-11-29 (479 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed

[Bug Watch Updater]

** Changed in: network-manager
   Status: New => Fix Released

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

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

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged

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

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

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

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

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


  network-manager version: 1.36.6-0ubuntu2

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


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

[Touch-packages] [Bug 2059033] Re: Xorg crashes with SIGABRT

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  Xorg crashes with SIGABRT

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

Bug description:
  I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915
  graphics driver.  I am seeing random Xorg crashes due to SIGABRT,
  which kicks me back to the login screen.

  Ubuntu version: 22.04
  Kernel version: 5.19.0-50-generic
  libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 

  I am seeing this message in kern.log:

  i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617]

  I have also gotten a core dump; here is the track trace:

  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140131874372224) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=6, threadid=140131874372224) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #4  0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79
  #5  0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352
  #6  0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879
  #7  0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal 
%d (%s). Server aborting\n") at ../../../../os/log.c:1017
  #8  0x560c5cc72abd in OsSigHandler (unused=, 
sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156
  #9  OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at 
../../../../os/osinit.c:110
  #10 
  #11 __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140131874372224) at ./nptl/pthread_kill.c:44
  #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at 
./nptl/pthread_kill.c:78
  #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79
  #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, 
file=, line=) at 
../src/gallium/drivers/iris/iris_batch.c:1116
  #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, 
out_fence=0x0, flags=) at 
../src/gallium/drivers/iris/iris_fence.c:267
  #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at 
../src/mesa/state_tracker/st_cb_flush.c:60
  #19 st_glFlush (ctx=, gallium_flush_flags=0) at 
../src/mesa/state_tracker/st_cb_flush.c:94
  #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, 
timeout=0x713af054) at ../../../../glamor/glamor.c:285
  #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, 
timeout=0x713af054) at 
../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701
  #22 0x560c5cb01095 in BlockHandler 
(pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394
  #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:201
  #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492
  #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, 
envp=) at ../../../../dix/main.c:272
  #26 0x7f72fec29d90 in __libc_start_call_main 
(main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, 
argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58
  #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , 
argc=11, argv=0x713af268, init=, fini=, 
rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392
  #28 0x560c5cae9605 in _start ()

  This post describes a similar issue:
  https://gitlab.freedesktop.org/drm/intel/-/issues/4858

  I tried using a workaround from the above link, to set GPU to max
  frequency using command "intel_gpu_frequency -m", this seemed to
  reduce the rate of occurrence from once per day to once every 3 days,
  but this is not a permanent solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2059033/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection (Debian)
   Status: New => Fix Released

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  Fix Released

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2058775] Re: coreutils: printf formatting bug for nb_NO and nn_NO locales

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=31542.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-03-24T09:42:26+00:00 Thomas Dreibholz wrote:

There is a formatting bug for integers in printf() when using locale
settings and formatting with thousands separator.

Test program printfbug.c:
#include 
#include 
#include 

int main(int argc, char** argv)
{
   setlocale (LC_ALL, "");

   struct lconv* loc = localeconv();
   printf("Thousands Separator: <%s>\n", loc->thousands_sep);

   for(int i = 1; i \tint <%'10d>\n", f, n);
   }
   return 0;
}

Test run:
for l in en_US de_DE nb_NO nn_NO ; do
   echo "$l:" ; LC_ALL=$l.UTF-8 ./printfbug 1 10 100 1000 1 10 100 
1000
done

Output:
en_US:
Thousands Separator: <,>
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1,000> int < 1,000>
double <10,000> int <10,000>
double <   100,000> int <   100,000>
double < 1,000,000> int < 1,000,000>
double <10,000,000> int <10,000,000>
de_DE:
Thousands Separator: <.>
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1.000> int < 1.000>
double <10.000> int <10.000>
double <   100.000> int <   100.000>
double < 1.000.000> int < 1.000.000>
double <10.000.000> int <10.000.000>
nb_NO:
Thousands Separator: < >
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1 000> int <   1 000>
double <10 000> int <  10 000>
double <   100 000> int < 100 000>
double < 1 000 000> int <1 000 000>
double <10 000 000> int <10 000 000>
nn_NO:
Thousands Separator: < >
double < 1> int < 1>
double <10> int <10>
double <   100> int <   100>
double < 1 000> int <   1 000>
double <10 000> int <  10 000>
double <   100 000> int < 100 000>
double < 1 000 000> int <1 000 000>
double <10 000 000> int <10 000 000>

That is, en_US and de_DE are fine (they use ',' and '.' as thousands
separator). But nb_NO and nn_NO produce the wrong output when using
integers (%'10d). However, float is fine as well (%'10.0f).

For nb_NO and nn_NO, the separator is a 3-byte UTF-8 character 0xe2 0x80
0xaf, which is UTF-8 NARROW NO-BREAK SPACE ->
https://www.fileformat.info/info/unicode/char/202f/index.htm . It seems
that for integer formatting, the number of bytes is processed, instead
of counting the actual characters. For float formatting, the number of
characters is counted correctly.

That is:
$ LC_ALL=nb_NO.UTF-8 ./printfbug 1000 | hexdump -C
  54 68 6f 75 73 61 6e 64  73 20 53 65 70 61 72 61  |Thousands Separa|
0010  74 6f 72 3a 20 3c e2 80  af 3e 0a 64 6f 75 62 6c  |tor: <...>.doubl|
0020  65 20 3c 20 20 20 20 20  31 e2 80 af 30 30 30 3e  |e < 1...000>|
0030  09 69 6e 74 20 3c 20 20  20 31 e2 80 af 30 30 30  |.int <   1...000|
0040  3e 0a |>.|
0042

I can reproduce the issue under Ubuntu 22.04, Ubuntu 24.04 (development
version), and Fedora 39.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2058775/comments/5


** Changed in: coreutils
   Status: Unknown => New

** Changed in: coreutils
   Importance: Unknown => Medium

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

Title:
  coreutils: printf formatting bug for nb_NO and nn_NO locales

Status in coreutils:
  New
Status in coreutils package in Ubuntu:
  New

Bug description:
  I just discovered a printf bug for at least the nb_NO and nn_NO
  locales when printing numbers with thousands separator. To reproduce:

  #!/bin/bash
  for l in de_DE en_US nb_NO ; do
     echo "LC_NUMERIC=$l.UTF-8"
     for n in 1 100 1000 1 10 100 1000 ; do
    LC_NUMERIC=$l.UTF-8 /usr/bin/printf "<%'10d>\n" $n
     done
  done

  The expected output of "%'10d" is a right-formatted number string with
  10 characters.

  The output of the test script is fine for e.g. LC_NUMERIC=de_DE.UTF-8
  and LC_NUMERIC=en_US.UTF-8:

  LC_NUMERIC=de_DE.UTF-8
  < 1>
  <   100>
  < 1.000>
  <10.000>
  <   100.000>
  < 1.000.000>
  <10.000.000>
  LC_NUMERIC=en_US.UTF-8
  < 1>
  <   100>
  < 1,000>
  <10,000>
  <   100,000>
  < 1,000,000>
  <10,000,000>

  However, for LC_NUMERIC=nb_NO.UTF-8 and LC_NUMERIC=nn_NO.UTF-8, the
  formatting

[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Bug Watch Updater]

** Changed in: ipykernel (Debian)
   Status: New => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Confirmed
Status in cython-legacy package in Debian:
  New
Status in ipykernel package in Debian:
  Fix Released
Status in jupyter-client package in Debian:
  Confirmed
Status in numpy package in Debian:
  Fix Released
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Fix Released
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

[Bug Watch Updater]

** Changed in: mesa
   Status: New => Fix Released

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Bug Watch Updater]

** Changed in: numpy (Debian)
   Status: New => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Confirmed
Status in cython-legacy package in Debian:
  New
Status in ipykernel package in Debian:
  New
Status in jupyter-client package in Debian:
  Confirmed
Status in numpy package in Debian:
  Fix Released
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Fix Released
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection
   Status: New => Fix Released

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  New

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

[Bug Watch Updater]

** Changed in: evolution-ews
   Status: New => Fix Released

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  Fix Released
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  Earlier I could add outlook.com to gnome calendar with exchange in
  Gnome online accounts and evolution-ews installed, now Microsoft has
  changed something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

  edit 10.3.24: upgraded to Ubuntu 23.10 and it still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+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 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

[Bug Watch Updater]

** Changed in: mesa (Debian)
   Status: Unknown => Confirmed

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

** Changed in: gst-python1.0 (Debian)
   Status: Unknown => Confirmed

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  New
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Confirmed

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2057836] Re: gst-python1.0 fails to build: test failures

[Bug Watch Updater]

** Changed in: pygobject
   Status: Unknown => New

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  New
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Unknown

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Bug Watch Updater]

** Changed in: rich (Debian)
   Status: Confirmed => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Confirmed
Status in cython-legacy package in Debian:
  New
Status in ipykernel package in Debian:
  New
Status in jupyter-client package in Debian:
  Confirmed
Status in numpy package in Debian:
  New
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Fix Released
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection (Debian)
   Status: Unknown => New

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  New
Status in gobject-introspection package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gobject-introspection package in Debian:
  New

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

[Bug Watch Updater]

** Changed in: gobject-introspection
   Status: Unknown => New

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  New
Status in gobject-introspection package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gobject-introspection package in Debian:
  Unknown

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2054924] Re: color emoji are broken with fontconfig 2.15

[Bug Watch Updater]

** Changed in: fontconfig (Debian)
   Status: Confirmed => Fix Released

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Fix Released

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

[Bug Watch Updater]

** Changed in: evolution-ews
   Status: Fix Released => New

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

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

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  Earlier I could add outlook.com to gnome calendar with exchange in
  Gnome online accounts and evolution-ews installed, now Microsoft has
  changed something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

  edit 10.3.24: upgraded to Ubuntu 23.10 and it still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+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 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

[Bug Watch Updater]

** Changed in: evolution-ews
   Status: Unknown => Fix Released

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  Fix Released
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  
  Earlier I could add outlook.com to gnome calendar with exchange in Gnome 
online accounts and evolution-ews installed, now Microsoft has changed 
something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Bug Watch Updater]

** Changed in: upower
   Status: Fix Released => New

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Bug Watch Updater]

** Changed in: gst-plugins-good
   Status: Unknown => New

** Changed in: pipewire
   Status: Unknown => Fix Released

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

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  New
Status in PipeWire:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I hoped that Pulseaudio 17 would be included in Debian in time for
  integration into Ubuntu 24.04-LTS, but apparently not much maintenance
  of pulseaudio is happening on the Debian side at the moment.

  Given that this bug affects all Ubuntu versions since Ubuntu
  22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio
  15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at
  least for the upcoming 24.04-LTS.

  Alternatively it would have been great to get Pulseaudio upgraded to
  version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
  apparently that is too late now, according to
  https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

  Thanks,
  -mario

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+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 1746765] Re: systemd FTBFS on arm64

[Bug Watch Updater]

Launchpad has imported 17 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=22764.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-01-31T12:16:02+00:00 Matthias Klose wrote:

seen with 4.13 and 4.15 kernel builds, works with the 2.29 branch, 
aarch64-linux-gnu.
log at
https://launchpadlibrarian.net/355195922/buildlog_ubuntu-bionic-arm64.linux_4.15.0-6.7_BUILDING.txt.gz

  LD  vmlinux.o
  MODPOST vmlinux.o
ld: arch/arm64/kernel/head.o: relocation R_AARCH64_ABS32 against 
`_kernel_offset_le_lo32' can not be used when making a shared object
ld: arch/arm64/kernel/efi-entry.stub.o: relocation R_AARCH64_ABS32 against 
`__efistub_stext_offset' can not be used when making a shared object
arch/arm64/kernel/head.o: In function `kimage_vaddr':
(.idmap.text+0x0): dangerous relocation: unsupported relocation
arch/arm64/kernel/head.o: In function `__primary_switch':
/<>/arch/arm64/kernel/head.S:772:(.idmap.text+0x340): dangerous 
relocation: unsupported relocation
/<>/arch/arm64/kernel/head.S:772:(.idmap.text+0x348): dangerous 
relocation: unsupported relocation
/<>/Makefile:1026: recipe for target 'vmlinux' failed
make[2]: *** [vmlinux] Error 1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1746765/comments/0


On 2018-01-31T12:24:37+00:00 Ard Biesheuvel wrote:

The arm64 Linux kernel uses absolute ELF symbols to expose various build
time constants whose values are only known after linking to the program
itself.

The size of the loadable image in little endian format (even on BE builds)
The memory footprint of the image in LE
The offset to and size of the RELA section, relative to the start of the image 
(on KASLR kernels)

 A _kernel_flags_le_hi32
000a A _kernel_flags_le_lo32
 A _kernel_offset_le_hi32
0008 A _kernel_offset_le_lo32
 A _kernel_size_le_hi32
013b5000 A _kernel_size_le_lo32
004afa00 A __pecoff_data_rawsize
0051d000 A __pecoff_data_size
0200 A PECOFF_FILE_ALIGNMENT
00fa3898 A __rela_offset
002e2ab0 A __rela_size

The KASLR kernel is a PIE executable, and is no longer allowed to refer
to these symbols via R_AARCH64_ABS32 relocations, resulting in the build
error reported by Matthias.

So please explain how a PIE executable should refer to such absolute ELF
symbols if not via R_AARCH64_ABS32 relocations.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1746765/comments/1


On 2018-01-31T12:58:17+00:00 Ard Biesheuvel wrote:

>From commit 79e741920446582bd0e09f3e2b9f899c258efa56

R_AARCH64_ABS64 under LP64 is allowed in shared object and a dynamic 
relocation entry
will be generated. This allows the dynamic linker to do further symbol 
resolution.
R_AARCH64_ABS32 likewise is allowed in shared object, however under ILP32 
abi.

The original behavior for R_AARCH64_ABS32 under LP64 is that, it's allowed
in shared object and silently resolved at static linking time.
No dynamic relocation entry is generate for it.

One could argue that absolute relocations against *absolute* ELF symbols
should always be resolved at static link time, but I am aware that, for
historical reasons, symbols like __GLOBAL_OFFSET_TABLE__ are emitted as
absolute, making this difficult to realise in practice.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1746765/comments/2


On 2018-01-31T13:08:16+00:00 Hjl-tools wrote:

(In reply to Ard Biesheuvel from comment #2)
> 
> One could argue that absolute relocations against *absolute* ELF symbols
> should always be resolved at static link time, but I am aware that, for
> historical reasons, symbols like __GLOBAL_OFFSET_TABLE__ are emitted as
> absolute, making this difficult to realise in practice.

Not true on x86:

  3987: 003dd000 0 OBJECT  LOCAL  DEFAULT   33
_GLOBAL_OFFSET_TABLE_

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1746765/comments/3


On 2018-01-31T13:11:21+00:00 Ard Biesheuvel wrote:

(In reply to H.J. Lu from comment #3)
> (In reply to Ard Biesheuvel from comment #2)
> > 
> > One could argue that absolute relocations against *absolute* ELF symbols
> > should always be resolved at static link time, but I am aware that, for
> > historical reasons, symbols like __GLOBAL_OFFSET_TABLE__ are emitted as
> > absolute, making this difficult to realise in practice.
> 
> Not true on x86:
> 

[Touch-packages] [Bug 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian

[Bug Watch Updater]

** Changed in: rsyslog
   Status: Confirmed => Fix Released

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

Title:
  Merge rsyslog 8.2312.0-2 from Debian

Status in Rsyslog:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  Debian has released rsyslog 8.2310.0-4. Merge it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsyslog/+bug/2045033/+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 2054924] Re: color emoji are broken with fontconfig 2.15

[Bug Watch Updater]

** Changed in: fontconfig (Debian)
   Status: New => Confirmed

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Confirmed

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2052318] Re: pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13

[Bug Watch Updater]

** Changed in: pycountry (Debian)
   Status: New => Fix Released

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

Title:
  pycountry: FTBFS: dh_auto_test: error: pybuild --test -i
  python{version} -p "3.12 3.11" returned exit code 13

Status in iso-codes package in Ubuntu:
  Fix Released
Status in pycountry package in Ubuntu:
  Fix Released
Status in pycountry package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1060934:

  Source: pycountry
  Version: 23.12.11+ds1-1
  Severity: serious
  Justification: FTBFS
  Tags: trixie sid ftbfs
  User: lu...@debian.org
  Usertags: ftbfs-20240115 ftbfs-trixie

  Hi,

  During a rebuild of all packages in sid, your package failed to build
  on amd64.

  
  Relevant part (hopefully):
  > make[1]: Entering directory '/<>'
  > # The data provided by the iso-codes package is not within this
  > # source package; reassemble the sources
  > # poetry insists on real files not strange out-of-module symlinks when
  > # building, but we want to end up with symlinks back to iso-codes
  > # in the package
  > echo "# AUTOGENERATED FROM d/rules" >> debian/links
  > # json databases
  > mkdir -p src/pycountry/databases
  > for f in /usr/share/iso-codes/json/iso*; do \
  >   src="$f"; \
  >   part=`echo "$f" | sed s@/usr/share/iso-codes/json/@@ | tr -d _`; \
  >   srcdest=src/pycountry/databases/"$part"; \
  >   debdest=usr/lib/python3/dist-packages/pycountry/databases/"$part"; \
  >   cp "$src" "$srcdest"; \
  >   echo "$src" "$debdest" >> debian/links; \
  > done
  > # locales data
  > mkdir -p src/pycountry/locales
  > dpkg -L iso-codes | \
  >   grep /usr/share/locale/ | \
  >   xargs dirname | \
  >   uniq | \
  >   sed "s@/usr/share/locale/@@" | \
  >   xargs -I{} -n1 mkdir -p src/pycountry/locales/{}
  > for f in `dpkg -L iso-codes | grep /usr/share/locale/`; do \
  >   if [ -f "$f" ]; then \
  > src="$f"; \
  > part=`echo "$f" | sed "s@/usr/share/locale/@@;s@iso_@iso@"`; \
  > srcdest=src/pycountry/locales/"$part"; \
  > debdest=/usr/lib/python3/dist-packages/pycountry/locales/"$part"; \
  > cp "$src" "$srcdest"; \
  > echo "$src" "$debdest" >> debian/links; \
  >   fi; \
  > done
  > echo "RECONSTRUCTED PACKAGE:"
  > RECONSTRUCTED PACKAGE:
  > find src/pycountry
  > src/pycountry
  > src/pycountry/db.py
  > src/pycountry/__init__.py
  > src/pycountry/tests
  > src/pycountry/tests/test_general.py
  > src/pycountry/databases
  > src/pycountry/databases/iso3166-2.json
  > src/pycountry/databases/iso15924.json
  > src/pycountry/databases/iso3166-1.json
  > src/pycountry/databases/iso639-5.json
  > src/pycountry/databases/iso639-3.json
  > src/pycountry/databases/iso3166-3.json
  > src/pycountry/databases/iso639-2.json
  > src/pycountry/databases/iso4217.json
  > src/pycountry/py.typed
  > src/pycountry/locales
  > src/pycountry/locales/wa
  > src/pycountry/locales/wa/LC_MESSAGES
  > src/pycountry/locales/wa/LC_MESSAGES/iso3166-1.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso3166.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso639-2.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso3166-2.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso639-3.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso639.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso3166-3.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso639_3.mo
  > src/pycountry/locales/wa/LC_MESSAGES/iso3166_2.mo
  > src/pycountry/locales/chr
  > src/pycountry/locales/chr/LC_MESSAGES
  > src/pycountry/locales/chr/LC_MESSAGES/iso3166-1.mo
  > src/pycountry/locales/chr/LC_MESSAGES/iso3166.mo
  > src/pycountry/locales/gv
  > src/pycountry/locales/gv/LC_MESSAGES
  > src/pycountry/locales/gv/LC_MESSAGES/iso3166-1.mo
  > src/pycountry/locales/gv/LC_MESSAGES/iso3166.mo
  > src/pycountry/locales/en
  > src/pycountry/locales/en/LC_MESSAGES
  > src/pycountry/locales/en/LC_MESSAGES/iso3166-2.mo
  > src/pycountry/locales/en/LC_MESSAGES/iso3166_2.mo
  > src/pycountry/locales/ka
  > src/pycountry/locales/ka/LC_MESSAGES
  > src/pycountry/locales/ka/LC_MESSAGES/iso3166-1.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso4217.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso639-5.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso3166.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso639-2.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso3166-2.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso639-3.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso639.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso639_5.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso15924.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso3166-3.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso639_3.mo
  > src/pycountry/locales/ka/LC_MESSAGES/iso3166_2.mo
  > src/pycountry/locales/tt@iqtelif
  > src/pycountry/locales/tt@iqtelif/LC_MESSAGES
  > src/pycountry/locales/tt@iqtelif/LC_MESSAGES/iso3166-1.mo
  > src/py