This is greatly exasperated because systemd until v251 is using MemFree
and not MemAvailable to decide how much memory is remaining. Since Linux
aggressively uses MemFree for caching, this will result in systemd-oomd
excessively killing applications.
There's a fix in upstream 030bc91cb98385904b28a
Yeah, I just removed 22.10. It was just far too unstable. I had a crash
where I couldn't do anything, not even shut my system down, it appeared
to be a kde issue. So I am now testing 22.04 on my desktop and mint 21
on my laptop.
Sent with Proton Mail secure email.
--- Original Message -
The bug reports stopped working all together, too.
Sent with Proton Mail secure email.
--- Original Message ---
On Saturday, December 10th, 2022 at 4:59 PM, ke7in.dev
wrote:
> Yeah, I just removed 22.10. It was just far too unstable. I had a crash where
> I couldn't do anything, no
Public bug reported:
1. Ubuntu 22.10 (studio install)
2. 2.23.1-0ubuntu3 500
3. I was on generic bug selection screen and picked the "best fitting"
one (konsole popped up 1319), but realized there were no great options
and went to 'x' it out to dig a little more...
4. crash.
ProblemType: Bug
D
Hi Benjamin,
Thanks for getting back to me. There is unfortunately no crash report
available for apport. I went and tinkered with the ubuntu-bug command as
you suggested to try and close in on the issue here.
I want to note 2 things:
1. The generic bug reporter was not allowing me to select "oth
Steps to achieve hang (or crash on the 1st attempt, before updating
system packages -- not sure if that's unrelated to the change in the
behavior or not, but worth mentioning):
1. type 'ubuntu-bug' in konsole
2. click audio related
3. click "It's not listed here"
4. don't click "OK", click "Can
Side note: I hit ctrl+c to cancel terminal after and got this:
```
^CException ignored in:
Traceback (most recent call last):
File "/usr/lib/python3.10/threading.py", line 1567, in _shutdown
lock.acquire()
KeyboardInterrupt:
```
Sent with Proton Mail secure email.
--- Original Mess
Follow-up:
I don't think the bug report actually went through. I was never brought
to the website like before.
Should I attempt to post a new bug for this, or did the request send
through my user acc around the time I depicted steps and mentioned
sending it?
Sent with Proton Mail secure email.
@dwmw2
Were you able to make this work by doing this for firefox?
sudo mv /usr/lib/firefox/libnssckbi.so /usr/lib/firefox/libnssckbi.so.bak
sudo ln -s /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so
/usr/lib/firefox/libnssckbi.so
https://askubuntu.com/questions/244582/add-certificate-authorit
@dwmw2,
I figured out the issue. Long story short, freeipa (which is our CA),
when we enroll a PC into the realm, it adds the freeIPA cert to
/etc/ssl/certs/ca-certificates.crt like it should, however it also adds
other information that it shouldn't.
This results in p11-kit-trust.so blowing parsi
My printer is Epson WFC-869R Workforce series. Affected with same bug.
--
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/1853373
Title:
Print problems for double sided, multiple
I'm running into this bug as well on 16.04.5
I've tried the autofs.service (SystemD) solution. I've tried the startup
scripts in the rc.local and it "seems" to work most of the time, but not
really ideal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Can confirm. 17.10 works much better so far.
Rob Schultz <405...@bugs.launchpad.net> schrieb am Do., 2. Nov. 2017,
15:46:
> Interesting. I installed 17.10 and Bluetooth worked so much better than it
> had with 16.04 (I had basically given up using it).
> Then I re-installed to eliminate any of my
Is there any reason the lines creating the menu entry can't just be
removed? https://bazaar.launchpad.net/~vcs-imports/network-manager-
applet/git-master/view/head:/src/applet.c#L1322
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
same here:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1665579
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1616695
Title:
Bluetooth signal is unusably poor
Hi everybody,
I had this problem too on LinuxMint 18 (based on 16.04).
I solved the problem by reverting the network-manager package to the version
1.2.2 (instead of 1.2.6) using synaptic.
Maybe it can help someone
Cheers
--
You received this bug notification because you are a member of Ubun
** Changed in: pm-utils (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1577738
Title:
pm-utils does not write pm-suspend
Public bug reported:
Hi, this is the second bug I report, and I hope I'm reporting that one
in a better way than the first, I'm including a report at least this
time xD
The thing is that sometimes wired network stops working and needs to be
turned off and on to get it back to the work. It's happe
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kevin 2411 F pulseaudio
/dev/snd/controlC0: kevin 2411 F pulseaudio
CurrentDesktop: Unity
Date: Fri Feb 17 10:03:15 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-12-15 (63 days ago
ntu.
https://bugs.launchpad.net/bugs/1589893
Title:
Xorg crashes
Status in xorg package in Ubuntu:
Incomplete
Bug description:
Jun 7 11:40:18 kevin-MacBookPro kernel: [ 6818.471186] Freezing of tasks
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Jun 7 11:40:18 kevin-MacBook
Hi,
Im working now with 4.7.0-040700rc5-generic on Ubuntu 16.04 LTS.
no crashes since 4 days. Hurray!
Cheers,
Kevin
--
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/1589893
:
Incomplete
Bug description:
Jun 7 11:40:18 kevin-MacBookPro kernel: [ 6818.471186] Freezing of tasks
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Jun 7 11:40:18 kevin-MacBookPro kernel: [ 6818.471220] XorgD
880089ccfa78 0 1109 1099 0x0044
Public bug reported:
On Ubuntu 16.04 LTS with MacBook Pro 12.01 I can't connect to any Wifi after
booting.
When I restart the network-manager everything is OK.
I expect that Ubuntu should connect to the Wifi directly.
I'm using the following network-manager package:
Installed: 1.1.93-0ubuntu4
P
maybe related to https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1434986
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1583019
Title:
network-mana
works with 1.2.0-0ubuntu0.16.04.2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1583019
Title:
network-manager needs a restart after booting (otherwise can't conn
Public bug reported:
Installed a 32bit laptop with Ubuntu 16.04. Installation worked fine, on
initial login was prompted by Software Updater that additional updates
were available - which was accepted.
These appeared to work fine without any issues, however after the
subsequent reboot. Get the GU
Additional Information -
The bug has occurred on the same hardware a couple of times now. The
installation of 16.04 works, and I am able to use the desktop.
It is the upgrade that introduce 16.04.1 onto the hardware that appears
to cause the issues.
After upgrading I am prompted for a password w
After re-installing back to 16.04, I managed to determine that the
processes taking up the most memory an CPU were compiz and XOrg, which
were at times making the laptop unresponsive. I read through a number of
Forums, suggesting that Ubuntu 16.04 was using excessive amount of
memory compared to pr
Public bug reported:
Jun 7 11:40:18 kevin-MacBookPro kernel: [ 6818.471186] Freezing of tasks
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Jun 7 11:40:18 kevin-MacBookPro kernel: [ 6818.471220] XorgD
880089ccfa78 0 1109 1099 0x0044
Jun 7 11
Same exact symptoms on my gigabyte P35x v4. I fiddled around with audio
settings forever before I found (from this thread) that I could mute and
raise the volume from there. At least it is workable for now but I
subscribed to this bug.
--
You received this bug notification because you are a mem
** Also affects: linux-intel-iotg-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2056383
Title:
Audio turned t
All of a sudden SLAAC addresses are preferred over DHCPv6 addresses,
which should not be happening. Setting ip6.privacy=0 no longer helps,
nor does setting net.ipv6.conf.all.use_tempaddr = 0 with sysctl.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Public bug reported:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=0 for the conne
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1974428
Title:
Update to the current 1.36 sta
Looking at the changelog of 1.38.0:
* Fix bug setting priority for IP addresses.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS
So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
Please either backport it from 1.38.0 or revert to 1.36.4.
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
Comparing the output of `ip -6 a`, you can see that the dynamic
addresses are no longer at the top of the list, where they should be.
Before (network-manager 1.36.4):
2: eno0: mtu 1500 state UP qlen 1000
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute
valid_lft 43193
I guess these commits are relevant:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c631aa48f034ade2b5cb97ccc4462d56d80174e7
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/257221d1986b56cbb2e329fcc74a2daca145b7aa
Bottom line: addresses are now being a
** Tags added: jammy
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
@seb128 I have created a new bug report with links to the upstream
commits. The core of the issue is that IPv6 addresses are now being
added in the wrong order, so the kernel prefers SLAAC addresses over
DHCPv6 addresses, which should be the other way around.
As this is a breaking change in source
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
- ip6.privacy=
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 orders IPv6 addresses incorrectly
Status in n
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available.
+ over SLAAC addresses when available. And according to RFC 6724 the
+ smaller /128 scope o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available. And according to RFC 6724 the
smaller /128 scope of the DHCPv6 address should be chosen o
** Description changed:
- My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
- perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available. And according to RFC 6724 the
- smaller /128 scope of the DHCPv6 address should be chosen o
** Description changed:
Situation:
My network has both DHCPv6 and SLAAC for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over SLAAC addresses when
available. And according to RFC 6724, the smaller /1
** Description changed:
Situation:
- My network has both DHCPv6 and SLAAC for IPv6. From a privacy
+ My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over
** Summary changed:
- NetworkManager 1.36.6 orders IPv6 addresses incorrectly
+ NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
ht
@seb128 What is the plan for the network-manager package in Ubuntu
jammy-updates? Is it to be left broken until upstream fixes this bug?
Because I think that the problem this last version introduces is a lot
bigger than the problem(s) it solves. Therefore I would say that it can
be defended to upl
Unfortunately I was not tracking jammy-proposed, so I only found out
about this bug when it entered jammy-updates.
I don't think my configuration is that exotic to be honest. Many
companies use DHCPv6 servers giving out static leases, and many
companies use firewalls to restrict incoming (SSH) con
This seems to restore previous behaviour yes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 no longer prefers DHCPv6 addresse
kevin@arcadia:~$ apt info network-manager
Package: network-manager
Version: 1.36.6-0ubuntu2
kevin@arcadia:~$ apt info libnm0
Package: libnm0
Version: 1.36.6-0ubuntu2
I have installed network-manager and libnm0 version 1.36.6-0ubuntu2 from
jammy-proposed. After connecting to a network with both
It's fixed upstream as well now:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6920b6ceb1c2e7856ad76e118ee5b4dd36130735
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https:/
look into, but I figured I would share
my findings. Please let me know if you have any questions or if I can
provide any additional information, troubleshooting, or testing.
Thanks!
-Kevin
** Affects: powermgmt-base (Ubuntu)
Importance: Undecided
Status: New
--
You received this b
Looks like the specific upstream issue is
https://github.deere.com/FOCUS/WineATL/blob/fab575865d1bbceedde12226d2517d17b20189bc/gdb/wine-
add-symbol-file.py
And there's a build for kinetic that contains the fix, which does
actually install and work on jammy (since no other dependencies changed
too
It's fixed upstream on the 2.38 branch too, and kinetic has that update
in binutils-source_2.38-4ubuntu1. So binutils-mingw-w64 just needs to be
recompiled against that latest binutils-source package (no other changes
needed, it already pulls the latest). And ideally an SRU back to jammy
LTS, just
Just tested the linux-firmeware in proposed, it fixed the problem.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2077490
Tit
Public bug reported:
As distribted, the file sshd_config has apparently been modified from an
upstream version -- those lines that are NOT comments. There is no good
way for me to change any of them, even though there is a sshd_config.d
directory for my changes. That is because the files in the
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Kevin bush (akjk32002)
** Changed in: software-properties (Ubuntu Jammy)
Assignee: (unassigned) => Kevin bush (akjk32002)
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
[Summary]
During the kernel SRU testing on focal-hwe, I found the audio output of some
machines are broken.
I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and
haven't seen this happened.
The volume bars in settings react to what sound is played co
** Changed in: alsa-driver (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2007798
Title:
[Inspiron
Public bug reported:
since the upadating to Ubuntu 22.04.2 LTS, i have no sounds from
internet. Sound works from Rhythm box software or videos. I also don't
have "system" sound. The audio device is not detected
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubun
** Tags added: cert-sru
--
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/2051068
Title:
GUI crashed after installed proposed package libegl-mesa0
Status in mesa package in Ubu
Public bug reported:
Sorry for the somewhat weird / vague title; hopefully the rest of this
issue will make it more concrete ...
First, to set the stage; gdb and R both installed from apt repositories:
$ /usr/bin/gdb --version
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Softw
In addition, I get a segfault if I use a single-quoted string rather
than a double-quoted string. (My understanding is that single-quoted
strings are normally used to reference symbols, so this should be an
error but not a crash)
$ /usr/bin/gdb -batch -p $(pgrep -nx R) -ex "print (char*) getenv('o
** Summary changed:
- gdb doesn't work properly when attaching to R
+ gdb 'call' / 'print' commands don't work properly when attaching to R
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad
** Bug watch added: Sourceware.org Bugzilla #28885
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
** Also affects: binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
Importance: Unknown
Status: Unknown
** Also affects: binutils (Ubuntu)
Importance: Undeci
Linking binutils package and subscribing Mattias Klose since
https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu1 mentions
"Update from the binutils 2.38 branch: Fix PR 28885" and so a rebuild
based on binutils-source_2.38-4ubuntu1 would fix this issue.
--
You received this bug notificatio
** Also affects: wine via
https://bugs.winehq.org/show_bug.cgi?id=52770
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/19719
Public bug reported:
I installed Ubuntu 21.10 on my laptop (Lenovo Yoga Slim 14 ARE 05 - AMD
Ryzen 4700 - 1§ GB RAM - 512 GB SSD). Every time I close the lid or let
the laptop go to suspend the system doesn't resume. Clicking the mouse
or pushing the keys doesn't resume the OS.
The only way to re
Public bug reported:
Graphics option in About pane shows "llvmpipe (LLVM 12.0.0, 256 bits)"
$ lspci | grep -E 'VGA|Display'
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05)
$ glxinfo -B
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer i
Public bug reported:
Version: ufw 0.36
Ubuntu Version: 20.04.3 LTS
There doesn't appear to be a Python method for accessing IPv4 and IPv6
rules in a distinguishable manner.
In the source code (root/src/backend.py) there is an object that stores
IPv4 and IPv6 rules in separate lists. Those lists
I now realize that I may have submitted this bug to the wrong location.
Should I submit this to the UFW source site (https://launchpad.net/ufw)
or is it alright to keep it here?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Working on a new app to do full-disk backup and recovery, I'm having
trouble with clearing existing partitions on a target drive. The man
page for wipefs says that wipefs -a should wipe all partitions
on the drive, but I have a situation where it has a strange result:
lsblk
Actually, this ran from a thumb drive, and I was about to update the
whole show to 22.0 LTS. I'm not used to doing updates of just one
package. Can you give some details on how to do that? Or would the
blanket update serve your purpose?
--
You received this bug notification because you are a m
Well, color me baffled. I was all set to try testing before and after
applying the update. But now I cannot make the problem happen. I'll
apply the updates anyway. Feel free to do what makes sense with this
bug report -- mark worksforme, mark as duplicate, whatever.
All I can think of is that
Looks like https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2
is now in the ubuntu-proposed pocket (thanks Matthias!). So binutils-
mingw-w64 would just need a recompile based on that resulting new
binutils-source_2.38-4ubuntu2_all.deb.
I don't think there should be any changes needed to
> Changed in binutils-mingw-w64 (Ubuntu):
> status: Triaged → Fix Released
not fixed in Kinetic yet either; it would be if rebuilt with the
binutils-source there now, but
https://launchpad.net/ubuntu/+source/binutils-mingw-w64/9build1 built on
2022-04-26 is before Mattias brought in PR2885
> And it fixes a VSCode integration issue.
Also Qt Creator. And probably most any other gdb GUI that displays a
"locals" window and therefore might try to display an optimized-out
symbol.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
binutils fix publised to jammy-updates on 2022-10-24, binutils-mingw-w64
would just need a recompile against binutils-source 2.38-4ubuntu2 to fix
this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework
laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device.
Every time wpa-supplicant chooses to associate with a different BSSID
(of the same SSID), the interface ends up being given a new IP address
by the DHCP server (usu
The only upstream bug that seems potentially related is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024
. But that's more about ensuring that WPA auth has completed before
starting the DHCP renewal, and it's not clear to me how blocking ICMP
could avoid that problem. So
** Changed in: binutils (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1971901
Title:
dlltool uses non-unique
The versioning is confusing because this package is not self-contiained.
It gets most of its source code from another package, recorded via
`Built-Using: binutils` in its debian/control file. The actual buggy
code is in binutils-source 2.38-3ubuntu1; binutils-source 2.38-4ubuntu2
contains the fix.
Public bug reported:
Trying to restore a GPT partition table using a dump sfdisk previously
created from a larger disk to a smaller one (but has enough room for the
partitions) fails. I'm using the --force option to try to make this
work. It doesn't. The first line of the output (with added bla
Public bug reported:
According to the man page, $(variable:offset[:length]} should treat
negative offsets as counting from the end of the value. Instead, I find
any such substring expansion expands the ENTIRE variable regardless of
the exact negative offset or any length provided.
A short typesc
Public bug reported:
I have a dump from an M.5 drive named "/dev/nvme0n1" that I wanted to
apply to a regular SCSI drive /dev/sdc. This got the GPT built but when
it tried to work on partitions, it failed, giving the error message
sfdisk: failed to parse partition number: '/dev/sdc'
This is prob
There is probably more going on than I realized. I edited the file so
that all references were to /dev/sdc without those added "p"
characters. It still complained about parsing sdc. Now I'm completely
puzzled and would ask for a better error message.
--
You received this bug notification beca
Color me embarassed. I just tried this again on a different system,
still with the same software, and it worked perfectly, using the same
source and destination drives as when I first had a problem.
Mark this "worksforme" I guess.
--
You received this bug notification because you are a member o
Public bug reported:
Just installed ubuntu 20.04 and the screen has been flickering all
through. tried applying the ubuntu on Wayland solution but no change.
Please help with a solution on workaround for this.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersion
Public bug reported:
This system reports /dev/sda5 will be checked on the next reboot. Maybe
it is (it's EXT4 on as SSD drive, so it could be too fast to notice),
but the message persists even after such a reboot.
I would expect it to go away.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Packag
I would not trust ecryptfs anymore.
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840
Use the time to migrate your data.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
Public bug reported:
This is only an issue if the headphones are plugged in before boot. If I
unplug/plug the headphone jack the audio works just fine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Un
I see that this arises when the script calls pip3 to install a python
package. I'll clean this up to do just that by itself, and re-submit.
Call this one invalid, I guess.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt
Public bug reported:
It may be this is a problem in gmpy itself, but since it is not
installed, ubuntu-bug won't let me report a problem with it.
In any event, I routinely capture the output of package maintenance
tasks, and I'm attaching the output of the most recent run of a shell
script I call
1 - 100 of 2331 matches
Mail list logo
