There's 6.5.0-15 package incoming on mantic-update, does it contains the
fix?
--
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/2039868
Title:
amdgpu reset during usage of
Thanks, I'll try and keep you updated, however I am also facing bug
2039958 (probably a dupe of bug 2034619), so I might still need GNOME
45.1 to be released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Sorry, I did not receive any email for your comment:
- yes, I was on -proposed, so as I said, I had the version with the fix
- I will try to capture those, but I disabled systemd-oomd since, and have not
had issue (at all).
--
You received this bug notification because you are a member of
And FTR I also have 1GB swap, the install is not from Jammy (rather
21.04 or 21.10)
$ LC_ALL=C swapon -s
FilenameTypeSizeUsed
Priority
/dev/dm-2 partition 999420 631852
-2
Was this released ? I've received an update of that package this
morning:
> $ dpkg --list systemd-oomd
> Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
> |
> État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
> |/ Err?=(aucune)/besoin
I gave a try and I can confirm that following the modemmanager docs to
enable FCC unlock procedure at ModemManager level, the modem is properly
unlocked and connects to the internet.
However, this is another issue, but the firmware crashing persist when
trying to make use of the LTE connection a
Thanks, I just saw that Jammy has 1.26.2. I might try and give it a try
to verify the behavior of the LTE modem there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
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:
Closing as invalid, since I can't repro anymore and I can't explain why.
** Changed in: modemmanager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
Trying to investigate
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1949621 I
made a few local backports of modemmanager / libmm / libqmi packages
from next 22.04 (but the source was still too old to handle the modem),
and when I reverted to latest impish version, it seems the bug
** Summary changed:
- libmbim cannot make use of Quectel EM120
+ modemmanager/libmbim cannot make use of Quectel EM120
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
I just had a look and next version of Ubuntu uses ModemMamager 1.18.2 as
of now, so it does not have the handling for FCC unlock procedure.
** Also affects: modemmanager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Running as normal user"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534920/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-34.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Running GNOME Control Center as root (not a good idea, I know), clearly
gets the ModemManager connection to work.
** Attachment added: "GNOME Control Center (root)"
According to the policies in place for ModemManager in
/etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf it looks like
only root can really do something. Assuming this is right, then I'm
wondering why GNOME Control Center tries to directly access ModemManager
instead of going via
NetworkManager itself is able to properly talk to ModemManager:
> $ nmcli con show |grep gsm
> Orange Internet0a196fc4-89e3-479b-b049-ab13dfff897b gsm --
And a `nmcli con "Orange Internet" up` works (assuming you have enabled
the modem which is blocked on
Attached journal taken after following the previously documented STR:
- Open Settings,
- Go to Network tab
--
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/1946481
Title:
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+attachment/5532127/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
The output of `mmcli -L` was already provided above:
> $ mmcli -L
> error: couldn't create manager:
> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 5
> matched rules; type="method_call", sender=":1.269" (uid=1000 pid=48173
> comm="mmcli -L " label="unconfined")
>
> gnome-control-c[49211]: Error connecting to ModemManager:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send
message, 5 matched rules; type="method_call", sender=":1.508" (uid=1000
pid=49211 comm="gnome-control-center " label="unconfined")
Public bug reported:
Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get
access to Modem Manager fails with:
> error: couldn't create manager:
> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied
This was working on 21.04.
STR:
- Open Settings, go to "Network"
OR
-
Looks like https://gitlab.freedesktop.org/mobile-
broadband/ModemManager/-/issues/402#note_1064882 does help, I have been
able to enable my EM120 on 21.10. Take care to change the proper defines
in the provided C code. The `mbim2sar.so` comes from the Snap package
linked above. Thanks to Joar
Sadly, Quectel EM120 is not supported, so I can't use mine on ThinkPad
P14s Gen2 laptop.
--
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/1934286
Title:
Update the
Newer versions of NetworkManager, after upgrading from 17.04, have been
bundling the proper fix.
--
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/1695601
Title:
Same on upgrade from Ubuntu 18.04 to 18.10, fuser -v confirms exclusive
access taken by timidity on the sound device, removing timidity* fixes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Ok, in my case, |fuser -v| reveals that it's being blocked by timidity.
--
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/1799007
Title:
no sound after 18.10 upgrade
I'm also facing the same issue, and "apport-collect 1799007" does not
accept to run for me, stating I'm not on the bug :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I just got confirmation from Beniamino Galvani that this is consistent
with his change. Also, the patch is part of the 1.4 branch and should
be in the next release:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-1-4
--
You received this bug notification because you are a
Public bug reported:
My ISP's router provides IPv6 connectivity and advertises valid lifetime
of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and
previous) installation has been showing weird behavior over IPv6, with
connections dropping quite often but on a regular basis.
After
It is likely to be an upstream problem. Given a zone with A/ records
with enough addresses, I can reproduce the problem.
Hacking in systemd source code, I could find those STR:
- disable "resolve" in nsswitch.conf
- add a resolution against a record with a lot of addresses in
So, comment #5 is somehow invalid, I got the whole story on why it
started to work again: Schiggn (comment #4) contacted some Freenode
staff, and they changed the DNS records to expose less addresses. This
indeed proved to workaround the issue.
--
You received this bug notification because you
Adding back "[NOTFOUND=return] resolve" to /etc/nsswitch.conf, setting
DNSSEC=no in /etc/systemd/resolved.conf, restarting systemd-resolved process
and then:
> $ getent ahosts irc.freenode.net
Gives proper list of hosts
Commenting again the DNSSEC line of resolved.conf, restarting the
service,
Public bug reported:
I am running Ubuntu 16.10 (from a base install upgraded several times),
with proposed-updates enabled. Recently, I started having problems where
I am unable to resolve irc.freenode.net.
This is unrelated to the networks. I have been able to confirm that
systemd-resolved is
A workaround is to remove "[NOTFOUND=return] resolve" from
/etc/nsswitch.conf, though it may break other things (but nothing
visible so far).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
34 matches
Mail list logo
