[Kernel-packages] [Bug 2053040] Re: GPU Crash When Waking from Suspend

[Mario Limonciello]

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

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

-- 
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/2053040

Title:
  GPU Crash When Waking from Suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Screen goes completely white, have to reboot the system to recover.
  I've manually attached the kernel log from the previous boot which
  contains the relevant errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 10:19:39 2024
  InstallationDate: Installed on 2024-02-02 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.6.0-14-generic N/A
   linux-backports-modules-6.6.0-14-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053040/+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 2052467] Re: Unplugging External Monitor Causes GPU Crash

[Mario Limonciello]

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

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

-- 
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/2052467

Title:
  Unplugging External Monitor Causes GPU Crash

Status in linux package in Ubuntu:
  New

Bug description:
  Unplugging an exteranal usb-c monitor caused the GPU to crash - the
  screen went white and unresponsive, reboot was required for the
  machine to become usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:holmanb1976 F pipewire
   /dev/snd/controlC0:  holmanb1989 F wireplumber
   /dev/snd/controlC1:  holmanb1989 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb  5 16:20:03 2024
  InstallationDate: Installed on 2024-02-02 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.6.0-14-generic N/A
   linux-backports-modules-6.6.0-14-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052467/+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 2053040] Re: GPU Crash When Waking from Suspend

[Mario Limonciello]

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

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

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

Title:
  GPU Crash When Waking from Suspend

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


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

[Bug 2052467] Re: Unplugging External Monitor Causes GPU Crash

[Mario Limonciello]

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

** This bug has been marked a duplicate of bug 2056445
   external monitors flash white with every interrupt

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

Title:
  Unplugging External Monitor Causes GPU Crash

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


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

Re: [regext] EPP evolution and the REGEXT charter

[Mario Loffredo]

Il 22/03/2024 13:01, Gould, James ha scritto:

Andy,

It's not a question of fairness, but a question of what is defined in EPP RFC 
5730 as it comes to extensibility of EPP.  EPP RFC 5730 includes extensibility 
of transport, as reflected in Section 2.1.


This is what I meant to say with my previous post.

Mapping EPP over a new transport is compliant with RFC5730 because it's 
a kind of extension defined and allowed by that document itself. 
Otherwise I do wonder what would be the purpose of Section 2.1.


On the contrary, as expressed by many of us including me, REPP would be 
something different from EPP , hence it would require to recharter 
RegExt. Otherwise I wouldn't catch the purpose of the feedback provided 
by this WG about first EoH version


to require it to be fully compliant with RFC5730. And that version was 
really almost compliant with RFC5730.


Finally, I'd allso like to outline that some time ago I provided Maarten 
with a more comprehensive feedback about REPP on CENTR R list. It 
included the objections I have just raised here.


Am sure that I've always been fair.


Best,

Mario




--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Re: [regext] EPP evolution and the REGEXT charter

[Mario Loffredo]

Hi Jasdip,


IMO, REPP is not an "EPP extension" as defined by RFC5730. It provides 
neither just a switch of transport (like EoH and EoQ) nor an extension 
to EPP comands and responses.


Instead, it presents a full revision of EPP that maps some EPP features 
onto HTTP features.


Moreover, the current proposal is incompatible with some existing or 
future documents including extensions to EPP query commands (see Jody's 
question at last meeting about REPP compatibility with the Fee Extension).


On the contrary, in the spirit of achieving a full compliance with 
RFC5730, .it is going to update its EPP implementation that has been 
working since 2009.



With regard to a possible RegExt rechartering, I also don't think we 
need it.


RFC5730 already allows for implementing EPP over multiple transports. 
But it does even more, it makes some examples of possible alternatives 
to TCP.


