Re: [PacketFence-users] Google Oauth2 captive portal

[Diego Garcia del Rio via PacketFence-users]

Ciao Leonardo,

For the 1st question, you need a DNS record that makes the PF server
reachable FROM THE CLIENTs. It doesnt need to be reachable at all from the
internet. But the clients need to resolve "pf.mycompany.com" and get an IP
that PF has associated with the portal service. If you're using a
registration vlan where PF is directly the DHCP server (and also DNS and
default gateway) for unregistered clients, then that part should work fine.

For the second option, you can try letsencrypt (but if your server has no
ports exposed to the internet, then it can get a bit complicated).
Otherwise just search for "cheap ssl" .. I use this: https://www.ssls.com/
but your mileage might vary.. depending on which domain you own and how you
can prove you own it. Sssls.com lets you validate via email but you have to
be in control (or at least, in contact) with whoever owned / registered "
mycompany.com"

If you want to test in the meantime, you can try temporarily adding the PF
"fake" certificate (normally untrusted) to your host's certificate store...

but if youre not very familiar with certificates it wont be as easy

cheers


On Sat, May 21, 2022 at 10:29 AM  wrote:

> hi Diego,
>
>
>
>- *there is no need for the PF machine to be publicly reachable. But
>it should have a proper dns name / domain*
>
> Let's take a very simple case: the customer has a pf machine behind an
> Internet router and has an Internet domain like mycompanyname.com and a
> static public IP.
>
> Now, if by publicly reachable you mean the pf console it is clear that it
> is not necessary, however there will be a DNS record that will associate
> the public IP address with pf.mycompanyname.com ", and a port mapping of
> port 443 (https) towards the host corresponding to the machine pf itself
> Right or did I understand nothing?
>
>
>
>- *so yes, the certificate is mandatory. It needs to be trusted by the
>browser, so given you're looking at using this with "guests", then yes, you
>would have to buy a domain or at least a certificate for a host in a domain
>already owned. In this case, the certificate would be for
>"pf.mycompanyname.com <http://pf.mycompanyname.com>"  or something like
>that*
>
> is there an inexpensive service that allows you to purchase SSL
> certificates?
>
>
>
>
>
> thanks always
>
>
>
>
>
> *Da:* Diego Garcia del Rio 
> *Inviato:* venerdì 20 maggio 2022 19:56
> *A:* leonardo.i...@itsinformatica.it
> *Cc:* packetfence-users 
> *Oggetto:* Re: [PacketFence-users] Google Oauth2 captive portal
>
>
>
> Hi leonardo,
>
>
>
> there is no need for the PF machine to be publicly reachable. But it
> should have a proper dns name / domain and valid certificates issued to
> that name (or at least certificates that the client, the laptop pc, can
> trust.)
>
>
>
> If this is a use case with google-for-education domains, then you could
> use the LDAP authentication.
>
>
>
> now, if you dont care about the google usernames (meaning, any user with a
> google account, not just your school / company) then yes, the google-oauth
> path should work.
>
>
>
> I was using it in several deployments but stopped (and switched to the
> secure LDAP) because of the browser restrictions.
>
>
>
> so yes, the certificate is mandatory. It needs to be trusted by the
> browser, so given you're looking at using this with "guests", then yes, you
> would have to buy a domain or at least a certificate for a host in a domain
> already owned. In this case, the certificate would be for "
> pf.mycompanyname.com"  or something like that
>
>
>
> cheers
>
>
>
>
>
> On Fri, May 20, 2022 at 12:00 PM  wrote:
>
> hello Diego and thanks for the reply.
>
> Leaving aside the discussion on mobile devices, and restricting the
> scenario for simplicity to a laptop of a guest who is connected to a wifi
> network and must authenticate on the Internet.
>
> Our client asks that the guest who launches the browser (eg Chrome) from
> his laptop must come up with a captive portal where he is asked to enter
> his Google credentials to authenticate and register his laptop and then be
> able to surf the Internet.
>
> Now let's see if I understand correctly:
>
> the Packetfence machine implemented locally at the customer must be
> reached from the internet using the url: https: // your_portal_hostname /
> oauth2 / callback where is your_portal_hostname is a dns record that allows
> you to reach the Packetfence machine itself from the Internet.
>
> So the customer must have a right internet domain?
>
> Also I understand that it mus

[libreoffice-documentation] Inquiry about contributing documentation

[Diego Vargas]

 Hello,

Hope you're doing well. I'm writing to let you know that I'd like to be a
volunteer for writing documentation for LibreOffice.

For a brief background, I've studied for four years as a Communications
major and have just completed a two-year certificate in Professional and
Technical Communication. I'd like to help write documentation so that I can
expand my technical writing portfolio as well as understand more about the
process of technical writing itself.

I look forward to hearing from you.

Best,

Diego Vargas

-- 
To unsubscribe e-mail to: documentation+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [PacketFence-users] Google Oauth2 captive portal

[Diego Garcia del Rio via PacketFence-users]

Hi leonardo,

there is no need for the PF machine to be publicly reachable. But it should
have a proper dns name / domain and valid certificates issued to that name
(or at least certificates that the client, the laptop pc, can trust.)

If this is a use case with google-for-education domains, then you could use
the LDAP authentication.

now, if you dont care about the google usernames (meaning, any user with a
google account, not just your school / company) then yes, the google-oauth
path should work.

I was using it in several deployments but stopped (and switched to the
secure LDAP) because of the browser restrictions.

so yes, the certificate is mandatory. It needs to be trusted by the
browser, so given you're looking at using this with "guests", then yes, you
would have to buy a domain or at least a certificate for a host in a domain
already owned. In this case, the certificate would be for "
pf.mycompanyname.com"  or something like that

cheers


On Fri, May 20, 2022 at 12:00 PM  wrote:

> hello Diego and thanks for the reply.
>
> Leaving aside the discussion on mobile devices, and restricting the
> scenario for simplicity to a laptop of a guest who is connected to a wifi
> network and must authenticate on the Internet.
>
> Our client asks that the guest who launches the browser (eg Chrome) from
> his laptop must come up with a captive portal where he is asked to enter
> his Google credentials to authenticate and register his laptop and then be
> able to surf the Internet.
>
> Now let's see if I understand correctly:
>
> the Packetfence machine implemented locally at the customer must be
> reached from the internet using the url: https: // your_portal_hostname /
> oauth2 / callback where is your_portal_hostname is a dns record that allows
> you to reach the Packetfence machine itself from the Internet.
>
> So the customer must have a right internet domain?
>
> Also I understand that it must also have a valid https certificate, is
> that so?
>
>
>
> *Da:* Diego Garcia del Rio via PacketFence-users <
> packetfence-users@lists.sourceforge.net>
> *Inviato:* giovedì 19 maggio 2022 21:36
> *A:* packetfence-users 
> *Cc:* Diego Garcia del Rio ; supp...@inverse.ca
> *Oggetto:* Re: [PacketFence-users] Google Oauth2 captive portal
>
>
>
> If you're trying this from a mobile phone (captive portal browser) then
> yes, it will be blocked as google is blocking all embedded browsers and any
> "not-full browsers". It means google authentication can't really be used
> from mobile devices when accessed throguh the captive portal.
>
>
>
> also, your authorized redirect seems wrong. You need to provide a proper,
> REAL HTTPS (with valid certificate) url / server name. NOT "
> pf.packetfence.org/oauth2/callback"
>
>
>
> you need a proper domain name / proper server name.
>
>
>
> On Thu, May 19, 2022 at 10:40 AM leonardo.izzo--- via PacketFence-users <
> packetfence-users@lists.sourceforge.net> wrote:
>
> hi, could you please answer? Thanks
>
>
>
>
>
>
>
> *Da:* leonardo.i...@itsinformatica.it 
> *Inviato:* domenica 15 maggio 2022 15:39
> *A:* 'packetfence-users@lists.sourceforge.net' <
> packetfence-users@lists.sourceforge.net>; 'luza...@akamai.com' <
> luza...@akamai.com>
> *Oggetto:* Google Oauth2 captive portal
>
>
>
> hi, i configured pf for a captive portal with OAuth2 using google.
>
> I followed the instructions in the guide on what to do on
> http://code.google.com/apis/console:
>
> 1) I created a project
>
> 2) I went to "OAuth consent screen" and configured it \ I chose External
> and then Create \ I gave a name and email, then I went on without entering
> anything
>
> 3) I went to Credentials \ Create credentials \ I chose "OAuth client ID"
> \ and then as application type "Web Application" and I gave the name pf
>
> 4) I went under "Authorized redirect URI" \ Add URI \ and I entered the
> string https://pf.packetfence.org/oauth2/callback as in my Packetfence
> console in Configuration \ System Configuration \ General Configuration I
> have pf Domain = packetfence.org and Hostname = pf
>
> 5) I have saved the "client ID" and the "client secret"
>
> 6) I went to the OAuth consent screen \ modify App \ authorized domains
> and entered:
>
> google.com, google.it, etc.
>
> 7) I went to OAuth Consent Screen \ Publish App
>
>
>
> I then created a Google-type external authentication source by entering
> the data created in the previous point.
>
> I then created a connection profile containing this source.
>
>
>
> When I try to connect from a device, I get the following er

Re: [PacketFence-users] Google Oauth2 captive portal

[Diego Garcia del Rio via PacketFence-users]

If you're trying this from a mobile phone (captive portal browser) then
yes, it will be blocked as google is blocking all embedded browsers and any
"not-full browsers". It means google authentication can't really be used
from mobile devices when accessed throguh the captive portal.

also, your authorized redirect seems wrong. You need to provide a proper,
REAL HTTPS (with valid certificate) url / server name. NOT "
pf.packetfence.org/oauth2/callback"

you need a proper domain name / proper server name.

On Thu, May 19, 2022 at 10:40 AM leonardo.izzo--- via PacketFence-users <
packetfence-users@lists.sourceforge.net> wrote:

> hi, could you please answer? Thanks
>
>
>
>
>
>
>
> *Da:* leonardo.i...@itsinformatica.it 
> *Inviato:* domenica 15 maggio 2022 15:39
> *A:* 'packetfence-users@lists.sourceforge.net' <
> packetfence-users@lists.sourceforge.net>; 'luza...@akamai.com' <
> luza...@akamai.com>
> *Oggetto:* Google Oauth2 captive portal
>
>
>
> hi, i configured pf for a captive portal with OAuth2 using google.
>
> I followed the instructions in the guide on what to do on
> http://code.google.com/apis/console:
>
> 1) I created a project
>
> 2) I went to "OAuth consent screen" and configured it \ I chose External
> and then Create \ I gave a name and email, then I went on without entering
> anything
>
> 3) I went to Credentials \ Create credentials \ I chose "OAuth client ID"
> \ and then as application type "Web Application" and I gave the name pf
>
> 4) I went under "Authorized redirect URI" \ Add URI \ and I entered the
> string https://pf.packetfence.org/oauth2/callback as in my Packetfence
> console in Configuration \ System Configuration \ General Configuration I
> have pf Domain = packetfence.org and Hostname = pf
>
> 5) I have saved the "client ID" and the "client secret"
>
> 6) I went to the OAuth consent screen \ modify App \ authorized domains
> and entered:
>
> google.com, google.it, etc.
>
> 7) I went to OAuth Consent Screen \ Publish App
>
>
>
> I then created a Google-type external authentication source by entering
> the data created in the previous point.
>
> I then created a connection profile containing this source.
>
>
>
> When I try to connect from a device, I get the following error:
>
>
>
> Authorization error
>
> Error 400: invalid_request
>
> You can't sign in to this app because it doesn't comply with Google's
> OAuth 2.0 policy for keeping apps secure.
>
>
>
> You can let the app developer know that this app doesn't comply with one
> or more Google validation rules.
>
> Find out more
>
> Request details
>
> The content in this section was provided by the app developer and has not
> been reviewed or verified by Google.
>
> If you developed the app, make sure these request details comply with
> Google's policies.
>
> redirect_uri: https: //  / oauth2 / callback
>
>
>
> Thanks
> ___
> PacketFence-users mailing list
> PacketFence-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

[nexa] [REMINDER] [GI-STS/TSS] AVVISO DI SEMINARIO (in presenza e online) - Le tecnologie per la salute all’epoca del COVID

