[Bug 2008441] Re: 389 Directory Server Manager not show even cockpit-389-ds is installed
After discussion with SRU sponsors, it was recommended that the missing files be built during the build process. This latest debdiff does that, instead of including pre-built files in the debian/ directory ** Patch added: "lp2008441.debdiff" https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+attachment/5821849/+files/lp2008441.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2008441 Title: 389 Directory Server Manager not show even cockpit-389-ds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945661] Re: openstack commands fail with GTK3 error
Updated debdiff based on feedback in comment #17
** Patch added: "lp1945661.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cmd2/+bug/1945661/+attachment/5821791/+files/lp1945661.debdiff
** Description changed:
[ Impact ]
- * There is a bug in cmd2 v0.8.5 where an exception is thrown when GTK3
-libraries are not installed. This causes Python applications using
-cmd2 to crash unexpectedly
+ * There is a bug in cmd2 v0.8.5 where an exception is thrown when GTK3
+ libraries are not installed. This causes Python applications using
+ cmd2 to crash unexpectedly
- * This patch backports a fix from upstream that handles that expection
-gracefully, allowing applications to function properly.
+ * This patch backports a fix from upstream that handles that expection
+ gracefully, allowing applications to function properly.
- * The workaround to this was to install GTK3, which is not ideal as the
-Python applications are command line tools, not graphical
+ * The workaround to this was to install GTK3, which is not ideal as the
+ Python applications are command line tools, not graphical
[ Test Plan ]
- * Deploy focal
+ * Deploy focal
- * Install an application that has cmd2 as a dependency
-e.g. python3-openstackclient
+ * Install an application that has cmd2 as a dependency
+ e.g. python3-openstackclient
- * Run command that uses cmd2: `openstack server list`
+ * Run command that uses cmd2: `openstack server list`
+
+ * In the failing case, we would expect to see an uncaught ValueError
exception
+
+ * In the successful case, the command runs as anticipated
[ Where problems could occur ]
- * This changes the error handling for a library that is used by many
-Python applications. Some of these applications could rely on the
-existing behavior (a ValueError exception being thrown) to detect
-certain configurations and change their behavior accordingly.
+ * This changes the error handling for a library that is used by many
+ Python applications. Some of these applications could rely on the
+ existing behavior (a ValueError exception being thrown) to detect
+ certain configurations and change their behavior accordingly.
- * This would result in those applications failing under certain use
-cases. For example, the configuration in question is a headless
-Linux system without GTK libraries installed.
+ * This would result in those applications failing under certain use
+ cases. For example, the configuration in question is a headless
+ Linux system without GTK libraries installed.
[ Original bug description ]
Openstack release: Wallaby
OS: Ubuntu 20.04 server edition
After installation of python3-openstackclient from apt, while setting up
user, roles and project, I executed following command:
openstack domain create --description "An Example Domain" example
Error:
Traceback (most recent call last):
- File "/usr/bin/openstack", line 6, in
- from openstackclient.shell import main
- File "/usr/lib/python3/dist-packages/openstackclient/shell.py", line 23, in
- from osc_lib import shell
- File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 24, in
- from cliff import app
- File "/usr/lib/python3/dist-packages/cliff/app.py", line 22, in
- import cmd2
- File "/usr/lib/python3/dist-packages/cmd2.py", line 585, in
- _ = pyperclip.paste()
- File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 667, in
lazy_load_stub_paste
- copy, paste = determine_clipboard()
- File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 558, in
determine_clipboard
- return init_gi_clipboard()
- File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 167, in
init_gi_clipboard
- gi.require_version('Gtk', '3.0')
- File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
- raise ValueError('Namespace %s not available' % namespace)
+ File "/usr/bin/openstack", line 6, in
+ from openstackclient.shell import main
+ File "/usr/lib/python3/dist-packages/openstackclient/shell.py", line 23, in
+ from osc_lib import shell
+ File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 24, in
+ from cliff import app
+ File "/usr/lib/python3/dist-packages/cliff/app.py", line 22, in
+ import cmd2
+ File "/usr/lib/python3/dist-packages/cmd2.py", line 585, in
+ _ = pyperclip.paste()
+ File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 667, in
lazy_load_stub_paste
+ copy, paste = determine_clipboard()
+ File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 558, in
determine_clipboard
+ return init_gi_clipboard()
+ File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 167, in
init_gi_clipboard
+ gi.require_version('Gtk', '3.0')
+ File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129,
[Bug 2081646] [NEW] gnome-shell 47.0 crashed if screen keyboard enabled when login
Public bug reported: Hello, The gnome-shell keeps crash after installing gnome-shell 47.0-1ubuntu2, after searching on google, it is because I enabled screen keyboard on gdm login interface, and the upstream bug is: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7912 there is a patch for this bug, would you please backport it after it is merged upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3476 A workaround is disable the screen keyboard: *) First check if the screen-keyboard-enabled is enabled: $ sudo -u gdm gsettings get org.gnome.desktop.a11y.applications screen-keyboard-enabled true *) If the result is true, then disable it with command: $ sudo -u gdm dbus-run-session gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled false *) Then restart the gdm service: sudo systemctl restart gdm Affected gnome-shell version: ii gnome-shell 47.0-1ubuntu2 amd64 Thanks, Tom ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081646 Title: gnome-shell 47.0 crashed if screen keyboard enabled when login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2081646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081310] [NEW] TypeError on launching gnome-passwordsafe
Public bug reported: When trying to launch gnome-passwordsafe I get the following traceback: Traceback (most recent call last): File "/usr/bin/gnome-passwordsafe", line 47, in from passwordsafe.application import Application File "/usr/lib/python3/dist-packages/passwordsafe/application.py", line 12, in from passwordsafe.main_window import MainWindow File "/usr/lib/python3/dist-packages/passwordsafe/main_window.py", line 12, in from passwordsafe.create_database import CreateDatabase File "/usr/lib/python3/dist-packages/passwordsafe/create_database.py", line 8, in from passwordsafe.unlock_database import KeyFileFilter, UnlockDatabase File "/usr/lib/python3/dist-packages/passwordsafe/unlock_database.py", line 13, in from pykeepass.exceptions import ( File "/usr/lib/python3/dist-packages/pykeepass/__init__.py", line 2, in from .pykeepass import PyKeePass, create_database File "/usr/lib/python3/dist-packages/pykeepass/pykeepass.py", line 23, in from pykeepass.kdbx_parsing.kdbx import KDBX File "/usr/lib/python3/dist-packages/pykeepass/kdbx_parsing/__init__.py", line 1, in from .kdbx import KDBX File "/usr/lib/python3/dist-packages/pykeepass/kdbx_parsing/kdbx.py", line 2, in from .kdbx3 import DynamicHeader as DynamicHeader3 File "/usr/lib/python3/dist-packages/pykeepass/kdbx_parsing/kdbx3.py", line 10, in from .common import ( File "/usr/lib/python3/dist-packages/pykeepass/kdbx_parsing/common.py", line 376, in CipherId = Mapping( TypeError: Mapping.__init__() missing 1 required positional argument: 'encoding' ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-passwordsafe 5.1-2 ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 15:57:15 2024 InstallationDate: Installed on 2022-09-05 (746 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-passwordsafe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-passwordsafe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081310 Title: TypeError on launching gnome-passwordsafe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-passwordsafe/+bug/2081310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
Hello, would it be possible to get https://github.com/latchset/mod_auth_mellon/commit/c6102de6ff651bf763400cb59202d9abe384f615 applied to jammy for libapache2-mod-auth-mellon? This is causing problems for saml integration in the apache2 charm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945774 Title: openssl: breaks ssl-cert installation: 8022CB35777F:error:127A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom To manage notifications about this bug go to: https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056735] Re: docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked'
Hello, Looks the root cause of this bug is python3-docker, not in the docker-compose, and its issue is tracking in bug: https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2065348 I'm setting this bug as Invalid. Thanks, Tom Zhou ** Changed in: docker-compose (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056735 Title: docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/2056735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079912] [NEW] package mysql-server-8.0 8.0.39-0ubuntu0.24.04.2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: Error ocurred during sudo apt upgrade No LSB modules are available. Description:Ubuntu 24.04.1 LTS Release:24.04 apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Package DistroRelease: Ubuntu 24.04 Package: mysql-server-8.0 8.0.39-0ubuntu0.24.04.2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Sep 8 03:41:35 2024 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-07-25 (45 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: my.cnf links to /etc/mysql/mysql.cnf MySQLVarLibDirListing: ['#ib_16384_0.dblwr', '#innodb_temp', 'debian-5.7.flag', 'binlog.10', 'binlog.08', 'sys', 'auto.cnf', 'binlog.07', 'ib_buffer_pool', 'client-key.pem', 'binlog.index', 'undo_001', 'binlog.02', 'server-key.pem', 'undo_002', 'binlog.06', 'binlog.04', 'public_key.pem', '#innodb_redo', 'mysql.ibd', '#ib_16384_1.dblwr', 'ca.pem', 'binlog.05', 'private_key.pem', 'ibdata1', 'mysql', 'binlog.09', 'binlog.01', 'ca-key.pem', 'client-cert.pem', 'performance_schema', 'binlog.03', 'server-cert.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic root=UUID=4d972606-cab2-4918-ad9e-a9f67bd41cbc ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079912 Title: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2079912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064694] Re: Can't install ksmbd-tools package on Ubuntu 24.04
More information, after some input. It appears that the 3.5.1-1 ksmbd-tools package does not install cleanly on top of an older version, nor does the fixed 3.5.2-3. But after removing *and purging* the existing package (Jammy), the 3.5.2-3 package from Oracular installs cleanly and completely, with configuration files in /etc/ksmbd not /usr/local/etc/. Also because the location and filename of the config file have changed, it's necessary to move it by hand currently. So for an existing Jammy installation or failed upgrade: cp /etc/smb/smb.conf ./ksmbd.conf dpkg --purge ksmbd-tools wget https://launchpad.net/ubuntu/oracular/+package/ksmbd-tools> dpkg --install ./ksmbd-tools- cp ./ksmbd.conf /etc/ksmbd For a new installation, all should be good, or at least, it was for me after the purge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064694 Title: Can't install ksmbd-tools package on Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksmbd-tools/+bug/2064694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064694] Re: Can't install ksmbd-tools package on Ubuntu 24.04
I installed the 3.5.2-3 ksmbd-tools from Oracular and while it installs, it shows the same issue as Bernard saw - it expects the ksmbd.conf in /usr/local/etc/ksmbd, instead of /etc/ksmbd. Also, it doesn't install the sample conf file, and since the name and some of the options have changed since Jammy, this may lead to even more confusion. Strangely, the installed manpage refers to /etc/ksmbd too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064694 Title: Can't install ksmbd-tools package on Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksmbd-tools/+bug/2064694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019247] Re: perf should be compiled with libtraceevent
*** This bug is a duplicate of bug 2076190 *** https://bugs.launchpad.net/bugs/2076190 ** This bug has been marked a duplicate of bug 2076190 perf build disables tracepoint support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2019247 Title: perf should be compiled with libtraceevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077241] Re: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Maybe it was not a bug. Maybe it was just a bad apt package that had to be removed before the lamp-server could be installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077241 Title: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2077241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077241] [NEW] package mysql-server-8.0 8.0.39-0ubuntu0.24.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: Errors were encountered while processing: mysql-server-8.0 mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 24.04 Package: mysql-server-8.0 8.0.39-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Aug 17 12:49:34 2024 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-07-25 (23 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: my.cnf links to /etc/mysql/mysql.cnf MySQLVarLibDirListing: ['#ib_16384_0.dblwr', '#innodb_temp', 'debian-5.7.flag', 'sys', 'auto.cnf', 'ib_buffer_pool', 'client-key.pem', 'binlog.index', 'undo_001', 'binlog.02', 'server-key.pem', 'undo_002', 'public_key.pem', '#innodb_redo', 'mysql.ibd', '#ib_16384_1.dblwr', 'ca.pem', 'private_key.pem', 'ibdata1', 'mysql', 'binlog.01', 'ca-key.pem', 'client-cert.pem', 'performance_schema', 'server-cert.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic root=UUID=4d972606-cab2-4918-ad9e-a9f67bd41cbc ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077241 Title: package mysql-server-8.0 8.0.39-0ubuntu0.24.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2077241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945661] Re: openstack commands fail with GTK3 error
** Description changed:
+ [ Impact ]
+
+ * There is a bug in cmd2 v0.8.5 where an exception is thrown when GTK3
+libraries are not installed. This causes Python applications using
+cmd2 to crash unexpectedly
+
+ * This patch backports a fix from upstream that handles that expection
+gracefully, allowing applications to function properly.
+
+ * The workaround to this was to install GTK3, which is not ideal as the
+Python applications are command line tools, not graphical
+
+ [ Test Plan ]
+
+ * Deploy focal
+
+ * Install an application that has cmd2 as a dependency
+e.g. python3-openstackclient
+
+ * Run command that uses cmd2: `openstack server list`
+
+ [ Where problems could occur ]
+
+ * This changes the error handling for a library that is used by many
+Python applications. Some of these applications could rely on the
+existing behavior (a ValueError exception being thrown) to detect
+certain configurations and change their behavior accordingly.
+
+ * This would result in those applications failing under certain use
+cases. For example, the configuration in question is a headless
+Linux system without GTK libraries installed.
+
+ [ Original bug description ]
+
Openstack release: Wallaby
OS: Ubuntu 20.04 server edition
- After installation of python3-openstackclient from apt, while setting up
user, roles and project, I executed following command:
+ After installation of python3-openstackclient from apt, while setting up
user, roles and project, I executed following command:
openstack domain create --description "An Example Domain" example
- Error:
+ Error:
Traceback (most recent call last):
File "/usr/bin/openstack", line 6, in
from openstackclient.shell import main
File "/usr/lib/python3/dist-packages/openstackclient/shell.py", line 23, in
from osc_lib import shell
File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 24, in
from cliff import app
File "/usr/lib/python3/dist-packages/cliff/app.py", line 22, in
import cmd2
File "/usr/lib/python3/dist-packages/cmd2.py", line 585, in
_ = pyperclip.paste()
File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 667, in
lazy_load_stub_paste
copy, paste = determine_clipboard()
File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 558, in
determine_clipboard
return init_gi_clipboard()
File "/usr/lib/python3/dist-packages/pyperclip/__init__.py", line 167, in
init_gi_clipboard
gi.require_version('Gtk', '3.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in
require_version
raise ValueError('Namespace %s not available' % namespace)
Had to install GTK3 to make openstack commands work but it is taking
huge time to get a response to the commands. The wait time after firing
any openstack cli command is around 30 seconds.
Anybody faced the issue? What is the fix for it if it exists?
** Patch added: "lp1945661.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cmd2/+bug/1945661/+attachment/5801946/+files/lp1945661.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945661
Title:
openstack commands fail with GTK3 error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cmd2/+bug/1945661/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945661] Re: openstack commands fail with GTK3 error
** Package changed: python-openstackclient (Ubuntu) => cmd2 (Ubuntu) ** Also affects: cmd2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: cmd2 (Ubuntu Focal) Assignee: (unassigned) => Tom Moyer (tom-tom) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945661 Title: openstack commands fail with GTK3 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmd2/+bug/1945661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073267] Re: Guru meditation on VM start
I have the same setup as Andy (comment #22). Ubuntu 22.04.4 LTS VirtualBox is version installed from Ubuntu repo: virtualbox/jammy-updates,now 6.1.50-dfsg-1~ubuntu1.22.04.1 amd64 [installed] Problem with no longer being able to start any guest OS in VirtualBox first appeared after system update to kernel package: linux-image-5.15.0-116-generic/jammy-updates,jammy-security,now 5.15.0-116.126 amd64 [installed,automatic] Choosing to boot using previous kernel package allows VirtualBox to start guest OSs again without issue. Previous kernel package is: linux-image-5.15.0-113-generic/jammy-updates,jammy-security,now 5.15.0-113.123 amd64 [installed,automatic] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Guru meditation on VM start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073367] [NEW] bug in module cx18
Public bug reported: tv card Hauppauge HVR 1600 not working probably because of this. several array-index-out-of-bounds in dmesg regarding cx18-streams.c and cx18-queue.c ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-38-generic 6.8.0-38.38 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Wed Jul 17 05:48:46 2024 InstallationDate: Installed on 2024-07-12 (5 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 (20240423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 1M MachineType: Dell Inc. Precision 3630 Tower ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic root=UUID=54d1671f-8bdd-443b-9090-b92da043658e ro RelatedPackageVersions: linux-restricted-modules-6.8.0-38-generic N/A linux-backports-modules-6.8.0-38-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2024 dmi.bios.release: 2.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.29.0 dmi.board.name: 0NNNCT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.29.0:bd06/03/2024:br2.29:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0NNNCT:rvrA01:cvnDellInc.:ct3:cvr:sku0871: dmi.product.family: Precision dmi.product.name: Precision 3630 Tower dmi.product.sku: 0871 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073367 Title: bug in module cx18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
I tested 5.15.0-116 on a HP ProDesk 405 G6 Desktop running Mint 20.1 (using linux-hwe for the 5.15 kernel) and 5.15.0-116 resolved the problem. Thanks all :) (Now I just have to wait for it to hit general release so I can update the other 20 or so I'm responsible for ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068738 Title: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063888] Re: 24.04 unusable after Gnome-Tweaks change to the mouse pointer
*** This bug is a duplicate of bug 2062377 *** https://bugs.launchpad.net/bugs/2062377 @aki thanks that was exactly my problem! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063888 Title: 24.04 unusable after Gnome-Tweaks change to the mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072549] [NEW] rpi-imager offers to overwrite in-use second hard drive
Public bug reported: My laptop has two M.2 drives which are part of the same LVM volume group and my root partition is spread across them (as well as some VM partitions). rpi-imager correctly identifies that one of these should not be overwritten and doesn't offer it as a choice when writing an image, but regards the other as available. Needless to say, the consequences of actually doing this would be pretty severe. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rpi-imager 1.8.5+noembed-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Jul 9 10:16:54 2024 InstallationDate: Installed on 2023-12-05 (217 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: rpi-imager UpgradeStatus: Upgraded to noble on 2024-04-28 (72 days ago) ** Affects: rpi-imager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072549 Title: rpi-imager offers to overwrite in-use second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-imager/+bug/2072549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072395] Re: [snap] won't start with desktop-launch not found
I can confirm that after a `snap refresh` I'm at 2897 and things are back to working order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072395 Title: [snap] won't start with desktop-launch not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2072395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072395] [NEW] [snap] won't start with desktop-launch not found
Public bug reported: Today I was prompted to update my chromium snap, so I closed it down and the auto-refresh happened. When I tried to launch it, it did not come up. Running `chromium` from the command line resulted in the following error: $ chromium Content snap command-chain for /snap/chromium/2905/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Browsing the internet, I found people saying that gnome needed to be connected. Running `sudo snap connect chromium:gnome-46-2404 gnome-46-2404:gnome-46-2404` did not fix the problem. I'm not sure it matters for a snap, but this is (very recently updated) ubuntu 22.04 running KDE on x86_64. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072395 Title: [snap] won't start with desktop-launch not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2072395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
I can't confirm whether blacklisting the simpledrm driver fixes this, because it very definitely breaks the system boot. I'm using whole-disk encryption and blacklisting this driver leaves it unable to ask me for the encryption key to unlock the root partition. Presumably there is a way to use the nvidia driver to do this. I'll see if I can figure it out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049315] Re: cups-browsed running non-stop on two cores
> CUPS 2.4.8 got released and the fix https://github.com/OpenPrinting/cups/issues/879 is included. Is this incorporated into 24.04 yet ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049315 Title: cups-browsed running non-stop on two cores To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2008441] Re: 389 Directory Server Manager not show even cockpit-389-ds is installed
** Attachment added: "389-ds-base_2.0.15-1ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+attachment/5790503/+files/389-ds-base_2.0.15-1ubuntu1.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2008441 Title: 389 Directory Server Manager not show even cockpit-389-ds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2008441] Re: 389 Directory Server Manager not show even cockpit-389-ds is installed
** Attachment added: "389-ds-base_2.0.15.orig.tar.gz" https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+attachment/5790502/+files/389-ds-base_2.0.15.orig.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2008441 Title: 389 Directory Server Manager not show even cockpit-389-ds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2008441] Re: 389 Directory Server Manager not show even cockpit-389-ds is installed
I have updated the 2.0.15 source package to include the necessary UI files. These are not included as part of the upstream archive, and instead are built during the release process. As such, I created a release archive in a clean LXD container and extracted the necessary files. As these are binary files, I am including the entire source package here instead of a diff. ** Description changed: [ Impact ] - It is expected that there will be minimal impact by updating the package - from 2.0.15 to 2.0.16. I have reviewed the upstream commits between the - two versions and the only commits are ones that close upstream bugs. No - new features are included and no functionality is changed. The biggest - difference between 2.0.15 and 2.0.16 is the inclusion of the missing - files for cockpit-389-ds. Version 2.0.15 ships an empty package for - cockpit-389-ds which causes the plugin to be non-functional. + It is expected that there will be minimal impact by this SRU. The only + things that were added to the package were the missing Cockpit plugin + files (in debian/cockpit_dist) and adding a line to debian/rules to copy + those files into the correct location during the package build process. + No other files outside of these were touched by this SRU. [ Test Plan ] 1. Install the following packages on a fresh installation of Jammy - - 389-ds - - cockpit - - cockpit-389-ds + - 389-ds + - cockpit + - cockpit-389-ds 2. Ensure that cockpit is enabled and listening on port 9090 3. Open a browser and connect to the system on port 9090 4. Login to the cockpit web application 5. Verify that the menu on the left includes the 389 Directory Server link 6. Click the link and use the plugin to create a new instance of 389-ds [ Where problems could occur ] While issues are unlikely, there are a number of places where bug fixes include minor changes to the cockpit UI. If users rely on scripts for automated testing/automation (e.g. selenium), these changes could cause those tests/automations could break. [ Other Info ] - * This change only applies to jammy as releases after jammy have a newer -version of 389-ds-base that includes the missing files + * This change only applies to jammy as releases after jammy have a newer + version of 389-ds-base that includes the missing files [ Original Bug Description ] In 22.04 LTS, cockpit-389-ds will also install when install 389-ds ``` # apt info 389-ds Package: 389-ds Version: 2.0.15-1 Priority: optional Section: universe/net Source: 389-ds-base Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian FreeIPA Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 49.2 kB Depends: 389-ds-base, cockpit-389-ds Homepage: https://directory.fedoraproject.org Download-Size: 10.8 kB APT-Manual-Installed: yes APT-Sources: http://azure.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Description: 389 Directory Server suite - metapackage - Based on the Lightweight Directory Access Protocol (LDAP), the 389 - Directory Server is designed to manage large directories of users and - resources robustly and scalably. - . - This is a metapackage depending on the LDAPv3 server and a Cockpit UI plugin - for administration. + Based on the Lightweight Directory Access Protocol (LDAP), the 389 + Directory Server is designed to manage large directories of users and + resources robustly and scalably. + . + This is a metapackage depending on the LDAPv3 server and a Cockpit UI plugin + for administration. ``` After cockpit-389-ds install, 389 Directory Server suppose could be administrated via Cockpit but "389 Directory Server" does not shown after login Cockpit. After check the files installed via cockpit-389-ds, it seems missing some files inside /usr/share/cockpit/389-console such as /usr/share/cockpit/389-console/manifest.json, /usr/share/cockpit/389-console/index.html, etc. ``` # dpkg --listfiles cockpit-389-ds /. /usr /usr/share /usr/share/cockpit /usr/share/cockpit/389-console /usr/share/doc /usr/share/doc/cockpit-389-ds /usr/share/doc/cockpit-389-ds/copyright /usr/share/metainfo /usr/share/metainfo/389-console /usr/share/metainfo/389-console/org.port389.cockpit_console.metainfo.xml /usr/share/doc/cockpit-389-ds/changelog.Debian.gz ``` Thank you for your time! ** Attachment added: "389-ds-base_2.0.15-1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+attachment/5790501/+files/389-ds-base_2.0.15-1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2008441 Title: 389 Directory Server Manager not show even cockpit-389-ds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-b
[Bug 1673247] Re: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1
This still happens ? Unpacking snapd (2.63+24.04) over (2.62+24.04build1) ... Setting up snapd (2.63+24.04) ... Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ... snapd.failure.service is a disabled or a static unit not running, not starting it. snapd.snap-repair.service is a disabled or a static unit not running, not starting it. Failed to restart snapd.mounts-pre.target: Operation refused, unit snapd.mounts-pre.target may be requested by dependency only (it is configured to refuse manual start/stop). See system logs and 'systemctl status snapd.mounts-pre.target' for details. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Processing triggers for man-db (2.12.0-4build2) ... Processing triggers for dbus (1.14.10-4ubuntu4) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for desktop-file-utils (0.27-2build1) ... Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. falken@frame:~$ systemctl status snapd.mounts-pre.target ● snapd.mounts-pre.target - Mounting snaps Loaded: loaded (/usr/lib/systemd/system/snapd.mounts-pre.target; static) Active: active since Sun 2024-06-16 14:29:38 BST; 1h 14min ago Notice: journal has been rotated since unit was started, output may be incomplete. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu 24.04 LTS" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673247 Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1673247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
I've managed to recover my system to the point that snap is working again - see #2068874 - but won't get a chance to test this just now. Yes, drm_info reports card0 as simpledrm and card1 as nvidia-drm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
Also trying to set the kernel commandline with `sudo snap set system system.kernel.cmdline-append` appears to have crashed snapd. Quite what state that's left my system in is anyone's guess. It _might_ be bootable... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
I'm uncertain how to tell if I'm affected by that bug. I'm not seeing the main symptom - a "phantom" display in settings. But I'm only running Nvidia drivers version 535, so possibly that symptom doesn't show up until you install 545? I do have a /dev/card0 which is from the simple-framebuffer module. I'll try adding the initcall_blacklist but I don't think it'll do anything; AFAICT there is no simpledrm driver on the system, only simple-framebuffer, and I thought that module init methods and to match the name of the module? Or maybe not when it's not loaded as a module, IDK (and simple-framebuffer appears to be compiled-in on this system). I saw the crash again this morning and again there are no crash files in /var/crash - the most recent was three days ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
And the only whoopsie link is from January, ie before the upgrade to 24.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
I'm not locking the screen while in the overview. This happened this morning and I'm not absolutely sure that I'd had Satisfactory running beforehand. I've uploaded the journal files from this crash above. The crash this morning produced crash files from chrome and vscode but I don't think these are a symptom rather than the cause; previous crashes have not produced these. There is a crash file for /usr/lib/xorg/Xorg but `ubuntu-bug --save bug.txt /var/crash/_usr_lib_xorg_Xorg.1000.crash` produces an empty file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+attachment/5787097/+files/prevjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
Attaching journal.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+attachment/5787096/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] [NEW] Screen lock crashes after playing fullscreen games
Public bug reported: This appears to be new after an upgrade to 24.04. My laptop has a 2560x1600 panel. When I play a fullscreen Steam game (in this case Satisfactory) set to that resolution, afterwards the virtual display size in GNOME is increased, so that if I move the mouse off the bottom or right-hand sides of the screen then the desktop scrolls. The GNOME shell has not resized and the extra virtual space is just grey. If I then suspend the system by shutting the lid and then unsuspend it again, the lock screen does not appear and I get a brief glimpse of the screen content before the "Something went wrong" screen and a forced log off. After logging off, everything is okay again. I am using the Xorg display session. This only happens after playing the game and therefore when the virtual display size is increased. My guess is that GNOME Shell is not handling the mismatched display sizes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Jun 6 08:39:09 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-12-05 (184 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-28 (39 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059352] Re: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures
** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059352 Title: paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2059352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066098] [NEW] release upgrade doesn't work, way to many "Broken" to make sense of
Public bug reported: I've removed all packages not originating from ubuntu.com; there were still hundreds of "Broken" packages listed. I've removed a lot of them, but there's also a bunch of "essentials" like ubuntu-desktop, gnome- shell, gnome-settings-daemon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.41 ProcVersionSignature: Ubuntu 5.4.0-182.202-generic 5.4.269 Uname: Linux 5.4.0-182-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Sun May 19 01:03:48 2024 InstallationDate: Installed on 2019-03-16 (1890 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm-256color PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2024-05-18 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066098 Title: release upgrade doesn't work, way to many "Broken" to make sense of To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2066098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2008441] Re: 389 Directory Server Manager not show even cockpit-389-ds is installed
** Changed in: 389-ds-base (Ubuntu) Assignee: (unassigned) => Tom Moyer (tom-tom) ** Also affects: 389-ds-base (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: + [ Impact ] + + It is expected that there will be minimal impact by updating the package + from 2.0.15 to 2.0.16. I have reviewed the upstream commits between the + two versions and the only commits are ones that close upstream bugs. No + new features are included and no functionality is changed. The biggest + difference between 2.0.15 and 2.0.16 is the inclusion of the missing + files for cockpit-389-ds. Version 2.0.15 ships an empty package for + cockpit-389-ds which causes the plugin to be non-functional. + + [ Test Plan ] + + 1. Install the following packages on a fresh installation of Jammy + - 389-ds + - cockpit + - cockpit-389-ds + + 2. Ensure that cockpit is enabled and listening on port 9090 + + 3. Open a browser and connect to the system on port 9090 + + 4. Login to the cockpit web application + + 5. Verify that the menu on the left includes the 389 Directory Server + link + + 6. Click the link and use the plugin to create a new instance of 389-ds + + [ Where problems could occur ] + + While issues are unlikely, there are a number of places where bug fixes + include minor changes to the cockpit UI. If users rely on scripts for + automated testing/automation (e.g. selenium), these changes could cause + those tests/automations could break. + + [ Other Info ] + + * This change only applies to jammy as releases after jammy have a newer +version of 389-ds-base that includes the missing files + + [ Original Bug Description ] + In 22.04 LTS, cockpit-389-ds will also install when install 389-ds ``` # apt info 389-ds Package: 389-ds Version: 2.0.15-1 Priority: optional Section: universe/net Source: 389-ds-base Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian FreeIPA Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 49.2 kB Depends: 389-ds-base, cockpit-389-ds Homepage: https://directory.fedoraproject.org Download-Size: 10.8 kB APT-Manual-Installed: yes APT-Sources: http://azure.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Description: 389 Directory Server suite - metapackage Based on the Lightweight Directory Access Protocol (LDAP), the 389 Directory Server is designed to manage large directories of users and resources robustly and scalably. . This is a metapackage depending on the LDAPv3 server and a Cockpit UI plugin for administration. ``` After cockpit-389-ds install, 389 Directory Server suppose could be administrated via Cockpit but "389 Directory Server" does not shown after login Cockpit. After check the files installed via cockpit-389-ds, it seems missing some files inside /usr/share/cockpit/389-console such as /usr/share/cockpit/389-console/manifest.json, /usr/share/cockpit/389-console/index.html, etc. ``` # dpkg --listfiles cockpit-389-ds /. /usr /usr/share /usr/share/cockpit /usr/share/cockpit/389-console /usr/share/doc /usr/share/doc/cockpit-389-ds /usr/share/doc/cockpit-389-ds/copyright /usr/share/metainfo /usr/share/metainfo/389-console /usr/share/metainfo/389-console/org.port389.cockpit_console.metainfo.xml /usr/share/doc/cockpit-389-ds/changelog.Debian.gz ``` Thank you for your time! ** Patch added: "lp2008441.debdiff" https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+attachment/5776336/+files/lp2008441.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2008441 Title: 389 Directory Server Manager not show even cockpit-389-ds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
This is now a mix of maybe similar seeming, but likely different issues with different root causes, also mixing AMD / Intel GPUs. Anyone but twelfth (OP): Please remember to post separate / new bug reports - not here. To file a bug, use "ubuntu-bug linux" if you expect it to be about a packaged and supported Ubuntu Linux kernel. I think this bug report should be closed unless twelfth can reproduce the issue with a fresh 24.04 install and provide logs as indicated above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
Please reproduce the problem (boot to black screen). Then reboot in a way that you can use the computer and run this without rebooting again: sudo journalctl -k -b -1 > /tmp/kernel.log Then attach /tmp/kernel.log to your bug report. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I think it would be quite helpful if any of you could file separate bug reports of testing a fresh 24.04 install of any flavour and could gather the full kernel log from when the system booted to black screen, with AMD graphics. That's because this can have many different causes, and we do not know the root causes for what you're describing are identical at this point. While obviously what you report is correct and a real issue for each of you, developers need to identify root causes across ideally multiple installations of the same type and in the same or similar environment. However, from a developers' perspective, all we have so far is a few reports of "under some (possibly different) circumstances, an unsupported upgrade to 24.04 resulted into the system booting to a black screen, with some (different models of) AMD graphics. Having seperate reports including logs which *may* (should) point to the root cause would certainly help understanding whether these are isolated corner cases with similar symptoms but different root causes, or whether there really is a generic issue affecting some or many amdgpu driven devices with the 24.04 LTS GA kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056627] Re: PHPStorm crashes when opening a project
Also occurs with https://lmstudio.ai/ which is also AppImage based. I think the feature is broken in general ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056627 Title: PHPStorm crashes when opening a project To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063510] [NEW] "find_java_runtime openjdk" fails to find /usr/lib/jvm/java-21-openjdk-amd64
Public bug reported: # . /usr/lib/java-wrappers/java-wrappers.sh # find_java_runtime openjdk [warning] /bin/bash: No java runtime was found # ls -l /usr/lib/jvm total 4 lrwxrwxrwx 1 root root 25 Oct 4 2023 default-java -> java-1.21.0-openjdk-amd64 lrwxrwxrwx 1 root root 21 Apr 22 19:35 java-1.21.0-openjdk-amd64 -> java-21-openjdk-amd64 drwxr-xr-x 7 root root 4096 Apr 25 15:31 java-21-openjdk-amd64 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: java-wrappers 0.4 Uname: Linux 5.15.146.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudBuildName: ubuntu-oci:minimized CloudSerial: 20240407.1 Date: Thu Apr 25 22:17:36 2024 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) TERM=xterm SourcePackage: java-wrappers UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: java-wrappers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cloud-image noble ** Patch added: "patch to add openjdk21 to jvm-list.sh" https://bugs.launchpad.net/bugs/2063510/+attachment/5770583/+files/jvmlist.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063510 Title: "find_java_runtime openjdk" fails to find /usr/lib/jvm/java-21-openjdk-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-wrappers/+bug/2063510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060766] [NEW] Can't run bpftrace , ERROR: too many arguments
Public bug reported:
```bash
sudo bpftrace test.bt
error: :0:0: in function BEGIN i64 (ptr): 0x5ae8a70ee260: i64 =
GlobalAddress 0 too many arguments
```
```
// test.bt
BEGIN
{
printf("Hello\n");
}
```
`OS: Ubuntu Noble Numbat (development branch) x86_64Linux vmnobel
6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC
2024 x86_64 x86_64 x86_64 GNU/Linux`
```
delta@vmnobel ~> sudo apt info bpftrace
Package: bpftrace
Version: 0.20.2-1ubuntu3
Priority: optional
Section: utils
Origin: Ubuntu
```
** Affects: bpftrace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060766
Title:
Can't run bpftrace , ERROR: too many arguments
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2060766/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059712] [NEW] `perf report` complains about missing tips.txt file
Public bug reported: The `perf` command-line tool expects a tips.txt file at /usr/share/doc/perf-tip/tips.txt, from which it displays random tips in `perf report` mode. If this file is not present (it is not on Ubuntu 22.04 LTS), `perf report` complains, both in interactive and in non- interactive mode, that: > Cannot load tips.txt file, please install perf! Reproduction: $ mkdir tmpdir; cd tmpdir $ perf record ls $ perf report | cat The expected behaviour is that this message is not shown (and a (useful?) tip is shown instead). This has led to bug reports (and fixes) on various other Linux distributions: at least Fedora [1] and Arch [2]. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1448402 [2]: https://bugs.archlinux.org/task/48788 Further info: $ lsb_release -rd Description:Ubuntu 22.04.4 LTS Release:22.04 $ apt-cache policy linux-tools-common | head -5 linux-tools-common: Installed: 5.15.0-101.111 Candidate: 5.15.0-101.111 Version table: *** 5.15.0-101.111 500 $ cat /proc/version_signature Ubuntu 5.15.0-101.111-generic 5.15.143 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059712 Title: `perf report` complains about missing tips.txt file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915226] Re: network-manager continuous inappropriate site surveys
Kroger is conducting a customer satisfaction survey to learn about customers' actual experience during their Kroger store visit. As a token of appreciation from the company, the management is offering 50 fuel points for free to the customers who participated in the survey on the https://kroger-feedback.online/ official site. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915226 Title: network-manager continuous inappropriate site surveys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1915226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052457] Re: libreoffice latest version not detecting my java installation
** Tags added: snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052457 Title: libreoffice latest version not detecting my java installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2052457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 15027] Re: gdm: Suppresses X logging with "Too much output"
This still happens, ex Apr 19 14:34:35 lego.house /usr/libexec/gdm-x-session[3605]: discarding unsupported packet "kdeconnect.mpris" for "Nexus 7" $ journalctl | wc -l 156428 $ journalctl | grep 'discarding unsupported packet' |wc -l 4461 tchiverton@lego:~$ journalctl | grep gdm-x-session| wc -l 7426 And other unrelated and pointless junk, over and over again. All day. Every day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/15027 Title: gdm: Suppresses X logging with "Too much output" To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/15027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977675] [NEW] Bluetooth adapter not found after reboot
Public bug reported: After rebooting my Dell Vostro Vostro-14-5401 running Ubuntu 18.04.5 LTS, the Bluetooth icon disappeared from the icons tray. The settings menu doesn't appear to register any BT device (No Bluetooth Found - Plug in a dongle to use Bluetooth). The command "service Bluetooth status" returns the following: ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: inactive (dead) Condition: start condition failed at Sun 2022-06-05 10:23:15 IDT; 56s ago └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met Docs: man:bluetoothd(8) I did not update or change anything prior to the reboot. Needless to say, I tried to reboot the laptop again, but the device is still not booting. using systemctl to reboot the service (systemctl disable Bluetooth,systemctl enable Bluetooth,systemctl start Bluetooth) does not work either. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bluetooth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977675 Title: Bluetooth adapter not found after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976481] [NEW] ath9k driver takes 100% of CPU since update to 22.04
Public bug reported: Hi all, I recently updated my home server to Ubuntu 22.04, and since then my WiFi access point (ath9k driver) fails after an hour or so. I saw with htop that one of my CPU core is at 100% of the kernel. With perf top I could find it's spending time in the ath9k driver, in ioread32, see the attachment. Looks like an infinite loop or so. It worked very well before the upgrade. Any idea? Thanks, Tom ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm3274 F pulseaudio /dev/snd/controlC1: gdm3274 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Jun 1 10:35:42 2022 InstallationDate: Installed on 2020-08-25 (644 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. N550JV ProcEnviron: LANG=fr_BE.UTF-8 LANGUAGE=fr_BE:fr PATH=(custom, no user) TERM=screen-256color SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=/dev/mapper/lvgroup-system ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-19 (12 days ago) dmi.bios.date: 11/19/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy ** Attachment added: "Capture d’écran 2022-06-01 104143.png" https://bugs.launchpad.net/bugs/1976481/+attachment/5594244/+files/Capture%20d%E2%80%99%C3%A9cran%202022-06-01%20104143.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976481 Title: ath9k driver takes 100% of CPU since update to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975685] [NEW] Wifi hotspot does not work when band A is selected
Public bug reported: I'm using a built-in RTL8822BE WiFi adapter on a Ryzen 7 system. When I create a hotspot by opening the GNOME settings app, opening the WiFi settings page and selecting "Turn on hotspot..." from the drop-down menu, everything works fine. If I then open nm-connection-editor and edit the connection to select band A (5GHz), the hotspot fails to start. If I then open the connection editor again and switch back to automatic band selection, the hotspot works again. When it fails, this appears in syslog: May 25 10:21:30 frog NetworkManager[815]: [1653470490.8638] device (wlo1): Activation: starting connection 'Hotspot' (514f603b-25e2-4c1e-9220-7b77ed966ff5) May 25 10:21:30 frog NetworkManager[815]: [1653470490.8643] device (wlo1): supplicant interface state: completed -> disconnected May 25 10:21:30 frog NetworkManager[815]: [1653470490.8653] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8676] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8783] device (wlo1): Activation: (wifi) access point 'Hotspot' has security, but secrets are required. May 25 10:21:30 frog NetworkManager[815]: [1653470490.8783] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8800] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8810] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8883] device (wlo1): Activation: (wifi) connection 'Hotspot' has security, and secrets exist. No new secrets needed. May 25 10:21:30 frog wpa_supplicant[866]: wlo1: Failed to start AP functionality May 25 10:21:56 frog NetworkManager[815]: [1653470516.1521] device (wlo1): Activation: (wifi) Hotspot network creation took too long, failing activation May 25 10:21:56 frog NetworkManager[815]: [1653470516.1522] device (wlo1): state change: config -> failed (reason 'supplicant-timeout', sys-iface-state: 'managed') May 25 10:21:56 frog NetworkManager[815]: [1653470516.1526] device (wlo1): Activation: failed for connection 'Hotspot' May 25 10:21:56 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all May 25 10:21:56 frog NetworkManager[815]: [1653470516.1530] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') May 25 10:21:56 frog wpa_supplicant[866]: wlo1: Reject scan trigger since one is already pending May 25 10:21:59 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN I'm guessing that NetworkManager is getting the way it drives wpa_supplicant wrong when the 5GHz band is selected, but it's only a guess. Ubuntu version is: tkcook@frog:~$ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 NetworkManager version is: tkcook@frog:~$ apt-cache policy network-manager-gnome network-manager-gnome: Installed: 1.24.0-1ubuntu3 Candidate: 1.24.0-1ubuntu3 Version table: *** 1.24.0-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 Uname: Linux 5.18.0 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 25 10:29:37 2022 InstallationDate: Installed on 2021-08-27 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: network-manager-applet UpgradeStatus: Upgraded to jammy on 2022-05-05 (19 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975685 Title: Wifi hotspot does not work when band A is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
SRU request: Please accept qt6-base 6.2.4+dfsg-8 into jammy. [Impact] 1. QLibraryInfo can return non-existent paths. 2. This results in Qt6 QWebEngine being unusable. [Test Plan] 1. Check the output of qtdiag from qt6-tools-dev-tools, and verify the paths exist. a) Run "qtdiag --no-vulkan --no-rhi --no-gl | grep Path" b) verify that the paths actually exist, in particular DataPath: /share/qt6 does not exist on jammy. 2. Build the Qt supplied simplebrowser example, and verify it launches without error a) apt-get source libqt6webenginecore6 b) cd qt6-webengine-6.2.4+dfsg/examples/webenginewidgets/simplebrowser c) mkdir bld d) cd bld e) cmake -DCMAKE_BUILD_TYPE=Release .. f) cmake --build . g) ./simplebrowser An example of output from a failure is attached as faillog.txt. In particular note the failure to find resources at /share: Qt WebEngine resources not found at /share/qt6/resources. Trying parent directory... Qt WebEngine resources not found at /share/qt6. Trying application directory... and the resulting segmentation fault: Segmentation fault (core dumped) [Where problems could occur] The change in 6.2.4+dfsg-8 restores the configuration settings that were used to build qtbase-opensource-src (5.14.2+dfsg-3) through qtbase- opensource-src (5.15.3+dfsg-2). The setting was lost on the transition from the Qt5 qmake build to the Qt6 cmake build. The change causes QLibraryInfo to use paths known at build time instead of trying to dynamically establish the paths. This will fail if the package is relocated to a different location from that which it is build for. Since the package isn't relocatable this shouldn't be a problem. [Other Info] The change is currently in The Kinetic Kudu (active development). ** Attachment added: "test plan part 2 failure example" https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+attachment/5592341/+files/faillog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973423] [NEW] Remote Desktop Sharing reactivates itself, cannot be permanently disabled (on GUI)
*** This bug is a security vulnerability *** Public security bug reported: On Ubuntu 22.04 with Wayland, once you activate, from the Settings application, Sharing, and Remote Desktop Sharing, it is not possible to permanently deactivate it on the GUI. While it is still possible to deactivate it temporarily, this will only last until next reboot. After a reboot, Remote Desktop Sharing will be active again. This means that a service which provides remote access and system control, which the user has chosen to deactivate, actually remains active / respawns, and available for remote login. This behavior is unexpected to the user and can have security impact. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42.0-4ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 14 16:13:44 2022 InstallationDate: Installed on 2022-05-08 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973423 Title: Remote Desktop Sharing reactivates itself, cannot be permanently disabled (on GUI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1973423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972154] Re: package grub-efi-amd64-signed 1.180(2.06-2ubuntu7 failed to install/upgrade: Installed grub-efi-amd64-signed package post-Installation script subprocess returned error exit status 32
can close, thanks ** Changed in: grub2-signed (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972154 Title: package grub-efi-amd64-signed 1.180(2.06-2ubuntu7 failed to install/upgrade: Installed grub-efi-amd64-signed package post- Installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1972154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972154] Re: package grub-efi-amd64-signed 1.180(2.06-2ubuntu7 failed to install/upgrade: Installed grub-efi-amd64-signed package post-Installation script subprocess returned error exit status 32
After using "Christian Merges (christianmerges)" recommendation and the error gone: My Server is not using efi boot i resolved this by this command: apt remove shim-signed grub-efi-amd64-bin --allow-remove-essential https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1971059 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972154 Title: package grub-efi-amd64-signed 1.180(2.06-2ubuntu7 failed to install/upgrade: Installed grub-efi-amd64-signed package post- Installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1972154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972154] [NEW] package grub-efi-amd64-signed 1.180(2.06-2ubuntu7 failed to install/upgrade: Installed grub-efi-amd64-signed package post-Installation script subprocess returned error exit status
Public bug reported: when upgrade ubuntu 21.10 to ubuntu 22.04 LTS using do-release-upgrade, this package show an error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64-signed 1.180+2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 9 15:38:23 2022 DuplicateSignature: package:grub-efi-amd64-signed:1.180+2.06-2ubuntu7 Setting up grub-efi-amd64-signed (1.180+2.06-2ubuntu7) ... mount: /var/lib/grub/esp: special device /dev/disk/by-id/wwn-0x600224800e0c6a887173a2c44f979804-part1 does not exist. dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32 InstallationDate: Installed on 2022-01-17 (111 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.180+2.06-2ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32 UpgradeStatus: Upgraded to jammy on 2022-05-09 (0 days ago) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972154 Title: package grub-efi-amd64-signed 1.180(2.06-2ubuntu7 failed to install/upgrade: Installed grub-efi-amd64-signed package post- Installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1972154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
A bug has been opened with debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010575 ** Bug watch added: Debian Bug tracker #1010575 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010575 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971492] [NEW] package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: Nothing obviously wrong that I could tell ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: rfkill:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 3 06:05:52 2022 DpkgHistoryLog: Start-Date: 2022-05-03 06:05:50 Commandline: /usr/bin/unattended-upgrade Upgrade: rfkill:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2018-12-10 (1239 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2021-12-15 (139 days ago) mtime.conffile..etc.pam.d.lightdm: 2018-12-10T13:15:57.713002 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971492 Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1971492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
I note that qtbase-opensource-src-5.15.3+dfsg works correctly on jammy. This is likely because the "-no-feature-relocatable" option is used with configure in debian/rules. 2-qt6-base_6.2.4+dfsg-2ubuntu2.debdiff adds the equivalent cmake option for qt6-base_6.2.4+dfsg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
This is another way to fix the problem. It was suggested in https://bugreports.qt.io/browse/QTBUG-82589?focusedCommentId=500548&page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#comment-500548: "or disable the relocating feature for your distro". That is what this patch does. This is a debdiff for qt6-base applicable to 6.2.4+dfsg-2ubuntu1. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended. ** Patch added: "2-qt6-base_6.2.4+dfsg-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+attachment/5585995/+files/2-qt6-base_6.2.4+dfsg-2ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964763] Re: QtChooser doesn't support qt6
This is a debdiff for qtchooser applicable to qtchooser_66-2build1. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended. ** Patch added: "1-qtchooser_66-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+attachment/5585108/+files/1-qtchooser_66-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964763 Title: QtChooser doesn't support qt6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
Here is a more complete patch. The fix is the same, but this includes the updates to changelog, patches/series, as well. ** Patch added: "1-qt6-base_6.2.4+dfsg-2ubuntu2.dsc.debdiff" https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+attachment/5584085/+files/1-qt6-base_6.2.4+dfsg-2ubuntu2.dsc.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
One could imagine a more robust solution where the cmake function file(REAL_PATH [BASE_DIRECTORY ] [EXPAND_TILDE]) was used to guarantee that QtQmakeHelpers.cmake resolved the relative path used to compute QT_CONFIGURE_LIBLOCATION_TO_PREFIX_PATH in the same manner that the supplied patch works at run time. This isn't necessary the way the jammy build is set up, but it might be necessary in general. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
This issue appears on jammy because /lib is a symbolic link, and the /lib/x86_64-linux-gnu entry in the loader search path is used to find libQt6Core. The cmake generated qconfig.cpp contains this line: #define QT_CONFIGURE_LIBLOCATION_TO_PREFIX_PATH "../../" So, prefixFromQtCoreLibraryHelper() computes prefixdir as /lib/x86_64-linux-gnu/../../ and returns /. Note if /usr/lib/x86_64-linux-gnu had been used to find libQt6Core by the loader, then prefixFromQtCoreLibraryHelper() would have computed prefixdir as /usr/lib/x86_64-linux-gnu/../../, and returned /usr, which would have worked. Instead of messing with the loader search path, or messing with cmake to compute QT_CONFIGURE_LIBLOCATION_TO_PREFIX_PATH correctly given the loader search path, the attached patch just resolves any symbolic link so libdir becomes /usr/lib/x86_64-linux-gnu instead of /lib/x86_64-linux-gnu and prefixFromQtCoreLibraryHelper() returns /usr. ** Patch added: "qlibraryinfo_symlink.patch" https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+attachment/5583206/+files/qlibraryinfo_symlink.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd
** Tags added: regression-release ** Summary changed: - using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd + (Encrypted) ZFS breaks 22.04 installation ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970066 Title: (Encrypted) ZFS breaks 22.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd
** Description changed: On a freshly installed 22.04.0 amd64 Desktop with (encrypted) ZFS, removing the Firefox snap breaks: * the current gnome-shell session - it returns to gdm3 login prompt * snapd - all snaps are marked 'broken' * dpkg - dpkg status database is lost - Reproducible on dedicated hardware and VMs. + Reproducible on dedicated hardware and VMs. Not reproducible on a + default (/ on ext4) installation. Video showing the whole process on a freshly installed system: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583102/+files/1970066.webm journalctl -b output: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583100/+files/1970066_journal.txt /proc/self/mountinfo: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583101/+files/1970066_mountinfo.txt - This is not reproducible on a default (/ on ext4) installation. + Installation procedure: + - Minimal installation + - Tick 'download updates' + - Tick 'install third party software' + - Erase disk and use ZFS + encrypt + - Require password to log in ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970066 Title: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd
** Description changed: - An installation of 22.04 LTS on a VM or dedicated hardware crashes the system. - You can login again but the system (APT, snap) is broken. + On a freshly installed 22.04.0 amd64 Desktop with (encrypted) ZFS, removing the Firefox snap breaks: + * the current gnome-shell session - it returns to gdm3 login prompt + * snapd - all snaps are marked 'broken' + * dpkg - dpkg status database is lost - This video shows the whole process: - https://p.haxxors.com/fysoxj8t.webm + Reproducible on dedicated hardware and VMs. - journald output: https://termbin.com/nas2 - /proc/self/mountinfo: https://termbin.com/cjh1 + Video showing the whole process on a freshly installed system: + https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583102/+files/1970066.webm - This only happens on ZFS. Same VM with ext4 has no problems. + journalctl -b output: + https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583100/+files/1970066_journal.txt + + /proc/self/mountinfo: + https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583101/+files/1970066_mountinfo.txt + + This is not reproducible on a default (/ on ext4) installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970066 Title: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] Re: Qt6 QLibraryInfo returns wrong paths
This seems to be related to the dynamic loader search path, see the comments in https://bugreports.qt.io/browse/QTBUG-82589 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd
** Attachment added: "Attaching video (by IRC user ravage) reproducing the bug" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583102/+files/1970066.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970066 Title: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd
** Attachment added: "Attaching N. Buechners' output of: cat /proc/self/mountinfo" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583101/+files/1970066_mountinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970066 Title: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd
** Attachment added: "Attaching N. Buechners' output of: journalctl -b" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+attachment/5583100/+files/1970066_journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970066 Title: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd
Changing status to 'new' (from 'incomplete') since apport is broken. ** Changed in: snapd (Ubuntu Jammy) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970066 Title: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966911] Re: Cannot enroll finger on Jammy
Same problem here: Bus 001 Device 004: ID 27c6:533c Shenzhen Goodix Technology Co.,Ltd. FingerPrint Dell XPS 15 9500 Attached English language version of @mfr0301's screenshot in case that is helpful. ** Attachment added: "Screenshot of error" https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+attachment/5583038/+files/Screenshot%20from%202022-04-24%2010-13-16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966911 Title: Cannot enroll finger on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970057] [NEW] Qt6 QLibraryInfo returns wrong paths
Public bug reported: The qtdiag program can be used to find the paths returned by QLibraryInfo: qtdiag --no-vulkan --no-rhi --no-gl In this output on jammy (22.04) with qt6-base-dev (6.2.4+dfsg-2ubuntu1) I see: Library info: PrefixPath: / DocumentationPath: /share/qt6/doc HeadersPath: /include/x86_64-linux-gnu/qt6 LibrariesPath: /lib/x86_64-linux-gnu LibraryExecutablesPath: /lib/qt6/libexec BinariesPath: /lib/qt6/bin PluginsPath: /lib/x86_64-linux-gnu/qt6/plugins QmlImportsPath: /lib/x86_64-linux-gnu/qt6/qml ArchDataPath: /lib/x86_64-linux-gnu/qt6 DataPath: /share/qt6 TranslationsPath: /share/qt6/translations ExamplesPath: /lib/x86_64-linux-gnu/qt6/examples TestsPath: /tests SettingsPath: /etc/xdg This is problematic. For example, the DataPath /share/qt6 does not exist. This can lead to various failures. For example a Qt application using the Qt WebEngine might report: Qt WebEngine resources not found at /share/qt6/resources. Trying parent directory... Qt WebEngine resources not found at /share/qt6. Trying application directory... Qt WebEngine resources not found at /app/gpsbabel/gui/GPSBabelFE. Trying fallback directory... The application MAY NOT work. Path override failed for key base::DIR_QT_LIBRARY_DATA and path '/home/tsteven4/.GPSBabel' Installed Qt WebEngine locales directory not found at location /share/qt6/translations/qtwebengine_locales. Trying application directory... Qt WebEngine locales directory not found at location /app/gpsbabel/gui/GPSBabelFE/qtwebengine_locales. Trying fallback directory... Translations MAY NOT not be correct. Path override failed for key ui::DIR_LOCALES and path '/home/tsteven4/.GPSBabel' [0423/194717.040426:ERROR:resource_bundle.cc(911)] Failed to load /home/tsteven4/.GPSBabel/qtwebengine_resources_100p.pak Some features may not be available. [0423/194717.041440:ERROR:resource_bundle.cc(911)] Failed to load /home/tsteven4/.GPSBabel/qtwebengine_resources_200p.pak Some features may not be available. [0423/194717.041481:ERROR:resource_bundle.cc(911)] Failed to load /home/tsteven4/.GPSBabel/qtwebengine_resources.pak Some features may not be available. [0423/194717.042243:WARNING:resource_bundle_qt.cpp(119)] locale_file_path.empty() for locale [3004:3004:0423/194717.389096:ERROR:extension_system_qt.cpp(121)] Failed to parse extension manifest. Segmentation fault (core dumped) I note that qtdiag reports the correct paths on debian sid and qt6-base- dev (6.2.4+dfsg-4): Library info: PrefixPath: /usr DocumentationPath: /usr/share/qt6/doc HeadersPath: /usr/include/x86_64-linux-gnu/qt6 LibrariesPath: /usr/lib/x86_64-linux-gnu LibraryExecutablesPath: /usr/lib/qt6/libexec BinariesPath: /usr/lib/qt6/bin PluginsPath: /usr/lib/x86_64-linux-gnu/qt6/plugins QmlImportsPath: /usr/lib/x86_64-linux-gnu/qt6/qml ArchDataPath: /usr/lib/x86_64-linux-gnu/qt6 DataPath: /usr/share/qt6 TranslationsPath: /usr/share/qt6/translations ExamplesPath: /usr/lib/x86_64-linux-gnu/qt6/examples TestsPath: /usr/tests SettingsPath: /etc/xdg It is not clear to me if this is because of the difference in package versions, or some issue with ubuntu packaging. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libqt6core6 6.2.4+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Apr 23 19:40:12 2022 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: qt6-base UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qt6-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970057 Title: Qt6 QLibraryInfo returns wrong paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt6-base/+bug/1970057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970039] Re: cannot disable Remote Desktop in Ubuntu 22.04
** Package changed: ubuntu => gnome-remote-desktop (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970039 Title: cannot disable Remote Desktop in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969478] [NEW] package python3-distupgrade 1:20.04.38 failed to install/upgrade: installed python3-distupgrade package post-installation script subprocess returned error exit status 1
Public bug reported: Running sudo apt-get update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-distupgrade 1:20.04.38 ProcVersionSignature: Ubuntu 5.14.0-1032.35-oem 5.14.21 Uname: Linux 5.14.0-1032-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Tue Apr 19 07:42:54 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 ErrorMessage: installed python3-distupgrade package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-27 (51 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: ubuntu-release-upgrader Title: package python3-distupgrade 1:20.04.38 failed to install/upgrade: installed python3-distupgrade package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969478 Title: package python3-distupgrade 1:20.04.38 failed to install/upgrade: installed python3-distupgrade package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1969478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967622] Re: Audio distortion
*** This bug is a duplicate of bug 1966066 *** https://bugs.launchpad.net/bugs/1966066 This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux- signed-hwe-5.13/+bug/1966066 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967622 Title: Audio distortion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896350] Re: nbd locks system?
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896350 Title: nbd locks system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964741] [NEW] date command produces "invalid date" on day of DST change when calculating a time between 02:00 and 02:59
Public bug reported: When calculating a timestamp for a time between 02:00 and 02:59 in some locales, date will report "invalid date". This only occurs if the system time is currently during the day that standard time transitions to daylight time. Example: OS Version information: Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal System Locale is: America/Chicago System time the command was issued: Sun 13 Mar 2022 10:15:18 PM CDT Command issued: date +%s -d 'tomorrow 02:50' System Response: date: invalid date 'tomorrow 02:50' If the command issued is changed such that the calculated time is anything other than a time between 02:00 and 02:59 the output is normal. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964741 Title: date command produces "invalid date" on day of DST change when calculating a time between 02:00 and 02:59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1964741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960655] Re: Firefox 97.0 is out since 3 days and not yet updated
https://snapcraft.io/firefox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960655 Title: Firefox 97.0 is out since 3 days and not yet updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960544] Re: External Monitors Not Detected Anymore
** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960544 Title: External Monitors Not Detected Anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960544] Re: External Monitors Not Detected Anymore
You are right, updating the kernel did solve the problem. Thanks a lot for your swift answer! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960544 Title: External Monitors Not Detected Anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960544] [NEW] External Monitors Not Detected Anymore
Public bug reported: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: - Same here with Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the - update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, - libglapi, libdrm etc.), external monitors (here connected via DELL USB - Dock) are not detected anymore. I had to restore the old version with - Timeshift. + On Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of + mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm + etc.), external monitors (here connected via DELL USB Dock) are not + detected anymore. I had to restore the old version with Timeshift. ** Description changed: - On Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of + On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm etc.), external monitors (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. ** Description changed: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of - mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm - etc.), external monitors (here connected via DELL USB Dock) are not - detected anymore. I had to restore the old version with Timeshift. + mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), + external monitors (here connected via DELL USB Dock) are not detected + anymore. I had to restore the old version with Timeshift. ** Description changed: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), - external monitors (here connected via DELL USB Dock) are not detected + external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960544 Title: External Monitors Not Detected Anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692302] Re: Can't connect on external monitor or projector
Same here with Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm etc.), external monitors (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692302 Title: Can't connect on external monitor or projector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1692302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933983] Re: 5.1.0-1ubuntu0.6 on bionic (python2) can fail on Parser.feed(data) due to OSError
This is still an issue with 5.1.0-1ubuntu0.7 of python-pil on bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933983 Title: 5.1.0-1ubuntu0.6 on bionic (python2) can fail on Parser.feed(data) due to OSError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pillow/+bug/1933983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956838] Re: drag and drop broken chromium snap
As to your own posted link above, you can keep as many versions as you like with snap set system refresh.retain=X -- and you can keep running any version as long as you like with snap revert. TimeShift is your second line of defense for your whole system, incl. Snap misconfiguration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956838] Re: drag and drop broken chromium snap
You can esily restore an old Snap version: fetch the old chromium_1854.snap from your Timeshift folder from before Jan 7th from /var/lib/snapd/snaps Install the file and delete the new one with sudo snap install chromium_1854.snap When the system installs the new version in the next update cycle, revert it again with: sudo snap revert chromium Then it will stay until you update manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957844] [NEW] python3 cannot upgrade, if tried, will delete a ton of packages
Public bug reported: Updating the python3 packages on Ubuntu Jammy Jellyfish (22.04) Expected upgrade to upgrade the python3 package It actually said it would delete a ton of packages ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "apt logs" https://bugs.launchpad.net/bugs/1957844/+attachment/5554069/+files/Apt%20Log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957844 Title: python3 cannot upgrade, if tried, will delete a ton of packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1957844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772791] Re: Lock/login screen displays password in clear text occasionally
Is there any update about it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772791 Title: Lock/login screen displays password in clear text occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1772791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956838] Re: drag and drop broken chromium snap
I can confirm the two cases from above since the latest update. In addition a 3rd one: Tab-dropping (to move an tab back into the tab bar) doesn't work either. Expected behavior as before: 1. drag a tab outside the browser window to get a new window (works now) 2. drag a tab into another browser windows to let it join the new window (broken) Suggest to set importance to Medium Thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Confirmed on Ryzen 7 3700U, and that the -24 pre-release update fixes it. Standby has never worked on this system so I can't comment on that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956838] [NEW] drag and drop broken chromium snap
Public bug reported: With the latest Chromium refresh on 2020-01-07 to version 97.0.4692.71 Chromium will not drag and drop selected text onto any any application including Chromium. In a virtual machine, I was able to revert the Chromium snap to version 96.0.4664.110 and drag and drop works. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955985] Re: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same"
patched with version openssh-client version 8.7p1-4 ** Changed in: openssh (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955985 Title: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1955985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955985] Re: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same"
also having this issue Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same Use 'update-alternatives --help' for program usage information. dpkg: error processing package openssh-client (--configure): installed openssh-client package post-installation script subprocess returned e rror exit status 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955985 Title: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1955985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948957] Re: CVE-2021-21703: PHP-FPM oob R/W in root process leading to privilege escalation
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-21703 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948957 Title: CVE-2021-21703: PHP-FPM oob R/W in root process leading to privilege escalation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.4/+bug/1948957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953076] [NEW] Ubuntu 20.04 - NVIDIA GPU consuming power even when using only integrated graphics card (Intel iGPU)
Public bug reported: The issue is pretty simple: using Nvidia X Sever Settings GUI to switch from NVIDIA GPU to Intel iGPU doesn't work and the NVIDIA GPU does still consume some power after rebooting and, as a consequence, it generates uneccesary heat. Same thing (obviously) happens if I use prime-select from the terminal. I can see from powertop that when I have everything on idle, I am still consuming around 18-22W which is at least 10W more than I would expect. This seems to be a rather old bug and supposedly it got "fixed". I can find at least two launchpad bug reports (https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363) and there are some workaround there. Problem is that at this point I am not even sure what works and what doesn't since most posts are over 3 years old. I tried for example installing ubuntu without selecting "install third party drivers" since someone suggested it would fix the problem but it didn't work in my case. Someone else here recently posted about this issue again -> https://discourse.ubuntu.com/t/nvidia-prime-not-powering-off-the-dgpu/21856 I used to have another Optimus laptop years ago and I remember it worked fine in older Ubuntu versions but now something seems wrong. Config: - Zephyrus M16, 11800H, 3070 - Ubuntu 20.04 (but same problem with 21.10) - Nvidia Driver 470 and 460 tested. ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: gpu nvidia prime -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953076 Title: Ubuntu 20.04 - NVIDIA GPU consuming power even when using only integrated graphics card (Intel iGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1953076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765363] Re: prime-select intel is not powering off the nvidia card
This is still happening even on Ubuntu 20.04. I even tried installing without "Additional Drivers" checked and the problem is still there. I tried some workarounds posted here but they don't work or they might be out of date. Any update on this? Zephyrus M16 - 11800H - 3070 - Nvidia Driver 470 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950917] [NEW] Reporting a gimp crash
Public bug reported: ``` The "Gimp" crash happened when try to apply the oilify filter to an image layer. I had tried to apply it to the top layer. It was not turned on. So I turned the layer on and then used from the Gimp menu "re-apply" oilify filter. Since it was never applied in the first place, I had guessed that that was where the error came in. However, I restarted Gimp selected recover last session and tried to apply the oilify filter (this time with the layer being selected. I got the same crash. Went back in and change the image precision to 32 bit integer from 32 bit floating integer and there was no crash; and the filter applied. I think Gimp needs grey out filters when they are not designed to work under certain conditions. Note: The Gimp error dialog led me here via send report button, so I assume this is the right place to report? GNU Image Manipulation Program version 2.10.24 git-describe: GIMP_2_10_24 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 10.3.0-6ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-IAajkb/gcc-10-10.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-IAajkb/gcc-10-10.3.0/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.3.0 (Ubuntu 10.3.0-6ubuntu1) # Libraries # using babl version 0.1.88 (compiled against version 0.1.88) using GEGL version 0.4.32 (compiled against version 0.4.30) using GLib version 2.68.4 (compiled against version 2.68.3) using GdkPixbuf version 2.42.6 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.48.10 (compiled against version 1.48.7) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 263490 - Thread 263490 # [New LWP 263491] [New LWP 263492] [New LWP 263493] [New LWP 263494] [New LWP 263495] [New LWP 263496] [New LWP 263537] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=256, buf=0x7ffccb54edd0, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target IdFrame * 1Thread 0x7fe6e94a6300 (LWP 263490) "gimp"__GI___libc_read (nbytes=256, buf=0x7ffccb54edd0, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fe6e8d22640 (LWP 263491) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fe6e8521640 (LWP 263492) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fe6e7d20640 (LWP 263493) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fe6e69b1640 (LWP 263494) "gmain" 0x7fe6ea157cdf in __GI___poll (fds=0x55dcb3095800, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 6Thread 0x7fe6e61b0640 (LWP 263495) "gdbus" 0x7fe6ea157cdf in __GI___poll (fds=0x55dcb52d5830, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 7Thread 0x7fe6cd005640 (LWP 263496) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fe6c4bb1640 (LWP 263537) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 8 (Thread 0x7fe6c4bb1640 (LWP 263537) "swap writer"): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 No locals. #1 0x7fe6ea3f6e03 in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so
[Bug 1356433] Re: detached tabs can not be reattached
Is this feature ever going to come back? I miss it. Affecting me currently in 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1356433 Title: detached tabs can not be reattached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1356433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
I confirm the bug is still present (and very annoying, making me lose a lot of time) on Ubuntu 21.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