Therefore, leaving aside for the moment the debate about considering a 
new transport as an extension or not, it would be paradoxical if the 
protocol itself admitted other transports than TCP but it wouldn't be 
allowed to standardize them just like it has been done for TCP :-(



Best,

Mario


Il 22/03/2024 01:12, Jasdip Singh ha scritto:


Hi.

Curious if the newly proposed “RESTful EPP” is considered a new 
protocol that is different from EPP, or is it an “extension” of EPP? 
(AFAICT, the former seems outside the current regext charter.)


Thanks,

Jasdip

*From: *regext  on behalf of Hollenbeck, 
Scott 

*Date: *Friday, March 22, 2024 at 9:56 AM
*To: *jgould=40verisign@dmarc.ietf.org 
, 
maarten.wullink=40sidn...@dmarc.ietf.org 
, regext@ietf.org 


*Subject: *Re: [regext] EPP evolution and the REGEXT charter

*From:*regext  *On Behalf Of *Gould, James
*Sent:* Thursday, March 21, 2024 7:49 PM
*To:* maarten.wullink=40sidn...@dmarc.ietf.org; regext@ietf.org
*Subject:* [EXTERNAL] Re: [regext] EPP evolution and the REGEXT charter

*Caution:*This email originated from outside the organization. Do not 
click links or open attachments unless you recognize the sender and 
know the content is safe.


Maarten,

The charter refers to EPP extensions, which transports is a form of an 
EPP extension.  RFC 5730 defines the extension points for EPP and 
includes support for extending the transports based on Section 2.1 
“Transport Mapping Considerations”.  I don’t believe that there is a 
need to revise the REGEXT charter to support the additional of new EPP 
transports.


*/[SAH] Agreed. New transport mappings are just another type of 
extension as long as they preserve the data model described in RFC 5730./*


*//*

*/Scott/*


___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

[Kernel-packages] [Bug 2056445] Re: external monitors flash white with every interrupt

[Mario Limonciello]

I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.

-- 
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/2056445

Title:
  external monitors flash white with every interrupt

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  an interesting amdgpu issue:

  I currently have two external monitors, and only one will display the
  desktop at a time - the other is completely white. The interesting
  thing is that with each interrupt that the kernel receives from
  keyboard / mouse, the screens will flip which one is visible. With my
  monitors positioned above and to the left of the laptop's built-in
  display, the flashing monitors feel akin to attending an electronic
  light show, or perhaps a display of fireworks - the monitors flip
  visibility with each keypress.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-11-generic 6.8.0-11.11
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 05:23:23 2024
  InstallationDate: Installed on 2024-02-02 (34 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+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 2056445] Re: external monitors flash white with every interrupt

[Mario Limonciello]

For some unknown reason this only seems to be reported on some people's
Framework 13 AMD laptops.

FYI - there are two workarounds for those currently encountering this
issue.

* On the kernel command line: amdgpu.sg_display=0
* Change the BIOS settings from Auto to UMA_Game_Optimized.


** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3187
   https://gitlab.freedesktop.org/drm/amd/-/issues/3187

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/3187
   Importance: Unknown
   Status: Unknown

** Changed in: linux (Ubuntu)
   Status: New => Triaged

-- 
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/2056445

Title:
  external monitors flash white with every interrupt

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  an interesting amdgpu issue:

  I currently have two external monitors, and only one will display the
  desktop at a time - the other is completely white. The interesting
  thing is that with each interrupt that the kernel receives from
  keyboard / mouse, the screens will flip which one is visible. With my
  monitors positioned above and to the left of the laptop's built-in
  display, the flashing monitors feel akin to attending an electronic
  light show, or perhaps a display of fireworks - the monitors flip
  visibility with each keypress.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-11-generic 6.8.0-11.11
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 05:23:23 2024
  InstallationDate: Installed on 2024-02-02 (34 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+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 2056445] Re: external monitors flash white with every interrupt

[Mario Limonciello]

I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.

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

Title:
  external monitors flash white with every interrupt

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


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

[Bug 2056445] Re: external monitors flash white with every interrupt

[Mario Limonciello]

For some unknown reason this only seems to be reported on some people's
Framework 13 AMD laptops.

FYI - there are two workarounds for those currently encountering this
issue.

* On the kernel command line: amdgpu.sg_display=0
* Change the BIOS settings from Auto to UMA_Game_Optimized.


** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3187
   https://gitlab.freedesktop.org/drm/amd/-/issues/3187

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/3187
   Importance: Unknown
   Status: Unknown

** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

Title:
  external monitors flash white with every interrupt

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


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

[bareos-users] bareos-sd error - broken drive?

[Mario Kneidinger]

I get a bareos error on the backup jobs and wonder, if the drive is broken. 
Has anyone an idea, what I could try?

I get this error in Bareos:

```
bareos-sd JobId 30873: Error: stored/block.cc:1057 Read error on fd=6 at 
file:blk 0:0 on device "tapedrive-0" 
(/dev/tape/by-id/scsi-35000e11162fc2001-nst). ERR=Input/output error.
```

I tried using other tapes, but that does not work either. I tried 
relabeling the tapes but this does not work either and I get an error. Not 
even manually writing to the tapes with 'mt' works and I get the error 

```
/dev/nst0: Input/output error
mt: The tape is write-protected.
```

Drive status on the tape roboter says: Drive Error Code 3
When I start diagnostics on the tape roboter it says on all tests passed 
and after cleaning the drive it shows no error code, until I try labeling 
the tapes.

When asking the status with 'mtx' I get "/dev/sch0 is not an sg device, or 
old sg driver".

So is there anything left that I could try?

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/374dcbd6-a39f-43fc-b8a8-368968fdef14n%40googlegroups.com.

Re: [apache/incubator-teaclave] Is DCAP actually supported? (Issue #726)

[Mario López]

Closed #726 as completed.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/726#event-12198299145
You are receiving this because you are subscribed to this thread.

Message ID: 

Re: [apache/incubator-teaclave] Certificate Errors on deployment (Issue #725)

[Mario López]

Closed #725 as completed.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/725#event-12198303313
You are receiving this because you are subscribed to this thread.

Message ID: 

[PATCH] drm/amd: Flush GFXOFF requests in prepare stage

[Mario Limonciello]

From: Mario Limonciello 

If the system hasn't entered GFXOFF when suspend starts it can cause
hangs accessing GC and RLC during the suspend stage.

Cc:  # 6.1.y: 5095d5418193 ("drm/amd: Evict resources 
during PM ops prepare() callback")
Cc:  # 6.1.y: cb11ca3233aa ("drm/amd: Add concept of 
running prepare_suspend() sequence for IP blocks")
Cc:  # 6.1.y: 2ceec37b0e3d ("drm/amd: Add missing 
kernel doc for prepare_suspend()")
Cc:  # 6.1.y: 3a9626c816db ("drm/amd: Stop evicting 
resources on APUs in suspend")
Cc:  # 6.6.y: 5095d5418193 ("drm/amd: Evict resources 
during PM ops prepare() callback")
Cc:  # 6.6.y: cb11ca3233aa ("drm/amd: Add concept of 
running prepare_suspend() sequence for IP blocks")
Cc:  # 6.6.y: 2ceec37b0e3d ("drm/amd: Add missing 
kernel doc for prepare_suspend()")
Cc:  # 6.6.y: 3a9626c816db ("drm/amd: Stop evicting 
resources on APUs in suspend")
Cc:  # 6.1+
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3132
Fixes: ab4750332dbe ("drm/amdgpu/sdma5.2: add begin/end_use ring callbacks")
Signed-off-by: Mario Limonciello 
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c 
b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index 94bdb5fa6ebc..1fbaf7b81d69 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@ -4524,6 +4524,8 @@ int amdgpu_device_prepare(struct drm_device *dev)
if (r)
goto unprepare;
 
+   flush_delayed_work(>gfx.gfx_off_delay_work);
+
for (i = 0; i < adev->num_ip_blocks; i++) {
if (!adev->ip_blocks[i].status.valid)
continue;
-- 
2.34.1

[Ubuntu-x-swat] [Bug 2058604] [NEW] Framework 16 disable touchpad when typing doesn't work

[Mario Limonciello]

Public bug reported:

Due to the "input deck" the Framework 16 has a "USB" internal keyboard.
This throws off heuristics for detection of keyboards to turn off when
you select disable touchpad when typing.

This is fixed in upstream libinput with the following change:
https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0

As that's not yet part of a release yet and it's a trivial change, could
it be cherry picked for Ubuntu to give a better experience to Framework
16 users?

** Affects: libinput (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Framework 16 disable touchpad when typing doesn't work

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


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Bug 2058604] [NEW] Framework 16 disable touchpad when typing doesn't work

[Mario Limonciello]

Public bug reported:

Due to the "input deck" the Framework 16 has a "USB" internal keyboard.
This throws off heuristics for detection of keyboards to turn off when
you select disable touchpad when typing.

This is fixed in upstream libinput with the following change:
https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0

As that's not yet part of a release yet and it's a trivial change, could
it be cherry picked for Ubuntu to give a better experience to Framework
16 users?

** Affects: libinput (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/2058604

Title:
  Framework 16 disable touchpad when typing doesn't work

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


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

[Desktop-packages] [Bug 2058604] [NEW] Framework 16 disable touchpad when typing doesn't work

[Mario Limonciello]

Public bug reported:

Due to the "input deck" the Framework 16 has a "USB" internal keyboard.
This throws off heuristics for detection of keyboards to turn off when
you select disable touchpad when typing.

This is fixed in upstream libinput with the following change:
https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0

As that's not yet part of a release yet and it's a trivial change, could
it be cherry picked for Ubuntu to give a better experience to Framework
16 users?

** Affects: libinput (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Framework 16 disable touchpad when typing doesn't work

Status in libinput package in Ubuntu:
  New

Bug description:
  Due to the "input deck" the Framework 16 has a "USB" internal
  keyboard.  This throws off heuristics for detection of keyboards to
  turn off when you select disable touchpad when typing.

  This is fixed in upstream libinput with the following change:
  
https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0

  As that's not yet part of a release yet and it's a trivial change,
  could it be cherry picked for Ubuntu to give a better experience to
  Framework 16 users?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2058604/+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

[regext] Shepherd's wirteup about rir-search completed

[Mario Loffredo]

Hi Chairs,

this is to inform you that I just completed the shepherd's writeup of 
rir-search.



Best,

Mario

--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Re: [VOTE] Accept Amended Proposal to unblock Apache KIE 10.0.0 Release

[Mario Fusco]

+1

Mario

On 2024/03/19 14:11:30 Alex Porcelli wrote:
> With all the feedback from the proposal discussion [1], I am starting
> this official vote to accept the amended proposal to unblock Apache
> KIE 10.0.0 Release.
> 
> Here [2] is the link for the final amended proposal.
> 
> Please cast your vote:
> [ ] +1, accept the proposal
> [ ] +0, I don't care
> [ ] -1, do not accept the amended proposal, with the following
> alternative proposal...
> 
> The vote will be open for 72 hours from today, 19 March, 2024. Thanks.
> 
> --
> Alex
> 
> [1] https://lists.apache.org/thread/58xm7pqdyztf7qztmhvntf8wdmvfx7jx
> [2] https://lists.apache.org/thread/pw327lkpmy9gxklq4t5zbwzxjo2y3c0w
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> For additional commands, e-mail: dev-h...@kie.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
For additional commands, e-mail: dev-h...@kie.apache.org

Re: [BRLTTY] Affordable refreshable braille display project

[Mario Lang]

"Jason J.G. White"  writes:

> On 18/3/24 14:49, Sébastien Hinderer wrote:
>
>  I confess that the document felt too long for me to try to study it so I
> am just passing the link,, with the hope that it wiill be of interest to
> somebody on the list.
>
> This appeared in social media recently as well. Without commenting on that
> particular proposal (or set of proposals), I can say the following.
>
> There have been many braille display cell technology proposals over the last
> several decades, few of which have ever been developed into products, and
> details of which can be found by searching a patent database. I've learned
> to treat new such proposals with scepticism, at least until there's a
> working prototype demonstrated publicly and a plausible plan to manufacture
> a device.

And rightly so.  The graveyard of failed projects is huge.
And a few years ago, I think I even happened to cross paths with an
outright scam.  Besides marketing and a "demo" unit made of wood which
only demonstrated the size of the planned device, there was never
anything substantial.  After some funding was acquired, the team
suddenly vanished with no trace.  I am deliberately not naming names,
but you know who you are if you read this.

It has become hard to decide if a "this should be cheaper and simpler"
EE-project is worthy of support.

-- 
CYa,
  ⡍⠁⠗⠊⠕
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty

Re: [Metamath] Help building hmm (Haskell Metamath verifier)

[Mario Carneiro]

Regarding the Haskell errors, do you have warnings-as-errors on? It seems
like all of the errors are actually just promoted warnings, so possibly you
can just disable those warnings.

On Mon, Mar 18, 2024 at 4:59 PM Antony Bartlett  wrote:

> I've been trying to add hmm to metamath-docker, because it's one of the
> verifiers that metamath-test is set up to run against.
>
> The more I think about it, the more any attempt to maintain metamath-test
> without containerization seems insane.  You need to have C, C++, Rust,
> Java, Python, and Haskell installed, then use them to build metamath.exe,
> checkmm, metamath-knife, mmj2, mmverifypy, and hmm respectively in order to
> be able to run ./run-testsuite-all-drivers
>
> Respect to David Wheeler for getting it all running in the first place!
>
> The README (http://home.solcon.nl/mklooster/repos/hmm/README) says hmm
> was developed with GHC 6.4, and this is almost certainly the problem
> because neither the apt or apk package manager repositories seem to go back
> any further than the current major version of Haskell, GHC 9.x
>
> Any suggestions?  I'm afraid it's not my programming language, so I'm not
> going to be able to upgrade it myself.
>
> For the sake of completeness my attempted changes look like this
> https://github.com/Antony74/metamath-docker/compare/main...add-haskell-verifier
>
> # hmm: dependencies for building Haskell programs
> RUN apk add --no-cache ghc
> # hmm: get and build
> WORKDIR /build
> RUN curl https://us.metamath.org/downloads/hmm.zip -o hmm.zip
> RUN unzip hmm.zip -d .
> WORKDIR /build/hmm
> # RUN make
> And the errors I get when I run make:
>
> /build/hmm # make
> ghc -Wall -Werror -O -o hmmTest --make HmmTest
> [1 of 3] Compiling HmmImpl  ( HmmImpl.hs, HmmImpl.o )
>
> HmmImpl.hs:37:1: error: [-Wtabs, -Werror=tabs]
> Tab character found here, and in 756 further locations.
> Suggested fix: Please use spaces instead.
>|
> 37 | deriving (Eq, Show)
>| 
>
> HmmImpl.hs:94:40: error: [-Wincomplete-uni-patterns,
> -Werror=incomplete-uni-patterns]
> Pattern match(es) are non-exhaustive
> In a pattern binding:
> Patterns of type ‘Expression’ not matched:
> []
> ((Var _):_)
> [(Con _)]
> ((Con _):(Con _):_)
> ...
>|
> 94 | DollarF -> let [Con _c, Var v] = syms in
>|^^
>
> HmmImpl.hs:219:17: error: [-Wunused-do-bind, -Werror=unused-do-bind]
> A do-notation statement discarded a result of type ‘[()]’
> Suggested fix:
>   Suppress this warning by saying
> ‘_ <- many1 ((space >> return ()) <|> mmpComment)’
> |
> 219 | many1 ((space >> return ()) <|> mmpComment)
> | ^^^
>
> HmmImpl.hs:224:17: error: [-Wunused-do-bind, -Werror=unused-do-bind]
> A do-notation statement discarded a result of type ‘String’
> Suggested fix:
>   Suppress this warning by saying ‘_ <- try (string "$(")’
> |
> 224 | try (string "$(")
> | ^
>
> HmmImpl.hs:225:17: error: [-Wunused-do-bind, -Werror=unused-do-bind]
> A do-notation statement discarded a result of type ‘[Char]’
> Suggested fix:
>   Suppress this warning by saying
> ‘_ <- manyTill anyChar (try (space >> string "$)"))’
> |
> 225 | manyTill anyChar (try (space >> string "$)"))
> | ^
>
> HmmImpl.hs:279:17: error: [-Wunused-do-bind, -Werror=unused-do-bind]
> A do-notation statement discarded a result of type ‘String’
> Suggested fix: Suppress this warning by saying ‘_ <- string "$."’
> |
> 279 | string "$."
> | ^^^
>
> HmmImpl.hs:319:17: error: [-Wunused-do-bind, -Werror=unused-do-bind]
> A do-notation statement discarded a result of type ‘String’
> Suggested fix: Suppress this warning by saying ‘_ <- string "("’
> |
> 319 | string "("
> | ^^
>
> HmmImpl.hs:344:33: error: [-Wincomplete-uni-patterns,
> -Werror=incomplete-uni-patterns]
> Pattern match(es) are non-exhaustive
> In a pattern binding: Patterns of type ‘[Proof]’ not matched: []
> |
> 344 | newSubproofStack@(newSubproof:_) =
> (meaning !! n) subproofStack
> |
> ^^^
>
> HmmImpl.hs:400:17: error: [-Wunused-do-bind, -Werror=unused-do-bind]
> A do-notation statement discarded a result of type ‘String’
> Suggested fix: Suppress this warning by saying ‘_ <- string "$}"’
> |
> 400 | string "$}"
> | ^^^
>
> HmmImpl.hs:410:33: error: [-Wunused-do-bind, -Werror=unused-do-bind]
> A do-notation statement discarded a result 

Re: [Metamath] Help building hmm (Haskell Metamath verifier)

[Mario Carneiro]

On Mon, Mar 18, 2024 at 4:59 PM Antony Bartlett  wrote:

> The more I think about it, the more any attempt to maintain metamath-test
> without containerization seems insane.  You need to have C, C++, Rust,
> Java, Python, and Haskell installed, then use them to build metamath.exe,
> checkmm, metamath-knife, mmj2, mmverifypy, and hmm respectively in order to
> be able to run ./run-testsuite-all-drivers
>

As a docker noob, could you explain to me how containerization helps with
this in any way? You still have to have all those things, plus docker, if
you are doing it with containers.

-- 
You received this message because you are subscribed to the Google Groups 
"Metamath" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to metamath+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/metamath/CAFXXJSs%3Dv94Fermc-B7ASstgK5j6%2B%2B0%3D5EZcJminVQmr4OXGDA%40mail.gmail.com.

Re: [Metamath] metamath-test added to metamath-cmds docker image

[Mario Carneiro]

> I'm still not clear on the difference between running metamath-knife with
--verify and without, but I am very satisfied with this outcome, and
grateful for your assistance.

Running with --verify makes metamath-knife act like a traditional verifier:
it checks correctness of the metamath theorems and no more. The default
mode of metamath-knife does required processing only, which basically means
parsing the file. This is not particularly useful on its own, but because
there are lots of other flags with additive behavior this avoids needing to
do verification work if other things are requested (e.g. axiom-use /
discouraged generation, markup validation, etc).

On Sun, Mar 17, 2024 at 9:44 AM Antony Bartlett  wrote:

> Thanks for looking at that, Mario, that's really helpful.  I have added
> hyperfine to the metamath-cmds container (it's in github, I'll push to
> dockerhub later).  The 'warm up' functionality is particularly useful as
> --verify seems particularly susceptible to cold starts.  I've taken some
> benchmarks (below) and metamath-knife looks completely safe as expected.
> Containers of course cannot be relied on for absolute benchmarks - my
> Windows host system seems to take very roughly twice as long compared to
> running natively.  My concern when I compared your results with mine was
> that maybe containers can't be relied on for relative benchmarks either,
> but these look entirely in line with expectation.  I'm still not clear on
> the difference between running metamath-knife with --verify and without,
> but I am very satisfied with this outcome, and grateful for your assistance.
>
> I'm going to try and tidy up the changes to my copy of metamath-test, and
> maybe get a PR or two into the metamath-test repo too.  There's a regexp
> that didn't run for me and which I fear I've overly weakened, but if I need
> some help with that, will worry about it later.  This has all been prompted
> because I was telling someone on Reddit about how my TypeScript port of
> checkmm runs faster than the original C++.  In the best possible way they
> were sufficiently affronted by the idea of TypeScript running faster than
> C++ that they examined checkmm.cpp and apparently have found a serious
> performance flaw in it.  This work on the metamath-cmds container means
> that now I'm all ready to analyse a PR should I get one (otherwise I'll
> write it myself).
>
> https://www.reddit.com/r/node/comments/1bego9s/comment/kutgea1/
>
> =
> Metamath command line tools (https://github.com/Antony74/metamath-docker)
> =
>
> Please find below, an example command for each of the tools provided here:
>
> metamath "READ set.mm" "VERIFY PROOF *" "exit"
> checkmmc set.mm
> metamath-knife --verify set.mm
> echo -e "LoadFile,set.mm\nVerifyProof,*" > params.txt && mmj2 -f
> params.txt
> python3 mmverify.py set.mm
> checkmm set.mm
> prettier --write demo0.mm
> alt-mm set.mm
> cd /metamath-test && ./run-testsuite-all-drivers
>
> Prefix with time to measure how long a command took.
> Put command in quotes and prefix with hyperfine -w 2 -- to benchmark how
> long it takes.
>
> /set.mm # hyperfine -w 2 -- 'metamath-knife set.mm'
> Benchmark 1: metamath-knife set.mm
>   Time (mean ± σ): 354.7 ms ±  97.8 ms[User: 247.8 ms, System:
> 101.2 ms]
>   Range (min … max):   261.5 ms … 514.6 ms10 runs
>
> /set.mm # hyperfine -w 2 -- 'metamath-knife --verify set.mm'
> Benchmark 1: metamath-knife --verify set.mm
>   Time (mean ± σ):  2.351 s ±  0.214 s[User: 2.151 s, System:
> 0.200 s]
>   Range (min … max):2.099 s …  2.688 s10 runs
>
> /set.mm # hyperfine -w 2 -- 'metamath "READ set.mm" "VERIFY PROOF *"
> "exit" > output.log'
> Benchmark 1: metamath "READ set.mm" "VERIFY PROOF *" "exit" > output.log
>   Time (mean ± σ): 10.899 s ±  0.163 s[User: 10.341 s, System:
> 0.555 s]
>   Range (min … max):   10.739 s … 11.244 s10 runs
>
> /set.mm # hyperfine -w 2 -- 'echo -e "LoadFile,set.mm\nVerifyProof,*" >
> params.txt && mmj2 -f params.txt'
> Benchmark 1: echo -e "LoadFile,set.mm\nVerifyProof,*" > params.txt &&
> mmj2 -f params.txt
>   Time (mean ± σ): 10.039 s ±  0.241 s[User: 22.526 s, System:
> 1.711 s]
>   Range (min … max):9.479 s … 10.340 s10 runs
>
> /set.mm # hyperfine -w 2 -- 'checkmm set.mm'
> Benchmark 1: checkmm set.mm
>   Time (mean ± σ): 15.926 s ±  0.268 s[User: 19.688 s, System:
> 1.408 s]
>   Range (min … max):   15.589 s …

Re: [Metamath] metamath-test added to metamath-cmds docker image

[Mario Carneiro]

As far as I know and last I checked, metamath-knife can check set.mm in
sub-one-second with verification enabled, and about half a second with
verification disabled. It's possible that things have changed due to the
growth of set.mm?

Just checked again:

$ cargo build --release
$ hyperfine -w 2 -- "target/release/metamath-knife -v set.mm"
Benchmark 1: target/release/metamath-knife -v set.mm
  Time (mean ± σ):  1.367 s ±  0.052 s[User: 1.280 s, System: 0.085
s]
  Range (min … max):1.307 s …  1.464 s10 runs
$ hyperfine -w 2 -- "target/release/metamath-knife set.mm"
Benchmark 1: target/release/metamath-knife set.mm
  Time (mean ± σ): 199.7 ms ±  13.7 ms[User: 151.8 ms, System: 47.4
ms]
  Range (min … max):   185.6 ms … 236.6 ms15 runs

so a bit more than a second now, and without verification it's even less
than I remember, probably because the default profile has more things
disabled than there used to be.

On Sat, Mar 16, 2024 at 5:59 PM Antony Bartlett  wrote:

> metamath-cmds is a docker image where I've collected a number of metamath
> command line tools together for convenience (metamath.exe, metamath-knife,
> mmj2, checkmm, checkmm-ts, mmverify.py).
>
> Today I have updated this image, so if you run
>
> docker run -it akb74/metamath-cmds
>
> you will be in a command line which has all the latest versions of these
> tools and the latest set.mm.  However, the last time I did this was two
> years ago, so most of the time you'd be better off following the
> instructions in the github repository
>
> https://github.com/Antony74/metamath-docker
>
> Today I have also added metamath-test (
> https://github.com/david-a-wheeler/metamath-test) to the commands
> available.  This is a useful collection of good .mm files which a verifier
> is expected to pass, and bad .mm files which a verifier is expected to
> fail.  I had to patch my copy of the test harness considerably to get it to
> run in the metamath-cmds container, some of which is due to the
> environment, but additionally I think the suite itself may be a little out
> of date?
>
> Finally, I have a question about metamath-knife.  In order for the test
> suite to pass, you have to set the --verify parameter.  However, if you do
> that, it seems metamath-knife loses much of its fabled speed.  So I'm
> wondering in what sense metamath-knife can be considered a sub-one-second
> verifier if it doesn't pass the test suite in this mode?  Sorry if that
> sounds impertinent, I'd just like to understand the distinction, I'm sure
> it's doing the most important checks really fast.
>
> Thanks,
>
> Best regards,
>
> Antony
>
> --
> You received this message because you are subscribed to the Google Groups
> "Metamath" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to metamath+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/metamath/CAJ48g%2BASabinmU590eC41US0So42YSeuMdbR0GUwenj0P1Fd%2Bw%40mail.gmail.com
> 
> .
>

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

Re: [edk2-devel] [PATCH 1/1] MdeModulePkg/UefiBootManagerLib: Build proper SD/MMC boot descriptions

[Mario Bălănică]

Bump


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116818): https://edk2.groups.io/g/devel/message/116818
Mute This Topic: https://groups.io/mt/103516251/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [edk2-devel] [PATCH 1/1] MdeModulePkg/SdMmcPciHcDxe: Support override for SD 1.8v signaling switch

[Mario Bălănică]

Can someone please take a look at this?


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116817): https://edk2.groups.io/g/devel/message/116817
Mute This Topic: https://groups.io/mt/103516142/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[kwin] [Bug 482178] Wayland renders the whole desktop in half refresh rate

[Mario Ray Mahardhika]

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

--- Comment #9 from Mario Ray Mahardhika  ---
6.0.2 arrives to Neon, and I can confirm it's fixed.

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

Re: Error en barman

[Mario González Troncoso]

On Fri, 15 Mar 2024 at 13:44, Guillermo E. Villanueva
 wrote:
>
> Hola les paso algunas lineas de lo que me sale ahora en el log con nivel de 
> log en DEBUG
[...]
>

Gracias por los logs. Logre reproducir el problema. Tiene que ver con
`config_changes_queue`, eso fue introducido en Barman 3.10.x y parece
que no hicimos una buena pega al documentar. Me fije que en tu config
lo tienes declarado asi, que parece que es el default:
"config_changes_queue": "/var/lib/barman/cfg_changes.queue"

Puedes contarnos que tienes actualmente en ese archivo? algo como `cat
/var/lib/barman/cfg_changes.queue`

El contenido de ese archivo debe ser json pero si por alguna razón se
escribe con algo diferente, falla misteriosamente. Si lo quieres
re-crear desde cero simplemente lo borras y barman debería encargarse
de dejar una lista de items vacia. Luego de eso el problema debe haber
desaparecido.

Cuéntanos.

> El jue, 14 mar 2024 a las 12:20, Jaime Soler () 
> escribió:
>>
>> Buenas Guillermo,
>>
>> Con la info que has pasado, no se vé claro que puede ser. Tal como decía 
>> Mario, será mejor que pongas el log en debug , un momento , y así capturas 
>> más detalles del error
>> según aparece en el código de barman ( 
>> https://github.com/EnterpriseDB/barman/blob/26ed480cd0268dfd3f8546cc97660d4bd827772a/barman/config.py#L2054-L2070
>>  )
>> Para ponerlo en debug, es cambiando el parámetro log_level =DEBUG , en el 
>> fichero barman.conf
>>
>> Un saludo
>>
>> El jue, 14 mar 2024 a las 14:24, Guillermo E. Villanueva 
>> () escribió:
>>>
>>> Les paso el diagnose y el contenido del archivo de configuración del server 
>>> santacruz
>>> A pesar de que todo parece funcionar bien, el log sigue mostrando el error 
>>> mencionado.
>>> /etc/braman.d/santacruz.conf
>>> [santacruz]
>>> description =  "PJud de Santa Cruz Pg (via SSH)"
>>> backup_directory = /home/barman/santacruz
>>> ssh_command = ssh postgres@192.168.172.33
>>> conninfo = host=192.168.172.33 port=5432 user=barman password=xxx 
>>> dbname=postgres
>>> backup_method = rsync
>>> streaming_archiver = off
>>> archiver = on
>>>
>>>
>>> El mié, 13 mar 2024 a las 13:08, Jaime Soler () 
>>> escribió:
>>>>
>>>> ¿ Puedes compartir la salida de barman diagnose y la configuración del 
>>>> fichero de backup de tu servidor que se guarda dentro de /etc/barman.d ? , 
>>>> parece como si no parseara bien alguno de los ficheros de configuración y 
>>>> lo que compartiste parece que está bien, por eso te pido el otro fichero.
>>>>
>>>> Un saludo
>>>>
>>>> El mié, 13 mar 2024 a las 14:24, Guillermo E. Villanueva 
>>>> () escribió:
>>>>>
>>>>> Hola buen día, en un debian 11 instalé barman 3.10, ya lo configuré para 
>>>>> backups con rsync y parece que va todo ok, los wal llegan correctamente y 
>>>>> el primer full funcionó correctamente pero en el log de barman, cada 
>>>>> minuto tengo el siguiente error:
>>>>>
>>>>> .  [3029] barman.config ERROR: Cannot execute None: Expecting value: 
>>>>> line 1 column 1 (char 0)
>>>>>
>>>>> El archivo barman.conf tiene lo siguiente:
>>>>> [barman]
>>>>> barman_user = barman
>>>>> configuration_files_directory = /etc/barman.d
>>>>> backup_options = exclusive_backup
>>>>> reuse_backup = link
>>>>> barman_home = /var/lib/barman
>>>>> log_file = /var/log/barman/barman.log
>>>>> log_level = ERROR
>>>>> compression = gzip
>>>>> immediate_checkpoint = true
>>>>> basebackup_retry_times = 3
>>>>> basebackup_retry_sleep = 30
>>>>> last_backup_maximum_age = 7 DAYS
>>>>> retention_policy = RECOVERY WINDOW OF 3 WEEKS
>>>>>
>>>>> barman check all tambien me da todo ok.
>>>>>
>>>>> ¿Qué podrá ser lo del error que muestra el log?
>>>>> Desde ya muchas gracias!
>>>>>


-- 
https://www.linkedin.com/in/gonzalemario

Re: Chromium can't be compiled because a bug with webrtc.

[Mario Marietto]

Hello.

On FreeBSD 13.3 I'm trying to install Chromium,but the compilation stopped
because a bug :

.
/usr/local/include  -c ../../third_party/webrtc/api/candidate.cc -o
obj/third_party/webrtc/api/candidate/candidate.o
In file included from ../../third_party/webrtc/api/candidate.cc:11:
In file included from ../../third_party/webrtc/api/candidate.h:24:
In file included from
./../third_party/webrtc/rtc_base/socket_address.h:20:
In file included from ../../third_party/webrtc/rtc_base/ip_address.h:30:

./../third_party/webrtc/rtc_base/byte_order.h:114:18: error: use of
undeclared identifier 'htobe16'
 114 |   uint16_t val = htobe16(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:119:18: error: use of
undeclared identifier 'htobe32'
 119 |   uint32_t val = htobe32(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:124:18: error: use of
undeclared identifier 'htobe64'
 124 |   uint64_t val = htobe64(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:131:10: error: use of
undeclared identifier 'be16toh'
 131 |   return be16toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:137:10: error: use of
undeclared identifier 'be32toh'
 137 |   return be32toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:143:10: error: use of
undeclared identifier 'be64toh'
 143 |   return be64toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:147:18: error: use of
undeclared identifier 'htole16'
 147 |   uint16_t val = htole16(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:152:18: error: use of
undeclared identifier 'htole32'
 152 |   uint32_t val = htole32(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:157:18: error: use of
undeclared identifier 'htole64'
 157 |   uint64_t val = htole64(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:164:10: error: use of
undeclared identifier 'le16toh'
 164 |   return le16toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:170:10: error: use of
undeclared identifier 'le32toh'
 170 |   return le32toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:176:10: error: use of
undeclared identifier 'le64toh'
 176 |   return le64toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:189:10: error: use of
undeclared identifier 'htobe16'
 189 |   return htobe16(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:193:10: error: use of
undeclared identifier 'htobe32'
 193 |   return htobe32(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:197:10: error: use of
undeclared identifier 'htobe64'
 197 |   return htobe64(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:201:10: error: use of
undeclared identifier 'be16toh'
 201 |   return be16toh(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:205:10: error: use of
undeclared identifier 'be32toh'
 205 |   return be32toh(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:209:10: error: use of
undeclared identifier 'be64toh'
 209 |   return be64toh(n);
 |  ^
18 errors generated.
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/chromium
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium

On Thu, Mar 14, 2024 at 11:02 PM Mario Marietto 
wrote:

> Hello.
>
> On FreeBSD 13.3 I'm trying to install Chromium,but the compilation stopped
> because a bug :
>
> ..
> /usr/local/include  -c ../../third_party/webrtc/api/candidate.cc -o
> obj/third_party/webrtc/api/candi
> date/candidate.o
> In file included from ../../third_party/webrtc/api/candidate.cc:11:
> In file included from ../../third_party/webrtc/api/candidate.h:24:
> In file included from
> ../../third_party/webrtc/rtc_base/socket_address.h:20:
> In file included from ../../third_party/webrtc/rtc_base/ip_address.h:30:
> ../../third_party/webrtc/rtc_base/byte_order.h:114:18: error: use of
> undeclared identifier 'htobe16'
>  114 |   uint16_t val = htobe16(v);
>  |  ^
> ../../third_party/webrtc/rtc_base/byte_order.h:119:18: error: use of
> undeclared identifier 'htobe32'
>  119 |   uint32_t val = htobe32(v);
>  |  ^
> ../../third_party/webrtc/rtc_base/byte_order.h:124:18: error: use of
> undeclared identifier 'htobe64'
>  124 |   uint64_t val = htobe64(v);
>  |  ^
> ../../third_party/webrtc/rtc_base/byte_order.h:131:10: error: use of
> undeclared identifier 'be16toh'
>  131 |   return be16toh(val);
>  |  ^
> ../../third_party/webrtc/rtc_base/byte_order.h:137:10: error: use of
> undeclared identifier 'be32toh'
>  137 |   return be32toh(val);
>  |  ^
> ../../third_party/webrtc/rt

Chromium can't be compiled because a bug with webrtc.

[Mario Marietto]

Hello.

On FreeBSD 13.3 I'm trying to install Chromium,but the compilation stopped
because a bug :

.
/usr/local/include  -c ../../third_party/webrtc/api/candidate.cc -o
obj/third_party/webrtc/api/candi
date/candidate.o
In file included from ../../third_party/webrtc/api/candidate.cc:11:
In file included from ../../third_party/webrtc/api/candidate.h:24:
In file included from
./../third_party/webrtc/rtc_base/socket_address.h:20:
In file included from ../../third_party/webrtc/rtc_base/ip_address.h:30:
./../third_party/webrtc/rtc_base/byte_order.h:114:18: error: use of
undeclared identifier 'htobe16'
 114 |   uint16_t val = htobe16(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:119:18: error: use of
undeclared identifier 'htobe32'
 119 |   uint32_t val = htobe32(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:124:18: error: use of
undeclared identifier 'htobe64'
 124 |   uint64_t val = htobe64(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:131:10: error: use of
undeclared identifier 'be16toh'
 131 |   return be16toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:137:10: error: use of
undeclared identifier 'be32toh'
 137 |   return be32toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:143:10: error: use of
undeclared identifier 'be64toh'
 143 |   return be64toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:147:18: error: use of
undeclared identifier 'htole16'
 147 |   uint16_t val = htole16(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:152:18: error: use of
undeclared identifier 'htole32'
 152 |   uint32_t val = htole32(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:157:18: error: use of
undeclared identifier 'htole64'
 157 |   uint64_t val = htole64(v);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:164:10: error: use of
undeclared identifier 'le16toh'
 164 |   return le16toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:170:10: error: use of
undeclared identifier 'le32toh'
 170 |   return le32toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:176:10: error: use of
undeclared identifier 'le64toh'
 176 |   return le64toh(val);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:189:10: error: use of
undeclared identifier 'htobe16'
 189 |   return htobe16(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:193:10: error: use of
undeclared identifier 'htobe32'
 193 |   return htobe32(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:197:10: error: use of
undeclared identifier 'htobe64'
 197 |   return htobe64(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:201:10: error: use of
undeclared identifier 'be16toh'
 201 |   return be16toh(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:205:10: error: use of
undeclared identifier 'be32toh'
 205 |   return be32toh(n);
 |  ^
./../third_party/webrtc/rtc_base/byte_order.h:209:10: error: use of
undeclared identifier 'be64toh'
 209 |   return be64toh(n);
 |  ^
18 errors generated.
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/www/chromium
*** Error code 1

Stop.
make: stopped in /usr/ports/www/chromium

-- 
Mario.

[seL4] R: DIFFICULTY RUNNING SEL4TEST ON RASPBERRY PI 4 REV 1.5 4GB

[Mario CUSANO via Devel]

processor   : 0
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

processor   : 1
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

processor   : 2
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

processor   : 3
BogoMIPS: 108.00
Features: fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd08
CPU revision: 3

Revision: c03115
Serial  : 1000fb1b38b1
Model   : Raspberry Pi 4 Model B Rev 1.5
U-Boot 2024.04-rc4 (Mar 12 2024 - 17:05:43 +0100)

DRAM:  128 MiB (effective 3.1 GiB)
RPI 4 Model B (0xc03115)
Core:  210 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, mmc@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... 
In:serial,usbkbd
Out:   serial,vidconsole
Err:   serial,vidconsole
Net:   eth0: ethernet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
Hit any key to stop autoboot:  0 
Card did not respond to voltage select! : -110
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 2 USB Device(s) found
ethernet@7d58 Waiting for PHY auto negotiation to complete. TIMEOUT 
!
bcmgenet: PHY startup failed: -110
ethernet@7d58 Waiting for PHY auto negotiation to complete. TIMEOUT 
!
bcmgenet: PHY startup failed: -110
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> printenv 
arch=arm
baudrate=115200
board=rpi
board_name=4 Model B
board_rev=0x11
board_rev_scheme=1
board_revision=0xC03115
boot_targets=mmc usb pxe dhcp
bootcmd=bootflow scan
bootdelay=2
cpu=armv8
dfu_alt_info=u-boot.bin fat 0 1;uboot.env fat 0 1; config.txt fat 0 1;Image fat 
0 1
dhcpuboot=usb start; dhcp u-boot.uimg; bootm
ethact=ethernet@7d58
ethaddr=d8:3a:dd:b0:3f:a0
fdt_addr=7fe2500
fdt_addr_r=0x0260
fdt_high=
fdtcontroladdr=7b1a2e0
fdtfile=broadcom/bcm2711-rpi-4-b.dtb
initrd_high=
kernel_addr_r=0x0008
loadaddr=0x100
preboot=pci enum;
pxefile_addr_r=0x0250
ramdisk_addr_r=0x0270
scriptaddr=0x0240
serial#=1000fb1b38b1
soc=bcm283x
stderr=serial,vidconsole
stdin=serial,usbkbd
stdout=serial,vidconsole
usbethaddr=d8:3a:dd:b0:3f:a0
vendor=raspberrypi

Environment size: 814/16380 bytes
U-Boot> 

U-Boot 2024.04-rc4 (Mar 12 2024 - 17:05:43 +0100)

DRAM:  128 MiB (effective 3.1 GiB)
RPI 4 Model B (0xc03115)
Core:  210 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e30: 1, mmc@7e34: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... 
In:serial,usbkbd
Out:   serial,vidconsole
Err:   serial,vidconsole
Net:   eth0: ethernet@7d58
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
Hit any key to stop autoboot:  0 
Card did not respond to voltage select! : -110
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 2 USB Device(s) found
ethernet@7d58 Waiting for PHY auto negotiation to complete. TIMEOUT 
!
bcmgenet: PHY startup failed: -110
ethernet@7d58 Waiting for PHY auto negotiation to complete. TIMEOUT 
!
bcmgenet: PHY startup failed: -110
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> fatls mmc 0
.Trash-1001/
   648648   u-boot.bin
overlays/
52476   bootcode.bin
  2256224   start4.elf
54809   bcm2711-rpi-4-b.dtb
  5234944   sel4test-driver-image-arm-bcm2711
   52   config.txt

6 file(s), 2 dir(s)

U-Boot> fatload mmc 0 0x1000 sel4test-driver-image-arm-bcm2711
** Reading file would overwrite reserved memory **
Failed to load 'sel4test-driver-image-arm-bcm2711'
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> fatload mmc 0 ${kernel_addr_r} sel4test-driver-image-arm-bcm2711 
5234944 bytes read in 237 ms (21.1 MiB/s)
U-Boot> go ${kernel_addr_r}
## Starting application at 0x0008 ...



___
Devel mailing list -- devel@sel4.systems
To unsubscribe send an email to devel-leave@sel4.systems

C_Initialize failed: 0x00000030, CKR_DEVICE_ERROR

[Mario Marietto]

On FreeBSD 13.3 :

root@marietto-132:/usr/ports/security/nss # make MAKE_JOBS_UNSAFE=ye

.
/usr/ports/security/nss/work/nss-3.98/nss/cmd/shlibsign/FreeBSD13.3_OPT.OBJ/shlibsign
-v -i /usr/por
ts/security/nss/work/nss-3.98/nss/cmd/shlibsign/../../../dist/FreeBSD13.3_OPT.OBJ/lib/libsoftokn3.so

moduleSpec configdir='' certPrefix='' keyPrefix='' secmod=''
flags=noCertDB, noModDB
C_Initialize failed: 0x0030, CKR_DEVICE_ERROR
NSPR error code: -5977: Failure to load dynamic library
Initiailzing softoken failed: 0x0030, CKR_DEVICE_ERROR

NSPR error code: -5977: Failure to load dynamic library
gmake[4]: *** [Makefile:92:
./../../dist/FreeBSD13.3_OPT.OBJ/lib/libsoftokn3.chk] Error 1
gmake[4]: Leaving directory
'/usr/ports/security/nss/work/nss-3.98/nss/cmd/shlibsign'
gmake[3]: *** [Makefile:100: libs] Error 2
gmake[3]: Leaving directory
'/usr/ports/security/nss/work/nss-3.98/nss/cmd/shlibsign'
gmake[2]: *** [../coreconf/rules.mk:44: shlibsign] Error 2
gmake[2]: Leaving directory '/usr/ports/security/nss/work/nss-3.98/nss/cmd'
gmake[1]: *** [coreconf/rules.mk:44: cmd] Error 2
gmake[1]: Leaving directory '/usr/ports/security/nss/work/nss-3.98/nss'
gmake: *** [manifest.mn:21: all] Error 2
*** Error code 1

-- 
Mario.

Re: [Gvsig_usuarios] GvSig se cierra

[Mario Carrera]

La autenticidad de este mensaje no ha podido ser verificada, por lo que podría 
ser malicioso. Recomendamos que no abra ningún enlace ni adjunto incluido en 
él, y ante la duda se verifique la autenticidad contactando con el emisor por 
medios alternativos (p.e. por teléfono).

L'autenticitat d'aquest missatge no ha pogut ser verificada, per la qual cosa 
podria ser maliciós. Recomanem que no òbriga cap enllaç ni adjunt inclòs en 
ell, i davant el dubte es verifique l'autenticitat contactant amb l'emissor per 
mitjans alternatius (p.e. per telèfon).

Buenos días Roberto,

¿qué versión de gvSIG estás utilizando? ¿Es la versión portable o la 
instalable?


Por el tipo de error parece que puede ser algún problema con la 
instalación, como si se hubiese descargado el fichero corrupto, por una 
posible caída de red, o porque haya habido problema al instalar después.


Si estabas utilizando la versión instalable (que la instalarías con el 
asistente), como prueba inicial puedes descargar la versión portable. 
Solo debes descomprimir el zip en una ruta sin espacios ni acentos, y ya 
puedes ejecutarlo. Puedes por ejemplo crear una carpeta "gvSIG" en C:\ y 
descomprimirla ahí dentro.


Prueba si así te funciona bien y nos comentas.

En paralelo, para ver qué podría ocurrir, si tenías la instalable, si 
vas a la carpeta C:\Usuarios\[tu_usuario]\gvSIG, tendrás varios ficheros 
"gvSIG" (gvSIG.log...). Haz un zip con ellos y lo adjuntas, así podemos 
ver si está la traza del error.


Un saludo,
  Mario Carrera

El 13/3/24 a las 21:16, Roberto Núñez escribió:

Buenas tardes:
He instalado GvSig porque estoy haciendo un curso sobre el programa.
Lo primero, no sale entre los programas instalados en el PC, aunque sí 
veo la carpeta en la dirección descargada.

La versión desktop del ordenador, directamente no se abre.
La versión desktop que ejecuto desde un pen sí se abre, pero en cuanto 
pulso un botón o intento hacer una operación, se cierra.

¿Saben qué puede pasar?
¿A dónde debo dirigirme?
¿Me pueden ayudar?
Un saludo
Roberto Núñez Conde

___
gvSIG_usuarios mailing list
gvSIG_usuarios@listserv.gva.es

Para ver histórico de mensajes, editar sus preferencias de usuario o darse de 
baja en esta lista, acuda a la siguiente dirección:

https://listserv.gva.es/mailman/listinfo/gvsig_usuarios


--

*Mario Carrera*

gvSIG Association / Asociación gvSIG

http://www.gvsig.com <http://www.gvsig.com/>


Antes de imprimir este e-mail piense bien si es necesario hacerlo.

AVISO LEGAL: Este mensaje y sus archivos adjuntos van dirigidos 
exclusivamente a su destinatario, pudiendo contener información 
confidencial sometida a secreto profesional. No está permitida su 
comunicación, reproducción o distribución sin la autorización expresa de 
la Asociación gvSIG. Si usted no es el destinatario final, por favor 
elimínelo e infórmenos por esta vía.


PROTECCIÓN DE DATOS: De conformidad con lo dispuesto en las normativas 
vigentes en protección de datos personales, el Reglamento (UE) 2016/679 
de 27 de abril de 2016 (GDPR) y la Ley Orgánica (ES) 15/1999 de 13 de 
diciembre (LOPD), le informamos que los datos personales y dirección de 
correo electrónico, recabados del propio interesado o de fuentes 
públicas, serán tratados bajo la responsabilidad de la /Asociación gvSIG 
/para el envío de comunicaciones sobre nuestros productos y servicios y 
se conservarán mientras exista un interés mutuo para ello. Los datos no 
serán comunicados a terceros, salvo obligación legal. Le informamos que 
puede ejercer los derechos de acceso, rectificación, portabilidad y 
supresión de sus datos y los de limitación y oposición a su tratamiento 
dirigiéndose enviando un mensaje al correo electrónico a i...@gvsig.com. 
Si considera que el tratamiento no se ajusta a la normativa vigente, 
podrá presentar una reclamación ante la autoridad de control en 
www.agpd.es <http://www.agpd.es/>.


___
gvSIG_usuarios mailing list
gvSIG_usuarios@listserv.gva.es

Para ver histórico de mensajes, editar sus preferencias de usuario o darse de 
baja en esta lista, acuda a la siguiente dirección:

https://listserv.gva.es/mailman/listinfo/gvsig_usuarios

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?

-- 
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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?

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

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


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

Re: [aspectj-users] AspectJ 1.9.21.2 maintenance release

[Mario Ivankovits via aspectj-users]

As always! Thank you! :-)

As a short heads up, I have some issues with that version and the version 
before within the IDE. I just filed a bug with IntellilJ about that.

https://youtrack.jetbrains.com/issue/IDEA-349094/Cannot-read-the-array-length-because-buf-is-null


Had not much change right now to look into that in more detail. But might be 
able to do so if required.


Best regards

Mario


> Am 13.03.2024 um 10:50 schrieb Alexander Kriegisch via aspectj-users 
> :
> 
> Dear AspectJ users,
> 
> we are pleased to announce the AspectJ maintenance release 1.9.21.2 
> supporting Java 21. Please note that since 1.9.19, the minor-minor version 
> indicates the corresponding latest Java release (byte code version) supported 
> by the AspectJ compiler and weaver. I.e., 1.9.21.2 → Java 21.
> 
>  
> Improvements
> 
> Previously, when targeting the same join point from multiple around advices 
> in annotation-style @AspectJ syntax, there were limitations in functionality 
> in concurrent (multi-threaded) situations, if the around advice code was not 
> inlined. This was improved in AspectJ 1.9.9 
> <https://eclipse.dev/aspectj/doc/latest/release/README-1.9.9#async_proceed> 
> (see also issue #128 
> <https://github.com/eclipse-aspectj/aspectj/issues/128>), but the improvement 
> only applied to child threads directly created during aspect execution and 
> would fail for pre-existing, long-lived threads, e.g. thread pools used by 
> executor services. Furthermore, the improvement could lead to memory leaks, 
> not cleaning up thread-local references to posssibly expensive objects. In 
> such situations, users had to switch to native-syntax aspects which never had 
> that problem to begin with due to their different internal structure.
>  
> Now, issue #141 <https://github.com/eclipse-aspectj/aspectj/issues/141> has 
> been resolved, closing the gap and, as well as possible given their different 
> internal structure, bringing @AspectJ aspects up to par with native-syntax 
> aspects in concurrent situations, while simultaneously also addressing the 
> memory leak issue #288 
> <https://github.com/eclipse-aspectj/aspectj/issues/288>. This is a 
> substantial improvement, and annotation-style syntax users are strongly 
> engouraged to upgrade. Thanks to user pagrawalgit for raising the memory leak 
> issue and triggering me to think about the concurrency issue more broadly and 
> finally solve both in one shot.
> Other changes and bugfixes
> 
> The fix for issue #277 
> <https://github.com/eclipse-aspectj/aspectj/issues/277> in AspectJ 1.9.21.1 
> introduced a regression bug in the optional weaving cache now fixed in issue 
> #285 <https://github.com/eclipse-aspectj/aspectj/issues/285>. Thanks to user 
> Kimming Lau for raising and re-testing both issues.
> 
> Other notes about 1.9.21.x
> 
> Since 1.9.21, the AspectJ compiler AJC (contained in the aspectjtools 
> library) no longer works on JDKs 11 to 16. The minimum compile-time 
> requirement is now JDK 17 due to upstream changes in the Eclipse Java 
> Compiler (subset of JDT Core), which AspectJ is a fork of. You can still 
> compile to legacy target versions as low as Java 1.3 when compiling plain 
> Java code or using plain Java ITD constructs which do not require the AspectJ 
> runtime aspectjrt, but the compiler itself needs JDK 17+. Just like in 
> previous AspectJ versions, both the runtime aspectjrt and the load-time 
> weaver aspectjweaver still only require JRE 8+.
> History: Since 1.9.7, the AspectJ compiler AJC needed JDK 11+, before then 
> JDK 8+.
> Resources
> 
> For more detailed release information, please read the release notes 
> <https://eclipse.dev/aspectj/doc/latest/release/README-1.9.21.html#_aspectj_1_9_21_2>.
> The current artifacts (runtime, weaver, compiler, matcher) are available on 
> Maven Central.
> The AspectJ installer can be found on GitHub 
> <https://github.com/eclipse/org.aspectj/releases/tag/V1_9_21_2>.
> There is also an AJDT update site for Eclipse 4.30 (2023-12) 
> <https://download.eclipse.org/tools/ajdt/430/dev/update>. Unfortunately, 
> updates sites for previous Eclipse versions , e.g. 4.26 (2022-12) and 4.23 
> (2022-03) are no longer compatible with AspectJ 1.9.21, because the latter 
> dependes on upstream Eclipse changes. So if you want to use ADJT builds with 
> Eclipse IDE, you need to upgrade to 2023-12. Otherwise, you can only use 
> AspectJ 1.9.21 via Maven build, not via direct IDE. On top of that, you also 
> need an extra update site for Eclipse 2023-12 itself 
> <https://download.eclipse.org/eclipse/updates/4.31-I-builds/I20231201-1800/>. 
> The IDE guide 
> <https://github.com/eclipse-aspectj/aspectj/blob/master

Re: Error en barman

[Mario González Troncoso]

On Wed, 13 Mar 2024 at 10:24, Guillermo E. Villanueva
 wrote:
>
> Hola buen día, en un debian 11 instalé barman 3.10, ya lo configuré para 
> backups con rsync y parece que va todo ok, los wal llegan correctamente y el 
> primer full funcionó correctamente pero en el log de barman, cada minuto 
> tengo el siguiente error:
>
> .  [3029] barman.config ERROR: Cannot execute None: Expecting value: line 
> 1 column 1 (char 0)
>

Viendo el código, ocurre cuando hay una doble excepción. Puedes
cambiar a modo debug con `-d` y enviar lo relevante del log por favor?

El "None" es el cambio en la configuración que debería haberse
aplicado pero por alguna razón fallo. En debug se puede ver más
información. No es el mejor approach pero nunca había visto ese
mensaje.

> El archivo barman.conf tiene lo siguiente:
> [barman]
> barman_user = barman
> configuration_files_directory = /etc/barman.d
> backup_options = exclusive_backup
> reuse_backup = link
> barman_home = /var/lib/barman
> log_file = /var/log/barman/barman.log
> log_level = ERROR
> compression = gzip
> immediate_checkpoint = true
> basebackup_retry_times = 3
> basebackup_retry_sleep = 30
> last_backup_maximum_age = 7 DAYS
> retention_policy = RECOVERY WINDOW OF 3 WEEKS
>
> barman check all tambien me da todo ok.
>
> ¿Qué podrá ser lo del error que muestra el log?
> Desde ya muchas gracias!
>


-- 
https://www.linkedin.com/in/gonzalemario

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.

If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.

-- 
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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.

If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


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

[Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.

If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.

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

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


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

Re: Alto consumo de procesador

[Mario González Troncoso]

On Mon, 8 Jan 2024 at 06:24, Alvaro Herrera  wrote:
>
> Fernando Siguenza escribió:
> > Amigos, su ayuda porfa tengo un servidor en debian con postgres ejecutando 
> > un sistema en php, estaba funcionando bein pero desde el viernes veo que el 
> > consumo del procesador esta altisimo y es por los procesos del postgres
>
> Ugh, suena a que tienes un cryptominero, algo como
> https://unit42.paloaltonetworks.com/pgminer-postgresql-cryptocurrency-mining-botnet/
>

Fernando, lograste identificar si fue algo relacionado? sería
interesante conocer, (si fue ataque) si usaron algún usuario con
permiso "pg_execute_server_program" activado.

> Condolencias,
>
> --
> Álvaro Herrera PostgreSQL Developer  —  https://www.EnterpriseDB.com/
> "La primera ley de las demostraciones en vivo es: no trate de usar el sistema.
> Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)
>
>


-- 
https://www.linkedin.com/in/gonzalemario

RE: Accessible doorbell systems

[Mario Eiland]

Yes it does. That’s how we know if anyone has stepped on to our porch. WE do 
have another camera to broaden the range, but it became a bit annoying since it 
saw people walking by.

 

From: viphone@googlegroups.com  On Behalf Of Peter 
Tesar
Sent: Tuesday, March 12, 2024 1:20 PM
To: viphone@googlegroups.com
Subject: Re: Accessible doorbell systems

 

Hello,

 

What I need is a motion detector. I don't need another doorbell.

Currently I have the logenex intercom, teledoorBell. The intercom box on the 
outside has a door bell button. Inside, the home phones ring (with a distinct 
pattern). Cordless phones can be moved around easily for convenience. 

Someone mentioned that the Ring doorbell pro has a motion detector. 

Having two door bell buttons would be confusing to door visitors. 

 

Is there an iPhone app for a motion detector?

This would warn me when there is a delivery: package, groceries etc. 

 

Peter T.

 

 

 

On 2024-03-11 7:51 AM, Mario Eiland wrote:

The doorbell has to be installed outside like your standard doorbell. I had 
someone sighted do that for me. Actually, I had a professional do it for me. I 
think that’s all you would need, accept I went further by purchasing a wireless 
chime that was place upstairs so if the doorbell was rang then it could be 
heard in every echo in the house plus your smart phone.

It’s been several years ago since I bought the equipment.

Ring Chime Pro - $44.99

Ring Video Doorbell 2 - $134.99

Installation was $58.49.

Just remember this was 3 years ago.

 

Hope that helps.

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>   
<mailto:viphone@googlegroups.com>  On Behalf Of 
djrisav...@att.net <mailto:djrisav...@att.net> 
Sent: Sunday, March 10, 2024 9:59 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

Yes that’s what was looking for and asfter when asking.

So how do they come and are they wired or wireless?

I have the Alexa devices from amazon plus my iPhone and google home too.

Are they expensive?

Thanks.

 

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Mario Eiland
Sent: Sunday, March 10, 2024 9:23 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

Hi Don,

 

When asking about accessible doorbells, what do you mean by accessible? How 
accessible would you like it to be?

I also use the Ring doorbell and I have it integrated with everybody’s  iPhone 
who lives in the house plus our Echo devices. Any time anyone nears our house 
porch we receive announcements that it detected motion. If someone rings the 
doorbell we have the option to either pick it up via the Ring app on our 
iPhones or the Alexa by simply asking Alexa to answer doorbell. For those who 
can see can activate the camera on their phones and see who is at the door. 
Unfortunately, it doesn’t identify the person for me yet. I’m hoping that’s 
near in the future with the advancement of AI. But for now I love it since we 
are notified any time we have a package dropped off and if anyone is home then 
we can immediately retrieve it.

I’m not sure how it integrates with the Google Home, but with the Echo devices 
you can download, what they call a Skill with the Alexa app and as long as you 
have a Ring account establish then you can sign into the Ring Skill and 
integrate it with your Echo. It’s pretty awesome!

Hope that helps some!

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Esther Levegnale
Sent: Sunday, March 10, 2024 6:05 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: Re: Accessible doorbell systems

 

I believe ring doorbell is a good one. Anyway, good luck. Esther.

Sent From Esther's Amazing and Awesome iPhone 13 Pro Max!

 

On Mar 10, 2024, at 6:25 AM, djrisav...@att.net <mailto:djrisav...@att.net>  
wrote:



Hello all,

I was wondering what anyone suggest or recommend as the most accessible and 
also affordable doorbell system is for a single widower person living in a 
small size condo that can be accessed with various devices like iPhones, google 
home or Alexa and how easy are they to set up?

Thanks.

Don

 

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu <mailto:mk...@ucla.edu> . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com <mailto:caraqu...@caraquinn.com> 
 
The archives for this list can be search

RE: Accessible doorbell systems

[Mario Eiland]

Yes. Here for example, we say, “Alexa answer doorbell.” And it connects us with 
the person outside.

 

From: viphone@googlegroups.com  On Behalf Of 
djrisav...@att.net
Sent: Tuesday, March 12, 2024 12:34 PM
To: viphone@googlegroups.com
Subject: RE: Accessible doorbell systems

 

Yes and don’t think would need the extra doorbell chime since live in a one 
story condo that has three of the amazon Alexa devices throughout my place.

I’m sure can get someone like my Dad who is an electrical engineer to wire the 
doorbell up or someone from the condo association or hire someone to do it.

So excuse me if this has already been answered from others; but, take it  that 
can talk back and forth through the system when someone rings the doorbell?

Thanks.

 

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Mario Eiland
Sent: Monday, March 11, 2024 7:52 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

The doorbell has to be installed outside like your standard doorbell. I had 
someone sighted do that for me. Actually, I had a professional do it for me. I 
think that’s all you would need, accept I went further by purchasing a wireless 
chime that was place upstairs so if the doorbell was rang then it could be 
heard in every echo in the house plus your smart phone.

It’s been several years ago since I bought the equipment.

Ring Chime Pro - $44.99

Ring Video Doorbell 2 - $134.99

Installation was $58.49.

Just remember this was 3 years ago.

 

Hope that helps.

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
djrisav...@att.net <mailto:djrisav...@att.net> 
Sent: Sunday, March 10, 2024 9:59 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

Yes that’s what was looking for and asfter when asking.

So how do they come and are they wired or wireless?

I have the Alexa devices from amazon plus my iPhone and google home too.

Are they expensive?

Thanks.

 

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Mario Eiland
Sent: Sunday, March 10, 2024 9:23 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

Hi Don,

 

When asking about accessible doorbells, what do you mean by accessible? How 
accessible would you like it to be?

I also use the Ring doorbell and I have it integrated with everybody’s  iPhone 
who lives in the house plus our Echo devices. Any time anyone nears our house 
porch we receive announcements that it detected motion. If someone rings the 
doorbell we have the option to either pick it up via the Ring app on our 
iPhones or the Alexa by simply asking Alexa to answer doorbell. For those who 
can see can activate the camera on their phones and see who is at the door. 
Unfortunately, it doesn’t identify the person for me yet. I’m hoping that’s 
near in the future with the advancement of AI. But for now I love it since we 
are notified any time we have a package dropped off and if anyone is home then 
we can immediately retrieve it.

I’m not sure how it integrates with the Google Home, but with the Echo devices 
you can download, what they call a Skill with the Alexa app and as long as you 
have a Ring account establish then you can sign into the Ring Skill and 
integrate it with your Echo. It’s pretty awesome!

Hope that helps some!

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Esther Levegnale
Sent: Sunday, March 10, 2024 6:05 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: Re: Accessible doorbell systems

 

I believe ring doorbell is a good one. Anyway, good luck. Esther.

Sent From Esther's Amazing and Awesome iPhone 13 Pro Max!

 

On Mar 10, 2024, at 6:25 AM, djrisav...@att.net <mailto:djrisav...@att.net>  
wrote:



Hello all,

I was wondering what anyone suggest or recommend as the most accessible and 
also affordable doorbell system is for a single widower person living in a 
small size condo that can be accessed with various devices like iPhones, google 
home or Alexa and how easy are they to set up?

Thanks.

Don

 

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu <mailto:mk...@ucla.edu> . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com <mail

Re: [PATCH] Add bounds-checks to substring

[Mario Domenech Goulart]

Hi,

On Mon, 11 Mar 2024 12:17:51 +0100 felix.winkelm...@bevuta.com wrote:

> Thanks! A signed off copy is attached (waiting for another chicken-hacker
> to approve).

Thanks siiki and Felix.  The patch has been applied.

All the best.
Mario
-- 
http://parenteses.org/mario

Re: VNC Viewer on Windows: Unable to access VMs GUI

[Mario Marietto]

You will not go to stable.

On Tue, Mar 12, 2024 at 2:44 PM Odhiambo Washington 
wrote:

> I run 14-RELEASE and would not like to go to -STABLE.
>
> On Tue, Mar 12, 2024 at 3:00 PM Mario Marietto 
> wrote:
>
>> Try the procedure explained below to have the latest bhyve version well
>> patched. Lets create these script files :
>>
>> 1) build_branch_releng-140 :
>>
>> set -e
>> set -u
>>
>> readonly script_path="$(cd "$(dirname "${0}")" && pwd)"
>> readonly branch="${1?Missing $(usage)}"
>> shift
>> echo $branch
>>
>> cd /usr/corvin-src-releng-140
>> git fetch --all --prune
>> git checkout -f "${branch}"
>>
>> ${script_path}/build_releng_140 "$@"
>>
>>
>> 2) build_releng_140 :
>>
>>
>> #!/bin/sh
>> usage() {
>> cat >&2 << EOF
>> Usage: ${0} [--no-bhf] [--reboot] [--verbose] [--without-kernel]
>> Builds bhyve
>> EOF
>> exit 1
>> }
>>
>> build_module() {
>> local _path
>> _path="${1}"
>>
>> # change to module path
>> cd "${_path}"
>>
>> # clean module
>> if test "${clean}" = "true"; then
>> make clean > "${cmd_redirect}" 2>&1
>> fi
>>
>> # build module
>> make > "${cmd_redirect}" 2>&1
>>
>> # install module
>> make install > "${cmd_redirect}"
>> }
>>
>> build() {
>> build_module "${src_dir}/include"
>> build_module "${src_dir}/lib/libvmmapi"
>> build_module "${src_dir}/sys/modules/vmm"
>>
>> # build kernel
>> if test "${with_kernel}" = "true"; then
>> cd "${src_dir}"
>> local kern_opts
>> kern_opts="-j$(sysctl -n hw.ncpu)"
>> if test "${with_bhf}" = "true"; then
>> kern_opts="${kern_opts} KERNCONF=BHF"
>> fi
>> if ! test "${clean}" = "true"; then
>> kern_opts="${kern_opts} NO_CLEAN=YES"
>> fi
>> make kernel ${kern_opts} > "${cmd_redirect}" 2>&1
>> fi
>>
>> build_module "${src_dir}/usr.sbin/bhyve"
>> build_module "${src_dir}/usr.sbin/bhyvectl"
>> build_module "${src_dir}/usr.sbin/bhyveload"
>>
>> if test "${with_reboot}" = "true"; then
>> reboot
>> fi
>> }
>>
>> set -e
>> set -u
>>
>> while test $# -gt 0; do
>> case "${1-}" in
>> --clean)
>> clean="true"
>> shift
>> ;;
>> --reboot)
>> with_reboot="true"
>> shift
>> ;;
>> --src-dir=*)
>> src_dir="${1#*=}"
>> shift
>> ;;
>> --verbose)
>> cmd_redirect="/dev/stdout"
>> shift
>> ;;
>> --without-bhf)
>>     with_bhf="false"
>> shift
>> ;;
>> --without-kernel)
>> with_kernel="false"
>> shift
>> ;;
>> *)
>> usage
>> ;;
>> esac
>> done
>>
>> readonly clean="${clean-"false"}"
>> readonly cmd_redirect="${cmd_redirect-"/dev/null"}"
>> readonly src_dir="${src_dir-"/usr/corvin-src-releng-140"}"
>> echo $src_dir
>> readonly with_bhf="${with_bhf-"true"}"
>> readonly with_kernel="${with_kernel-"true"}"
>> readonly with_reboot="${with_reboot-"false"}"
>> build
>>
>>
>> 3) com

[Desktop-packages] [Bug 2057684] [NEW] Backport a fix from Pulseaudio 17 to fix playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Public bug reported:

This is a request for a backport of an existing bug fix, present in the
recent Pulseaudio version 17 upstream release, to the outdated
Pulseaudio 16 releases in jammy - noble.

Affects: Ubuntu 22.04.0 LTS and all later versions.

The fix fixes an annoying start of playback timing bug that affects my
own software package octave-psychtoolbox-3 (part of Ubuntu universe),
see
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
which uses GStreamer for video and audio playback. Psychtoolbox is a
very popular toolkit for neuroscience and related medical research, with
Ubuntu as the recommended target distribution. It requires high
reliability in audio and video presentation timing, so the bug described
in the various links below is serious to our users.

The bug also in the same way affects other media applications in Ubuntu
which play back audio via the default (auto-plugged) pulseaudiosink
GStreamer plugin. See GStreamer bug report
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
GStreamer bug turned out to be a pulseaudio client library bug (in
libpulse.so.0).

Any native pulseaudio client is affected, even if pipewire is used as
desktop sound server in recent Ubuntu releases, given that many audio
applications still access pipewire via its pulseaudio frontend (package
pipewire-pulse). See pipewire bug
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

The bug in libpulse.so.0, reported against Pulseaudio 16 in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
been fixed for the Pulseaudio 17 release.

See the following merge request for the following trivial one-liner
patch that would need to be backported to Ubuntu's current
implementation:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

I hoped that Pulseaudio 17 would be included in Debian in time for
integration into Ubuntu 24.04-LTS, but apparently not much maintenance
of pulseaudio is happening on the Debian side at the moment.

Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS,
I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in
22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for
the upcoming 24.04-LTS.

Alternatively it would have been great to get Pulseaudio upgraded to
version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

Thanks,
-mario

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gstreamer pipewire pulseaudio sound timing

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

Title:
  Backport a fix from Pulseaudio 17 to fix playback timing problems
  affecting GStreamer and other pulseaudio and pipewire audio clients

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 upstream release, to the outdated
  Pulseaudio 16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I hoped

[Touch-packages] [Bug 2057684] [NEW] Backport a fix from Pulseaudio 17 to fix playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Public bug reported:

This is a request for a backport of an existing bug fix, present in the
recent Pulseaudio version 17 upstream release, to the outdated
Pulseaudio 16 releases in jammy - noble.

Affects: Ubuntu 22.04.0 LTS and all later versions.

The fix fixes an annoying start of playback timing bug that affects my
own software package octave-psychtoolbox-3 (part of Ubuntu universe),
see
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
which uses GStreamer for video and audio playback. Psychtoolbox is a
very popular toolkit for neuroscience and related medical research, with
Ubuntu as the recommended target distribution. It requires high
reliability in audio and video presentation timing, so the bug described
in the various links below is serious to our users.

The bug also in the same way affects other media applications in Ubuntu
which play back audio via the default (auto-plugged) pulseaudiosink
GStreamer plugin. See GStreamer bug report
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
GStreamer bug turned out to be a pulseaudio client library bug (in
libpulse.so.0).

Any native pulseaudio client is affected, even if pipewire is used as
desktop sound server in recent Ubuntu releases, given that many audio
applications still access pipewire via its pulseaudio frontend (package
pipewire-pulse). See pipewire bug
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

The bug in libpulse.so.0, reported against Pulseaudio 16 in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
been fixed for the Pulseaudio 17 release.

See the following merge request for the following trivial one-liner
patch that would need to be backported to Ubuntu's current
implementation:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

I hoped that Pulseaudio 17 would be included in Debian in time for
integration into Ubuntu 24.04-LTS, but apparently not much maintenance
of pulseaudio is happening on the Debian side at the moment.

Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS,
I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in
22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for
the upcoming 24.04-LTS.

Alternatively it would have been great to get Pulseaudio upgraded to
version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

Thanks,
-mario

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gstreamer pipewire pulseaudio sound timing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2057684

Title:
  Backport a fix from Pulseaudio 17 to fix playback timing problems
  affecting GStreamer and other pulseaudio and pipewire audio clients

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 upstream release, to the outdated
  Pulseaudio 16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I

[Bug 2057684] [NEW] Backport a fix from Pulseaudio 17 to fix playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Public bug reported:

This is a request for a backport of an existing bug fix, present in the
recent Pulseaudio version 17 upstream release, to the outdated
Pulseaudio 16 releases in jammy - noble.

Affects: Ubuntu 22.04.0 LTS and all later versions.

The fix fixes an annoying start of playback timing bug that affects my
own software package octave-psychtoolbox-3 (part of Ubuntu universe),
see
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
which uses GStreamer for video and audio playback. Psychtoolbox is a
very popular toolkit for neuroscience and related medical research, with
Ubuntu as the recommended target distribution. It requires high
reliability in audio and video presentation timing, so the bug described
in the various links below is serious to our users.

The bug also in the same way affects other media applications in Ubuntu
which play back audio via the default (auto-plugged) pulseaudiosink
GStreamer plugin. See GStreamer bug report
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
GStreamer bug turned out to be a pulseaudio client library bug (in
libpulse.so.0).

Any native pulseaudio client is affected, even if pipewire is used as
desktop sound server in recent Ubuntu releases, given that many audio
applications still access pipewire via its pulseaudio frontend (package
pipewire-pulse). See pipewire bug
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

The bug in libpulse.so.0, reported against Pulseaudio 16 in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
been fixed for the Pulseaudio 17 release.

See the following merge request for the following trivial one-liner
patch that would need to be backported to Ubuntu's current
implementation:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

I hoped that Pulseaudio 17 would be included in Debian in time for
integration into Ubuntu 24.04-LTS, but apparently not much maintenance
of pulseaudio is happening on the Debian side at the moment.

Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS,
I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in
22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for
the upcoming 24.04-LTS.

Alternatively it would have been great to get Pulseaudio upgraded to
version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

Thanks,
-mario

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gstreamer pipewire pulseaudio sound timing

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

Title:
  Backport a fix from Pulseaudio 17 to fix playback timing problems
  affecting GStreamer and other pulseaudio and pipewire audio clients

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


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

Re: [Metamath] Results about ax-13 usage

[Mario Carneiro]

On Mon, Mar 11, 2024 at 11:36 AM Jim Kingdon  wrote:

> If this is just a hypothetical question I guess we don't really need to
> come up with a definitive answer, but I will say that if we want to keep
> some of our other values (like preferring short proofs), we'd end up
> with a lot of ALT theorems or other ways in which there is a classical
> proof, there is an intuitionistic proof, and the intuitionistic proof is
> much longer.


We already have a caveat in the proof shortening rules for this. We want
shorter proofs but *only* assuming it doesn't take the theorem out of a
"subsystem of interest". For the most part that means that proof searches
using MINIMIZE will add /NO_NEW_AXIOMS to ensure that intuitionistic proofs
stay intuitionistic. So in the variation you are talking about I would
expect there to only be an intuitionistic proof, and the classical proof
(if the statement is different) would be the shorter of "do the proof
directly" and "apply the intuitionistic version and remove the unnecessary
assumptions", which probably would end up with the latter most of the time.


> Proof length aside, I guess I'm just not sure that set.mm would read
> very nicely if it needed to concern itself with decidability, apartness,
> additional conditions on things like supremums and convergence, etc. Not
> to mention topology which beyond a certain point falls apart unless you
> switch from point-set topology to locales (or so I read, iset.mm hasn't
> really gotten that far yet).
>

This is a fair criticism. For those areas like topology where it's still
unclear how to intuitionize it, the whole thing would simply be classical.
But I would expect a cover-to-cover reader of set.mm to already know that
it is trying to simultaneously cover intuitionistic and classical logic,
and the abstractions that work in intuitionistic logic are also interesting
in their own way. I know I had to search far and wide for proofs about
measure theory in the absence of the axiom of choice (thanks Fremlin!) so
it wouldn't be the first time for proofs that go out of their way to avoid
some axiom.


> I'll also say that I do agree about the observations about how iset.mm
> and set.mm are similar enough that it is also awkward, in different
> ways, to keep them separate. There are a lot of theorems which can
> simply be copy-pasted in one direction or the other.
>

And of course these copy-pasted theorems are a future maintenance issue,
since people will have to remember to change them in tandem (or not! if the
change needs classical logic) and this is hard to deal with without a
global view of all the databases.

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

[Bug 2057424] Re: No variable refresh rate (VRR) on the Framework 16

[Mario Limonciello]

V2 addressed comments and was reviewed.

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

Title:
  No variable refresh rate (VRR) on the Framework 16

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions


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

[Kernel-packages] [Bug 2057424] Re: No variable refresh rate (VRR) on the Framework 16

[Mario Limonciello]

V2 addressed comments and was reviewed.

-- 
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/2057424

Title:
  No variable refresh rate (VRR) on the Framework 16

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Noble:
  Incomplete

Bug description:
  Quoted from AMD proposed fix in https://lore.kernel.org/amd-
  
gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f

  > The monitor shipped with the Framework 16 supports VRR [1], but it's not
  > being advertised.
  >
  > This is because the detailed timing block doesn't contain
  > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max
  > frequencies.  This check however is superfluous for this case because
  > update_display_info() calls drm_get_monitor_range() to get these ranges
  > already.
  >
  > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then
  > turn on freesync without extra checks.

  See: 
https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/
  See: 
https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/
  See: 
https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338
  Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2057424/+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

Re: VNC Viewer on Windows: Unable to access VMs GUI

[Mario Marietto]

Try the procedure explained below to have the latest bhyve version well
patched. Lets create these script files :

1) build_branch_releng-140 :

set -e
set -u

readonly script_path="$(cd "$(dirname "${0}")" && pwd)"
readonly branch="${1?Missing $(usage)}"
shift
echo $branch

cd /usr/corvin-src-releng-140
git fetch --all --prune
git checkout -f "${branch}"

${script_path}/build_releng_140 "$@"


2) build_releng_140 :


#!/bin/sh
usage() {
cat >&2 << EOF
Usage: ${0} [--no-bhf] [--reboot] [--verbose] [--without-kernel]
Builds bhyve
EOF
exit 1
}

build_module() {
local _path
_path="${1}"

# change to module path
cd "${_path}"

# clean module
if test "${clean}" = "true"; then
make clean > "${cmd_redirect}" 2>&1
fi

# build module
make > "${cmd_redirect}" 2>&1

# install module
make install > "${cmd_redirect}"
}

build() {
build_module "${src_dir}/include"
build_module "${src_dir}/lib/libvmmapi"
build_module "${src_dir}/sys/modules/vmm"

# build kernel
if test "${with_kernel}" = "true"; then
cd "${src_dir}"
local kern_opts
kern_opts="-j$(sysctl -n hw.ncpu)"
if test "${with_bhf}" = "true"; then
kern_opts="${kern_opts} KERNCONF=BHF"
fi
if ! test "${clean}" = "true"; then
kern_opts="${kern_opts} NO_CLEAN=YES"
fi
make kernel ${kern_opts} > "${cmd_redirect}" 2>&1
fi

build_module "${src_dir}/usr.sbin/bhyve"
build_module "${src_dir}/usr.sbin/bhyvectl"
build_module "${src_dir}/usr.sbin/bhyveload"

if test "${with_reboot}" = "true"; then
reboot
fi
}

set -e
set -u

while test $# -gt 0; do
case "${1-}" in
--clean)
clean="true"
shift
;;
--reboot)
with_reboot="true"
shift
;;
--src-dir=*)
src_dir="${1#*=}"
shift
;;
--verbose)
cmd_redirect="/dev/stdout"
shift
;;
--without-bhf)
with_bhf="false"
shift
;;
--without-kernel)
with_kernel="false"
shift
;;
*)
usage
;;
esac
done

readonly clean="${clean-"false"}"
readonly cmd_redirect="${cmd_redirect-"/dev/null"}"
readonly src_dir="${src_dir-"/usr/corvin-src-releng-140"}"
echo $src_dir
readonly with_bhf="${with_bhf-"true"}"
readonly with_kernel="${with_kernel-"true"}"
readonly with_reboot="${with_reboot-"false"}"
build


3) compile-bhyve-releng-140 :


cd /usr/
mv src src-old
git clone https://github.com/beckhoff/freebsd-src /usr/corvin-src-releng-140
cd /usr/corvin-src-releng-140
/build_branch_releng-140 origin/phab/corvink/14.0/nvidia-wip --without-bhf
--verbose


and run : ./compile-bhyve-releng-140 (on FreeBSD 14.0)

On Tue, Mar 12, 2024 at 12:53 PM Mario Marietto 
wrote:

> Maybe because some patches haven't been upstreamed to 14.0 branch.
>
> On Tue, Mar 12, 2024 at 12:49 PM Odhiambo Washington 
> wrote:
>
>> Actually, I am trying to figure out why they do not work after upgrade
>> from FreeBSD 13 to 14. They used to work before.
>> History:
>> 1. My FreeBSD host lives in a Data Centre several kilometers from me. I
>> only access it via SSH.
>> 2. My FreeBSD host does not have a keyboard, mouse, or screen attached to
>> it.
>> 3. I use VNC Viewer to connect to the VMs like HOST_IP:PORT
>>
>>
>> On Tue, Mar 12, 2024 at 2:36 PM Mario Marietto 
>> wrote:
>>
>>> Hello my friend Odhiambo,
>>>
>>> you can try to pass your keyboard and mouse to a specific USB to pci
>>> adapter,using an USB splitter to attach both the input devices. Actually
>>> I'm using the one integrated on my nvidia gpu,

RE: Accessible doorbell systems

[Mario Eiland]

The Ring doorbell replaces the old one. So it’s powered like the original.

 

From: viphone@googlegroups.com  On Behalf Of Peter 
Tesar
Sent: Tuesday, March 12, 2024 4:20 AM
To: viphone@googlegroups.com
Subject: Re: Accessible doorbell systems

 

How is the outside door bell unit powered?

I assume it is attached to the wall. 

does a hole need to be drilled through the wall to connect to the household 
wiring?

 

Thanks, 

Peter T. 

 

On 2024-03-11 7:51 AM, Mario Eiland wrote:

The doorbell has to be installed outside like your standard doorbell. I had 
someone sighted do that for me. Actually, I had a professional do it for me. I 
think that’s all you would need, accept I went further by purchasing a wireless 
chime that was place upstairs so if the doorbell was rang then it could be 
heard in every echo in the house plus your smart phone.

It’s been several years ago since I bought the equipment.

Ring Chime Pro - $44.99

Ring Video Doorbell 2 - $134.99

Installation was $58.49.

Just remember this was 3 years ago.

 

Hope that helps.

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>   
<mailto:viphone@googlegroups.com>  On Behalf Of 
djrisav...@att.net <mailto:djrisav...@att.net> 
Sent: Sunday, March 10, 2024 9:59 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

Yes that’s what was looking for and asfter when asking.

So how do they come and are they wired or wireless?

I have the Alexa devices from amazon plus my iPhone and google home too.

Are they expensive?

Thanks.

 

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Mario Eiland
Sent: Sunday, March 10, 2024 9:23 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

Hi Don,

 

When asking about accessible doorbells, what do you mean by accessible? How 
accessible would you like it to be?

I also use the Ring doorbell and I have it integrated with everybody’s  iPhone 
who lives in the house plus our Echo devices. Any time anyone nears our house 
porch we receive announcements that it detected motion. If someone rings the 
doorbell we have the option to either pick it up via the Ring app on our 
iPhones or the Alexa by simply asking Alexa to answer doorbell. For those who 
can see can activate the camera on their phones and see who is at the door. 
Unfortunately, it doesn’t identify the person for me yet. I’m hoping that’s 
near in the future with the advancement of AI. But for now I love it since we 
are notified any time we have a package dropped off and if anyone is home then 
we can immediately retrieve it.

I’m not sure how it integrates with the Google Home, but with the Echo devices 
you can download, what they call a Skill with the Alexa app and as long as you 
have a Ring account establish then you can sign into the Ring Skill and 
integrate it with your Echo. It’s pretty awesome!

Hope that helps some!

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Esther Levegnale
Sent: Sunday, March 10, 2024 6:05 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: Re: Accessible doorbell systems

 

I believe ring doorbell is a good one. Anyway, good luck. Esther.

Sent From Esther's Amazing and Awesome iPhone 13 Pro Max!

 

On Mar 10, 2024, at 6:25 AM, djrisav...@att.net <mailto:djrisav...@att.net>  
wrote:



Hello all,

I was wondering what anyone suggest or recommend as the most accessible and 
also affordable doorbell system is for a single widower person living in a 
small size condo that can be accessed with various devices like iPhones, google 
home or Alexa and how easy are they to set up?

Thanks.

Don

 

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu <mailto:mk...@ucla.edu> . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com <mailto:caraqu...@caraquinn.com> 
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
<mailto:viphone+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/021f01da72d5%24499f0610%24dcdd1230%24%40att.net
 
<https://groups.g

Re: VNC Viewer on Windows: Unable to access VMs GUI

[Mario Marietto]

Maybe because some patches haven't been upstreamed to 14.0 branch.

On Tue, Mar 12, 2024 at 12:49 PM Odhiambo Washington 
wrote:

> Actually, I am trying to figure out why they do not work after upgrade
> from FreeBSD 13 to 14. They used to work before.
> History:
> 1. My FreeBSD host lives in a Data Centre several kilometers from me. I
> only access it via SSH.
> 2. My FreeBSD host does not have a keyboard, mouse, or screen attached to
> it.
> 3. I use VNC Viewer to connect to the VMs like HOST_IP:PORT
>
>
> On Tue, Mar 12, 2024 at 2:36 PM Mario Marietto 
> wrote:
>
>> Hello my friend Odhiambo,
>>
>> you can try to pass your keyboard and mouse to a specific USB to pci
>> adapter,using an USB splitter to attach both the input devices. Actually
>> I'm using the one integrated on my nvidia gpu,RTX 2080 ti,that's :
>>
>> 02:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX
>> 2080 Ti]
>> 02:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio
>> Controller
>> *02:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Host Controller*
>> 02:00.3 Serial bus controller: NVIDIA Corporation TU102 USB Type-C UCSI
>> Controller
>>
>> For sure you will add the PCI address of the board between your bhyve
>> parameters,for example in my case :
>>
>> -s 8:2,passthru,2/0/2 \
>>
>> A single hardware solution would be a pcie riser which splits the pcie
>> port.
>>
>>
>> I've asked for a good USB controller some time ago :
>>
>>
>>
>> https://forums.freebsd.org/threads/im-looking-for-a-good-usb-controller-3-0-4-ports-self-powered-compatible-with-freebsd.83323/
>>
>>
>> If it’s only mouse and keyboard you could use bhyves virtio-input
>> emulation.
>>
>>
>> Corvin included virtio-input support in his github.
>>
>>
>> He committed virtio-input to 13.2 and 14.0 upstream.
>>
>>
>> From “man bhyve”
>>
>>
>>
>> https://www.freebsd.org/cgi/man.cgi?query=bhyve=0=8=FreeBSD+14.0-CURRENT=default=html
>> ):
>>
>>
>> Virtio  input device backends:
>>
>>
>>
>> */dev/input/eventX*
>>
>>Send inputevents of */dev/input/eventX* to
>> guest
>>
>>by  VirtIO Input Interface.
>>
>> On Tue, Mar 12, 2024 at 11:39 AM Odhiambo Washington 
>> wrote:
>>
>>>
>>> Even with this, my mouse pointer doesn't work:
>>>
>>> # Linux Guest
>>> bhyve -S -c sockets=2,cores=2,threads=2 -m 4G -w -H -A \
>>> -s 0,hostbridge \
>>> -s 3,ahci-cd,/usr/local/bhyve-vms/.iso/debian-12.5.0-amd64-DVD-1.iso \
>>> -s 4,virtio-blk,/usr/local/bhyve-vms/Debian/debian.img \
>>> -s 5,virtio-net,tap4 \
>>> -s 8,hda,play=/dev/dsp,rec=/dev/dsp \
>>> -s 29,fbuf,tcp=0.0.0.0:5905,w=1024,h=768 \
>>> -s 30,xhci,tablet \
>>> -s 31,lpc -l com1,stdio \
>>> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
>>> debian
>>>
>>>
>>>
>>> On Wed, Feb 14, 2024 at 3:47 PM Mario Marietto >> > wrote:
>>>
>>>> -s 3,fbuf,tcp=0.0.0.0:59 <http://0.0.0.0:5915>*15*,w=1600,h=950 \
>>>> -s 10,virtio-net,tap*15* \
>>>> *vm15* < /dev/null & sleep 2 && vncviewer *0:15*
>>>>
>>>> On Wed, Feb 14, 2024 at 1:19 PM Odhiambo Washington 
>>>> wrote:
>>>>
>>>>> Hellos,
>>>>>
>>>>> When I was still on FreeBSD 13.2-RELEASE I was able to access some
>>>>> Linux VMs GUI using VNC Viewer on my Windows PC.
>>>>> After I upgraded to 14-RELEASE, this changed: I can connect to the
>>>>> VMs, but the GUI desktop is frozen. The mouse cursor isn't moving at all
>>>>> and the Desktop doesn't load like before.
>>>>> I start all my VMs the same way:
>>>>>
>>>>> bhyve -c N -m NG -w -H \
>>>>> -s 0,hostbridge \
>>>>> -s 4,virtio-blk,/usr/local/bhyve-vms/DISTRONAME/distroname.img \
>>>>> -s 5,virtio-net,tapN \
>>>>> -s 8,hda,play=/dev/dsp,rec=/dev/dsp \
>>>>> -s 29,fbuf,tcp=0.0.0.0:59XX,w=1680,h=1050 \
>>>>> -s 30,xhci,tablet \
>>>>> -s 31,lpc -l com1,stdio \
>>>>> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
>>>>> distroname
>>>>>
>>>>> I would then connect to a.b.c.d:59xx using VNC Viewer and I'd 

Re: VNC Viewer on Windows: Unable to access VMs GUI

[Mario Marietto]

Hello my friend Odhiambo,

you can try to pass your keyboard and mouse to a specific USB to pci
adapter,using an USB splitter to attach both the input devices. Actually
I'm using the one integrated on my nvidia gpu,RTX 2080 ti,that's :

02:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX
2080 Ti]
02:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio
Controller
*02:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Host Controller*
02:00.3 Serial bus controller: NVIDIA Corporation TU102 USB Type-C UCSI
Controller

