How helpful to you would it be for me to install the .ddeb file and
which of the traces would you want me to run again? Would I do the
install via sudo dpkg -i or use synaptic or apt in some manner? Should
I uninstall it after the traces? Obviously I would need to do the
traces you want prior to
Per the above dpkg search and looking at /var/cache/apt/archives I see
the following:
-rw-r--r-- 1 root root195976 Feb 16 05:54
gir1.2-gtk-3.0_3.24.20-0ubuntu1.1_amd64.deb
-rw-r--r-- 1 root root 28756 Feb 16 05:54
gtk-update-icon-cache_3.24.20-0ubuntu1.1_amd64.deb
-rw-r--r-- 1 root root
Cf.: https://bugs.launchpad.net/ubuntu/+source/system-config-
printer/+bug/1963723.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/471650
Title:
system-config-printer can't f
the segfault seems to be in the gtk menu code, do ypu have any special
indicator or plugin installed? what desktop environment do you use? it
would also help to get details on the backtrace if
https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.32-4ubuntu4/+build/18229140/+files/libgtk2.0-0-dbgsym_2.
Opened #1006784 in src:automake-1.16 1:1.16.5-1.1 by Gianfranco
Costamagna (locutusofborg) «automake: fixes for python3.10 distutils
changes». https://bugs.debian.org/1006784
Please have a look at it if possible.
** Bug watch added: Debian Bug tracker #1006784
https://bugs.debian.org/cgi-bin/
you can find the deb files on
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1/+build/19437463
check on your system the packages from that source using
$ dpkg -l | grep 3.24.20-0ubuntu1.1
and download in a new directory the corresponding deb from the webpage, then
install them using
There’s an upstream fix that has been merged:
https://github.com/libexpat/libexpat/pull/577
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to expat in Ubuntu.
https://bugs.launchpad.net/bugs/1961800
Title:
Seeing out of memor
I was going to add a copy of the libgail-3-0 package that was working
for me to my local repository to see if I could prepare to attempt to
back out the update. I am having difficulty locating a copy of the
package that was replaced. I have access to 3.24.18 in the main
repository and the failing
This bug was fixed in the package automake-1.16 - 1:1.16.5-1.1ubuntu1
---
automake-1.16 (1:1.16.5-1.1ubuntu1) jammy; urgency=medium
* Upload to jammy with a fix for LP: #1960608
-- Gianfranco Costamagna Fri, 04 Mar 2022
10:29:43 +0100
** Changed in: automake-1.16 (Ubuntu)
Found yet another program with the same crash.
To my untrained eyes the failure appears to start with
gdk_display_open_default_libgtk_only in all three of these crashes.
Is it possible that this crash impacts ALL gtk2 dependent programs?
** Attachment added: "gdb-gimp.txt"
https://bugs.launc
hm, $ lxc launch --vm ubuntu:xenial fails for me
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, inc
** Description changed:
[impact]
now that jammy has moved to using unified cgroup2, containers started on
jammy must also use unified cgroup2 (since the cgroup subsystems can
only be mounted as v1 or v2 throughout the entire system, including
inside containers).
However, the syst
Irrespective of ESM status, we have always had extremely long support
overlaps both backwards and forwards between ubuntu releases.
At the moment, my only solution is to use lxd vms; i.e.
do
$ lxc launch --vm ubuntu:xenial
However, I say for the sake of ease of development, testing, upgrades,
Public bug reported:
Sound is too low when built_in speaker working. I hear low frequencies
better.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeK
I have found a specific way to stop this by getting visit
https://betterscapeslv.com/ and learn a lot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1714763
Title:
No
Exactly, so at the moment only the following are affected:
- impish
- jammy
I've added a few comments to the arctica-greeter repo and issued a pull
request that basically reverts the commit that introduced the weakness.
However this still needs to be reviewed by the maintainers
--
You received
Hello. No news about this ? Computer being unusable, should I switch
back to 18.04 or buy a new computer ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1961857
Title:
compi
That would mean that Jammy, a LTS, will not be able to make use of LTE
modems on 2021 shipped ThinkPad ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1949621
Title:
Hello, there are also bugs in python.m4, the same fix as
https://github.com/pybind/pybind11/pull/3764/files fixes the issue in m4
too
I patched locally my python.m4 with something like this:
- sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
- sitedir = sysconfig.get_path(
Changing package to xfce-screensaver after additional troubleshooting:
-apt remove xfce4-screensaver resolves the issue
Appears that the frozen screen is a result of xfce4-screensaver not
operating as expected and is not a LightDM issue
** Package changed: lightdm (Ubuntu) => xfce4-screensaver (U
20 matches
Mail list logo
