Please actually read the warning message. Also read the warning message
apt-key gives you:
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d
instead (see apt-key(8)).
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
Public bug reported:
Hi Everyone,
I want to install Firefox from Mozilla PPA. I added issued apt-key (from
apt package) to fetch the signing key, and then enabled the PPA in
/etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list. The apt-key
command used was:
sudo apt-key adv --keyserver
Yes, I have just confirmed:
* Suspend works
* Hibernate works
* Hybrid Sleep does not work
More specifically, Hybrid sleep results in what appears to be a
successful suspend (after a longer period, because it is saving
hibernation data). When an awakening is attempted, it fails, and the
system m
You are correct, it was set to 'security updates only.' After changing
to 'All updates' and updating, I was able to install librtaudio-dev
finally and some related dependencies were updated with that operation
(pulse things). I think my issue is solved! :)
--
You received this bug notification be
Note that this was due to a very specialized kind of outage, namely
where the machine-readable API description file fetched from
api.launchpad.net refers to api.launchpad.test (which only exists in
some development setups and shouldn't be referred to from production).
This part of the problem was o
Public bug reported:
`man limits.conf` reports that the "core" setting "limits the core file
size (KB)".
However, if I set the size to 3200:
# Limit the size of core dumps (32GB = 3200KB)
* soft core 3200
* hard core 3200
Then reboot and check the size with ulimit:
$ ulimit -a
>I don't know all the vagaries of the package versioning but it seems my
apt isn't finding the latest libpulse-dev or something.
Yes, exactly :) If we do a little comparison here:
~$ apt policy libpulse-dev libpulse0
libpulse-dev:
Installed: (none)
Candidate: 1:15.99.1+dfsg1-1ubuntu2.1
Versi
** Description changed:
+ [ Impact ]
+
Customer reported that this issue happens randomly during their
automated regression runs. It's not consistent and hard to reproduce.
They have shared a coredump:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x555962aa1c34
Right. The handover from basic networking in initrd to the full Netplan
setup in the booting/booted system could probably be improved (in may
ways), e.g. flushing the IP addresses.
I guess that's something we'd need to implement in systemd-networkd when
taking over the interfaces. I wonder if Netw
See attached output as requested.
As I noted in a comment above, this problem appears to have been fixed in one
of the patches since I submitted the initial report. It's now working correctly.
** Attachment added: "log.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020229/+a
** Changed in: accountsservice (Ubuntu)
Importance: Undecided => High
** Changed in: accountsservice (Ubuntu)
Status: New => Fix Committed
** Summary changed:
- accountsservice package
+ accountsservice segfault when toggling autologin
--
You received this bug notification because yo
Thanks, interesting discussion. It's also worth noting that newer Ubuntu
versions have the current dbus serie with SO_PEERGROUPS support so the
issue should be resolved there
** Changed in: dbus (Ubuntu)
Importance: Undecided => High
** Changed in: dbus (Ubuntu)
Status: New => Triaged
Closing since the problem is fixed in the current Ubuntu serie, if we
decide to SRU a fix to 22.04 we will add that target serie to the report
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launch
https://github.com/canonical/netplan/pull/371
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bu
** Also affects: dbus via
https://gitlab.freedesktop.org/dbus/dbus/-/issues/343
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2
I have to correct the information - currently even if I rebooted several
times, the option "Enable Wireless" is not available :-o
--
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.launchpa
1. I boot my PC with LAN cable connected. Lan works, but I only see "Enable
networking" when I open the network manager options in the top right corner of
the screen. I guess, the "Enable Wireless" option is disabled deliberately,
while on LAN - which is not the best idea IMHO.
Can't screenshot
Thank you for your bug report. Could you provide the output of
$ pw-cli ls
in a logfile attached to the bug?
Are the devices listed for example in pavucontrol?
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Hi,
I confirm that the patch fixes input encoding detection issue for me
(22.04.2 LTS)
Current package:
free1 : ~ [0] # echo $LC_ALL
en_US.UTF-8
free1 : ~ [0] # dpkg -l idn libidn12
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Public bug reported:
See my public question open here:
https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate
I'd expect, to see the option "dis/enable wifi" at least when I disconnect from
LAN, (if not regardless on LAN connection).
But I can not see that opt
--- Comment From wint...@de.ibm.com 2023-06-26 03:07 EDT---
I was not able to reproduce this.
Runs fine on my machine (see below).
Any ideas how to continue?
root@m8360007:~/# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy
22 matches
Mail list logo