For sure you will add the PCI address of the board between your bhyve
parameters,for example in my case :

-s 8:2,passthru,2/0/2 \

A single hardware solution would be a pcie riser which splits the pcie port.


I've asked for a good USB controller some time ago :


https://forums.freebsd.org/threads/im-looking-for-a-good-usb-controller-3-0-4-ports-self-powered-compatible-with-freebsd.83323/


If it’s only mouse and keyboard you could use bhyves virtio-input emulation.


Corvin included virtio-input support in his github.


He committed virtio-input to 13.2 and 14.0 upstream.


>From “man bhyve”


https://www.freebsd.org/cgi/man.cgi?query=bhyve=0=8=FreeBSD+14.0-CURRENT=default=html
):


Virtio  input device backends:



*/dev/input/eventX*

   Send inputevents of */dev/input/eventX* to guest

   by  VirtIO Input Interface.

On Tue, Mar 12, 2024 at 11:39 AM Odhiambo Washington 
wrote:

>
> Even with this, my mouse pointer doesn't work:
>
> # Linux Guest
> bhyve -S -c sockets=2,cores=2,threads=2 -m 4G -w -H -A \
> -s 0,hostbridge \
> -s 3,ahci-cd,/usr/local/bhyve-vms/.iso/debian-12.5.0-amd64-DVD-1.iso \
> -s 4,virtio-blk,/usr/local/bhyve-vms/Debian/debian.img \
> -s 5,virtio-net,tap4 \
> -s 8,hda,play=/dev/dsp,rec=/dev/dsp \
> -s 29,fbuf,tcp=0.0.0.0:5905,w=1024,h=768 \
> -s 30,xhci,tablet \
> -s 31,lpc -l com1,stdio \
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
> debian
>
>
>
> On Wed, Feb 14, 2024 at 3:47 PM Mario Marietto  > wrote:
>
>> -s 3,fbuf,tcp=0.0.0.0:59 <http://0.0.0.0:5915>*15*,w=1600,h=950 \
>> -s 10,virtio-net,tap*15* \
>> *vm15* < /dev/null & sleep 2 && vncviewer *0:15*
>>
>> On Wed, Feb 14, 2024 at 1:19 PM Odhiambo Washington 
>> wrote:
>>
>>> Hellos,
>>>
>>> When I was still on FreeBSD 13.2-RELEASE I was able to access some Linux
>>> VMs GUI using VNC Viewer on my Windows PC.
>>> After I upgraded to 14-RELEASE, this changed: I can connect to the VMs,
>>> but the GUI desktop is frozen. The mouse cursor isn't moving at all and the
>>> Desktop doesn't load like before.
>>> I start all my VMs the same way:
>>>
>>> bhyve -c N -m NG -w -H \
>>> -s 0,hostbridge \
>>> -s 4,virtio-blk,/usr/local/bhyve-vms/DISTRONAME/distroname.img \
>>> -s 5,virtio-net,tapN \
>>> -s 8,hda,play=/dev/dsp,rec=/dev/dsp \
>>> -s 29,fbuf,tcp=0.0.0.0:59XX,w=1680,h=1050 \
>>> -s 30,xhci,tablet \
>>> -s 31,lpc -l com1,stdio \
>>> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
>>> distroname
>>>
>>> I would then connect to a.b.c.d:59xx using VNC Viewer and I'd get the
>>> Linux/Windows Desktop.
>>> Not anymore!
>>>
>>> Is there something I need to do to fix the issue?
>>>
>>>
>>> --
>>> Best regards,
>>> Odhiambo WASHINGTON,
>>> Nairobi,KE
>>> +254 7 3200 0004/+254 7 2274 3223
>>>  In an Internet failure case, the #1 suspect is a constant: DNS.
>>> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
>>> [How to ask smart questions:
>>> http://www.catb.org/~esr/faqs/smart-questions.html]
>>>
>>
>>
>> --
>> Mario.
>>
>
>
> --
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
>  In an Internet failure case, the #1 suspect is a constant: DNS.
> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
> [How to ask smart questions:
> http://www.catb.org/~esr/faqs/smart-questions.html]
>


-- 
Mario.

Re: [PATCH v2 00/14] libvhost-user: support more memslots and cleanup memslot handling code

[Mario Casquero]

This series has been successfully tested by QE. Start the
qemu-storage-daemon in the background with a rhel 9.5 image and
vhost-user-blk. After that, boot up a VM with virtio-mem and
vhost-user-blk-pci. Check with the HMP command 'info mtree' that
virtio-mem is making use of multiple memslots.

Tested-by: Mario Casquero 

On Mon, Mar 11, 2024 at 9:00 PM Mario Casquero  wrote:
>
> This series has been successfully tested by QE. Start the
> qemu-storage-daemon in the background with a rhel 9.5 image and
> vhost-user-blk. After that, boot up a VM with virtio-mem and
> vhost-user-blk-pci. Check with the HMP command 'info mtree' that
> virtio-mem is making use of multiple memslots.
>
>
> On Wed, Feb 14, 2024 at 4:18 PM David Hildenbrand  wrote:
> >
> > This series adds support for more memslots (509) to libvhost-user, to
> > make it fully compatible with virtio-mem that uses up to 256 memslots
> > accross all memory devices in "dynamic-memslot" mode (more details
> > in patch #2).
> >
> > With that in place, this series optimizes and extends memory region
> > handling in libvhost-user:
> > * Heavily deduplicate and clean up the memory region handling code
> > * Speeds up GPA->VA translation with many memslots using binary search
> > * Optimize mmap_offset handling to use it as fd_offset for mmap()
> > * Avoid ring remapping when adding a single memory region
> > * Avoid dumping all guest memory, possibly allocating memory in sparse
> >   memory mappings when the process crashes
> >
> > I'm being very careful to not break some weird corner case that modern
> > QEMU might no longer trigger, but older one could have triggered or some
> > other frontend might trigger.
> >
> > The only thing where I am not careful is to forbid memory regions that
> > overlap in GPA space: it doesn't make any sense.
> >
> > With this series, virtio-mem (with dynamic-memslots=on) +
> > qemu-storage-daemon works flawlessly and as expected in my tests.
> >
> > v1 -> v2:
> > * Drop "libvhost-user: Fix msg_region->userspace_addr computation"
> >  -> Not actually required
> > * "libvhost-user: Factor out adding a memory region"
> >  -> Make debug output more consistent (add missing ":")
> > * "libvhost-user: Use most of mmap_offset as fd_offset"
> >  -> get_fd_pagesize -> get_fd_hugepagesize; remove getpagesize()
> >  -> "mmap_offset:" to "old mmap_offset:" in debug message
> >  -> "adj mmap_offset:" to "new mmap_offset:" in debug message
> >  -> Use "(unsigned int)fs.f_type"; the man page of fstatfs() calls out
> > that the type of f_type can vary depending on the architecture.
> > "unsigned int" is sufficient here.
> >  -> Updated patch description
> > * Added RBs+ACKs
> > * Did a Gitlab CI run, seems to be happy reagrding libvhost-user
> >
> > Cc: Michael S. Tsirkin 
> > Cc: Jason Wang 
> > Cc: Stefan Hajnoczi 
> > Cc: Stefano Garzarella 
> > Cc: Germano Veit Michel 
> > Cc: Raphael Norwitz 
> >
> > David Hildenbrand (14):
> >   libvhost-user: Dynamically allocate memory for memory slots
> >   libvhost-user: Bump up VHOST_USER_MAX_RAM_SLOTS to 509
> >   libvhost-user: Factor out removing all mem regions
> >   libvhost-user: Merge vu_set_mem_table_exec_postcopy() into
> > vu_set_mem_table_exec()
> >   libvhost-user: Factor out adding a memory region
> >   libvhost-user: No need to check for NULL when unmapping
> >   libvhost-user: Don't zero out memory for memory regions
> >   libvhost-user: Don't search for duplicates when removing memory
> > regions
> >   libvhost-user: Factor out search for memory region by GPA and simplify
> >   libvhost-user: Speedup gpa_to_mem_region() and vu_gpa_to_va()
> >   libvhost-user: Use most of mmap_offset as fd_offset
> >   libvhost-user: Factor out vq usability check
> >   libvhost-user: Dynamically remap rings after (temporarily?) removing
> > memory regions
> >   libvhost-user: Mark mmap'ed region memory as MADV_DONTDUMP
> >
> >  subprojects/libvhost-user/libvhost-user.c | 595 --
> >  subprojects/libvhost-user/libvhost-user.h |  10 +-
> >  2 files changed, 334 insertions(+), 271 deletions(-)
> >
> > --
> > 2.43.0
> >
> >

Re: [PATCH v2 00/14] libvhost-user: support more memslots and cleanup memslot handling code

[Mario Casquero]

This series has been successfully tested by QE. Start the
qemu-storage-daemon in the background with a rhel 9.5 image and
vhost-user-blk. After that, boot up a VM with virtio-mem and
vhost-user-blk-pci. Check with the HMP command 'info mtree' that
virtio-mem is making use of multiple memslots.


On Wed, Feb 14, 2024 at 4:18 PM David Hildenbrand  wrote:
>
> This series adds support for more memslots (509) to libvhost-user, to
> make it fully compatible with virtio-mem that uses up to 256 memslots
> accross all memory devices in "dynamic-memslot" mode (more details
> in patch #2).
>
> With that in place, this series optimizes and extends memory region
> handling in libvhost-user:
> * Heavily deduplicate and clean up the memory region handling code
> * Speeds up GPA->VA translation with many memslots using binary search
> * Optimize mmap_offset handling to use it as fd_offset for mmap()
> * Avoid ring remapping when adding a single memory region
> * Avoid dumping all guest memory, possibly allocating memory in sparse
>   memory mappings when the process crashes
>
> I'm being very careful to not break some weird corner case that modern
> QEMU might no longer trigger, but older one could have triggered or some
> other frontend might trigger.
>
> The only thing where I am not careful is to forbid memory regions that
> overlap in GPA space: it doesn't make any sense.
>
> With this series, virtio-mem (with dynamic-memslots=on) +
> qemu-storage-daemon works flawlessly and as expected in my tests.
>
> v1 -> v2:
> * Drop "libvhost-user: Fix msg_region->userspace_addr computation"
>  -> Not actually required
> * "libvhost-user: Factor out adding a memory region"
>  -> Make debug output more consistent (add missing ":")
> * "libvhost-user: Use most of mmap_offset as fd_offset"
>  -> get_fd_pagesize -> get_fd_hugepagesize; remove getpagesize()
>  -> "mmap_offset:" to "old mmap_offset:" in debug message
>  -> "adj mmap_offset:" to "new mmap_offset:" in debug message
>  -> Use "(unsigned int)fs.f_type"; the man page of fstatfs() calls out
> that the type of f_type can vary depending on the architecture.
> "unsigned int" is sufficient here.
>  -> Updated patch description
> * Added RBs+ACKs
> * Did a Gitlab CI run, seems to be happy reagrding libvhost-user
>
> Cc: Michael S. Tsirkin 
> Cc: Jason Wang 
> Cc: Stefan Hajnoczi 
> Cc: Stefano Garzarella 
> Cc: Germano Veit Michel 
> Cc: Raphael Norwitz 
>
> David Hildenbrand (14):
>   libvhost-user: Dynamically allocate memory for memory slots
>   libvhost-user: Bump up VHOST_USER_MAX_RAM_SLOTS to 509
>   libvhost-user: Factor out removing all mem regions
>   libvhost-user: Merge vu_set_mem_table_exec_postcopy() into
> vu_set_mem_table_exec()
>   libvhost-user: Factor out adding a memory region
>   libvhost-user: No need to check for NULL when unmapping
>   libvhost-user: Don't zero out memory for memory regions
>   libvhost-user: Don't search for duplicates when removing memory
> regions
>   libvhost-user: Factor out search for memory region by GPA and simplify
>   libvhost-user: Speedup gpa_to_mem_region() and vu_gpa_to_va()
>   libvhost-user: Use most of mmap_offset as fd_offset
>   libvhost-user: Factor out vq usability check
>   libvhost-user: Dynamically remap rings after (temporarily?) removing
> memory regions
>   libvhost-user: Mark mmap'ed region memory as MADV_DONTDUMP
>
>  subprojects/libvhost-user/libvhost-user.c | 595 --
>  subprojects/libvhost-user/libvhost-user.h |  10 +-
>  2 files changed, 334 insertions(+), 271 deletions(-)
>
> --
> 2.43.0
>
>

RE: Accessible doorbell systems

[Mario Eiland]

The doorbell has to be installed outside like your standard doorbell. I had 
someone sighted do that for me. Actually, I had a professional do it for me. I 
think that’s all you would need, accept I went further by purchasing a wireless 
chime that was place upstairs so if the doorbell was rang then it could be 
heard in every echo in the house plus your smart phone.

It’s been several years ago since I bought the equipment.

Ring Chime Pro - $44.99

Ring Video Doorbell 2 - $134.99

Installation was $58.49.

Just remember this was 3 years ago.

 

Hope that helps.

 

From: viphone@googlegroups.com  On Behalf Of 
djrisav...@att.net
Sent: Sunday, March 10, 2024 9:59 AM
To: viphone@googlegroups.com
Subject: RE: Accessible doorbell systems

 

Yes that’s what was looking for and asfter when asking.

So how do they come and are they wired or wireless?

I have the Alexa devices from amazon plus my iPhone and google home too.

Are they expensive?

Thanks.

 

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Mario Eiland
Sent: Sunday, March 10, 2024 9:23 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Accessible doorbell systems

 

Hi Don,

 

When asking about accessible doorbells, what do you mean by accessible? How 
accessible would you like it to be?

I also use the Ring doorbell and I have it integrated with everybody’s  iPhone 
who lives in the house plus our Echo devices. Any time anyone nears our house 
porch we receive announcements that it detected motion. If someone rings the 
doorbell we have the option to either pick it up via the Ring app on our 
iPhones or the Alexa by simply asking Alexa to answer doorbell. For those who 
can see can activate the camera on their phones and see who is at the door. 
Unfortunately, it doesn’t identify the person for me yet. I’m hoping that’s 
near in the future with the advancement of AI. But for now I love it since we 
are notified any time we have a package dropped off and if anyone is home then 
we can immediately retrieve it.

I’m not sure how it integrates with the Google Home, but with the Echo devices 
you can download, what they call a Skill with the Alexa app and as long as you 
have a Ring account establish then you can sign into the Ring Skill and 
integrate it with your Echo. It’s pretty awesome!

Hope that helps some!

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Esther Levegnale
Sent: Sunday, March 10, 2024 6:05 AM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: Re: Accessible doorbell systems

 

I believe ring doorbell is a good one. Anyway, good luck. Esther.

Sent From Esther's Amazing and Awesome iPhone 13 Pro Max!

 

On Mar 10, 2024, at 6:25 AM, djrisav...@att.net <mailto:djrisav...@att.net>  
wrote:



Hello all,

I was wondering what anyone suggest or recommend as the most accessible and 
also affordable doorbell system is for a single widower person living in a 
small size condo that can be accessed with various devices like iPhones, google 
home or Alexa and how easy are they to set up?

Thanks.

Don

 

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu <mailto:mk...@ucla.edu> . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com <mailto:caraqu...@caraquinn.com> 
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
<mailto:viphone+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/021f01da72d5%24499f0610%24dcdd1230%24%40att.net
 
<https://groups.google.com/d/msgid/viphone/021f01da72d5%24499f0610%24dcdd1230%24%40att.net?utm_medium=email_source=footer>
 .

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu <mailto:mk...@ucla.edu> . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com <mailto:caraqu...@caraquinn.com&g

Re: [Metamath] Results about ax-13 usage

[Mario Carneiro]

Well it's redoing a lot of the work that exists in set.mm, and you can't
really share results across them. For most logical subsystems, we address
it directly in set.mm by using more itemized axioms and leveraging the
"this theorem was proved from axioms:" list for tracking so that all the
subsystems can transparently coexist. When the axiomatic system is
significantly different and/or inconsistent with set.mm, it has to be
developed in a separate database (like hol.mm or nf.mm), but iset.mm does
not look like that to me, it uses variables and binding and all of the
other structural things in exactly the same way, it just omits some logical
axiom and replaces it with weaker things. Given a free choice I think that
developing in the same database is better since then intuitionistic proofs
can be used in classical theorems (and vice versa, when the classical
theorem was not actually using classical logic on accident or because of a
refactor).

On Sun, Mar 10, 2024 at 9:16 AM Gino Giotto 
wrote:

> > And of course the largest such refactor in this vein is iset.mm,
> although this one was considered sufficiently different as to be moved to a
> separate database (which I think is slightly unfortunate).
>
> Why is it slightly unfortunate? (just curious, I don't know much about
> iset.mm).
>
> Il giorno mercoledì 10 gennaio 2024 alle 09:16:41 UTC+1 kin...@panix.com
> ha scritto:
>
>> In a sense iset.mm is that sort of thing, although to state what is
>> probably obvious but maybe needs to be said anyway, iset.mm does not
>> only remove axioms relative to set.mm, it also adds axioms and modifies
>> axioms.
>> On 1/9/24 19:19, Mario Carneiro wrote:
>>
>> And of course the largest such refactor in this vein is iset.mm,
>> although this one was considered sufficiently different as to be moved to a
>> separate database (which I think is slightly unfortunate).
>>
>> On Tue, Jan 9, 2024 at 10:17 PM Mario Carneiro  wrote:
>>
>>> IMO this is definitely worthwhile, especially since it moves an axiom
>>> from used almost everywhere to used almost nowhere. We have previously done
>>> refactors of that kind for ax-groth, ax-ac2, ax-reg, ax-rep and I think we
>>> have a better understanding of the true dependencies of many theorems as a
>>> result.
>>>
>>> On Tue, Jan 9, 2024 at 9:30 PM Gino Giotto 
>>> wrote:
>>>
>>>> I believe the question now is whether there is a general consensus for
>>>> eventually bringing set.mm towards this direction. Is low usage of
>>>> ax-13 at the cost of more than 100 additional lemmas what we wish for? Or
>>>> maybe you would like to follow different paths and pursue different
>>>> achievements? Looking forward to hear your thoughts.
>>>>
>>>> Il giorno mercoledì 3 gennaio 2024 alle 02:02:21 UTC+1 Benoit ha
>>>> scritto:
>>>>
>>>>> Thanks Gino, I'm going to have a look.  In addition to my post on the
>>>>> discussion group that you mention, I also began to do in my mathbox what
>>>>> you described, i.e., adding enough DV conditions to the technical lemmas 
>>>>> so
>>>>> as to later remove some ax-13 usages, but less systematically.  Some
>>>>> theorems made it to the main sections, but most remain in my mathbox, in
>>>>> the section "20.15.4.12  Removing dependencies on ax-13 (and ax-11)", 
>>>>> which
>>>>> also has a section head comment to explain the principles. The plan was to
>>>>> move to Main only the ones that had the greatest benefits, but since there
>>>>> was no clear criterion, this kind of stalled.
>>>>>
>>>>> Benoît
>>>>>
>>>>> On Tuesday, January 2, 2024 at 12:52:10 AM UTC+1 di@gmail.com
>>>>> wrote:
>>>>>
>>>>>> On Mon, Jan 1, 2024 at 6:43 PM Jim Kingdon  wrote:
>>>>>>
>>>>>>> One (historical?) note: some of what we have now is the result of
>>>>>>> experimentation in the opposite direction - trying to figure out 
>>>>>>> whether a
>>>>>>> logical system can be built without distinct variable constraints at 
>>>>>>> all (I
>>>>>>> think there is some reference to this in some comments or web pages). I
>>>>>>> think the verdict was that it was possible but so cumbersome as to be
>>>>>>> impractical (because all the distinctor antecedents need to be carried
>>>>>>> along until the point where 

RE: Those of you that have Nest Thermostats.

[Mario Eiland]

HI Jenny,

I don’t know if you use an iPhone or some other type of phone. I use an iPhone 
and I installed the Nest app on there. In the event that you do have access to 
the Nest app on an iPhone. This is how you would turn off the learning mode.

Open the Nest app > Find the Settings button and double tap to get into 
Settings > scroll all the way to the bottom and look for whatever you named the 
location of where the thermostat is located (in my case it’s Dining Room) > 
double tap here to get into the specific settings for your location > look for 
Auto Schedule and turn that off.

 

If you use Alexa, you can also integrate your thermostat with it. Go to your 
Alexa app on your smart phone and download the Nest Skill.

 

Hope that helps some!

 

From: viphone@googlegroups.com  On Behalf Of Jenny 
Bomareto
Sent: Sunday, March 10, 2024 10:20 AM
To: viphone@googlegroups.com
Subject: Re: Those of you that have Nest Thermostats.

 

If you think the learning mode is on, how do I turn that off? Or would it be 
better for a visual person to do that with the wheel thing on the thermostat 
that’s connected to the wall?  Also, will I still conserve energy if learning 
mode is turned off? When I leave to go somewhere will it go into a way mode 
since you know how like when you leave your house that’s why it normally does 
that it’s so it’s not using as much energy once you leave your house.

Thanks for reading regarding this matter.
Jenny Bomareto


Sent from my iPhone 15





On Mar 10, 2024, at 12:02 AM, Mario Eiland mailto:eila...@gmail.com> > wrote:



Hi Jenny,

It sounds like you might have your thermostat set on learning mode?

I turned learning mode off and I just go with the conventional way of using a 
schedule. I keep mine always in heat or cool mode depending in which season we 
are and om home mode all the time. There are four of us living in the house and 
seldom is the house empty. So I don’t find it necessary to have it change to 
away.

I scheduled for the night temperature to drop as low as 65 degrees from 10:00 
PM to 5:00 AM. 

>From 5:00 AM to 10:00 PM I have it set to get up to 68 degrees.

Of course, if I need it to change it then I use my Alexa to tell it to set the 
heat or cool to whatever temperature I want. Also, I can use the Nest app to do 
that as well, but I find it’s more convenient to use the Alexa devices.

I don’t know if that helps any, but there you go.  

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Jenny Bomareto
Sent: Saturday, March 9, 2024 5:02 PM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: Those of you that have Nest Thermostats.

 

Is it better to keep it on home mode when I’m at home? To conserve energy as I 
do not want to do the eco-temperatures because I don’t know what is the proper 
range for that and of course I know the reason it goes to a way mode for when I 
leave my house is to conserve energy.

 

Cooling is said to 78° with the current temperature of 74°. Now earlier today 
even though it’s been set on 78 and I have not changed the temperature earlier 
we’re staying with the temperature of 70° sometimes 71 sometimes 72 sometimes 
73° again I have not changed, the temperature since my neighbor took off all 
those schedules I have no clue how that happened but she turned auto schedule 
off. 

 

Thanks for reading regarding this matter.
Jenny Bomareto


Sent from my iPhone 15

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu <mailto:mk...@ucla.edu> . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com <mailto:caraqu...@caraquinn.com> 
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
<mailto:viphone+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/EE4399E2-4679-4B89-92D4-DA2B1FABC572%40gmail.com
 
<https://groups.google.com/d/msgid/viphone/EE4399E2-4679-4B89-92D4-DA2B1FABC572%40gmail.com?utm_medium=email_source=footer>
 .

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than 

[kwordquiz] [Bug 483117] New: Error when search for download new stuff

[Mario]

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

Bug ID: 483117
   Summary: Error when search for download new stuff
Classification: Applications
   Product: kwordquiz
   Version: 24.02.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: pe...@peterandlinda.com
  Reporter: mojo...@gmail.com
CC: aa...@kde.org
  Target Milestone: ---

SUMMARY
Gives a unspecific error when search is used but still produces results.

STEPS TO REPRODUCE
1. open kwordquiz
2. go to download deck
3. search someting and hit enter

OBSERVED RESULT
get a box with:
An Error Occurred
Unknown Open Collaboration Service API error.(0)


EXPECTED RESULT
should not throw an error

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
terminal extract:
QList("/home/mario/.local/share/kvtml/spanisch.kvtml")
kf.coreaddons: Could not lock file:
"/home/mario/.local/share/stalefiles/kwordquiz/spanisch.kvtmlvR7file_%2Fhome%2Fmario%2F.local%2Fshare%2FkvtmlEUNcuvR7"
KEduVocKvtmlReader for kvtml version 1 files started.
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
Warning! Lesson order may be confused. Are all lessons in order in the file?
addLanguage(  0 ,  "de" ):  "German"
addLanguage(  1 ,  "es" ):  "Spanish"
Reading user defined tense description:  "Presente"
 Add tense:  "#1"  -  "Presente"
Reading user defined tense description:  "Participio"
 Add tense:  "#2"  -  "Participio"
Reading user defined tense description:  "Gerundio"
 Add tense:  "#3"  -  "Gerundio"
Reading user defined tense description:  "Pretérito perfecto"
 Add tense:  "#4"  -  "Pretérito perfecto"
Reading user defined tense description:  "Pretérito indefinido"
 Add tense:  "#5"  -  "Pretérito indefinido"
Reading user defined tense description:  "Futuro imperfecto"
 Add tense:  "#6"  -  "Futuro imperfecto"
Reading user defined tense description:  "Condicional simple"
 Add tense:  "#7"  -  "Condicional simple"
Reading user defined tense description:  "Imperativo"
 Add tense:  "#8"  -  "Imperativo"
Reading user defined tense description:  "Subjuntivo presente"
 Add tense:  "#9"  -  "Subjuntivo presente"
QIODevice::read (QNetworkReplyHttpImpl): device not open
parseList():: XML Error:  "Premature end of document." 
In xml name "" with text "" at offset:
 0 
In XML:
 ""
qrc:/qml/SettingsPage.qml:10:1: QML SettingsPage: Created graphical object was
not placed in the graphics scene.
file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:1014:5: QML RowLayout:
StackView has detected conflicting anchors. Transitions may not execute
properly.
QIODevice::read (QNetworkReplyHttpImpl): device not open
parseList():: XML Error:  "Premature end of document." 
In xml name "" with text "" at offset:
 0 
In XML:
 ""

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

RE: Accessible doorbell systems

[Mario Eiland]

Hi Don,

 

When asking about accessible doorbells, what do you mean by accessible? How 
accessible would you like it to be?

I also use the Ring doorbell and I have it integrated with everybody’s  iPhone 
who lives in the house plus our Echo devices. Any time anyone nears our house 
porch we receive announcements that it detected motion. If someone rings the 
doorbell we have the option to either pick it up via the Ring app on our 
iPhones or the Alexa by simply asking Alexa to answer doorbell. For those who 
can see can activate the camera on their phones and see who is at the door. 
Unfortunately, it doesn’t identify the person for me yet. I’m hoping that’s 
near in the future with the advancement of AI. But for now I love it since we 
are notified any time we have a package dropped off and if anyone is home then 
we can immediately retrieve it.

I’m not sure how it integrates with the Google Home, but with the Echo devices 
you can download, what they call a Skill with the Alexa app and as long as you 
have a Ring account establish then you can sign into the Ring Skill and 
integrate it with your Echo. It’s pretty awesome!

Hope that helps some!

 

From: viphone@googlegroups.com  On Behalf Of Esther 
Levegnale
Sent: Sunday, March 10, 2024 6:05 AM
To: viphone@googlegroups.com
Subject: Re: Accessible doorbell systems

 

I believe ring doorbell is a good one. Anyway, good luck. Esther.

Sent From Esther's Amazing and Awesome iPhone 13 Pro Max!





On Mar 10, 2024, at 6:25 AM, djrisav...@att.net   
wrote:



Hello all,

I was wondering what anyone suggest or recommend as the most accessible and 
also affordable doorbell system is for a single widower person living in a 
small size condo that can be accessed with various devices like iPhones, google 
home or Alexa and how easy are they to set up?

Thanks.

Don

 

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu  . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com  
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/021f01da72d5%24499f0610%24dcdd1230%24%40att.net
 

 .

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu  . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com  
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/5EBF4CC0-0D1B-4F2C-BF6B-FB5A7D47C720%40sbcglobal.net
 

 .

-- 
The following information is important for all members of the V iPhone list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your V iPhone list moderator is Mark Taylor.  Mark can be reached at:  
mk...@ucla.edu.  Your list owner is Cara Quinn - you can reach Cara at 
caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com.
To view this 

RE: Those of you that have Nest Thermostats.

[Mario Eiland]

Hi Jenny,

It sounds like you might have your thermostat set on learning mode?

I turned learning mode off and I just go with the conventional way of using a 
schedule. I keep mine always in heat or cool mode depending in which season we 
are and om home mode all the time. There are four of us living in the house and 
seldom is the house empty. So I don’t find it necessary to have it change to 
away.

I scheduled for the night temperature to drop as low as 65 degrees from 10:00 
PM to 5:00 AM. 

>From 5:00 AM to 10:00 PM I have it set to get up to 68 degrees.

Of course, if I need it to change it then I use my Alexa to tell it to set the 
heat or cool to whatever temperature I want. Also, I can use the Nest app to do 
that as well, but I find it’s more convenient to use the Alexa devices.

I don’t know if that helps any, but there you go.  

 

From: viphone@googlegroups.com  On Behalf Of Jenny 
Bomareto
Sent: Saturday, March 9, 2024 5:02 PM
To: viphone@googlegroups.com
Subject: Those of you that have Nest Thermostats.

 

Is it better to keep it on home mode when I’m at home? To conserve energy as I 
do not want to do the eco-temperatures because I don’t know what is the proper 
range for that and of course I know the reason it goes to a way mode for when I 
leave my house is to conserve energy.

 

Cooling is said to 78° with the current temperature of 74°. Now earlier today 
even though it’s been set on 78 and I have not changed the temperature earlier 
we’re staying with the temperature of 70° sometimes 71 sometimes 72 sometimes 
73° again I have not changed, the temperature since my neighbor took off all 
those schedules I have no clue how that happened but she turned auto schedule 
off. 

 

Thanks for reading regarding this matter.
Jenny Bomareto


Sent from my iPhone 15

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu  . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com  
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/EE4399E2-4679-4B89-92D4-DA2B1FABC572%40gmail.com
 

 .

-- 
The following information is important for all members of the V iPhone list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your V iPhone list moderator is Mark Taylor.  Mark can be reached at:  
mk...@ucla.edu.  Your list owner is Cara Quinn - you can reach Cara at 
caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/01e201da72a8%2418fbd380%244af37a80%24%40gmail.com.

[Bug 2056498] Re: Kernel crash in amd gpu driver

[Mario Limonciello]

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

** This bug has been marked a duplicate of bug 2039926
   Error UBSAN: array-index-out-of-bounds amdgpu 
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

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

Title:
  Kernel crash in amd gpu driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056498/+subscriptions


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

[Kernel-packages] [Bug 2056498] Re: Kernel crash in amd gpu driver

[Mario Limonciello]

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

** This bug has been marked a duplicate of bug 2039926
   Error UBSAN: array-index-out-of-bounds amdgpu 
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

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

Title:
  Kernel crash in amd gpu driver

Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Mar  7 19:07:10 ripper kernel: [9.873519] UBSAN: 
array-index-out-of-bounds in 
/build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  Mar  7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for 
type 'ATOM_Polaris_SCLK_Dependency_Record [1]'
  Mar  7 19:07:10 ripper kernel: [9.873538] CPU: 4 PID: 849 Comm: 
systemd-udevd Not tainted 6.5.0-17-generic #17~22.04.1-Ubuntu
  Mar  7 19:07:10 ripper kernel: [9.873542] Hardware name: LENOVO 
30E1S3VV00/1046, BIOS S07KT45A 01/20/2022
  Mar  7 19:07:10 ripper kernel: [9.873544] Call Trace:
  Mar  7 19:07:10 ripper kernel: [9.873545]  
  Mar  7 19:07:10 ripper kernel: [9.873547]  dump_stack_lvl+0x48/0x70
  Mar  7 19:07:10 ripper kernel: [9.873551]  dump_stack+0x10/0x20
  Mar  7 19:07:10 ripper kernel: [9.873554]  
__ubsan_handle_out_of_bounds+0xc6/0x110
  Mar  7 19:07:10 ripper kernel: [9.873560]  
smu7_get_pp_table_entry_callback_func_v1+0x9b7/0xa00 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.873897]  ? srso_return_thunk+0x5/0x10
  Mar  7 19:07:10 ripper kernel: [9.873900]  ? vi_pcie_rreg+0x6e/0x90 
[amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.874187]  ? 
__pfx_smu7_get_pp_table_entry_callback_func_v1+0x10/0x10 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.874515]  
get_powerplay_table_entry_v1_0+0xf8/0x490 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.874842]  
smu7_get_pp_table_entry_v1+0x41/0x4c0 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.875169]  
smu7_get_pp_table_entry+0x3d/0x50 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.875495]  
psm_init_power_state_table+0x161/0x250 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.875826]  hwmgr_hw_init+0xe3/0x1e0 
[amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.876150]  pp_hw_init+0x16/0x50 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.876484]  
amdgpu_device_ip_init+0x48d/0x960 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.876749]  
amdgpu_device_init+0x9a2/0x1150 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.877014]  
amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.877278]  amdgpu_pci_probe+0x182/0x450 
[amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.877541]  local_pci_probe+0x47/0xb0
  Mar  7 19:07:10 ripper kernel: [9.877545]  pci_call_probe+0x55/0x190
  Mar  7 19:07:10 ripper kernel: [9.877550]  pci_device_probe+0x84/0x120
  Mar  7 19:07:10 ripper kernel: [9.877553]  ? srso_return_thunk+0x5/0x10
  Mar  7 19:07:10 ripper kernel: [9.877557]  really_probe+0x1cc/0x430
  Mar  7 19:07:10 ripper kernel: [9.877560]  
