Public bug reported:
I noticed that it upgraded mesa to 22.x and now video acceleration is
not working due to:
❯ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva error: /us
Public bug reported:
Upgraded to jammy and this crash showed up.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: python3 3.9.7-4
ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
Uname: Linux 5.13.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Ap
Upgrade was successful but there were problems in the rtupdate like:
Exception: cannot get content of ibus-hangul
so had to:
cd /usr/share/python3/runtime.d
sudo mkdir temp
sudo mv ibus-hangul.rtupdate temp
Had to move all of those those .rtupdate that said cannot get content
of. Then dpkg --co
Yes, it said somewhere after the error that ibus-hangul is not
installed.
On Wed, Jan 19, 2022 at 11:25 PM Stefano Rivera <1958...@bugs.launchpad.net>
wrote:
> What was the dpkg state of ibus-hangul?
>
> It sounds like it wasn't installed, but the rtupdate file still existed
> on disk.
>
> --
> Y
Another office mate upgraded to jammy jellyfish development and this error
showed up:
Setting up python3 (3.9.7-4) ...
running python rtupdate hooks for python3.9...
E: py3compile:212: cannot create directory
/usr/share/sqlmap/thirdparty/gprof2dot/__pycache__: FileNotFoundError(2,
'No such
file or
The fix was the same:
cd /usr/share/python3/runtime.d
sudo mkdir temp
sudo mv * temp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1958266
Title:
package python
use-dns doesn't work with NetworkManager:
network:
version: 2
renderer: NetworkManager
wifis:
wlan0:
optional: true
dhcp4: true
dhcp4-overrides:
use-dns: no
use-routes: false
nameservers:
addresses: [192.168.77.1]
access-points:
Verified with newest evince: 3.31.90-1 and the bug doesn't exit any
more.
** Changed in: poppler (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bug
Public bug reported:
apt update doesn't work after upgrading apt to 1.9.2 with strace:
openat(AT_FDCWD, "/var/lib/apt/lists/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
--- SIG
Replacing acquire.cc from 1.9.1 fixes the crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1839714
Title:
Segmentation fault when running apt update using libapt-pkg5.90_
Here's the backtrace:
0x77dc4310 in pkgAcquire::Enqueue (this=0x7fffdf20, Item=...) at
../apt-pkg/acquire.cc:339
warning: Source file is more recent than executable.
339if (Config->LocalOnly == true
(gdb) bt
#0 0x77dc4310 in pkgAcquire::Enqueue (this=0x7fffdf20, I
Thanks for fixing the issue. I can confirm that with commit 7c724251 apt
update works in my system now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1839714
Title:
Segmentat
Public bug reported:
Upgraded to new ca-certificates and still says script returned 2.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
*** This bug is a duplicate of bug 1764848 ***
https://bugs.launchpad.net/bugs/1764848
shemgp shemgp-x230t ~ USAGE $ apt-cache show libssl1.1
Package: libssl1.1
Architecture: amd64
Version: 1.1.0g-2ubuntu4
Multi-Arch: same
Priority: important
Section: libs
Source: openssl
Origin
*** This bug is a duplicate of bug 1764848 ***
https://bugs.launchpad.net/bugs/1764848
Downgraded libssl1.1 and still has the error:
shemgp shemgp-x230t ~ USAGE $ apt-cache show libssl1.1
Package: libssl1.1
Architecture: amd64
Version: 1.1.0g-2ubuntu4
Multi-Arch: same
Priority
*** This bug is a duplicate of bug 1764848 ***
https://bugs.launchpad.net/bugs/1764848
I tried to reboot:
shemgp shemgp-x230t ~ ERROR $ sudo dpkg --configure -a
[sudo] password for shemgp:
Sorry, try again.
[sudo] password for shemgp:
Setting up ca-certificates (20180409
Public bug reported:
This error showed up when I was updating Ubuntu. Running :
cd /var/lib/dpkg/info
sudo -H -b bash -x ca-certificates.postinst configure
+ set -e
+ case "$1" in
+ '[' '!' -e /usr/local/share/ca-certificates ']'
+ dpkg-statoverride --list /usr/local/share/ca-certificates
++ sta
Public bug reported:
When the default nameserver, which is set by systemd-resolve, is
127.0.0.53, guest systems (libvirtd, lxc, snaps, anbox, etc) won't work
unless there's a non 127.0.0.x nameserver (eg. 8.8.8.8) in
/etc/resolv.conf. Because the dnsmasq in these guest machines try to
resolve to
Hello,
Are you using Artful? I've tested it again in Ubuntu 17.10 and the UI
doesn't get updated immediately but it does pause, resume, and cancel
jobs just fine: https://youtu.be/Z5IuAAtKlnI.
Could you test using this PPA:
https://launchpad.net/~shemgp/+archive/ubuntu/other-apps?
I&
Yup, as I see it using cups-pk-helper gives two layers of auth, one for
cupsd and another for policy-kit. Using cups-pk-helper as lpadmin or
root would override cupsd permissions as it'll be running with all
privileges, but there's still the policy-kit permissions.
Right now, I've tested it, with
Also, add/change dns=* to dns=default in
/etc/NetworkManager/NetworkManager.conf under [main]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1737732
Title:
systemd-resolve
Does the PPA work?
Sent from Mailspring (https://link.getmailspring.com/link/local-
2575ba08-3601@shemgp-
x230t/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=934291%40bugs.launchpad.net),
the best free email app for work
On Dec 21 2017, at 12:05 am, Till Kamppeter
Thanks for testing. It really does not work on a freshly installed
Artful, because the mechanism was only allowing root and not lpadmin to
run. I changed that and tested it on a freshly installed Artful, and it
worked, so here's another debdiff. I also updated my PPA. Please do
test.
** Patch a
Public bug reported:
On Cosmic development version here and after a few upgrades (didn't
remember when) my wifi would disconnect and turn into a hotspot. To fix
it I would disconnect the hotspot and then connect to my wifi, but it'll
do that after a while again.
Thank you for your help.
Problem
Purged and reinstalled network-manager and it seems to be fixed.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.la
Verified that the patch in fd works in mesa 17.3.3. People may test
here: https://launchpad.net/~shemgp/+archive/ubuntu/testing
Although, totem still runs at like 10~18% CPU while mpv is lower at
3~5%.
** Attachment added: "Screenshot from 2018-02-09 17-41-49.png"
https://bugs.lau
Experienced this with Ubuntu 16.04 after using my work desktop station
as a temporary server with vagrant servers and using gnome-shell as my
DE for about a month. Nautilus started to crash with the error:
cannot open display: :0.0
Maximum number of clients reached
Restarting gdm3 didn't work ei
Fixed in latest gnome-shell in my instance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1654490
Title:
gdm3 won't work on 17.04
Status in xorg package in Ubuntu:
Confir
I'm getting this when starting lxd images on Zesty:
lxc 20160212143429.678 ERROR lxc_apparmor -
lsm/apparmor.c:apparmor_process_label_set:220 - If you really want to start
this container, set
lxc 20160212143429.678 ERROR lxc_apparmor -
lsm/apparmor.c:apparmor_process_label_set:221 - lxc.aa_
Here's another debdiff to make cups-pk-helper run as lpadmin.
** Patch added: "run_as_lpadmin.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/934291/+attachment/4912677/+files/run_as_lpadmin.debdiff
--
You received this bug notification because you are a member o
Now, yes. I thought it was working but I was using a gnome-shell
extension that used the command 'cancel' to cancel a job and not cups-
pk-helper. Anyway, still digging into it. Sorry for the non-working
patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seede
Here's another debdiff. I tested this on my machine and was able to
delete jobs from the queue. I just had to add the annotation which I
got an idea from from the colord package.
** Patch added: "run_as_lpadmin2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/9342
Here's a more complete fix. Added the annotation for all actions and
made setting the daemon user an option in the configure.ac.
** Patch added: "run_as_lpadmin3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/934291/+attachment/4913165/+files/run_as_lpadmin3.debdi
Quick fix:
sudo sed -i '/ExecStart=/a ExecStop=/bin/systemctl stop cups.service'
/lib/systemd/system/cups-browsed.service
Got the idea from previous 16.04 bug with cups-browsed.service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Work around (the previous one doesn't work):
sudo sed -i '/ExecStart=/a ExecStop=/bin/bash -c "ps -AfH | grep cups-browsed |
awk '\''{print $2}'\'' | xargs kill -s 9"'
/lib/systemd/system/cups-browsed.service
sudo systemctl daemon-reload
sudo systemctl restart cups-browsed.service
--
You recei
Public bug reported:
Upgraded to focal development and rebooted. When I try to login, it
doesn't allow me. Looking at the logs, there's a crash.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux
Here's the user xorg log that shows the crash
** Attachment added: "Xorg.1.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868561/+attachment/5340509/+files/Xorg.1.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Here's the backtrace.
If I run:
sudo gdb --args /usr/lib/xorg/Xorg -nolisten tcp :1 vt2 -keeptty
-logfile xorg.log
on terminal and on another terminal run:
export DISPLAY=:1
gnome-session
it crashes and the backtrace full is attached.
But if I just run:
export DISPLAY=:1
gnome-shell
it doe
Also, the latest mainline kernel didn't fix the problem:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc7/linux-modules-5.6.0-050600rc7-generic_5.6.0-050600rc7.202003230230_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
Here's the bt only.
** Attachment added: "xorg.crash.bt_only.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868561/+attachment/5340610/+files/xorg.crash.bt_only.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Here's a patch to add root to the system-groups in the rules file in the
debian directory.
** Patch added: "add root to system-groups in rules"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/934291/+attachment/4782065/+files/934291.diff
--
You received this bug notificat
Upgraded to Xenial 16.04 and also the BIOS and I haven't experienced the
crash yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1531471
Title:
Xorg suddenly closes
Status
Public bug reported:
Was just clicking around when the screen suddenly when black--went to
the virtual terminal-- after a few seconds lightdm started back up. I
had to login and launch my apps again. It happened a few times already.
Looked at the logs and there's a backtrace in /var/log/Xorg.0.
What else do I need to provide? And how do I get it? Thanks.
On Wed, Nov 25, 2015 at 9:27 PM, Raymond <1519...@bugs.launchpad.net>
wrote:
> username-ThinkPad-X230-Tablet systemd-udevd[345]: Unknown key identifier
> 'direction'
> Nov 24 17:04:32 username-ThinkPad-X230-Tablet systemd-tmpfiles[675
Public bug reported:
When I was clearing up unpurged packages, grub-pc was not being purged because
of an error "basename: missing operand". Looked at the code and "ucf --purge
/etc/default/grub" was bailing out at line 472, which has the code:
old_mdsum_file="$source_dir/$(basename ${new_f
45 matches
Mail list logo
