[Desktop-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
Any fixes for this yet? I have started to experience this in the last few days for Ubuntu 20.04 LTS. The only change was that the laptop battery was replaced. However, this problem does not occur on my dual- boot Windows 10, so this is probably not a hardware issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Bug description: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+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 1771880] Re: Seahorse unable to import pkcs12 certificates
Right, I do plan to cherry pick the gnome-keyring change at some point, I just started with gcr while waiting to see if a gnome-keyring upstream maintainer is still active to review the change -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gcr package in Ubuntu: Fix Committed Status in gnome-keyring package in Ubuntu: Triaged Status in seahorse package in Ubuntu: Triaged Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+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 2046001] Re: PipeWire: Too many open files
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3406 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 Importance: Unknown Status: Unknown -- 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/2046001 Title: PipeWire: Too many open files Status in PipeWire: Unknown Status in pipewire package in Ubuntu: New Bug description: Starting with Ubuntu 23.10 , PipeWire regularly started running into a file descriptor limits likely to a known leak which is already fixed upstream, therefore either updating or fix backporting would be required. Symptoms vary: - Media playback may not start - Media playback may start but without sound - Media playback may suppress the audio output of another source Sample log output: ``` mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.client-node: can't create node: Too many open files mod.protocol-native: connection 0x560d8f270390: could not recvmsg on fd:0: Bad file descriptor mod.protocol-native: 0x560d8ed941a0: connection_data: client 0x560d8f26fa50 error -9 (Bad file descriptor) ``` More info: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2046001/+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 1961508] Re: Dock displaying over window after resuming from blank screen
same problem for me on Ubuntu 22.04.3 with latest updates (GNOME 42), the Terminal window appears under the dock after sleep or screen lock. This is very annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2046360] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto" because the bug is in auto mode (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+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 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
This bug was fixed in the package mutter - 45.2-0ubuntu2~really45.0 --- mutter (45.2-0ubuntu2~really45.0) mantic; urgency=medium * Roll back to address regression LP: #2046360. - Full revert to mutter 45.0-3ubuntu3.1, with revert implemented under debian/patches to avoid having to keep around confusing version numbers for very long. - mutter 45.2 introduces new library symbols vs 45.0 but no packages have picked up dependencies on these symbols yet via rebuilds, and all binary packages built from mutter source have a strict versioned dependency on the library package; so a straight revert of the symbols file is possible without the need to add any additional Breaks. -- Steve Langasek Sun, 17 Dec 2023 19:44:15 -0800 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto" because the bug is in auto mode (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+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 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
This bug was fixed in the package mutter - 45.2-3ubuntu1 --- mutter (45.2-3ubuntu1) noble; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (45.2-3) experimental; urgency=medium [ Daniel van Vugt ] * Update Support-Dynamic-triple-double-buffering.patch with a fix to the frame clock for a regression inherited from 45.1 (8f27ebf8) whereby it would enter triple buffering mode prematurely. And because it was premature, the clock would soon notice that triple buffering isn't required and drop back to double buffering. But the switch from triple to double buffering stalls the client frame queue by one frame which for some clients like Firefox is seen as a frame skip. (LP: #2046360) mutter (45.2-2) experimental; urgency=medium * Team upload [ Chris Hofstaedtler ] * Honor udev.pc's udevdir when installing udev rules (Closes: #1057319) [ Simon McVittie ] * Merge with version 44.7-1 from unstable * d/control, d/rules: Stop generating d/control from d/control.in * d/patches: Mark several additional tests as flaky. Most of these have never been reliable on Debian buildds, especially on ARM, so having them fail is not a regression. They usually succeed after a few retries, but that's time-consuming and unsuitable to be a QA gate. The restore-size test was previously not run at all: now it is run, but marked as flaky (so its result is ignored). -- Jeremy Bícha Wed, 20 Dec 2023 09:32:48 -0500 ** Changed in: mutter (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto" because the bug is in auto mode (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+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 1771880] Re: Seahorse unable to import pkcs12 certificates
Pleasure Sebastien, that's how open-source works, we help each other and all win :-). I'm glad you are picking it up at the distro level, but that gcr-3 patch alone won't fix this issue, as it only comes into play after gnome- keyring-pkcs11.so is loaded, which won't happen without the gnome- keyring patch. If you don't like deleting the "enable-in" line, maybe rather try adding "seahorse" to the list of apps on that line instead? (You only need to edit /usr/share/p11-kit/modules/gnome-keyring.module before starting seahorse, which can be done without rebuilding the .deb) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gcr package in Ubuntu: Fix Committed Status in gnome-keyring package in Ubuntu: Triaged Status in seahorse package in Ubuntu: Triaged Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+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 2043863] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2043863/+attachment/5731285/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2043863 Title: Keyboard Settings Won't Open (Ubuntu Unity 23.10) Status in unity-control-center package in Ubuntu: Incomplete Bug description: Note: this is for the Unity flavour of Ubuntu. I tried opening "Keyboard". It wouldn't won't open. The app icon was blinking in that bar thing where all opened apps are. And then it went away after a couple seconds. I tried to go to System Settings, and Keyboard. It wouldn't go to Keyboard settings. System Settings disappeared. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 23.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Sorry, i don't know the package name. And Ubuntu Unity 23.10 didn't come with Software Center. 3) What you expected to happen I expected keyboard settings to open. 4) What happened instead It didn't open. I made sure system was up to date, and restarted pc. Still won't open. I tried looking for a solution. I tried running this in terminal: unity-control-center keyboard. It didn't open Keyboard settings. Here's what terminal said: amix@amix-XPS-8500:~$ unity-control-center keyboard (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.402: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 1, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/org/gnome/desktop/input-sources/" (establishing: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 3) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 4) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 5) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 6) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 7) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 8) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 9) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 10) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 11) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 12) (unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 13) (unity-control-center:10603): dconf-DEBUG:
[Desktop-packages] [Bug 2043863] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2043863/+attachment/5731286/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2043863 Title: Keyboard Settings Won't Open (Ubuntu Unity 23.10) Status in unity-control-center package in Ubuntu: Incomplete Bug description: Note: this is for the Unity flavour of Ubuntu. I tried opening "Keyboard". It wouldn't won't open. The app icon was blinking in that bar thing where all opened apps are. And then it went away after a couple seconds. I tried to go to System Settings, and Keyboard. It wouldn't go to Keyboard settings. System Settings disappeared. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 23.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Sorry, i don't know the package name. And Ubuntu Unity 23.10 didn't come with Software Center. 3) What you expected to happen I expected keyboard settings to open. 4) What happened instead It didn't open. I made sure system was up to date, and restarted pc. Still won't open. I tried looking for a solution. I tried running this in terminal: unity-control-center keyboard. It didn't open Keyboard settings. Here's what terminal said: amix@amix-XPS-8500:~$ unity-control-center keyboard (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.402: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 1, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/org/gnome/desktop/input-sources/" (establishing: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 3) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 4) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 5) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 6) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 7) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 8) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 9) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 10) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 11) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 12) (unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 13) (unity-control-center:10603):
[Desktop-packages] [Bug 2043863] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2043863/+attachment/5731287/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2043863 Title: Keyboard Settings Won't Open (Ubuntu Unity 23.10) Status in unity-control-center package in Ubuntu: Incomplete Bug description: Note: this is for the Unity flavour of Ubuntu. I tried opening "Keyboard". It wouldn't won't open. The app icon was blinking in that bar thing where all opened apps are. And then it went away after a couple seconds. I tried to go to System Settings, and Keyboard. It wouldn't go to Keyboard settings. System Settings disappeared. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 23.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Sorry, i don't know the package name. And Ubuntu Unity 23.10 didn't come with Software Center. 3) What you expected to happen I expected keyboard settings to open. 4) What happened instead It didn't open. I made sure system was up to date, and restarted pc. Still won't open. I tried looking for a solution. I tried running this in terminal: unity-control-center keyboard. It didn't open Keyboard settings. Here's what terminal said: amix@amix-XPS-8500:~$ unity-control-center keyboard (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.402: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 1, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/org/gnome/desktop/input-sources/" (establishing: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 3) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 4) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 5) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 6) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 7) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 8) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 9) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 10) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 11) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 12) (unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 13) (unity-control-center:10603): dconf-DEBUG:
[Desktop-packages] [Bug 2043863] Re: Keyboard Settings Won't Open (Ubuntu Unity 23.10)
I executed the command " apport-collect 2043863" if it helps ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-12-15 (5 days ago) InstallationMedia: Ubuntu-Unity 23.10 "Mantic Minotaur" - Release amd64 (20231010) Package: unity-control-center 15.04.0+23.04.20230220-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Tags: mantic Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True ** Tags added: apport-collected mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2043863 Title: Keyboard Settings Won't Open (Ubuntu Unity 23.10) Status in unity-control-center package in Ubuntu: Incomplete Bug description: Note: this is for the Unity flavour of Ubuntu. I tried opening "Keyboard". It wouldn't won't open. The app icon was blinking in that bar thing where all opened apps are. And then it went away after a couple seconds. I tried to go to System Settings, and Keyboard. It wouldn't go to Keyboard settings. System Settings disappeared. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 23.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Sorry, i don't know the package name. And Ubuntu Unity 23.10 didn't come with Software Center. 3) What you expected to happen I expected keyboard settings to open. 4) What happened instead It didn't open. I made sure system was up to date, and restarted pc. Still won't open. I tried looking for a solution. I tried running this in terminal: unity-control-center keyboard. It didn't open Keyboard settings. Here's what terminal said: amix@amix-XPS-8500:~$ unity-control-center keyboard (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/peripherals/keyboard/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.402: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 0, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: "/org/gnome/desktop/input-sources/" (establishing: 1, active: 0) (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: "/org/gnome/desktop/input-sources/" (establishing: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 1) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 2) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 3) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 4) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 5) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 6) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 7) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 8) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: "/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, active: 9) (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast:
[Desktop-packages] [Bug 2047046] Re: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-b
pipewire-bin 1.0.0-1~ubuntu23.10 comes from a PPA, it's not a package from Ubuntu repo. Your issue comes from this package, please report it to the PPA maintainer. The manpage of pipewire-pulse is in the wrong package pipewire-bin whereas it should be in pipewire-pulse ** Changed in: pipewire (Ubuntu) Status: New => Invalid -- 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/2047046 Title: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 Status in pipewire package in Ubuntu: Invalid Bug description: crashed when changing appearance ProblemType: Package DistroRelease: Ubuntu 24.04 Package: pipewire-pulse 1.0.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 17 03:57:20 2023 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 InstallationDate: Installed on 2023-07-08 (165 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: pipewire Title: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2047046/+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 2047046] [NEW] package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire
Public bug reported: crashed when changing appearance ProblemType: Package DistroRelease: Ubuntu 24.04 Package: pipewire-pulse 1.0.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 17 03:57:20 2023 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 InstallationDate: Installed on 2023-07-08 (165 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: pipewire Title: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble 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/2047046 Title: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 Status in pipewire package in Ubuntu: New Bug description: crashed when changing appearance ProblemType: Package DistroRelease: Ubuntu 24.04 Package: pipewire-pulse 1.0.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 17 03:57:20 2023 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 InstallationDate: Installed on 2023-07-08 (165 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: pipewire Title: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2047046/+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 1845601] Re: Images blurry in Background selection screen when scaling > 100%
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1845601 Title: Images blurry in Background selection screen when scaling > 100% Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce: 0. Go to Settings > Devices > Displays and make sure the scaling is 200% or more 1. Go to Settings > Background Expected result: 1. The thumbnails for the suggested backgrounds are sharp Actual result: 1. The thumbnails are blurry. I attached 3 screenshots of the Background screen at different scales (100%, 200%, 300%). This is a problem for people with UHD (4K) screens which are likely to select a 200% scaling. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 15:03:35 2019 InstallationDate: Installed on 2019-09-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1845601/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Hi, I'm on Ubuntu 23.10 using Brave browser SNAP and I still face the
issue (cannot open links in evince -using Brave browser snap).
Here are the versions:
```console
❯ apt list --installed | rg 'evince|apparmor'
apparmor/mantic,now 4.0.0~alpha2-0ubuntu5 amd64 [installed,automatic]
evince-common/mantic,mantic,now 45.0-1 all [installed,automatic]
evince/mantic,now 45.0-1 amd64 [installed]
libapparmor1/mantic,now 4.0.0~alpha2-0ubuntu5 amd64 [installed,automatic]
```
Brave Browser 120.1.61.101
`journalctl -f` log:
```console
Dec 20 12:18:37 laptop kernel: audit: type=1400 audit(1703071117.044:3565):
apparmor="DENIED" operation="open" class="file"
profile="/usr/bin/evince//snap_browsers" name="/proc/cgroups" pid=1351803
comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Dec 20 12:18:37 laptop brave_brave.desktop[1351803]: internal error, please
report: running "brave" failed: open /snap/brave/323/meta/snap.yaml: permission
denied
Dec 20 12:18:37 laptop kernel: audit: type=1400 audit(1703071117.052:3566):
apparmor="DENIED" operation="open" class="file"
profile="/usr/bin/evince//snap_browsers" name="/snap/brave/323/meta/snap.yaml"
pid=1351803 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
```
I see the following in `/etc/apparmor.d/usr.bin.evince` with all
includes commented, including `snap_browsers` line. Is that normal?
Thanks
```
│ File: /etc/apparmor.d/usr.bin.evince
│ Size: 11.5 KB
───┼
1 │ # vim:syntax=apparmor
2 │
3 │ # evince is not written with application confinement in mind and is
designed to
4 │ # operate within a trusted desktop session where anything running
within the
5 │ # user's session is trusted. That said, evince will often process
untrusted
6 │ # input (PDFs, images, etc). Ideally evince would be written in such a
way that
7 │ # image processing is separate from the main process and that
processing
8 │ # happens in a restrictive sandbox, but unfortunately that is not
currently the
9 │ # case. Because evince will process untrusted input, this profile aims
to
10 │ # provide some hardening, but considering evince's design and other
factors such
11 │ # as X, gsettings, accessibility, translations, DBus session and system
12 │ # services, etc, complete confinement is not possible.
13 │
14 │ #include
15 │
16 │ /usr/bin/evince {
17 │ #include
18 │ #include
19 │ #include
20 │ #include
21 │ #include
22 │ #include
23 │ #include
24 │
25 │ #include
26 │ #include
27 │ #include
28 │ #include
29 │ #include
30 │
31 │ # allow evince to spawn browsers distributed as snaps (LP: #1794064)
32 │ #include if exists
33 │
34 │ # For now, let evince talk to any session services over dbus. We can
35 │ # blacklist any problematic ones (but note, evince uses libsecret :\)
36 │ #include
37 │
38 │ #include
39 │ dbus (receive) bus=system,
```
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink in a PDF fails to open it if the default browser
is a snap
Status in apparmor package in Ubuntu:
Fix Released
Status in evince package in Ubuntu:
Fix Released
Status in apparmor source package in Jammy:
Fix Released
Status in evince source package in Jammy:
Fix Released
Status in apparmor source package in Lunar:
Fix Released
Status in evince source package in Lunar:
Fix Released
Status in apparmor package in Debian:
Fix Released
Status in evince package in Debian:
Confirmed
Bug description:
[Impact]
* Users cannot open a hyperlink in a PDF opened with evince when the default
browser is a snap.
* The fix creates a snap_browsers abstraction on AppArmor which can be used
in a transition for when the browser is executed. The snap_browsers abstraction
provides the minimal amount of permissions required to execute a browser
provided through snaps. This is a workaround since AppArmor currently does not
provide mediation/filtering on enhanced environment variables.
[Test Plan]
* Make sure the default browser is provided through the snap store.
* Open a PDF that contains a hyperlink using evince and click on the URL.
* The browser should open the requested URL.
[Where problems could occur]
* If the browser or snap core update to have new requirements for
opening a browser, then the current policy could become obsolete and
will need to be updated again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to :
[Desktop-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop
I also made a mistake with a person who can help with this problem https://github.com/codepayne/linux-sound-huawei/issues/27 ** Bug watch added: github.com/codepayne/linux-sound-huawei/issues #27 https://github.com/codepayne/linux-sound-huawei/issues/27 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+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 1771880] Re: Seahorse unable to import pkcs12 certificates
Thanks Damjan for the investigation work and the fixes, I've cherrypicked the gcr fix and uploaded to Debian now (which will sync to Ubuntu later today). I would prefer to see an upstream review for the keyring change before distro patching that one since the situation there is a bit more complicated ** Also affects: gcr (Ubuntu) Importance: Undecided Status: New ** Changed in: gcr (Ubuntu) Importance: Undecided => High ** Changed in: gcr (Ubuntu) Status: New => Fix Committed ** Changed in: gcr (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gcr package in Ubuntu: Fix Committed Status in gnome-keyring package in Ubuntu: Triaged Status in seahorse package in Ubuntu: Triaged Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+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 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
** Description changed: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always - or "never" also works. Just not "auto". + or "never" also works. Just not "auto" because the bug is in auto mode + (the default). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto" because the bug is in auto mode (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+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 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
Proposed fix for 45.2 (we usually go through Debian first because that's where the patch is maintained): https://salsa.debian.org/gnome-team/mutter/-/merge_requests/114 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+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 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
Also verified fixed in mantic using version 45.2-0ubuntu2~really45.0 and the test case that's now in the Bug Description above. ** Description changed: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] - Since the bug only hurts the triple buffering patch, that's where it has - been fixed upstream: + The bug was introduced upstream in 45.1 by + https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d + but since it only hurts the triple buffering patch, that's where it has + been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+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 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
** Description changed: - There is heavy stuttering visible in Firefox with mutter 45.1/45.2. This - is a regression introduced upstream in mutter 45.1 (8f27ebf8), although - it only hurts the triple buffering patch so that's where it's fixed: + [ Impact ] + + There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when + kinetic scrolling a non-animated web page with a touchpad. This is a + regression introduced upstream in mutter 45.1 (8f27ebf8). + + [ Test Plan ] + + 0. Find a laptop with a touchpad. + 1. Open a simple web page like a Wikipedia page in Firefox. + 2. Use two fingers on the touchpad to fling it so it continues scrolling. + + Expect: The scrolling proceeds and slows perfectly smoothly. + + [ Where problems could occur ] + + Anywhere in frame scheduling (visual smoothness), since that is the code + affected. + + [ Other Info ] + + Since the bug only hurts the triple buffering patch, that's where it has + been fixed upstream: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+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 2047008] Re: [SRU] Add Telit FN990 compositions
The verified log is attached. ** Attachment added: "modemmanager_1.20.0-1~ubuntu22.04.3_verified.log" https://bugs.launchpad.net/oem-priority/+bug/2047008/+attachment/5730937/+files/modemmanager_1.20.0-1~ubuntu22.04.3_verified.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+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 2047008] Re: [SRU] Add Telit FN990 compositions
The debdiff is attached. ** Patch added: "modemmanager_1.20.0-1~ubuntu22.04.3.debdiff" https://bugs.launchpad.net/oem-priority/+bug/2047008/+attachment/5730935/+files/modemmanager_1.20.0-1~ubuntu22.04.3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+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