__driver_probe_device+0x8c/0x190
  Mar  7 19:07:10 ripper kernel: [9.877563]  driver_probe_device+0x24/0xd0
  Mar  7 19:07:10 ripper kernel: [9.877566]  __driver_attach+0x10b/0x210
  Mar  7 19:07:10 ripper kernel: [9.877569]  ? 
__pfx___driver_attach+0x10/0x10
  Mar  7 19:07:10 ripper kernel: [9.877572]  bus_for_each_dev+0x8d/0xf0
  Mar  7 19:07:10 ripper kernel: [9.877576]  driver_attach+0x1e/0x30
  Mar  7 19:07:10 ripper kernel: [9.877579]  bus_add_driver+0x127/0x240
  Mar  7 19:07:10 ripper kernel: [9.877583]  driver_register+0x5e/0x130
  Mar  7 19:07:10 ripper kernel: [9.877586]  ? __pfx_amdgpu_init+0x10/0x10 
[amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.877849]  __pci_register_driver+0x62/0x70
  Mar  7 19:07:10 ripper kernel: [9.877852]  amdgpu_init+0x69/0xff0 [amdgpu]
  Mar  7 19:07:10 ripper kernel: [9.878111]  ? srso_return_thunk+0x5/0x10
  Mar  7 19:07:10 ripper kernel: [9.878114]  do_one_initcall+0x5e/0x340
  Mar  7 19:07:10 ripper kernel: [9.878120]  do_init_module+0x68/0x260
  Mar  7 19:07:10 ripper kernel: [9.878123]  load_module+0xb85/0xcd0
  Mar  7 19:07:10 ripper kernel: [9.878128]  ? srso_return_thunk+0x5/0x10
  Mar  7 19:07:10 ripper kernel: [9.878131]  ? 