[Diego Latella]

[Con preghiera di diffusione - scusandomi per eventuali duplicati]

==
AVVISO DI SEMINARIO
==

“Le tecnologie per la salute all’epoca del COVID”
lunedì 23 maggio 2022, alle ore 16:00,
CNR - Area della Ricerca di Pisa - Aula 27 e online

Il seminario è organizzato dal
Gruppo di Lavoro “Tecnologia, Salute e Società” del
Gruppo Interdisciplinare su Scienza, Tecnologia e Società (GI-STS) 
dell’Area della Ricerca di Pisa del CNR


In collaborazione con
Areaperta – Area della Ricerca CNR di Pisa
Caffè della Scienza “N. Badaloni” - Livorno
Gruppo Multimedia, CNR-IFC
Istituto di Fisiologia Clinica del CNR
Istituto di Informatica e Telematica del CNR
Istituto di Scienza e Tecnologie dell'Informazione “A. Faedo'” del CNR
Laboratorio Informatica e Società del CINI
La Nuova Limonaia

Sarà possibile partecipare sia in presenza (massimo 40 posti 
disponibili) che on-line.


PROGRAMMA:

16:00 Saluti Istituzionali

16:10 La telemedicina per la gestione territoriale dei pazienti COVID-19
  Prof. Luca Fanucci (Università di Pisa)

16:30 Neuropsichiatria infantile nell'era COVID19: il ruolo della 
telemedicina

  Dott.ssa Eugenia Conti (ASL Toscana Centro)

16:50 Deep Learning ed ecografia toracica a supporto della gestione dei 
pazienti COVID-19

  Dott. Francesco Faita (CNR-IFC)

17:10 Tavola rotonda e conclusioni


