[Desktop-packages] [Bug 1975823] [NEW] pipewire alsa blocks after initial buffer size of data got written
Public bug reported: I have this bug also if I install pipewire manaully on focal and jammy. I use a Java Application using the javax.sound package to get a output to the AudioSystem. I have an own Java library using the same and I poked around a bit: It uses Alsa as Output. The line object Java provides has the possibility to ask for the available bytes in the buffer. Normally with pulseaudio you can see the buffer getting filled and then, as the audio get's played back, recovering by the played back bytes amount. With pipewire-pulse on the other hand it just fills the buffer and reporting no more available bytes. But it plays back the bytes successfully written to the buffer. Meaning its unable to write more, as the available buffer size never recovers, even though the already written ones have been played just fine. I have checked the behavior also on Debain-testing, Manjaro and Fedora. Fedora is the only distro without this problem. Fedora has the package pipewire-alsa in its repositories and installed, which is not available on the other distros. If I have understood it correctly, the alsa functionality should be included into the default pipewire-pulse now, but for some reason fedora decided to keep the extra package? So I'd really like to see pipewire-pulse being the default in the future, but this has to be fixed somehow. For reference, here's an issue on the pipewire gitlab I've filed already about this: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2255 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.48-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 14:58:40 2022 InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal jammy kinetic pipewire third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1975823 Title: pipewire alsa blocks after initial buffer size of data got written Status in pipewire package in Ubuntu: New Bug description: I have this bug also if I install pipewire manaully on focal and jammy. I use a Java Application using the javax.sound package to get a output to the AudioSystem. I have an own Java library using the same and I poked around a bit: It uses Alsa as Output. The line object Java provides has the possibility to ask for the available bytes in the buffer. Normally with pulseaudio you can see the buffer getting filled and then, as the audio get's played back, recovering by the played back bytes amount. With pipewire-pulse on the other hand it just fills the buffer and reporting no more available bytes. But it plays back the bytes successfully written to the buffer. Meaning its unable to write more, as the available buffer size never recovers, even though the already written ones have been played just fine. I have checked the behavior also on Debain-testing, Manjaro and Fedora. Fedora is the only distro without this problem. Fedora has the package pipewire-alsa in its repositories and installed, which is not available on the other distros. If I have understood it correctly, the alsa functionality should be included into the default pipewire-pulse now, but for some reason fedora decided to keep the extra package? So I'd really like to see pipewire-pulse being the default in the future, but this has to be fixed somehow. For reference, here's an issue on the pipewire gitlab I've filed already about this: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2255 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.48-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 14:58:40 2022 InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1975823/+subscriptions -- Mailing list: https://lau
[Desktop-packages] [Bug 1879580] Re: Screencast interface missing
Do I see that right, that this means for people wanting to use wayland and have working screensharing (which is a kind of important thing to have working right now), are forced to use a non-LTS Ubuntu version 21.04+? And until the fix for [1] makes it into 21.10, it's basically 21.04 only that's theoretically having a working solution for the criterias: - wayland - non-buggy DE - screenshare Or will you maybe take into consideration to rebuild xdg-desktop-portal with the needed flags for the Screencast interface for 20.04? [1]: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947467 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing Status in xdg-desktop-portal package in Ubuntu: Fix Released Bug description: The `org.freedesktop.portal.ScreenCast` inferface is missing in the version shipped with Ubuntu 20.04. This interface is needed for OBS no work in non-X11 environments. Further reading: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+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
[Desktop-packages] [Bug 1947467] [NEW] gome 40 wayland-session exiting fullscreen doesn't restore original size & position
Public bug reported: Switching applications between normal and fullscreen got slower and also it won't remember position and size of the window on exiting fullscreen compared to gnome 3.x. I can also confirm this on a 20.04 installation with gnome 40 installed, that this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is working fine. I've tested this with - firefox (F11 to enter/exit fullscreen) - YouTube videos - eog On going to fullscreen it often looses focus, and on exit the window just gets resized to the full monitor resolution. Rolling back my 20.04 machine to gnome 3.36 will make this work again under wayland. Considered that gnome 40 is the default for 21.10 and also wayland is the default, I hope this get's investigated and a fix is found before 20.04 is EOL. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 21:23:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome-shell impish wayland-session ** Summary changed: - gome 40 wayland-session exiting fullscrr + gome 40 wayland-session exiting fullscreen doesn't restore original size & position ** Description changed: - switching applications between normal and fullscreen got slower and also - it won't remember position and size of the window on exiting fullscreen - compared to gnome 3.x. Can also confirm this on a 20.04 installation - with gnome 40 installed and rolled back, that this is a degradation for - gnome-shell 40 on wayland sessions. Xorg session is working fine. + Switching applications between normal and fullscreen got slower and also it won't remember position and size of the window on exiting fullscreen compared to gnome 3.x. + I can also confirm this on a 20.04 installation with gnome 40 installed, that this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is working fine. + + Rolling back my 20.04 machine to gnome 3.36 will make this work again under wayland. + Considered that gnome 40 is the default for 21.10 and also wayland is the default, I hope this get's investigated and a fix is found before 20.04 is EOL. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 21:23:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Switching applications between normal and fullscreen got slower and also it won't remember position and size of the window on exiting fullscreen compared to gnome 3.x. I can also confirm this on a 20.04 installation with gnome 40 installed, that this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is working fine. + + I've tested this with + - firefox (F11 to enter/exit fullscreen) + - YouTube videos + - eog + + On going to fullscreen it often looses focus, and on exit the window + just gets resized to the full monitor resolution. + Rolling back my 20.04 machine to gnome 3.36 will make this work again under wayland. Considered that gnome 40 is the default for 21.10 and also wayland is the default, I hope this get's investigated and a fix is found before 20.04 is EOL. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 21:23:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
@Oliver I've upgraded mine now. For me (with researching beforehand yet) the transition was a five minute thing. The downsides described above stay of course, but that's not Ubuntu's fault. But for others if they stumble across this, my setup has changed in the following points: - I've set sign+encrypt as default. This forces me to always explicitly disable it, if I send someone an email who doesn't use encryption. (automatism by email-match missing). - On the migration assistant from enigmail to port your keys, I canceled all passphrase requests, as I didn't want my private keys to be in the TB keyring. This way I got all public keys ported, but none of the private ones. - then checked with `gpg --list-secret-keys --keyid-format long` for private keys, and added for each account the correct external gnupg keyid (important: you need to use the encryption keyid, not the signing key one) Background: As long as you don't set a master password for the TB keyring, your private keys would be stored unsecured on your disk. P.S: For the privacy concerned people in general: There's a site called privacy manual, which provides a user.js for TB 78 setting a bunch of configs regarding security and privacy. It's only available in german, but maybe interesting anyway: https://privacy-handbuch.de/handbuch_31p.htm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: In Progress Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
I already assumed that would be the case^^ Thank you for the links Timo (y) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: In Progress Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Hi, If I could give an opinion from users perspective to this backport: I'm using 20.04 focal. My setup ist Thunderbird 68 + Enigmail + OpenPGP. With the Thunderbird 78 update users have to change their workflow. A few examples: User has disabled encryption per default, as most of it's recipients don't use encryption. If the keyring contains a key for all recipients, enigmail automatically enables encryption. This behavior is not possible with TB 78, you either have it enabled by default or not. Keys inside TB keyring don't have passphrases. To secure them, you have to set a master password for the keyring, which disables you to just look at some mailing lists, newletters, whatsoever without typing the keyring password. (workaround is to use for the private key an external keyring key) TB 78 doesn't offer the same capabilities (e.g. to alter your private keys to add another identity), as the old setup with TB 68 + Enigmail. If it would be just to port all keys to the internal keyring and everything else would be available as before (function wise, a few optical changes would not be problematic, as long as the functionality would be equal), fine. But that's not the case. Therefore I'd ask to take this into consideration updating the main thunderbird package in 20.04 and 18.04, as it surely will force those using encryption yet, to investigate how to replace their old setup. Maybe an option could be to provide the backport as a new package like thunderbird-78? Greetings, Lukas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: In Progress Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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
[Desktop-packages] [Bug 1802976] Re: [amdgpu] Horizontal black bars flicker across the screen
>From the description it sound similar to my problem with a Ryzen5 2500U: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825554 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1802976 Title: [amdgpu] Horizontal black bars flicker across the screen Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: 1) Ubuntu 18.04.1 LTS 31.4 GiB Ram AMD® Ryzen 5 1600 six-core processor × 12 AMD® Radeon (tm) rx 480 graphics 3.28.2 gnome 64-bit os 2) ?what? 3) see the desktop and apps without horizontal black bars flickering across the screen 4) horizontal black bars flicker across the screen over the desktop, apps and whatever is on screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 19:45:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2018-11-10 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e7adf075-12a7-4981-980a-dcdb43eeb260 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4023 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1802976/+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