security_kernel_post_read_file+0x75/0x90
  Mar  7 19:07:10 ripper kernel: [9.878136]  
init_module_from_file+0x96/0x100
  Mar  7 19:07:10 ripper kernel: [9.878139]  ? srso_return_thunk+0x5/0x10
  Mar  7 19:07:10 ripper kernel: [9.878142]  ? 
init_module_from_file+0x96/0x100
  Mar  7 19:07:10 ripper kernel: [9.878149]  
idempotent_init_module+0x11c/0x2b0
  Mar  7 19:07:10 ripper kernel: [9.878155]  
__x64_sys_finit_module+0x64/0xd0
  Mar  7 19:07:10 ripper kernel: [9.878159]  do_syscall_64+0x5b/0x90
  

[PATCH v2] drm/amd/display: Use freesync when `DRM_EDID_FEATURE_CONTINUOUS_FREQ` found

[Mario Limonciello]

The monitor shipped with the Framework 16 supports VRR [1], but it's not
being advertised.

This is because the detailed timing block doesn't contain
`EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max
frequencies.  This check however is superfluous for this case because
update_display_info() calls drm_get_monitor_range() to get these ranges
already.

So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then
turn on freesync without extra checks.

Closes: 
https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/
Closes: 
https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/
Closes: 
https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338
Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf
Signed-off-by: Mario Limonciello 
---
v1->v2:
 * Use is_dp_capable_without_timing_msa() as well for new case
 * Move edid checks up a level
---
 .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 19 +++
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 
b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 5b7293da5453..4e1633a18f2c 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -11233,18 +11233,21 @@ void amdgpu_dm_update_freesync_caps(struct 
drm_connector *connector,
if (!adev->dm.freesync_module)
goto update;
 
-   if (sink->sink_signal == SIGNAL_TYPE_DISPLAY_PORT
-   || sink->sink_signal == SIGNAL_TYPE_EDP) {
+   if (edid && (sink->sink_signal == SIGNAL_TYPE_DISPLAY_PORT ||
+sink->sink_signal == SIGNAL_TYPE_EDP)) {
bool edid_check_required = false;
 
-   if (edid) {
-   edid_check_required = is_dp_capable_without_timing_msa(
-   adev->dm.dc,
-   amdgpu_dm_connector);
+   if (is_dp_capable_without_timing_msa(adev->dm.dc,
+amdgpu_dm_connector)) {
+   if (edid->features & DRM_EDID_FEATURE_CONTINUOUS_FREQ)
+   freesync_capable = true;
+   else
+   edid_check_required = edid->version > 1 ||
+ (edid->version == 1 &&
+  edid->revision > 1);
}
 
-   if (edid_check_required == true && (edid->version > 1 ||
-  (edid->version == 1 && edid->revision > 1))) {
+   if (edid_check_required) {
for (i = 0; i < 4; i++) {
 
timing  = >detailed_timings[i];
-- 
2.34.1

[Bug 2056548] Re: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories

[Mario Limonciello]

JFYI, Noble already has 1.9.14, this request is for Jammy.  There are a
bunch of other Jammy specific bugs that would be fixed by such a SRU.

https://bugs.launchpad.net/ubuntu/jammy/+source/fwupd

The SRU process (https://wiki.ubuntu.com/StableReleaseUpdate) has an
exception for fwupd (https://wiki.ubuntu.com/firmware-updates) that
/should/ allow migrating from 1.7.x to 1.9.x.


** Also affects: fwupd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: fwupd (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: fwupd (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  fwupd metadata bug due to outdated version in Ubuntu 22.04
  repositories

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


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

[Desktop-packages] [Bug 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Technically this bug belongs to the pulseaudio package in Ubuntu, not
pipewire, but the bug tracker does not let me file a bug against
pulseaudio.

** Tags added: pipewire pulseaudio

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

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  New
Status in PipeWire:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I hoped that Pulseaudio 17 would be included in Debian in time for
  integration into Ubuntu 24.04-LTS, but apparently not much maintenance
  of pulseaudio is happening on the Debian side at the moment.

  Given that this bug affects all Ubuntu versions since Ubuntu
  22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio
  15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at
  least for the upcoming 24.04-LTS.

  Alternatively it would have been great to get Pulseaudio upgraded to
  version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
  apparently that is too late now, according to
  https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

  Thanks,
  -mario

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+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 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Technically this bug belongs to the pulseaudio package in Ubuntu, not
pipewire, but the bug tracker does not let me file a bug against
pulseaudio.

** Tags added: pipewire pulseaudio

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

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+subscriptions


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

[Touch-packages] [Bug 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Technically this bug belongs to the pulseaudio package in Ubuntu, not
pipewire, but the bug tracker does not let me file a bug against
pulseaudio.

** Tags added: pipewire pulseaudio

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2056079

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  New
Status in PipeWire:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I hoped that Pulseaudio 17 would be included in Debian in time for
  integration into Ubuntu 24.04-LTS, but apparently not much maintenance
  of pulseaudio is happening on the Debian side at the moment.

  Given that this bug affects all Ubuntu versions since Ubuntu
  22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio
  15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at
  least for the upcoming 24.04-LTS.

  Alternatively it would have been great to get Pulseaudio upgraded to
  version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
  apparently that is too late now, according to
  https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

  Thanks,
  -mario

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+subscriptions


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

RE: Apps and Widgets

[Mario Eiland]

You get announcements such as it will start raining in 15 minutes at your 
location.

 

 

From: viphone@googlegroups.com  On Behalf Of 
Christopher Chaltain
Sent: Thursday, March 7, 2024 4:30 PM
To: viphone@googlegroups.com
Subject: RE: Apps and Widgets

 

You can also get into edit mode by just flicking down once and double tapping.

 

I have the weather widget in a stacked widget, and I hear “74 degrees, cloudy, 
high of 74 degrees, low of 64 degrees” when I touch the app, so I think Mario 
is right, and that’s what you need.

 

I’m also wondering what you get when you turn on badges in the notifications 
for the weather app.

 

--

Christopher (AKA CJ) =>÷

Chaltain at Outlook, USA

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
Mario Eiland
Sent: Thursday, March 7, 2024 5:40 PM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: RE: Apps and Widgets

 

HI Jim,

If I remember correctly widgets were an option we could have on or turned off 
when we first set up our iPhones. If that’s something you want back such as the 
weather widget, then try the following.

Double tap twice and hold on the second tap and you will hear couple of tones 
and VoiceOver will announce “start Editing.” Scroll to the top and you will 
find an option to add a widget. Double tap on that and you will see a list of 
widgets you can add and one of those is the weather widget. That should give 
you a good start.

 

From: viphone@googlegroups.com <mailto:viphone@googlegroups.com>  
mailto:viphone@googlegroups.com> > On Behalf Of 
portillo@gmail.com <mailto:portillo@gmail.com> 
Sent: Thursday, March 7, 2024 2:31 PM
To: viphone@googlegroups.com <mailto:viphone@googlegroups.com> 
Subject: Apps and Widgets

 

Good afternoon,

I have an inquiry, so please bear with me, because I’m uncertain about some 
things.

When I received a new work iPhone, one thing I noticed was that when I’d put my 
finger on the Weather app, it would not just say “Weather”, but it would also 
give me the location and other information, such as temperatures and whether or 
not rain was expected. My own personal phone doesn’t do that when I touch the 
weather app. I have to go into it and then read about my location and 
temperature and such. Much more swiping.

I’d love to be able to have my weather app speak those things on my personal 
iPhone as well.

It’s the same with the calendar app on my work iPhone. I’ll touch it, and it 
will give me the date, and then I swipe to the right, and it lets me know if I 
have any appointments or events. 

I’ve looked at things like settings in both apps, which really didn’t do me 
much good. Then, someone asked if I had widgets on my screen for these apps, 
and I had no idea what that meant. So, I thought I’d ask.

1.  What’s a widget?
2.  How can I make the weather app or widget speak my location’s 
temperature and relevant information by just simply touching it without 
actually getting into it?
3.  How can I get my calendar to automatically let me know if I have any 
appointments or events without always getting into it? 

If these things are being done on my Work iPhone, which is a 12, I would 
imagine they can be done on a 15 Pro.

Thanks for any information.

I’m also going to see if there are any AppleVis tutorials on whatever widgets 
are. 

Jim

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu <mailto:mk...@ucla.edu> . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com <mailto:caraqu...@caraquinn.com> 
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
<mailto:viphone+unsubscr...@googlegroups.com> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/00ca01da70df%2424480ad0%246cd82070%24%40gmail.com
 
<https://groups.google.com/d/msgid/viphone/00ca01da70df%2424480ad0%246cd82070%24%40gmail.com?utm_medium=email_source=footer>
 .

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Tayl

RE: Apps and Widgets

[Mario Eiland]

HI Jim,

If I remember correctly widgets were an option we could have on or turned off 
when we first set up our iPhones. If that’s something you want back such as the 
weather widget, then try the following.

Double tap twice and hold on the second tap and you will hear couple of tones 
and VoiceOver will announce “start Editing.” Scroll to the top and you will 
find an option to add a widget. Double tap on that and you will see a list of 
widgets you can add and one of those is the weather widget. That should give 
you a good start.

 

From: viphone@googlegroups.com  On Behalf Of 
portillo@gmail.com
Sent: Thursday, March 7, 2024 2:31 PM
To: viphone@googlegroups.com
Subject: Apps and Widgets

 

Good afternoon,

I have an inquiry, so please bear with me, because I’m uncertain about some 
things.

When I received a new work iPhone, one thing I noticed was that when I’d put my 
finger on the Weather app, it would not just say “Weather”, but it would also 
give me the location and other information, such as temperatures and whether or 
not rain was expected. My own personal phone doesn’t do that when I touch the 
weather app. I have to go into it and then read about my location and 
temperature and such. Much more swiping.

I’d love to be able to have my weather app speak those things on my personal 
iPhone as well.

It’s the same with the calendar app on my work iPhone. I’ll touch it, and it 
will give me the date, and then I swipe to the right, and it lets me know if I 
have any appointments or events. 

I’ve looked at things like settings in both apps, which really didn’t do me 
much good. Then, someone asked if I had widgets on my screen for these apps, 
and I had no idea what that meant. So, I thought I’d ask.

1.  What’s a widget?
2.  How can I make the weather app or widget speak my location’s 
temperature and relevant information by just simply touching it without 
actually getting into it?
3.  How can I get my calendar to automatically let me know if I have any 
appointments or events without always getting into it? 

If these things are being done on my Work iPhone, which is a 12, I would 
imagine they can be done on a 15 Pro.

Thanks for any information.

I’m also going to see if there are any AppleVis tutorials on whatever widgets 
are. 

Jim

-- 
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: 
mk...@ucla.edu  . Your list owner is Cara Quinn - you 
can reach Cara at caraqu...@caraquinn.com  
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com 
 .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/00ca01da70df%2424480ad0%246cd82070%24%40gmail.com
 

 .

-- 
The following information is important for all members of the V iPhone list.

If you have any questions or concerns about the running of this list, or if you 
feel that a member's post is inappropriate, please contact the owners or 
moderators directly rather than posting on the list itself.

Your V iPhone list moderator is Mark Taylor.  Mark can be reached at:  
mk...@ucla.edu.  Your list owner is Cara Quinn - you can reach Cara at 
caraqu...@caraquinn.com

The archives for this list can be searched at:
http://www.mail-archive.com/viphone@googlegroups.com/
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/viphone/083f01da70e8%24c01e5d70%24405b1850%24%40gmail.com.

How to add the bootargs parameter between the bootcmds parameters

[Mario Marietto]

Hello to everyone.

These days I'm playing with my old ARM Chromebook model "SNOW". As you
probably know,this kind of Netbook can load an external operating system
using the sd card slot or the usb port. Unfortunately,my Chromebook has the
sd card slot broken. So,what I want to do is to load Linux using the usb
port. I've bought one converter from sd card to usb and I've installed
Devuan 5 on the sd card ; I have inserted the sd card inside the adapter
and would like to boot Linux (Devuan 5) through it. The u-boot version that
I have installed is special because the code contains the patches needed to
enable kvm. You should also know that the parameters to boot Linux are
embedded inside the code,as you can see below :

https://github.com/virtualopensystems/u-boot/blob/eecfeb578e296ef3b739ac918a39b6c177dff58a/include/configs/snow.h#L101

now. I've tried many times to recompile it,trying to change the root device
from /dev/mmcblk1p4 to /dev/sda4,because sda4 is the root device
now,because the Linux files are stored on the sd card,partition 4,but I
failed every time. Now I want to use another method to bypass the
"root=/dev/mmcblk1p4"
parameter. This is what I did :

setenv bootcmd "usb start ; usb dev 0 ; ext2load usb 0:3 0x80008000 uImage
; ext2load usb 0:3 0x4300 exynos5250-snow.dtb ; bootargs console=tty1
root=/dev/sda4 rw rootwait clk_ignore_unused --no-log ; bootm 0x80008000 -
0x4300"
saveenv
boot

Well,it does not work because despite the fact that I have said to choose
sda4 as the root device,it persists to use mmcblk1p4. This is the message
reported :

waiting for root device /dev/mmcblk1p4
sda attached SCSI removable disk...

I would like to know if I have written the parameters correctly. I don't
see errors. The only problem is that it does not pick sda4.

Let me know,thanks.

-- 
Mario.

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Opinion
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


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

[Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.

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

Title:
  Annoying boot messages interfering with splash screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.

-- 
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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Opinion
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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

Re: Migrar de 11 a 16 en CentOS 6.8

[Mario González Troncoso]

On Wed, 6 Mar 2024, 20:14 Alejandro Flores,  wrote:

> Hola
>
> Quiero saber si alguien ha instalado la versión 16 en CentOS 6.8.
>

Seguro que es CentOS 6.8? Si es así, pienso que las posibilidades de que
encuentres a alguien son super pocas. Ya va a ser EOL incluso.


> Y si pueden compartir su experiencia de migración.
>
> Saludos
> Alejandro Flores
>

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 15:31, Marek Marczykowski-Górecki wrote:

On Wed, Mar 06, 2024 at 02:37:20PM -0600, Mario Limonciello wrote:

On 3/6/2024 14:34, Sébastien Chaumat wrote:



Le mer. 6 mars 2024 à 19:51, Mario Limonciello
mailto:mario.limoncie...@amd.com>> a écrit :

 On 3/6/2024 12:49, Sébastien Chaumat wrote:
  >
  >
  > Le mer. 6 mars 2024 à 19:08, Mario Limonciello
  > mailto:mario.limoncie...@amd.com>
 <mailto:mario.limoncie...@amd.com
 <mailto:mario.limoncie...@amd.com>>> a écrit :
  >
  >     On 3/6/2024 12:05, Sébastien Chaumat wrote:
  >      >
  >      >
  >      > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
  >      >       >     Also; I'd be really interested to hear what happens with
  >     s2idle with
  >      >     Xen
  >      >     now (if it works).
  >      >
  >      >
  >      > suspend to RAM now works :)
  >
  >     Do you see /sys/power/suspend_stats/last_hw_sleep increasing
 with your
  >     suspend cycle?
  >
  >
  > No,  it does not increase (0).
  >

 OK, then in that case I suggest you run
 https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py 
<https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py>
 in the hypervisor to find out what's wrong.


It fails with xen (not bare metal) during the prerequisite tests :



The script might need some modifications for tests that don't make sense in
the context of Xen.


✅ GPIO driver `pinctrl_amd` available
Traceback (most recent call last):
    File "/home/sch/Downloads/amd_s2idle.py", line 2447, in 
      test = app.prerequisites()
             ^^^
    File "/home/sch/Downloads/amd_s2idle.py", line 1938, in prerequisites
      if not check():
             ^^^
    File "/home/sch/Downloads/amd_s2idle.py", line 826, in check_msr
      val = read_msr(reg, 0)
            
    File "/home/sch/Downloads/amd_s2idle.py", line 813, in read_msr
      val = struct.unpack("Q", os.read(f, 8))[0]
                               ^
OSError: [Errno 5] Input/output error

Last line in the log is :
2024-03-06 21:29:33,146 DEBUG: Lockdown: [none] integrity confidentiality



Do you have userspace MSR support compiled in?  If not; that could explain
that problem.  But it's very unlikely you changed the MSRs.
For the purpose of finding where the suspend problem is, I'd comment out
that specific check for now.


The s2idle isn't supported in Xen yet. Only S3 is. In fact, I have some
work-in-progress patches for that, I may try testing them on this
system.



OK; the "most important parts" I want to point out that are on bare 
metal and might not be obvious:

 * Infra from drivers/acpi/x86/s2idle.c
 * amd-pmc driver
 * USB4 driver (thunderbolt.ko)
 * NVME needs to use "simple suspend"

FYI - I'm going to be MIA for a while on personal leave starting this 
weekend, please keep me on CC on your progress and if you need help when 
I get back from my leave I'll comment on it.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 14:34, Sébastien Chaumat wrote:



Le mer. 6 mars 2024 à 19:51, Mario Limonciello 
mailto:mario.limoncie...@amd.com>> a écrit :


On 3/6/2024 12:49, Sébastien Chaumat wrote:
 >
 >
 > Le mer. 6 mars 2024 à 19:08, Mario Limonciello
 > mailto:mario.limoncie...@amd.com>
<mailto:mario.limoncie...@amd.com
<mailto:mario.limoncie...@amd.com>>> a écrit :
 >
 >     On 3/6/2024 12:05, Sébastien Chaumat wrote:
 >      >
 >      >
 >      > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
 >      > mailto:mario.limoncie...@amd.com> <mailto:mario.limoncie...@amd.com
<mailto:mario.limoncie...@amd.com>>
 >     <mailto:mario.limoncie...@amd.com
<mailto:mario.limoncie...@amd.com>
 >     <mailto:mario.limoncie...@amd.com
<mailto:mario.limoncie...@amd.com>>>> a écrit :
 >      >
 >      >     On 3/6/2024 11:28, Sébastien Chaumat wrote:
 >      >      >
 >      >      >
 >      >      >
 >      >      >
 >      >      >     Reasoning backward  (using a  kernel without the
 >     pinctrl_amd
 >      >     driver
 >      >      >     to ensure xen only is at stake) :
 >      >      >       checking the diff in IOAPIC  between bare
metal and xen
 >      >     (IRQ7 is
 >      >      >     on pin07 on APIC )
 >      >      >
 >      >      >     using kernel argument : apic=debug
 >      >      >
 >      >      >     bare metal :
 >      >      >     [    0.715330] fedora kernel: ... APIC VERSION:
81050010
 >      >      >     ...
 >      >      >     [    0.715433] fedora kernel:  pin07, disabled,
edge ,
 >     high,
 >      >     V(00),
 >      >      >     IRR(0), S(0), physical, D(), M(0)
 >      >      >
 >      >      >     xen :
 >      >      >     [    2.249582] fedora kernel: ... APIC VERSION:
0014
 >      >      >     ...
 >      >      >     [    2.249730] fedora kernel:  pin07, disabled,
level,
 >     low ,
 >      >     V(60),
 >      >      >     IRR(0), S(0), physical, D(), M(0)
 >      >      >
 >      >      >     So the APIC table is not the same.
 >      >      >
 >      >      >     As strange as it looks the  (IOAPIC 0) pin07 is
correctly
 >      >     described
 >      >      >     by the APIC in xen but yet differently than in
baremetal.
 >      >      >     But the APIC message comes long after the
 >      >      >     [    1.833145] fedora kernel: xen: registering
gsi 7
 >     triggering 0
 >      >      >     polarity 1
 >      >      >
 >      >      >     so I wonder if the APIC pin07 info had any
influence.
 >      >      >
 >      >      > Finally found the fix : adding ioapic_ack=new to
xen boot
 >     parameters.
 >      >      > Not only the trackpad is now working but also the ACPI
 >     Embedded
 >      >      > Controller which is completely disabled.
 >      >      >
 >      >      > Sébastien
 >      >      >
 >      >     That's great news!  I'm personally totally unfamiliar with
 >      >     ioapic_ack=new, so I did a quick search and found out
it's a Xen
 >      >     parameter (I came across
 >      >
 >
https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
<https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>
 >   
  <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>>

 >      >
 > 
  <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html> <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>>>).

 >      >
 >      >     This mentions that "new" should be the default, so why
isn't
 >     it the
 >      >     case?
 >      >
 >      >
 >      >   "This is the the default unless directed-EOI is supported"
 >      > xl dmesg without forcing the parameters shows :
 >      >
 >      > (X

Re: [PATCH] drm/amd: Drop abm_level property

[Mario Limonciello]

On 3/6/2024 12:59, Harry Wentland wrote:



On 2024-03-06 13:02, Mario Limonciello wrote:

On 3/6/2024 12:00, Xaver Hugl wrote:

Am Mi., 6. März 2024 um 18:19 Uhr schrieb Mario Limonciello
:

So the idea being if the compositor isn't using it we let
power-profiles-daemon (or any other software) take control via sysfs and
if the compositor does want to control it then it then it writes a DRM
cap and we destroy the sysfs file?


Yes. That way still only one party controls it at a given time, and we
can get both good default behavior for display servers that don't care
(like Xorg or compositors without color management support), and
compositors that want to put in the effort can do more specific things
with it.


I think that's a very good solution.

Harry, Hamza, what do you guys think?


In theory I like it. But how will this look in practice? Is PPD or compositor
on the scene first? Would it be possible to yank the sysfs away from PPD?



I double checked the existing PPD code to see how well this case maps out.

* If the compositor shows up first then PPD just wouldn't find amdgpu 
support when it probed.
* If PPD goes first and then the compositor I expect right now that PPD 
wouldn't explode.  All the cases that would update it check that the 
file exists before trying to write it.


I think the only risk is TOCTOU for that check relative to when it would 
write the file, but the worst case is you have an error in the journal 
log that it tried to write the file but it's not present (there is 
already error handling everywhere for this).


What we can do to smooth it out even more is export a CHANGE uevent from 
amdgpu when this happens.  PPD can react to the change event and totally 
stop the amdgpu plugin.



DRM client caps are set by the client when the client interacts with DRM.
At driver creation there is no client. How will the driver set things up?



You jog my mind for another idea.

1) We could reintroduce abm_level property.
2) If client connects with the cap set, we make any reads or writes to 
the sysfs return -EBUSY and we make amdgpu issue a CHANGE uevent.


* Unchanged PPD will likely log a message to the journal that writes 
fail, but won't explode.
* A changed PPD could react to the uevent and look for -EBUSY to not 
bother even logging a message to the journal.



A user might switch between DRM clients (login manager, to desktop compositor,
maybe to another VT with a different compositor). I know everything but the
login manager to desktop compositor hand-off is today considered exotic, but
what if someone starts building a use-case for it? I've done a bunch of 
gamescope
or IGT work in a different VT while I've had Plasma running on its default
VT.



If going off the cap of the client to decide whether or not to report 
-EBUSY to sysfs I think it handles the handoff cleanly.



If someone can sketch this out, with answers to all the questions above and
any other questions you can come up (be creative), I'd be happy to review.
Alternatively we can discuss this at the hackfest and maybe arrive at a
solution.


Yes; I think we should use this thread as a basis for that discussion.

Re: [PATCH] drm/amd: Drop abm_level property

[Mario Limonciello]

On 3/6/2024 12:59, Harry Wentland wrote:



On 2024-03-06 13:02, Mario Limonciello wrote:

On 3/6/2024 12:00, Xaver Hugl wrote:

Am Mi., 6. März 2024 um 18:19 Uhr schrieb Mario Limonciello
:

So the idea being if the compositor isn't using it we let
power-profiles-daemon (or any other software) take control via sysfs and
if the compositor does want to control it then it then it writes a DRM
cap and we destroy the sysfs file?


Yes. That way still only one party controls it at a given time, and we
can get both good default behavior for display servers that don't care
(like Xorg or compositors without color management support), and
compositors that want to put in the effort can do more specific things
with it.


I think that's a very good solution.

Harry, Hamza, what do you guys think?


In theory I like it. But how will this look in practice? Is PPD or compositor
on the scene first? Would it be possible to yank the sysfs away from PPD?



I double checked the existing PPD code to see how well this case maps out.

* If the compositor shows up first then PPD just wouldn't find amdgpu 
support when it probed.
* If PPD goes first and then the compositor I expect right now that PPD 
wouldn't explode.  All the cases that would update it check that the 
file exists before trying to write it.


I think the only risk is TOCTOU for that check relative to when it would 
write the file, but the worst case is you have an error in the journal 
log that it tried to write the file but it's not present (there is 
already error handling everywhere for this).


What we can do to smooth it out even more is export a CHANGE uevent from 
amdgpu when this happens.  PPD can react to the change event and totally 
stop the amdgpu plugin.



DRM client caps are set by the client when the client interacts with DRM.
At driver creation there is no client. How will the driver set things up?



You jog my mind for another idea.

1) We could reintroduce abm_level property.
2) If client connects with the cap set, we make any reads or writes to 
the sysfs return -EBUSY and we make amdgpu issue a CHANGE uevent.


* Unchanged PPD will likely log a message to the journal that writes 
fail, but won't explode.
* A changed PPD could react to the uevent and look for -EBUSY to not 
bother even logging a message to the journal.



A user might switch between DRM clients (login manager, to desktop compositor,
maybe to another VT with a different compositor). I know everything but the
login manager to desktop compositor hand-off is today considered exotic, but
what if someone starts building a use-case for it? I've done a bunch of 
gamescope
or IGT work in a different VT while I've had Plasma running on its default
VT.



If going off the cap of the client to decide whether or not to report 
-EBUSY to sysfs I think it handles the handoff cleanly.



If someone can sketch this out, with answers to all the questions above and
any other questions you can come up (be creative), I'd be happy to review.
Alternatively we can discuss this at the hackfest and maybe arrive at a
solution.


Yes; I think we should use this thread as a basis for that discussion.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 12:49, Sébastien Chaumat wrote:



Le mer. 6 mars 2024 à 19:08, Mario Limonciello 
mailto:mario.limoncie...@amd.com>> a écrit :


On 3/6/2024 12:05, Sébastien Chaumat wrote:
 >
 >
 > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
 > mailto:mario.limoncie...@amd.com>
<mailto:mario.limoncie...@amd.com
<mailto:mario.limoncie...@amd.com>>> a écrit :
 >
 >     On 3/6/2024 11:28, Sébastien Chaumat wrote:
 >      >
 >      >
 >      >
 >      >
 >      >     Reasoning backward  (using a  kernel without the
pinctrl_amd
 >     driver
 >      >     to ensure xen only is at stake) :
 >      >       checking the diff in IOAPIC  between bare metal and xen
 >     (IRQ7 is
 >      >     on pin07 on APIC )
 >      >
 >      >     using kernel argument : apic=debug
 >      >
 >      >     bare metal :
 >      >     [    0.715330] fedora kernel: ... APIC VERSION: 81050010
 >      >     ...
 >      >     [    0.715433] fedora kernel:  pin07, disabled, edge ,
high,
 >     V(00),
 >      >     IRR(0), S(0), physical, D(), M(0)
 >      >
 >      >     xen :
 >      >     [    2.249582] fedora kernel: ... APIC VERSION: 0014
 >      >     ...
 >      >     [    2.249730] fedora kernel:  pin07, disabled, level,
low ,
 >     V(60),
 >      >     IRR(0), S(0), physical, D(), M(0)
 >      >
 >      >     So the APIC table is not the same.
 >      >
 >      >     As strange as it looks the  (IOAPIC 0) pin07 is correctly
 >     described
 >      >     by the APIC in xen but yet differently than in baremetal.
 >      >     But the APIC message comes long after the
 >      >     [    1.833145] fedora kernel: xen: registering gsi 7
triggering 0
 >      >     polarity 1
 >      >
 >      >     so I wonder if the APIC pin07 info had any influence.
 >      >
 >      > Finally found the fix : adding ioapic_ack=new to xen boot
parameters.
 >      > Not only the trackpad is now working but also the ACPI
Embedded
 >      > Controller which is completely disabled.
 >      >
 >      > Sébastien
 >      >
 >     That's great news!  I'm personally totally unfamiliar with
 >     ioapic_ack=new, so I did a quick search and found out it's a Xen
 >     parameter (I came across
 >
https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
<https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>
 >   
  <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html <https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>>).

 >
 >     This mentions that "new" should be the default, so why isn't
it the
 >     case?
 >
 >
 >   "This is the the default unless directed-EOI is supported"
 > xl dmesg without forcing the parameters shows :
 >
 > (XEN) Enabled directed EOI with ioapic_ack_old on!

Got it; it sounds to me like a logic mismatch in Xen then.

 >
 >     Also; I'd be really interested to hear what happens with
s2idle with
 >     Xen
 >     now (if it works).
 >
 >
 > suspend to RAM now works :)

Do you see /sys/power/suspend_stats/last_hw_sleep increasing with your
suspend cycle?


No,  it does not increase (0).



OK, then in that case I suggest you run 
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py 
in the hypervisor to find out what's wrong.

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 12:05, Sébastien Chaumat wrote:



Le mer. 6 mars 2024 à 18:33, Mario Limonciello 
mailto:mario.limoncie...@amd.com>> a écrit :


On 3/6/2024 11:28, Sébastien Chaumat wrote:
 >
 >
 >
 >
 >     Reasoning backward  (using a  kernel without the pinctrl_amd
driver
 >     to ensure xen only is at stake) :
 >       checking the diff in IOAPIC  between bare metal and xen 
(IRQ7 is

 >     on pin07 on APIC )
 >
 >     using kernel argument : apic=debug
 >
 >     bare metal :
 >     [    0.715330] fedora kernel: ... APIC VERSION: 81050010
 >     ...
 >     [    0.715433] fedora kernel:  pin07, disabled, edge , high,
V(00),
 >     IRR(0), S(0), physical, D(), M(0)
 >
 >     xen :
 >     [    2.249582] fedora kernel: ... APIC VERSION: 0014
 >     ...
 >     [    2.249730] fedora kernel:  pin07, disabled, level, low ,
V(60),
 >     IRR(0), S(0), physical, D(), M(0)
 >
 >     So the APIC table is not the same.
 >
 >     As strange as it looks the  (IOAPIC 0) pin07 is correctly
described
 >     by the APIC in xen but yet differently than in baremetal.
 >     But the APIC message comes long after the
 >     [    1.833145] fedora kernel: xen: registering gsi 7 triggering 0
 >     polarity 1
 >
 >     so I wonder if the APIC pin07 info had any influence.
 >
 > Finally found the fix : adding ioapic_ack=new to xen boot parameters.
 > Not only the trackpad is now working but also the ACPI Embedded
 > Controller which is completely disabled.
 >
 > Sébastien
 >
That's great news!  I'm personally totally unfamiliar with
ioapic_ack=new, so I did a quick search and found out it's a Xen
parameter (I came across
https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html
<https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html>).

This mentions that "new" should be the default, so why isn't it the
case?


  "This is the the default unless directed-EOI is supported"
xl dmesg without forcing the parameters shows :

(XEN) Enabled directed EOI with ioapic_ack_old on!


Got it; it sounds to me like a logic mismatch in Xen then.



Also; I'd be really interested to hear what happens with s2idle with
Xen
now (if it works).


suspend to RAM now works :)


Do you see /sys/power/suspend_stats/last_hw_sleep increasing with your 
suspend cycle?

Re: [PATCH] drm/amd: Drop abm_level property

[Mario Limonciello]

On 3/6/2024 12:00, Xaver Hugl wrote:

Am Mi., 6. März 2024 um 18:19 Uhr schrieb Mario Limonciello
:

So the idea being if the compositor isn't using it we let
power-profiles-daemon (or any other software) take control via sysfs and
if the compositor does want to control it then it then it writes a DRM
cap and we destroy the sysfs file?


Yes. That way still only one party controls it at a given time, and we
can get both good default behavior for display servers that don't care
(like Xorg or compositors without color management support), and
compositors that want to put in the effort can do more specific things
with it.


I think that's a very good solution.

Harry, Hamza, what do you guys think?

Re: [PATCH] drm/amd: Drop abm_level property

[Mario Limonciello]

On 3/6/2024 12:00, Xaver Hugl wrote:

Am Mi., 6. März 2024 um 18:19 Uhr schrieb Mario Limonciello
:

So the idea being if the compositor isn't using it we let
power-profiles-daemon (or any other software) take control via sysfs and
if the compositor does want to control it then it then it writes a DRM
cap and we destroy the sysfs file?


Yes. That way still only one party controls it at a given time, and we
can get both good default behavior for display servers that don't care
(like Xorg or compositors without color management support), and
compositors that want to put in the effort can do more specific things
with it.


I think that's a very good solution.

Harry, Hamza, what do you guys think?

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

AFAICT; these initramfs-tools package changes would cover it:

* hooks/framebuffer can be totally removed.  
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

AFAICT; these initramfs-tools package changes would cover it:

* hooks/framebuffer can be totally removed.  
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it

-- 
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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

AFAICT; these initramfs-tools package changes would cover it:

* hooks/framebuffer can be totally removed.  
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it

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

Title:
  Annoying boot messages interfering with splash screen

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


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

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.

So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.

So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.

-- 
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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Mario Limonciello]

Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.

So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.

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

Title:
  Annoying boot messages interfering with splash screen

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


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

Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD

[Mario Limonciello]

On 3/6/2024 11:28, Sébastien Chaumat wrote:





Reasoning backward  (using a  kernel without the pinctrl_amd driver
to ensure xen only is at stake) :
  checking the diff in IOAPIC  between bare metal and xen  (IRQ7 is
on pin07 on APIC )

using kernel argument : apic=debug

bare metal :
[    0.715330] fedora kernel: ... APIC VERSION: 81050010
...
[    0.715433] fedora kernel:  pin07, disabled, edge , high, V(00),
IRR(0), S(0), physical, D(), M(0)

xen :
[    2.249582] fedora kernel: ... APIC VERSION: 0014
...
[    2.249730] fedora kernel:  pin07, disabled, level, low , V(60),
IRR(0), S(0), physical, D(), M(0)

So the APIC table is not the same.

As strange as it looks the  (IOAPIC 0) pin07 is correctly described
by the APIC in xen but yet differently than in baremetal.
But the APIC message comes long after the
[    1.833145] fedora kernel: xen: registering gsi 7 triggering 0
polarity 1

so I wonder if the APIC pin07 info had any influence.

Finally found the fix : adding ioapic_ack=new to xen boot parameters.
Not only the trackpad is now working but also the ACPI Embedded 
Controller which is completely disabled.


Sébastien

That's great news!  I'm personally totally unfamiliar with 
ioapic_ack=new, so I did a quick search and found out it's a Xen 
parameter (I came across

https://xenbits.xen.org/docs/4.5-testing/misc/xen-command-line.html).

This mentions that "new" should be the default, so why isn't it the case?

Also; I'd be really interested to hear what happens with s2idle with Xen 
now (if it works).

Re: [PATCH] drm/amd: Drop abm_level property

[Mario Limonciello]

On 3/6/2024 11:08, Xaver Hugl wrote:

Like already mentioned in the power profiles daemon repository, I don't think
this makes sense. This is a display setting, which compositors have interest
in controlling, for example to:
- disable it in a bright environment, because afaiu it reduces the maximum
screen brightness
- disable it when it shows color critical content
- disable it while profiling the display
- enable it when it shows content that's definitely not color critical (based
on the content-type property of Wayland surfaces)
- enable it as a first step before properly dimming the screen on idle



This specific topic is on the agenda to discuss at 2024 Display Next 
Hackfest.



If the primary concern here is that this hasn't been used by compositors and
potential power savings aren't being realized, that could be solved by
providing documentation about what the feature does in the kernel, and by
sending a mail to wayland-devel describing why it should be used.

If the goal is to implement it in power profiles daemon and not get conflicts, I
think disabling the property by default and instead enable it + disable the
sysfs file when a CAP for it is set would make more sense than making the
listed features impossible.




So the idea being if the compositor isn't using it we let 
power-profiles-daemon (or any other software) take control via sysfs and 
if the compositor does want to control it then it then it writes a DRM 
cap and we destroy the sysfs file?

Re: [PATCH] drm/amd: Drop abm_level property

[Mario Limonciello]

On 3/6/2024 11:08, Xaver Hugl wrote:

Like already mentioned in the power profiles daemon repository, I don't think
this makes sense. This is a display setting, which compositors have interest
in controlling, for example to:
- disable it in a bright environment, because afaiu it reduces the maximum
screen brightness
- disable it when it shows color critical content
- disable it while profiling the display
- enable it when it shows content that's definitely not color critical (based
on the content-type property of Wayland surfaces)
- enable it as a first step before properly dimming the screen on idle



This specific topic is on the agenda to discuss at 2024 Display Next 
Hackfest.



If the primary concern here is that this hasn't been used by compositors and
potential power savings aren't being realized, that could be solved by
providing documentation about what the feature does in the kernel, and by
sending a mail to wayland-devel describing why it should be used.

If the goal is to implement it in power profiles daemon and not get conflicts, I
think disabling the property by default and instead enable it + disable the
sysfs file when a CAP for it is set would make more sense than making the
listed features impossible.




So the idea being if the compositor isn't using it we let 
power-profiles-daemon (or any other software) take control via sysfs and 
if the compositor does want to control it then it then it writes a DRM 
cap and we destroy the sysfs file?

[Bug 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail

[Mario Chisari]

Can confirm too. It was hard to find the solution, so I hope this will
avoid people banging head on the table.

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

Title:
  missing includedir snippet in krb5.conf causes GSSAPI to fail

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


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

[Members] Re: voting results & meeting minutes

[Mario Sabatino]

Dear Alex thank you again for your welcome and thanks to all members 
have voted me. I'll do my best to give my contribution to the XSF.


You can read information about me on the application page: 
https://wiki.xmpp.org/web/Mario_Sabatino


I'd be happy to participate to the Communication Team as a member.

Have a nice day!

Mario


Il 05/03/24 20:45, Alexander Gnauck ha scritto:

Hello,
you can find the meeting minutes here:
https://wiki.xmpp.org/web/Meeting-Minutes-2024-03-05
<https://wiki.xmpp.org/web/Meeting-Minutes-2024-03-05>
All applicants and reappliers were accepted. Congrats to everyone.

You can find the updated memberlist here:
https://xmpp.org/about/xsf/members/ <https://xmpp.org/about/xsf/members/>
A warm welcome to all our new member Mario. Feel free to say hello to the list.

Thanks,
Alex


--
Avv. Mario Sabatino

www.studiosabatino.it



publickey - mario@sabatino.pro - 0x56617369.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

[PATCH] drm/amd/display: Use freesync when `DRM_EDID_FEATURE_CONTINUOUS_FREQ` found

[Mario Limonciello]

The monitor shipped with the Framework 16 supports VRR [1], but it's not
being advertised.

This is because the detailed timing block doesn't contain
`EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max
frequencies.  This check however is superfluous for this case because
update_display_info() calls drm_get_monitor_range() to get these ranges
already.