Per ulteriori informazioni - incluso il link per la registrazione 
all’evento in presenza e il link per la partecipazione all’evento online 
- si rimanda alla pagina “Events” (http://gists.pi.cnr.it/events.html) 
del sito web del Gruppo Interdisciplinare su Scienza, Tecnologia e 
Società (GI-STS) dell’Area della Ricerca di Pisa del CNR 
(http://gists.pi.cnr.it)

===
For more information - including the link for in presence registration 
and the link for online participation - please refer to the “Events” 
page (http://gists.pi.cnr.it/events.html) in the web site of the Gruppo 
Interdisciplinare su Scienza, Tecnologia e Società (GI-STS) dell’Area 
della Ricerca di Pisa del CNR (http://gists.pi.cnr.it)


--
Dott. Diego Latella - Senior Researcher CNR/ISTI, Via Moruzzi 1, 56124 Pisa, 
Italy  (http:www.isti.cnr.it)
FM& Lab. (http://fmt.isti.cnr.it)
CNR/GI-STS (http://gists.pi.cnr.it)
https://www.isti.cnr.it/People/D.Latella - ph: +390506212982, fax: +390506212040
===
The quest for a war-free world has a basic purpose: survival.
But if in the process we learn  how to achieve it by love rather than by fear, 
by kindness rather than compulsion;
if in the process we learn how to combine the essential with the enjoyable, the 
expedient with the benevolent,
the practical with the beautiful, this will be an extra incentive to embark on 
this great task.
Above all, remember your humanity.
-- Sir Joseph Rotblat

___
nexa mailing list
nexa@server-nexa.polito.it
https://server-nexa.polito.it/cgi-bin/mailman/listinfo/nexa

[oe] [meta-networking][kirkstone][PATCH] conntrack-tools: fix postinst script

[Diego Sueiro]

From: Kai Kang 

Fix error caused by postinst script of conntrack-tools:

| /var/tmp/rpm-tmp.or09Iq: line 4: unexpected EOF while looking for matching `"'
| %post(conntrack-tools-1.4.6-r0.core2_64): waitpid(1173) rc 1173 status 200
| warning: %post(conntrack-tools-1.4.6-r0.core2_64) scriptlet failed, exit 
status 2

Signed-off-by: Kai Kang 
Signed-off-by: Khem Raj 
---
 .../recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git 
a/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb 
b/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb
index e76238fe0..50f7ced88 100644
--- a/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb
+++ b/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb
@@ -35,5 +35,5 @@ do_install:append() {
 
 # fix error message: Do not forget that you need *root* or CAP_NET_ADMIN 
capabilities ;-)
 pkg_postinst:${PN} () {
-setcap cap_net_admin+ep $D/${sbindir}/conntrack"
-}
\ No newline at end of file
+setcap cap_net_admin+ep "$D/${sbindir}/conntrack"
+}
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#97199): 
https://lists.openembedded.org/g/openembedded-devel/message/97199
Mute This Topic: https://lists.openembedded.org/mt/91210764/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [I2nsf] I2NSF WG status update

[Diego R. Lopez]

Definitely agree with Paul on the session request! We have been discussing the 
way to make a more focused proposal for the re-chartering…

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lo...@telefonica.com<mailto:diego.r.lo...@telefonica.com>
Mobile:  +34 682 051 091
--

On 18/05/2022, 15:56, "I2nsf on behalf of Mr. Jaehoon Paul Jeong" 
mailto:i2nsf-boun...@ietf.org> on behalf of 
jaehoon.p...@gmail.com<mailto:jaehoon.p...@gmail.com>> wrote:

Hi Linda,
Thanks for the announcement of the updates for I2NSF WG.

draft-ietf-i2nsf-nsf-monitoring-data-model-18 is under "Approved-announcement 
to be sent::AD Followup".
The approval announcement will be done today or tomorrow.

draft-ietf-i2nsf-registration-interface-dm-16 has the Document Shepherd Writeup 
be ready:
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-registration-interface-dm/shepherdwriteup/

draft-ietf-i2nsf-consumer-facing-interface-dm-19 has been posted today and its 
Shepherd Writeup will be posted
since Linda has the writeup to post.
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-consumer-facing-interface-dm/

As you said, we need to continue the discussion on the mailing list
to make the objectives align with the expertise of the contributors.

I feel that we need a session at IETF 114 to finalize the proposal
to have a handful of WG items for the next step in I2NSF.

Thanks for your leadership and support for our WG work.

Best Regards,
Paul

On Wed, May 18, 2022 at 5:49 AM Linda Dunbar 
mailto:linda.dun...@futurewei.com>> wrote:
I2NSF WG participants:

Yesterday I2NSF WG reached a big milestone with 2 RFCs being approved by IESG 
for publication. Many thanks to the WG and authors for the tireless work in 
addressing all the comments along the way. It has been a long process.

The IESG has approved the following document:
- 'I2NSF Capability YANG Data Model'
  (draft-ietf-i2nsf-capability-data-model-31.txt) as Proposed Standard

The IESG has approved the following document:
- 'I2NSF Network Security Function-Facing Interface YANG Data Model'
  (draft-ietf-i2nsf-nsf-facing-interface-dm-27.txt) as Proposed Standard

In addition, the draft-ietf-i2nsf-nsf-monitoring-data-model-18 has got enough 
support from IESG review to move forward, now waiting for our AD Roman’s final 
review.

The authors have requested WG LC for the following two I2NSF WG drafts:
draft-ietf-i2nsf-consumer-facing-interface-dm-18
draft-ietf-i2nsf-registration-interface-dm-16

I2NSF Chairs will complete the Shepherd review this week, request early review 
from Ops/Sec Directorates,  and issue the WGLC.

At IETF 113,  we discussed re-chartering proposal. Some people felt that the 
scope of work proposed is exceeding the expertise of the participants.  We need 
to continue the discussion on the mailing list to make the objectives align 
with the expertise of the contributors.

Do people feel that we need a session at IETF114 to finalize the proposal?

Thanks, Linda
___
I2nsf mailing list
I2nsf@ietf.org<mailto:I2nsf@ietf.org>
https://www.ietf.org/mailman/listinfo/i2nsf



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede 
contener información privilegiada o confidencial y es para uso exclusivo de la 
persona o entidad de destino. Si no es usted. el destinatario indicado, queda 
notificado de que la lectura, utilización, divulgación y/o copia sin 
autorización puede estar prohibida en virtud de la legislación vigente. Si ha 
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente 
por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged 
information intended only for the use of the individual or entity named above. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this transmission in error, do not 
read it. Please immediately reply to the sender that you have received this 
communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode 
conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa 
ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica 
notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização 
pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem 
por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e 
proceda a sua destruição
___
I2nsf mailing list
I2nsf@ietf.org
https://www.ietf.org/mailman/listinfo/i2nsf

Re: FAI e dischi "intrusi"

[Diego Zuccato]

Recuperato da "indesiderata"... Mah! Oramai i filtri antispam bidonano 
più messaggi legittimi che spam.


Il 17/05/2022 10:18, Felipe Salvador ha scritto:


immagino tu intenda /dev/sde -> /dev/sdj ...

Nono, proprio sdae :)


La nomenclatura che io ricordi vuole canale>partizone
sda1, sda2, sdb1, sdc1, sdc2, sde1, sdf1 [..]

È una novità?

No, se non specifichi il numero, intendi il raw device.
/dev/sda1 è la prima partizione di /dev/sda .
Nel mio caso non basta una sola lettera per identificare il device, 
quindi il sistema la raddoppia e dopo sdz ho sdaa, sdab ecc.


Meno male che non hanno pensato di usare caratteri Unicode... :)

--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: [oe] [meta-networking][PATCH] conntrack-tools: fix postinst script

[Diego Sueiro]

Hi,

Can we please have this patch backported to the kirkstone branch ASAP since 
builds including this package are currently broken?

Cheers,
Diego Sueiro

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#97156): 
https://lists.openembedded.org/g/openembedded-devel/message/97156
Mute This Topic: https://lists.openembedded.org/mt/91005947/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[oe] [meta-oe][kirkstone][PATCH] bats: upgrade 1.6.0 -> 1.6.1

[Diego Sueiro]

Changelog:
==

Fixed:
--
prevent teardown, teardown_file, and teardown_suite from overriding bats'
exit code by setting $status (e.g. via calling run) (#581, #575)
CRITICAL: this can return exit code 0 despite failed tests, thus preventing
your CI from reporting test failures! The regression happened in version 1.6.0.

Documentation:
--
corrected invalid documentation of run -N (had =N instead) (#579)
CRITICAL: using the incorrect form can lead to silent errors. See issue #578
for more details and how to find out if your tests are affected.

Signed-off-by: Diego Sueiro 
---
 .../recipes-test/bats/{bats_1.6.0.bb => bats_1.6.1.bb}   | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)
 rename meta-oe/recipes-test/bats/{bats_1.6.0.bb => bats_1.6.1.bb} (85%)

diff --git a/meta-oe/recipes-test/bats/bats_1.6.0.bb 
b/meta-oe/recipes-test/bats/bats_1.6.1.bb
similarity index 85%
rename from meta-oe/recipes-test/bats/bats_1.6.0.bb
rename to meta-oe/recipes-test/bats/bats_1.6.1.bb
index 7ea1aa8f3..7d72a5198 100644
--- a/meta-oe/recipes-test/bats/bats_1.6.0.bb
+++ b/meta-oe/recipes-test/bats/bats_1.6.1.bb
@@ -6,9 +6,12 @@ HOMEPAGE = "https://github.com/bats-core/bats-core;
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE.md;md5=2970203aedf9e829edb96a137a4fe81b"
 
-SRC_URI = 
"git://github.com/bats-core/bats-core.git;branch=master;protocol=https"
-# v1.4.1
-SRCREV = "210acf3a8ed318ddedad3137c15451739beba7d4"
+SRC_URI = "\
+  git://github.com/bats-core/bats-core.git;branch=version/1.6.x;protocol=https 
\
+  "
+
+# v1.6.1
+SRCREV = "1977254c2a7faa2e0af17355856f91dc471d1daa"
 
 S = "${WORKDIR}/git"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#97153): 
https://lists.openembedded.org/g/openembedded-devel/message/97153
Mute This Topic: https://lists.openembedded.org/mt/91181156/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: FAI e dischi "intrusi"

[Diego Zuccato]

Grazie Paolo.

In effetti è un limite logico da tenere presente su sistemi molto grandi 
e a basse prestazioni. Pensa ad uno di quegli enclosure con 90 dischi + 
connettore per baie esterne... In pratica, considerando un disco di 
sistema (con RAID HW il SO vede un solo disco), non si potrebbe comunque 
riempire la terza baia esterna da 15 dischi... 90+1+3*15=136 > 128.


Comunque anche per un sistema a basse prestazioni non sarebbe una buona 
situazione. Il costo dei dischi dominerebbe comunque, tanto vale mettere 
due o più chassis. Come fanno per Backblaze.


Il 17/05/2022 11:39, Paolo Miotto ha scritto:


--

Mandi.

Paolo

Il 17/05/22 10:33, Diego Zuccato ha scritto:

Il 17/05/2022 10:30, Giuliano Curti ha scritto:


    La nomenclatura che io ricordi vuole canale>partizone
    sda1, sda2, sdb1, sdc1, sdc2, sde1, sdf1 [..]


Felipe stai confermando il formato sdXN dove la cifra N rappresenta 
la partizione ed il carattere X rappresenta il disco (canale); ma i 
caratteri A-Z sono 26 (alfabeto inglese) e qui si sta parlando di 30 
e oltre dischi; quello schema non funziona più, ci deve essere per 
forza qualcosa di diverso, forse sdXXN?


Confermo. Dopo sdz il sistema rileva sdaa, sdab, ecc. Non so cosa 
faccia dopo sdzz... Magari un giorno lo scoprirò con qualche baia 
aggiuntiva :)


Nella realtà non si riesce ad arrivare a sdzz: secondo TLDP [1] è 
possibile avere solo 128 dischi SCSI, a causa della numerazione dei 
block devices.


Eight block major numbers are reserved for SCSI disks: 8, 65, 66, 67, 
68, 69, 70 and 71. Each major can accommodate 256 minor numbers which, 
in the case of SCSI disks, are subdivided as follows:


[b,8,0]/dev/sda
[b,8,1]/dev/sda1

[b,8,15]   /dev/sda15
[b,8,16]   /dev/sdb
[b,8,17]   /dev/sdb1

[b,8,255]  /dev/sdp15

The disk device names without a trailing digit refer to the whole disk 
(e.g. /dev/sda) while those with a trailing digit refer to one of the 
15 allowable partitions [1] 
<https://tldp.org/HOWTO/SCSI-2.4-HOWTO/dnames.html#FTN.AEN172> within 
that disk.


The remaining 7 SCSI disk block major numbers follow a similar pattern:

[b,65,0]   /dev/sdq
[b,65,1]   /dev/sdq1

[b,65,159] /dev/sdz15
[b,65,160] /dev/sdaa
[b,65,161] /dev/sdaa1

[b,65,255] /dev/sdaf15
[b,66,0]   /dev/sdag
[b,66,1]   /dev/sdag1

[b,66,255] /dev/sdav15

[b,71,255] /dev/sddx15

So there are 128 possible disks (i.e. /dev/sda to /dev/sddx) each 
having up to 15 partitions. By way of contrast, the IDE subsystem 
allows 20 disks (10 controllers each with 1 master and 1 slave) which 
can have up to 63 partitions each.





1: https://tldp.org/HOWTO/SCSI-2.4-HOWTO/dnames.html



--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

[nexa] Finding it hard to get a new job? Robot recruiters might be to blame - Finding it hard to get a new job? Robot recruiters might be to blame - the Guardian

[Diego Latella]

Molto istruttiva la sezione titolata  "How to write a resume in the age 
of AI"; e altrettanto deprimente ...


https://www.theguardian.com/us-news/2022/may/11/artitifical-intelligence-job-applications-screen-robot-recruiters

DL


--
Dott. Diego Latella - Senior Researcher CNR/ISTI, Via Moruzzi 1, 56124 Pisa, 
Italy  (http:www.isti.cnr.it)
FM& Lab. (http://fmt.isti.cnr.it)
CNR/GI-STS (http://gists.pi.cnr.it)
https://www.isti.cnr.it/People/D.Latella - ph: +390506212982, fax: +390506212040
===
The quest for a war-free world has a basic purpose: survival.
But if in the process we learn  how to achieve it by love rather than by fear, 
by kindness rather than compulsion;
if in the process we learn how to combine the essential with the enjoyable, the 
expedient with the benevolent,
the practical with the beautiful, this will be an extra incentive to embark on 
this great task.
Above all, remember your humanity.
-- Sir Joseph Rotblat

___
nexa mailing list
nexa@server-nexa.polito.it
https://server-nexa.polito.it/cgi-bin/mailman/listinfo/nexa

Re: FAI e dischi "intrusi"

[Diego Zuccato]

Il 17/05/2022 10:39, Paolo Miotto ha scritto:

Con la virtualizzazione la parte di bare metal startup ha perso di 
appeal e, secondo me, questo è un punto di forza di FAI.


Beh, in effetti con la virtualizzazione è molto più facile creare 
un'immagine da usare come template per nuove VM.
Però le immagini hanno regolarmente qualche problemino... Se non si sta 
iperattenti quando le si crea, ci si ritrova con tutte le istanze con la 
stessa chiave ssh, o con tracce del MAC address della scheda sbagliata, 
o con il join ad AD che tenta di essere "condiviso" e non funzia più 
niente... :(


FAI è più debole sulla condivisione dei ruoli o delle classi che dir si 
voglia: i file appartenenti ad una classe sono suddivisi tra class, 
hooks, script, ecc. e questo rende più complicato la gestione e la 
condivisione dei ruoli.


In effetti "spalma" molto la configurazione ed è facile scordarsi 
qualche impostazione.


Ora sono passato ad ansible, che gestisce molto bene quest'ultima parte, 
è un po' più organico ma è anche un po' meno "manuale"; in ogni caso non 
gestisce il bare metal startup per cui dubito possa fare al caso tuo in 
cui hai a che fare con il buon vecchio HW.


Sono complementari. Io penso di procedere con FAI per l'installazione 
"base" su bare metal o VM, poi personalizzare la configurazione con 
SaltStack (analogo ad Ansible, ma dovrebbe essere meno "programmatico" e 
più "dichiarativo"... a quanto mi hanno detto: non ho ancora iniziato a 
provarlo).


Come sempre lo strumento va scelto in base all'utilizzo, l'importante è 
mantenere la filosofia dell'Infrastructure as a code, che, oltre a 
automatizzare molti parti ripetitive del lavoro, serve anche per 
documentazione e per rafforzare una disciplina nella gestione delle 
macchine.


Parole sante. Anche perché finché si gestiscono 20 macchine è 
relativamente semplice, ma quando diventano 200 il discorso cambia ed è 
facile scordarsi che quel ferro richiedeva quella specifica impostazione.


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: FAI e dischi "intrusi"

[Diego Zuccato]

Il 17/05/2022 10:30, Giuliano Curti ha scritto:


La nomenclatura che io ricordi vuole canale>partizone
sda1, sda2, sdb1, sdc1, sdc2, sde1, sdf1 [..]


Felipe stai confermando il formato sdXN dove la cifra N rappresenta la 
partizione ed il carattere X rappresenta il disco (canale); ma i 
caratteri A-Z sono 26 (alfabeto inglese) e qui si sta parlando di 30 e 
oltre dischi; quello schema non funziona più, ci deve essere per forza 
qualcosa di diverso, forse sdXXN?


Confermo. Dopo sdz il sistema rileva sdaa, sdab, ecc. Non so cosa faccia 
dopo sdzz... Magari un giorno lo scoprirò con qualche baia aggiuntiva :)


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: FAI e dischi "intrusi"

[Diego Zuccato]

Il 17/05/2022 08:26, Paolo Miotto ha scritto:

disco in base alle caratteristiche (tipo "se è superiore a 10T 
ignoralo) e non alla posizione?

Non uso più FAI,


Posso chiedere come mai e cosa usi ora? Magari va a finire che non 
valeva la pena di usare FAI... Meglio scoprirlo adesso prima di fare il 
redeploy che dopo :)


ma a suo tempo avevo il problema di distinguere i 
dischi locali da quelli della SAN in fibra, e l'avevo risolto con un 
hook (hooks/sysinfo.DEFAULT.source) che modificava la variabile disklist 
di FAI prima del partizionamento.


Grazie! Trovata ora la sezione "Hooks": 
https://fai-project.org/fai-guide/#hooks


Non è esattamente il tuo problema ma il principio è lo stesso: se riesci 
a discernere quali sono i dischi di sistema da shell allora puoi 
compilarti un elenco di dischi da passare a FAI che contenga solo quelli 
che vuoi fargli vedere.


Yup. La logica è analoga.

Se non sbaglio sul sito di FAI c'era anche della documentazione sul 
problema del renaming dei dischi.

Oppure puoi vedere se riesci a giocare con udev.


Non dovrebbe essere necessario scomodare udev. Spero: ogni volta è un 
bagno di sangue... :(


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: FAI e dischi "intrusi"

[Diego Zuccato]

Il 16/05/2022 16:51, Marco Ciampa ha scritto:

Prima ci sono 30 dischi (che dovrebbero diventare 36) per i dati.

Urca, ti ho già detto che ti invidio? Modello / foto della "bestia"?


C'è poco da invidiare. Sono bruttarelli :)
https://www.supermicro.com/en/products/chassis/4u/847/sc847be2c-r1k23lpb

E ormai ci sono anche i modelli che gestiscono fino a 90 HDD 3.5" in 4U:
https://www.supermicro.com/en/products/top-loading-storage


Mi arrendo, ma un dubbio mi sorge spontaneo (che non ti serve ma soddisfa
la mia curiosità...). Usi il FAI perché... mi sorge un dubbio ... ma
quante ne hai di queste "bestie"?


Attualmente 3 con 30 dischi SATA da 12TB, con Gluster in "replica 3 
arbiter 1" (2 copie dei dati, tre dei metadati). Però l'uso interattivo 
è decisamente lento, anche se hanno 192G di RAM. :(


FAI mi serve sia per poter automatizzare l'installazione di probabili 
altri futuri nodi di storage che, soprattutto, per i nuovi nodi di 
calcolo: quando qualcuno acquista qualche nodo, vorrebbe poterlo usare 
subito, e attualmente mi serviva quasi una giornata per l'installazione 
di ogni nodo. Salvo altri problemi :( Con FAI posso avere in "poco" una 
base sempre uguale, da personalizzare poi con Salt o Ansible (devo 
ancora guardarci...).


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

[oe] [meta-oe][PATCH] bats: upgrade 1.6.0 -> 1.6.1

[Diego Sueiro]

The 1.6.1 incorporates the
0001-Fix-status-in-teardown-overriding-exit-code.patch backport patch.

Changelog:
==

Fixed:
--
prevent teardown, teardown_file, and teardown_suite from overriding bats'
exit code by setting $status (e.g. via calling run) (#581, #575)
CRITICAL: this can return exit code 0 despite failed tests, thus preventing
your CI from reporting test failures! The regression happened in version 1.6.0.

Documentation:
--
corrected invalid documentation of run -N (had =N instead) (#579)
CRITICAL: using the incorrect form can lead to silent errors. See issue #578
for more details and how to find out if your tests are affected.

Signed-off-by: Diego Sueiro 
---
 .../bats/{bats_1.6.0.bb => bats_1.6.1.bb} |   7 +-
 ...tus-in-teardown-overriding-exit-code.patch | 150 --
 2 files changed, 3 insertions(+), 154 deletions(-)
 rename meta-oe/recipes-test/bats/{bats_1.6.0.bb => bats_1.6.1.bb} (82%)
 delete mode 100644 
meta-oe/recipes-test/bats/files/0001-Fix-status-in-teardown-overriding-exit-code.patch

diff --git a/meta-oe/recipes-test/bats/bats_1.6.0.bb 
b/meta-oe/recipes-test/bats/bats_1.6.1.bb
similarity index 82%
rename from meta-oe/recipes-test/bats/bats_1.6.0.bb
rename to meta-oe/recipes-test/bats/bats_1.6.1.bb
index df81595c9..7d72a5198 100644
--- a/meta-oe/recipes-test/bats/bats_1.6.0.bb
+++ b/meta-oe/recipes-test/bats/bats_1.6.1.bb
@@ -7,12 +7,11 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE.md;md5=2970203aedf9e829edb96a137a4fe81b"
 
 SRC_URI = "\
-  git://github.com/bats-core/bats-core.git;branch=master;protocol=https \
-  file://0001-Fix-status-in-teardown-overriding-exit-code.patch \
+  git://github.com/bats-core/bats-core.git;branch=version/1.6.x;protocol=https 
\
   "
 
-# v1.6.0
-SRCREV = "210acf3a8ed318ddedad3137c15451739beba7d4"
+# v1.6.1
+SRCREV = "1977254c2a7faa2e0af17355856f91dc471d1daa"
 
 S = "${WORKDIR}/git"
 
diff --git 
a/meta-oe/recipes-test/bats/files/0001-Fix-status-in-teardown-overriding-exit-code.patch
 
b/meta-oe/recipes-test/bats/files/0001-Fix-status-in-teardown-overriding-exit-code.patch
deleted file mode 100644
index f4b1db931..0
--- 
a/meta-oe/recipes-test/bats/files/0001-Fix-status-in-teardown-overriding-exit-code.patch
+++ /dev/null
@@ -1,150 +0,0 @@
-From aa628ccdc4dec1c129c1bd98b53ef94d8c2e119a Mon Sep 17 00:00:00 2001
-From: Richard Neill 
-Date: Mon, 9 May 2022 12:20:48 +0100
-Subject: [PATCH] Fix status in teardown* overriding exit code
-
-Patch fixes regression which produces false-negatives in v1.6.0, where the
-teardown function can cause BATS to report success even if test cases fail.
-Fixes: https://github.com/bats-core/bats-core/issues/575
-
-Upstream-Status: Backport [Adapted from 
https://github.com/bats-core/bats-core/commit/5f372058b05f817e4e3a8dab27f83c30fd467504]
-Signed-off-by: Richard Neill 

- libexec/bats-core/bats-exec-file  | 18 --
- libexec/bats-core/bats-exec-suite | 12 ++--
- libexec/bats-core/bats-exec-test  |  8 
- 3 files changed, 18 insertions(+), 20 deletions(-)
-
-diff --git a/libexec/bats-core/bats-exec-file 
b/libexec/bats-core/bats-exec-file
-index 298441b..63452c7 100755
 a/libexec/bats-core/bats-exec-file
-+++ b/libexec/bats-core/bats-exec-file
-@@ -118,7 +118,6 @@ bats_run_teardown_file() {
-
- bats_file_teardown_trap() {
-   bats_run_teardown_file
--  local status=0
-   bats_file_exit_trap
- }
-
-@@ -144,9 +143,9 @@ bats_file_exit_trap() {
- bats_print_failed_command "${stack_trace[@]}" >&3
- bats_prefix_lines_for_tap_output < "$BATS_OUT" | bats_replace_filename >&3
- rm -rf "$BATS_OUT"
--status=1
-+bats_exec_file_status=1
-   fi
--  exit $status
-+  exit $bats_exec_file_status
- }
-
- function setup_file() {
-@@ -250,15 +249,15 @@ bats_read_tests_list_file() {
- }
-
- bats_run_tests() {
--  status=0
-+  bats_exec_file_status=0
-
-   if [[ "$num_jobs" != 1 && "${BATS_NO_PARALLELIZE_WITHIN_FILE-False}" == 
False ]]; then
- export BATS_SEMAPHORE_NUMBER_OF_SLOTS="$num_jobs"
--bats_run_tests_in_parallel "$BATS_RUN_TMPDIR/parallel_output" || status=1
-+bats_run_tests_in_parallel "$BATS_RUN_TMPDIR/parallel_output" || 
bats_exec_file_status=1
-   else
- for test_name in "${tests_to_run[@]}"; do
-   if [[ "${BATS_INTERRUPTED-NOTSET}" != NOTSET ]]; then
--status=130 # bash's code for SIGINT exits
-+bats_exec_file_status=130 # bash's code for SIGINT exits
- break
-   fi
-   # Only handle non-empty lines
-@@ -267,14 +266,13 @@ bats_run_tests() {
- ((++test_number_in_file))
- # deal with empty flags to avoid spurious "unbound variable" errors 
on Bash 4.3 and lower
- if [[ "${#flags[@]}" -gt 0 ]]; then
--  

Re: FAI e dischi "intrusi"

[Diego Zuccato]

Ciao Marco.

Il 16/05/2022 10:29, Marco Ciampa ha scritto:


va a finire in coda ai dischi dati (ora è sdae ma quando inserirò tutti gli
altri finirà come sdaj o giù di lì).

immagino tu intenda /dev/sde -> /dev/sdj ...

Nono, proprio sdae :)
Prima ci sono 30 dischi (che dovrebbero diventare 36) per i dati.


C'è un qualche modo per dire al partizionatore di identificare il disco in
base alle caratteristiche (tipo "se è superiore a 10T ignoralo) e non alla
posizione?

Non credo. L'identificazione tramite UUID è stata inventata proprio per
questa ragione.
Il fatto è che FAI le partizioni deve crearle: arriva un server nuovo 
con 30 dischi dati e un RAID 1 per il SO (tutti probabilmente non 
partizionati), inserisco in FAI il MAC address e le classi da 
utilizzare, lo imposto per il boot via rete e mi ritrovo un server quasi 
completamente installato senza rischiare di scordarmi qualcosa per strada.
Gli ultimi ritocchi alla config li farei fare a Salt o Ansible, così da 
non dover "mai" mettere mano direttamente sui server (o, peggio, dover 
tenere allineati i nodi di calcolo del cluster).


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

[ovirt-users] Re: failed to mount hosted engine gluster storage - how to debug?

[Diego Ercolani]

Same problem after upgrade to 4.5.0.2
I've reapplied the patch to make it work againt so please tell upstream

yum --enablerepo=baseos install patch
cd /
patch -p0 

FAI e dischi "intrusi"

[Diego Zuccato]

Ciao a tutti.

Sto finalmente iniziando ad usare FAI per automatizzare le installazioni 
e mi trovo in un caso un po' strano.
In pratica, su alcuni server, il disco del sistema non è il primo (sda) 
ma va a finire in coda ai dischi dati (ora è sdae ma quando inserirò 
tutti gli altri finirà come sdaj o giù di lì).
C'è un qualche modo per dire al partizionatore di identificare il disco 
in base alle caratteristiche (tipo "se è superiore a 10T ignoralo) e non 
alla posizione?


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: [utenti-it] installazione su Debian 11

[Diego Maniacco]

LibreOffice non presenta problemi.


On Sunday, 15 May 2022, Valerio Messina  wrote:
> ciao,
> OO 4.1.12 si installava bene su Debian 10
>
> Oggi ho aggiornato a Debian 11, ma OO mi da questo errore con tutti i
pacchetti .deb:
>
> $ sudo dpkg -i openoffice-core04_4.1.12-1_amd64.deb
> Running:'dpkg -i openoffice-core04_4.1.12-1_amd64.deb'
> dpkg: informazioni su openoffice-core04_4.1.12-1_amd64.deb che contiene
openoffice-core04:
>  libreoffice-common è in conflitto con openoffice.org-unbundled
>   openoffice-core04 fornisce openoffice.org-unbundled e sta per essere
installato.
>
> dpkg: errore nell'elaborare l'archivio
openoffice-core04_4.1.12-1_amd64.deb (--install):
>  pacchetti in conflitto - openoffice-core04 non verrà installato
> Si sono verificati degli errori nell'elaborazione:
>  openoffice-core04_4.1.12-1_amd64.deb
>
>
>
> Ovviamente il pacchetto "openoffice.org-unbundled" non è installato
> $ sudo dpkg -r openoffice.org-unbundled
> Running:'dpkg -r openoffice.org-unbundled'
> dpkg: attenzione: viene ignorata la richiesta di rimuovere
openoffice.org-unbundled poiché non è installato
>
>
> Sapete come risolvere?
>
> grazie,
> --
> Valerio
>
> -
> To unsubscribe, e-mail: utenti-it-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: utenti-it-h...@openoffice.apache.org
>
>

-- 
---
Diego Maniacco, Bolzano (Italy)
diego.mania...@gmail.com
---

[image: Not f'd — you won't find me on Facebook] <https://www.fsf.org/fb>
Not f'd — you won't find me on FacebookNot wa'd — you won't find me on WhatsApp

[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Diego Viola]

Same problem here with a Logitech C505 on Ubuntu 22.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in cheese package in Ubuntu:
  Invalid
Status in clutter-gst-3.0 package in Ubuntu:
  Fix Released
Status in clutter-gst-3.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  ==
  The cheese app is unusable with color bands showing in the main view.

  This bug doesn't affect all webcams. It's unknown what percentage of
  webcams are affected.

  Test Case
  
  On a system that experiences this bug:
  Install the update
  Run the cheese app
  Verify that the main view shows what your webcam can see normally.
  Click the camera button in the bottom toolbar area.
  Check if the photo looks normal. You can find it in ~/Pictures/Webcam

  What Could Go Wrong
  ===
  Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint

  clutter-gst has been archived by GNOME. (It's recommended for apps to
  use GTK4 instead of GTK3 + Clutter). That means it's not possible for
  this patch to be accepted upstream. Instead, distros like Arch Linux
  are applying this patch.

  This patch removes 2 renderers that don't work (RGBx and BGRx) but
  still keeps ones that do work: RGBA and BRGA.

  Original Bug Report
  ===
  The cheese application produces a corrupted display under Ubuntu 22.04 with a 
Logitech C525 webcam. When started from the command line, cheese produces 
repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev 

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Diego Viola]

Same problem here with a Logitech C505 on Ubuntu 22.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications

[Diego Agulló]

https://bugs.kde.org/show_bug.cgi?id=451612

--- Comment #21 from Diego Agulló  ---
Maybe it's a bit early to tell, but it happened again. However, this time I
noticed something different: the crass didn't happen until I made a few windows
border-less (window menu -> more actions -> no border - apologies if those are
not the English strings, but I have my system configured in a different
language). After doing this and alt+tab'ing, it crashed almost immediately.
Maybe a coincidence, but still.



Application: kwin_x11 (5.24.5)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.14.0-1024-oem x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.5 [KCrashBackend]

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140283062248768)
at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140283062248768) at
./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=140283062248768, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#7  0x7f9636bd1476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7f9636bb77f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x7f962a710144 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#10 0x7f962b37938f in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#11 0x7f962a976782 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#12 0x7f963982e384 in KWin::WindowThumbnailItem::updateOffscreenTexture
(this=0x55fc843b0a10) at ./src/scripting/thumbnailitem.cpp:432
#13 0x7f9637d49783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f9639805c98 in KWin::Scene::paintScreen (this=0x55fc8328ee10,
damage=..., repaint=..., updateRegion=0x7ffc2a3b09d0,
validRegion=0x7ffc2a3b09c8, renderLoop=, projection=...) at
./src/scene.cpp:282
#15 0x7f96398c7060 in KWin::SceneOpenGL::paint (this=0x55fc8328ee10,
output=0x0, damage=..., toplevels=..., renderLoop=0x55fc82e862f0) at
./src/scenes/opengl/scene_opengl.cpp:259
#16 0x7f9639768071 in KWin::Compositor::composite (this=0x55fc82e86b90,
renderLoop=0x55fc82e862f0) at ./src/composite.cpp:633
#17 0x7f9639771a06 in KWin::X11Compositor::composite (this=0x55fc82e86b90,
renderLoop=) at ./src/composite.cpp:844
#18 0x7f9637d49783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f9639727b16 in KWin::RenderLoop::frameRequested (this=, _t1=) at
./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206
#20 0x7f96397f4297 in KWin::RenderLoopPrivate::dispatch
(this=0x55fc82e85640) at ./src/renderloop.cpp:150
#21 0x7f9637d49783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f9637d4d7ee in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f9637d3f32f in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f96372e8713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f9637d11e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f9637d6a3db in QTimerInfoList::activateTimers() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f9637d68897 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f9631855142 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#29 0x7f9637d1074b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f9637d18ce4 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x55fc82ad4bad in main (argc=, argv=0x7ffc2a3b13d8) at
./src/main_x11.cpp:482
[Inferior 1 (process 6282) detached]

Informar a https://bugs.kde.org/

-- 
You are receiving this mail because:
You are watching all bug changes.

[ovirt-users] Re: grafana @ ovirt 4.5.0.6 "origin not allowed"

[diego . ercolani]

in ovirt-engine-4.5.0.8 I had to reapply the workaround so the problem seem to 
be here
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CAOEV56NNQA6ZGMDAJL7HIYHXO64MKZR/

[kwin] [Bug 451612] Kwin crashes in KWin::WindowThumbnailItem::updateOffscreenTexture() when switching applications

[Diego Agulló]

https://bugs.kde.org/show_bug.cgi?id=451612

--- Comment #20 from Diego Agulló  ---
(In reply to Nate Graham from comment #18)
> Cool, thanks. Diego, can you reproduce the issue in 5.24.5?

Thanks Nate and every reporter!

I just installed 5.24.5 (with debug symbols) and will get back to you in a few
days, as suggested by Oleksandr, since we haven't found a way to reliably
reproduce the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[oe] [meta-oe][PATCH] conntrack-tools: Fix package installation during do_rootfs

[Diego Sueiro]

Fix the following error message:

do_rootfs: Postinstall scriptlets of ['conntrack-tools'] have failed. If the 
intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget:${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.

Signed-off-by: Diego Sueiro 
---
 .../recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git 
a/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb 
b/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb
index e76238fe0..28dfc0325 100644
--- a/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb
+++ b/meta-networking/recipes-filter/conntrack-tools/conntrack-tools_1.4.6.bb
@@ -34,6 +34,6 @@ do_install:append() {
 }
 
 # fix error message: Do not forget that you need *root* or CAP_NET_ADMIN 
capabilities ;-)
-pkg_postinst:${PN} () {
-setcap cap_net_admin+ep $D/${sbindir}/conntrack"
-}
\ No newline at end of file
+pkg_postinst_ontarget:${PN} () {
+setcap cap_net_admin+ep ${sbindir}/conntrack"
+}
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#97035): 
https://lists.openembedded.org/g/openembedded-devel/message/97035
Mute This Topic: https://lists.openembedded.org/mt/91034874/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: Interfacce di rete che non si attivano

[Diego Zuccato]

Grazie delle risposte. Purtroppo leggo solo ora: erano finite in spam :(

Avevo anche chiesto sul forum di Proxmox:
https://forum.proxmox.com/threads/kernel-5-13-19-4-pve-breaks-e1000e-networking.108141/

Alla fine il problema era che l'attivazione della rete dipende da udev, 
che fa una scansione con pvscan, il quale tenta di accedere ad un 
multipath che non risponde (canale "passive" del link alla CX3-80) 
malgrado sia filtrato nel file /etc/lvm/lvm.conf .


Per un po' ho tenuto il kernel più vecchio, poi ieri ho provato a 
spostare il global_filter nella sezione che viene aggiunta da Proxmox 
(modificando la sua riga) e anche aggiornando all'ultimo pare 
funzionare. Dovrò provare se lo spostamento del global_filter è 
necessario o se avevano risolto con gli altri aggiornamenti.


Diego

Il 19/04/2022 10:16, Roberto Resoli ha scritto:

Il 15/04/22 09:33, Diego Zuccato ha scritto:

Ciao a tutt*

Ieri ho riavviato alcuni dei server Proxmox e mi sono ritrovato con 
due che non riattivano la rete.


Versione di proxmox? Sarebbe utile capire anche il livello di 
aggiornamento dei vari pacchetti, usando il bottone "Package Versions" 
nel "Summary" del server.


La configurazione in /etc/network/interfaces è uguale (a meno dell'IP) 
a quella di altri server che invece ripartono correttamente.


ok, anche qui la configurazione sarebbe di aiuto.


Qualche consiglio su dove cercare?


Il forum PVE di Proxmox può sicuramente esserti di aiuto:

https://forum.proxmox.com/forums/proxmox-ve-installation-and-configuration.16/ 



ciao,
rob



--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

[ovirt-users] Re: grafana @ ovirt 4.5.0.6 "origin not allowed"

[diego . ercolani]

Yes, that worked, I saw this solution but was referred to an old ovirt-engine 
version, is this a regression issue?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XP2STLM3F2L7FBO4HHWMGUTMUOSW65M3/

[ovirt-users] Re: grafana @ ovirt 4.5.0.6 "origin not allowed"

[diego . ercolani]

I tried but obtaining the same message.
Keep in mind that I cannot see any data from grafana wichever dashboard I try 
to visualize I obtain a plenty of popup saying:
"Error updating options: origin not allowed"
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MRGA7FT2WP7O7Z7KTM5YZDDXOM4RCHT2/

[ovirt-users] grafana @ ovirt 4.5.0.6 "origin not allowed"

[diego . ercolani]

Hello,
in my current new installation ovirt-engine-4.5.0.6-1.el8.noarch I have a 
problem setting up the grafana monitoring portal.
I'm supposing that there is some problem regarding connection to ovirt DWH DB.

I tested the credentials stored in 
/etc/grafana/conf/provisioning/datasources/ovirt-dwh.yaml of the ovirt-engine 
and with psql it seem to work and also the DWH is populated by the engine.

But

connecting to configuration->data sources and trying to reconfigure the ovirt 
dwh datasource, when you click on "save & test" it appears a popup telling that 
the "origin not allowed".
I cannot find anything in the grafana log or the httpd log.
Can you help?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6USYSPBHOVD4JMOQZMZVEFOPNXJIJMBS/

[Bug 1971435] Re: Modem Manager gui crashed

[Diego A. Elizondo]

Model: Huawei E303

It seems that the problem is related to the chosen connection manager,
with pppd the app opens allowing to send messages and USSD codes but it
does not have support to manage internet connections, and if I choose
the Network Manager the app just closes

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971435

Title:
  Modem Manager gui crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1971435/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [go-nuts] how is xml.Decoder.CharsetReader supposed to be held?

[Diego Joss]

Does this work for you?

https://go.dev/play/p/xLRawVhcRtF

-- Diego

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAGjxhKmCJWczpUhtgyWsn0dJ1_E9PcTUBOZW112bGsVQyMZq0g%40mail.gmail.com.

[jenkinsci/subversion-plugin] 60583b: [maven-release-plugin] prepare for next developmen...

['Diego Díez Ricondo' via Jenkins Commits]

  Branch: refs/heads/master

  Home:   https://github.com/jenkinsci/subversion-plugin

  Commit: 60583bcf95f47e54c9bb01d4a458c69afab0c917

  
https://github.com/jenkinsci/subversion-plugin/commit/60583bcf95f47e54c9bb01d4a458c69afab0c917

  Author: Diego Díez 

  Date:   2022-05-05 (Thu, 05 May 2022)



  Changed paths:

M pom.xml



  Log Message:

  ---

  [maven-release-plugin] prepare for next development iteration





-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/subversion-plugin/push/refs/heads/master/108e6e-60583b%40github.com.

[jenkinsci/subversion-plugin]

['Diego Díez Ricondo' via Jenkins Commits]

  Branch: refs/tags/subversion-2.15.5
  Home:   https://github.com/jenkinsci/subversion-plugin

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/subversion-plugin/push/refs/tags/subversion-2.15.5/00-66a9b8%40github.com.

[jenkinsci/subversion-plugin] 108e6e: [maven-release-plugin] prepare release subversion-...

['Diego Díez Ricondo' via Jenkins Commits]

  Branch: refs/heads/master

  Home:   https://github.com/jenkinsci/subversion-plugin

  Commit: 108e6e2b9abc07f43d29af252c50de934dfb302e

  
https://github.com/jenkinsci/subversion-plugin/commit/108e6e2b9abc07f43d29af252c50de934dfb302e

  Author: Diego Díez 

  Date:   2022-05-05 (Thu, 05 May 2022)



  Changed paths:

M pom.xml



  Log Message:

  ---

  [maven-release-plugin] prepare release subversion-2.15.5





-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/subversion-plugin/push/refs/heads/master/c1023b-108e6e%40github.com.

[jenkinsci/subversion-plugin] 9e3e7f: Use inclusive naming in plugin docs

['Diego Díez Ricondo' via Jenkins Commits]

  Branch: refs/heads/master

  Home:   https://github.com/jenkinsci/subversion-plugin

  Commit: 9e3e7f9bd793241106ca96521afcb8ea9f4a0be5

  
https://github.com/jenkinsci/subversion-plugin/commit/9e3e7f9bd793241106ca96521afcb8ea9f4a0be5

  Author: Mark Waite 

  Date:   2022-05-04 (Wed, 04 May 2022)



  Changed paths:

M README.md



  Log Message:

  ---

  Use inclusive naming in plugin docs



Master -> controller

Slave -> agent





  Commit: b21c65b2f0f95166b2769ccdccd3d14abe9daa31

  
https://github.com/jenkinsci/subversion-plugin/commit/b21c65b2f0f95166b2769ccdccd3d14abe9daa31

  Author: Mark Waite 

  Date:   2022-05-04 (Wed, 04 May 2022)



  Changed paths:

M src/main/java/hudson/scm/subversion/WorkspaceUpdater.java



  Log Message:

  ---

  Inclusive naming for javadoc





  Commit: 3b4ede0db0fe155dfac731306384be2d0f3a8ecd

  
https://github.com/jenkinsci/subversion-plugin/commit/3b4ede0db0fe155dfac731306384be2d0f3a8ecd

  Author: Mark Waite 

  Date:   2022-05-04 (Wed, 04 May 2022)



  Changed paths:

M src/main/java/hudson/scm/SubversionWorkspaceSelector.java



  Log Message:

  ---

  Inclusive naming in a javadoc comment





  Commit: c1023b873ae1179c046e1cb72c9a466dcbe215e2

  
https://github.com/jenkinsci/subversion-plugin/commit/c1023b873ae1179c046e1cb72c9a466dcbe215e2

  Author: Diego Díez Ricondo 

  Date:   2022-05-05 (Thu, 05 May 2022)



  Changed paths:

M README.md

M src/main/java/hudson/scm/SubversionWorkspaceSelector.java

M src/main/java/hudson/scm/subversion/WorkspaceUpdater.java



  Log Message:

  ---

  Merge pull request #272 from MarkEWaite/patch-2



Inclusive naming in docs and javadoc





Compare: 
https://github.com/jenkinsci/subversion-plugin/compare/5ee0140ae092...c1023b873ae1

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/subversion-plugin/push/refs/heads/master/5ee014-c1023b%40github.com.

[jenkinsci/subversion-plugin] a79d3e: Add description for plugin manager

['Diego Díez Ricondo' via Jenkins Commits]

  Branch: refs/heads/master

  Home:   https://github.com/jenkinsci/subversion-plugin

  Commit: a79d3e24b1fda7eec341a3ee03c9b190b17968d1

  
https://github.com/jenkinsci/subversion-plugin/commit/a79d3e24b1fda7eec341a3ee03c9b190b17968d1

  Author: Zbynek Konecny 

  Date:   2022-04-19 (Tue, 19 Apr 2022)



  Changed paths:

A src/main/resources/index.jelly



  Log Message:

  ---

  Add description for plugin manager





  Commit: cef6da586a9c54199b29e2cdd5f3ca87dc025a5a

  
https://github.com/jenkinsci/subversion-plugin/commit/cef6da586a9c54199b29e2cdd5f3ca87dc025a5a

  Author: Zbynek Konecny 

  Date:   2022-04-19 (Tue, 19 Apr 2022)



  Changed paths:

M src/main/resources/index.jelly



  Log Message:

  ---

  Open link in a new window



Co-authored-by: Jesse Glick 





  Commit: 6cc65be55e715a95253b5dd51fb3de70d88f4ad0

  
https://github.com/jenkinsci/subversion-plugin/commit/6cc65be55e715a95253b5dd51fb3de70d88f4ad0

  Author: Diego Díez Ricondo 

  Date:   2022-05-05 (Thu, 05 May 2022)



  Changed paths:

M .mvn/extensions.xml

M pom.xml

M src/main/java/hudson/scm/SubversionSCM.java

M src/main/java/hudson/scm/SubversionTagAction.java

M src/main/java/hudson/scm/UserProvidedCredential.java

M src/main/java/hudson/scm/browsers/VisualSVN.java

M src/main/java/hudson/scm/subversion/CheckoutUpdater.java

M src/main/resources/index.jelly

M src/test/java/hudson/scm/CompareAgainstBaselineCallableTest.java



  Log Message:

  ---

  Merge branch 'master' into patch-1





  Commit: 5ee0140ae0920244071b78b7c9b5738ad665a8f6

  
https://github.com/jenkinsci/subversion-plugin/commit/5ee0140ae0920244071b78b7c9b5738ad665a8f6

  Author: Diego Díez Ricondo 

  Date:   2022-05-05 (Thu, 05 May 2022)



  Changed paths:

M src/main/resources/index.jelly



  Log Message:

  ---

  Merge pull request #270 from zbynek/patch-1



Add description for plugin manager





Compare: 
https://github.com/jenkinsci/subversion-plugin/compare/3cda03616f54...5ee0140ae092

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/subversion-plugin/push/refs/heads/master/3cda03-5ee014%40github.com.

[jenkinsci/subversion-plugin] 6b466b: Update plugin parent POM and plugin BOM

['Diego Díez Ricondo' via Jenkins Commits]

  Branch: refs/heads/master

  Home:   https://github.com/jenkinsci/subversion-plugin

  Commit: 6b466b556a213aa085b5763d70729b044ded8e6f

  
https://github.com/jenkinsci/subversion-plugin/commit/6b466b556a213aa085b5763d70729b044ded8e6f

  Author: Basil Crow 

  Date:   2022-04-24 (Sun, 24 Apr 2022)



  Changed paths:

M .mvn/extensions.xml

M pom.xml

A src/main/resources/index.jelly



  Log Message:

  ---

  Update plugin parent POM and plugin BOM





  Commit: 2a4203d4a044b6c1fea3f3c36802e6da0eced478

  
https://github.com/jenkinsci/subversion-plugin/commit/2a4203d4a044b6c1fea3f3c36802e6da0eced478

  Author: Basil Crow 

  Date:   2022-04-24 (Sun, 24 Apr 2022)



  Changed paths:

M pom.xml

M src/main/java/hudson/scm/SubversionSCM.java

M src/main/java/hudson/scm/SubversionTagAction.java

M src/main/java/hudson/scm/UserProvidedCredential.java

M src/main/java/hudson/scm/browsers/VisualSVN.java

M src/main/java/hudson/scm/subversion/CheckoutUpdater.java



  Log Message:

  ---

  SpotBugs





  Commit: 79b5d36d9a9e52a090c99ba93adde09d23444053

  
https://github.com/jenkinsci/subversion-plugin/commit/79b5d36d9a9e52a090c99ba93adde09d23444053

  Author: Basil Crow 

  Date:   2022-04-27 (Wed, 27 Apr 2022)



  Changed paths:

M src/test/java/hudson/scm/CompareAgainstBaselineCallableTest.java



  Log Message:

  ---

  Remove usage of deprecated Guava class





  Commit: 3cda03616f543b2cd44aeb8052a57c9f791aed12

  
https://github.com/jenkinsci/subversion-plugin/commit/3cda03616f543b2cd44aeb8052a57c9f791aed12

  Author: Diego Díez Ricondo 

  Date:   2022-05-05 (Thu, 05 May 2022)



  Changed paths:

M .mvn/extensions.xml

M pom.xml

M src/main/java/hudson/scm/SubversionSCM.java

M src/main/java/hudson/scm/SubversionTagAction.java

M src/main/java/hudson/scm/UserProvidedCredential.java

M src/main/java/hudson/scm/browsers/VisualSVN.java

M src/main/java/hudson/scm/subversion/CheckoutUpdater.java

A src/main/resources/index.jelly

M src/test/java/hudson/scm/CompareAgainstBaselineCallableTest.java



  Log Message:

  ---

  Merge pull request #271 from basil/pom



Update plugin parent POM and plugin BOM





Compare: 
https://github.com/jenkinsci/subversion-plugin/compare/bd76d544fe8d...3cda03616f54

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/subversion-plugin/push/refs/heads/master/bd76d5-3cda03%40github.com.

[nexa] e-privacy torna in presenza

[Diego Giorio]

O, meglio, in modalità mista presenza/remoto

Non mi sembra di averlo visto passare in lista, quindi segnalo che torna 
l'ormai storico convegno e-privacy, che festeggia la XXX edizione in 20 anni di 
attività.
Si terrà a giugno, a Firenze, dov'è nato, e sarà dedicato a tematiche molto di 
attualità:

https://e-privacy.winstonsmith.org/
[https://e-privacy.winstonsmith.org/images/editions/EPRIVACY_29_1200x700.png]
e-privacy XXX — Sospendiamo la privacy
e-privacy XXX @ Firenze | Rete Call for Paper. Il Progetto Winston Smith e 
l'Hermes Center for Transparency and Digital Human Rights sono lieti di 
invitarti come relatore all'edizione primaverile alla trentesima edisione di 
e-privacy, che si terrà in modalità mista, presenza + videoconferenza il 16 e 
17 giugno 2022 a Firenze.. Oltre a poterci stringere la mano, avremo 
l'occasione di ...
e-privacy.winstonsmith.org
Saluti a tutti

D.
___
nexa mailing list
nexa@server-nexa.polito.it
https://server-nexa.polito.it/cgi-bin/mailman/listinfo/nexa

Re: [meta-virtualization] [PATCH] docker: Add runtime provide for virtual-docker

[Diego Sueiro]

>-Original Message-
>From: meta-virtualization@lists.yoctoproject.org virtualizat...@lists.yoctoproject.org> On Behalf Of Diego Sueiro via
>lists.yoctoproject.org
>Sent: 04 May 2022 15:31
>To: bruce.ashfi...@gmail.com; Richard Neill 
>Cc: meta-virtualization@lists.yoctoproject.org; nd 
>Subject: Re: [meta-virtualization] [PATCH] docker: Add runtime provide for
>virtual-docker
>
>Hi Bruce,
>
>>-Original Message-
>>From: meta-virtualization@lists.yoctoproject.org >virtualizat...@lists.yoctoproject.org> On Behalf Of Bruce Ashfield via
>>lists.yoctoproject.org
>>Sent: 04 May 2022 15:27
>>To: Richard Neill 
>>Cc: meta-virtualization@lists.yoctoproject.org; nd 
>>Subject: Re: [meta-virtualization] [PATCH] docker: Add runtime provide
>>for virtual-docker
>>
>>On Wed, May 4, 2022 at 10:09 AM Richard Neill 
>>wrote:
>>>
>>> This patch enables successful runtime-dependency on the Docker
>>> preferred provider, as virtual/docker does not resolve. Doing so
>>> aligns with other virtual package providers (e.g. virtual-runc), and
>>> follows the Yocto Project documentation
>>> (https://docs.yoctoproject.org/singleindex.html#virtual-runtime-provides).
>>
>>We don't have a virtual-docker rprovides by design. Since there are
>>differences
>>(historically) between docker-ce and docker-moby.
>>
>>Your package lists and images should be referring to the one they want,
>>not virtual-docker as a rdepends.
>
>In this case having ` PREFERRED_PROVIDER_virtual/docker ?= "docker-ce"` and
>` PROVIDES += "virtual/docker"` is useless?
>

Also, it seems that on the browser github.com/docker/docker.git (from 
docker-ce_git.bb) redirects to github.com/moby/moby.git.
Does it not make sense to retire one of the recipes and just keep one? It will 
reduce maintenance effort and avoid
confusions to which one should be used. 

Diego


>
>>
>>Bruce
>>
>>>
>>> Signed-off-by: Richard Neill 
>>> ---
>>>  recipes-containers/docker/docker.inc | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/recipes-containers/docker/docker.inc
>>> b/recipes-containers/docker/docker.inc
>>> index 40a3642..e196f9b 100644
>>> --- a/recipes-containers/docker/docker.inc
>>> +++ b/recipes-containers/docker/docker.inc
>>> @@ -32,6 +32,7 @@ RDEPENDS:${PN} += "virtual-containerd virtual-runc"
>>>  RRECOMMENDS:${PN} = "kernel-module-dm-thin-pool kernel-module-nf-
>>nat kernel-module-nf-conntrack-netlink kernel-module-xt-addrtype
>>kernel- module-xt-masquerade"
>>>
>>>  PROVIDES += "virtual/docker"
>>> +RPROVIDES:${PN} += "virtual-docker"
>>>
>>>  # we want all the docker variant recpes to be installable via "docker"
>>>  PACKAGE_NAME = "docker"
>>> --
>>> 2.25.1
>>>
>>>
>>>
>>>
>>
>>
>>--
>>- Thou shalt not follow the NULL pointer, for chaos and madness await
>>thee at its end
>>- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7245): 
https://lists.yoctoproject.org/g/meta-virtualization/message/7245
Mute This Topic: https://lists.yoctoproject.org/mt/90888043/21656
Group Owner: meta-virtualization+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [meta-virtualization] [PATCH] docker: Add runtime provide for virtual-docker

[Diego Sueiro]

Hi Bruce,

>-Original Message-
>From: meta-virtualization@lists.yoctoproject.org virtualizat...@lists.yoctoproject.org> On Behalf Of Bruce Ashfield via
>lists.yoctoproject.org
>Sent: 04 May 2022 15:27
>To: Richard Neill 
>Cc: meta-virtualization@lists.yoctoproject.org; nd 
>Subject: Re: [meta-virtualization] [PATCH] docker: Add runtime provide for
>virtual-docker
>
>On Wed, May 4, 2022 at 10:09 AM Richard Neill 
>wrote:
>>
>> This patch enables successful runtime-dependency on the Docker
>> preferred provider, as virtual/docker does not resolve. Doing so
>> aligns with other virtual package providers (e.g. virtual-runc), and
>> follows the Yocto Project documentation
>> (https://docs.yoctoproject.org/singleindex.html#virtual-runtime-provides).
>
>We don't have a virtual-docker rprovides by design. Since there are
>differences
>(historically) between docker-ce and docker-moby.
>
>Your package lists and images should be referring to the one they want, not
>virtual-docker as a rdepends.

In this case having ` PREFERRED_PROVIDER_virtual/docker ?= "docker-ce"` and ` 
PROVIDES += "virtual/docker"` is useless?

--
Diego

>
>Bruce
>
>>
>> Signed-off-by: Richard Neill 
>> ---
>>  recipes-containers/docker/docker.inc | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/recipes-containers/docker/docker.inc
>> b/recipes-containers/docker/docker.inc
>> index 40a3642..e196f9b 100644
>> --- a/recipes-containers/docker/docker.inc
>> +++ b/recipes-containers/docker/docker.inc
>> @@ -32,6 +32,7 @@ RDEPENDS:${PN} += "virtual-containerd virtual-runc"
>>  RRECOMMENDS:${PN} = "kernel-module-dm-thin-pool kernel-module-nf-
>nat kernel-module-nf-conntrack-netlink kernel-module-xt-addrtype kernel-
>module-xt-masquerade"
>>
>>  PROVIDES += "virtual/docker"
>> +RPROVIDES:${PN} += "virtual-docker"
>>
>>  # we want all the docker variant recpes to be installable via "docker"
>>  PACKAGE_NAME = "docker"
>> --
>> 2.25.1
>>
>>
>>
>>
>
>
>--
>- Thou shalt not follow the NULL pointer, for chaos and madness await thee at
>its end
>- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7244): 
https://lists.yoctoproject.org/g/meta-virtualization/message/7244
Mute This Topic: https://lists.yoctoproject.org/mt/90888043/21656
Group Owner: meta-virtualization+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[ovirt-users] Re: Self-hosted engine 4.5.0 deployment fails

[diego . ercolani]

Please follow the instruction here:
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/N6MNSV4ZK26V5NVPBFAMHQPAQAWUR2OE/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VWBTUX6UWQ2R3GJK7CGZMXHXOA26INMI/

[Bug 1971435] [NEW] Modem Manager gui crashed

[Diego A. Elizondo]

Public bug reported:

OS:Ubuntu 22.04 Jammy Jellyfish

Modem manager: Modem Manager >= 0.7.0
Segmentation fault at address: 0x20
Stack trace:
1. /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_bit_lock+0x50) [0x7fe50fcac540]
2. /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_bit_lock+0x50) [0x7fe50fcac540]
3. /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_variant_n_children+0x1d) 
[0x7fe50fd2637d]
4. 
/usr/lib/x86_64-linux-gnu/modem-manager-gui/modules/libmodcm_nm09.so(+0x3bc0) 
[0x7fe50c314bc0]
5. modem-manager-gui(mmguicore_connections_enum+0x6d) [0x5650e5bafd4d]
6. modem-manager-gui(+0x4ac35) [0x5650e5bd0c35]
7. 
/usr/lib/x86_64-linux-gnu/modem-manager-gui/modules/libmodmm_mm07.so(+0x9189) 
[0x7fe5057f0189]
8. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x16f) 
[0x7fe50fc41d2f]
9. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x30b76) [0x7fe50fc5db76]

** Affects: modem-manager-gui (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971435

Title:
  Modem Manager gui crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1971435/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: Un NAS x86 per Debian?

[Diego Zuccato]

Il 03/05/2022 07:06, Paride Desimone ha scritto:

Ho installato una motherboard con un i5 in un case rackable "short", dove ho 
montato 5 hdd da 2TB che avevo in giro (attenzione a *non* usare dischi green!) in RAID 
(con mdadm).
Perché e cosa sarebbero i dischi green?Sono dischi a basso consumo e basse prestazioni per uso desktop (8x5) 

che si deteriorano velocemente se usati 24x7.
Stupidamente, anni fa ho montato 3 WD green in RAID 5: dopo 
"esattamente" 3 anni (e qualche settimana) due sono morti insieme.


Da allora solo dischi adatti per RAID e/o di classe enterprise.

Per es. i WD Red sono pensati proprio per l'uso in RAID e oltre a poter 
lavorare 24x7 hanno (o dicono di avere... :) ) anche una 
compensazione/protezione per le vibrazioni di diversi dischi che 
lavorano vicini. Fatto sta che coi dischi non green i fail che ho visto 
negli ultimi 10 anni si contano sulle dita di una mano, su un parco di 
più di 600 dischi.


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: Un NAS x86 per Debian?

[Diego Zuccato]

Personalmente ho optato per una soluzione più "corposa", ma ho esigenze 
"anomale" :)


Ho installato una motherboard con un i5 in un case rackable "short", 
dove ho montato 5 hdd da 2TB che avevo in giro (attenzione a *non* usare 
dischi green!) in RAID (con mdadm). Proxmox per gestire il ferro, una VM 
per Home Assistant (questo fa inorridire quelli di Indomus, ma per me va 
bene :) ), un'altra per i miei server web (con ISPConfig), un'altra per 
NextCloud (il "NAS"), altre VM piccoline "di servizio".
In più ho collegato un disco esterno al FritzBox da usare come media 
repository DLNA.

L'unico problema è che il consumo è un po' alto (più di 150W continui).

Comunque il "mondo" NAS ha tante sfaccettature diverse per esigenze 
leggermente diverse. C'è chi vuole semplicemente ottenere una certa 
funzionalità e fa tutto con un QNAP, chi è quasi più interessato al 
processo che al risultato e smanetta (come me), chi vuole solo un media 
server per i televisori di casa (tanto vale usare la porta USB del 
modem!), ecc. Alla fine sono tutte soluzioni valide, ma nessuna è adatta 
per tutti.


Il 02/05/2022 14:31, gerlos ha scritto:

Il 02/05/22 11:55, Leandro Noferini ha scritto:


Ciao a tutti,

HP proliant microserver con un AMD turion con 4 gb di ram che funziona 
perfettamente da circa sei anni con cinque dischi (questi cambiati via 
via tutti) con openmediavault come sistema operativo.




+1 per OpenMediaVault (che è comunque basato su Debian).

Per quanto si possano ottenere le stesse cose partendo da un sistema 
Debian "generico", è infinitamente più comodo e veloce partire da un 
qualcosa più "specifico". L'interfaccia web è comodissima e, 
soprattutto, ci si evitano errori grossolani se non si vuole/può leggere 
tutta la documentazione necessaria a fare le cose in sicurezza e 
compatibilità.


saluti,

gerlos




--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

[Kernel-packages] [Bug 1969853] Re: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

[Diego Aparecido de Souza Pereira]

Bluetooth working well with `linux-firmware/jammy-proposed,now
20220329.git681281e4-0ubuntu3 all  [installed]`. Thank you so much!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  No bluetooth found on QCA9565.

  [Test Case]

  See below.

  [Fix]

  Provide ar3k/* firmware blobs.

  [Where Problems Could Occur]

  None expected, this is a regression from Impish.

  [Original Description]

  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
     Docs: man:bluetoothd(8)
     Main PID: 1100 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1969853] Re: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

[Diego Aparecido de Souza Pereira]

Bluetooth working well with `linux-firmware/jammy-proposed,now
20220329.git681281e4-0ubuntu3 all  [installed]`. Thank you so much!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

(PN) Student Forum CFP at EDCC 2022 - The 18th European Dependable Computing Conference

[Diego Perez]

-
The 18th European Dependable Computing Conference (EDCC 2022)
  12 September - 15 September 2022
  Zaragoza, Spain
  https://webdiis.unizar.es/EDCC22/index.html
-

Call for Papers | Student Forum | EDCC 2022

-

The EDCC 2022 Student Forum is a vibrant and friendly environment where 
students can present and discuss their work, and exchange ideas and 
experiences with other students, researchers and industry.
Students are invited to submit papers describing their potential and 
ongoing research at any stage, from ideas to results.
We seek papers presenting early technical work, in-progress research and 
introduction of novel ideas to the community.
One of the key goals of the Forum is to provide students with feedback 
on their preliminary results that might help with their future research 
directions.


Topics of interest include, but are not limited to:

- Hardware and software architectures of dependable systems
- Model-driven engineering approaches
- Fault-tolerant networks & ultra-reliable low-latency communication
- Dependability modelling and tools
- Testing and validation methods
- Development of safety and security-critical systems
- Data protection and data privacy
- Dependability and security of:
* Critical infrastructures, e.g. smart energy grids, intelligent 
transportation systems, smart cities

* Cyber-physical systems
* (Industrial) Internet of Things
* Cloud, fog, and edge computing systems
* Data analytics applications & systems based on machine learning 
and artificial intelligence

* Databases and distributed ledgers (incl. Blockchains)
* Artificial intelligence approaches


*Submission*

The first author of the paper must be a student.

Submitted papers should conform to the IEEE format 
(https://www.ieee.org/conferences/publishing/templates.html) with a 
maximum of 4 pages (references included).


Student Forum papers will be reviewed by the members of the Student 
Forum Program Committee. The selection will be based on the following 
criteria:

- Relevance to the technical content of EDCC 2022
- Originality
- Technical soundness
- Quality and clarity of the written presentation

Students with accepted papers are expected to attend the conference and 
present the paper. A presentation slot will be reserved for students in 
the main EDCC conference program.


For accepted papers, students can choose to have it published on 
arxiv.org, a free open-access publication service. The student must 
communicate to the Student Forum Chair whether he/she would the paper to 
be published (or not) on arxiv.org after notification.


The Organizing Committee will provide certificates of attendance for 
students upon request.


Submit your student paper by email and in PDF format to:
Ibéria Medeiros (Student Forum Chair)
email address: ivmedei...@fc.ul.pt
Subject: "EDCC 2022 Student Forum Submission"


*Important Dates*

June 30, 2022 Paper submission deadline
July 21, 2022 Notification to authors
July 31, 2021 Camera-ready submission deadline

More information at https://webdiis.unizar.es/EDCC22/studentforum.html

If you have any questions, please contact the Student Forum Chair at 
ivmedei...@fc.ul.pt


[[ Petri Nets World:]]
[[  http://www.informatik.uni-hamburg.de/TGI/PetriNets/ ]]
[[ Mailing list FAQ:]]
[[ http://www.informatik.uni-hamburg.de/TGI/PetriNets/pnml/faq.html ]]
[[ Post messages/summary of replies:]]
[[   petrinet@informatik.uni-hamburg.de ]]

[ovirt-users] Re: hosted engine ovirt-engine-appliance-4.5-20220419162115.1.el8.x86_64 doesn't deploy

[diego . ercolani]

Yes. The problem is that 
hosted-engine --deploy --4 --ansible-extra-vars=he_pause_host=true

pause the deploy far after the problem so you have to intercept the engine 
start then, as I have an installation behind proxy:

echo "proxy=http://192.168.9.149:3128; >> /etc/yum.conf

then waiting the upgrade process and during the upgrade:
while :; do dnf -y downgrade postgresql-jdbc; sleep 5; done

and then wait


how it's possible to use answer file in the node and in the engine only not to 
have to reissue all the parameter?

Thank you
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/K7TQBJNKJBJJ5O6EC2ZTWCOA5GNMC3LK/

[ovirt-users] hosted engine ovirt-engine-appliance-4.5-20220419162115.1.el8.x86_64 doesn't deploy

[diego . ercolani]

I have a full installation of ovirt hosted-engine but it always stop telling:
[ ERROR ] fatal: [localhost -> 192.168.222.15]: FAILED! => {"attempts": 30, 
"changed": false, "connection": "close", "content_encoding": "identity", 
"content_length": "86", "content_type": "text/html; charset=UTF-8", "date": 
"Sat, 30 Apr 2022 06:56:58 GMT", "elapsed": 0, "msg": "Status code was 500 and 
not [200]: HTTP Error 500: Internal Server Error", "redirected": false, 
"server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1", 
"status": 500, "url": "http://localhost/ovirt-engine/services/health"}

and it's true, I can access the engine via the temporary address (192.168.1.69 
or 192.168.222.69) and issuing a curl:
[root@ovirt-engine ~]# curl http://localhost/ovirt-engine/services/health
Error500 - Internal Server 
Error[root@ovirt-engine ~]# 

it give back an Internal server error.

I can not deploy how it's possible to fix?

currently the engine is running.. should I try something from inside the engine?
Thank you
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7OVXEYY33B7RTDMMOJHDJR4RI44AN7F3/

[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

[Diego Lineros]

*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243

Interestingly, the gear appears only after hibernation. I can choose
Wayland, but, once I log out everything is gone and I'm back to X11

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1969254

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After some recent update to Ubuntu 22.04 dev, X11 is selected by
  default and there is no longer the option to select the display
  protocol at login.

  It seems I am not the only affected:
  https://askubuntu.com/questions/1402671/ubuntu-no-gear-for-
  waylaland-x11

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-session 42.0-1ubuntu2
  Uname: Linux 5.17.3-051703-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 22:20:35 2022
  InstallationDate: Installed on 2022-02-02 (72 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

[Diego Lineros]

*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243

Interestingly, the gear appears only after hibernation. I can choose
Wayland, but, once I log out everything is gone and I'm back to X11

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969254

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

[Diego Lineros]

*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243

Interestingly, the gear appears only after hibernation. I can choose
Wayland, but, once I log out everything is gone and I'm back to X11

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1969254

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[slurm-users] MPICH

[Diego Zuccato]

Hello all.

Does someone know which flags to use to compile MPICH to be 
Slurm-compatible?


One of our users is trying to do that, but:
./configure --with-slurm-include=/usr/include/slurm/ 
--with-slurm-lib=/usr/lib/x86_64-linux-gnu/slurm-wlm/ --with-pm=none 
--with-pmi=slurm --prefix=${HOME}/usr/mpich-4.0.2

gives an executable that only uses 1 CPU even if sbatch requested 52. :(

Any hint appreciated.

Tks.

--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786

Re: [Gluster-users] Usage not updating in quotas

[Diego Zuccato]

Hello Amar.

Maybe I missed something, but does that mean that if I upgrade from 9.5 
to 10 I lose the quota? Seems too strange to be true...


Tks,
 Diego

Il 28/04/2022 07:12, Amar Tumballi ha scritto:

Hi Alan, Strahil,

On Thu, Apr 28, 2022 at 3:50 AM Strahil Nikolov <mailto:hunter86...@yahoo.com>> wrote:


@Amar,

did the quota feature reach Gluster v10 ?


It got merged in the development branch (ie, confirmed on v11). As per 
our release policy, it wouldn't make it to v10 as its a feature. Anyone 
wanting to test it, experiment with it should build from nightly or 
development branch for now.


Regards,
Amar

On Tue, Apr 26, 2022 at 12:09, Alan Orth
mailto:alan.o...@gmail.com>> wrote:






Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users


--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: Energy cost time-varying in MOST

[Diego Feroldi]

Thank you very much Ray! Now it works correctly. Your guide has been very
helpful to me.
Best regards,

El mar, 26 abr 2022 a las 22:11, Ray Daniel Zimmerman ()
escribió:

> The 'chgtype' field cannot be CT_REP (1, for replacement). It needs to be
> either CT_REL (2, for scaling) or CT_ADD (3, for shifting).
>
>Ray
>
> On Apr 25, 2022, at 1:12 PM, Diego Feroldi  wrote:
>
> Dear Ray,
>
> Thank you very much for the quick answer! Unfortunately, I tried what
> you suggested but I get the following error message:
>
> Error using apply_changes (line 190)
> apply_changes: unsupported modification type 1 for gencost table
> CT_MODCOST_F/X
> modification
>
> It may be that some other field needs to be set in addition to 'table'
> and 'col'?
>
> Diego
>
> El lun, 25 abr 2022 a las 14:02, Ray Daniel Zimmerman ()
> escribió:
>
>> Hi Diego,
>>
>> You should be able to do it just like any other profile (e.g. see
>> ex_wind_profile.m and ex_load_profile.m), except you would set the
>> 'table' field to CT_TGENCOST and the 'col' field to either CT_MODCOST_F
>> or CT_MODCOST_X. See Section 9.3.5 in the MATPOWER User’s Manual
>> <https://matpower.org/docs/MATPOWER-manual-7.1.pdf> for more details
>> about the types of modifications that can be made by apply_changes() and
>> therefore by a MOST profile.
>>
>> Hope this helps,
>>
>>Ray
>>
>>
>> On Apr 25, 2022, at 9:09 AM, Diego Feroldi  wrote:
>>
>> Hi everyone,
>>
>> I am trying to incorporate a time-varying energy cost profile (gencost) into 
>> an economic dispatch problem. I can't find the way to enter the profile into 
>> the MOST problem. Could someone give me some idea or let me know if it is 
>> not possible? Thanks in advance for any feedback,
>>
>>
>> Best regards,
>>
>>
>> Diego
>>
>> --
>> Diego Feroldi
>>
>>
>>
>
> --
> Diego Feroldi
>
>
>

-- 
Diego Feroldi

Re: [google-appengine] Re: Hidden usage of frontend instance hours

[Diego Crapper]

Hello, Ernesto.

Thank you for your reply.

If I remember correctly, setting min_instances = 1 and max_instances = 1
created problems when I tried it. I assume it's a problem when Google needs
to move the app to a different server, update the underlying software and
such.

Regardless, I haven't made any changes since November 3, 2021, and the
billing issues only began last month. There hasn't been any noticeable
increase in traffic, so what changed?

This is my billing report chart:
[image: screenshot.1.png]

Thanks again.



On Tue, Apr 26, 2022 at 7:27 PM 'Ernesto Contreras Pinon' via Google App
Engine  wrote:

> The documentation 
> shows that when instances are increased, instance time is accrued for 15
> minutes after the last request to the instance. This could explain a
> possible accruing of cost that adds up per month. You could try setting an 
> upper
> limit
> of
> 1 instance, so that if an additional instance is created automatically by
> App Engine, it does not use up instance time
> . Do you see other
> costs that might be also adding up from related services? You can filter
> the billing report table
> 
> for your project to see detailed costs of your usage for App Engine.
>
> On Tuesday, April 26, 2022 at 6:55:28 AM UTC-5 di...@sinopsis.com wrote:
>
>> Hello.
>>
>> I have a single service running on App Engine. It's a very-low-traffic
>> website, so I've set it to always have 1 instance running, to avoid lengthy
>> cold starts when someone does visit. It's been running with no problems for
>> a couple of years or so. It always stayed within the free tier. I haven't
>> made changes to it in at least several months.
>>
>> However, since around mid-March, I've been getting charged for extra
>> instance hours. I've checked the console and everything seems normal. The
>> instances chart shows a straight line on 1, with occasional spikes to 2
>> which last for maybe five minutes every couple of hours or so, which is
>> normal due to restarts and such, and certainly doesn't seem enough to go
>> over the 28 free hours per day. Right now, for example, it says that I've
>> used 19 hours today, and that the quota will reset in 5 hours, so 24 hours
>> total.
>>
>> And yet, I keep getting charged. Not a lot, it adds up to maybe 3 or 4
>> dollars a month, but still, I don't know where it's coming from.
>>
>> Did App Engine change something about how hours are billed around
>> mid-March? Any ideas on how to check what's going on?
>>
>> Thanks!
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/VGJlSAlqbjk/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/df1d17f0-211f-443b-a803-cf8a53d78289n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAOVkKbgai8fUP2_V7KDz3Wq_1neP8OQObO3mNc3gNe5v0zXc1Q%40mail.gmail.com.

[Kernel-packages] [Bug 1969853] PulseList.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584030/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] Re: No Bluetooth Found

[Diego Aparecido de Souza Pereira]

Hi! I'll add some information that might help. As using bluetooth was
very important to me (and I had this same problem on 3 different
installs of that Ubuntu version), I searched forums and found a
solution. Basically I manually downloaded the linux firmware and copied
the ar3k folder to /lib/firmware. I followed the following steps from
the forum below.

- Download linux-firmware_1.201.tar.xz at 
[http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.201.tar.xz](http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.201.tar.xz)
 (you can visit 
[https://packages.ubuntu.com/impish/linux-firmware](https://packages.ubuntu.com/impish/linux-firmware)
 for more details)
- Extract linux-firmware_1.201.tar.xz, copy folder ar3k into /lib/firmware
- Restart your computer

https://askubuntu.com/questions/1403934/patch-file-not-found-
ar3k-athrbt-0x3101-dfu

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] ProcInterrupts.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584028/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] ProcCpuinfoMinimal.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584026/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] ProcEnviron.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584027/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] ProcModules.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584029/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] RfKill.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584031/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] UdevDb.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584032/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] acpidump.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584034/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] WifiSyslog.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584033/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1969853] Re: No Bluetooth Found

[Diego Aparecido de Souza Pereira]

Hi! I'll add some information that might help. As using bluetooth was
very important to me (and I had this same problem on 3 different
installs of that Ubuntu version), I searched forums and found a
solution. Basically I manually downloaded the linux firmware and copied
the ar3k folder to /lib/firmware. I followed the following steps from
the forum below.

- Download linux-firmware_1.201.tar.xz at 
[http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.201.tar.xz](http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.201.tar.xz)
 (you can visit 
[https://packages.ubuntu.com/impish/linux-firmware](https://packages.ubuntu.com/impish/linux-firmware)
 for more details)
- Extract linux-firmware_1.201.tar.xz, copy folder ar3k into /lib/firmware
- Restart your computer

https://askubuntu.com/questions/1403934/patch-file-not-found-
ar3k-athrbt-0x3101-dfu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] acpidump.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584034/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] WifiSyslog.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584033/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] UdevDb.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584032/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] RfKill.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584031/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] ProcModules.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584029/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] PulseList.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584030/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] ProcCpuinfoMinimal.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584026/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] ProcInterrupts.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584028/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] ProcEnviron.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584027/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] ProcCpuinfo.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584025/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1969853] Lspci.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584019/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] ProcCpuinfo.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584025/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] IwConfig.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584018/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] Lspci-vt.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584020/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] Lsusb-v.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584023/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] PaInfo.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584024/+files/PaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] Lsusb-t.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584022/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969853] Lsusb.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584021/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1969853] PaInfo.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584024/+files/PaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] Lsusb-v.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584023/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] Lsusb-t.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584022/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] Lspci-vt.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584020/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] Lsusb.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584021/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] Lspci.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1969853/+attachment/5584019/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] IwConfig.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584018/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969853] CurrentDmesg.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584017/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1969853] Re: No Bluetooth Found

[Diego Aparecido de Souza Pereira]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:
  
  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd
  
  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  diego  2220 F pulseaudio
+  /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-04-23 (2 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ MachineType: Dell Inc. Inspiron 15-3567
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-27-generic N/A
+  linux-backports-modules-5.15.0-27-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu1
+ Tags:  wayland-session jammy
+ Uname: Linux 5.15.0-27-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/15/2021
+ dmi.bios.release: 2.18
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 2.18.0
+ dmi.board.name: 0MM5K1
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 15-3567
+ dmi.product.sku: 078B
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584016/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationD

[Kernel-packages] [Bug 1969853] CurrentDmesg.txt

[Diego Aparecido de Souza Pereira]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584017/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1969853] Re: No Bluetooth Found

[Diego Aparecido de Souza Pereira]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:
  
  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd
  
  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  diego  2220 F pulseaudio
+  /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-04-23 (2 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ MachineType: Dell Inc. Inspiron 15-3567
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-27-generic N/A
+  linux-backports-modules-5.15.0-27-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu1
+ Tags:  wayland-session jammy
+ Uname: Linux 5.15.0-27-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/15/2021
+ dmi.bios.release: 2.18
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 2.18.0
+ dmi.board.name: 0MM5K1
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 15-3567
+ dmi.product.sku: 078B
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1969853/+attachment/5584016/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969853

Title:
  No Bluetooth Found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[google-appengine] Hidden usage of frontend instance hours

[Diego C.]

Hello.

I have a single service running on App Engine. It's a very-low-traffic 
website, so I've set it to always have 1 instance running, to avoid lengthy 
cold starts when someone does visit. It's been running with no problems for 
a couple of years or so. It always stayed within the free tier. I haven't 
made changes to it in at least several months.

However, since around mid-March, I've been getting charged for extra 
instance hours. I've checked the console and everything seems normal. The 
instances chart shows a straight line on 1, with occasional spikes to 2 
which last for maybe five minutes every couple of hours or so, which is 
normal due to restarts and such, and certainly doesn't seem enough to go 
over the 28 free hours per day. Right now, for example, it says that I've 
used 19 hours today, and that the quota will reset in 5 hours, so 24 hours 
total.

And yet, I keep getting charged. Not a lot, it adds up to maybe 3 or 4 
dollars a month, but still, I don't know where it's coming from.

Did App Engine change something about how hours are billed around 
mid-March? Any ideas on how to check what's going on?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4e51c3af-1d88-4cc5-ba8e-a0267a5b6da0n%40googlegroups.com.

Re: Energy cost time-varying in MOST

[Diego Feroldi]

Dear Ray,

Thank you very much for the quick answer! Unfortunately, I tried what
you suggested but I get the following error message:

Error using apply_changes (line 190)
apply_changes: unsupported modification type 1 for gencost table
CT_MODCOST_F/X
modification

It may be that some other field needs to be set in addition to 'table'
and 'col'?

Diego

El lun, 25 abr 2022 a las 14:02, Ray Daniel Zimmerman ()
escribió:

> Hi Diego,
>
> You should be able to do it just like any other profile (e.g. see
> ex_wind_profile.m and ex_load_profile.m), except you would set the 'table'
> field to CT_TGENCOST and the 'col' field to either CT_MODCOST_F or
> CT_MODCOST_X. See Section 9.3.5 in the MATPOWER User’s Manual
> <https://matpower.org/docs/MATPOWER-manual-7.1.pdf> for more details
> about the types of modifications that can be made by apply_changes() and
> therefore by a MOST profile.
>
> Hope this helps,
>
>    Ray
>
>
> On Apr 25, 2022, at 9:09 AM, Diego Feroldi  wrote:
>
> Hi everyone,
>
> I am trying to incorporate a time-varying energy cost profile (gencost) into 
> an economic dispatch problem. I can't find the way to enter the profile into 
> the MOST problem. Could someone give me some idea or let me know if it is not 
> possible? Thanks in advance for any feedback,
>
>
> Best regards,
>
>
> Diego
>
> --
> Diego Feroldi
>
>
>

-- 
Diego Feroldi