So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then
turn on freesync without extra checks.

Closes: 
https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/
Closes: 
https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/
Closes: 
https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338
Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf [1]
Signed-off-by: Mario Limonciello 
---
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 
b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 5b7293da5453..38186d669a85 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -11238,9 +11238,12 @@ void amdgpu_dm_update_freesync_caps(struct 
drm_connector *connector,
bool edid_check_required = false;
 
if (edid) {
-   edid_check_required = is_dp_capable_without_timing_msa(
-   adev->dm.dc,
-   amdgpu_dm_connector);
+   if (edid->features & DRM_EDID_FEATURE_CONTINUOUS_FREQ)
+   freesync_capable = true;
+   else
+   edid_check_required = 
is_dp_capable_without_timing_msa(
+   adev->dm.dc,
+   amdgpu_dm_connector);
}
 
if (edid_check_required == true && (edid->version > 1 ||
-- 
2.34.1

[Touch-packages] [Bug 2056079] [NEW] Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Public bug reported:

This is a request for a backport of an existing bug fix, present in the
recent Pulseaudio version 17 release, to the outdated Pulseaudio 16
releases in jammy - noble.

Affects: Ubuntu 22.04.0 LTS and all later versions.

The fix fixes an annoying start of playback timing bug that affects my
own software package octave-psychtoolbox-3 (part of Ubuntu universe),
see
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
which uses GStreamer for video and audio playback. Psychtoolbox is a
very popular toolkit for neuroscience and related medical research, with
Ubuntu as the recommended target distribution. It requires high
reliability in audio and video presentation timing, so the bug described
in the various links below is serious to our users.

The bug also in the same way affects other media applications in Ubuntu
which play back audio via the default (auto-plugged) pulseaudiosink
GStreamer plugin. See GStreamer bug report
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
GStreamer bug turned out to be a pulseaudio client library bug (in
libpulse.so.0).

Any native pulseaudio client is affected, even if pipewire is used as
desktop sound server in recent Ubuntu releases, given that many audio
applications still access pipewire via its pulseaudio frontend (package
pipewire-pulse). See pipewire bug
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

The bug in libpulse.so.0, reported against Pulseaudio 16 in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
been fixed for the Pulseaudio 17 release.

See the following merge request for the following trivial one-liner
patch that would need to be backported to Ubuntu's current
implementation:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

I hoped that Pulseaudio 17 would be included in Debian in time for
integration into Ubuntu 24.04-LTS, but apparently not much maintenance
of pulseaudio is happening on the Debian side at the moment.

Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS,
I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in
22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for
the upcoming 24.04-LTS.

Alternatively it would have been great to get Pulseaudio upgraded to
version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

Thanks,
-mario

** Affects: gst-plugins-good
 Importance: Unknown
 Status: Unknown

** Affects: pipewire
 Importance: Unknown
 Status: Unknown

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #1735
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735

** Also affects: gst-plugins-good via
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3399
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

** Also affects: pipewire via
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2056079

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  Unknown
Status in PipeWire:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client

[Desktop-packages] [Bug 2056079] [NEW] Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

[Mario Kleiner]

Public bug reported:

This is a request for a backport of an existing bug fix, present in the
recent Pulseaudio version 17 release, to the outdated Pulseaudio 16
releases in jammy - noble.

Affects: Ubuntu 22.04.0 LTS and all later versions.

The fix fixes an annoying start of playback timing bug that affects my
own software package octave-psychtoolbox-3 (part of Ubuntu universe),
see
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
which uses GStreamer for video and audio playback. Psychtoolbox is a
very popular toolkit for neuroscience and related medical research, with
Ubuntu as the recommended target distribution. It requires high
reliability in audio and video presentation timing, so the bug described
in the various links below is serious to our users.

The bug also in the same way affects other media applications in Ubuntu
which play back audio via the default (auto-plugged) pulseaudiosink
GStreamer plugin. See GStreamer bug report
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
GStreamer bug turned out to be a pulseaudio client library bug (in
libpulse.so.0).

Any native pulseaudio client is affected, even if pipewire is used as
desktop sound server in recent Ubuntu releases, given that many audio
applications still access pipewire via its pulseaudio frontend (package
pipewire-pulse). See pipewire bug
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

The bug in libpulse.so.0, reported against Pulseaudio 16 in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
been fixed for the Pulseaudio 17 release.

See the following merge request for the following trivial one-liner
patch that would need to be backported to Ubuntu's current
implementation:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

I hoped that Pulseaudio 17 would be included in Debian in time for
integration into Ubuntu 24.04-LTS, but apparently not much maintenance
of pulseaudio is happening on the Debian side at the moment.

Given that this bug affects all Ubuntu versions since Ubuntu 22.04-LTS,
I'd ask kindly for a backport, ideally for Pulseaudio 15.99.1 in
22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at least for
the upcoming 24.04-LTS.

Alternatively it would have been great to get Pulseaudio upgraded to
version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

Thanks,
-mario

** Affects: gst-plugins-good
 Importance: Unknown
 Status: Unknown

** Affects: pipewire
 Importance: Unknown
 Status: Unknown

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #1735
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735

** Also affects: gst-plugins-good via
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3399
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

** Also affects: pipewire via
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399
   Importance: Unknown
   Status: Unknown

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

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  Unknown
Status in PipeWire:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even